From: schily@schily.net (Joerg Schilling)
Subject: [TUHS] TUHS Digest, Vol 14, Issue 63
Date: Tue, 17 Jan 2017 15:21:54 +0100 [thread overview]
Message-ID: <587e2882.ucdKFsgP38LOZ3N7%schily@schily.net> (raw)
In-Reply-To: <201701161600.v0GG00XA080461@tahoe.cs.Dartmouth.EDU>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 909 bytes --]
Doug McIlroy <doug at cs.dartmouth.edu> wrote:
> The highest levels of AT&T were happy to carry digital data, but
> did not see digital as significant business. Even though digital T1
> was the backbone of long-distance transmission, it was IBM, not
> AT&T, that offered direct digital interfaces to T1 in the 60s.
Was T1 a "digital" line interface, or was this rather a 24x3.1 kHz channel?
How was the 64 ??? Kbit/s interface to the first IMPs implemented?
Wasn't it AT&T that provided the lines for the first IMPs?
I was always wondering how they could provide such a "high speed" line in the
1960s.
I hope somebody knows this....
Jörg
--
EMail:joerg at schily.net (home) Jörg Schilling D-13353 Berlin
joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/
next prev parent reply other threads:[~2017-01-17 14:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1484532001.2693.tuhs@minnie.tuhs.org>
2017-01-16 16:00 ` Doug McIlroy
2017-01-16 16:22 ` Marc Rochkind
2017-01-16 16:44 ` Larry McVoy
2017-01-16 16:52 ` Marc Rochkind
2017-01-16 19:17 ` Steve Johnson
2017-01-16 19:21 ` Larry McVoy
2017-01-16 19:57 ` Ken Thompson
2017-01-16 23:41 ` Tim Bradshaw
2017-01-16 23:45 ` Brantley Coile
2017-01-17 4:07 ` Jason Stevens
2017-01-17 5:22 ` William Corcoran
2017-01-17 11:43 ` Jason Stevens
2017-01-17 14:27 ` Joerg Schilling
2017-01-17 14:21 ` Joerg Schilling [this message]
2017-01-16 19:46 Noel Chiappa
2017-01-17 0:30 ` Brad Spencer
2017-01-17 15:32 Noel Chiappa
2017-01-18 14:29 ` Paul Ruizendaal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=587e2882.ucdKFsgP38LOZ3N7%schily@schily.net \
--to=schily@schily.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).