Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!ames!elroy!cit-vax!ucla-cs!zen!ucbvax!sdr.slb.COM!BARBE
From: BARBE@sdr.slb.COM ("Claude Barbe - SDR -  431 5524", 203)
Newsgroups: comp.sys.xerox
Subject: Protocol number for PUP on Ethernet
Message-ID: <8711122227.AA06574@ucbvax.Berkeley.EDU>
Date: Thu, 12-Nov-87 15:47:00 EST
Article-I.D.: ucbvax.8711122227.AA06574
Posted: Thu Nov 12 15:47:00 1987
Date-Received: Sat, 14-Nov-87 21:51:05 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 13

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?

Thanks for any info on the subject.

Claude Barbe - Schlumberger-Doll Research - Ridgefield, CT