[6bone] 3ffe/2001:0 et.al.

Bill Manning bmanning@ISI.EDU
Tue, 19 Nov 2002 06:24:47 -0800 (PST)


Ok, so here is an alternate view

presume AS 4554 has the following delegations:

	3ffe:08::/24
	2001:0478::/32

and there is a mix of hosts, routers, and links (local/wide)

local links all run native IPv6 and there is a mix of native and tunneled
IPv6 over the wan links.

Due to acidents of history, 3ffe and 2001 addresses are used on both 
lan and wan links.

Perhaps it would be worthwhile to ask folks to consider doing the
following:

	for native IPv6 connections, use 2001 space.
	for tunnels between IPv6 islands over IPv4 only space,
	use 3ffe space.

this will ensure that, at least for AS 4554, any exposure of 3ffe space
will reflect the "knitting" of native IPv6 networks together over tunneled
environments. e.g. the 6bone.

then comes the fun part... :)

AS 4554 would be injecting a single 3ffe prefix into the routing system,
3ffe:08::/24.  Thats a whole bunch of p2p tunnels.  There are only ~30 tunnels
for this AS.  One could renumber all the tunnels into one end of the address
range, making the effective used space something like:
3ffe:8::/120

AS 4554 would like to remove the 3ffe:08::/24 in the routing system and 
replace it in the routing system with 3ffe:08::/120
As AS 4554 removes/replaces tunnels with native connectivity, the
routing announcement will shrink, from a /120, to a /122, to a /126
and then zero, which indicates that AS 4554 is no longer using tunnels
to link v6 islands (e.g. no 6bone!)



--bill