|
|
ARCHIVE: TCP-IP Distribution List - Archives (1988)
DOCUMENT: TCP-IP Distribution List for June 1988 (316 messages, 158510 bytes)
SOURCE: http://securitydigest.org/exec/display?f=tcp-ip/archive/1988/06.txt&t=text/plain
NOTICE: securitydigest.org recognises the rights of all third-party works.
START OF DOCUMENT
-----------[000000][next][prev][last][first]---------------------------------------------------- Date: 1 Jun 88 03:01:35 GMT From: jra@jc3b21.UUCP (Jay R. Ashworth) To: rec.ham-radio.packet,comp.protocols.tcp-ip Subject: SLIP Info please?
Can anybody email me more details about SLIP (Serial Link Internet Protocol)? I am interested in the possibility of supporting multiple telnet type login sessions on one physical radio channel, using a standard, albeit high speed (38.4Kb?) serial line between TNC and computer. Does KA9Q do this? Are other possible sources PD? I need to have source code available. I (read: my employer) would be interested in discussing commercial licensing at some future point. For now, though, folks, I'd just like to know what I'm talking about. Can you help? Email ONLY, please. The .sig path should work just fine. Tnx, -- jra KA1FJX -- Jay R. Ashworth ---+-- Suncoast Television Productions--+ ...!uunet!codas! 10974 111th St. N. | producers of Suncoast Magazine | !usfvax2!jc3b21!jra Seminole FL 34648 +------------------------------------------------+--------- (813) 397-1859 ----+-- Premiering on Vision Cable Ch. 24 in July ---+ :-) !$ Robert Heinlein, 1901-1988, alas, not as long-lived as Lazarus Long. R. I. P.
-----------[000001][next][prev][last][first]---------------------------------------------------- Date: 1 Jun 88 06:54:36 GMT From: per@erix.UUCP (Per Hedeland) To: comp.dcom.lans,comp.protocols.tcp-ip Subject: Re: Subnetting
While it may be a bit late, I thought I should post a short summary of the information I got in response to my query a few weeks back - it did generate some discussion, after all. If you recall, the issue was how to use subnetting on a network structure with a big backbone net and many small ones hanging off of it. I think the below is the essence of what I found out; I also have a pile of mail for those particularly interested. - Unequal-sized subnets, whether or not a Good Thing, is not currently implemented in any generally accepted way (and thus of little interest to us). - Partitioned subnets (i.e. subnets of a given net interconnected only by some other net) are out. - One can have several logical subnets on the same wire (i.e. the backbone in our case), thus effectively increasing the address space, at the expense of some manual "routing" (i.e. gateways have to be explicitly told that the different subnets can be accessed via the same interface - hosts on such a wire can be "fooled" into believing that it's all one (bigger) subnet). We will probably go for the latter method, with a long-term goal of splitting our backbone by using dedicated routers. Thanks to all who offered help and advice! ---Per Hedeland
-----------[000002][next][prev][last][first]---------------------------------------------------- Date: 1 Jun 88 07:09:14 GMT From: tmanos@aocgl.UUCP (Theodore W. Manos) To: comp.protocols.tcp-ip Subject: Re: non-*NIX implementations
Ya Mike, what are you looking for? VM/CMS? VMS? MS/DOS? Macintosh? MPE?
There's stuff all over the place.
-Ted
---------
Ted Manos tmanos@aocgl.{COM,UUCP,UU.NET} or ...!{uunet,mcdchg}!aocgl!tmanos
-----------[000003][next][prev][last][first]----------------------------------------------------
Date: 1 Jun 88 07:44:49 GMT
From: jh@tut.fi (Juha Hein{nen)
To: comp.protocols.misc,comp.dcom.lans,comp.protocols.tcp-ip
Subject: Re: Linking LAN's via Public X.25SunLink X.25 indeed allows connecting two IP networks over X.25 but it requires a PVC and cannot dynamically open and close the connection. You may want to check the Cisco router product that also has the later capability. -- Juha Heinanen, Tampere Univ. of Technology, Finland jh@tut.fi (Internet), tut!jh (UUCP), jh@tut (Bitnet)
-----------[000004][next][prev][last][first]---------------------------------------------------- Date: Wed, 1 Jun 88 14:06 EST From: AIVANO@Venus.YCC.Yale.Edu To: tcp-ip@sri-nic.arpa Subject: Moderated Newsgroup Posting
Path: venus!aivano From: aivano@venus.ycc.yale.edu Newsgroups: mail.tcp-ip Subject: Public Domain TN3270 Message-ID: <27@venus.ycc.yale.edu> Date: 1 Jun 88 14:05:48 GMT Organisation: VMS NEWS V4.0 Lines: 11 Is there a public domain TN3270 program that runs under VMS and can interface with Wollongong's TCP/IP? We would prefer to have source code so that we could write our own interface, but could live with a documented executable that includes an interface to the Wollongong TCP/IP. Please send replies directly to me, Sandy Aivano Yale Computer Center AIVANO@YALEVMS (BITNET) AIVANO@YALEVMS.YCC.YALE.EDU (ARPA)
-----------[000005][next][prev][last][first]---------------------------------------------------- Date: Wed, 1 Jun 88 18:45 EDT From: PMDF Mail Server <Postmaster%BKNLVMS.BITNET@CUNYVM.CUNY.EDU> To: TCP-IP@SRI-NIC.ARPA Subject: Undeliverable mail
The message could not be delivered to:
Addressee: DAVIS
Reason:
%MAIL-E-NOSUCHUSR, no such user DAVIS at node
----------------------------------------
Received: from JNET-DAEMON by BKNLVMS.BITNET; Wed, 1 Jun 88 18:40 EDT
Received: From OHSTVMA(MAILER) by BKNLVMS with Jnet id 6415 for DAVIS@BKNLVMS;
Wed, 1 Jun 88 18:39 EDT
Received: by OHSTVMA (Mailer X1.25) id 6412; Wed, 01 Jun 88 18:36:57 EDT
Date: Wed, 1 Jun 88 07:09:14 GMT
From: "Theodore W. Manos" <aocgl!tmanos@uunet.uu.NET>
Subject: Re: non-*NIX implementations
Sender: ARPA TCP-IP Discussion Redistribution <TCPIP-L@OHSTVMA.BITNET>
To: jeff davis <DAVIS@BKNLVMS.BITNET>, 'Ralph Droms' <DROMS@BKNLVMS.BITNET>,
JERRY MEAD <MEAD@BKNLVMS.BITNET>, "CARL I. NEWMAN" <NEWMAN@BKNLVMS.BITNET>,
CHRIS RILEY <RILEY@BKNLVMS.BITNET>, "TIMOTHY M. SCHREYER"
<SCHREYER@BKNLVMS.BITNET>
Reply-to: TCP-IP@SRI-NIC.ARPA
Comments: Warning -- original Sender: tag was tcp-ip-request@sri-nic.arpa
X-To: tcp-ip@sri-nic.arpa
Ya Mike, what are you looking for? VM/CMS? VMS? MS/DOS? Macintosh? MPE?
There's stuff all over the place.
-Ted
---------
Ted Manos tmanos@aocgl.{COM,UUCP,UU.NET} or ...!{uunet,mcdchg}!aocgl!tmanos
-----------[000006][next][prev][last][first]---------------------------------------------------- Date: Wed, 1 Jun 88 18:50 EDT From: PMDF Mail Server <Postmaster%BKNLVMS.BITNET@CUNYVM.CUNY.EDU> To: TCP-IP@SRI-NIC.ARPA Subject: Undeliverable mail
The message could not be delivered to:
Addressee: SCHREYER
Reason:
%MAIL-E-NOSUCHUSR, no such user SCHREYER at node
----------------------------------------
Received: from JNET-DAEMON by BKNLVMS.BITNET; Wed, 1 Jun 88 18:46 EDT
Received: From OHSTVMA(MAILER) by BKNLVMS with Jnet id 6421 for
SCHREYER@BKNLVMS; Wed, 1 Jun 88 18:41 EDT
Received: by OHSTVMA (Mailer X1.25) id 6412; Wed, 01 Jun 88 18:36:58 EDT
Date: Wed, 1 Jun 88 07:09:14 GMT
From: "Theodore W. Manos" <aocgl!tmanos@uunet.uu.NET>
Subject: Re: non-*NIX implementations
Sender: ARPA TCP-IP Discussion Redistribution <TCPIP-L@OHSTVMA.BITNET>
To: jeff davis <DAVIS@BKNLVMS.BITNET>, 'Ralph Droms' <DROMS@BKNLVMS.BITNET>,
JERRY MEAD <MEAD@BKNLVMS.BITNET>, "CARL I. NEWMAN" <NEWMAN@BKNLVMS.BITNET>,
CHRIS RILEY <RILEY@BKNLVMS.BITNET>, "TIMOTHY M. SCHREYER"
<SCHREYER@BKNLVMS.BITNET>
Reply-to: TCP-IP@SRI-NIC.ARPA
Comments: Warning -- original Sender: tag was tcp-ip-request@sri-nic.arpa
X-To: tcp-ip@sri-nic.arpa
Ya Mike, what are you looking for? VM/CMS? VMS? MS/DOS? Macintosh? MPE?
There's stuff all over the place.
-Ted
---------
Ted Manos tmanos@aocgl.{COM,UUCP,UU.NET} or ...!{uunet,mcdchg}!aocgl!tmanos
-----------[000007][next][prev][last][first]---------------------------------------------------- Date: Wed, 1 Jun 88 18:55 EDT From: PMDF Mail Server <Postmaster%BKNLVMS.BITNET@CUNYVM.CUNY.EDU> To: TCP-IP@SRI-NIC.ARPA Subject: Undeliverable mail
The message could not be delivered to: Addressee: SCHREYER Reason: %MAIL-E-NOSUCHUSR, no such user SCHREYER at node ---------------------------------------- Received: from JNET-DAEMON by BKNLVMS.BITNET; Wed, 1 Jun 88 18:51 EDT Received: From OHSTVMA(MAILER) by BKNLVMS with Jnet id 6556 for SCHREYER@BKNLVMS; Wed, 1 Jun 88 18:46 EDT Received: by OHSTVMA (Mailer X1.25) id 6547; Wed, 01 Jun 88 18:38:26 EDT Date: Wed, 1 Jun 88 03:01:35 GMT From: "Jay R. Ashworth" <ukma!uflorida!usfvax2!jc3b21!jra@nrl-cmf.ARPA> Subject: SLIP Info please? Sender: ARPA TCP-IP Discussion Redistribution <TCPIP-L@OHSTVMA.BITNET> To: jeff davis <DAVIS@BKNLVMS.BITNET>, 'Ralph Droms' <DROMS@BKNLVMS.BITNET>, JERRY MEAD <MEAD@BKNLVMS.BITNET>, "CARL I. NEWMAN" <NEWMAN@BKNLVMS.BITNET>, CHRIS RILEY <RILEY@BKNLVMS.BITNET>, "TIMOTHY M. SCHREYER" <SCHREYER@BKNLVMS.BITNET> Reply-to: TCP-IP@SRI-NIC.ARPA Comments: Warning -- original Sender: tag was tcp-ip-request@sri-nic.arpa X-To: tcp-ip@sri-nic.arpa Can anybody email me more details about SLIP (Serial Link Internet Protocol)? I am interested in the possibility of supporting multiple telnet type login sessions on one physical radio channel, using a standard, albeit high speed (38.4Kb?) serial line between TNC and computer. Does KA9Q do this? Are other possible sources PD? I need to have source code available. I (read: my employer) would be interested in discussing commercial licensing at some future point. For now, though, folks, I'd just like to know what I'm talking about. Can you help? Email ONLY, please. The .sig path should work just fine. Tnx, -- jra KA1FJX -- Jay R. Ashworth ---+-- Suncoast Television Productions--+ ...!uunet!codas! 10974 111th St. N. | producers of Suncoast Magazine | !usfvax2!jc3b21!jra Seminole FL 34648 +------------------------------------------------+--------- (813) 397-1859 ----+-- Premiering on Vision Cable Ch. 24 in July ---+ :-) !$ Robert Heinlein, 1901-1988, alas, not as long-lived as Lazarus Long. R. I. P.
-----------[000008][next][prev][last][first]---------------------------------------------------- Date: Wed, 1 Jun 88 19:00 EDT From: PMDF Mail Server <Postmaster%BKNLVMS.BITNET@CUNYVM.CUNY.EDU> To: TCP-IP@SRI-NIC.ARPA Subject: Undeliverable mail
The message could not be delivered to: Addressee: RILEY Reason: %MAIL-E-NOSUCHUSR, no such user RILEY at node ---------------------------------------- Received: from JNET-DAEMON by BKNLVMS.BITNET; Wed, 1 Jun 88 18:56 EDT Received: From OHSTVMA(MAILER) by BKNLVMS with Jnet id 6555 for RILEY@BKNLVMS; Wed, 1 Jun 88 18:46 EDT Received: by OHSTVMA (Mailer X1.25) id 6547; Wed, 01 Jun 88 18:38:25 EDT Date: Wed, 1 Jun 88 03:01:35 GMT From: "Jay R. Ashworth" <ukma!uflorida!usfvax2!jc3b21!jra@nrl-cmf.ARPA> Subject: SLIP Info please? Sender: ARPA TCP-IP Discussion Redistribution <TCPIP-L@OHSTVMA.BITNET> To: jeff davis <DAVIS@BKNLVMS.BITNET>, 'Ralph Droms' <DROMS@BKNLVMS.BITNET>, JERRY MEAD <MEAD@BKNLVMS.BITNET>, "CARL I. NEWMAN" <NEWMAN@BKNLVMS.BITNET>, CHRIS RILEY <RILEY@BKNLVMS.BITNET>, "TIMOTHY M. SCHREYER" <SCHREYER@BKNLVMS.BITNET> Reply-to: TCP-IP@SRI-NIC.ARPA Comments: Warning -- original Sender: tag was tcp-ip-request@sri-nic.arpa X-To: tcp-ip@sri-nic.arpa Can anybody email me more details about SLIP (Serial Link Internet Protocol)? I am interested in the possibility of supporting multiple telnet type login sessions on one physical radio channel, using a standard, albeit high speed (38.4Kb?) serial line between TNC and computer. Does KA9Q do this? Are other possible sources PD? I need to have source code available. I (read: my employer) would be interested in discussing commercial licensing at some future point. For now, though, folks, I'd just like to know what I'm talking about. Can you help? Email ONLY, please. The .sig path should work just fine. Tnx, -- jra KA1FJX -- Jay R. Ashworth ---+-- Suncoast Television Productions--+ ...!uunet!codas! 10974 111th St. N. | producers of Suncoast Magazine | !usfvax2!jc3b21!jra Seminole FL 34648 +------------------------------------------------+--------- (813) 397-1859 ----+-- Premiering on Vision Cable Ch. 24 in July ---+ :-) !$ Robert Heinlein, 1901-1988, alas, not as long-lived as Lazarus Long. R. I. P.
-----------[000009][next][prev][last][first]---------------------------------------------------- Date: Wed, 1 Jun 88 19:05 EDT From: PMDF Mail Server <Postmaster%BKNLVMS.BITNET@CUNYVM.CUNY.EDU> To: TCP-IP@SRI-NIC.ARPA Subject: Undeliverable mail
The message could not be delivered to: Addressee: NEWMAN Reason: %MAIL-E-NOSUCHUSR, no such user NEWMAN at node ---------------------------------------- Received: from JNET-DAEMON by BKNLVMS.BITNET; Wed, 1 Jun 88 19:01 EDT Received: From OHSTVMA(MAILER) by BKNLVMS with Jnet id 6554 for NEWMAN@BKNLVMS; Wed, 1 Jun 88 18:46 EDT Received: by OHSTVMA (Mailer X1.25) id 6547; Wed, 01 Jun 88 18:38:25 EDT Date: Wed, 1 Jun 88 03:01:35 GMT From: "Jay R. Ashworth" <ukma!uflorida!usfvax2!jc3b21!jra@nrl-cmf.ARPA> Subject: SLIP Info please? Sender: ARPA TCP-IP Discussion Redistribution <TCPIP-L@OHSTVMA.BITNET> To: jeff davis <DAVIS@BKNLVMS.BITNET>, 'Ralph Droms' <DROMS@BKNLVMS.BITNET>, JERRY MEAD <MEAD@BKNLVMS.BITNET>, "CARL I. NEWMAN" <NEWMAN@BKNLVMS.BITNET>, CHRIS RILEY <RILEY@BKNLVMS.BITNET>, "TIMOTHY M. SCHREYER" <SCHREYER@BKNLVMS.BITNET> Reply-to: TCP-IP@SRI-NIC.ARPA Comments: Warning -- original Sender: tag was tcp-ip-request@sri-nic.arpa X-To: tcp-ip@sri-nic.arpa Can anybody email me more details about SLIP (Serial Link Internet Protocol)? I am interested in the possibility of supporting multiple telnet type login sessions on one physical radio channel, using a standard, albeit high speed (38.4Kb?) serial line between TNC and computer. Does KA9Q do this? Are other possible sources PD? I need to have source code available. I (read: my employer) would be interested in discussing commercial licensing at some future point. For now, though, folks, I'd just like to know what I'm talking about. Can you help? Email ONLY, please. The .sig path should work just fine. Tnx, -- jra KA1FJX -- Jay R. Ashworth ---+-- Suncoast Television Productions--+ ...!uunet!codas! 10974 111th St. N. | producers of Suncoast Magazine | !usfvax2!jc3b21!jra Seminole FL 34648 +------------------------------------------------+--------- (813) 397-1859 ----+-- Premiering on Vision Cable Ch. 24 in July ---+ :-) !$ Robert Heinlein, 1901-1988, alas, not as long-lived as Lazarus Long. R. I. P.
-----------[000010][next][prev][last][first]---------------------------------------------------- Date: Wed, 1 Jun 88 19:20 EDT From: PMDF Mail Server <Postmaster%BKNLVMS.BITNET@CUNYVM.CUNY.EDU> To: TCP-IP@SRI-NIC.ARPA Subject: Undeliverable mail
The message could not be delivered to: Addressee: DAVIS Reason: %MAIL-E-NOSUCHUSR, no such user DAVIS at node ---------------------------------------- Received: from JNET-DAEMON by BKNLVMS.BITNET; Wed, 1 Jun 88 19:16 EDT Received: From OHSTVMA(MAILER) by BKNLVMS with Jnet id 6550 for DAVIS@BKNLVMS; Wed, 1 Jun 88 18:45 EDT Received: by OHSTVMA (Mailer X1.25) id 6547; Wed, 01 Jun 88 18:38:24 EDT Date: Wed, 1 Jun 88 03:01:35 GMT From: "Jay R. Ashworth" <ukma!uflorida!usfvax2!jc3b21!jra@nrl-cmf.ARPA> Subject: SLIP Info please? Sender: ARPA TCP-IP Discussion Redistribution <TCPIP-L@OHSTVMA.BITNET> To: jeff davis <DAVIS@BKNLVMS.BITNET>, 'Ralph Droms' <DROMS@BKNLVMS.BITNET>, JERRY MEAD <MEAD@BKNLVMS.BITNET>, "CARL I. NEWMAN" <NEWMAN@BKNLVMS.BITNET>, CHRIS RILEY <RILEY@BKNLVMS.BITNET>, "TIMOTHY M. SCHREYER" <SCHREYER@BKNLVMS.BITNET> Reply-to: TCP-IP@SRI-NIC.ARPA Comments: Warning -- original Sender: tag was tcp-ip-request@sri-nic.arpa X-To: tcp-ip@sri-nic.arpa Can anybody email me more details about SLIP (Serial Link Internet Protocol)? I am interested in the possibility of supporting multiple telnet type login sessions on one physical radio channel, using a standard, albeit high speed (38.4Kb?) serial line between TNC and computer. Does KA9Q do this? Are other possible sources PD? I need to have source code available. I (read: my employer) would be interested in discussing commercial licensing at some future point. For now, though, folks, I'd just like to know what I'm talking about. Can you help? Email ONLY, please. The .sig path should work just fine. Tnx, -- jra KA1FJX -- Jay R. Ashworth ---+-- Suncoast Television Productions--+ ...!uunet!codas! 10974 111th St. N. | producers of Suncoast Magazine | !usfvax2!jc3b21!jra Seminole FL 34648 +------------------------------------------------+--------- (813) 397-1859 ----+-- Premiering on Vision Cable Ch. 24 in July ---+ :-) !$ Robert Heinlein, 1901-1988, alas, not as long-lived as Lazarus Long. R. I. P.
-----------[000011][next][prev][last][first]---------------------------------------------------- Date: Wed, 1 Jun 88 19:25 EDT From: PMDF Mail Server <Postmaster%BKNLVMS.BITNET@CUNYVM.CUNY.EDU> To: TCP-IP@SRI-NIC.ARPA Subject: Undeliverable mail
The message could not be delivered to:
Addressee: RILEY
Reason:
%MAIL-E-NOSUCHUSR, no such user RILEY at node
----------------------------------------
Received: from JNET-DAEMON by BKNLVMS.BITNET; Wed, 1 Jun 88 19:21 EDT
Received: From OHSTVMA(MAILER) by BKNLVMS with Jnet id 6420 for RILEY@BKNLVMS;
Wed, 1 Jun 88 18:40 EDT
Received: by OHSTVMA (Mailer X1.25) id 6412; Wed, 01 Jun 88 18:36:58 EDT
Date: Wed, 1 Jun 88 07:09:14 GMT
From: "Theodore W. Manos" <aocgl!tmanos@uunet.uu.NET>
Subject: Re: non-*NIX implementations
Sender: ARPA TCP-IP Discussion Redistribution <TCPIP-L@OHSTVMA.BITNET>
To: jeff davis <DAVIS@BKNLVMS.BITNET>, 'Ralph Droms' <DROMS@BKNLVMS.BITNET>,
JERRY MEAD <MEAD@BKNLVMS.BITNET>, "CARL I. NEWMAN" <NEWMAN@BKNLVMS.BITNET>,
CHRIS RILEY <RILEY@BKNLVMS.BITNET>, "TIMOTHY M. SCHREYER"
<SCHREYER@BKNLVMS.BITNET>
Reply-to: TCP-IP@SRI-NIC.ARPA
Comments: Warning -- original Sender: tag was tcp-ip-request@sri-nic.arpa
X-To: tcp-ip@sri-nic.arpa
Ya Mike, what are you looking for? VM/CMS? VMS? MS/DOS? Macintosh? MPE?
There's stuff all over the place.
-Ted
---------
Ted Manos tmanos@aocgl.{COM,UUCP,UU.NET} or ...!{uunet,mcdchg}!aocgl!tmanos
-----------[000012][next][prev][last][first]---------------------------------------------------- Date: Wed, 1 Jun 88 19:30 EDT From: PMDF Mail Server <Postmaster%BKNLVMS.BITNET@CUNYVM.CUNY.EDU> To: TCP-IP@SRI-NIC.ARPA Subject: Undeliverable mail
The message could not be delivered to:
Addressee: NEWMAN
Reason:
%MAIL-E-NOSUCHUSR, no such user NEWMAN at node
----------------------------------------
Received: from JNET-DAEMON by BKNLVMS.BITNET; Wed, 1 Jun 88 19:26 EDT
Received: From OHSTVMA(MAILER) by BKNLVMS with Jnet id 6419 for NEWMAN@BKNLVMS;
Wed, 1 Jun 88 18:40 EDT
Received: by OHSTVMA (Mailer X1.25) id 6412; Wed, 01 Jun 88 18:36:57 EDT
Date: Wed, 1 Jun 88 07:09:14 GMT
From: "Theodore W. Manos" <aocgl!tmanos@uunet.uu.NET>
Subject: Re: non-*NIX implementations
Sender: ARPA TCP-IP Discussion Redistribution <TCPIP-L@OHSTVMA.BITNET>
To: jeff davis <DAVIS@BKNLVMS.BITNET>, 'Ralph Droms' <DROMS@BKNLVMS.BITNET>,
JERRY MEAD <MEAD@BKNLVMS.BITNET>, "CARL I. NEWMAN" <NEWMAN@BKNLVMS.BITNET>,
CHRIS RILEY <RILEY@BKNLVMS.BITNET>, "TIMOTHY M. SCHREYER"
<SCHREYER@BKNLVMS.BITNET>
Reply-to: TCP-IP@SRI-NIC.ARPA
Comments: Warning -- original Sender: tag was tcp-ip-request@sri-nic.arpa
X-To: tcp-ip@sri-nic.arpa
Ya Mike, what are you looking for? VM/CMS? VMS? MS/DOS? Macintosh? MPE?
There's stuff all over the place.
-Ted
---------
Ted Manos tmanos@aocgl.{COM,UUCP,UU.NET} or ...!{uunet,mcdchg}!aocgl!tmanos
-----------[000013][next][prev][last][first]---------------------------------------------------- Date: Wed, 1 Jun 88 19:45 EDT From: PMDF Mail Server <Postmaster%BKNLVMS.BITNET@CUNYVM.CUNY.EDU> To: TCP-IP@SRI-NIC.ARPA Subject: Undeliverable mail
The message could not be delivered to: Addressee: SCHREYER Reason: %MAIL-E-NOSUCHUSR, no such user SCHREYER at node ---------------------------------------- Received: from JNET-DAEMON by BKNLVMS.BITNET; Wed, 1 Jun 88 19:40 EDT Received: From OHSTVMA(MAILER) by BKNLVMS with Jnet id 8645 for SCHREYER@BKNLVMS; Wed, 1 Jun 88 19:36 EDT Received: by OHSTVMA (Mailer X1.25) id 8634; Wed, 01 Jun 88 19:31:40 EDT Date: Wed, 1 Jun 88 12:42:55 CDT From: John Lee <JLEE@STL-HOST1.ARPA> Subject: WHOIS prog. for 5000/80 Sender: ARPA TCP-IP Discussion Redistribution <TCPIP-L@OHSTVMA.BITNET> To: jeff davis <DAVIS@BKNLVMS.BITNET>, 'Ralph Droms' <DROMS@BKNLVMS.BITNET>, JERRY MEAD <MEAD@BKNLVMS.BITNET>, "CARL I. NEWMAN" <NEWMAN@BKNLVMS.BITNET>, CHRIS RILEY <RILEY@BKNLVMS.BITNET>, "TIMOTHY M. SCHREYER" <SCHREYER@BKNLVMS.BITNET> Reply-to: TCP-IP@SRI-NIC.ARPA X-To: tcp-ip@SRI-NIC.ARPA Ladies and Gentlemen: I am the host administrator of an Unisys (Sperry) 5000/80 running release 5.2 of UNIX with release 2.0 of the DDN software. I am looking for someone who has a version of "WHOIS" running on their 5000/80. I would greatly appreciate getting the source code of that program. Can anyone help? Thanks for your time. John lee Information Systems Command 4300 Goodfellow St. Louis, Mo. 63120 mailbox: jlee@AVSCOM.ARPA phone: (314) 263-3137 autovon: 693-3137 -------
-----------[000014][next][prev][last][first]---------------------------------------------------- Date: Wed, 1 Jun 88 19:53 EDT From: PMDF Mail Server <Postmaster%BKNLVMS.BITNET@CUNYVM.CUNY.EDU> To: TCP-IP@SRI-NIC.ARPA Subject: Undeliverable mail
The message could not be delivered to: Addressee: RILEY Reason: %MAIL-E-NOSUCHUSR, no such user RILEY at node ---------------------------------------- Received: from JNET-DAEMON by BKNLVMS.BITNET; Wed, 1 Jun 88 19:49 EDT Received: From OHSTVMA(MAILER) by BKNLVMS with Jnet id 8640 for RILEY@BKNLVMS; Wed, 1 Jun 88 19:36 EDT Received: by OHSTVMA (Mailer X1.25) id 8634; Wed, 01 Jun 88 19:31:40 EDT Date: Wed, 1 Jun 88 12:42:55 CDT From: John Lee <JLEE@STL-HOST1.ARPA> Subject: WHOIS prog. for 5000/80 Sender: ARPA TCP-IP Discussion Redistribution <TCPIP-L@OHSTVMA.BITNET> To: jeff davis <DAVIS@BKNLVMS.BITNET>, 'Ralph Droms' <DROMS@BKNLVMS.BITNET>, JERRY MEAD <MEAD@BKNLVMS.BITNET>, "CARL I. NEWMAN" <NEWMAN@BKNLVMS.BITNET>, CHRIS RILEY <RILEY@BKNLVMS.BITNET>, "TIMOTHY M. SCHREYER" <SCHREYER@BKNLVMS.BITNET> Reply-to: TCP-IP@SRI-NIC.ARPA X-To: tcp-ip@SRI-NIC.ARPA Ladies and Gentlemen: I am the host administrator of an Unisys (Sperry) 5000/80 running release 5.2 of UNIX with release 2.0 of the DDN software. I am looking for someone who has a version of "WHOIS" running on their 5000/80. I would greatly appreciate getting the source code of that program. Can anyone help? Thanks for your time. John lee Information Systems Command 4300 Goodfellow St. Louis, Mo. 63120 mailbox: jlee@AVSCOM.ARPA phone: (314) 263-3137 autovon: 693-3137 -------
-----------[000015][next][prev][last][first]---------------------------------------------------- Date: Wed, 1 Jun 88 19:59 EDT From: PMDF Mail Server <Postmaster%BKNLVMS.BITNET@CUNYVM.CUNY.EDU> To: TCP-IP@SRI-NIC.ARPA Subject: Undeliverable mail
The message could not be delivered to: Addressee: NEWMAN Reason: %MAIL-E-NOSUCHUSR, no such user NEWMAN at node ---------------------------------------- Received: from JNET-DAEMON by BKNLVMS.BITNET; Wed, 1 Jun 88 19:54 EDT Received: From OHSTVMA(MAILER) by BKNLVMS with Jnet id 8639 for NEWMAN@BKNLVMS; Wed, 1 Jun 88 19:36 EDT Received: by OHSTVMA (Mailer X1.25) id 8634; Wed, 01 Jun 88 19:31:40 EDT Date: Wed, 1 Jun 88 12:42:55 CDT From: John Lee <JLEE@STL-HOST1.ARPA> Subject: WHOIS prog. for 5000/80 Sender: ARPA TCP-IP Discussion Redistribution <TCPIP-L@OHSTVMA.BITNET> To: jeff davis <DAVIS@BKNLVMS.BITNET>, 'Ralph Droms' <DROMS@BKNLVMS.BITNET>, JERRY MEAD <MEAD@BKNLVMS.BITNET>, "CARL I. NEWMAN" <NEWMAN@BKNLVMS.BITNET>, CHRIS RILEY <RILEY@BKNLVMS.BITNET>, "TIMOTHY M. SCHREYER" <SCHREYER@BKNLVMS.BITNET> Reply-to: TCP-IP@SRI-NIC.ARPA X-To: tcp-ip@SRI-NIC.ARPA Ladies and Gentlemen: I am the host administrator of an Unisys (Sperry) 5000/80 running release 5.2 of UNIX with release 2.0 of the DDN software. I am looking for someone who has a version of "WHOIS" running on their 5000/80. I would greatly appreciate getting the source code of that program. Can anyone help? Thanks for your time. John lee Information Systems Command 4300 Goodfellow St. Louis, Mo. 63120 mailbox: jlee@AVSCOM.ARPA phone: (314) 263-3137 autovon: 693-3137 -------
-----------[000016][next][prev][last][first]---------------------------------------------------- Date: 1 Jun 88 17:36:58 GMT From: JLEE@STL-HOST1.ARPA (John Lee) To: comp.protocols.tcp-ip Subject: whois prog. for 5000/80
Ladies/Gentlemen: I am the host administrator of an Unisys (Sperry) 5000/80 running UNIX 5.2. We are running release 2.0 of DDN software. I am looking for someone who has the "whois" program running on their 5000/80. If so, I would like to get the program (source if possible). Is there anyone who can help? My mailbox is jlee@AVSCOM.ARPA. Thanks for you time. John Lee Information Systems Command 4300 Goodfellow St. Louis, Mo. 63120 mailbox address : jlee@AVSCOM.ARPA -------
-----------[000017][next][prev][last][first]---------------------------------------------------- Date: 1 Jun 88 17:42:55 GMT From: JLEE@STL-HOST1.ARPA (John Lee) To: comp.protocols.tcp-ip Subject: WHOIS prog. for 5000/80
Ladies and Gentlemen: I am the host administrator of an Unisys (Sperry) 5000/80 running release 5.2 of UNIX with release 2.0 of the DDN software. I am looking for someone who has a version of "WHOIS" running on their 5000/80. I would greatly appreciate getting the source code of that program. Can anyone help? Thanks for your time. John lee Information Systems Command 4300 Goodfellow St. Louis, Mo. 63120 mailbox: jlee@AVSCOM.ARPA phone: (314) 263-3137 autovon: 693-3137 -------
-----------[000018][next][prev][last][first]---------------------------------------------------- Date: 1 Jun 88 19:00:48 GMT From: chuck@excelan.UUCP (Chuck Kollars) To: comp.protocols.tcp-ip Subject: Re: Third TCP-IP Book?
In article <925@actnyc.UUCP> gcf@actnyc.UUCP (Gordon Fitch) writes:
>I'd like to get the full titles, etc., of the [TCP/IP] books ...
An Introduction to TCP/IP
by John Davidson
Springer-Verlag, 1988 - ISBN# 0-387-96651-X (also 3-540-96651-X)
paperback, over 100 pages - suggested retail price $24.95
Handbook of Computer Communications Standards
Volume 3, Department of Defense (DOD) Protocol Standards
by William Stallings
Macmillan, 1988 - ISBN# 0-02-948072-8
hardbound, over 200 pages - suggested retail price $34.95
Internetworking With TCP/IP
Principles, Protocols, and Architecture
by Douglas Comer
Prentice Hall, 1988 - ISBN# 0-13-470154-2
hardbound, almost 400 pages - suggested retail price $36.00
--
Chuck Kollars, Excelan, Inc. mtxinu!excelan!chuck@ucbvax.Berkeley.COM
(chuck@excelan.UUCP) ...!{mtxinu,leadsv,cae780}!excelan!chuck
-----------[000019][next][prev][last][first]---------------------------------------------------- Date: 1 Jun 88 19:06:00 GMT From: AIVANO@VENUS.YCC.YALE.EDU To: comp.protocols.tcp-ip Subject: Moderated Newsgroup Posting
Path: venus!aivano From: aivano@venus.ycc.yale.edu Newsgroups: mail.tcp-ip Subject: Public Domain TN3270 Message-ID: <27@venus.ycc.yale.edu> Date: 1 Jun 88 14:05:48 GMT Organisation: VMS NEWS V4.0 Lines: 11 Is there a public domain TN3270 program that runs under VMS and can interface with Wollongong's TCP/IP? We would prefer to have source code so that we could write our own interface, but could live with a documented executable that includes an interface to the Wollongong TCP/IP. Please send replies directly to me, Sandy Aivano Yale Computer Center AIVANO@YALEVMS (BITNET) AIVANO@YALEVMS.YCC.YALE.EDU (ARPA)
-----------[000020][next][prev][last][first]---------------------------------------------------- Date: 1 Jun 88 19:55:34 GMT From: karn@thumper.bellcore.com (Phil R. Karn) To: rec.ham-radio.packet,comp.protocols.tcp-ip Subject: Re: SLIP Info please?
I don't think I've seen a formal description of SLIP, but it is very simple. It is just a framing technique suitable for carrying IP datagrams (or whatever you want) on asynchronous links. Four special characters are defined. They are as follows: <Frame End> C0 hex <Frame Esc> DB <Transposed Frame End> DC <Transposed Frame Esc> DD Transmitter Operation The transmitter sends the frame a byte at a time, ending it with the <Frame End> character. If a <Frame End> character occurs in the body of the frame, it is replaced by the two character sequence <Frame Esc>, <Transposed Frame End>. Similarly, if a <Frame Esc> character occurs in the body of the frame, it is replaced by the two byte sequence <Frame Esc>, <Transposed Frame Esc>. Receiver Operation The receiver appends incoming bytes to a reassembly buffer, passing whatever has been accumulated up to the next layer when it sees a <Frame End> character. (The <Frame End> itself is not added to the buffer). The receiver maintains a one-bit "escaped" flag that is set whenever it sees a <Frame Esc> character. (The <Frame Esc> character itself is NOT added to the reassembly buffer). If the receiver then sees either a <Transposed Frame End> or a <Transposed Frame Esc> while in "escaped" mode, it is translated to a <Frame End> or a <Frame Esc>, respectively, and adds it to the reassembly buffer. Regardless of the character received while in escaped mode, the "escaped" flag is cleared. If the <Transposed Frame End> or <Transposed Frame Esc> characters are received while NOT in "escaped" mode, no special action is necessary; they are added to the reassembly buffer unchanged. Note that the <Frame End> character is *never* sent over the line except as an actual end-of-frame indication. The original SLIP put <Frame End> characters only at the end of each frame. I.e., a series of back-to-back frames would be separated by only a single <Frame End>. I have made a minor, backward compatible change to the protocol that puts a <Frame End> in front of each frame as well. This adds a very small bit of overhead (back-to-back frames are now separated by two <Frame End> characters) but it improves performance over noisy links by forcing the receiver into a known state at the beginning of each new frame. When used to send IP datagrams over phone lines, the datagrams are encapsulated directly in frames formatted as described here; no additional header is carried. There has been considerable discussion about the need for such a header, but nothing has actually come into use, as far as I know. I use SLIP in a different way between a system running my TCP/IP software and a KISS TNC. There I use SLIP style framing to carry AX.25 frames and control messages between the TNC and host, and there is a one-byte "type" field at the beginning of each frame. For details, see the paper by K3MC and myself in last year's ARRL Computer Networking Conference proceedings. (The same article also described SLIP in detail). Phil
-----------[000021][next][prev][last][first]---------------------------------------------------- Date: 1 Jun 88 21:23:40 GMT From: HEILNER_K@VAXC.STEVENS-TECH.EDU To: comp.protocols.tcp-ip Subject: ISO Documents
Hi Does anyone have the address for purchasing documents like ISO 8348. I am particularly interested in finding documents that explain the structure of the network address as defined by ISO. Thanks Keith Heilner Stevens Institute Network Coordinator Heilner_k@sitvxc Heilner_k@vaxc.stevens-tech.edu ------------
-----------[000022][next][prev][last][first]---------------------------------------------------- Date: 1 Jun 88 22:01:10 GMT From: amdahl!pacbell!david@ames.arc.nasa.gov (David St.Pierre) To: tcp-ip@sri-nic.arpa Subject: TCP/IP in MVS?
I'm trying to determine whether or not there are any commercial
products which support TCP/IP on MVS, specifically for the purposes of
FTP. We need to transfer a lot of files around and sneaker-net just
isn't cutting it.
I've talked to one vendor who may have a product out this summer.
Other than that, I'm completely at a loss as to what's available.
What kind of hardware is needed? What's required on the MVS side? How
is security handled (RACF, ACF2)?
Any leads would be appreciated. Please E-mail them to me. Thanks.
--
David St. Pierre 415/823-6800 {att,bellcore,sun,ames,pyramid}!pacbell!david
-----------[000023][next][prev][last][first]---------------------------------------------------- Date: 2 Jun 88 00:25:57 GMT From: wiltzius@lll-lcc.aRpA (Dave P. Wiltzius) To: comp.protocols.tcp-ip Subject: UDP reserved ports
I believe this was discussed here a while back, but I would like to know how daemons (such as TFTPD or FTPD) get their reserved UDP or TCP port (as specified in RFC 1010 if I recall correctly). That is, the port for TFTP is 69 (dex) as per RFC 1010. The TFTP client therefore sends packets to the destination host with UDP port number 69 - which the TFTP daemon on that host should subsequently receive since it listens on UDP port 69. How does it acquire UDP port 69? Directions to appropriate BSD code would be most welcome. Thank you. Dave (wiltzius@lll-lcc.llnl.gov)
-----------[000024][next][prev][last][first]---------------------------------------------------- Date: 2 Jun 88 02:36:48 GMT From: bzs@bu-cs.BU.EDU (Barry Shein) To: comp.protocols.tcp-ip Subject: Re: UDP reserved ports
>How does it acquire UDP port 69? Directions to appropriate >BSD code would be most welcome. > >Thank you. > Dave (wiltzius@lll-lcc.llnl.gov) See the bind and recvfrom manual pages. -Barry Shein, Boston University
-----------[000025][next][prev][last][first]---------------------------------------------------- Date: Thu, 2 Jun 88 11:53 CST From: Michael Califf <CALIFFM%BAYLOR.BITNET@CUNYVM.CUNY.EDU> To: TCP-IP@SRI-NIC.ARPA Subject: RE: TCP/IP in MVS?
Here at Baylor we are using a product from Advintech inc. on our MVS 4381. It is a combined hardware/software product which uses a custom channel-attach box to interface to the ether/DDN and includes SMTP (with a mailer) FTP and TELNET (nvt). This is a new company and a new product so there are still a few bugs, but they are working on them. If you want an address/phone number please send me a note or call. Mike Califf Communications Programming Coordinator Baylor University CALIFFM@BAYLOR.BITNET (817) 755-2711 I have no connection with ACVINTECH other than being an employee of a moderately satisfied customer. My opinions are my own and rarely reflect those of my employers.
-----------[000026][next][prev][last][first]---------------------------------------------------- Date: 2 Jun 88 06:26:44 GMT From: MKL@SRI-NIC.ARPA (Mark Lottor) To: comp.protocols.tcp-ip Subject: Mail Loop
Submissions to the TCP-IP list will now be manually redistributed until the person responsible for the mail loop sends me a personal letter explaining that it is fixed. The bogus mail is from: From: PMDF Mail Server <Postmaster%BKNLVMS.BITNET@CUNYVM.CUNY.EDU> -------
-----------[000027][next][prev][last][first]---------------------------------------------------- Date: 2 Jun 88 12:10:22 GMT From: steve@pdn.UUCP (Steve Fowler) To: comp.protocols.tcp-ip Subject: Re: ISO Documents
In article <8851162341.21a0028a.HEILNER_K> you write: >Does anyone have the address for purchasing documents like ISO 8348. I am >particularly interested in finding documents that explain the structure of >the network address as defined by ISO. > >Keith Heilner >Stevens Institute >Network Coordinator >Heilner_k@sitvxc >Heilner_k@vaxc.stevens-tech.edu Keith, The document you are looking for can be purchased from the following company: OMNICOM, INC. 115 Park Street, S.E. Vienna, VA 22180 TEL: (703) 281-1135 FAX: (703) 281-1505 TLX: 279678 OMNI UR ORDER#: 1-800-OMNICOM (666-4266) I quote from their order form: "The American National Standards Institute (ANSI) has granted to Omnicom the right to distribute ISO/IEC JTC 1 (Information Processing Systems) working papers, draft proposals, draft international standards, and internmational standards currently available for Open Systems Interconnection and Data Commuinications. Topics of interest ionclude the seven layers of OSI, OSI Management, Formal Description Languages, Conformance Testing, Database Languages, Computer Graphics, Text and Office Systems, The Directory, and Remote Database Operations." Omnicom also distributes the CCITT "red" and "green" books. I hope that this information helps you. -- Steve Fowler W(813) 530-8708 Paradyne Corporation | \ _ / "I can't even be held responsible for Mail Stop LF-207 | ~o.O~ my own opinions much less my employer's" 8550 Ulmerton Rd., | (_|_) ..!uunet!pdn!steve Largo, FL 34641 | / U
-----------[000028][next][prev][last][first]---------------------------------------------------- Date: 2 Jun 88 17:06:52 GMT From: indra@amdcad.AMD.COM (Indra K. Singhal) To: comp.protocols.tcp-ip Subject: Convert /etc/hosts to RR format pgm anyone?
Has anyone put together a program/shell script that converts
/etc/hosts to the standard RR format as specified in the RFCs listed?
Thought I'd ask before I get a coleague to spend time reinventing
it. Thanks !!
--
Indra K. Singhal | |
{ucbvax,decwrl,allegra}!amdcad!indra | This space for rent ! |
amdcad!indra@decwrl.dec.com | |
(408) 749-5445(w) | |
-----------[000029][next][prev][last][first]---------------------------------------------------- Date: 2 Jun 88 19:52:31 GMT From: zu!kurt@hc.dspo.gov (Kurt Zeilenga) To: tcp-ip@sri-nic.arpa Subject: TCP/IP for PDP-11 running TSX (RT11)
We have a system here in need of a cheap, basic TCP/IP implementation. It should support at least telnet and FTP. Here is the description I was given of the system: >My machine is a PDP-11/23. The Ethernet card is a DEQNA. My operating >system is TSX-Plus Version 5.1B, which is written by S&H Enterprises. >TSX is based on DEC's RT11, inc this case Version 5. TSX uses all of the >RT11 filesystem and I/O handlers, but replaces the kernel with a >multitasking multiuser real-time kernel. Any pointers, etc., would be greatly appreciated. -- Kurt
-----------[000030][next][prev][last][first]---------------------------------------------------- Date: 2 Jun 88 21:08:08 GMT From: MKL@SRI-NIC.ARPA (Mark Lottor) To: comp.protocols.tcp-ip Subject: a bunch of messages
Received: from DOCKMASTER.ARPA by SRI-NIC.ARPA with TCP; Thu, 2 Jun 88 05:47:11 PDT
Date: Thu, 2 Jun 88 08:45 EDT
From: Fitch@DOCKMASTER.ARPA
Subject: UDP Example Sources
To: tcp-ip@SRI-NIC.ARPA
Message-ID: <880602124550.014174@DOCKMASTER.ARPA>
I am looking for a suite of examples using UDP, ranging from something
simple (say an echo server) to something more complex (say TFTP). Can
someone point me to public domain, anonymous FTP-able, sources? In
particular, I am looking for examples using the Berkeley socket
interface to UDP.
--Jack Fitch (Fitch@dockmaster.arpa) include <std_disclaims.h>
----------------------------------------------------------------------
Received: from uxc.cso.uiuc.edu by SRI-NIC.ARPA with TCP; Thu, 2 Jun 88 09:13:15 PDT
Received: by uxc.cso.uiuc.edu (5.51/9.7)
id AA23522; Thu, 2 Jun 88 10:28:59 CDT
Date: Thu, 2 Jun 88 10:28:59 CDT
From: kline@uxc.cso.uiuc.edu (Charley Kline)
Message-Id: <8806021528.AA23522@uxc.cso.uiuc.edu>
To: tcp-ip@sri-nic.arpa
Subject: Re: non-*NIX implementations
We run TCP implementations on Unix systems as well as VMS, Macintosh,
MSDOS, Cray CTSS, and VM/SP. What did you want to know?
-----
Charley Kline, University of Illinois Computing Services
kline@tuna.cso.uiuc.edu
{ihnp4,uunet,pur-ee,convex}!uiucuxc!kline
"Birth. School. Work. Death."
----------------------------------------------------------------------
Received: from ucbvax.Berkeley.EDU by SRI-NIC.ARPA with TCP;
Thu, 2 Jun 88 09:41:24 PDT
Received: by ucbvax.Berkeley.EDU (5.59/1.28)
id AA16608; Thu, 2 Jun 88 08:32:10 PDT
Received: from USENET by ucbvax.Berkeley.EDU with netnews
for tcp-ip@sri-nic.arpa (tcp-ip@sri-nic.arpa)
(contact usenet@ucbvax.Berkeley.EDU if you have questions)
Date: 1 Jun 88 06:54:36 GMT
From: mcvax!enea!erix!per@uunet.uu.net (Per Hedeland)
Organization: Ericsson Telecom, Stockholm, Sweden
Subject: Re: Subnetting
Message-Id: <1624@erix.UUCP>
References: <1607@erix.UUCP>
Sender: tcp-ip-request@sri-nic.arpa
To: tcp-ip@sri-nic.arpa
While it may be a bit late, I thought I should post a short summary of the
information I got in response to my query a few weeks back - it did generate
some discussion, after all. If you recall, the issue was how to use subnetting
on a network structure with a big backbone net and many small ones hanging
off of it. I think the below is the essence of what I found out; I also have
a pile of mail for those particularly interested.
- Unequal-sized subnets, whether or not a Good Thing, is not currently
implemented in any generally accepted way (and thus of little interest to
us).
- Partitioned subnets (i.e. subnets of a given net interconnected only by some
other net) are out.
- One can have several logical subnets on the same wire (i.e. the backbone in
our case), thus effectively increasing the address space, at the expense of
some manual "routing" (i.e. gateways have to be explicitly told that the
different subnets can be accessed via the same interface - hosts on such
a wire can be "fooled" into believing that it's all one (bigger) subnet).
We will probably go for the latter method, with a long-term goal of splitting
our backbone by using dedicated routers.
Thanks to all who offered help and advice!
---Per Hedeland
----------------------------------------------------------------------
Received: from ucbvax.Berkeley.EDU by SRI-NIC.ARPA with TCP; Thu, 2 Jun 88 10:28:56 PDT
Received: by ucbvax.Berkeley.EDU (5.59/1.28)
id AA18222; Thu, 2 Jun 88 10:04:56 PDT
Received: from USENET by ucbvax.Berkeley.EDU with netnews
for tcp-ip@sri-nic.arpa (tcp-ip@sri-nic.arpa)
(contact usenet@ucbvax.Berkeley.EDU if you have questions)
Date: 1 Jun 88 19:00:48 GMT
From: amdahl!pyramid!leadsv!excelan!chuck@ames.arc.nasa.gov (Chuck Kollars)
Organization: Excelan Inc., San Jose, CA
Subject: Re: Third TCP-IP Book?
Message-Id: <360@lalk.excelan.UUCP>
References: <8805170601.AA21125@Larry.McRCIM.McGill.EDU>, <12399598897.40.LYNCH@A.ISI.EDU>, <925@actnyc.UUCP>
Sender: tcp-ip-request@sri-nic.arpa
To: tcp-ip@sri-nic.arpa
In article <925@actnyc.UUCP> gcf@actnyc.UUCP (Gordon Fitch) writes:
>I'd like to get the full titles, etc., of the [TCP/IP] books ...
An Introduction to TCP/IP
by John Davidson
Springer-Verlag, 1988 - ISBN# 0-387-96651-X (also 3-540-96651-X)
paperback, over 100 pages - suggested retail price $24.95
Handbook of Computer Communications Standards
Volume 3, Department of Defense (DOD) Protocol Standards
by William Stallings
Macmillan, 1988 - ISBN# 0-02-948072-8
hardbound, over 200 pages - suggested retail price $34.95
Internetworking With TCP/IP
Principles, Protocols, and Architecture
by Douglas Comer
Prentice Hall, 1988 - ISBN# 0-13-470154-2
hardbound, almost 400 pages - suggested retail price $36.00
--
Chuck Kollars, Excelan, Inc. mtxinu!excelan!chuck@ucbvax.Berkeley.COM
(chuck@excelan.UUCP) ...!{mtxinu,leadsv,cae780}!excelan!chuck
----------------------------------------------------------------------
Received: from acc.arpa by SRI-NIC.ARPA with TCP; Thu, 2 Jun 88 10:47:19 PDT
Date: 2 Jun 88 10:31:00 PST
From: <art@acc.arpa>
Subject: RE: ISO Documents
To: "heilner_k" <heilner_k@vaxc.stevens-tech.edu>
cc: tcp-ip@sri-nic.arpa
Reply-To: <art@acc.arpa>
>Does anyone have the address for purchasing documents like ISO 8348. I am
>particularly interested in finding documents that explain the structure of
>the network address as defined by ISO.
Two places that we use are:
OMNICOM, Inc.
115 Park Street S.E.
Vienna, VA 22180
(703) 281-1135
AlphaGraphics
10215 N. 35th Ave.
Phoenix, AZ 85051
(602) 863-0999
Both try to obtain up-to-date copies of the standards documents and offer
document duplication services. I believe both will take phone orders on
major credit cards. OMNICOM also provides seminars on ISO protocols, etc.
Art Berggreen
art@acc.arpa
------
----------------------------------------------------------------------
Received: from ucbvax.Berkeley.EDU by SRI-NIC.ARPA with TCP; Thu, 2 Jun 88 12:25:12 PDT
Received: by ucbvax.Berkeley.EDU (5.59/1.28)
id AA19084; Thu, 2 Jun 88 10:44:07 PDT
Received: from USENET by ucbvax.Berkeley.EDU with netnews
for tcp-ip@sri-nic.arpa (tcp-ip@sri-nic.arpa)
(contact usenet@ucbvax.Berkeley.EDU if you have questions)
Date: 2 Jun 88 17:06:52 GMT
From: amdcad!indra@ucbvax.Berkeley.EDU (Indra K. Singhal)
Organization: Advanced Micro Devices, Inc., Sunnyvale, Ca.
Subject: Convert /etc/hosts to RR format pgm anyone?
Message-Id: <21877@amdcad.AMD.COM>
Sender: tcp-ip-request@sri-nic.arpa
To: tcp-ip@sri-nic.arpa
Has anyone put together a program/shell script that converts
/etc/hosts to the standard RR format as specified in the RFCs listed?
Thought I'd ask before I get a coleague to spend time reinventing
it. Thanks !!
--
Indra K. Singhal | |
{ucbvax,decwrl,allegra}!amdcad!indra | This space for rent ! |
amdcad!indra@decwrl.dec.com | |
(408) 749-5445(w) | |
-------
-----------[000031][next][prev][last][first]---------------------------------------------------- Date: 2 Jun 88 22:59:43 GMT From: symchych@SKL-CRC.ARPA (Tim Symchych) To: comp.protocols.tcp-ip Subject: Re: Linking LAN's via Public X.25
Perhaps another view of IP over X.25 might help. While the original question was asked about Sun X.25, there are a number of networks within the ARPA/Internet that use IP over X.25. The experience that Phil Karn described at Bellcore does not describe our experience in establishing the DRENET and XDRENET here in Canada. There is no doubt in my mind that some implementations of packet switching using CCITT X.25 are poor. We did some testing of various networks about two years ago including ARPANET (1822 Links), Telenet in the USA, SATNET, and the public packet switching networks in the UK and Canada (Datapac). Packets were timed in some great loops, and by network segment to allow us to determine level of service over the various segments. Generally, the packets through Telenet and SATNET suffered the most delay. The X.75 gateways didn't seem to work all that well then either. I'm not sure that X.25 was designed for slow speed terminal multiplexing. NO packet switching network works well at that task. In our own case, use of TCP/IP over X.25 has been shown effective from both points of view: cost and throughput. In Canada, we have at least one first rate X.25 packet switching network. Through eight years of using Datapac for applications, including five years of TCP/IP over X.25, we have found no problems in service or reliability. By the way, I don't work for any of the Bell franchises, nor do I own any of their stock. I just pay the phone bill. We have several hosts and gateways that connect LANs using X.25. I don't agree that X.25 is overly complex, or managing virtual circuits is a big problem. Our gateways and hosts usually do the work in software on board level products. We did some preliminary testing with SunLink using our hosts and one of their software implementations. Everything worked but the Sun stuff has some minor rough edges. For instance, the Sun would only allow one virtual circuit between two hosts even thought our side would allow one per user process. Imagine sharing your TELNET session with an FTP with each IP packet waiting it turn in in the X.25 queue. TELNET over X.25 is bad, but Sun made it worse. I hope they worked on that "kludge". Our tariff structure for communication services is almost the reverse to that in the U.S. Our leased lines cost us dearly, but out packet switching cost much less. If you look at our telco infrastructure, its easy to see why. Our population is spread across the country, and leased lines are nearly always new services. In the way of cost and performance, we have this kind of experience: Rental of 9600 bps X.25 modem with 20 virtual circuits is $390.00 U.S. per month. Traffic charges range from $35.00 to $300.00 U.S. per month per X.25 interface depending on usage and distance. The later is for about 50MB per month to a site 1500 miles away using the Datapac cost formula. On most of our X.25 legs, we get between 50 and 75 per cent of the of the 9600 bps. But this does depend a great deal on the HOST implementation of TCP/IP. In contrast, our 9600 bps HDH line gives us about 80 to 85 per cent of the line speed. Our 56 kbps line gives about 20 to 30 percent of the line speed, but we are not sure that we have hosts at either end to drive it faster. To send a 10 MB file across the country, it would cost about $75.00 U.S.. Thats about the same as it would cost to run the data on to a mag new tape and send it FEDEX. Some of our sites will be running 19.2 bps X.25 service which will double the monthly modem cost, and increase throughput but will be limited by the TCP/IP on the hosts. We expect that these 19.2 links will get us about 12000 bps or just about what we get out of our very expensive 56k bps line between our core gateway and the U. of Rochester. When our core gateway was replaced in Feb/88 with a Butterfly, the measured throughput went up slightly even though the HDH interface was replaced with an X.25 interface. I've tried to figure that one out. I will be the first to agree that our needs and network structure is different than Bellcore. However, I view X.25 packet switches as a low cost backbone that will allow us to operate until we have sufficient traffic levels to support leased lines. If there is a target needing a thumper, it sounds like the implementation of X.25 in Telenet will do. When it comes to bad implementations of TCP/IP, the cry is "burn them at the stake". There are good and bad X.25 implementations, and I recommend burning where it is due.
-----------[000032][next][prev][last][first]---------------------------------------------------- Date: 3 Jun 1988 1131-PDT (Friday) From: Charles Spurgeon <spurgeon@jessica.Stanford.EDU> To: tcp-ip@sri-nic.arpa Cc: Subject: Network books, TCP/IP and Ethernet
The following is an annotated list of books that I've found useful while
designing, building, and operating networks at Stanford University over the
last several years. The list reflects the experience of building networks
primarily based on TCP/IP protocols and Ethernet technology.
This message is long. I just set out to list some useful books with
complete access information, and it got longer and longer...
-Charles Spurgeon
(spurgeon@jessica.stanford.edu)
Networking and Communications Systems, Stanford University.
June 3, 1988
-- Introductory --
1. "Local Area Networks", by John E. McNamara, 1985, 165pps with index and
glossary. $29.00 Published by Digital Press, ISBN 0-932376-79-7. Digital
Press part number for ordering is EY-00051-DP. Digital Press phone is
1-800-343-8321.
This is a good general introduction to the concepts and technologies of
LANs. As stated in the preface:
" This book is intended for students, computer system managers,
telecommunications managers, and others who want to become more familiar
with local area networks. Since product offerings in this area are
constantly changing, a deliberate attempt has been made to emphasize the
general principles, operating characteristics, and problem areas of local
area network hardware, rather than cite specific product examples."
Of special note is the chapter on "Administrative considerations for large
networks" which is largely taken from David Clark's 1983 "M.I.T. Campus
Network Implementation Planning Document". This chapter mentions many of
the problems of supporting large campus area networks with special reference
to the issue of multiple protocol support on campus backbone networks.
-- Two books by Douglas Comer --
Douglas Comer has written two books of special interest to the networker.
His books are comprehensive and he has an excellent writing style, making
these the best books I've seen on the TCP/IP protocols.
2. "Internetworking With TCP/IP, Principles, Protocols, and Architecture". By
Douglas E. Comer. 1988, 382pps with index and glossary. Prentice-Hall,
Inc., New Jersey, ISBN 0-13-470154-2. $36.00. (Stanford Bookstore price.)
As stated in the preface:
"For professionals, the book provides a comprehensive introduction to TCP/IP
technology and the architecture of the Internet. Although it is not
intended to replace protocol standards, the book is a good starting point
for learning about internetworking because it gives a uniform overview that
emphasizes principles. Moreover, it gives the reader perspective that can
be extremely difficult to obtain from individual protocol documents."
"The book is organized into four main parts. Chapters 1 and 2 form an
introduction that provides an overview and discusses existing technologies.
In particular, Chapter 2 reviews physical network hardware. The intention
is to provide basic intuition about what is possible, not to spend
inordinate time on hardware details. Chapters 3-12 describe the TCP/IP
Internet from the viewpoint of a single host, showing the basic services
available and the protocols a host uses to access them. They cover the
basics of Internet addressing and routing as well as the notion of protocol
layering. Chapters 13-16 describe the architecture of the Internet when
viewed globally. They explore the core gateway system and the protocols
gateways use to exchange routing information. Finally, Chapters 17-19
discuss application level services available in the Internet. They present
the client-server model of interaction and give several examples of how one
can organize client and server software. The last section discusses
electronic mail and the domain name system, two topics that are extremely
popular."
I particularly like the real-world orientation of this book. For instance,
there is an appendix on "4.3 BSD UNIX Interface to Internet Protocols" that
describes Berkeley sockets and presents example client and server programs
for a network whois service. There's another appendix on "Hints And
Suggestions For Implementors" full of useful tips for network programmers.
And there's a nice appendix called "A Guide To RFCs" which explains the
Requests For Comments completely and with due regard for the early folklore
and development of the ARPAnet. A guide to the first one thousand RFCs,
extracted from RFC1000, is presented as well as electronic and snail mail
addresses for getting your own copies of the RFCs.
3. "Operating System Design - Volume II, Internetworking with Xinu". By
Douglas Comer. 1987, 5667pps with index. Published by Prentice-Hall, Inc.,
New Jersey, ISBN 0-13-637414-X. $39.33. (Stanford Bookstore price.)
As stated in the preface:
"Chapters 1-11 comprise a self-contained unit that covers the basics of
internet communication. Each of the eleven chapters explores one component
of internet protocol software, motivating and explaining how that component
fits into the overall system design. The unit starts with a detailed
examination of one network technology, the Ethernet, and moves on to
consider the internet concept, address resolution, internet datagrams,
routing, control messages, user datagrams, and datagram demultiplexing.
Later chapters build on the basic communication system, examining
client-server interaction, and remote file access, as well as a user
interface and commands that manipulate both local and remote files."
"Written as a continuation of 'Operating System Design - The XINU Approach'
(Comer [1984]), this text starts where the earlier one ends. The two
volumes were written to support a two-semester course in systems design that
encompasses operating systems and networks... ."
This book is based on the XINU operating system software which is available
from Purdue University as described in the book. XINU was written to give
students the experience of studying a UNIX-like operating system whose
source code was available for modification. Lots of software examples in
every chapter make this an especially useful text for aspiring network
programmers. It's also good resource for those just curious as to what
network software looks like and how it fits together.
-- Three books by William Stallings --
William Stallings has published a series of three books that can be helpful
in hacking one's way through the jargon laden jungles of network standards -
especially the OSI and IEEE standards.
4. "Volume 1. Handbook of Computer Communications Standards, The Open Systems
Interconnection (OSI) Model and OSI-Related Standards". By William Stallings.
1987, 322pps with index. Macmillan Publishing Co., NY, ISBN 0-02-948071-X.
$34.95.
The first volume sets the stage by explaining the OSI standards effort and
the organization of the OSI standards process. The OSI reference model is
then presented, and each layer is discussed in depth with lots of detail.
OSI is a moving target, and some of the material here is no doubt already
dated, but it's still a good explanation of the whole OSI world.
5. "Volume 2. Handbook of Computer Communications Standards, Local Network
Standards". By William Stallings. 1987, 244pps with index. Macmillan
Publishing Co,, NY, ISBN 0-02-948070-1. $34.95.
This book covers the IEEE 802 series of standards and the emerging FDDI
standard. The material described here makes it possible to decipher the
802.3 standard. After a brief introduction covering network topologies and
media, Stallings explains the standardization efforts, including the
structure of the standards committees and how the various standards agencies
interact.
Next the IEEE 802 standards structure is described, with the various
subsets explained. Chapter 4 describes the 802.3 standard including
variants such as 10BASE2. Also included is a brief description of the major
differences between 802.3 and DIX Ethernet. An appendix provides a short
introduction to the OSI reference model, so that you don't need volume 1 to
figure out volume 2.
6. "Volume 3. Handbook of Computer Communications Standards, Department of
Defense (DOD) Protocol Standards". By William Stallings, Paul Mockapetris,
Sue McLeod and Tony Michel, 1988, 206pps with index. Macmillan Publishing
Co., NY, ISBN 0-02-948072-8. $34.95.
This volume is a guide to the TCP/IP protocol suite. As stated in the
preface:
"...Volume 3, covers the five military standard protocols that have been
issued by the DOD. The book begins by introducing the four layer
communications architecture that is the framework within which these
standards fit. Following the introduction of this architecture, a chapter
is devoted to each of the standards."
"In contrast with the other books in this series, several of the chapters of
this book were written by contributors. Each contributor is intimately
familiar with the topic under discussion: biographies of the main author and
the contributing authors are found at the end of the book."
The chapters on IP and TCP appear to have been written by Stallings. The
chapter on FTP is by Tony Michel, the SMTP chapter by Paul Mockapetris and
the Telnet chapter by Sue McLeod. The chapters are good descriptions of the
various protocols. On the other hand, I prefer Douglas Comer's book, for
reasons given above.
-- Ethernet Standards --
The next several items deal with the various Ethernet standards in use
today.
7. "Ethernet Local Area Network Specification Version 2.0. November, 1982".
103pps, $32.00. DEC Part Number: AA-K759B-TK. Available from DEC-Direct by
calling 1-800-344-4825.
This is version 2 of the original ten megabit Ethernet specification. The
newer 802.3 standard supersedes the DEC-Intel-Xerox (DIX) spec listed here,
but most TCP/IP implementations are still based on this DIX specification.
Since this specification is not based on the OSI model it is relatively
jargon free and reads like something close to English, making it a much more
approachable document than the IEEE standards.
8. "Carrier Sense Multiple Access with Collision Detection, ANSI/IEEE Std
802.3, 1985, ISO/DIS 8802/3". ISBN 0-471-82749-5. Available from, IEEE
Service Center, 445 Hoes Lane, Piscataway, New Jersey 08854, or by calling
1-201-981-0060, or from technical bookstores (see below).
The new Ethernet specifications. Much has changed. Much stayed the same.
Vendors like to gloss over the differences (it's a lot easier than trying to
describe them!) and you're on your own trying to figure out how it all
works.
This standard was written to comply with the OSI model. As a result, it
contains much more jargon and can be much less understandable at first. An
explanatory guide like Stalling's volume 2 is a requirement to help the
newcomer to OSI make any sense of it all.
9. "Supplements to Carrier Sense Multiple Access with Collision Detection,
ANSI/IEEE Std 802.3a,b,c,and e-1988". ISBN 0-471-61153-0 Same access as
above.
A set of additions to the 1985 802.3 standard, including the thin Ethernet
standard (Type 10BASE2). Also included is the broadband standard (Type
10BROAD36) and a revision of section 9 of the 1985 standard on repeaters.
-- Ethernet hardware information --
None of the Ethernet standards docs are very useful when it comes to
actually building, testing, and operating an Ethernet. For that you need
information about what topologies are allowed, how Ethernet equipment is
configured, how to attach connectors and all the rest. While there isn't a
good general book available on Ethernet design and construction, the
following manual can help.
10. "LAN Cable and Accessories Installation Manual", January 1986, published
by Hewlett-Packard Co.. HP Part No. 5955-7680. $45.00. Order from H.P.
Direct at 1-800-538-8787.
This manual is somewhat dated and contains instructions for installing thick
cable transceivers that are obsolete, for instance. On the other hand, the
network configuration information is useful and the guidelines for
routing cables and grounding issues are informative. My major disagreement
with H.P.'s grounding instructions is that they allow metallic cable between
building frames if H.P.'s surge arrestors are installed. Given the
ease of using fiber optic repeaters, and the dangers inherent in metallic
network cables that travel between building frames, there seems little
excuse for not using fiber in these situations.
In any event, the manual really shines when it comes to complete
descriptions of thick cable and thin cable wire strippers and connector
crimpers. The H.P. manual has diagrams showing how to strip each kind of
cable and how to crimp on N connectors and BNC connectors.
There's a short section on verifying the cables you've built, and a longer
section on how to use a Time Domain Reflectometer to test networks. Another
useful section is the one on how to open up a crimp tool that has been
closed on something you didn't want to crimp (like your finger!). Don't
laugh - this section came in handy the other day when a student used a crimp
tool with a 75 ohm UHF crimp die in it to crimp a 50 ohm N connector. The
instructions in the H.P. manual allowed us to get the mauled N connector out
without dismantling the whole tool and ruining the precision adjustments.
-- Access --
Aside from various phone numbers listed above, the following book stores can
be of service:
Computer Literacy Bookshop, 2590 North First St., San Jose, CA 95131. Phone
408-435-1118 for mail orders. A good source for computer and electronics
books of all kinds. They carry the IEEE network standards, and can probably
supply most of the books listed above.
Jim Joyce's UNIX Bookstore, 47 Potomac St., San Francisco, CA 94117. Phone
415-626-7581 for mail orders. A handy resource for UNIX-related books of
all kinds, including the Douglas Comer books.
-----------[000033][next][prev][last][first]---------------------------------------------------- Date: Fri 3 Jun 88 14:53:09-EDT From: Dan Lynch <LYNCH@A.ISI.EDU> To: symchych@skl-crc.arpa Cc: thumper!karn@faline.bellcore.com, tcp-ip@sri-nic.arpa, lynch@A.ISI.EDU Subject: Re: Linking LAN's via Public X.25
Tim, Thanks for the explanation of how X.25 works in Canada. Different "administrations" charge differently for the "same services" for their local reasons. That's just the way the world works. Doesn't seem to be a way to optomize an architecture to account for all possible larcenies or charities. But, I was amazed to see you describe the low throughput on some of your slow links (anything under T1 is "slow" in my book). How can there be implementation sout there that cannot keep a 9600 baud link running full tilt??? Reason I ask is that your wording left me feeling that the host implementations were somehow anemic. I would hop that they just had poor data link drivers that can be fixed rapidly. Or are they mainly suffering from the lack of Van Jacobson's fixes? Dan -------
-----------[000034][next][prev][last][first]---------------------------------------------------- Date: 3 Jun 88 13:17:23 GMT From: doug@MSC2.TN.CORNELL.EDU.UUCP To: comp.protocols.tcp-ip Subject: Re: TCP/IP for PDP-11 running TSX (RT11)
Process Software in in Mass. has FTP for RT and TSX, TELNET for RT, and I believe they are working on TELNET for TSX. Their product is NOT a general TCP/IP implementation, but a series of applications. The FTP is a very basic vanilla FTP, but the TSX version uses DEC command-line syntax instead of interactive Unix-style syntax. The result of this is that they open and close the connection for EACH file that gets transferred. Also missing is wildcarding (MPUT/MGET), CWD, and DIR functionality. I have written to them requesting that they add the above. It is, however, a basic implementation that works. They can be reached at: Process Software 35 Montague Road PO Box 746 Amherst, MA 01004 (413) 549-6994 - Doug Neuhauser, Materials Science Center, Cornell University (doug@msc2.tn.cornell.edu)
-----------[000035][next][prev][last][first]---------------------------------------------------- Date: 3 Jun 88 13:32:04 GMT From: doug@ICASE.ARPA.UUCP To: comp.protocols.tcp-ip Subject: Sun File server
My apologies if this is posted to the wrong discussion group. We have just upgraded our server from a 3/180 to a 3/280, and have seen a DECREASE in performance. We run Sun OS 3.5. The number of diskless clients in both cases is the same. The e-net collision rate is much higher with the new server, which may account for some of the decrease. But I just received my copy of the May Sun STB, which has an article describing how the cache works on a Sun 3/200 series machine. On page 826, there is a statement to the effect that if the cache hit rate is effectively zero, then performance of a 3/280 system will be less than a 3/280. As a server, handling lots of random client requests, I would think that the cache hit rate would be very low. Has anyone observed similar phenomenon? I will summarize to the net. Doug Peterson Systems Manager ICASE Mail Stop 132C NASA Langley Research Center Hampton, VA 23665-5225 (804) 865-4090 ----- End Forwarded Message -----
-----------[000036][next][prev][last][first]---------------------------------------------------- Date: 3 Jun 88 14:40:49 GMT From: jon@CS.UCL.AC.UK (Jon Crowcroft) To: comp.protocols.tcp-ip Subject: Re: Linking LAN's via Public X.25
>Perhaps another view of IP over X.25 might help. While the original >question was asked about Sun X.25, there are a number of networks within the >ARPA/Internet that use IP over X.25. another e.g. of IP over X.25 is the UK Academic link to the US, which has run over IPSS for some years, as leased lines were rather expensive for the amount of traffic we used to have, and since the SATNET was mainly reserved for research use. A lot of interesting work was done on accounting and access control so that we could forward bills for the IPSS usage to the UK source of any IP packets on a sensible basis. Useful reading... %A R. H. Cole %T User Experience and Evaluation of International X.25 Services %J Proc. Telecoms Today Conf. %I Online %C London %D March 1984 %P 107-118 %K X.25 performance jon
-----------[000037][next][prev][last][first]---------------------------------------------------- Date: 3 Jun 88 14:49:46 GMT From: virchaux@CLSEPF51.BITNET (J.Virchaux EPFL-SIG) To: comp.protocols.tcp-ip Subject: Query : TCP/IP on TSX+
I'm looking for an implementation of TCP/IP on TSX+.
We should like to FTP files from a PDP running TSX+ operating system
to a VAX through an Ethernet link. Is such software (and hardware if
not DEQNA) available ?
Please, do not answer to the list as I'm not a member. Reply to :
VIRCHAUX@CLSEPF51.BITNET
Virchaux@Eldp.Epfl.CH (Arpa, Cs.Net, X.400)
PSI%022846911008::ELDP::VIRCHAUX (PSI-Mail)
-----------[000038][next][prev][last][first]---------------------------------------------------- Date: Fri, 03 Jun 88 15:40:49 +0100 From: Jon Crowcroft <jon@Cs.Ucl.AC.UK> To: tcp-ip@sri-nic.arpa Subject: Re: Linking LAN's via Public X.25
>Perhaps another view of IP over X.25 might help. While the original >question was asked about Sun X.25, there are a number of networks within the >ARPA/Internet that use IP over X.25. another e.g. of IP over X.25 is the UK Academic link to the US, which has run over IPSS for some years, as leased lines were rather expensive for the amount of traffic we used to have, and since the SATNET was mainly reserved for research use. A lot of interesting work was done on accounting and access control so that we could forward bills for the IPSS usage to the UK source of any IP packets on a sensible basis. Useful reading... %A R. H. Cole %T User Experience and Evaluation of International X.25 Services %J Proc. Telecoms Today Conf. %I Online %C London %D March 1984 %P 107-118 %K X.25 performance jon
-----------[000039][next][prev][last][first]---------------------------------------------------- Date: 3 Jun 88 18:31:00 GMT From: spurgeon@JESSICA.STANFORD.EDU (Charles Spurgeon) To: comp.protocols.tcp-ip Subject: Network books, TCP/IP and Ethernet
The following is an annotated list of books that I've found useful while
designing, building, and operating networks at Stanford University over the
last several years. The list reflects the experience of building networks
primarily based on TCP/IP protocols and Ethernet technology.
This message is long. I just set out to list some useful books with
complete access information, and it got longer and longer...
-Charles Spurgeon
(spurgeon@jessica.stanford.edu)
Networking and Communications Systems, Stanford University.
June 3, 1988
-- Introductory --
1. "Local Area Networks", by John E. McNamara, 1985, 165pps with index and
glossary. $29.00 Published by Digital Press, ISBN 0-932376-79-7. Digital
Press part number for ordering is EY-00051-DP. Digital Press phone is
1-800-343-8321.
This is a good general introduction to the concepts and technologies of
LANs. As stated in the preface:
" This book is intended for students, computer system managers,
telecommunications managers, and others who want to become more familiar
with local area networks. Since product offerings in this area are
constantly changing, a deliberate attempt has been made to emphasize the
general principles, operating characteristics, and problem areas of local
area network hardware, rather than cite specific product examples."
Of special note is the chapter on "Administrative considerations for large
networks" which is largely taken from David Clark's 1983 "M.I.T. Campus
Network Implementation Planning Document". This chapter mentions many of
the problems of supporting large campus area networks with special reference
to the issue of multiple protocol support on campus backbone networks.
-- Two books by Douglas Comer --
Douglas Comer has written two books of special interest to the networker.
His books are comprehensive and he has an excellent writing style, making
these the best books I've seen on the TCP/IP protocols.
2. "Internetworking With TCP/IP, Principles, Protocols, and Architecture". By
Douglas E. Comer. 1988, 382pps with index and glossary. Prentice-Hall,
Inc., New Jersey, ISBN 0-13-470154-2. $36.00. (Stanford Bookstore price.)
As stated in the preface:
"For professionals, the book provides a comprehensive introduction to TCP/IP
technology and the architecture of the Internet. Although it is not
intended to replace protocol standards, the book is a good starting point
for learning about internetworking because it gives a uniform overview that
emphasizes principles. Moreover, it gives the reader perspective that can
be extremely difficult to obtain from individual protocol documents."
"The book is organized into four main parts. Chapters 1 and 2 form an
introduction that provides an overview and discusses existing technologies.
In particular, Chapter 2 reviews physical network hardware. The intention
is to provide basic intuition about what is possible, not to spend
inordinate time on hardware details. Chapters 3-12 describe the TCP/IP
Internet from the viewpoint of a single host, showing the basic services
available and the protocols a host uses to access them. They cover the
basics of Internet addressing and routing as well as the notion of protocol
layering. Chapters 13-16 describe the architecture of the Internet when
viewed globally. They explore the core gateway system and the protocols
gateways use to exchange routing information. Finally, Chapters 17-19
discuss application level services available in the Internet. They present
the client-server model of interaction and give several examples of how one
can organize client and server software. The last section discusses
electronic mail and the domain name system, two topics that are extremely
popular."
I particularly like the real-world orientation of this book. For instance,
there is an appendix on "4.3 BSD UNIX Interface to Internet Protocols" that
describes Berkeley sockets and presents example client and server programs
for a network whois service. There's another appendix on "Hints And
Suggestions For Implementors" full of useful tips for network programmers.
And there's a nice appendix called "A Guide To RFCs" which explains the
Requests For Comments completely and with due regard for the early folklore
and development of the ARPAnet. A guide to the first one thousand RFCs,
extracted from RFC1000, is presented as well as electronic and snail mail
addresses for getting your own copies of the RFCs.
3. "Operating System Design - Volume II, Internetworking with Xinu". By
Douglas Comer. 1987, 5667pps with index. Published by Prentice-Hall, Inc.,
New Jersey, ISBN 0-13-637414-X. $39.33. (Stanford Bookstore price.)
As stated in the preface:
"Chapters 1-11 comprise a self-contained unit that covers the basics of
internet communication. Each of the eleven chapters explores one component
of internet protocol software, motivating and explaining how that component
fits into the overall system design. The unit starts with a detailed
examination of one network technology, the Ethernet, and moves on to
consider the internet concept, address resolution, internet datagrams,
routing, control messages, user datagrams, and datagram demultiplexing.
Later chapters build on the basic communication system, examining
client-server interaction, and remote file access, as well as a user
interface and commands that manipulate both local and remote files."
"Written as a continuation of 'Operating System Design - The XINU Approach'
(Comer [1984]), this text starts where the earlier one ends. The two
volumes were written to support a two-semester course in systems design that
encompasses operating systems and networks... ."
This book is based on the XINU operating system software which is available
from Purdue University as described in the book. XINU was written to give
students the experience of studying a UNIX-like operating system whose
source code was available for modification. Lots of software examples in
every chapter make this an especially useful text for aspiring network
programmers. It's also good resource for those just curious as to what
network software looks like and how it fits together.
-- Three books by William Stallings --
William Stallings has published a series of three books that can be helpful
in hacking one's way through the jargon laden jungles of network standards -
especially the OSI and IEEE standards.
4. "Volume 1. Handbook of Computer Communications Standards, The Open Systems
Interconnection (OSI) Model and OSI-Related Standards". By William Stallings.
1987, 322pps with index. Macmillan Publishing Co., NY, ISBN 0-02-948071-X.
$34.95.
The first volume sets the stage by explaining the OSI standards effort and
the organization of the OSI standards process. The OSI reference model is
then presented, and each layer is discussed in depth with lots of detail.
OSI is a moving target, and some of the material here is no doubt already
dated, but it's still a good explanation of the whole OSI world.
5. "Volume 2. Handbook of Computer Communications Standards, Local Network
Standards". By William Stallings. 1987, 244pps with index. Macmillan
Publishing Co,, NY, ISBN 0-02-948070-1. $34.95.
This book covers the IEEE 802 series of standards and the emerging FDDI
standard. The material described here makes it possible to decipher the
802.3 standard. After a brief introduction covering network topologies and
media, Stallings explains the standardization efforts, including the
structure of the standards committees and how the various standards agencies
interact.
Next the IEEE 802 standards structure is described, with the various
subsets explained. Chapter 4 describes the 802.3 standard including
variants such as 10BASE2. Also included is a brief description of the major
differences between 802.3 and DIX Ethernet. An appendix provides a short
introduction to the OSI reference model, so that you don't need volume 1 to
figure out volume 2.
6. "Volume 3. Handbook of Computer Communications Standards, Department of
Defense (DOD) Protocol Standards". By William Stallings, Paul Mockapetris,
Sue McLeod and Tony Michel, 1988, 206pps with index. Macmillan Publishing
Co., NY, ISBN 0-02-948072-8. $34.95.
This volume is a guide to the TCP/IP protocol suite. As stated in the
preface:
"...Volume 3, covers the five military standard protocols that have been
issued by the DOD. The book begins by introducing the four layer
communications architecture that is the framework within which these
standards fit. Following the introduction of this architecture, a chapter
is devoted to each of the standards."
"In contrast with the other books in this series, several of the chapters of
this book were written by contributors. Each contributor is intimately
familiar with the topic under discussion: biographies of the main author and
the contributing authors are found at the end of the book."
The chapters on IP and TCP appear to have been written by Stallings. The
chapter on FTP is by Tony Michel, the SMTP chapter by Paul Mockapetris and
the Telnet chapter by Sue McLeod. The chapters are good descriptions of the
various protocols. On the other hand, I prefer Douglas Comer's book, for
reasons given above.
-- Ethernet Standards --
The next several items deal with the various Ethernet standards in use
today.
7. "Ethernet Local Area Network Specification Version 2.0. November, 1982".
103pps, $32.00. DEC Part Number: AA-K759B-TK. Available from DEC-Direct by
calling 1-800-344-4825.
This is version 2 of the original ten megabit Ethernet specification. The
newer 802.3 standard supersedes the DEC-Intel-Xerox (DIX) spec listed here,
but most TCP/IP implementations are still based on this DIX specification.
Since this specification is not based on the OSI model it is relatively
jargon free and reads like something close to English, making it a much more
approachable document than the IEEE standards.
8. "Carrier Sense Multiple Access with Collision Detection, ANSI/IEEE Std
802.3, 1985, ISO/DIS 8802/3". ISBN 0-471-82749-5. Available from, IEEE
Service Center, 445 Hoes Lane, Piscataway, New Jersey 08854, or by calling
1-201-981-0060, or from technical bookstores (see below).
The new Ethernet specifications. Much has changed. Much stayed the same.
Vendors like to gloss over the differences (it's a lot easier than trying to
describe them!) and you're on your own trying to figure out how it all
works.
This standard was written to comply with the OSI model. As a result, it
contains much more jargon and can be much less understandable at first. An
explanatory guide like Stalling's volume 2 is a requirement to help the
newcomer to OSI make any sense of it all.
9. "Supplements to Carrier Sense Multiple Access with Collision Detection,
ANSI/IEEE Std 802.3a,b,c,and e-1988". ISBN 0-471-61153-0 Same access as
above.
A set of additions to the 1985 802.3 standard, including the thin Ethernet
standard (Type 10BASE2). Also included is the broadband standard (Type
10BROAD36) and a revision of section 9 of the 1985 standard on repeaters.
-- Ethernet hardware information --
None of the Ethernet standards docs are very useful when it comes to
actually building, testing, and operating an Ethernet. For that you need
information about what topologies are allowed, how Ethernet equipment is
configured, how to attach connectors and all the rest. While there isn't a
good general book available on Ethernet design and construction, the
following manual can help.
10. "LAN Cable and Accessories Installation Manual", January 1986, published
by Hewlett-Packard Co.. HP Part No. 5955-7680. $45.00. Order from H.P.
Direct at 1-800-538-8787.
This manual is somewhat dated and contains instructions for installing thick
cable transceivers that are obsolete, for instance. On the other hand, the
network configuration information is useful and the guidelines for
routing cables and grounding issues are informative. My major disagreement
with H.P.'s grounding instructions is that they allow metallic cable between
building frames if H.P.'s surge arrestors are installed. Given the
ease of using fiber optic repeaters, and the dangers inherent in metallic
network cables that travel between building frames, there seems little
excuse for not using fiber in these situations.
In any event, the manual really shines when it comes to complete
descriptions of thick cable and thin cable wire strippers and connector
crimpers. The H.P. manual has diagrams showing how to strip each kind of
cable and how to crimp on N connectors and BNC connectors.
There's a short section on verifying the cables you've built, and a longer
section on how to use a Time Domain Reflectometer to test networks. Another
useful section is the one on how to open up a crimp tool that has been
closed on something you didn't want to crimp (like your finger!). Don't
laugh - this section came in handy the other day when a student used a crimp
tool with a 75 ohm UHF crimp die in it to crimp a 50 ohm N connector. The
instructions in the H.P. manual allowed us to get the mauled N connector out
without dismantling the whole tool and ruining the precision adjustments.
-- Access --
Aside from various phone numbers listed above, the following book stores can
be of service:
Computer Literacy Bookshop, 2590 North First St., San Jose, CA 95131. Phone
408-435-1118 for mail orders. A good source for computer and electronics
books of all kinds. They carry the IEEE network standards, and can probably
supply most of the books listed above.
Jim Joyce's UNIX Bookstore, 47 Potomac St., San Francisco, CA 94117. Phone
415-626-7581 for mail orders. A handy resource for UNIX-related books of
all kinds, including the Douglas Comer books.
-----------[000040][next][prev][last][first]---------------------------------------------------- Date: Sat, 4 Jun 88 00:30 EST From: PMDF Mail Server <Postmaster@GRAD.CIS.TEMPLE.EDU> To: TCP-IP@SRI-NIC.ARPA Subject: Undeliverable mail
Your message could not be delivered to:
STAFFORD
Your message has been enqueued and undeliverable for 6 days.
The mail system will continue to try to deliver your message
for an additional 6 days.
The beginning of your message follows:
-----------[000041][next][prev][last][first]---------------------------------------------------- Date: 3 Jun 88 19:54:59 GMT From: symchych@SKL-CRC.ARPA (Tim Symchych) To: comp.protocols.tcp-ip Subject: Re: Linking LAN's via Public X.25
Dan: Yes, there are still versions of IP around in hosts that do not perform well. Regardless of some of the fine work that has been done in end-to-end performance, we still use what comes off the shelf, and if the vendors don't put it out in the product, then we don't have it. Most of our sites have no interest in "patch and run" systems for their users. Many people on this mailing list have covered this problem, including the problems of mixing speeds on segments of the path that traverse ethernet, leased lines and non-IP packet switched nets. Except for ethernet LANS, all our links between hosts use combinations of different link types. I guess that in our case, X.25 is the least of our problems. Something I forgot to mention is that in our PDN connections at 9600, we use 256 byte packets with a window size of up to 7 packets. I also received some hints on the 56 kbps X.25 line to our Butterfly from Dave Capshaw at Lockheed. Seems that some tuning may be possible between the PSN and the Butterfly. regards tim
-----------[000042][next][prev][last][first]---------------------------------------------------- Date: 3 Jun 88 23:33:08 GMT From: jdc@naucse.UUCP (John Campbell) To: comp.misc,comp.protocols.tcp-ip,comp.os.vms Subject: cmu tcp-ip
I know that CMU's TCP/IP has been out for a while. I would like to hear from anyone who has used this implementation. In particular, I am interested in sites that have used TCP/IP terminal servers with CMU TCP/IP on VMS. I would like to say that this is a cost-effective way to get out of LAT and away from DECServers. Any comments? Please mail directly to me. Some of these groups I don't follow. I will summarize responses if there is any interest. Also--if you know other VMS TCP/IP vendors and cost/quality information send it along as well. I'll include anything I get that pretains to the above in my summary. Thanks. -- John Campbell ...!arizona!naucse!jdc unix? Sure send me a dozen, all different colors.
-----------[000043][next][prev][last][first]---------------------------------------------------- Date: Sat, 4 Jun 88 07:01:42 CDT From: lhl@cs.wisc.edu (L.H. Landweber) To: tcp-ip@sri-nic.arpa Subject: SIGCOMM '88 Program
All,
Enclosed is the advance program and registration form for the 1988 ACM
SIGCOMM symposium. SIGCOMM is THE ACM symposium on computer
communications. This year we have a very strong technical program,
consisting of three days of conference papers, plus one tutorial day.
For more information about hotels and on-campus accommodations, please
contact Stanford University directly (415/723-3126).
Please note that VERY limited on-campus accommodations are available.
To expedite the registration process, you can send print outs of the
attached forms with payment.
Sincerely,
JJ Garcia-Luna
General Chair, SIGCOMM 88
-----------------------------------------------------------------------
ACM SIGCOMM 88 SYMPOSIUM
ADVANCE PROGRAM
Communications Architectures and Protocols
August 16-19, 1988
Stanford University, Stanford, California
SYMPOSIUM
August 17-19, 1988
August 17, 1988
9:00 - 10:00
Session 1: Keynote Session
General Chair: J.J. Garcia-Luna-Aceves, SRI International, USA
Program Chair: L. Landweber, University of Wisconsin, USA
Student Paper Award: J.J. Garcia-Luna-Aceves, SRI International, USA
Keynote Address: Donald Nielson, SRI International, USA
10:30 - 12:00
Session 2: Local/Metropolitan Area Internets
Chair: D. Anderson, Unviversity of California, Berkeley, USA
Topological Analysis of Local-Area Internetworks
(G. Trewitt, Stanford University) --- Student Paper
Dynamic Resource Allocation in a Metropolitan Area Network
(K. Maly, C. Overstreet, Old Dominion Univ.;
X. Qui, China State Shipbuilding Corporation, Peoples Republic
of China; and D. Tang, Chengdu University of Science &
Technology, Peoples Republic of China)
Optical Interconnection Using ShuffleNet Multihop Networks in
Multi-Connected Ring Topologies
(M.J. Karol, AT&T Bell Laboratories, USA)
1:15 - 2:45
Session 3: Routing
Chair: L. Chapin, Data General Corporation, USA
Landmark Routing: Distributed Name-Based Routing for Very
Large Networks
(P.F. Tsuchiya, Mitre, USA)
Pitfalls of a Certain Class of Distributed Routing Algorithms
(R. Perlman and G. Varghese, DEC, USA)
Multicast Routing in Internetworks and Extended LANs
(S.E. Deering, Stanford University, USA) --- Student Paper
3:15 - 5:15
Session 4: Transport Level and Operating System Issues
Chair: S. Lam, University of Texas at Austin, USA
Design of an x-Kernel
(N. Hutchinson and L. Peterson, Univ. of Arizona, USA)
Exploiting Recursion to Simplify RPC Communication Architectures
(D.R. Cheriton, Stanford University, USA)
Service Specification and Protocol Construction for the Transport Layer
(S.L. Murphy and A.U. Shankar, Univ. of Maryland at College Park, USA)
A Network Management Language for OSI Networks
(U. Warrier, A. Relan, Unisys Corporation, USA;
O. Berry, IBM Science and Technology, Israel;
and J. Bannister, The Aerospace Corporation, USA)
7:00 pm - on
Banquet
August 18, 1988
8:30 - 10:00
Session 5: Lessons of the Internet
Chair: J. Mogul, Digital Equipment Corporation, USA
Some thoughts on the DARPA Internet Architecture
(David Clark, MIT, USA)
The Fuzzball
(D.L. Mills, University of Delaware, USA)
Development of the Domain Name System
(Paul Mockapetris, USC Information Sciences Institute, USA)
10:30 - 12:00
Session 6: Local Area Network Architecture
Chair: R. Cheung, Hewlett-Packard, USA
Optimizing Bulk Data Transfer Performance: The Packet Train Model
(C. Song and L.H. Landweber, University of Wisconsin, USA)
--- Student paper
A Mesh/Token Ring Hybrid-Architecture LAN
(C. Kang, The American University, USA;
and J. Herzog, Oregon State University, USA)
Tree LANs with Collision Avoidance: Protocol, Switch Architecture,
and Simulated Performance
(T. Suda, S. Morris, and T. Nguyen,
University of California, Irvine, USA)
1:15 - 2:45
Session 7: Very High Speed Networking
Chair: D. Farber, University of Pennsylvania, USA
An Analysis of Memnet - An Experiment in High Speed Memory Mapped
Local Networking (G. Delp, A. Sethi, University of Delaware, USA;
and D. Farber, University of Pennsylvania, USA)
--- Student paper
The VMP Network Adapter Board (NAB): High-Performance Network
Communication for Multiprocessors
(H. Kanakia and D. Cheriton, Stanford University, USA) --- Student paper
Fast Circuit Switching in Fiber Optic Networks
(I. Chlamtac, A. Ganz, and G. Karmi, University of Massachusetts, USA)
3:15 - 5:15
Session 8. Measurement and Management
Chair: V. Cerf, Corporation for National Research Initiatives, USA
A Pseudo-Machine for Packet Monitoring and Statistics
(R.T. Braden, USC Information Sciences Institute, USA)
Knowledge-Based Monitoring and Control: An Approach to
Understanding the Behavior of TCP/IP Network Protocols
(B.L. Hitson, Stanford University, USA) --- Student paper
Measured Capacity of an Ethernet
(D.R. Boggs, J.C. Mogul, and C.A. Kent, DEC, USA)
Distributed Testing and Measurement across the Atlantic Packet
Satellite Network (SATNET)
(K. Seo, BBN, USA; J. Crowcroft, UCL, England;
P. Spilling, Norwegian Telecommunications Administration, Norway;
J. Laws, Royal Signals and Radar Establishment, Englanand;
and C. Topolcic, BBN, USA)
5:30 - 7:00
Reception
August 19, 1988
8:30 - 10:00
Session 9: Communication Protocol Design and Testing
Chair: D. Mills, University of Delaware, USA
A Multicast Transport Protocol
(J. Crowcroft and K. Paliwoda, University College London, England)
Experience with Test Generation for Real Protocols
(D. Sidhu and T. Leung, Iowa State University, USA)
Performance Models for Noahnet
(G.M. Parulkar, A.S. Sethi, D.J. Farber, University of Pennsylvania, USA)
10:30 - 12:00
Session 10: Broadcast Issues
Chair: D. Sidhu, Iowa State University, USA
A High Performance Broadcast File Transfer Protocol
(J.S.J. Daka, A.G. Waters, University of Essex, England)
Specification and Verification of Collision-Free Broadcast Networks
(P. Jain and S.S. Lam, University of Texas, Austin, USA)-- Student Paper
Delivery and Discrimination: The Seine Protocol
(M. Gouda, University of Texas at Austin, USA;
N. Maxemchuk, U. Mukherji, and K. Sabnani,
AT&T Bell Laboratories, USA)
1:15 - 2:45
Session 11: Congestion and Topology Control
Chair: J.J. Garcia-Luna-Aceves, SRI International
An Explicit Binary Feedback Scheme for Congestion Avoidance in
Computer Networks with a Connectionless Network Layer
(K.K. Ramakrishnan and R. Jain, DEC, USA)
Congestion Avoidance and Control
(Van Jacobson, Lawrence Berkeley Laboratory, USA)
A Protocol to Maintain a Minimum Spanning Tree in a Dynamic Topology
(C. Cheng, I. Cimet, P. Kumar, Northwestern Univ., USA)
3:00 - 5:00
Session 12: Panel on Internet Engineering
Chair: P. Gross, Mitre, USA
Panelsists to be announced
--------------------------------------------------------------------------
TUTORIALS
August 16, 1988
9:00 am - 5:00 pm
1. INTEGRATED SERVICES DATA NETWORKS:
NARROWBAND AND BROADBAND
(Mario Gerla, UCLA)
Abstract
ISDN is one of the newest " buzzwords " in the communications arena.
The concept is extremely appealing: by integrating various services (
voice, data, video etc.) in a common network we will be able to achieve
lower operating costs, higher efficiency, better
availability/maintainability and higher flexibility in the introduction
of new services.This concept is now becoming a reality, and both users
and service providers are taking into account the potential of ISDN's
in formulating their plans.
This seminar will review the evolution of the ISDN concept during the
past few years,will discuss the standard recommendations, will compare
implemen- tation alernatives and finally will report on recent field
trials. In organizing this seminar , the attempt was to maintain a
good balance between design principles, standard recommendations and
actual network implementations.
Outline
- Why integrated services
- Narrowband and Broadband ISDN's
- Standard recommendations
- ISDN backbone implementation alternatives
( Packet/Circuit/Hybrid switching)
- ISDN routing and flow control
- Service integration in MAN's and LAN's
- Field trials
- Future trends
Biography
Professor Mario Gerla received the PhD degree in engineering from the
University of California, Los Angeles (UCLA), in 1973. From 1973 to
1976, he was Network Planning Manager at Network Analysis Corporation.
>From 1976 to 1977, he was with Tran Telecommunications, Los Angeles,
where he participated in the development of integrated packet and
circuit networks. In 1977, he joined UCLA and is now a Professor in
the Department of Computer Science. His research interests include the
design and control of distributed computer communications systems and
networks, and the development of high-speed local area networks.
2. MULTI-HOP TOPOLOGIES, BRIDGES AND ROUTERS
(Radia Perlman, DEC)
Abstract
A Local Area Network (LAN) allows direct communication between any
stations directly connected to the LAN. Route computation and
forwarding nodes are not necessary. However, technology and
performance constrains the topology, distance, and number of stations
of a single LAN. Thus a network usually needs to grow beyond the
limits of a single LAN. One method of interconnecting LANs is through
"Bridges". Two different schemes for interconnecting LANs are being
standardized by two different subcommittees of the IEEE 802 committee,
which is standardizing LANs. These two schemes are "spanning
tree/transparent" bridges, and "source routing" bridges. Another
method of creating a network with multiple links is through "routers".
These too are being standardized by various committees. "Routers"
perform the "Network Layer Protocol" as defined by the ISO reference
model.
This tutorial will briefly review the ISO reference model. It will
explain the two bridge schemes, and contrast their functionality and
performance. It will explain the functionality of the Network Layer,
and explain design alternatives for meeting this functionality. The
emphasis will be placed on the design of a "connectionless" style of
Network Layer. No background other than intellectual curiosity is
required. Emphasis is on protocol concepts rather than specifics of
the schemes, or mathematical analysis.
Outline
o ISO Reference Model Review (20 minutes)
o LAN review -- CSMA/CD, token ring, token bus (15 minutes)
o Bridges -- Spanning Tree, Source Routing, Comparisons (1 1/2
hours)
o Network Layer functionality -- connection oriented vs
connectionless, routing, fragmentation and reassembly,
autoconfigurability, addressing (45 minutes)
o Routing Algorithms -- "Distance Vector" vs "Link State" (2
hours)
o Depending on time and interest, remaining time can be spent
exploring the design implications of:
- interoperability of spanning tree and source routing
bridges
- Network Layer autoconfigurability
- Design implications of hierarchical networks; subnetwork
partition problem, subnetwork autonomy
Biography
Radia Perlman is a consulting engineer at Digital Equipment
Corporation. She designed the spanning tree algorithm used by
Digital's bridges and adopted for use by both bridge standards
(transparent bridges and source routing bridges). She also was
responsible for the design and specification of the Network Layer in
Digital's Network Architecture, aspects of which have been adopted by
ISO for use in the standard connectionless Network Layer.
She has taught as adjunct faculty at the graduate schools of Wang
Institute and University of Lowell, and at the Wang Summer Institute.
She received the B.S. and M.S. degrees in mathematics at MIT, and is
currently pursuing a Ph.D. degree in Computer Science at MIT.
-----------------------------------------------------------------------
TUTORIAL AND SYMPOSIUM REGISTRATION
Please check applicable fees:
ADVANCE REGULAR
(before 7/25/88)
TUTORIAL 1:
____ ACM members $200 $250
____ Non-members 250 300
____ Full-time students** 100 150
TUTORIAL 2:
____ ACM members $200 $250
____ Non-members 250 300
____ Full-time students** 100 150
SYMPOSIUM*:
____ ACM members $200 $250
____ Non-members 250 300
____ Full-time students** 100 150
* Reception and banquet fees will be included in the recidence hall
registration package.
** Student registration must be accompanied by a copy of valid full-time
student ID. Must be ACM member.
TOTAL PAYMENT MUST BE INCLUDED IN US$. $____________.
Advance registration payment must be received by July 25, 1988. After
that date, please wait to register at the Symposium itself. Make
checks payable in US$ to ACM SIGCOMM. There will be a $10.00 Surcharge
on foreign banks.
Please return tutorial and symposium registration form and complete
payment to: Dr. J.J. Garcia-Luna-Aceves, SRI International, 333
Ravenswood Ave., Menlo Park, CA 94025, USA; tel: (415) 859-5647;
e-mail: garcia@sri.com.
----------------------------------------------------------------------------
APPLICATION FOR RESIDENCE HALLS
Room and meal payments are due upon arrival. DO NOT PAY IN ADVANCE.
All payments must be in $US dollars, and made in cash, traveler's
checks, or personal checks from a U.S. Bank made payable to
Stanford University.
A VERY LIMITED number of rooms in Stanford University are available on
a first-come, first-served basis. Complete this form and return it, no
later than July 25, 1988, to Dr. J.J. Garcia-Luna-Aceves, SRI International,
Menlo Park, CA 94035; Tel: (415) 859-5647; e-mail: garcia@sri.com.
RATES:
PLAN I - Room for 4 nights (Mon., Tue., Wed., and Thurs.) and 10 meals
from Tue. breakfast thru Fri. lunch (omitting Wed. Dinner).
Single room - $102.00, shared room - $76.00
meals 95.00 meals - $95.50
------- -------
$197.50 $171.50 per person
PLAN II - Room for 3 nights (Tues., Wed., Thurs.) and 7 meals
(breakfast and lunch on Wed., Thurs., Fri., and dinner on Thursday.
Single room - $76.50, shared room - $57.00
meals 65.00 meals - $65.50
------- -------
$141.50 $122.50 per person
EXTRA NIGHT'S STAY: single room - $25.50, shared room - $19.00 per person.
CHILDREN: 10 yrs. old and under are charged half rate for housing and
meal package.
RESIDENCE HALL REQUIREMENTS:
Name: ____________________________________________________________
Last First Middle
Address: _________________________________________________________
_________________________________________________________
_________________________________________________________
____ Plan I, ____ Plan II
____ Single, ____ Double
____ Female, ____ Male
____ Smoking, ____ Nonsmoking
Preferred rommate: ________________________________________________
Date and time of arrival: _________________________________________
Date and time of departure: _______________________________________
_________________________________________________________________________
-----------[000044][next][prev][last][first]---------------------------------------------------- Date: Sat, 4 Jun 88 15:12 From: John Laws (on UK.MOD.RSRE) <LAWS%rsre.mod.uk@relay.MOD.UK> To: tcp-ip <@relay.MOD.UK:tcp-ip@sri-nic.arpa> Cc: Subject: Re: Linking LAN's via Public X.25
>Perhaps another view of IP over X.25 might help. While the original >question was asked about Sun X.25, there are a number of networks within the >ARPA/Internet that use IP over X.25. Yet another view. The RSRE Internet Lab connects to two other European Internet sites (one in Holland and one in Germany) and others internal to the UK running IP over X.25. Quality of service is good and at current traffic levels is much cheaper than international/national leased circuits. The software has been developed to pay attention to the fact that real money is being spent e.g. virtual circuits close if IP traffic stops, and of course accounting and access control are well developed. If national X.25 provision by US carriers is seen as less than adequate, by US users, maybe its because they (the carriers) do not see it as a viable commercial market to make a big investment in given the existing 'free' networks like Arpanet, Milnet, NSFnet etc. YES I DO KNOW that they are not really free - that Government, Academic institutions and companies make payments. But in many cases the users at the keyboard are unaware and uncaring of the costs (judged by many of the remarks in this forum some months ago). John
-----------[000045][next][prev][last][first]---------------------------------------------------- Date: 4 Jun 88 13:48:35 GMT From: guru@flora.wustl.EDU (Gurudatta Parulkar) To: comp.protocols.tcp-ip Subject: A couple of questions
Has anybody successfully installed Van Jacobson's tcp/ip on a binary only sun 3/50 ? Please let me know. I need some help. Are there any good references on operating large campus networks which talk about administrative as well as technical issues ? I have accumulated a lot of info from this and other bboards, but want to check if there are any comprehensive papers on the subject. Thanks in advance. -guru Dr. Guru Parulkar Asst Professor guru@flora.wustl.edu Dept of Computer Science parulkar@udel.edu Washington University wucs1!guru@uunet.uu.net St. Louis MO 63130 (314) 889-4621
-----------[000046][next][prev][last][first]---------------------------------------------------- Date: 4 Jun 88 13:48:35 GMT From: @hplabs.hp.com (Gurudatta Parulkar) To: tcp-ip@sri-nic.arpa Subject: A couple of questions
Has anybody successfully installed Van Jacobson's tcp/ip on a binary only sun 3/50 ? Please let me know. I need some help. Are there any good references on operating large campus networks which talk about administrative as well as technical issues ? I have accumulated a lot of info from this and other bboards, but want to check if there are any comprehensive papers on the subject. Thanks in advance. -guru Dr. Guru Parulkar Asst Professor guru@Dept of Computer Science parulkar@udel.edu Washington University wucs1!guru@uunet.uu.net St. Louis MO 63130 (314) 889-4621 #! rnews 1443e wind th: ucb
-----------[000047][next][prev][last][first]---------------------------------------------------- Date: 4 Jun 88 18:09:46 GMT From: MRC@PANDA.PANDA.COM.UUCP To: comp.protocols.tcp-ip Subject: Re: Linking LAN's via Public X.25
Dan -
I'm responsible for one of the TCP/IP implementations used on a
9600 baud link in Canada. The system is a DEC-2065 running a TOPS-20
with a heavily modified TCP. It has two IP interfaces; a NIA20 to the
local Ethernet and an AN20 to a C/30 PSN using 1822.
This TCP lacks RFNM counting which is a serious deficiency, but
in the case of this link it doesn't really matter all that much since
(at least the last I read) there is only one place for the 1822-grams
to go to. If you're RFNM blocked to the friendly not-so-local gateway,
you can't do anything anyway.
What makes the burden worse, this machine is the only path between
the local Ethernet (which talks TCP/IP and DECnet) and the rest of the
world. It has a rudimentary EGP-speaker that babbles updates to Friend
Gateway.
I've seen no indication of a bottleneck at the DEC-20. Instead,
it seems to be more that the DEC-20 (and the Symbolics Lisp machines
behind it on the Ethernet) are communicating almost exclusively with
the Internet in the US, across two gateways over a long long wire.
There isn't all that much traffic to begin with, so any latency in a
connection can easily stop the line...because there is no other traffic!
-- Mark --
-------
-----------[000048][next][prev][last][first]---------------------------------------------------- Date: 4 Jun 88 22:12:00 GMT From: LAWS@rsre.mod.UK (John Laws, on UK.MOD.RSRE) To: comp.protocols.tcp-ip Subject: Re: Linking LAN's via Public X.25
>Perhaps another view of IP over X.25 might help. While the original >question was asked about Sun X.25, there are a number of networks within the >ARPA/Internet that use IP over X.25. Yet another view. The RSRE Internet Lab connects to two other European Internet sites (one in Holland and one in Germany) and others internal to the UK running IP over X.25. Quality of service is good and at current traffic levels is much cheaper than international/national leased circuits. The software has been developed to pay attention to the fact that real money is being spent e.g. virtual circuits close if IP traffic stops, and of course accounting and access control are well developed. If national X.25 provision by US carriers is seen as less than adequate, by US users, maybe its because they (the carriers) do not see it as a viable commercial market to make a big investment in given the existing 'free' networks like Arpanet, Milnet, NSFnet etc. YES I DO KNOW that they are not really free - that Government, Academic institutions and companies make payments. But in many cases the users at the keyboard are unaware and uncaring of the costs (judged by many of the remarks in this forum some months ago). John
-----------[000049][next][prev][last][first]---------------------------------------------------- Date: 5 Jun 88 05:25:19 GMT From: roode@orc.olivetti.COM (David Roode) To: comp.protocols.tcp-ip Subject: Re: Linking LAN's via Public X.25
There's no question that X.25 packet switching is a service built on top of point-to-point data circuit (leased line) capability. The tariffs in the U.S treat this as a 'value added' service and prohibit the basic operating companies from competing in the national market. The Public Data Networks offering packet services have to pay the same leased line rates as an end-user, both for backbone circuits and for ties between their switch locations and customer premises. At the same time, the charges for leased line service are obviously much cheaper in the U.S. than they are elsewhere. (It calls for a judgement, but it seems likely that much in excess of costs is recovered in the charges for leased line service in Europe.) As a result, it may be illogical to 'blame' the U.S. Public Data Nets for their charges. European PTT's may subsidize their X.25 offerings. U.S. PDN's see reduced usage volume due to reasonable competition from leased lines. The main service a PDN provides is the sharing of data circuits. So, in the U.S. a smaller fraction of uses see an economic incentive to share costs by making use of a PDN. (It takes a smaller volume of usage to cost justify switching to a leased line in the U.S.) The operating efficiency of the U.S. PDN's may be the same or even higher than the European PTT's in providing PDN service. It appears the hierarchy in terms of increasing cost for a 2400 baud data flow is something like: leased lines at U.S. typical rates Public Data nets at European rates Public Data nets at U.S. rates leased lines at European rates For 300 baud data flow, it is something like: Public Data nets at European rates Public Data nets at U.S. rates leased lines at U.S. typical rates leased lines at European rates For 9600 baud data flow, sequence might be: -or- leased lines/ U.S. rates leased lines/ U.S. rates Public Data nets/ U.S. rates Public Data nets/ U.S. rates Public Data nets/ Europe rates leased lines/Europe rates leased lines/Europe rates Public Data nets/ Europe rates
-----------[000050][next][prev][last][first]---------------------------------------------------- Date: Sun, 05 Jun 88 12:40:10 -0400 From: Craig Partridge <craig@NNSC.NSF.NET> To: guru@flora.wustl.edu Cc: tcp-ip@sri-nic.ARPA Subject: re: a couple of questions
Installing Van Jacobson's TCP on a SUN 3/50 is quite simple. There is a special Makefile.sun that makes it easy to generate *.o files you can stick in /sys/OBJ. It also works wonderfully -- my TCP connections have been noticeably happier. Installing the entire Berkeley distribution (with the IP fixes, etc) is quite difficult -- it requires porting the software to the SUN. Craig
-----------[000051][next][prev][last][first]---------------------------------------------------- Date: Sun, 5 Jun 88 20:38:52 PDT From: nowicki@Sun.COM (Bill Nowicki) To: guru@flora.wustl.EDU Cc: tcp-ip@sri-nic.arpa Subject: Re: A couple of questions
From: guru@flora.wustl.EDU (Gurudatta Parulkar) Date: 4 Jun 88 13:48:35 GMT Has anybody successfully installed Van Jacobson's tcp/ip on a binary only sun 3/50 ? Yes. Several thousand have. It is in the current software release, SunOS 4.0. - Bill Nowicki Sun Microsystems
-----------[000052][next][prev][last][first]---------------------------------------------------- Date: 5 Jun 88 16:40:10 GMT From: craig@NNSC.NSF.NET (Craig Partridge) To: comp.protocols.tcp-ip Subject: re: a couple of questions
Installing Van Jacobson's TCP on a SUN 3/50 is quite simple. There is a special Makefile.sun that makes it easy to generate *.o files you can stick in /sys/OBJ. It also works wonderfully -- my TCP connections have been noticeably happier. Installing the entire Berkeley distribution (with the IP fixes, etc) is quite difficult -- it requires porting the software to the SUN. Craig<