[OCCAID] New path to KAME

[Scott J. Clifford]

On Fri, Jan 28, 2005 at 09:24:16PM -0500, James wrote:
> [ snip ]
> > 
> > Sorry if I'm hijacking your thread.. But speaking of 30071:30071 community routes, I
> > have a question.
> > 
> > 2001:770::/35       *[BGP/170] 21:29:29, MED 0, localpref 100, from 3ffe:401d:f00::1
> >                       AS path: 30071 1273 3549 1213 1213 1213 1213 I
> >                     > to 2001:468:d01:3c::1 via fe-0/0/0.0
> > 
> > Any reason to why we are doing this? We have transit from 3549 where HEAnet is
> > downstream of it. AFAIK, 3549 does not run a low performance network that are
> > seen in 30071:6969 routes.
> > 
> > Thanks!!
> > 
> > Scott.
> 
> You are right in that 3549 is a good network with sane routing. But we don't
> have 3549 transit in east coast. We have that in west coast and Chicago only.
> 
> HEAnet is one of the "popular" or otherwise "well-known" destinations that
> often resulted in complaint by end user that their FreeBSD port-tree is
> downloading so slow over ipv6 whenever going via heanet sourceforge mirror,
> *IN THE PAST*. 
> 
> Since we made changes on the network last week, including turning 6830 as a
> peer, and converting 6175 into peer as well (not done yet) path to HEAnet had
> got much better as we reconsolidated our routes to Europe. In order to improve
> it more, we'd rather cold-potato the outbound packets all the way to east point
> forward instead of having to go back to west or Chicago to exit the American
> continent to reach HEAnet.
> 
> Makes sense? :)
Indeed. Thanks

Scott.

> 
> -J
> 
> -- 
> James Jun                                            TowardEX Technologies, Inc.
> Technical Lead                      Boston IPv4/IPv6 Web Hosting, Colocation and
> james at towardex.com            Network design/consulting & configuration services
> cell: 1(978)-394-2867           web: http://www.towardex.com , noc: www.twdx.net