[db-wg] RPSL for for foreigh IPv6 space
- Previous message (by thread): [db-wg] RPSL for for foreigh IPv6 space
- Next message (by thread): [db-wg] RPSL for for foreigh IPv6 space
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ben Cartwright-Cox
ripencc at benjojo.co.uk
Sun Jun 23 22:41:17 CEST 2024
Have you considered renumbering to avoid being in this situation ;)? NTT has a IRR, NTTCOM, where I am unsure if Cogent uses that, or if RADB mirrors it. I suspect your path to success will be to register the objects in RADB yourself, find some kind person who already has a subscription to do it for you. On Sun, Jun 23, 2024, 18:43 Randy Bush via db-wg <db-wg at ripe.net> wrote: > hi, > > All of RGnet's address space, mostly legacy, is in the RIPE whois, with > RPKI etc. Except ... RGnet has three IPv6 /48s from NTT. > > Cogent filters BGP based on RPSL, and wants the RPSL for our ASs to be > in the appropriate RPSL route6: objects, each with the appropriate AS. > This is pretty old-fashioned and reasonable. > > Do we figure out how to register the route6: objects in NTT and presume > Cogent will pick them up across IRR instances? Do we try some hack to > violate the RIPE database's pristine authority model? Do we give up on > this silly IPv6 stuff? [ just kidding, gert :) ] > > Surely other have been here before us. > > randy > > -- > > To unsubscribe from this mailing list, get a password reminder, or change > your subscription options, please visit: > https://lists.ripe.net/mailman/listinfo/db-wg > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ripe.net/ripe/mail/archives/db-wg/attachments/20240623/07621c27/attachment.html>
- Previous message (by thread): [db-wg] RPSL for for foreigh IPv6 space
- Next message (by thread): [db-wg] RPSL for for foreigh IPv6 space
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]