IANA Considerations for Network Layer Protocol Identifiers
RFC 6328
| Document | Type |
RFC - Best Current Practice
(July 2011; No errata)
Also known as BCP 164
Was draft-eastlake-nlpid-iana-considerations (individual in ops area)
|
|
|---|---|---|---|
| Author | Donald Eastlake | ||
| Last updated | 2015-10-14 | ||
| Stream | Internent Engineering Task Force (IETF) | ||
| Formats | plain text html pdf htmlized (tools) htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | (None) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 6328 (Best Current Practice) | |
| Action Holders |
(None)
|
||
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Dan Romascanu | ||
| Send notices to | (None) | ||
Internet Engineering Task Force (IETF) D. Eastlake 3rd
Request for Comments: 6328 Huawei
BCP: 164 July 2011
Category: Best Current Practice
ISSN: 2070-1721
IANA Considerations for Network Layer Protocol Identifiers
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 Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6328.
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) 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.
Eastlake Best Current Practice [Page 1]
RFC 6328 IANA Considerations for NLPIDs July 2011
Table of Contents
1. Introduction ....................................................2
2. NLPIDs ..........................................................3
2.1. Sub-Ranges of the NLPID ....................................3
2.2. Code Point 0x80 ............................................4
2.3. NLPIDs Available for IANA Allocation .......................4
3. IANA Considerations .............................................5
4. Security Considerations .........................................5
5. References ......................................................5
5.1. Normative References .......................................5
5.2. Informative References .....................................6
6. Acknowledgements ................................................7
Appendix A. Initial IANA NLPID Web Page ............................8
Appendix B. RFC References to NLPID ................................9
1. Introduction
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 [ISO9577], 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
[ISO9577]. 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.
[RFC5226] is incorporated herein except to the extent that there are
contrary provisions in this document.
Eastlake Best Current Practice [Page 2]
RFC 6328 IANA Considerations for NLPIDs July 2011
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 [RFC2119].
2. NLPIDs
[ISO9577] 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
Show full document text