[6bone] Re: routing concern
Petr Baudis
pasky@pasky.ji.cz
Thu, 1 Aug 2002 08:25:55 +0200
Dear diary, on Thu, Aug 01, 2002 at 03:23:19AM CEST, I got a letter,
where Rik van Riel <riel@conectiva.com.br> told me, that...
> On Thu, 1 Aug 2002 itojun@iijlab.net wrote:
>
> > the problem is that there's no distinction between sTLA cloud and pTLA
> > cloud - they are overwrapped, and most of sTLA sites do hold pTLA
> > address with them too.
> >
> > if we could split these two clouds into two (interconnected via few
> > routers), it would be very nice, but i don't think it is going to be
> > possible. so we need to harden 6bone (= pTLA cloud).
>
> One thing possible to make 6bone traffic more reliable is
> BGP confederations. Inside the COMPENDIUM pTLA we have
> multiple ipv6 islands in a BGP confederation, advertising
> the same BGP AS number to external peers and non-confed
> islands in the pTLA.
>
> If routing to one of the central ipv6 islands is lost,
> the packets will be routed via one of the others.
>
> Of course, performance is bad in a pTLA as geographically
> dispersed as COMPENDIUM, but ipv6 has proven to be much
> more reliable for me than ipv4 has ever been.
>
> This idea could be used by organisations who are close to
> each other geographically and by hop count ... something
> vaguely like multihoming, without violating RFC 2772.
>
> Having 4 well-connected (to each other) sites participate
> in the same pTLA and same BGP confederation could make the
> 6bone traffic more reliable for both the sites themselves
> and the peers they transit for.
>
> Performance can be regained later when the sites move to
> native ipv6 links.
Well, this concept is already tested on 6bone - it's exactly what we do inside
XS26 (now almost even with the last paragraph :).
--
Petr "Pasky" Baudis
* ELinks maintainer * IPv6 guy (XS26 co-coordinator)
* IRCnet operator * FreeCiv AI occassional hacker
.
You can get much further with a kind word and a gun than you can with a
kind word alone. -- Al Capone
.
Public PGP key && geekcode && homepage: http://pasky.ji.cz/~pasky/