Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!ames!ucbcad!ucbvax!VENERA.ISI.EDU!postel
From: postel@VENERA.ISI.EDU
Newsgroups: comp.sys.xerox
Subject: Protocol number for PUP on Ethernet
Message-ID: <8711130053.AA02561@bel.isi.edu>
Date: Thu, 12-Nov-87 19:53:53 EST
Article-I.D.: bel.8711130053.AA02561
Posted: Thu Nov 12 19:53:53 1987
Date-Received: Sun, 15-Nov-87 01:55:52 EST
Sender: usenet@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 16


 Our PUP software between 1100s and VAX/VMS cuurently uses protocol 2. This
 was fine so far but with VMS 4.6, DEC have put restrictions on the XEDRIVER
 regarding the protocol number you may use, so that the driver can also
 process IEEE 802 packets. The restriction is that the protocol should look
 > 1501 (10) after its two bytes have been swapped (VMS 4.6 release notes).

 Before we select a random number for our PUP protocol and go into the 
 burden of upgrading all our systems, is there a recommended/standard 
 protocol number for PUP that is compatible with the above restriction?

See RFC-1010, page 14.  However, the number for PUP there is 512 decimal
which is not greated than 1501 decimal.  Let me know if you find a better
number and how it is justified.

--jon.