Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!decvax!decwrl!pyramid!hplabs!hp-sdd!ncr-sd!sdcsvax!ucbvax!XEROX.COM!Murray.pa
From: Murray.pa@XEROX.COM.UUCP
Newsgroups: mod.protocols.tcp-ip
Subject: Re: IEEE and Ethernet
Message-ID: <860624-141755-2789@Xerox>
Date: Tue, 24-Jun-86 16:34:05 EDT
Article-I.D.: Xerox.860624-141755-2789
Posted: Tue Jun 24 16:34:05 1986
Date-Received: Thu, 26-Jun-86 23:42:22 EDT
References: <860620104633.4.DCP@FIREBIRD.SCRC.Symbolics.COM>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 17
Approved: tcp-ip@sri-nic.arpa

"I assume this applies to the protocol field as well?"

The IEEE doesn't think anybody needs a protocol field. They use that
word for the packet length.  Thus I doubt very much if they are
interested in assigning values. I don't know for sure though.

Most of the existing protocol values were "grandfathered" in because
they are invalid lengths. The official 802 position is that they don't
care what consenting adults do with packets having invalid lengths.
(There is probably a footnote along that line in the specs.) 

The only protocol field values that weren't big/lucky enough to get
grandfathered this way are used for Pup. A pair of alternates have been
assigned. The switchover is painful. Most places have ignored it. I
think the Ethernet driver for the latest VMS now rejects old Pups. That
doesn't make the switchover any easier, but it might make it happen
sooner.