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!ucbvax!edn-unix.arpa!cain
From: cain@EDN-UNIX.ARPA (Edward A. Cain)
Newsgroups: mod.protocols.tcp-ip
Subject: Re: 802.2 SAP's
Message-ID: <8510281554.AA16293@UCB-VAX>
Date: Mon, 28-Oct-85 09:01:00 EST
Article-I.D.: UCB-VAX.8510281554.AA16293
Posted: Mon Oct 28 09:01:00 1985
Date-Received: Tue, 29-Oct-85 01:42:24 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 23
Approved: tcp-ip@ucbvax.berkeley.edu

Working with Rob Rosenthal of the National Bureau of Standards, I put 
together a case for a SAP for IP using the IEEE 802 committee's rules
for standard SAP assignments -- basically arguments about universal use
and widespread deployment. The IP SAP assignment for IP was an exception
to the usual practice of assigning SAPs to "international standards".

I tried the same route for ARP a few months ago, even though ARP isn't
nearly as universal as IP. I was told: 

	1. There is a critical shortage of reserved numbers, even limiting
	them to the ISO and CCITT standards.

	2. There are a bunch of numbers available for unofficial 
	assignment, and one of these numbers ought to be picked for 
	things like ARP. A directory of these unoffical number 
	assignment is available to help avoid stepping on already 
	assigned "toes".

	3. Don't push your luck.

Ed Cain