IANA Registries for LSP Ping Code Points
RFC 7537
| Document | Type |
RFC - Proposed Standard
(May 2015; No errata)
Obsoleted by RFC 8029
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Replaces | draft-decraene-mpls-lsp-ping-registry | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication (wg milestone: Apr 2015 - ++ Progress draft-ie... ) | |
| Document shepherd | Ross Callon | ||
| Shepherd write-up | Show (last changed 2015-02-06) | ||
| IESG | IESG state | RFC 7537 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Deborah Brungard | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) B. Decraene
Request for Comments: 7537 Orange
Updates: 4379, 6424 N. Akiya
Category: Standards Track C. Pignataro
ISSN: 2070-1721 Cisco Systems
L. Andersson
S. Aldrin
Huawei Technologies
May 2015
IANA Registries for LSP Ping Code Points
Abstract
RFCs 4379 and 6424 created name spaces for Multi-Protocol Label
Switching (MPLS) Label Switched Path (LSP) Ping. However, those RFCs
did not create the corresponding IANA registries for Downstream
Mapping object Flags (DS Flags), Multipath Types, Pad TLVs, and
Interface and Label Stack Address Types.
There is now a need to make further code point allocations from these
name spaces. This document updates RFCs 4379 and 6424 in that it
creates IANA registries for that purpose.
Status of This Memo
This is an Internet Standards Track document.
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
Internet Standards 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/rfc7537.
Decraene, et al. Standards Track [Page 1]
RFC 7537 IANA Registries for LSP Ping May 2015
Copyright Notice
Copyright (c) 2015 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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
2.1. DS Flags . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Multipath Types . . . . . . . . . . . . . . . . . . . . . 3
2.3. Pad Type . . . . . . . . . . . . . . . . . . . . . . . . 4
2.4. Interface and Label Stack Address Type . . . . . . . . . 5
3. Security Considerations . . . . . . . . . . . . . . . . . . . 5
4. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.1. Normative References . . . . . . . . . . . . . . . . . . 6
4.2. Informative References . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction
[RFC4379] and [RFC6424] created name spaces for MPLS LSP Ping.
However, those RFCs did not create the corresponding IANA registries
for DS Flags, Multipath Types, Pad TLVs, and Interface and Label
Stack Address Types.
There is now a need to make further code point allocations from these
name spaces. In particular, [ENTROPY-LSP-PING] and [LSP-PING-LAG]
request new DS Flags and Multipath Type allocations.
This document updates [RFC4379] and [RFC6424] in that it creates IANA
registries for that purpose.
Note that "DS Flags" and "Multipath Type" are fields included in two
TLVs defined in the "Multi-Protocol Label Switching (MPLS) Label
Switched Paths (LSPs) Ping Parameters - TLVs" registry: Downstream
Mapping (DEPRECATED) (value 2) and Downstream Detailed Mapping (value
20). Modification to either registry will affect both TLVs.
Decraene, et al. Standards Track [Page 2]
RFC 7537 IANA Registries for LSP Ping May 2015
2. IANA Considerations
Per this document, IANA has created new registries within the "Multi-
Protocol Label Switching (MPLS) Label Switched Paths (LSPs) Ping
Parameters" [IANA-MPLS-LSP-PING] registry to maintain DS Flags,
Show full document text