http://www.6assist.net/ - call for test

[Max Tulyev]

Easy, just set up the BGP session using 6to4 address space ;)

Still there are some major problems:
1. Unlike IXP-like infrastructure, it is difficult to set up and
maintain a lot of BGP sessions ("each to each mesh").
2. The 6to4 infrastructure is unstable. The reachability of 6to4 address
is a far away from 100%.
3. Your connectivity quality highly depends on 3rd party gate servers,
often has non-optimal paths from/to it, it can be overloaded, has a
packet loss and so on.

On 10.05.13 16:47, Tayeb Meftah wrote:
> Ole
> How do bgp tunelling over 6to4 works?
> 
> Envoyé de mon iPhone
> 
> Le 10 mai 2013 à 15:02, Ole Troan <otroan at cisco.com> a écrit :
> 
>> Max,
>>
>>> I mentioned Slovenia as we have a request for BGP-enabled tunnel from
>>> Slovenia ;) So for some reasons people still want to use BGP-enabled
>>> tunnels in real life, even in conuntries with well implemented native IPv6.
>>>
>>> The second reason to use 6assist instead of regular TB it is not depend
>>> of the actual load of tunnel server. If somebody download something huge
>>> through a tunnel broker server - the other people just share the tiny
>>> rest of the bandwidth...
>>
>> if you go down this path, you could rather do BGP tunnelling.
>> as in run BGP sessions between the peers, exchange native IPv6 prefixes, but use a 6to4
>> next-hop. that achieves the mesh properties you are looking for with an existing mechanism.
>> of course someone will have to advertise a default route somewhere.
>>
>> cheers,
>> Ole
>