[11481] in Commercialization & Privatization of the Internet

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

Re: The whole CIX concept is flawed

daemon@ATHENA.MIT.EDU (Karl Denninger)
Mon Apr 4 05:17:04 1994

From: karl@mcs.com (Karl Denninger)
To: jlw@cs.columbia.edu (James Waldrop)
Date: Mon, 4 Apr 1994 03:25:34 -0500 (CDT)
Cc: com-priv@psi.com
In-Reply-To: <199404040343.XAA28734@shekel.cs.columbia.edu> from "James Waldrop" at Apr 3, 94 11:43:05 pm

> 
> 
> To engage briefly in another thread, I have a question.  For the
> last couple weeks I've noticed a degradation in the connection
> between where I live and where I do most of my computing (call me
> an ur-telecommuter).  It seems that the ANS/CIX interconnecting
> point has been bogged down.
> 
> Now, I don't have access to enough networks to confirm this, but
> I've noticed that connections between PSI and Sprintlink are
> running at about a 2 or 3% packet loss -- pretty reasonable.
> Connections between PSI/Sprintlink (CIX) and ANS seem to be
> imposing an additional 10% packet loss on top of this.
> 
> Anyone out there able to confirm and/or explain this?
> 
> Is there a mailing list that deals with day to day network performance?
> 
> James Waldrop
> jlw@cs.columbia.edu
> sulam@well.sf.ca.us
> 

Packets between SprintLink and ANS normally go through FIX-East, at least
for sites over here. I don't know what the preferred path is from that part
of the world.

An example:

job control requires tty
traceroute to interaccess.com (198.80.0.2), 30 hops max, 40 byte packets
 1  MCSNet-AGS1 (192.160.127.110)  4 ms  2 ms  2 ms
 2  Inet-T1.MCS.NET (199.3.35.99)  17 ms  2 ms  2 ms
 3  sl-chi-2-S14-T1.sprintlink.net (144.228.133.1)  6 ms  5 ms  5 ms
 4  sl-chi-3-F0.sprintlink.net (144.228.129.3)  7 ms  5 ms  5 ms
 5  sl-dc-1-S1-T1.sprintlink.net (144.228.0.162)  27 ms  23 ms  24 ms
 6  icm-dc-1-F0.icp.net (144.228.1.43)  46 ms  22 ms  22 ms
 7  icm-fix-e-H2/0.icp.net (192.157.65.122)  68 ms  92 ms  100 ms
 8  mf-0.enss145.t3.ans.net (192.203.229.246)  22 ms  22 ms  22 ms
 9  t3-1.Washington-DC-cnss58.t3.ans.net (140.222.58.2)  22 ms  25 ms  24 ms
10  mf-0.Washington-DC-cnss56.t3.ans.net (140.222.56.222)  23 ms  23 ms  23 ms
11  t3-0.New-York-cnss32.t3.ans.net (140.222.32.1)  28 ms  28 ms  28 ms
12  t3-1.Cleveland-cnss40.t3.ans.net (140.222.40.2)  41 ms  40 ms  51 ms
13  t3-2.Chicago-cnss24.t3.ans.net (140.222.24.3)  47 ms  50 ms  47 ms
14  mf-0.Chicago-cnss27.t3.ans.net (140.222.24.195)  48 ms  47 ms  47 ms
15  Chicago-cnss28.t3.ans.net (192.103.62.6)  49 ms  49 ms  48 ms
16  enss169.t3.ans.net (192.103.62.54)  51 ms  52 ms  58 ms
17  home.interaccess.com (198.80.0.2)  53 ms  51 ms  52 ms

Interaccess is an ANS customer.  Transit is occurring at icm-fix-e to
ANS ENSS145.

--
--
Karl Denninger (karl@MCS.Net)| MCSNet - Full Internet Connectivity (shell,
Modem: [+1 312 248-0900]     | PPP, SLIP, leased) in Chicago and 'burbs.
Voice/FAX: [+1 312 248-8649] | Email "info@mcs.com".  MCSNet is a CIX member.
Fan Friendly Internet Here   | WWW: http://www.mcs.net, gopher: gopher.mcs.net

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