What’s the Internet? (on 1994's Today Show)

kkleiner writes "In a hilarious video segment from January 24th 1994, The Today Show morning anchors Bryant Gumbel and Katie Couric stumble over the identity and jargon of the internet technology that has come to define the past decade. Gumbel is unclear how you pronounce "@", Katie Couric suggests "about", and no one wants to say "dot" when they read ".com". Confusion with lingo aside, The Today Show cast has to ask a crew member to clarify how the internet works. Do you write to it like mail? Is it just in Universities? Does it require a phone line? This was less than two decades ago, and it's a wonderful reminder of how unprepared the mainstream media was for the innovation that was about to sweep the globe. As the crew member says of the internet, "it's getting bigger and bigger all the time." What a delightful understatement."

Comments

It's a series of tubes

[Toe, The]

Even today, a lot of people are pretty dang confused about what them there internets have on 'em.

Re:Why is this funny?

[elrous0]

1994 was the year I first got internet access myself. And my access consisted of an email address, telnet, and gopher. Almost no one had WWW access then (though Cello and Mosaic were around). It would be another 1995 before I would get a SLIP account to access the web directly (and this was at a major university). So, yeah, I don't really fault them either for not knowing.

1994? I was on the Internet in 1983.

[Animats]

Back in 1983, I was at "jbn@Ford-wdl1.ARPA":

Date: 15-Jul-83 14:03:40-PDT
From: jbn@FORD-WDL1.ARPA
Subject: Outstanding TOPS-20 TCP bug remains in v5.2
To: ICCB@BBN-UNIX.ARPA, Paetzold@DEC-MARLBORO.ARPA, CLynn@BBNA.ARPA, Tappan@BBNA.ARPA<br/>
Cc: MRC@SU-SCORE.ARPA

For some months now, we have observed that the BBN TOPS-20 implementation of TCP does not perform the TCP close handshake properly. This problem has been documented and reported to the appropriate people as shown below.

Crispin at SU-SCORE has just installed a new TOPS-20 monitor (5.2) and this outstanding problem has NOT been fixed.

The effect of this problem is that when a system which correctly performs the handshake is talking to a noncomplying TOPS-20, and the TCP close is initiated from the non-TOPS-20 end, the non-TOPS-20 end will hang in the close and eventually time out. This tends to cause STOR operations in FTP to TOPS-20 sites to fail. It also has the annoying property for us that every time we get mail from a TOPS-20 site, our TCP logs a protocol violation.

Larson at SRI has located the defective code in TOPS-20 as shown below. The messages below are the previous ones relating to this problem.

As we at Ford Aerospace do not run any TOPS-20 systems, we do not directly have this problem, but our users who need to communicate with some of the TOPS-20 sites find this a continual annoyance. Because of the former importance of TOPS-20 in the ARPANET community, there has been
an informal tradition that the TOPS-20 implementation has been considered the ``standard'' with which others were expected to interoperate. For this reason, it appears that considerable effort has been expended in some of the newer implementations (such as the 4.2BSD systems) to interoperate with TOPS-20 despite this problem. (Elaborate FTP strategies regarding data connection establishment are a means of getting around this problem).

Other implementors should be aware of this problem so that such wasted effort can be avoided.

John Nagle
Ford Aerospace and Communications Corp.

This was back when Berkeley's TCP implementation was new and barely working. (Yes, kiddies, TCP/IP did not come from Berkeley.) Ever wonder why FTP uses a different data connection port for each transfer? That's how it started.