One document matched: draft-ietf-mpls-lsp-ping-registry-03.xml
<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="no"?>
<?rfc tocompact="no"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="std" docName="draft-ietf-mpls-lsp-ping-registry-03" ipr="trust200902" updates="4379, 6424">
<front>
<title abbrev="IANA registries for LSP ping">IANA registries for LSP ping Code Points</title>
<author fullname="Bruno Decraene" initials="B." surname="Decraene">
<organization>Orange</organization>
<address>
<email>bruno.decraene@orange.com</email>
</address>
</author>
<author fullname="Nobo Akiya" initials="N."
surname="Akiya">
<organization>Cisco Systems</organization>
<address>
<email>nobo.akiya.dev@gmail.com</email>
</address>
</author>
<author fullname="Carlos Pignataro" initials="C."
surname="Pignataro">
<organization>Cisco Systems</organization>
<address>
<email>cpignata@cisco.com</email>
</address>
</author>
<author fullname="Loa Andersson" initials="L." surname="Andersson">
<organization>Huawei Technologies</organization>
<address>
<email>loa@mail01.huawei.com</email>
</address>
</author>
<author fullname="Sam Aldrin" initials="S."
surname="Aldrin">
<organization>Huawei Technologies</organization>
<address>
<email>aldrin.ietf@gmail.com</email>
</address>
</author>
<date year="2015" />
<abstract>
<t>RFC 4379 and RFC 6424 created name spaces for Multiprotocol Label Switching (MPLS) Label Switched Path (LSP)
Ping. However, those RFCs did not create the corresponding
IANA registries for the Downstream Mapping object Flags (DS Flags), Multipath Type, Pad TLV and Address Types.</t>
<t>There is now a need to make further code point allocations from these
name spaces. This document updates RFC 4379 and RFC 6424 in that it
creates the IANA registries for that purpose.</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t><xref target="RFC4379"></xref> and <xref target="RFC6424"></xref> created name spaces for MPLS LSP Ping. However, those RFCs did not create the corresponding IANA registries for DS Flags, Multipath Type, Pad TLV and Address Types.</t>
<t>There is now a need to make further code point allocations from these
name spaces. In particular <xref target="I-D.ietf-mpls-entropy-lsp-ping"></xref> and <xref target="I-D.ietf-mpls-lsp-ping-lag-multipath"></xref> are requesting allocation for DS Flags and Multipath Type.</t>
<t>This document serves to update <xref target="RFC4379"></xref> and <xref target="RFC6424"></xref> in that it
creates the IANA registries for that purpose.</t>
<t>Note that "DS Flags" and "Multipath Type" are fields included in two TLVs defined in "Multi-Protocol Label Switching (MPLS) Label Switched Paths (LSPs) Ping Parameters - TLVs" registry: Downstream Mapping TLV (value 2) and Downstream Detailed Mapping TLV (value 20). Modification to their registry will affect both TLVs.</t>
</section>
<section anchor="IANA" title="IANA Considerations">
<t> This document requests IANA to create new registries within <xref target="IANA-MPLS-LSP-PING" /> protocol to maintain "DS Flags", "Multipath Type", "Pad TLV" and "Address Types" fields. Name of registries and initial values are described in immediate sub-sections to follow.</t>
<section anchor="DS_Flags" title="DS Flags">
<t><xref target="RFC4379" /> defines the Downstream Mapping (DSMAP) TLV, which has the Type 2 assigned from the "Multi-Protocol Label Switching (MPLS) Label Switched Paths (LSPs) Ping Parameters - TLVs" registry.</t>
<t><xref target="RFC6424" /> defines the Downstream Detailed Mapping (DDMAP) TLV, which has the Type 20 assigned from the "Multi-Protocol Label Switching (MPLS) Label Switched Paths (LSPs) Ping Parameters - TLVs" registry.</t>
<t>DSMAP has been deprecated by DDMAP, but both TLVs share a field: "DS Flags".</t>
<t>The IANA is requested to create and maintain a registry entitled "DS Flags" with the following registration procedure:</t>
<t>
<figure align="left"><preamble></preamble><artwork align="left"> <![CDATA[
Registry Name: DS Flags.
Bit number Name Reference
---------- ---------------------------------------- ---------
7 N: Treat as a Non-IP Packet RFC4379
6 I: Interface and Label Stack Object Request RFC4379
5-0 Unassigned]]>
</artwork></figure>
Assignments of DS Flags are via Standards Action <xref target="RFC5226" />.</t>
</section>
<section anchor="Multipath_Type" title="Multipath Type">
<t>The IANA is requested to create and maintain a registry entitled "Multipath Type".</t>
<t>The registration policies [RFC5226] for this registry are:</t>
<t>
<figure align="left"><preamble></preamble><artwork align="left"> <![CDATA[
0-250 Standards Action
251-254 Experimental Use
255 Standards Action
]]>
</artwork></figure>
</t>
<t>IANA is requested to make the following initial assignments:</t>
<t>
<figure align="left"><preamble></preamble><artwork align="left"> <![CDATA[
Registry Name: Multipath Type.
Value Meaning Reference
---------- ---------------------------------------- ---------
0 no multipath RFC4379
1 Unassigned
2 IP address RFC4379
3 Unassigned
4 IP address range RFC4379
5-7 Unassigned
8 Bit-masked IP address set RFC4379
9 Bit-masked label set RFC4379
10-250 Unassigned
251-254 Experimental This document
255 Reserved This document
]]>
</artwork></figure>
</t>
</section>
<section anchor="Pad_Type" title="Pad Type">
<t>The IANA is requested to create and maintain a registry entitled "Pad Type".</t>
<t>The registration policies [RFC5226] for this registry are:</t>
<t> <figure align="left"><preamble></preamble><artwork align="left"> <![CDATA[
0-250 Standards Action
251-254 Experimental Use
255 Standards Action
]]>
</artwork></figure></t>
<t>IANA is requested to make the following initial assignments:</t>
<t> <figure align="left"><preamble></preamble><artwork align="left"> <![CDATA[
Registry Name: Pad Type.
Value Meaning Reference
---------- ---------------------------------------- ---------
0 Reserved This document
1 Drop Pad TLV from reply RFC4379
2 Copy Pad TLV to reply RFC4379
3-250 Unassigned
251-254 Experimental This document
255 Reserved This document
]]>
</artwork></figure></t>
</section>
<section anchor="Interface_and_Label_Stack" title="Interface and Label Stack Address Type">
<t>The IANA is requested to create and maintain a registry entitled "Interface and Label Stack Address Type".</t>
<t>The registration policies [RFC5226] for this registry are:</t>
<t><figure align="left"><preamble></preamble><artwork align="left"> <![CDATA[
0-250 Standards Action
251-254 Experimental Use
255 Standards Action
]]>
</artwork></figure></t>
<t>IANA is requested to make the following initial assignments:</t>
<t><figure align="left"><preamble></preamble><artwork align="left"> <![CDATA[
Registry Name: Interface and Label Stack Address Type.
Value Meaning Reference
---------- ---------------------------------------- ---------
0 Reserved This document
1 IPv4 Numbered RFC4379
2 IPv4 Unnumbered RFC4379
3 IPv6 Numbered RFC4379
4 IPv6 Unnumbered RFC4379
5-250 Unassigned
251-254 Experimental This document
255 Reserved This document
]]>
</artwork></figure></t>
</section>
</section>
<section anchor="Security" title="Security Considerations" toc="default">
<t>This document simply creates IANA registries for code point defined in <xref target="RFC4379"></xref> and <xref target="RFC6424"></xref>. Thus, there are no new security concerns.</t>
</section>
</middle>
<back>
<references title="Normative References">
<?rfc include="reference.RFC.4379"?>
<?rfc include="reference.RFC.6424"?>
</references>
<references title="Informative References">
<?rfc include="reference.RFC.5226"?>
<?rfc include="reference.I-D.ietf-mpls-entropy-lsp-ping"?>
<?rfc include="reference.I-D.ietf-mpls-lsp-ping-lag-multipath"?>
<reference anchor="IANA-MPLS-LSP-PING" target="http://www.iana.org/assignments/mpls-lsp-ping-parameters/mpls-lsp-ping-parameters.xhtml">
<front>
<title>Multi-Protocol Label Switching (MPLS) Label Switched Paths (LSPs) Ping Parameters</title>
<author><organization>IANA</organization></author>
<date/>
</front>
</reference>
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-23 00:05:38 |