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!BRUBECK.PROTEON.COM!jas
From: jas@BRUBECK.PROTEON.COM
Newsgroups: mod.protocols.tcp-ip
Subject: Re: Re: IEEE and Ethernet
Message-ID: <8606270407.AA16353@ucbvax.Berkeley.EDU>
Date: Thu, 26-Jun-86 13:29:40 EDT
Article-I.D.: ucbvax.8606270407.AA16353
Posted: Thu Jun 26 13:29:40 1986
Date-Received: Sat, 28-Jun-86 00:31:28 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: jas@proteon.com
Organization: The ARPA Internet
Lines: 15
Approved: tcp-ip@sri-nic.arpa

The protocol numbers are in the 802.2 data link control header, which
is standard for 802.3, 802.4, and 802.5. They are one byte, and are
incredibly stricly regulated. Basically, they're only available
to established international standards. There is a (they're called SAPs)
for TCP/IP, but that was considered an EXCEPTION to the rule, as TCP/IP
is not promulgated by an international standards body.

The only allocated SAPs are: ISO IP and TCP/IP. Half of them are
"unadministered", IBM has de-facto taken a group for SNA.

You'll notice that ARP is not listed. A group of us are trying to
work on this issue.

(I can provide more gruesome details of the list, if desired.)
-------