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]/
RPSLng in the RIPE Whois Database
- Previous message (by thread): [ipv6-wg at ripe.net] RPSLng in the RIPE Whois Database
- Next message (by thread): [afnog] New IPv6 Address Block Allocated to RIPE NCC
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Engin Gunduz
engin at ripe.net
Tue Dec 21 14:07:58 CET 2004
Hi Bernhard, On 2004-12-15 19:31:22 +0100, Bernhard Schmidt wrote: > Hi, > > > Beginning Wednesday 29 December 2004, the RIPE Database will support > > RPSLng. > > This is great, I really appreciate that. > > Now, any comments about registering route6-objects for 6to4 prefix > (2002::/16)? I would suggest a solution like it is already done for the > IPv4 part (192.88.99.0/24), perhaps even use the same maintainer. > 2002::/16 isn't RFC3068 per se, but since 3068 and the appropriate parts > in 3056 are strictly tied and 6to4 relays are mostly bidirectional > (announcing IPv4 and IPv6 prefix) it wouldn't hurt to use RFC3068-MNT > here, too. > > The initial object would need to be created by RIPE NCC though, due to > missing mnt-routes in ::0/0. OK, we will add "mnt-routes: RIPE-NCC-RPSL-MNT" to the 0::/0 inet6num object during the transition. Regards, > > Bernhard -- Engin Gunduz RIPE NCC Software Engineering Department
- Previous message (by thread): [ipv6-wg at ripe.net] RPSLng in the RIPE Whois Database
- Next message (by thread): [afnog] New IPv6 Address Block Allocated to RIPE NCC
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]