North American Network Operators Group|
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical
RE: Cogent now peering with Sprint?
> 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? Yea, but most of xfer-nets in this case appear to be assigned by Cogent (then again, how does that make any difference for special buy|peer cases): 2 sl-st21-la-13-0.sprintlink.net (18.104.22.168) 4 msec 4 msec 4 msec 3 p12-3.core01.lax05.atlas.cogentco.com (22.214.171.124) [AS 174] 4 msec 4 msec 4 msec 11 sprint.iad01.atlas.cogentco.com (126.96.36.199) 12.032 ms 12.061 ms 12.103 ms 9 sprint.dfw03.atlas.cogentco.com (188.8.131.52) 21.964 ms 21.897 ms 21.756 ms Etc.. And comm tags from Sprint side look similar to other SFI's: 1239 174 184.108.40.206 from 220.127.116.11 (18.104.22.168) Origin IGP, metric 4294967294, localpref 100, valid, external Community: 1239:321 1239:1000 1239:1011 1239 209 22.214.171.124 from 126.96.36.199 (188.8.131.52) Origin IGP, metric 4294967294, localpref 100, valid, external Community: 1239:321 1239:1000 1239:1011 > > 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. Indeed, at the end of the day, it really doesn't matter these days :) james