Cogent now peering with Sprint?

Patrick W. Gilmore patrick at ianai.net
Tue Oct 31 13:12:59 UTC 2006


On Oct 31, 2006, at 2:12 AM, Bob Collie wrote:

> That looks like a transit connection that Cogent bought at Ashburn,  
> VA,
> not SFI peering connection.

Hrmm, I can't tell by looking at a traceroute who paid whom, if  
anyone.  Care to explain your magic?  Is there a code in the in- 
addrs?  Perhaps "sl-$FOO" means something in Sprint-speak?

Secondly, does anyone really give a rat's ass who is "SFI" any  
longer?  There are at least 2 fully "SFI" networks who can't route  
half as well as a whole slew of non-SFI networks these days.

If [Cogent|Sprint] [buying|peering|whatever] [from|with] [Cogent| 
Sprint] makes their network better (i.e. lower latency, lower packet  
loss, higher throughput, and, if you care, lower jitter),  I applaud  
them.

Anyone who thinks "X pays Y" is more important than any of the  
metrics above needs to reevaluate their priorities.  (At least from a  
customer / engineering PoV.  I wouldn't suggest $NETWORK's bean  
counters have the same priorities as their network engineers &  
customers. :)

IMHO, of course.

-- 
TTFN,
patrick


> -----Original Message-----
> From: owner-nanog at merit.edu [mailto:owner-nanog at merit.edu] On  
> Behalf Of
> Ed Ray
> Sent: Tuesday, October 31, 2006 12:11 AM
> To: nanog at merit.edu
> Subject: Cogent now peering with Sprint?
>
>
> I never thought Sprint would ever renew its relationship with Sprint:
>
> Tracing the route to portus.netsecdesign.com (66.6.208.6)
>
>    1 sl-bb24-rly-9-0.sprintlink.net (144.232.14.122) 0 msec 0 msec 0
> msec
>    2 sl-st22-ash-6-0.sprintlink.net (144.232.20.189) 0 msec 4 msec 0
> msec
>    3 p15-2.core01.iad01.atlas.cogentco.com (154.54.13.61) [AS 174] 4
> msec 4 msec 0 msec
>    4 v3492-mpd01.iad01.atlas.cogentco.com (154.54.3.222) [AS 174] 16
> msec 80 msec 196 msec
>    5 v3497.mpd01.dca01.atlas.cogentco.com (154.54.5.65) [AS 174] 4  
> msec
> 4 msec 4 msec
>    6 t9-3.mpd01.iah01.atlas.cogentco.com (154.54.2.222) [AS 174] 44  
> msec
> 44 msec 48 msec
>    7 t2-3.mpd01.lax01.atlas.cogentco.com (154.54.3.186) [AS 174] 72  
> msec
> 72 msec 72 msec
>    8 g2-0-0.core01.lax01.atlas.cogentco.com (154.54.2.101) [AS 174] 72
> msec 72 msec 72 msec
>    9 g49.ba01.b002698-1.lax01.atlas.cogentco.com (66.250.12.130) [AS
> 174] 72 msec 72 msec 72 msec
>   10 PAJO-Networks.demarc.cogentco.com (38.112.9.190) [AS 174] 72 msec
> 76 msec 72 msec
>   11 dcap04.pcap.lax01.tierzero.net (216.31.128.14) [AS 11509] 72 msec
> 76 msec 72 msec
>   12 mmic-gw.dcap6.lax.us.tierzero.net (216.31.188.94) [AS 11509] 76
> msec 80 msec 80 msec
>   13 dazedandconfused.netsecdesign.com (66.6.208.4) [AS 11509] 84 msec
> 84 msec 88 msec
>   14 portus.netsecdesign.com (66.6.208.6) [AS 11509] 84 msec 84  
> msec 88
> msec
>
>
> Next I will see pigs flying :)  Wonder how long it will last based on
> Cogent's past behavior as noted here.
>
> Edward Ray
>
> -------------------------------------------------------------
> This mail was scanned by BitDefender
> For more informations please visit http://www.bitdefender.com
>
>
> -------------------------------------------------------------
>




More information about the NANOG mailing list