[30347] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Qwest and US WEST (non) routing problems

daemon@ATHENA.MIT.EDU (Bessant, Chuck)
Thu Jul 27 14:35:25 2000

Message-ID: <1BB5F59166EBD211B1860008C7E947D3023B32EB@denverx2.dnvr.firstworld.com>
From: "Bessant, Chuck" <Chuck.Bessant@firstworld.com>
To: nanog@nanog.org
Date: Thu, 27 Jul 2000 11:32:34 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFF7F9.13F35136"
Errors-To: owner-nanog-outgoing@merit.edu


This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01BFF7F9.13F35136
Content-Type: text/plain;
	charset="iso-8859-1"

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?

Thanks.

Chuck

------_=_NextPart_001_01BFF7F9.13F35136
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2650.12">
<TITLE>Qwest and US WEST (non) routing problems</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I have been working a ticket with Qwest regarding our =
upstream through them in Portland.&nbsp; 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.&nbsp; This =
AS serves the NW and the Denver area according to this engineer.&nbsp; =
</FONT></P>

<P><FONT SIZE=3D2>THE CAVEAT as related by the engineer is as =
follows:&nbsp; our advertisements should, technically, be propagated =
out to the Internet...however, all traffic would first hit Qwest's =
network, then go through the Cable &amp; 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.&nbsp; </FONT></P>

<P><FONT SIZE=3D2>Has anyone experienced this problem with AS3908 &amp; =
Qwest?</FONT>
</P>

<P><FONT SIZE=3D2>Thanks.</FONT>
</P>

<P><FONT SIZE=3D2>Chuck</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01BFF7F9.13F35136--


home help back first fref pref prev next nref lref last post