Date: Mon, 25 Oct 93 04:30:01 PDT
From: Advanced Amateur Radio Networking Group <tcp-group@ucsd.edu>
Errors-To: TCP-Group-Errors@UCSD.Edu
Reply-To: TCP-Group@UCSD.Edu
Precedence: Bulk
Subject: TCP-Group Digest V93 #277
To: tcp-group-digest


TCP-Group Digest            Mon, 25 Oct 93       Volume 93 : Issue  277

Today's Topics:
                     Kind of interesting problem.
                 TCP-Group Digest V93 #274  (2 msgs)
                your LISTSERV request "list tcp-group"

Send Replies or notes for publication to: <TCP-Group@UCSD.Edu>.
Subscription requests to <TCP-Group-REQUEST@UCSD.Edu>.
Problems you can't solve otherwise to brian@ucsd.edu.

Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: Sun, 24 Oct 1993 00:24:38 -0400
From: goldstein@carafe.tay2.dec.com (k1io, FN42jk)
Subject: Kind of interesting problem.
To: tcp-group@ucsd.edu

Isn't this packet (ARP _from_ broadcast, causing broadcast storm) known
in the trade as a "Chernobyl Packet"?
   fred

------------------------------

Date: Sun, 24 Oct 93 13:21:04 GMT
From: Jonathan Naylor <g4klx@g4klx.demon.co.uk>
Subject: TCP-Group Digest V93 #274
To: TCP-Group@ucsd.edu

> Date: Thu, 21 Oct 93 8:43:02 PDT
> From: bmeyer@netcom.com (R. W. Meyer)
> Subject: Network Standards
> To: TCP-Group@ucsd.edu
> 
> The statement was made here a couple days ago that NET/ROM was no longer
> being marketed.  As a point of order thats not entirely true.  I checked
> with WA8DED (one of NET/ROMs oringinal authors) and it is still being
> produced and marketed by a company called Amatech International (no I never
> heard of them before either).  I called and got one of their brochures.
> They can be reached at:
>

When I bought two NET/ROMs in late 1987 I had to send off to Amatech
International. About a month later TheNet 1.0 turned up, oh well. Would WA8DED
mind if the NET/ROM protocol was documented and made publically accessible ?
The protocols are fully described in the back of the manual (which is what
G8BPQ used for his implementation). I would be quite happy to do an ASCII text
version of the protocols complete with 'extensions' and some examples IF I knew
that it would not be infringing any copyrights.

> 

Unfortunately almost all of the discussion about NET/ROM has centred around the
implementation rather than the protocol itself. The NET/ROM manual splits the
Network and Transport 'Headers' and describes them seperately. My main
objections to NET/ROM are the lack of an ICMP type functionality, the lack of a
Transport Protocol ID so that IP, TCP and NET/ROM Transport could be
multiplexed over it much easier. Because NET/ROM uses callsigns for its Node
IDs makes subnetting and the use of masks for routing impossible. The fact that
NET/ROM does not have an ARP level doesn't worry me, I may be old fashioned but
we are talking about protocols that are to be used over amateur radio, not
Ethernet or land-lines, and I feel that the use of callsigns in the Link Layer
is a Good Thing (tm). FYI G8BPQ has NET/ROM running over ethernet.

>From the amateur radio viewpoint IP and TCP are not above criticism. There are
a lot of bytes (sorry octets) in them that are essentially unused most of the
time. By default amateur TCP/IP doesn't use VJ header compression or something
similar which I feel could be a big win on standard 1200 Baud user access
frequencies.

Jonathan

------------------------------

Date: Sun, 24 Oct 1993 14:31:06 -0400
From: "Louis A. Mamakos" <louie@uunet.uu.net>
Subject: TCP-Group Digest V93 #274 
To: g4klx@g4klx.demon.co.uk

> From the amateur radio viewpoint IP and TCP are not above criticism. There are
> a lot of bytes (sorry octets) in them that are essentially unused most of the
> time. By default amateur TCP/IP doesn't use VJ header compression or something
> similar which I feel could be a big win on standard 1200 Baud user access
> frequencies.

VJ header compress presumes a fairly reliable link-level protocol with
minimal loss.  This surely isn't met on most 1200 bps user channels,
unless you layer it over an AX.25 VC.

Louis A. Mamakos, WA3YMH   louie@uunet.uu.net
UUNET Technologies, Inc.   uunet!louie
3110 Fairview Park Dr., Suite 570  Voice) +1 703 204 8000
Falls Church, Va 22042    Fax)   +1 703 204 8001

------------------------------

Date: Mon, 25 Oct 1993 03:51:23 -0700
From: Listserv@ucsd.edu (Mailing List Processor)
Subject: your LISTSERV request "list tcp-group"
To: john.heaton@nessie.mcc.ac.uk

Per request by john.heaton@nessie.mcc.ac.uk
 "list tcp-group"
'tcp-group' is not subscribed to any mailing lists.

------------------------------

End of TCP-Group Digest V93 #277
******************************
******************************