6328
BEST CURRENT PRACTICE
IANA Considerations for Network Layer Protocol Identifiers
Authors: D. Eastlake 3rd
Date: July 2011
Working Group: NON WORKING GROUP
Stream: IETF
Abstract
Some protocols being developed or extended by the IETF make use of the ISO/IEC (International Organization for Standardization / International Electrotechnical Commission) Network Layer Protocol Identifier (NLPID). This document provides NLPID IANA considerations. This memo documents an Internet Best Current Practice.
RFC 6328
BEST CURRENT PRACTICE
Internet Engineering Task Force (IETF) D. Eastlake 3rd
Request for Comments: 6328 Huawei
BCP: 164 July 2011
Category: Best Current Practice
ISSN: 2070-1721
<span class="h1">IANA Considerations for Network Layer Protocol Identifiers</span>
Abstract
Some protocols being developed or extended by the IETF make use of
the ISO/IEC (International Organization for Standardization /
International Electrotechnical Commission) Network Layer Protocol
Identifier (NLPID). This document provides NLPID IANA
considerations.
Status of This Memo
This memo documents an Internet Best Current Practice.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
BCPs is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="https://www.rfc-editor.org/info/rfc6328">http://www.rfc-editor.org/info/rfc6328</a>.
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
<span class="grey">Eastlake Best Current Practice [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc6328">RFC 6328</a> IANA Considerations for NLPIDs July 2011</span>
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. NLPIDs ..........................................................<a href="#page-3">3</a>
<a href="#section-2.1">2.1</a>. Sub-Ranges of the NLPID ....................................<a href="#page-3">3</a>
<a href="#section-2.2">2.2</a>. Code Point 0x80 ............................................<a href="#page-4">4</a>
<a href="#section-2.3">2.3</a>. NLPIDs Available for IANA Allocation .......................<a href="#page-4">4</a>
<a href="#section-3">3</a>. IANA Considerations .............................................<a href="#page-5">5</a>
<a href="#section-4">4</a>. Security Considerations .........................................<a href="#page-5">5</a>
<a href="#section-5">5</a>. References ......................................................<a href="#page-5">5</a>
<a href="#section-5.1">5.1</a>. Normative References .......................................<a href="#page-5">5</a>
<a href="#section-5.2">5.2</a>. Informative References .....................................<a href="#page-6">6</a>
<a href="#section-6">6</a>. Acknowledgements ................................................<a href="#page-7">7</a>
<a href="#appendix-A">Appendix A</a>. Initial IANA NLPID Web Page ............................<a href="#page-8">8</a>
<a href="#appendix-B">Appendix B</a>. RFC References to NLPID ................................<a href="#page-9">9</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
Some protocols being developed or extended by the IETF make use of
the ISO/IEC (International Organization for Standardization /
International Electrotechnical Commission) Network Layer Protocol
Identifier (NLPID).
The term "NLPID" is not actually used in [<a href="#ref-ISO9577" title=""Information technology - Telecommunications and Information exchange between systems - Protocol identification in the network layer"">ISO9577</a>], which refers to
one-octet IPIs (Initial Protocol Identifiers) and SPIs (Subsequent
Protocol Identifiers). While these are two logically separate kinds
of one-octet identifiers, most values are usable as both an IPI and
an SPI. In the remainder of this document, the term NLPID is used
for such values.
The registry of NLPID values is maintained by ISO/IEC by updating
[<a href="#ref-ISO9577" title=""Information technology - Telecommunications and Information exchange between systems - Protocol identification in the network layer"">ISO9577</a>]. The procedure specified by ISO/IEC in that document is
that an NLPID code point can be allocated without approval by
ISO/IEC, as long as the code point is not in a range of values
categorized for an organization other than the organization
allocating the code point and as long as ISO/IEC JTC1 SC6 is
informed.
This document provides NLPID IANA considerations. That is, it
specifies the level of IETF approval necessary for a code point to be
allocated for IETF use, the procedures to be used and actions to be
taken by IANA in connection with NLPIDs, and related guidelines.
[<a id="ref-RFC5226">RFC5226</a>] is incorporated herein except to the extent that there are
contrary provisions in this document.
<span class="grey">Eastlake Best Current Practice [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc6328">RFC 6328</a> IANA Considerations for NLPIDs July 2011</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. NLPIDs</span>
[<a id="ref-ISO9577">ISO9577</a>] defines one-octet network layer protocol identifiers that
are commonly called NLPIDs, which is the term used in this document.
NLPIDs are used in a number of protocols. For example, in the
mar$pro.type field of the multicast address resolution server
protocol [<a href="./rfc2022" title=""Support for Multicast over UNI 3.0/3.1 based ATM Networks"">RFC2022</a>], the ar$pro.type field of the NBMA (Non-Broadcast
Multi-Access) next hop resolution protocol [<a href="./rfc2332" title=""NBMA Next Hop Resolution Protocol (NHRP)"">RFC2332</a>] and in the IS-IS
Protocols Supported TLV [<a href="./rfc1195" title=""Use of OSI IS-IS for routing in TCP/IP and dual environments"">RFC1195</a>]. See <a href="#appendix-B">Appendix B</a>.
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Sub-Ranges of the NLPID</span>
Sub-ranges of the possible NLPID values are categorized by [<a href="#ref-ISO9577" title=""Information technology - Telecommunications and Information exchange between systems - Protocol identification in the network layer"">ISO9577</a>]
for organizations as shown below, primarily for the ISO/IEC
(International Organization for Standardization / International
Electrotechnical Commission) and the ITU-T (International
Telecommunication Union - Telecommunication Standardization Sector):
Code Point Category
---------- --------
0x00 ISO/IEC
0x01-0x0F ITU-T
0x10-0x3F ITU-T Rec. X.25 and ISO/IEC 8208
0x40-0x43 ISO/IEC
0x44 ITU-T
0x45-0x4F ISO/IEC
0x50-0x6F ITU-T Rec. X.25 and ISO/IEC 8208
0x70-0x7F Joint ITU-T and ISO/IEC
0x80 ISO/IEC (see <a href="#section-2.2">Section 2.2</a>)
0x81-0x8F ISO/IEC
0x90-0xAF ITU-T Rec. X.25 and ISO/IEC 8208
0xB0-0xBF ITU-T
0xC0-0xCF Potentially available for IANA (see <a href="#section-2.3">Section 2.3</a>)
0xD0-0xEF ITU-T Rec. X.25 and ISO/IEC 8208
0xF0-0xFE Joint ITU-T and ISO/IEC
0xFF Reserved for an Extension mechanism to be
jointly developed by ITU-T and ISO/IEC
<span class="grey">Eastlake Best Current Practice [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc6328">RFC 6328</a> IANA Considerations for NLPIDs July 2011</span>
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Code Point 0x80</span>
NLPID 0x80 is known as the IEEE (Institute of Electrical &
Electronics Engineers) SNAP (SubNetwork Access Protocol) code point.
It is followed by five octets, using the IEEE SNAP SAP (Service
Access Point) conventions, to specify the protocol. Those
conventions are described in <a href="./rfc5342#section-3">Section 3 of [RFC5342]</a>. In particular,
it is valid for such a five-octet sequence to start with the IANA OUI
(Organizationally Unique Identifier) followed by two further octets
assigned by IANA as provided in [<a href="./rfc5342" title=""IANA Considerations and IETF Protocol Usage for IEEE 802 Parameters"">RFC5342</a>]. The same IANA registry is
used for such protocol identifiers whether they are planned to be
introduced by the 0x80 NLPID or the IEEE SNAP SAP LSAPs (Link-Layer
Service Access Points) (0xAAAA). Values allocated by IANA may be
used in either context as appropriate.
Because of the limited number of NLPID code points available for IANA
allocation, use of the IEEE SNAP NLPID is RECOMMENDED rather than
allocation of a new one-octet NLPID code point.
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. NLPIDs Available for IANA Allocation</span>
A limited number of code points are available that could be allocated
by IANA under [<a href="#ref-ISO9577" title=""Information technology - Telecommunications and Information exchange between systems - Protocol identification in the network layer"">ISO9577</a>]. Because of this, it is desirable, where
practical, to use code point 0x80, as discussed in <a href="#section-2.2">Section 2.2</a> above,
or to get code points allocated from the ranges categorized to other
organizations. For example, code point 0x8E was allocated for IPv6
[<a href="./rfc2460" title=""Internet Protocol, Version 6 (IPv6) Specification"">RFC2460</a>], although it is in a range of code points categorized for
ISO/IEC. One-byte code points are assigned to TRILL and IEEE 802.1aq
as they are intended for use within the IS-IS Protocols Supported TLV
[<a href="./rfc1195" title=""Use of OSI IS-IS for routing in TCP/IP and dual environments"">RFC1195</a>].
The table below, which includes two new code point allocations made
by this document, shows those still available.
Code Point Status
---------- --------
0xC0 TRILL [<a href="./rfc6325" title=""RBridges: Base Protocol Specification"">RFC6325</a>]
0xC1 IEEE 802.1aq [<a href="#ref-802.1aq" title="Draft IEEE P802.1aq/D2.1">802.1aq</a>]
0xC2-0xCB Available
0xCC IPv4 [<a href="./rfc791" title=""Internet Protocol"">RFC791</a>]
0xCD-0xCE Available
0xCF PPP [<a href="./rfc1661" title=""The Point-to-Point Protocol (PPP)"">RFC1661</a>]
<span class="grey">Eastlake Best Current Practice [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc6328">RFC 6328</a> IANA Considerations for NLPIDs July 2011</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. IANA Considerations</span>
As long as code points are available, IANA will allocate additional
values when required by applying the IETF Review policy as per
[<a href="./rfc5226" title="">RFC5226</a>].
Whenever it allocates an NLPID, IANA will inform the IETF liaison to
ISO/IEC JTC1 SC6 (Joint Technical Committee 1, Study Committee 6)
[<a href="#ref-JTC1SC6" title="Joint Technical Committee 1">JTC1SC6</a>], or if IANA is unable to determine that IETF liaison, the
IAB. The liaison (or the IAB) will then ensure that ISO/IEC JTC1 SC6
is informed so that [<a href="#ref-ISO9577" title=""Information technology - Telecommunications and Information exchange between systems - Protocol identification in the network layer"">ISO9577</a>] can be updated since ISO/IEC JTC1 SC6
is the body that maintains [<a href="#ref-ISO9577" title=""Information technology - Telecommunications and Information exchange between systems - Protocol identification in the network layer"">ISO9577</a>]. To simplify this process, it
is desirable that the IAB maintain an IETF liaison to ISO/IEC JTC1
SC6.
This document allocates the code points 0xC0 and 0xC1 as shown in
<a href="#section-2.3">Section 2.3</a> and IANA shall request the liaison (or the IAB) to so
inform ISO/IEC JTC1 SC6.
IANA maintains a web page showing NLPIDs that have been allocated to
a protocol being developed or extended by the IETF or are otherwise
of interest. The initial state of the web page is as shown in
<a href="#appendix-A">Appendix A</a>. IANA will update this web page for (1) NLPIDs allocated
by IANA and (2) other allocations or de-allocations when IANA is
requested to make such changes to this web page by the IETF liaison
mentioned above.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
This document is concerned with allocation of NLPIDs. It is not
directly concerned with security.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. References</span>
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Normative References</span>
[<a id="ref-ISO9577">ISO9577</a>] International Organization for Standardization "Information
technology - Telecommunications and Information exchange
between systems - Protocol identification in the network
layer", ISO/IEC TR 9577:1999, 1999-12-15.
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>, May
2008.
<span class="grey">Eastlake Best Current Practice [Page 5]</span><span id="page-6" ></span>
<span class="grey"><a href="./rfc6328">RFC 6328</a> IANA Considerations for NLPIDs July 2011</span>
[<a id="ref-RFC5342">RFC5342</a>] Eastlake 3rd., D., "IANA Considerations and IETF Protocol
Usage for IEEE 802 Parameters", <a href="https://www.rfc-editor.org/bcp/bcp141">BCP 141</a>, <a href="./rfc5342">RFC 5342</a>,
September 2008.
[<a id="ref-RFC6325">RFC6325</a>] Radia, P., Eastlake, D., Dutt, D., Gai, S., and A.
Ghanwani, "RBridges: Base Protocol Specification", <a href="./rfc6325">RFC</a>
<a href="./rfc6325">6325</a>, July 2011.
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Informative References</span>
[<a id="ref-802.1aq">802.1aq</a>] Standard for Local and Metropolitan Area Networks / Virtual
Bridged Local Area Networks / Amendment 9: Shortest Path
Bridging, Draft IEEE P802.1aq/D2.1, 21 August 2009.
[<a id="ref-JTC1SC6">JTC1SC6</a>] ISO/IEC JTC1 SC6 (International Organization for
Standardization / International Electrotechnical
Commission, Joint Technical Committee 1, Study Committee
6), <a href="http://www.iso.org/iso/iso_technical_committee.html?commid=45072">http://www.iso.org/iso/</a>
<a href="http://www.iso.org/iso/iso_technical_committee.html?commid=45072">iso_technical_committee.html?commid=45072</a>
[<a id="ref-RFC791">RFC791</a>] Postel, J., "Internet Protocol", STD 5, <a href="./rfc791">RFC 791</a>, September
1981.
[<a id="ref-RFC1195">RFC1195</a>] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and
dual environments", <a href="./rfc1195">RFC 1195</a>, December 1990.
[<a id="ref-RFC1661">RFC1661</a>] Simpson, W., Ed., "The Point-to-Point Protocol (PPP)", STD
51, <a href="./rfc1661">RFC 1661</a>, July 1994.
[<a id="ref-RFC1707">RFC1707</a>] McGovern, M. and R. Ullmann, "CATNIP: Common Architecture
for the Internet", <a href="./rfc1707">RFC 1707</a>, October 1994.
[<a id="ref-RFC2022">RFC2022</a>] Armitage, G., "Support for Multicast over UNI 3.0/3.1 based
ATM Networks", <a href="./rfc2022">RFC 2022</a>, November 1996.
[<a id="ref-RFC2332">RFC2332</a>] Luciani, J., Katz, D., Piscitello, D., Cole, B., and N.
Doraswamy, "NBMA Next Hop Resolution Protocol (NHRP)", <a href="./rfc2332">RFC</a>
<a href="./rfc2332">2332</a>, April 1998.
[<a id="ref-RFC2460">RFC2460</a>] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", <a href="./rfc2460">RFC 2460</a>, December 1998.
<span class="grey">Eastlake Best Current Practice [Page 6]</span><span id="page-7" ></span>
<span class="grey"><a href="./rfc6328">RFC 6328</a> IANA Considerations for NLPIDs July 2011</span>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgements</span>
The contributions and support of the following people, listed in
alphabetic order, are gratefully acknowledged:
Ayan Banerjee, Gonzalo Camarillo, Dinesh Dutt, Don Fedyk, Alfred
Hines, Russ Housley, Andrew Malis, Radia Perlman, Dan Romascanu,
and Peter Ashwood-Smith.
<span class="grey">Eastlake Best Current Practice [Page 7]</span><span id="page-8" ></span>
<span class="grey"><a href="./rfc6328">RFC 6328</a> IANA Considerations for NLPIDs July 2011</span>
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Initial IANA NLPID Web Page</span>
NLPIDs of Interest
Code Point Use
---------- --------
0x00 Null
0x08 Q.933 (<a href="./rfc2427">RFC 2427</a>)
0x80 IEEE SNAP (<a href="./rfc6328">RFC 6328</a>)
0x81 ISO CLNP (Connectionless Network Protocol)
0x82 ISO ES-IS
0x83 IS-IS (<a href="./rfc1195">RFC 1195</a>)
0x8E IPv6 (<a href="./rfc2460">RFC 2460</a>)
0xB0 FRF.9 (<a href="./rfc2427">RFC 2427</a>)
0xB1 FRF.12 (RF C2427)
0xC0 TRILL (<a href="./rfc6325">RFC 6325</a>)
0xC1 IEEE 802.1aq
0xCC IPv4 (<a href="./rfc791">RFC 791</a>)
0xCF PPP (<a href="./rfc1661">RFC 1661</a>)
Note: According to [<a href="./rfc1707" title=""CATNIP: Common Architecture for the Internet"">RFC1707</a>], NLPID 0x70 was assigned to IPv7. That
assignment appears to no longer be in effect as it is not listed in
ISO/IEC 9577. IPv7 was itself a temporary code point assignment made
while a decision was being made between three candidates for the next
generation of IP after IPv4. Those candidates were assigned IPv6,
IPv7, and IPv8. IPv6 was selected.
<span class="grey">Eastlake Best Current Practice [Page 8]</span><span id="page-9" ></span>
<span class="grey"><a href="./rfc6328">RFC 6328</a> IANA Considerations for NLPIDs July 2011</span>
<span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">Appendix B</a>. RFC References to NLPID</span>
The following RFCs, issued before the end of March 2009, excluding
other survey RFCs and obsolete RFCs, reference the NLPID as such:
<a href="./rfc1195">RFC 1195</a> Use of OSI IS-IS for Routing in TCP/IP and Dual
Environments
<a href="./rfc1356">RFC 1356</a> Multiprotocol Interconnect on X.25 and ISDN in the Packet
Mode
<a href="./rfc1377">RFC 1377</a> The PPP OSI Network Layer Control Protocol (OSINLCP)
<a href="./rfc1661">RFC 1661</a> The Point-to-Point Protocol (PPP)
<a href="./rfc1707">RFC 1707</a> CATNIP: Common Architecture for the Internet
<a href="./rfc1755">RFC 1755</a> ATM Signaling Support for IP over ATM
<a href="./rfc2022">RFC 2022</a> Support for Multicast over UNI 3.0/3.1 based ATM Networks
<a href="./rfc2332">RFC 2332</a> NBMA Next Hop Resolution Protocol (NHRP)
<a href="./rfc2337">RFC 2337</a> Intra-LIS IP multicast among routers over ATM using Sparse
Mode PIM
<a href="./rfc2363">RFC 2363</a> PPP Over FUNI
<a href="./rfc2390">RFC 2390</a> Inverse Address Resolution Protocol
<a href="./rfc2427">RFC 2427</a> Multiprotocol Interconnect over Frame Relay
<a href="./rfc2590">RFC 2590</a> Transmission of IPv6 Packets over Frame Relay Networks
Specification
<a href="./rfc2684">RFC 2684</a> Multiprotocol Encapsulation over ATM Adaptation Layer 5
<a href="./rfc2955">RFC 2955</a> Definitions of Managed Objects for Monitoring and
Controlling the Frame Relay/ATM PVC Service Interworking
Function
<a href="./rfc3070">RFC 3070</a> Layer Two Tunneling Protocol (L2TP) over Frame Relay
<a href="./rfc5308">RFC 5308</a> Routing IPv6 with IS-IS
Author's Address
Donald E. Eastlake 3rd
Huawei Technologies
155 Beaver Street
Milford, MA 01757 USA
Phone: +1-508-333-2270
EMail: [email protected]
Eastlake Best Current Practice [Page 9]
Annotations
Select text to annotate