[6bone] winding down and returns?

[Jeroen Massar]

-----BEGIN PGP SIGNED MESSAGE-----

Antonio Querubin wrote:

> On Thu, 18 Dec 2003, Jeroen Massar wrote:
> 
> > Afaik, the process is quite simple:
> >  - stop announcing the prefix into BGP
> >  - remove prefixes (inet6num, ipv6-site etc) from the 6bone registry
> 
> Are there any other alternate registries for tracking BGP 
> peering/tunnels between IPv6 networks?  We use the RADB for IPv4 prefixes but 
> it has no provision for handling IPv6 route objects as far as I can 
> tell.  I think the 6bone registry still serves a useful purpose in this area 
> for those of us peering with ASNs still using 6bone prefixes.

One can document import/export rules like in:

http://www.noc.easynet.net/network/public/whois.cgi?Whois=-r%20-a%20-T%20aut-num%20AS4589

For the rest one has to wait for RPSLng to be deployed, but afaik
that is nearing completion. RADB and RIPE will at least support this
and so will APNIC at the least. I am wondering what the state of both
ARIN and LACNIC's implementations are though.

> >  - notify this (6bone@mailman.isi.edu) list that your organisation
> >    is returning the prefix and not using it any more.
> 
> Ok, we're officially returning 3ffe:8160::/28.  There are 
> still some BGP
> links using a few addresses out there but they'll be renumbered soon.

It, nor any more specifics, where seen by GRH since 01-12-2003,
thus it looks it is globally gone already.

Greets,
 Jeroen

-----BEGIN PGP SIGNATURE-----
Version: Unfix PGP for Outlook Alpha 13 Int.
Comment: Jeroen Massar / jeroen@unfix.org / http://unfix.org/~jeroen/

iQA/AwUBP+I90imqKFIzPnwjEQLyxQCeJkt4Jpg3/l3iix95VkZZVbBxqbAAn1tr
PPgAaMa9DEQKFoRQTPCeUU3r
=Wyk1
-----END PGP SIGNATURE-----