Robert Braden | 12 May 2012 20:54
Picon
Favicon

The UCLA 360/91 on the ARPAnet/Internet

The side discussion of the two IBM 360/91s at UCLA would
seem to have little to do with Internet history. However, I
want to point out that the "other" 360/91 at UCLA was in
fact a relatively early (1971) ARPAnet host, and it became
an Internet host after the Big Switch in Jan 1983. It supported
Telnet, FTP (a rich version, suited to the baroque IBM file
system), and SMTP.  This machine was distinguished by being
one of two 91s with 4M bytes of main memory (the other
belonged to a secret facility in the DC area). Its TCP/IP
implementation was one of the 5 experimental
implementations of TCP[/IP] put together by members of
the Internet* working group . I wrote the code in the 1977-
1983 time frame. The initial code V 2 of TCP. When
IP was split off  (V 2.5, as I recall), I applied a virtual scalpel
to the TCP code to split off the IP layer.

  I left UCLA for ISI in 1986 before I got around to adding Van's
  congestion control to TCP, sadly.

One other historic note: during 1981-1983 I maintained
  the /91 TCP/IP code remotely  over the ARPAnet from UCL
  in London. Kirstein had a TIP on the ARPAnet,
Remote debugging over the ARPAnet was certainly not new,
but I could probably can claim a distance record at the time ;-)

Bob Braden

*Perhaps called the Catenet working group at the time?

(Continue reading)

Dave Crocker | 12 May 2012 21:49

Re: The UCLA 360/91 on the ARPAnet/Internet

On 5/12/2012 11:54 AM, Robert Braden wrote:
 > The side discussion of the two IBM 360/91s at UCLA would
 > seem to have little to do with Internet history. However, I
 > want to point out that the "other" 360/91 at UCLA was in
 > fact a relatively early (1971) ARPAnet host, and it became
 > an Internet host after the Big Switch in Jan 1983. It supported
 > Telnet, FTP (a rich version, suited to the baroque IBM file
 > system), and SMTP.  This machine was distinguished by being

It also supported a remote job entry protocol.

My job was documentation for the CS arpanet project and local 
timesharing (sigma executive) o/s.

We would do our text creation on the SRI NLS system, ship it down to ISI 
thru FTP and then RJE it to Bob's /91 for output, because it had a 
high-speed upper/lower case printer that could produce 8.5x11" sheets...

d/
--
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

Bernie Cosell | 12 May 2012 23:19

Re: The UCLA 360/91 on the ARPAnet/Internet

On 12 May 2012 at 11:54, Robert Braden wrote:

> The side discussion of the two IBM 360/91s at UCLA would
> seem to have little to do with Internet history. ...

all this talk of UCLAs connections to the ARPAnet got me wondering:, am I 
misremembering?   Didn't UCLA have a Sigma 7 that connected to the 
ARPAnet [I vaguely recall Mike Wingfield did the interface and I had to 
work with him to debug something about it].

  /bernie\

--

-- 
Bernie Cosell                     Fantasy Farm Fibers
mailto:bernie <at> fantasyfarm.com     Pearisburg, VA
    -->  Too many people, too few sheep  <--       

Vint Cerf | 12 May 2012 23:42
Picon
Favicon

Re: The UCLA 360/91 on the ARPAnet/Internet

yes, that was the first machine connected at UCLA - Mike W did the
hardware. Charley Kline and others had a hand in the i/o software. I
wrote a modified version of the Sigma-7 operating system to run
measurements and to generate artificial traffic into the network. Bob
Kahn and Dave Walden paid visits to UCLA where we did particular
experiments. We used this system to test the predictions of Len
Kleinrock and his students about the performance of the ARPANET based
on queueing models. Steve Crocker led the group that developed the
Sigma-7 Experiment Timesharing system. We called it SEX and the most
popular document among the geeks was the SEX Users Manual....

v

On Sat, May 12, 2012 at 5:19 PM, Bernie Cosell <bernie <at> fantasyfarm.com> wrote:
> On 12 May 2012 at 11:54, Robert Braden wrote:
>
>> The side discussion of the two IBM 360/91s at UCLA would
>> seem to have little to do with Internet history. ...
>
> all this talk of UCLAs connections to the ARPAnet got me wondering:, am I
> misremembering?   Didn't UCLA have a Sigma 7 that connected to the
> ARPAnet [I vaguely recall Mike Wingfield did the interface and I had to
> work with him to debug something about it].
>
>  /bernie\
>
> --
> Bernie Cosell                     Fantasy Farm Fibers
> mailto:bernie <at> fantasyfarm.com     Pearisburg, VA
>    -->  Too many people, too few sheep  <--
(Continue reading)

Dave Crocker | 13 May 2012 02:58

Re: The UCLA 360/91 on the ARPAnet/Internet


On 5/12/2012 2:42 PM, Vint Cerf wrote:
> Steve Crocker led the group that developed the
> Sigma-7 Experiment Timesharing system. We called it SEX and the most
> popular document among the geeks was the SEX Users Manual....

Cycling back to the topic of Arpa's wanting to share resources, when we 
tried to get funding for 32K more memory for the system, Arpa instead 
said we should get a PDP-11 and use one of the terminal concentrator 
systems (ANTS from Illinois or ELF from Santa Barbara) and do remote 
computing.

The concentrator systems weren't up to snuff, but Unix was coming 
available on PDP-11s and we got that.

So Arpa took away our Sex and gave us Unix.

Our original superuser password was, of course, eunuchs.

d/
--

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

John Day | 13 May 2012 03:26
Picon

Re: The UCLA 360/91 on the ARPAnet/Internet

Right, we put the first Unix up on the 'Net on a PDP-11/45 in the 
summer of 75.  Its IPC was terrible (and still is).  We shoehorned 
NCP into the kernel and Telnet as an application in the first 
version.  Then went back to fix the IPC.

John

At 17:58 -0700 2012/05/12, Dave Crocker wrote:
>On 5/12/2012 2:42 PM, Vint Cerf wrote:
>>Steve Crocker led the group that developed the
>>Sigma-7 Experiment Timesharing system. We called it SEX and the most
>>popular document among the geeks was the SEX Users Manual....
>
>
>Cycling back to the topic of Arpa's wanting to share resources, when 
>we tried to get funding for 32K more memory for the system, Arpa 
>instead said we should get a PDP-11 and use one of the terminal 
>concentrator systems (ANTS from Illinois or ELF from Santa Barbara) 
>and do remote computing.
>
>The concentrator systems weren't up to snuff, but Unix was coming 
>available on PDP-11s and we got that.
>
>So Arpa took away our Sex and gave us Unix.
>
>Our original superuser password was, of course, eunuchs.
>
>d/
>--
>  Dave Crocker
(Continue reading)

Sytel | 13 May 2012 03:38
Picon
Favicon

Re: The UCLA 360/91 on the ARPAnet/Internet

In all seriousness, this sounds very informative-- is this manual available 
somewhere? Would love to know more about the "sit down, log in and do stuff" 
specifics of it, especially that original UCLA Sigma 7...

----- Original Message ----- 
From: "Vint Cerf" <vint <at> google.com>
To: "Bernie Cosell" <bernie <at> fantasyfarm.com>
Cc: <internet-history <at> postel.org>
Sent: Saturday, May 12, 2012 2:42 PM
Subject: Re: [ih] The UCLA 360/91 on the ARPAnet/Internet

> yes, that was the first machine connected at UCLA - Mike W did the
> hardware. Charley Kline and others had a hand in the i/o software. I
> wrote a modified version of the Sigma-7 operating system to run
> measurements and to generate artificial traffic into the network. Bob
> Kahn and Dave Walden paid visits to UCLA where we did particular
> experiments. We used this system to test the predictions of Len
> Kleinrock and his students about the performance of the ARPANET based
> on queueing models. Steve Crocker led the group that developed the
> Sigma-7 Experiment Timesharing system. We called it SEX and the most
> popular document among the geeks was the SEX Users Manual....
>
> v
>
>
> On Sat, May 12, 2012 at 5:19 PM, Bernie Cosell <bernie <at> fantasyfarm.com> 
> wrote:
>> On 12 May 2012 at 11:54, Robert Braden wrote:
>>
>>> The side discussion of the two IBM 360/91s at UCLA would
(Continue reading)

dave.walden.family | 13 May 2012 05:28
Picon

Re: The UCLA 360/91 on the ARPAnet/Internet

Go to the UCLA Internet Archive web site.  It has scans of the log book from the Sigma 7 in those earliest days. 
Various of the people mention in this discussion are noted in the log book.  Dr. Brad Fidler is the staff
archivist if you want a contact there.  The archive is apparently in Boelter Hall where the IMP and Sigma 7
were.   I think the IMP is still there.  

Sent from my iPad

On May 12, 2012, at 9:38 PM, "Sytel" <sytel <at> shaw.ca> wrote:

> In all seriousness, this sounds very informative-- is this manual available somewhere? Would love to
know more about the "sit down, log in and do stuff" specifics of it, especially that original UCLA Sigma 7...
> 
> ----- Original Message ----- From: "Vint Cerf" <vint <at> google.com>
> To: "Bernie Cosell" <bernie <at> fantasyfarm.com>
> Cc: <internet-history <at> postel.org>
> Sent: Saturday, May 12, 2012 2:42 PM
> Subject: Re: [ih] The UCLA 360/91 on the ARPAnet/Internet
> 
> 
>> yes, that was the first machine connected at UCLA - Mike W did the
>> hardware. Charley Kline and others had a hand in the i/o software. I
>> wrote a modified version of the Sigma-7 operating system to run
>> measurements and to generate artificial traffic into the network. Bob
>> Kahn and Dave Walden paid visits to UCLA where we did particular
>> experiments. We used this system to test the predictions of Len
>> Kleinrock and his students about the performance of the ARPANET based
>> on queueing models. Steve Crocker led the group that developed the
>> Sigma-7 Experiment Timesharing system. We called it SEX and the most
>> popular document among the geeks was the SEX Users Manual....
>> 
(Continue reading)

Dave Crocker | 13 May 2012 16:40

Re: The UCLA 360/91 on the ARPAnet/Internet


On 5/12/2012 8:28 PM, dave.walden.family <at> gmail.com wrote:
> Go to the UCLA Internet Archive web site.  It has scans of the log book from the Sigma 7 in those earliest days. 
Various of the people mention in this discussion are noted in the log book.  Dr. Brad Fidler is the staff
archivist if you want a contact there.  The archive is apparently in Boelter Hall where the IMP and Sigma 7
were.   I think the IMP is still there.

Developing and maintaining the SEX (user) Manual was one of my jobs at 
the UCLA Arpanet project.  It's the only document that has co-authorship 
with Vint, Jon, Charlie, Steve, and me (and others).

Alas, I don't have a snapshot of it.

As I recall, it wasn't very interesting reading.  Given how little 
computer science I knew at the time, writing for it kept me up at night, 
but I suspect reading it now would have the opposite effect for most folk.

d/
--

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

dave.walden.family | 13 May 2012 12:33
Picon

Re: The UCLA 360/91 on the ARPAnet/Internet

Regarding a second ARPANET host at UCLA, and other places, e.g. MIT: my memory is that a lot of ARPANET
traffic was intra IMP site.  

Also, I never thought before where the word "host" came from -- perhaps from hosting some of those "shared
resources" that were supposed to be used cross network.

On May 12, 2012, at 2:54 PM, Robert Braden <braden <at> ISI.EDU> wrote:

> The side discussion of the two IBM 360/91s at UCLA would
> seem to have little to do with Internet history. However, I
> want to point out that the "other" 360/91 at UCLA was in
> fact a relatively early (1971) ARPAnet host, 

Noel Chiappa | 13 May 2012 15:58
Picon

Re: The UCLA 360/91 on the ARPAnet/Internet

    > From: Vint Cerf <vint <at> google.com>

    > I don't think we had a name for the group of implementors sponsored by
    > ARPA.

I think at the time we informally called it the 'Internet working group' - I
didn't realize at the time that that was a duplication of the name of the
earlier international high-level design effort! (No doubt this will confuse
unwary historians in the future! :-) I've seen it referred to in IEN's that
way too (e.g. IEN-3, IEN-191).

Just for additional confusion, at that point we referred to the Internet
Protocol as "IN" (see IEN-53 for an example of this), not "IP".

    > Dave Clark did his IBM PC version probably around 1980?

Dave didn't do the PC version - that was John Romkey and Dave Bridgham. Dave
had worked on the Multics TCP to start with (I'm not sure who wrote most of
it - see:

  http://mailman.postel.org/pipermail/internet-history/2006-January/000513.html

for more - I think Michael Greenwald took over maintaining on it after Dave,
and then Charlie Hornig); he then did one in BCPL for Tripos while on
sabatical at Cambridge, and after he got back, and MIT got the Xerox
Alto/Dover donation, he moved that one to the Alto.

Some of the ideas he did on his "user TELNET centric TCP" were used in a TCP
we did for PDP-11 Unix (by Larry Allen - Liza Martin did a more classical TCP
for the same machine - both used the same kernel support, where only the
(Continue reading)

Dave Walden | 13 May 2012 16:24
Picon

Re: The UCLA 360/91 on the ARPAnet/Internet

I think we called it the Network Working Group during the ARPANET 
pre-Internet days -- the group writing RFCs to each other.  (Or am I 
talking about some different topic than Noel is talking about.)

At 09:58 AM 5/13/2012, Noel Chiappa wrote:
>I think at the time we informally called it the 'Internet working group' -

--
home address: 12 Linden Rd., E. Sandwich, MA 02537
home ph=508-888-7655; cell ph = 503-757-3137
email address:  dave <at> walden-family.com; website: 
<http://www.walden-family.com/bbn/>http://www.walden-family.com/bbn/  

Vint Cerf | 13 May 2012 17:09
Picon
Favicon

Re: The UCLA 360/91 on the ARPAnet/Internet

The network working group did nco, telnet, FTP, eventually smtp, although the latter might have been post-1982 and for Internet and not Arpanet (?).

On May 13, 2012 10:32 AM, "Dave Walden" <dave.walden.family <at> gmail.com> wrote:
I think we called it the Network Working Group during the ARPANET pre-Internet days -- the group writing RFCs to each other.  (Or am I talking about some different topic than Noel is talking about.)

At 09:58 AM 5/13/2012, Noel Chiappa wrote:
I think at the time we informally called it the 'Internet working group' -


--
home address: 12 Linden Rd., E. Sandwich, MA 02537
home ph=508-888-7655; cell ph = 503-757-3137
email address:  dave <at> walden-family.com; website: <http://www.walden-family.com/bbn/>http://www.walden-family.com/bbn/  
Dave Crocker | 14 May 2012 03:01

Re: The UCLA 360/91 on the ARPAnet/Internet


On 5/13/2012 8:09 AM, Vint Cerf wrote:
> The network working group did nco, telnet, FTP, eventually smtp,
> although the latter might have been post-1982 and for Internet and not
> Arpanet (?).

Right.  SMTP was done in 1982, for the Internet Mail.(*)  Postel held 
some meetings that various folk attended.

At the same time, for RFC822, I only did mailing list discussion with 
folk.  But then, 822 was a relatively minor upgrade to RFC 733 from 1977 
(which was for Arpanet mail).

> On 5/13/2012 9:39 AM, Noel Chiappa wrote:
>> I thought SMTP came out of MSGROUP, or perhaps some hybrid of MSGGROUP and
>> the old NWG? (I vaguely recall chit-chat from other hackers in the MIT AI Lab
>> about it.) It _definitely_ was not from the TCP/Ip group(s).

Well, Jon created and ran the effort.  I don't remember what mailing 
list he used for 821 (nor which I used for 822).  Might have been 
msggroup, I suppose.  For 822 it might have been hdr-people...

>> SMTP was always intended for use with both NCP and TCP, and saw most of its
>> early use under NCP.

Mumble.  SMTP doesn't care about the underlying transport details, but 
its motivation was definitely the move to the Internet.

d/

(*) Beside upgrading to domain names, the main benefit of having SMTP 
over the FTP-based mail commands we'd been using for 10 years was 
allowing multiple addressees per transmitted message.  This has become 
ironic as current mail-sending softrware tends towards one-addressee per 
message, for management control -- different message identifiers and 
logging for different addressees and content tailoring.  sigh.

--

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

Michael Greenwald | 13 May 2012 18:41
Favicon

Re: The UCLA 360/91 on the ARPAnet/Internet

On 5/13/12 6:58 AM, Noel Chiappa wrote:
>      >  From: Vint Cerf<vint <at> google.com>
>
>      >  I don't think we had a name for the group of implementors sponsored by
>      >  ARPA.
>
> I think at the time we informally called it the 'Internet working group' - I
> didn't realize at the time that that was a duplication of the name of the
> earlier international high-level design effort! (No doubt this will confuse
> unwary historians in the future! :-) I've seen it referred to in IEN's that
> way too (e.g. IEN-3, IEN-191).
>
> Just for additional confusion, at that point we referred to the Internet
> Protocol as "IN" (see IEN-53 for an example of this), not "IP".
>
>
>      >  Dave Clark did his IBM PC version probably around 1980?
>
> Dave didn't do the PC version - that was John Romkey and Dave Bridgham. Dave
> had worked on the Multics TCP to start with (I'm not sure who wrote most of
Just to clarify in the wealth of 'Dave's: Dave 
Clark worked on Multics IP/TCP and not Dave 
Bridgham (as far as I remember).
> it - see:
>
>    http://mailman.postel.org/pipermail/internet-history/2006-January/000513.html
>
> for more - I think Michael Greenwald took over maintaining on it after Dave,
> and then Charlie Hornig);
Yes.  We actually split the IP stack; I'm not 100% 
sure of my memory (I wish I had my multics email), 
but I think that by 1979-80 Charlie was handling 
TCP and I was handling everything else (IP, the 
Internet Imp daemon), GGP (Multics actually ran 
experimentally as a gateway), TFTP, UDP, the mail 
protocol (I think I wrote an MTP implementation 
before the SMTP spec was written?  Although, I 
think SMTP was a set of minor modifications to 
MTP), ICMP when it turned up, TELNET (I think I 
needed to rewrite it to handle some new option 
negotiation, and interact with echo negotiation to 
make emacs work) -- I'm not sure of the dates of 
any of those).  After Charlie left we did a few 
rewrites of TCP and IP to reduce the number of 
context switches, to deal with congestion, and 
then a rewrite to have the IP stack run in an 
inner ring.  Dave Vinograd at Honeywell CISL hired 
me to come over and turn it into a product.  I 
worked on this transfer for a couple of months, I 
am pretty sure that J Spencer Love took over from 
me there, and did all of the hard work.

I'm not sure if this level of detail is useful to 
anyone, or just noise.
> he then did one in BCPL for Tripos while on
> sabatical at Cambridge, and after he got back, and MIT got the Xerox
> Alto/Dover donation, he moved that one to the Alto.
Double check with Dave.  I think the Alto donation 
occurred well before his stay at Cambridge, and I 
think we had an Alto TFTP implementation well 
before he left.  I don't remember if Dave's 
original small TCP/Telnet client on the Alto 
predated his Tripos implementation --- I have a 
vague memory that he rewrote the Alto 
implementation when he came back, but I may be 
totally off there -- he may have written it from 
scratch afterwards.
>
> Some of the ideas he did on his "user TELNET centric TCP" were used in a TCP
> we did for PDP-11 Unix (by Larry Allen - Liza Martin did a more classical TCP
> for the same machine - both used the same kernel support, where only the
> packet de-mux was in the kernel, and the rest of the TCP was in the user
> space). I then did a TCP for Bridge based on the Allen one. The IBM PC one
> came after all those, I think (maybe not after the Bridge one, but definitely
> after the others).
>
> I don't have dates off the top of my head for much of that (although I could
> probably research it in my archives if anyone needs to know); I can say for
> sure that the Alto one was done around March 1980.
>
>
>      >  Danny Cohen and David Reed were proponents of splitting off IP but I
>      >  don't think they were on the ICCB
>
> I'm pretty sure Dave didn't. He phased out of network work shortly after
> doing UDP (January 1979). I don't recall what he switched to working on (I
> had thought it was his PhD thesis, but I see that was done by '78).
Dave Reed was still working on networking, in 
addition to Swallow, after 79.  He worked on what 
he called "non-FIFO protocols", BLAST (a 
disk-to-disk transfer protocol, predating NETBLT, 
but influencing it) and Blink (a remote display 
protocol that was contemporary with Bob Scheiffler 
starting X down the hall, but we thought 
(incorrectly, it turns out) that the sequencing 
imposed by TCP would make it too slow for running 
the graphic displays for our operating system 
(Swift)).  This doesn't say anything about whether 
Dave Reed was on the ICCB (but you can ask him).
>
> 	Noel
>

Noel Chiappa | 13 May 2012 17:07
Picon

Re: The UCLA 360/91 on the ARPAnet/Internet

    > From: Dave Walden <dave.walden.family <at> gmail.com>

    > I think we called it the Network Working Group during the ARPANET
    > pre-Internet days -- the group writing RFCs to each other. (Or am I
    > talking about some different topic than Noel is talking about.)

I think so. You seem to be talking about the group that did the Host-Host
protocol (aka NCP), whereas I'm talking about the group that did TCP/IP.

	Noel

Noel Chiappa | 13 May 2012 18:39
Picon

Re: The UCLA 360/91 on the ARPAnet/Internet

    > From: Vint Cerf <vint <at> google.com>

    > The network working group did nco, telnet, FTP, eventually smtp,
    > although the latter might have been post-1982 and for Internet and not
    > Arpanet (?).

I thought SMTP came out of MSGROUP, or perhaps some hybrid of MSGGROUP and
the old NWG? (I vaguely recall chit-chat from other hackers in the MIT AI Lab
about it.) It _definitely_ was not from the TCP/Ip group(s).

None of RFCs 772, 780, 788 or 821 says anything definitive about where it
came from, alas. There are some (much earlier) RFCs about nail which I didn't
delve into which may help on this.

(Amusingly, 772 expands 'NCP' to "Network Control Protocol", which is what I
for many years thought/assumed it was - but it turns out that in the
beginning, it means 'Network Control Program'. Nice to know there is some
formal backup for 'Protocol'... :-)

SMTP was always intended for use with both NCP and TCP, and saw most of its
early use under NCP.

    > From: dave.walden.family <at> gmail.com

    > Regarding a second ARPANET host at UCLA, and other places, e.g. MIT: my
    > memory is that a lot of ARPA NET traffic was intra IMP site.

Indeed - especially between the ITS machines at MIT, which had a shared file
system across the ARPANET (and built into the OS, so all apps automatically
had access to it), so that any place you could name/use a file on the machine
you were on, you could just as easily name/use one on one of the others. So
that tended to generate a lot of traffic.

I recall seeing some numbers for packets at MIT, which split the data up into
inter-site and intra-site, but alas I don't think I have access to them any
more (there were weekly reports from BBN, IIRC).

	Noel

Craig Partridge | 13 May 2012 21:58
Picon

Re: The UCLA 360/91 on the ARPAnet/Internet

> The network working group did nco, telnet, FTP, eventually smtp, although
> the latter might have been post-1982 and for Internet and not Arpanet (?).

MTP and its successor, SMTP, were for the Internet, not ARPANET.  As best
I can reconstruct from RFCs and various people's recollections, the
initial plan was to launch TCP/IP with a new and improved email that
did multimedia mail.  But the DARPA PM (initials VC) realized in early
1980 that TCP/IP was going to mature ahead of multimedia -- and also felt
that the Internet needed something better than a hacked FTP supporting such
an important application.  So he created a transition plan, documented
in RFCs 771 and 773.  RFC 772, by Postel and Sluizer, introduced MTP, the
planned Internet email protocol.  After a year of working on MTP, and in
response to regular criticism of the MTP design, apparently led by Peter
Kirstein, Jon tossed MTP for a simpler SMTP (which, it appears, was
inspired by the RFC 785 documentation of the MTP TOPS-20 envelope -- as
each SMTP command fills in a line in the TOPS-20 envelope file).

Thanks!

Craig


Gmane