Ipv6 Routing (from hell)

Kim Hawtin kim at hawtin.net.au
Thu Mar 27 21:16:48 CET 2008


Jeroen Massar wrote:
> Bernhard Schmidt wrote:
> [..]
>>> 3) There are multiple tunnels to the tunnel broker, but all are 
>>> routing the
>>>   same /48. which then decides where to
>>>   send subsets of the /48 based on (some) set of oslr statistical 
>>> feedback via whatever
>>>   protocol, presumably BGP.  Who listens? Does any tunnel broker do 
>>> this?
>>
>> This was an idea I had as well. I don't think any public tunnelbroker 
>> can or will offer this
> 
> We (SixXS) have thought about this, 

This assumes you can actually get a login with SixXs.

They have a rather interesting policy about information required to 
setup logins, then of course theres the issue about no duplicate logins
for the same person.

It would be nice if they bothered to respond to their email to resolve
issues ;)

 > thus allowing people to have multiple tunnels to the same, or,
 > if the ISP is the same and are happy with it, to different PoPs.

One of our local ISPs is currently tinkering with IPv6 for their 
services and is working through the ideas for native IPv6 services,
AFAIK.

> Thus the ISP takes care of the global routing, thus only their /32 etc.
 > Internally one would have a few more routes though.
 > But that all depends on time for actually implementing it and it is
 > notsomething that a lot of people will use thus is not a high
 > priority.


> In Michael's case though, we don't have a closeby tunnelbroker though, 
> thus that would be one of the first things to get going.

In Australia AARNET has a tunnel broker, but ISPs are not widely 
connected/peered with them, AFAIK, despite AARNET having a wide coverage 
across Australia.

> As Bernhard mentioned, that is in effect just a colo'd box with a large 
> amount of IPv6 space routed to it.

regards,

Kim


More information about the ipv6-ops mailing list