rfc-7537

IANA Registries for LSP Ping Code Points

B. Decraene, N. Akiya, C. Pignataro, L. Andersson, S. Aldrin

date2015-05 streamIETF areartg wgmpls statusPROPOSED STANDARD pages7 canonicalhttps://www.rfc-editor.org/rfc/rfc7537 doi10.17487/RFC7537

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.

obsoleted by

rfc-8029 — Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures

updates

rfc-4379 — Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures
rfc-6424 — Mechanism for Performing Label Switched Path Ping (LSP Ping) over MPLS Tunnels

Extracted elements (8)

design-rationale §1

RFC 4379 and RFC 6424 defined name spaces for MPLS LSP Ping but did not create corresponding IANA registries for DS Flags, Multipath Types, Pad TLVs, and Interface and Label Stack Address Types. This document creates those registries to enable further code point allocations needed by in-progress work such as entropy label ping and LAG multipath support.

mpls, registry

design-rationale §1

The DS Flags and Multipath Type fields are shared between two TLVs: Downstream Mapping (DSMAP, value 2, deprecated) and Downstream Detailed Mapping (DDMAP, value 20). Modification to either the DS Flags or Multipath Types registry therefore affects both TLVs simultaneously.

mpls

interoperability-note §2.1

DSMAP (Downstream Mapping TLV, type 2) has been deprecated in favor of DDMAP (Downstream Detailed Mapping TLV, type 20), but both TLVs share the DS Flags field. Any new DS Flags registry allocations apply to both TLVs.

mpls

registry §2.1

IANA created the 'DS Flags' registry within the MPLS LSP Ping Parameters registry. Registration policy is Standards Action. Initial assignments include bit 7 (N: Treat as Non-IP Packet) and bit 6 (I: Interface and Label Stack Object Request), both from RFC 4379; bits 5-0 are Unassigned.

mpls, registry

registry §2.4

IANA created the 'Interface and Label Stack Address Types' registry for MPLS LSP Ping. Values 0-250 and 255 require Standards Action; 251-254 are Experimental Use. Initial values: 0 (Reserved), 1 (IPv4 Numbered), 2 (IPv4 Unnumbered), 3 (IPv6 Numbered), 4 (IPv6 Unnumbered), all from RFC 4379.

mpls, registry, ip

registry §2.2

IANA created the 'Multipath Types' registry for MPLS LSP Ping. Values 0-250 and 255 require Standards Action; 251-254 are Experimental Use. Initial values include 0 (no multipath), 2 (IP address), 4 (IP address range), 8 (Bit-masked IP address set), and 9 (Bit-masked label set), all from RFC 4379.

mpls, registry

registry §2.3

IANA created the 'Pad Types' registry for MPLS LSP Ping. Values 0-250 and 255 require Standards Action; 251-254 are Experimental Use. Initial assignments: 0 (Reserved), 1 (Drop Pad TLV from reply), 2 (Copy Pad TLV to reply), both from RFC 4379.

mpls, registry

security-consideration §3

This document solely creates IANA registries for code points already defined in RFC 4379 and RFC 6424, introducing no new protocol behavior. Therefore, there are no new security concerns.

security, mpls