Dear colleagues, At the DB-WG session at RIPE 91, Peter Hessler requested that the Database team look at the RIPE-NONAUTH database and find all the objects that were created under IANA or ICANN action: https://ripe91.ripe.net/programme/meeting-plan/sessions/38/transcript/
Using the IANA special puropose registry files, we found the following RIPE-NONAUTH objects referencing an IANA special purpose resource. Also some objects referencing an IANA or ICANN role or maintainer. Can we confirm whether any of these objects were actually created under IANA or ICANN action? Is there an opportunity to clean up or migrate any of these objects out of the RIPE-NONAUTH database? --- >From ASN : >https://www.iana.org/assignments/iana-as-numbers-special-registry/iana-as-numbers-special-registry.xhtml We found one matching ASN (AS112). >From IPv4 : >https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml We found 21 RIPE-NONAUTH routes matching a prefix in the special registry: 192.88.99.0/24 appears in a RIPE-NONAUTH ROUTE 192.88.99.0/24AS1741 192.175.48.0/24 appears in a RIPE-NONAUTH ROUTE 192.175.48.0/24AS112 192.88.99.0/24 appears in a RIPE-NONAUTH ROUTE 192.88.99.0/24AS3344 192.88.99.0/24 appears in a RIPE-NONAUTH ROUTE 192.88.99.0/24AS20640 192.88.99.0/24 appears in a RIPE-NONAUTH ROUTE 192.88.99.0/24AS5408 192.88.99.0/24 appears in a RIPE-NONAUTH ROUTE 192.88.99.0/24AS1835 192.88.99.0/24 appears in a RIPE-NONAUTH ROUTE 192.88.99.0/24AS15598 192.88.99.0/24 appears in a RIPE-NONAUTH ROUTE 192.88.99.0/24AS680 192.88.99.0/24 appears in a RIPE-NONAUTH ROUTE 192.88.99.0/24AS25192 192.88.99.0/24 appears in a RIPE-NONAUTH ROUTE 192.88.99.0/24AS35244 192.88.99.0/24 appears in a RIPE-NONAUTH ROUTE 192.88.99.0/24AS39326 192.88.99.0/24 appears in a RIPE-NONAUTH ROUTE 192.88.99.0/24AS5413 192.88.99.0/24 appears in a RIPE-NONAUTH ROUTE 192.88.99.0/24AS25308 192.88.99.0/24 appears in a RIPE-NONAUTH ROUTE 192.88.99.0/24AS3243 192.88.99.0/24 appears in a RIPE-NONAUTH ROUTE 192.88.99.0/24AS29076 192.88.99.0/24 appears in a RIPE-NONAUTH ROUTE 192.88.99.0/24AS29632 192.88.99.0/24 appears in a RIPE-NONAUTH ROUTE 192.88.99.0/24AS8903 192.88.99.0/24 appears in a RIPE-NONAUTH ROUTE 192.88.99.0/24AS21416 192.88.99.0/24 appears in a RIPE-NONAUTH ROUTE 192.88.99.0/24AS43097 192.31.196.0/24 appears in a RIPE-NONAUTH ROUTE 192.31.196.0/24AS112 192.88.99.0/24 appears in a RIPE-NONAUTH ROUTE 192.88.99.0/24AS50113 >From IPv6 : >https://www.iana.org/assignments/iana-ipv6-special-registry/iana-ipv6-special-registry.xhtml We found 26 RIPE-NONAUTH route6's matching a prefix in the special registry : 2002::/16 appears in a RIPE-NONAUTH ROUTE6 2002::/16AS29259 2002::/16 appears in a RIPE-NONAUTH ROUTE6 2002::/16AS559 2002::/16 appears in a RIPE-NONAUTH ROUTE6 2002::/16AS3344 2002::/16 appears in a RIPE-NONAUTH ROUTE6 2002::/16AS20640 2001::/23,2001::/32 appears in a RIPE-NONAUTH ROUTE6 2001::/32AS1741 2002::/16 appears in a RIPE-NONAUTH ROUTE6 2002::/16AS1741 2002::/16 appears in a RIPE-NONAUTH ROUTE6 2002::/16AS1835 2002::/16 appears in a RIPE-NONAUTH ROUTE6 2002::/16AS8473 2002::/16 appears in a RIPE-NONAUTH ROUTE6 2002::/16AS15598 2001::/23,2001::/32 appears in a RIPE-NONAUTH ROUTE6 2001::/32AS25525 2001::/23,2001::/32 appears in a RIPE-NONAUTH ROUTE6 2001::/32AS1101 2002::/16 appears in a RIPE-NONAUTH ROUTE6 2002::/16AS12871 2002::/16 appears in a RIPE-NONAUTH ROUTE6 2002::/16AS680 2002::/16 appears in a RIPE-NONAUTH ROUTE6 2002::/16AS35244 2002::/16 appears in a RIPE-NONAUTH ROUTE6 2002::/16AS39326 2002::/16 appears in a RIPE-NONAUTH ROUTE6 2002::/16AS5413 2001::/23,2001::/32 appears in a RIPE-NONAUTH ROUTE6 2001::/32AS25308 2002::/16 appears in a RIPE-NONAUTH ROUTE6 2002::/16AS25308 2001::/23,2001::/32 appears in a RIPE-NONAUTH ROUTE6 2001::/32AS44980 2002::/16 appears in a RIPE-NONAUTH ROUTE6 2002::/16AS29632 2620:4f:8000::/48 appears in a RIPE-NONAUTH ROUTE6 2620:4f:8000::/48AS112 2002::/16 appears in a RIPE-NONAUTH ROUTE6 2002::/16AS8903 2002::/16 appears in a RIPE-NONAUTH ROUTE6 2002::/16AS21416 2001::/23,2001::/32 appears in a RIPE-NONAUTH ROUTE6 2001::/32AS57801 2002::/16 appears in a RIPE-NONAUTH ROUTE6 2002::/16AS43097 2001::/23,2001:4:112::/48 appears in a RIPE-NONAUTH ROUTE6 2001:4:112::/48AS112 Additionally, we found some RIPE-NONAUTH objects referencing the IANA1-RIPE role (but not necessarily referencing the IANA special registry) : (using the query: "-r -i pn IANA1-RIPE -s RIPE-NONAUTH"): aut-num: AS1209 aut-num: AS131075 aut-num: AS132199 aut-num: AS1749 aut-num: AS19929 aut-num: AS270 aut-num: AS3 aut-num: AS37004 aut-num: AS395164 aut-num: AS4775 as-set: AS37148:AS-GLOBACOM Also some RIPE-NONAUTH objects referencing the ICANN-DNS maintainer : (using the query -r -i mnt-by ICANN-DNS -s RIPE-NONAUTH) aut-num: AS20144 aut-num: AS26710 route: 192.0.40.0/24AS20144 route: 192.0.41.0/24AS20144 route: 199.253.182.0/24AS26710 route: 199.253.183.0/24AS26710 route: 199.4.138.0/24AS26710 route: 199.7.82.0/23AS20144 route: 199.7.83.0/24AS20144 route: 199.7.94.0/24AS20144 route: 199.7.95.0/24AS20144 route6: 2001:500:3::/48AS20144 route6: 2001:500:86::/48AS26710 route6: 2001:500:87::/48AS26710 route6: 2001:500:89::/48AS26710 route6: 2001:500:9c::/48AS20144 route6: 2001:500:9d::/48AS20144 route6: 2001:500:9e::/47AS20144 route6: 2001:500:9f::/48AS20144 route6: 2620:0:22b0::/48AS20144 route6: 2620:0:2ee0::/48AS20144 Finally some RIPE-NONAUTH objects referencing the ICANN-MEETINGS maintainer : (using the query -r -i mnt-by ICANN-MEETINGS -s RIPE-NONAUTH) aut-num: AS27500 route: 199.91.192.0/21AS27500 route6: 2620:f:8000::/48AS27500 --- Regards Ed Shryane RIPE NCC > On 17 Jul 2025, at 18:07, Edward Shryane <[email protected]> wrote: > > Dear colleagues, > ... ----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/db-wg.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
