Mailing List Archive

:)
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

- - - - - - - - - - - - - - - - -
Re: :) [ In reply to ]
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
>
- - - - - - - - - - - - - - - - -
Re: :) [ In reply to ]
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
> >
- - - - - - - - - - - - - - - - -
Re: :) [ In reply to ]
>
> 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
- - - - - - - - - - - - - - - - -
Re: :) [ In reply to ]
| 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 :-)

Well, I wanted to name our private peerings after the
seven deadly sins, but maybe "somerouter.sprintlink.net"
is a good choice until the names are settled on this side.

That'll happen when the tactical build-out we began a week
and a half ago is completed in a few days.

Meanwhile, 206.157.77.90 is sl-chi-15-H1/0-T3.sprintlink.net (anger)
206.157.77.34 is sl-dc-1-H5/0-T3.sprintlink.net (sloth)
and 206.157.77.66 is sl-stk-1-H9/0-T3.sprintlink.net (pride)

which are subject to move, and the mapping for the
remaining RRs are not nearly as firm...

Of course, I like Enke's suggestion too. :-)

Sean.
- - - - - - - - - - - - - - - - -
Re: :) [ In reply to ]
Yah, but once you use Cook, Metcalfe, Bass, Fleming, Metzger, Denninger,
and Dillon, how do you name the rest?

:)

-scott

> From owner-nanog@merit.edu Wed Sep 4 16:46 EDT 1996
> From: Sean Doran <smd@icp.net>
> To: cnielsen@vii.com, roy@mci.net
> Subject: Re: :)
> Cc: nanog@merit.edu
> Date: Wed, 4 Sep 1996 16:39:06 +0100
> Sender: owner-nanog@merit.edu
> Content-Type> : > text>
> Content-Length: 774
>
> | 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 :-)
>
> Well, I wanted to name our private peerings after the
> seven deadly sins, but maybe "somerouter.sprintlink.net"
> is a good choice until the names are settled on this side.
>
> That'll happen when the tactical build-out we began a week
> and a half ago is completed in a few days.
>
> Meanwhile, 206.157.77.90 is sl-chi-15-H1/0-T3.sprintlink.net (anger)
> 206.157.77.34 is sl-dc-1-H5/0-T3.sprintlink.net (sloth)
> and 206.157.77.66 is sl-stk-1-H9/0-T3.sprintlink.net (pride)
>
> which are subject to move, and the mapping for the
> remaining RRs are not nearly as firm...
>
> Of course, I like Enke's suggestion too. :-)
>
> Sean.
>
- - - - - - - - - - - - - - - - -
Re: :) [ In reply to ]
> Yah, but once you use Cook, Metcalfe, Bass, Fleming, Metzger, Denninger,
> and Dillon, how do you name the rest?
>
> :)

And someone from another provider (than Sprint) will have to use
smd-hatesflaps-h3/0.me.net

Avi

- - - - - - - - - - - - - - - - -
Re: :) [ In reply to ]
At 15:41 9/4/96, Enke Chen wrote:

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

Hmm...

Do the routers at both ends actually think it's OC12?
/John


- - - - - - - - - - - - - - - - -
Re: :) [ In reply to ]
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

- - - - - - - - - - - - - - - - -
Re: :) [ In reply to ]
Sorry, it was a joke (read ":-)") in replying to the original
question "what kind link it is". Doing OC12 between routers
is still a dream today ...

-- Enke

> Date: Wed, 4 Sep 1996 18:50:36 -0400
> From: John Curran <jcurran@bbnplanet.com>
> To: Enke Chen <enke@mci.net>
> CC: roy alcala <roy@mci.net>, nanog@merit.edu

> At 15:41 9/4/96, Enke Chen wrote:
>
> >The direct interconnection between MCI and Sprint is in
> >the Chicago area rather than in Denver. The connection
> >speed is OC12 rather than DS3 :-)
>
> Hmm...
>
> Do the routers at both ends actually think it's OC12?
> /John
>
>
- - - - - - - - - - - - - - - - -
Re: :) [ In reply to ]
>
> Sorry, it was a joke (read ":-)") in replying to the original
> question "what kind link it is". Doing OC12 between routers
> is still a dream today ...
>
> -- Enke
>
> > Hmm...
> >
> > Do the routers at both ends actually think it's OC12?
> > /John
> >

Depends on your routers now doesn't it?
I don't think that commodity routers are
there yet, but products exist that claim
(and charge) for OC12.

--
--bill
- - - - - - - - - - - - - - - - -
Re: :) [ In reply to ]
On Thu, 5 Sep 1996, Bill Manning wrote:

> > > Do the routers at both ends actually think it's OC12?
>
> Depends on your routers now doesn't it?
> I don't think that commodity routers are
> there yet, but products exist that claim
> (and charge) for OC12.
>
Yes, there are products that claim to do OC-12, but they do not work. Then
there are router that can do OC-12, but the the software needs a LOT of
work (a few years).

Nathan Stratton CEO, NetRail, Inc. Tracking the future today!
---------------------------------------------------------------------------
Phone (703)524-4800 NetRail, Inc.
Fax (703)534-5033 2007 N. 15 St. Suite 5
Email sales@netrail.net Arlington, Va. 22201
WWW http://www.netrail.net/ Access: (703) 524-4802 guest
---------------------------------------------------------------------------
"Therefore do not worry about tomorrow, for tomorrow will worry about
itself. Each day has enough trouble of its own." Matthew 6:34


- - - - - - - - - - - - - - - - -
Re: :) [ In reply to ]
At 9:32 9/5/96, Enke Chen wrote:
>Sorry, it was a joke (read ":-)") in replying to the original
>question "what kind link it is". Doing OC12 between routers
>is still a dream today ...

Mea culpe... I mistook it for "marketing announcement"
(i.e. tied to reality only in theory... ;-)

/John


- - - - - - - - - - - - - - - - -
Re: :) [ In reply to ]
John Curran writes in reply to Enke Chen:
| >Sorry, it was a joke (read ":-)") in replying to the original
| >question "what kind link it is". Doing OC12 between routers
| >is still a dream today ...
|
| Mea culpe... I mistook it for "marketing announcement"
| (i.e. tied to reality only in theory... ;-)

Oh, tish and tosh. Think of it as an opportunity to announce
the OC24c connections between Sprintlink and BBN Planet.

Sean.
- - - - - - - - - - - - - - - - -
Re: :) [ In reply to ]
> Date: Thu, 5 Sep 1996 14:46:35 -0400
> From: John Curran <jcurran@bbnplanet.com>
> To: Enke Chen <enke@mci.net>
> CC: nanog@merit.edu

> At 9:32 9/5/96, Enke Chen wrote:
> >Sorry, it was a joke (read ":-)") in replying to the original
> >question "what kind link it is". Doing OC12 between routers
> >is still a dream today ...
>
> Mea culpe... I mistook it for "marketing announcement"
> (i.e. tied to reality only in theory... ;-)
>
> /John
>
>

Well, there are OC12 backbones that are being built today.
It will not be long before we see OC12 between providers.
Sometimes next year?

-- Enke




- - - - - - - - - - - - - - - - -
Re: :) [ In reply to ]
In message <96Sep5.153935+0100_edt.20623+120@chops.icp.net>, Sean Doran writes:
> John Curran writes in reply to Enke Chen:
> | >Sorry, it was a joke (read ":-)") in replying to the original
> | >question "what kind link it is". Doing OC12 between routers
> | >is still a dream today ...
> |
> | Mea culpe... I mistook it for "marketing announcement"
> | (i.e. tied to reality only in theory... ;-)
>
> Oh, tish and tosh. Think of it as an opportunity to announce
> the OC24c connections between Sprintlink and BBN Planet.
>
> Sean.


Or someone can announce OC192 at a NAP. Maybe it'll even make a trade
rag. ;-)

Curtis
- - - - - - - - - - - - - - - - -