North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

RE: Peering point speed publicly available?

  • From: Cody Lerum
  • Date: Thu Jul 01 22:15:03 2004

Not to mention I have run across a few providers who skew their dns records to make their network look bigger/faster.

Like I said it might get you a vague idea, but I wouldn’t place money on it. Just like GE might really be 10GE and FE might only be limited to 10Mbps.

How often do you think IP's get moved around, and the DNS doesn't?

-C

-----Original Message-----
From: Daniel Golding [mailto:[email protected]] 
Sent: Thursday, July 01, 2004 8:02 PM
To: Cody Lerum; [email protected]; [email protected]
Cc: [email protected]
Subject: Re: Peering point speed publicly available?


Sometimes it can give a hint. However, if the ISPs are following the
³interface name² convention, you¹ll get something like P3-1-2, which just
tells you its Packet Over SONET. That can mean anything from OC-3 to OC-192.
³ge² could mean 10 gige :)

The "2488M" from glbx is nice, but not too common.

It would be so nice if this were standardized between all providers. But
naming conventions are really political - they sometimes provoke huge fights
even within providers.

-- 
Daniel Golding
Network and Telecommunications Strategies
Burton Group


On 7/1/04 8:25 PM, "Cody Lerum" <[email protected]> wrote:

> DNS can sometimes give you a hint
>  
> [my nets snipped]
>  4 t3-1-2-0.ar2.SEA1.gblx.net (64.211.206.113)  20.436 ms  18.309 ms  17.605
> ms   <------------DS3
>  5  so1-0-0-2488M.ar4.SEA1.gblx.net (67.17.71.210)  17.607 ms  16.982 ms
> 16.971 ms  <-----OC-48
>  6  p3-3.IR1.Seattle-WA.us.xo.net (206.111.7.5)  17.864 ms  19.491 ms  17.181
> ms
>  7  p5-1-0-3.RAR1.Seattle-WA.us.xo.net (65.106.0.197)  17.723 ms  17.632 ms
> 19.045 ms
>  8  65.106.0.50 (65.106.0.50)  38.133 ms  39.197 ms  49.961 ms     MPLS
> Label=101549 CoS=0 TTL=1 S=1
>  9  p0-0-0d0.RAR1.SanJose-CA.us.xo.net (65.106.1.61)  37.669 ms  38.572 ms
> 36.517 ms
> 10  p7-0.DCR1.DC-SanJose-CA.us.xo.net (65.106.2.146)  37.830 ms  36.524 ms
> 37.743 ms
> 11  ge1-1.CDR2.DC-SanJose-CA.us.xo.net (209.220.168.10)  38.428 ms  38.050 ms
> 37.179 ms <-----Gig Ethernet
> 12  205.158.6.100.ptr.us.xo.net (205.158.6.100)  40.179 ms  39.784 ms  39.444
> ms
> 13  x218.cd9e6c.sj.concentric.net (205.158.108.218)  39.188 ms  39.723 ms
> 39.895 ms
>  
> However MPLS hidden hops may hide internal paths, and any connection may be
> limited to slower than its line rate, and dns entries may be old....
>  
> It's not publicly available at one source that I'm aware of, and if there is
> they don't have my info.
>  
> -C 
> 
> From: [email protected]it.edu [mailto:[email protected]] On Behalf Of Erik
> Amundson
> Sent: Thursday, July 01, 2004 6:10 PM
> To: [email protected]
> Cc: [email protected]
> Subject: Peering point speed publicly available?
> 
> NANOG,
>  
> I have a question regarding information on my ISP¹s peering relationships.
> Are the speeds of some or all peering relationships public knowledge, and if
> so, where can I find this?  By speed, I mean bandwidth (DS3, OC3, 100Mbps,
> 1Gbps, etc.).  I am trying to transfer large stuff from my AS, through my ISP,
> through another ISP, to another AS, and I¹m wondering how fast the peering
> point is between the ISPs.  I¹m working with my provider to get this
> information as we speak, but I¹m wondering if it¹s available publicly
> anywhere.  If it were, this could be one way to evaluate providers in the
> future, I guessÐ
>  
> Erik Amundson
> A+, N+, CCNA, CCNP
> IT and Network Manager
> Open Access Technology Int'l, Inc.
> Phone (763) 201-2005
> Fax (763) 553-2813
> mailto:[email protected]
>  
>