The Routing Over Large Clouds Mailing List Archive by date

["Andrew G. Malis" <malis@nexen.com>]

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]