draft-ietf-mpls-lsp-ping-registry-01.txt   draft-ietf-mpls-lsp-ping-registry-02.txt 
Network Working Group B. Decraene Network Working Group B. Decraene
Internet-Draft Orange Internet-Draft Orange
Updates: 4379, 6424 (if approved) N. Akiya Updates: 4379, 6424 (if approved) N. Akiya
Intended status: Standards Track C. Pignataro Intended status: Standards Track C. Pignataro
Expires: August 7, 2015 Cisco Systems Expires: August 20, 2015 Cisco Systems
L. Andersson L. Andersson
S. Aldrin S. Aldrin
Huawei Technologies Huawei Technologies
February 3, 2015 February 16, 2015
IANA registries for LSP ping Code Points IANA registries for LSP ping Code Points
draft-ietf-mpls-lsp-ping-registry-01 draft-ietf-mpls-lsp-ping-registry-02
Abstract Abstract
RFC 4379 and RFC 6424 created name spaces for Multiprotocol Label RFC 4379 and RFC 6424 created name spaces for Multiprotocol Label
Switching (MPLS) Label Switched Path (LSP) Ping. However, those RFCs Switching (MPLS) Label Switched Path (LSP) Ping. However, those RFCs
did not create the corresponding IANA registries for the Downstream did not create the corresponding IANA registries for the Downstream
Mapping object Flags (DS Flags), Multipath Type, Pad TLV and Address Mapping object Flags (DS Flags), Multipath Type, Pad TLV and Address
Types. Types.
There is now a need to make further code point allocations from these There is now a need to make further code point allocations from these
skipping to change at page 1, line 43 skipping to change at page 1, line 43
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 1, 2015. This Internet-Draft will expire on August 20, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 29 skipping to change at page 2, line 29
for DS Flags, Multipath Type, Pad TLV and Address Types. for DS Flags, Multipath Type, Pad TLV and Address Types.
There is now a need to make further code point allocations from these There is now a need to make further code point allocations from these
name spaces. In particular [I-D.ietf-mpls-entropy-lsp-ping] and name spaces. In particular [I-D.ietf-mpls-entropy-lsp-ping] and
[I-D.ietf-mpls-lsp-ping-lag-multipath] are requesting allocation for [I-D.ietf-mpls-lsp-ping-lag-multipath] are requesting allocation for
DS Flags and Multipath Type. DS Flags and Multipath Type.
This document serves to update [RFC4379] and [RFC6424] in that it This document serves to update [RFC4379] and [RFC6424] in that it
creates the IANA registries for that purpose. creates the IANA registries for that purpose.
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.
2. IANA Considerations 2. IANA Considerations
This document requests IANA to create new registries within This document requests IANA to create new registries within
[IANA-MPLS-LSP-PING] protocol to maintain "DS Flags", "Multipath [IANA-MPLS-LSP-PING] protocol to maintain "DS Flags", "Multipath
Type", "Pad TLV" and "Address Types" fields. Name of registries and Type", "Pad TLV" and "Address Types" fields. Name of registries and
initial values are described in immediate sub-sections to follow. initial values are described in immediate sub-sections to follow.
2.1. DS Flags 2.1. DS Flags
[RFC4379] defines the Downstream Mapping TLV, which has the Type 2 [RFC4379] defines the Downstream Mapping TLV, which has the Type 2
skipping to change at page 3, line 15 skipping to change at page 3, line 21
Registry Name: DS Flags. Registry Name: DS Flags.
Bit number Name Reference Bit number Name Reference
---------- ---------------------------------------- --------- ---------- ---------------------------------------- ---------
7 N: Treat as a Non-IP Packet RFC4379 7 N: Treat as a Non-IP Packet RFC4379
6 I: Interface and Label Stack Object Request RFC4379 6 I: Interface and Label Stack Object Request RFC4379
5-0 Unassigned 5-0 Unassigned
Assignments of DS Flags are via Standards Action [RFC5226]. Assignments of DS Flags are via Standards Action [RFC5226].
Note that "DS Flags" is a field 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 "DS
Flags" registry will affect both TLVs.
2.2. Multipath Type 2.2. Multipath Type
The IANA is requested to create and maintain a registry entitled The IANA is requested to create and maintain a registry entitled
"Multipath Type" with the following registration procedure: "Multipath Type".
The registration policies [RFC5226] for this registry are:
0-250 Standards Action
251-254 Experimental
255 Standards Action
IANA is requested to make the following initial assignments:
Registry Name: Multipath Type. Registry Name: Multipath Type.
Value Meaning Reference Value Meaning Reference
---------- ---------------------------------------- --------- ---------- ---------------------------------------- ---------
0 no multipath RFC4379 0 no multipath RFC4379
1 Unassigned 1 Unassigned
2 IP address RFC4379 2 IP address RFC4379
3 Unassigned 3 Unassigned
4 IP address range RFC4379 4 IP address range RFC4379
5-7 Unassigned 5-7 Unassigned
8 Bit-masked IP address set RFC4379 8 Bit-masked IP address set RFC4379
9 Bit-masked label set RFC4379 9 Bit-masked label set RFC4379
10-250 Unassigned 10-250 Unassigned
251-254 Experimental This document 251-254 Experimental This document
255 Reserved This document 255 Reserved This document
Assignments of Multipath Types are via Standards Action [RFC5226].
Note that "Multipath Type" is a field 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
"Multipath Type" registry will affect both TLVs.
2.3. Pad Type 2.3. Pad Type
The IANA is requested to create and maintain a registry entitled "Pad The IANA is requested to create and maintain a registry entitled "Pad
Type" with the following registration procedure: Type".
The registration policies [RFC5226] for this registry are:
0-250 Standards Action
251-254 Experimental
255 Standards Action
IANA is requested to make the following initial assignments:
Registry Name: Pad Type. Registry Name: Pad Type.
Value Meaning Reference Value Meaning Reference
---------- ---------------------------------------- --------- ---------- ---------------------------------------- ---------
0 Reserved RFC4379 0 Reserved RFC4379
1 Drop Pad TLV from reply RFC4379 1 Drop Pad TLV from reply RFC4379
2 Copy Pad TLV to reply RFC4379 2 Copy Pad TLV to reply RFC4379
3-250 Unassigned 3-250 Unassigned
251-254 Experimental This document 251-254 Experimental This document
255 Reserved This document 255 Reserved This document
Assignments of Pad Types are via Standards Action [RFC5226].
2.4. Interface and Label Stack Address Type 2.4. Interface and Label Stack Address Type
The IANA is requested to create and maintain a registry entitled The IANA is requested to create and maintain a registry entitled
"Interface and Label Stack Address Type" with the following "Interface and Label Stack Address Type".
registration procedure:
The registration policies [RFC5226] for this registry are:
0-250 Standards Action
251-254 Experimental
255 Standards Action
IANA is requested to make the following initial assignments:
Registry Name: Interface and Label Stack Address Type. Registry Name: Interface and Label Stack Address Type.
Value Meaning Reference Value Meaning Reference
---------- ---------------------------------------- --------- ---------- ---------------------------------------- ---------
0 Reserved RFC4379 0 Reserved RFC4379
1 IPv4 Numbered RFC4379 1 IPv4 Numbered RFC4379
2 IPv4 Unnumbered RFC4379 2 IPv4 Unnumbered RFC4379
3 IPv6 Numbered RFC4379 3 IPv6 Numbered RFC4379
4 IPv6 Unnumbered RFC4379 4 IPv6 Unnumbered RFC4379
5-250 Unassigned 5-250 Unassigned
251-254 Experimental This document 251-254 Experimental This document
255 Reserved This document 255 Reserved This document
Assignments of Interface and Label Stack Address Types are via
Standards Action [RFC5226].
3. Security Considerations 3. Security Considerations
This document simply creates IANA registries for code point defined This document simply creates IANA registries for code point defined
in [RFC4379] and [RFC6424]. Thus, there are no new security in [RFC4379] and [RFC6424]. Thus, there are no new security
concerns. concerns.
4. Acknowledgements 4. References
TBD.
5. References
5.1. Normative References 4.1. Normative References
[RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol [RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol
Label Switched (MPLS) Data Plane Failures", RFC 4379, Label Switched (MPLS) Data Plane Failures", RFC 4379,
February 2006. February 2006.
[RFC6424] Bahadur, N., Kompella, K., and G. Swallow, "Mechanism for [RFC6424] Bahadur, N., Kompella, K., and G. Swallow, "Mechanism for
Performing Label Switched Path Ping (LSP Ping) over MPLS Performing Label Switched Path Ping (LSP Ping) over MPLS
Tunnels", RFC 6424, November 2011. Tunnels", RFC 6424, November 2011.
5.2. Informative References 4.2. Informative References
[I-D.ietf-mpls-entropy-lsp-ping] [I-D.ietf-mpls-entropy-lsp-ping]
Akiya, N., Swallow, G., Pignataro, C., Malis, A., and S. Akiya, N., Swallow, G., Pignataro, C., Malis, A., and S.
Aldrin, "Label Switched Path (LSP) and Pseudowire (PW) Aldrin, "Label Switched Path (LSP) and Pseudowire (PW)
Ping/Trace over MPLS Network using Entropy Labels (EL)", Ping/Trace over MPLS Network using Entropy Labels (EL)",
draft-ietf-mpls-entropy-lsp-ping-00 (work in progress), draft-ietf-mpls-entropy-lsp-ping-00 (work in progress),
December 2014. December 2014.
[I-D.ietf-mpls-lsp-ping-lag-multipath] [I-D.ietf-mpls-lsp-ping-lag-multipath]
Akiya, N., Swallow, G., Litkowski, S., Decraene, B., and Akiya, N., Swallow, G., Litkowski, S., Decraene, B., and
 End of changes. 15 change blocks. 
34 lines changed or deleted 40 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/