[37527] in North American Network Operators' Group
2 Wire T1 - HDLC
daemon@ATHENA.MIT.EDU (wb8foz@nrk.com)
Tue May 15 08:14:37 2001
Message-Id: <200105151210.IAA03914@boudicca.tux.org>
To: nanog@merit.edu (nanog list)
Date: Tue, 15 May 2001 08:10:29 -0400 (EDT)
Reply-To: wb8foz@nrk.com
From: wb8foz@nrk.com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Errors-To: owner-nanog-outgoing@merit.edu
Of course, this whole flame-fest is pointless.
T-1 can't be 2-wire.
T-1 is a facility. Circa 1962, it *carries* DS-1 format bits,
over 2 pairs, with repeaters every 6Kft (except the first is 3Kft
from the CO..). {Gee, the exact spacing of 88mH load coils....must
be coincidence..}
You can get those DS-1 bits (that's what really you
want...) delivered over: T-1, HDSL, as part of something bigger,
<RFC-1149>, whatever.
And 95% of the time, you likely don't care....as long as the bits
arrive. Just like the guy downstream does not care if you have
a cisco 9000 or a HAL 9000, as long as his service stays up.
Can we go back to worrying about things that SHOULD scare all
of us, such as MPAA, COPA, RIAA, and CALEA; rather than worrying
about the ghostly remains of RabbitNet?
--
A host is a host from coast to coast.................wb8foz@nrk.com
& no one will talk to a host that's close........[v].(301) 56-LINUX
Unless the host (that isn't close).........................pob 1433
is busy, hung or dead....................................20915-1433
