Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!ittatc!dcdwest!sdcsvax!ucbvax!RED.RUTGERS.EDU!HEDRICK
From: HEDRICK@RED.RUTGERS.EDU (Charles Hedrick)
Newsgroups: mod.protocols.tcp-ip
Subject: Re: Re: IEEE and Ethernet
Message-ID: <12218560136.22.HEDRICK@RED.RUTGERS.EDU>
Date: Sat, 28-Jun-86 22:35:26 EDT
Article-I.D.: RED.12218560136.22.HEDRICK
Posted: Sat Jun 28 22:35:26 1986
Date-Received: Sun, 29-Jun-86 04:15:36 EDT
References: <8606272158.AA12405@trantor.UMD.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 9
Approved: tcp-ip@sri-nic.arpa

Do anyone know if there are plans to do a real 803.x implementation
of IP, i.e. one that uses the type field as a length?  One would
suppose that the first vendor to do this would lose big, since no
other implementation would talk to it.  I would think a more natural
approach would be for IP, PUP, etc., to continue using the type
field as a type.  Then if we see a packet with a value that is in
the range of legal 803 lengths, we treat it as if it specified a
type of ISO.
-------