--- 1/draft-ietf-mpls-lsp-ping-registry-02.txt 2015-03-06 01:14:35.594975859 -0800 +++ 2/draft-ietf-mpls-lsp-ping-registry-03.txt 2015-03-06 01:14:35.610976247 -0800 @@ -1,23 +1,23 @@ Network Working Group B. Decraene Internet-Draft Orange Updates: 4379, 6424 (if approved) N. Akiya Intended status: Standards Track C. Pignataro -Expires: August 20, 2015 Cisco Systems +Expires: September 7, 2015 Cisco Systems L. Andersson S. Aldrin Huawei Technologies - February 16, 2015 + March 6, 2015 IANA registries for LSP ping Code Points - draft-ietf-mpls-lsp-ping-registry-02 + draft-ietf-mpls-lsp-ping-registry-03 Abstract 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. There is now a need to make further code point allocations from these @@ -32,21 +32,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on August 20, 2015. + This Internet-Draft will expire on September 7, 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 @@ -78,27 +78,27 @@ 2. IANA Considerations This document requests IANA to create new registries within [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. 2.1. DS Flags - [RFC4379] defines the Downstream Mapping TLV, which has the Type 2 - assigned from the "Multi-Protocol Label Switching (MPLS) Label + [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. - [RFC6424] defines the Downstream Detailed Mapping TLV, which has the - Type 20 assigned from the "Multi-Protocol Label Switching (MPLS) - Label Switched Paths (LSPs) Ping Parameters - TLVs" registry. + [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. DSMAP has been deprecated by DDMAP, but both TLVs share a field: "DS Flags". The IANA is requested to create and maintain a registry entitled "DS Flags" with the following registration procedure: Registry Name: DS Flags. Bit number Name Reference @@ -110,21 +110,21 @@ Assignments of DS Flags are via Standards Action [RFC5226]. 2.2. Multipath Type The IANA is requested to create and maintain a registry entitled "Multipath Type". The registration policies [RFC5226] for this registry are: 0-250 Standards Action - 251-254 Experimental + 251-254 Experimental Use 255 Standards Action IANA is requested to make the following initial assignments: Registry Name: Multipath Type. Value Meaning Reference ---------- ---------------------------------------- --------- 0 no multipath RFC4379 1 Unassigned @@ -139,54 +139,54 @@ 255 Reserved This document 2.3. Pad Type The IANA is requested to create and maintain a registry entitled "Pad Type". The registration policies [RFC5226] for this registry are: 0-250 Standards Action - 251-254 Experimental + 251-254 Experimental Use 255 Standards Action IANA is requested to make the following initial assignments: Registry Name: Pad Type. Value Meaning Reference ---------- ---------------------------------------- --------- - 0 Reserved RFC4379 + 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 2.4. Interface and Label Stack Address Type The IANA is requested to create and maintain a registry entitled "Interface and Label Stack Address Type". The registration policies [RFC5226] for this registry are: 0-250 Standards Action - 251-254 Experimental + 251-254 Experimental Use 255 Standards Action IANA is requested to make the following initial assignments: Registry Name: Interface and Label Stack Address Type. Value Meaning Reference ---------- ---------------------------------------- --------- - 0 Reserved RFC4379 + 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 3. Security Considerations @@ -235,21 +235,21 @@ Authors' Addresses Bruno Decraene Orange Email: bruno.decraene@orange.com Nobo Akiya Cisco Systems - Email: nobo@cisco.com + Email: nobo.akiya.dev@gmail.com Carlos Pignataro Cisco Systems Email: cpignata@cisco.com Loa Andersson Huawei Technologies Email: loa@mail01.huawei.com