Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ihnp4!ihlpa!normt
From: normt@ihlpa.UUCP
Newsgroups: comp.dcom.lans
Subject: Re: Ethernet protocol numbers
Message-ID: <5306@ihlpa.ATT.COM>
Date: Tue, 1-Sep-87 08:36:10 EDT
Article-I.D.: ihlpa.5306
Posted: Tue Sep  1 08:36:10 1987
Date-Received: Wed, 2-Sep-87 07:14:11 EDT
References: <14440@hi.UUCP>
Organization: AT&T Bell Laboratories - Naperville, Illinois
Lines: 30

In article <14440@hi.UUCP>, zeilenga@hc.dspo.gov (Kurt Zeilenga) writes:
> We are writing some Ethernet tools and have an incomplete
> list of protocols.  Two unknown protocols, 0x9002 and 0x8038,
> are flying across our backbone.  0x9002 appear to be coming
> from Bridge CS/100 terminal servers and 0x8038 by VMS systems.
> 
> We all have most of the IP numbers, working on XNS and DEC numbers,
> others are not used here so....
> 
> 	Kurt Zeilenga	 (zeilenga@hc.dspo.gov)

From the incomplete list that I have, 0x8038 is for DEC LanBridge-100's.
I don't know what exactly it is used for, but it is known. 0x9002 is
unknown to me. My list also shows a slight difference for 0x6001 and 0x6002.

I have 6001 being Decnet MOP (Dump/Load assistance) and
0x6002 as NCP Connect (Remote Console facility).

	I'm not sure if these are the same as yours, as far as true meaning
	or not.

If you ever get a complete list (shouldn't this be available from someone)
could you please either submit it to the net or at  least mail me a copy.

	Thanks;

	Norm Tiedemann		Room IH 2G-331
	ihnp4!ihlpa!normt	AT&T Bell Labs
				Naperville, IL
					 60566