BTW, core4.wsp.mci.net did not show up in the traceroute due to a bug in the code that we are running. (The bug has been fixed in a later version.) The direct interconnection between MCI and Sprint is in the Chicago area rather than in Denver. The connection speed is OC12 rather than DS3 :-) -- Enke

Date: Wed, 04 Sep 1996 15:23:03 -0400 From: "roy alcala" <roy@mci.net> To: Christian Nielsen <cnielsen@vii.com> CC: nanog@merit.edu

This is a private interconnect between Sprint and MCI, and the serial subnet comes out of address space assigned to MCI (so the inverse mapping is handled by MCI as well). We didn't really know what map the inverse address to in the PTR record, but we wanted it to have *some* mapping, so we just picked an arbitrary hostname.

We'd be happy to change this mapping to some other hostname (or CNAME the inverse address), if the Sprint folks would prefer something different :-)

The other end of the link has a more-descriptive DNS entry:

roy@ns% host -t ptr 89.77.157.206.in-addr.arpa 89.77.157.206.in-addr.arpa PTR core4-hssi5-0.WillowSprings.mci.net

- roy -

------------------------------------------------------------------------- | roy alcala | MCI | | IP Development | 2100 Reston Parkway | | roy@mci.net | Reston, Virginia 22091 | | beep-roy@mci.net (pager) | (703) 715-7425 | | (800) SKY-PAGE PIN 1633689 | (703) 715-7066 FAX | -------------------------------------------------------------------------

...

I guess sometimes they don't like to tell us what kind of link they have.

4 core1-fddi-1.Denver.mci.net (204.70.3.113) 208 ms 29 ms 19 ms 5 somerouter.sprintlink.net (206.157.77.90) 84 ms 90 ms * 6 somerouter.sprintlink.net (206.157.77.90) 86 ms 88 ms 88 ms 7 * sl-chi-6-F0/0.sprintlink.net (144.228.50.6) 168 ms 92 ms

Christian

there are two oc-3 circuits feeding the pop on our side. btw. it was a joke it's a ds-3 interconnect. Jeff Young young@mci.net

Return-Path: owner-nanog@merit.edu Received: from merit.edu (merit.edu [35.1.1.42]) by postoffice.Reston.mci.net (8.7.5/8.7.3) with ESMTP id QAA08055; Wed, 4 Sep 1996 16:08:44 -0400 (EDT) Received: from localhost (daemon@localhost) by merit.edu (8.7.5/merit-2.0) with SMTP id QAA04199; Wed, 4 Sep 1996 16:03:15 -0400 (EDT) Received: by merit.edu (bulk_mailer v1.5); Wed, 4 Sep 1996 16:03:00 -0400 Received: (from daemon@localhost) by merit.edu (8.7.5/merit-2.0) id QAA04174 for nanog-outgoing; Wed, 4 Sep 1996 16:03:00 -0400 (EDT) Received: from aries.ai.net ([208.194.41.4]) by merit.edu (8.7.5/merit-2.0) with SMTP id QAA04164 for <nanog@merit.edu>; Wed, 4 Sep 1996 16:02:40 -0400 (EDT) Received: (from deepak@localhost) by aries.ai.net (8.6.11/8.6.12) id PAA22613; Wed, 4 Sep 1996 15:58:44 -0400 Date: Wed, 4 Sep 1996 15:58:44 -0400 (EDT) From: Deepak Jain <deepak@jain.com> To: Enke Chen <enke@mci.net> cc: roy alcala <roy@mci.net>, Christian Nielsen <cnielsen@vii.com>, nanog@merit.edu, enke@mci.net Subject: Re: :) In-Reply-To: <199609041942.PAA07000@postoffice.Reston.mci.net> Message-ID: <Pine.BSF.3.91.960904155737.22257C-100000@aries.ai.net> MIME-Version: 1.0 Sender: owner-nanog@merit.edu Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 347

...

The direct interconnection between MCI and Sprint is in the Chicago area rather than in Denver. The connection speed is OC12 rather than DS3 :-) ^^^^

Is this optimistic or are there really more than 4 DS3s on both sides feeding the routers? I'm not complaining, just curious.

Deepak Jain American Information Network