I did a spot check of a few ASNs and it looks to me as though the following ASNs have route(6) objects that only exist in NTTCOM: 2906, 20940 and 33438. (Stopped looking after I found these three.) My recommendation is to include NTTCOM. The cruft in the database should be suppressed according to https://www.gin.ntt.net/support-center/policies-procedures/routing-registry/.... [http://images.midcocomm.com/ES_MidcoLogo.png] Miles McCredie Principal Network Engineer II-Core IP Office: 6052755192 Miles.McCredie@midco.com Midco.com From: MICE Discuss <MICE-DISCUSS@LISTS.IPHOUSE.NET> On Behalf Of Richard Laager Sent: Thursday, May 11, 2023 11:52 PM To: MICE-DISCUSS@LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] [EXTERNAL] - Re: [MICE-DISCUSS] IRR Mandatory at MICE / New Route Servers On 2023-05-11 05:58, Miles McCredie wrote: I think a global list of sources would be easier to maintain and document. Excellent point. Is NTTCOM no longer trusted? The available sources are here: https://www.radb.net/query/?advanced_query=1 That does include NTTCOM, so we could use it. But if nobody is speaking up in favor of it, I'm not currently planning on it. The list I gave was the union of all choices that exist in IXP Manager by default, minus ARIN-NONAUTH and RIPE-NONAUTH. -- Richard ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1