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]/

[ipv6-wg at ripe.net] 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): [ipv6-wg at ripe.net] Re: RPSLng in the RIPE Whois Database

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

Bernhard Schmidt berni at birkenwald.de
Wed Dec 15 19:31:22 CET 2004

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.

Bernhard

Previous message (by thread): [ipv6-wg at ripe.net] RPSLng in the RIPE Whois Database
Next message (by thread): [ipv6-wg at ripe.net] Re: RPSLng in the RIPE Whois Database

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

[ ipv6-wg Archives ]