New "Assigned Numbers" text for IANA SNAP Protocol IDs
"Andrew G. Malis" <malis@nexen.com> Tue, 28 November 1995 19:47 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa25315;
28 Nov 95 14:47 EST
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa25311;
28 Nov 95 14:47 EST
Received: from maelstrom.nexen.com (maelstrom.nexen.com [204.249.98.5]) by
guelah.nexen.com (8.6.12/8.6.12) with ESMTP id OAA17999;
Tue, 28 Nov 1995 14:18:27 -0500
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id
OAA14879 for rolc-out; Tue, 28 Nov 1995 14:22:22 -0500
Received: from phish.nexen.com (phish.nexen.com [204.249.99.14]) by
maelstrom.nexen.com (8.6.12/8.6.12) with ESMTP id OAA14866 for <rolc-proc>;
Tue, 28 Nov 1995 14:22:18 -0500
Received: from localhost (malis@localhost) by phish.nexen.com (8.6.12/8.6.12)
with SMTP id OAA07680; Tue, 28 Nov 1995 14:22:16 -0500
Message-Id: <199511281922.OAA07680@phish.nexen.com>
To: rolc@nexen.com, ip-atm@matmos.hpl.hp.com
cc: malis@nexen.com
Subject: New "Assigned Numbers" text for IANA SNAP Protocol IDs
Date: Tue, 28 Nov 1995 14:22:16 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Andrew G. Malis" <malis@nexen.com>
X-Orig-Sender: owner-rolc@nexen.com
Precedence: bulk
X-Info: Submissions to rolc@nexen.com
X-Info: [Un]Subscribe requests to rolc-request@nexen.com
X-Info: Archives for rolc via
ftp://ietf.cnri.reston.va.us/ietf-mail-archive/rolc/
I can now report successful completion of an outstanding action item of mine for both the ROLC and IP/ATM working groups - the text below is now a part of the electronic version of "Assigned Numbers", and will be included in the next RFC version. If you check out ftp://ftp.isi.edu/in-notes/iana/assignments/ethernet-numbers, you'll see the new text near the end of the section. I worded and formatted it for consistency with other Assigned Numbers text. Andy ------- SNAP PROTOCOL IDS IN THE IANA ETHERNET ADDRESS BLOCK The Sub-Network Access Protocol (SNAP) header contains 40 bits: 24 bits containing an IEEE-assigned Organizationally Unique Identifier (OUI), and 16 bits containing a Protocol Identifier (PID). The OUIs are the same as those used in the Ethernet Vendor Address Components list below. The IANA's OUI, 00-00-5E, may be used in SNAP headers with the appropriate PID to identify the protocols listed below. Note that the IANA restricts this list to protocols that are ONLY identified in this manner; if a protocol has an EtherType, then SNAP headers identifying that protocol must contain an OUI of 00-00-00, with the EtherType in the PID field. The SNAP PID assignments using the IANA's OUI are: Protocol ID Description References ----------- ----------- ---------- decimal Hex 0001 0001 MARS Data Messages (short form) [work in progress] 0002 0002 reserved for future NHRP use [work in progress] 0003 0003 MARS/NHRP Control Messages [work in progress] 0004 0004 MARS Data Messages (long form) [work in progress]
- New "Assigned Numbers" text for IANA SNAP Protoco… Andrew G. Malis