[30401] in North American Network Operators' Group
Re: Qwest and US WEST (non) routing problems
daemon@ATHENA.MIT.EDU (Scott Call)
Wed Aug 2 19:34:11 2000
Message-ID: <3988B0A9.1000105@devolution.com>
Date: Wed, 02 Aug 2000 16:37:13 -0700
From: Scott Call <scall@devolution.com>
MIME-Version: 1.0
To: "Bessant, Chuck" <Chuck.Bessant@firstworld.com>
Cc: nanog@nanog.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Errors-To: owner-nanog-outgoing@merit.edu
Bessant, Chuck wrote:
>
> I have been working a ticket with Qwest regarding our upstream through
> them in Portland. I was informed by a Qwest engineer that, as a
> result of their merger with US West, they are under an FCC mandate not
> to traffic data directly through AS3908. This AS serves the NW and
> the Denver area according to this engineer.
>
> THE CAVEAT as related by the engineer is as follows: our
> advertisements should, technically, be propagated out to the
> Internet...however, all traffic would first hit Qwest's network, then
> go through the Cable & Wireless network, then back through Qwest to
> us...in other words, even if our routes *were* being propagated
> properly, we would probably have to do some kind of prepending or
> other preferencing to get traffic flowing in Qwest's direction and
> even then it would certainly not be an optimal path through the network.
>
> Has anyone experienced this problem with AS3908 & Qwest?
>
We killed our "Not-Qwest" transit because of *10 latency last friday.
Anyone had any good experience with "Not-Qwest" in the pacific north-west?
-scott
> Thanks.
>
> Chuck
>
--
------------------------------------------------------------------------
Scott Call | Perhaps the best way to keep kids from turning on
Router Geek | their classmates is to protect them in the first
Advanced Telcom Group| place, -jonkatz
