This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/

[db-wg] RPSL for for foreigh IPv6 space

Previous message (by thread): [db-wg] RIPE Policy document updated “IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region” (ripe-826)
Next message (by thread): [db-wg] RPSL for for foreigh IPv6 space

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Randy Bush randy at psg.com
Sun Jun 23 19:42:45 CEST 2024

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

Previous message (by thread): [db-wg] RIPE Policy document updated “IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region” (ripe-826)
Next message (by thread): [db-wg] RPSL for for foreigh IPv6 space

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]