Re: Well done Sprint!
Which is just *too* bad, as we were able to glean marketing stats about their network while they had this information ;) [from a long time ago...] Sprint Speed Count % of % of Customers Bandwidth 45000000 15 0.7% 25.8% 12360000 0 0.0% 0.0% 10200000 0 0.0% 0.0% 10000000 0 0.0% 0.0% 8048000 0 0.0% 0.0% 6000000 0 0.0% 0.0% 5000000 6 0.3% 1.1% 4500000 0 0.0% 0.0% 4000000 0 0.0% 0.0% 3088000 0 0.0% 0.0% 3072000 0 0.0% 0.0% 3055000 0 0.0% 0.0% 3000000 0 0.0% 0.0% 2048000 4 0.2% 0.3% 2000000 0 0.0% 0.0% 1544000 1117 55.5% 65.9% 1472000 0 0.0% 0.0% 1408000 2 0.1% 0.1% 1344000 13 0.6% 0.7% 1024000 0 0.0% 0.0% 768000 23 1.1% 0.7% 640000 4 0.2% 0.1% 512000 65 3.2% 1.3% 448000 4 0.2% 0.1% 384000 54 2.7% 0.8% 256000 178 8.8% 1.7% 224000 0 0.0% 0.0% 128000 105 5.2% 0.5% 112000 0 0.0% 0.0% 64000 395 19.6% 1.0% 56000 0 0.0% 0.0% Total 2014 100.0% 100.0% Total subscription 2.62Gb Nice while it lasted ;) -scott
From owner-nanog@merit.edu Wed Nov 12 18:13 EST 1997 X-Authentication-Warning: aegis.noc.telalink.net: rmc owned process doing -bs Date: Wed, 12 Nov 1997 16:58:31 -0600 (CST) From: Bob Collie <rmc@telalink.net> X-Sender: rmc@aegis.noc.telalink.net Reply-To: Bob Collie <bob.collie@telalink.net> To: "Neil J. McRae" <neil@domino.org> cc: nanog@merit.edu Subject: Re: Well done Sprint! X-Mailer: BobMail 1.0 (based on Pine 3.95) MIME-Version: 1.0 Sender: owner-nanog@merit.edu Content-Type> : > TEXT/PLAIN> ; > charset=US-ASCII> Content-Length: 1344
Although it appears that they have dropped off the link speed, etc and interface from the name...
Aaah...
-Bob
On Wed, 12 Nov 1997, Neil J. McRae wrote:
Wee after only about a year Sprint have lost the "/"'s!
traceroute to www.sprint.net (204.117.214.13), 30 hops max, 40 byte packets 1 router (194.70.50.129) 1.397 ms 1.2 ms 3.505 ms 2 gin-nyy-ac1.Teleglobe.net (207.45.199.245) 83.074 ms 82.97 ms 82.858 ms 3 sl-gw16-pen-2-0.sprintlink.net (144.228.164.61) 85.841 ms 85.247 ms 85.274 ms 4 208.28.7.25 (208.28.7.25) 103.272 ms 96.141 ms 88.932 ms 5 sl-bb6-pen-4-0-0.sprintlink.net (144.232.0.77) 87.373 ms 101.192 ms 94.284 ms 6 sl-bb3-pen-4-0-0-155M.sprintlink.net (144.232.0.73) 90.893 ms 86.522 ms 90.032 ms 7 sl-bb2-dc-5-0-0.sprintlink.net (144.232.8.2) 91.378 ms 90.434 ms 92.114 ms 8 sl-s1-dc-0-0.sprintlink.net (144.228.20.121) 92.608 ms 92.737 ms 92.398 ms 9 ftp.sprintlink.net (204.117.214.13) 98.038 ms * 90.365 ms
-- Neil J. McRae. Alive and Kicking. Domino: In the glow of the night neil@DOMINO.ORG NetBSD/sparc: 100% SpF (Solaris protection Factor) Free the daemon in your <A HREF="http://www.NetBSD.ORG/">computer!</A>
-- Bob Collie, VP/Chief Technical Officer, Telalink Corporation mailto:bob.collie@telalink.net
Scott Huddle wrote:
Which is just *too* bad, as we were able to glean marketing stats about their network while they had this information ;)
Wee after only about a year Sprint have lost the "/"'s!
Thank you for making Internet a bit more paranoid place, Scott. Next thing to follow: disabled traceroutes. You know, you can find quite a lot of interesting stuff by looking at the network topology. And that terrible IP RR option! There's no use in promoting corporate paranoia at the expense of engineering cooperation. It is like butcheing the hen which lays the golden eggs. Knowing link capacity was useful (while it lasted) to get the idea of what is more likely to be dropping packets on the floor when customers complained. But, then, i may be getting sentimental. --vadim
'Vadim Antonov writes...' **> **> There's no use in promoting corporate paranoia at the expense of **> engineering cooperation. It is like butcheing the hen which lays **> the golden eggs. Knowing link capacity was useful (while it lasted) **> to get the idea of what is more likely to be dropping packets **> on the floor when customers complained. well, one could get Van Jacobson's pathchar, and learn the true capacity that way. I could care less what *theoretical bandwidth* is available, when customers complain. I want to know what bandwidth *is available*, and pathchar goes a very long way towards that end. link labelling could be arguably silly, if you're basing your determination on a competetitor's labels, you could get some unusual surprises IMHO... -- steve c blair tivoli systems inc sblair@dev.tivoli.com "Why can't we blast them onto someone else's property?"
Has anyone tried pathchar over an asymmetric link? skm On Thu, 13 Nov 1997, Dorian R. Kim wrote:
On Thu, 13 Nov 1997, Steve Blair wrote:
well, one could get Van Jacobson's pathchar, and learn the true capacity that way. I could care less what *theoretical
Pathchar unfortunately is very unreliable at > DS3 links.
-dorian
On Thu, 13 Nov 1997, Scott Huddle wrote:
Which is just *too* bad, as we were able to glean marketing stats about their network while they had this information ;)
I hate to point out the obvious, but all of this info is still available for customer links. Try tracerouteing to cais.com or gmu.edu or netscape and you will still get the link banwidth... This info no longer seems to be present on all of the backbone links. Just guessing, I would speculate this may be due to new naming conventions on the 12000's. Thanks, -chris
participants (6)
-
cll＠athens.servint.com -
Dorian R. Kim -
Scott Huddle -
SK Miller -
Steve Blair -
Vadim Antonov