draft-akiya-mpls-lsp-ping-lag-multipath-04.txt   draft-akiya-mpls-lsp-ping-lag-multipath-05.txt 
Internet Engineering Task Force N. Akiya Internet Engineering Task Force N. Akiya
Internet-Draft G. Swallow Internet-Draft G. Swallow
Updates: 4379,6424 (if approved) Cisco Systems Updates: 4379,6424 (if approved) Cisco Systems
Intended status: Standards Track S. Litkowski Intended status: Standards Track S. Litkowski
Expires: June 2, 2015 B. Decraene Expires: June 24, 2015 B. Decraene
Orange Orange
J. Drake J. Drake
Juniper Networks Juniper Networks
November 29, 2014 December 21, 2014
Label Switched Path (LSP) Ping/Trace Multipath Support for Label Switched Path (LSP) Ping/Trace Multipath Support for
Link Aggregation Group (LAG) Interfaces Link Aggregation Group (LAG) Interfaces
draft-akiya-mpls-lsp-ping-lag-multipath-04 draft-akiya-mpls-lsp-ping-lag-multipath-05
Abstract Abstract
This document defines an extension to the MPLS Label Switched Path This document defines an extension to the MPLS Label Switched Path
(LSP) Ping and Traceroute as specified in RFC 4379. The extension (LSP) Ping and Traceroute as specified in RFC 4379. The extension
allows the MPLS LSP Ping and Traceroute to discover and exercise allows the MPLS LSP Ping and Traceroute to discover and exercise
specific paths of Layer 2 (L2) Equal-Cost Multipath (ECMP) over Link specific paths of Layer 2 (L2) Equal-Cost Multipath (ECMP) over Link
Aggregation Group (LAG) interfaces. Aggregation Group (LAG) interfaces.
This document updates RFC4379 and RFC6424. This document updates RFC4379 and RFC6424.
skipping to change at page 1, line 48 skipping to change at page 1, line 48
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 June 2, 2015. This Internet-Draft will expire on June 24, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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 26 skipping to change at page 2, line 26
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Background . . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Background . . . . . . . . . . . . . . . . . . . . . . . 3
2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Mechanism to Discover L2 ECMP Multipath . . . . . . . . . . . 5 3. LSR Capability Discovery . . . . . . . . . . . . . . . . . . 6
3.1. Initiator LSR Procedures . . . . . . . . . . . . . . . . 5 4. Mechanism to Discover L2 ECMP Multipath . . . . . . . . . . . 7
3.2. Responder LSR Procedures . . . . . . . . . . . . . . . . 5 4.1. Initiator LSR Procedures . . . . . . . . . . . . . . . . 7
3.3. Additional Initiator LSR Procedures . . . . . . . . . . . 7 4.2. Responder LSR Procedures . . . . . . . . . . . . . . . . 7
4. Mechanism to Validate L2 ECMP Traversal . . . . . . . . . . . 8
4.1. Initiator LSR Procedures . . . . . . . . . . . . . . . . 8
4.2. Responder LSR Procedures . . . . . . . . . . . . . . . . 9
4.3. Additional Initiator LSR Procedures . . . . . . . . . . . 9 4.3. Additional Initiator LSR Procedures . . . . . . . . . . . 9
5. LAG Interface Info TLV . . . . . . . . . . . . . . . . . . . 11 5. Mechanism to Validate L2 ECMP Traversal . . . . . . . . . . . 10
6. DDMAP TLV DS Flags: G . . . . . . . . . . . . . . . . . . . . 12 5.1. Incoming LAG Member Links Verification . . . . . . . . . 11
7. Interface Index Sub-TLV . . . . . . . . . . . . . . . . . . . 12 5.1.1. Initiator LSR Procedures . . . . . . . . . . . . . . 11
8. Detailed Interface and Label Stack TLV . . . . . . . . . . . 13 5.1.2. Responder LSR Procedures . . . . . . . . . . . . . . 11
8.1. Sub-TLVs . . . . . . . . . . . . . . . . . . . . . . . . 15 5.1.3. Additional Initiator LSR Procedures . . . . . . . . . 12
8.1.1. Incoming Label Stack Sub-TLV . . . . . . . . . . . . 15 5.2. Individual End-to-End Path Verification . . . . . . . . . 13
8.1.2. Incoming Interface Index Sub-TLV . . . . . . . . . . 16 6. LSR Capability TLV . . . . . . . . . . . . . . . . . . . . . 14
9. Security Considerations . . . . . . . . . . . . . . . . . . . 17 7. LAG Description Indicator Flag: G . . . . . . . . . . . . . . 15
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 8. Local Interface Index Sub-TLV . . . . . . . . . . . . . . . . 16
10.1. LAG Interface Info TLV . . . . . . . . . . . . . . . . . 17 9. Remote Interface Index Sub-TLV . . . . . . . . . . . . . . . 17
10.1.1. LAG Interface Info Flags . . . . . . . . . . . . . . 18 10. Detailed Interface and Label Stack TLV . . . . . . . . . . . 18
10.2. Interface Index Sub-TLV . . . . . . . . . . . . . . . . 18 10.1. Sub-TLVs . . . . . . . . . . . . . . . . . . . . . . . . 20
10.2.1. Interface Index Flags . . . . . . . . . . . . . . . 18 10.1.1. Incoming Label Stack Sub-TLV . . . . . . . . . . . . 20
10.3. Detailed Interface and Label Stack TLV . . . . . . . . . 19 10.1.2. Incoming Interface Index Sub-TLV . . . . . . . . . . 20
10.3.1. Sub-TLVs for TLV Type TBD3 . . . . . . . . . . . . . 19 11. Security Considerations . . . . . . . . . . . . . . . . . . . 21
10.4. DS Flags . . . . . . . . . . . . . . . . . . . . . . . . 19 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20 12.1. LSR Capability TLV . . . . . . . . . . . . . . . . . . . 22
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 20 12.1.1. LSR Capability Flags . . . . . . . . . . . . . . . . 22
12.1. Normative References . . . . . . . . . . . . . . . . . . 20 12.2. Local Interface Index Sub-TLV . . . . . . . . . . . . . 22
12.2. Informative References . . . . . . . . . . . . . . . . . 20 12.2.1. Interface Index Flags . . . . . . . . . . . . . . . 23
Appendix A. LAG with L2 Switch Issues . . . . . . . . . . . . . 21 12.3. Remote Interface Index Sub-TLV . . . . . . . . . . . . . 23
A.1. Equal Numbers of LAG Members . . . . . . . . . . . . . . 21 12.4. Detailed Interface and Label Stack TLV . . . . . . . . . 23
A.2. Deviating Numbers of LAG Members . . . . . . . . . . . . 21 12.4.1. Sub-TLVs for TLV Type TBD4 . . . . . . . . . . . . . 24
A.3. LAG Only on Right . . . . . . . . . . . . . . . . . . . . 21 12.5. DS Flags . . . . . . . . . . . . . . . . . . . . . . . . 24
A.4. LAG Only on Left . . . . . . . . . . . . . . . . . . . . 22 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 25
14.1. Normative References . . . . . . . . . . . . . . . . . . 25
14.2. Informative References . . . . . . . . . . . . . . . . . 25
Appendix A. LAG with L2 Switch Issues . . . . . . . . . . . . . 26
A.1. Equal Numbers of LAG Members . . . . . . . . . . . . . . 26
A.2. Deviating Numbers of LAG Members . . . . . . . . . . . . 26
A.3. LAG Only on Right . . . . . . . . . . . . . . . . . . . . 26
A.4. LAG Only on Left . . . . . . . . . . . . . . . . . . . . 27
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27
1. Introduction 1. Introduction
1.1. Terminology 1.1. Terminology
The following acronyms/terminologies are used in this document: The following acronyms/terms are used in this document:
o MPLS - Multiprotocol Label Switching. o MPLS - Multiprotocol Label Switching.
o LSP - Label Switched Path. o LSP - Label Switched Path.
o LSR - Label Switching Router. o LSR - Label Switching Router.
o ECMP - Equal-Cost Multipath. o ECMP - Equal-Cost Multipath.
o LAG - Link Aggregation Group. o LAG - Link Aggregation Group.
o Initiator LSR - LSR which sends MPLS echo request. o Initiator LSR - LSR which sends MPLS echo request.
o Responder LSR - LSR which receives MPLS echo request and sends o Responder LSR - LSR which receives MPLS echo request and sends
MPLS echo reply. MPLS echo reply.
1.2. Background 1.2. Background
The MPLS Label Switched Path (LSP) Ping and Traceroute as specified The MPLS Label Switched Path (LSP) Ping and Traceroute as specified
in [RFC4379] are powerful tools designed to diagnose all available in [RFC4379] are powerful tools designed to diagnose all available
layer 3 (L3) paths of LSPs, i.e. provides diagnostic coverage of L3 layer 3 (L3) paths of LSPs, i.e., provides diagnostic coverage of L3
Equal-Cost Multipath (ECMP). In many MPLS networks, Link Aggregation Equal-Cost Multipath (ECMP). In many MPLS networks, Link Aggregation
Group (LAG) as defined in [IEEE802.1AX], which provide Layer 2 (L2) Group (LAG) as defined in [IEEE802.1AX], which provide Layer 2 (L2)
ECMP, are often used for various reasons. MPLS LSP Ping and ECMP, are often used for various reasons. MPLS LSP Ping and
Traceroute tools were not designed to discover and exercise specific Traceroute tools were not designed to discover and exercise specific
paths of L2 ECMP. Result raises a limitation for following scenario paths of L2 ECMP. The result raises a limitation for following
when LSP X traverses over LAG Y: scenario when LSP X traverses over LAG Y:
o Label switching of LSP X over one or more member links of LAG Y is o Label switching of LSP X over one or more member links of LAG Y
succeeding. have succeeded.
o Label switching of LSP X over one or more member links of LAG Y is o Label switching of LSP X over one or more member links of LAG Y
failing. have failed.
o MPLS echo request for LSP X over LAG Y is load balanced over a o MPLS echo request for LSP X over LAG Y is load balanced over a
member link which is label switching successfully. member link which is label switching successfully.
With above scenario, MPLS LSP Ping and Traceroute will not be able to With the above scenario, MPLS LSP Ping and Traceroute will not be
detect the MPLS switching failure of problematic member link(s) of able to detect the label switching failure of problematic member
the LAG. In other words, lack of L2 ECMP discovery and exercise link(s) of the LAG. In other words, lack of L2 ECMP diagnostic
capability can produce an outcome where MPLS LSP Ping and Traceroute coverage can produce an outcome where MPLS LSP Ping and Traceroute
can be blind to label switching failures over LAG interface that are can be blind to label switching failures over problematic LAG
impacting MPLS traffic. It is, thus, desirable to extend the MPLS interface. It is, thus, desirable to extend the MPLS LSP Ping and
LSP Ping and Traceroute to have deterministic diagnostic coverage of Traceroute to have deterministic diagnostic coverage of LAG
LAG interfaces. interfaces.
Creation of this document was motivated by issues encountered in live Creation of this document was motivated by issues encountered in live
networks. networks.
2. Overview 2. Overview
This document defines an extension to the MPLS LSP Ping and This document defines an extension to the MPLS LSP Ping and
Traceroute to describe Multipath Information for LAG member links Traceroute to describe Multipath Information for LAG member links
separately, thus allowing MPLS LSP Ping and Traceroute to discover separately, thus allowing MPLS LSP Ping and Traceroute to discover
and exercise specific paths of L2 ECMP over LAG interfaces. Reader and exercise specific paths of L2 ECMP over LAG interfaces. Reader
skipping to change at page 5, line 18 skipping to change at page 5, line 31
1. Downstream C over Non-LAG (upper path). 1. Downstream C over Non-LAG (upper path).
2. First Downstream C over LAG (middle path). 2. First Downstream C over LAG (middle path).
3. Second Downstream C over LAG (middle path). 3. Second Downstream C over LAG (middle path).
4. Downstream D over Non-LAG (lower path). 4. Downstream D over Non-LAG (lower path).
This document defines: This document defines:
o In Section 3, a mechanism to discover L2 ECMP multipath o In Section 3, a mechanism discover capabilities of responder LSRs;
o In Section 4, a mechanism to discover L2 ECMP multipath
information; information;
o In Section 4, a mechanism to validate L2 ECMP traversal in some o In Section 5, a mechanism to validate L2 ECMP traversal in some
LAG provisioning models; LAG provisioning models;
o In Section 5, the LAG Interface Info TLV; o In Section 6, the LSR Capability TLV;
o In Section 6, the LAG Description Indicator flag; o In Section 7, the LAG Description Indicator flag;
o In Section 7, the Interface Index Sub-TLV; o In Section 8, the Local Interface Index Sub-TLV;
o In Section 8, the Detailed Interface and Label Stack TLV; o In Section 9, the Remote Interface Index Sub-TLV;
o In Section 10, the Detailed Interface and Label Stack TLV;
o In Appendix A, issues with LAG having an L2 Switch. o In Appendix A, issues with LAG having an L2 Switch.
Note that the mechanism described in this document does not impose Note that the mechanism described in this document does not impose
any changes to scenarios where an LSP is pinned down to a particular any changes to scenarios where an LSP is pinned down to a particular
LAG member (i.e. the LAG is not treated as one logical interface by LAG member (i.e. the LAG is not treated as one logical interface by
the LSP). the LSP).
3. Mechanism to Discover L2 ECMP Multipath Also note that many LAGs are built from p2p links, and thus router X
and router X+1 have the same number of LAG members. It is possible
to build LAGs asymmetrically by using Ethernet switches in the
middle. Appendix A lists some cases which this document does not
address; if an operator deploys LAGs in a manner similar to what's
shown in Appendix A, the mechanisms in this document may not suit
them.
3.1. Initiator LSR Procedures 3. LSR Capability Discovery
The MPLS echo request carries a DDMAP and the LAG Interface Info TLV The MPLS Ping operates by an initiator LSR sending an MPLS echo
(described in Section 5) to indicate that separate load balancing request message and receiving back a corresponding MPLS echo reply
information for each L2 nexthop over LAG is desired in MPLS echo message from a responder LSR. The MPLS Traceroute operates in a
reply. similar way except the initiator LSR potentially sends multiple MPLS
echo request messages with incrementing TTL values.
3.2. Responder LSR Procedures There has been many extensions to the MPLS Ping and Traceroute
mechanism over the years. Thus it is often useful, and sometimes
necessary, for the initiator LSR to deterministically disambiguate
the difference between:
Responder LSRs that understand the LAG Interface Info TLV but are o The responder LSR sent the MPLS echo reply message with contents C
unable to describe outgoing LAG member links separately are to use because it has feature X, Y and Z implemented.
the following procedures:
o The responder LSR MUST add the LAG Interface Info TLV in the MPLS o The responder LSR sent the MPLS echo reply message with contents C
echo reply. This will allow the initiator LSR to understand that because it has subset of features X, Y and Z implemented but not
the responder LSR understood the LAG Interface Info TLV. all.
o The responder LSR MUST clear the Downstream LAG Info Accommodation o The responder LSR sent the MPLS echo reply message with contents C
flag in the LAG Interface Info Flags field of the LAG Interface because it does not have features X, Y and Z implemented.
Info TLV. This will allow the initiator LSR to understand that
the responder LSR understood the LAG Interface Info TLV but cannot
describe outgoing LAG member links separately in the DDMAP.
The responder LSRs that understands the LAG Interface Info TLV and To allow the initiator LSR to disambiguate the above differences,
are able to describe outgoing LAG member links separately are to use this document defines the LSR Capability TLV (described in
the follow procedures, regardless of whether or not outgoing Section 6). When the initiator LSR wishes to discover the
capabilities of the responder LSR, the initiator LSR includes the LSR
Capability TLV in the MPLS echo request message. When the responder
LSR receives an MPLS echo reply message with the LSR Capability TLV
included, then the responder LSR MUST include the LSR Capability TLV
in the MPLS echo reply message with the LSR Capability TLV describing
features and extensions supported by the local LSR.
It is RECOMMENDED that implementations supporting the LAG Multipath
extensions defined in this document include the LSR Capability TLV in
MPLS echo request messages.
4. Mechanism to Discover L2 ECMP Multipath
4.1. Initiator LSR Procedures
The MPLS echo request carries a DDMAP with the "LAG Description
Indicator flag" (G) set in the DS Flags to indicate that separate
load balancing information for each L2 nexthop over LAG is desired in
MPLS echo reply. The new "LAG Description Indicator flag" is
described in Section 7.
4.2. Responder LSR Procedures
This section describes the handling of the new TLVs by nodes which
understand the "LAG Description Indicator flag". There are two cases
- nodes which understand the "LAG Description Indicator flag" but
which for some reason cannot describe LAG members separately, and
nodes which both understand the "LAG Description Indicator flag" and
are able to describe LAG members separately. Note that Section 6,
Section 8 and Section 9 describe the new TLVs referenced by this
section , and looking over the definition of the new TLVs first may
make it easier to read this section.
A responder LSR that understand the "LAG Description Indicator flag"
but is not capable of describing outgoing LAG member links separately
uses the following procedures:
o If the received MPLS echo request message had the LSR Capability
TLV, the responder LSR MUST include the LSR Capability TLV in the
MPLS echo reply message.
o The responder LSR MUST clear the "Downstream LAG Info
Accommodation flag" in the LSR Capability Flags field of the LSR
Capability TLV. This will allow the initiator LSR to understand
that the responder LSR cannot describe outgoing LAG member links
separately in the DDMAP.
A responder LSR that understands the "LAG Description Indicator flag"
and is capable of describing outgoing LAG member links separately
uses the follow procedures, regardless of whether or not outgoing
interfaces include LAG interfaces: interfaces include LAG interfaces:
o The responder LSR MUST add the LAG Interface Info TLV in the MPLS o If the received MPLS echo request message had the LSR Capability
echo reply. TLV, the responder LSR MUST include the LSR Capability TLV in the
MPLS echo reply message.
o The responder LSR MUST set the Downstream LAG Info Accommodation o The responder LSR MUST set the "Downstream LAG Info Accommodation
flag in the LAG Interface Info Flags field of the LAG Interface flag" in the LSR Capability Flags field of the LSR Capability TLV.
Info TLV.
o For each downstream that is a LAG interface: o For each downstream that is a LAG interface:
* The responder LSR MUST add DDMAP in the MPLS echo reply. * The responder LSR MUST add DDMAP in the MPLS echo reply.
* The responder LSR MUST set the LAG Description Indicator flag * The responder LSR MUST set the "LAG Description Indicator flag"
in the DS Flags field (described in Section 6) of the DDMAP. in the DS Flags field of the DDMAP.
* In the DDMAP, Interface Index Sub-TLV and Multipath Data Sub- * In the DDMAP, Local Interface Index Sub-TLV, Remote Interface
TLV are to describe each LAG member link. All other fields of Index Sub-TLV and Multipath Data Sub-TLV are to describe each
the DDMAP are to describe the LAG interface. LAG member link. All other fields of the DDMAP are to describe
the LAG interface.
* For each LAG member link of this LAG interface: * For each LAG member link of this LAG interface:
+ The responder LSR MUST add an Interface Index Sub-TLV + The responder LSR MUST add a Local Interface Index Sub-TLV
(described in Section 7) with the LAG Member Link Indicator (described in Section 8) with the "LAG Member Link Indicator
flag set in the Interface Index Flags field, describing this flag" set in the Interface Index Flags field, describing the
LAG member link. interface index of this outgoing LAG member link (the local
interface index is assigned by the local LSR).
+ The responder LSR MAY add a Remote Interface Index Sub-TLV
(described in Section 9) with the "LAG Member Link Indicator
flag" set in the Interface Index Flags field, describing the
interface index of the incoming LAG member link on the
downstream LSR (this interface index is assigned by the
downstream LSR). How the local LSR obtains the interface
index of the LAG member link on the downstream LSR is
outside the scope of this document.
+ The responder LSR MUST add an Multipath Data Sub-TLV for + The responder LSR MUST add an Multipath Data Sub-TLV for
this LAG member link, if received DDMAP requested multipath this LAG member link, if received DDMAP requested multipath
information. information.
Based on the procedures described above, every LAG member link will Based on the procedures described above, every LAG member link will
have the Interface Index Sub-TLV and the Multipath Data Sub-TLV have a Local Interface Index Sub-TLV and a Multipath Data Sub-TLV
entries in the DDMAP. When both the Interface Index Sub-TLV and the entries in the DDMAP. The order of the Sub-TLVs in the DDMAP for a
LAG member link MUST be Local Interface Index Sub-TLV immediately
followed by Multipath Data Sub-TLV. A LAG member link may also have
a corresponding Remote Interface Index Sub-TLV. When a Local
Interface Index Sub-TLV, a Remote Interface Index-Sub-TLV and a
Multipath Data Sub-TLV are placed in the DDMAP to describe a LAG Multipath Data Sub-TLV are placed in the DDMAP to describe a LAG
member link, Interface Index Sub-TLV MUST be added first with member link, they MUST be placed in the order of Local Interface
Multipath Data Sub-TLV immediately following. Index Sub-TLV, Remote Interface Index-Sub-TLV and Multipath Data Sub-
TLV.
For example, a responder LSR possessing a LAG interface with two A responder LSR possessing a LAG interface with two member links
member links would send the following DDMAP for this LAG interface: would send the following DDMAP for this LAG interface:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DDMAP fields describing LAG interface with DS Flags G set | ~ DDMAP fields describing LAG interface with DS Flags G set ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Index Sub-TLV of LAG member link #1 | |[MANDATORY] Local Interface Index Sub-TLV of LAG member link #1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multipath Data Sub-TLV LAG member link #1 | |[OPTIONAL] Remote Interface Index Sub-TLV of LAG member link #1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Index Sub-TLV of LAG member link #2 | |[MANDATORY] Multipath Data Sub-TLV LAG member link #1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multipath Data Sub-TLV LAG member link #2 | |[MANDATORY] Local Interface Index Sub-TLV of LAG member link #2|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|[OPTIONAL] Remote Interface Index Sub-TLV of LAG member link #2|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|[MANDATORY] Multipath Data Sub-TLV LAG member link #2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Label Stack Sub-TLV | | Label Stack Sub-TLV |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: Example of DDMAP in MPLS Echo Reply Figure 2: Example of DDMAP in MPLS Echo Reply
3.3. Additional Initiator LSR Procedures When none of the received multipath information maps to a particular
LAG member link, then the responder LSR MUST still place the Local
Interface Index Sub-TLV and the Multipath Data Sub-TLV for that LAG
member link in the DDMAP, with the Multipath Length field of the
Multipath Data Sub-TLV being zero.
Above procedures allow an initiator LSR to: 4.3. Additional Initiator LSR Procedures
o Require the responder LSR to always add the LAG Interface Info TLV The procedures above allow an initiator LSR to:
in the MPLS echo reply. This allows the initiator LSR to identify
whether or not the responder LSR understands the LAG Interface
Info TLV and can describe outgoing LAG member links separately.
o Utilize the value of the LAG Description Indicator flag in DS o Identify whether or not the responder LSR can describe outgoing
Flags to identify whether each DDMAP describes a LAG interface or LAG member links separately, by looking at the LSR Capability TLV.
a non-LAG interface.
o Utilize the value of the "LAG Description Indicator flag" in DS
Flags to identify whether each received DDMAP describes a LAG
interface or a non-LAG interface.
o Obtain multipath information which is expected to traverse the o Obtain multipath information which is expected to traverse the
specific LAG member link described by corresponding interface specific LAG member link described by corresponding interface
index. index.
When an initiator LSR receives a DDMAP containing LAG member When an initiator LSR receives a DDMAP containing LAG member
information from a downstream LSR with TTL=n, then the subsequent information from a downstream LSR with TTL=n, then the subsequent
DDMAP sent by the initiator LSR to the downstream LSR with TTL=n+1 DDMAP sent by the initiator LSR to the downstream LSR with TTL=n+1
through a particular LAG member link MUST be updated with following through a particular LAG member link MUST be updated with following
procedures: procedures:
o The Interface Index Sub-TLVs MUST NOT be present in the sending o The Local Interface Index Sub-TLVs MUST be removed in the sending
DDMAP. DDMAP.
o The Multipath Data Sub-TLVs SHOULD be updated to include just the o If the Remote Interface Index Sub-TLVs were present and the
one corresponding to the LAG member link being traversed. The initiator LSR is traversing over a specific LAG member link, then
initiator LSR MAY combine the Multipath Data Sub-TLVs for all LAG the Remote Interface Index Sub-TLV corresponding to the LAG member
member links into a single Multipath Data Sub-TLV, but there MUST link being traversed SHOULD be included in the sending DDMAP. All
be only one Multipath Data Sub-TLV in the sending DDMAP. other Remote Interface Index Sub-TLVs MUST be removed from the
sending DDMAP.
o The Multipath Data Sub-TLVs MUST be updated to include just one
Multipath Data Sub-TLV. The initiator MAY keep just the Multipath
Data Sub-TLV corresponding to the LAG member link being traversed,
or combine the Multipath Data Sub-TLVs for all LAG member links
into a single Multipath Data Sub-TLV when diagnosing further
downstream LSRs.
o All other fields of the DDMAP are to comply with procedures o All other fields of the DDMAP are to comply with procedures
described in [RFC6424]. described in [RFC6424].
Using the DDMAP example described in the Figure 2, the DDMAP being Using the DDMAP example described in the Figure 2, the DDMAP being
sent by the initiator LSR through LAG member link #1 to the next sent by the initiator LSR through LAG member link #1 to the next
downstream LSR should be: downstream LSR should be:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DDMAP fields describing LAG interface with DS Flags G set | ~ DDMAP fields describing LAG interface with DS Flags G set ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|[OPTIONAL] Remote Interface Index Sub-TLV of LAG member link #1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multipath Data Sub-TLV LAG member link #1 | | Multipath Data Sub-TLV LAG member link #1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Label Stack Sub-TLV | | Label Stack Sub-TLV |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: Example of DDMAP in MPLS Echo Request Figure 3: Example of DDMAP in MPLS Echo Request
4. Mechanism to Validate L2 ECMP Traversal 5. Mechanism to Validate L2 ECMP Traversal
This document does not update the FEC validation procedures nor the Section 4 defines the responder LSR procedures to constructs a DDMAP
DDMAP validation procedures, specified in [RFC4379] and [RFC6424] for a downstream LAG, and also defines that inclusion of the Remote
respectively. Rather this document provides the mechanism for the Interface Index Sub-TLVs describing the incoming LAG member links of
the downstream LSR is optional. The reason why it is optional for
the responder LSR to include the Remote Interface Index Sub-TLVs is
that this information from the downstream LSR is often not available
on the responder LSR. In such case, the traversal of LAG member
links can be validated with procedures described in Section 5.1. If
LSRs can provide the Remote Interface Index Sub-TLVs in DDMAP
objects, then the validation procedures described in Section 5.2 can
be used.
5.1. Incoming LAG Member Links Verification
Without downstream LSRs returning remote Interface Index Sub-TLVs in
the DDMAP, validation of the LAG member link traversal requires that
initiator LSR traverses all available LAG member links and taking the
results through a logic. This section provides the mechanism for the
initiator LSR to obtain additional information from the downstream initiator LSR to obtain additional information from the downstream
LSRs when incoming and/or outgoing interfaces are LAGs. With this LSRs and describes the additional logic in the initiator LSR to
additional information, it is the responsibility of the initiator LSR validate the L2 ECMP traversal.
to validate the L2 ECMP traversal.
4.1. Initiator LSR Procedures 5.1.1. Initiator LSR Procedures
The MPLS echo request is sent with a DDMAP with DS Flags I set and The MPLS echo request is sent with a DDMAP with the "Interface and
the optional LAG Interface Info TLV to indicate the request for Label Stack Object Request flag" and "LAG Description Indicator flag"
Detailed Interface and Label Stack TLV with additional LAG member set in the DS Flags to indicate the request for Detailed Interface
link information (i.e. interface index) in the MPLS echo reply. and Label Stack TLV with additional LAG member link information (i.e.
interface index) in the MPLS echo reply.
4.2. Responder LSR Procedures 5.1.2. Responder LSR Procedures
Responder LSRs that understands the LAG Interface Info TLV but unable A responder LSR that understands the "LAG Description Indicator flag"
to describe incoming LAG member link are to use following procedures: but is not capable of describing incoming LAG member link is to use
following procedures:
o The responder LSR MUST add the LAG Interface Info TLV in the MPLS o If the received MPLS echo request message had the LSR Capability
echo reply. This will allow the initiator LSR to understand that TLV, the responder LSR MUST include the LSR Capability TLV in the
the responder LSR understood the LAG Interface Info TLV. MPLS echo reply message.
o The responder LSR MUST clear The Upstream LAG Info Accommodation o The responder LSR MUST clear the "Upstream LAG Info Accommodation
flag in the LAG Interface Info Flags field of the LAG Interface flag" in the LSR Capability Flags field of the LSR Capability TLV.
Info TLV. This will allow the initiator LSR to understand that This will allow the initiator LSR to understand that the responder
the responder LSR understood the LAG Interface Info TLV but cannot LSR cannot describe incoming LAG member link.
describe incoming LAG member link.
The responder LSRs that understands the LAG Interface Info TLV and A responder LSR that understands the "LAG Description Indicator flag"
able to describe incoming LAG member link MUST use the following and is capable of describing incoming LAG member link MUST use the
procedures, regardless of whether or not incoming interface was a LAG following procedures, regardless of whether or not incoming interface
interface: was a LAG interface:
o Add the LAG Interface Info TLV in the MPLS echo reply to provide o If the received MPLS echo request message had the LSR Capability
acknowledgement back to the initiator. The Upstream LAG Info TLV, the responder LSR MUST include the LSR Capability TLV in the
Accommodation flag MUST be set in the LAG Interface Info Flags MPLS echo reply message.
field.
o When the received DDMAP had DS Flags I set, add the Detailed o The responder LSR MUST set the "Upstream LAG Info Accommodation
Interface and Label Stack TLV (described in Section 8) in the MPLS flag" in the LSR Capability Flags field of the LSR Capability TLV.
echo reply.
o When the received DDMAP had DS Flags I set and incoming interface o When the received DDMAP had "Interface and Label Stack Object
was a LAG, add the Incoming Interface Index Sub-TLV (described in Request flag" set in the DS Flags field, the responder LSR MUST
Section 8.1.2). The LAG Member Link Indicator flag MUST be set in add the Detailed Interface and Label Stack TLV (described in
the Interface Index Flags field, and the Interface Index field set Section 10) in the MPLS echo reply.
to the LAG member link which received the MPLS echo request.
o When the received DDMAP had "Interface and Label Stack Object
Request flag" set in the DS Flags field and the incoming interface
was a LAG, the responder LSR MUST add the Incoming Interface Index
Sub-TLV (described in Section 10.1.2) in the Detailed Interface
and Label Stack TLV. The "LAG Member Link Indicator flag" MUST be
set in the Interface Index Flags field, and the Interface Index
field set to the LAG member link which received the MPLS echo
request.
These procedures allow initiator LSR to: These procedures allow initiator LSR to:
o Identify whether or not the responder LSR understands the LAG o Identify whether or not the responder LSR can describe the
Interface Info TLV and can describe the incoming LAG member links incoming LAG member link, by looking at the LSR Capability TLV.
(the responder LSR is mandated to always add the LAG Interface
Info TLV in the MPLS echo reply).
4.3. Additional Initiator LSR Procedures o Utilize the Incoming Interface Index Sub-TLV in the Detailed
Interface and Label Stack TLV to identify, if the incoming
interface was a LAG, the identity of the incoming LAG member.
Along with procedures described in Section 3, described procedures in 5.1.3. Additional Initiator LSR Procedures
this section will allow an initiator LSR to know:
Along with procedures described in Section 4, the procedures
described in this section will allow an initiator LSR to know:
o The expected load balance information of every LAG member link, at o The expected load balance information of every LAG member link, at
LSR with TTL=n. LSR with TTL=n.
o With specific entropy, the expected interface index of the o With specific entropy, the expected interface index of the
outgoing LAG member link at TTL=n. outgoing LAG member link at TTL=n.
o With specific entropy, the interface index of the incoming LAG o With specific entropy, the interface index of the incoming LAG
member link at TTL=n+1. member link at TTL=n+1.
Expectation is that there's a relationship between the interface Expectation is that there's a relationship between the interface
index of the outgoing LAG member link at TTL=n and the interface index of the outgoing LAG member link at TTL=n and the interface
index of the incoming LAG member link at TTL=n+1 for all discovered index of the incoming LAG member link at TTL=n+1 for all discovered
entropies. In other words, set of entropies that load balances to entropies. In other words, set of entropies that load balances to
outgoing LAG member link X at TTL=n should all reach the nexthop on outgoing LAG member link X at TTL=n should all reach the nexthop on
same incoming LAG member link Y at TTL=n+1. same incoming LAG member link Y at TTL=n+1.
With additional logics added in the initiator LSR, following checks With additional logics, the initiator LSR can perform following
can be performed: checks in a scenario where the initiator knows that there is a LAG,
with two LAG members, between TTL=n and TTL=n+1, and has the
multipath information to traverse the two LAG members.
The initiator LSR sends two MPLS echo request messages to traverse
the two LAG members at TTL=1:
o Success case: o Success case:
* Traversing LAG member=1 at TTL=n results in LAG member=1' as * One MPLS echo request message reaches TTL=n+1 on an LAG member
the incoming interface at TTL=n+1. 1.
* Traversing LAG member=2 at TTL=n results in LAG member=2' as * The other MPLS echo request message reaches TTL=n+1 on an LAG
the incoming interface at TTL=n+1. member 2.
The two MPLS echo request messages sent by the initiator LSR reach
two different LAG members at the immediate downstream LSR.
o Error case: o Error case:
* Traversing LAG member=1 at TTL=n results in LAG member=1' as * One MPLS echo request message reaches TTL=n+1 on an LAG member
the incoming interface at TTL=n+1. 1.
* Traversing LAG member=2 at TTL=n results in LAG member=1' as * The other MPLS echo request message also reaches TTL=n+1 on an
the incoming interface at TTL=n+1. LAG member 1.
One or two MPLS echo request messages sent by the initiator LSR
does not reach the immediate downstream LSR, or the two MPLS echo
request messages reach a same LAG member at the immediate
downstream LSR.
Note that defined procedures will provide a deterministic result for Note that defined procedures will provide a deterministic result for
LAG interfaces that are back-to-back connected between routers (i.e. LAG interfaces that are back-to-back connected between routers (i.e.
no L2 switch in between). If there is a L2 switch between LSR at no L2 switch in between). If there is a L2 switch between LSR at
TTL=n and LSR at TTL=n+1, there is no guarantee that traversal of TTL=n and LSR at TTL=n+1, there is no guarantee that traversal of
every LAG member link at TTL=n will result in reaching different every LAG member link at TTL=n will result in reaching different
interface index at TTL=n+1. Issues resulting from LAG with L2 switch interface index at TTL=n+1. Issues resulting from LAG with L2 switch
in between are further described in Appendix A. LAG provisioning in between are further described in Appendix A. LAG provisioning
models in operated network should be considered when analyzing the models in operated network should be considered when analyzing the
output of LSP Traceroute exercising L2 ECMPs. output of LSP Traceroute exercising L2 ECMPs.
5. LAG Interface Info TLV 5.2. Individual End-to-End Path Verification
The LAG Interface Info object is a new TLV that MAY be included in When the Remote Interface Index Sub-TLVs are available from an LSR
the MPLS echo request message. An MPLS echo request MUST NOT include with TTL=n, then the validation of LAG member link traversal can be
more than one LAG Interface Info object. Presence of LAG Interface performed by the downstream LSR of TTL=n+1. The initiator LSR
Info object is a request that responder LSR describes upstream and follows the procedures described in Section 4.3.
downstream LAG interfaces according to procedures defined in this
document. If the responder LSR is able to accommodate this request,
then the LAG Interface Info object MUST be included in the MPLS echo
reply message.
LAG Interface Info TLV Type is TBD1. Length is 4. The Value field The DDMAP validation procedures by the downstream responder LSR are
of LAG Interface TLV has following format: then updated to include the comparison of the incoming LAG member
link (which MPLS echo request was received on) to the interface index
described in the Remote Interface Index Sub-TLV in the DDMAP.
Failure of this comparison results in the return code being set to
"Downstream Mapping Mismatch (5)".
A responder LSR that is not able to perform the above additional
DDMAP validation procedures is considered to lack the upstream LAG
capability. Thus, if the received MPLS echo request contained the
LSR Capability TLV, then the responder LSR MUST include the LSR
Capability TLV in the MPLS echo reply and the LSR Capability TLV MUST
have the "Upstream LAG Info Accomodation flag" cleared.
6. LSR Capability TLV
The LSR Capability object is a new TLV that MAY be included in the
MPLS echo request message and the MPLS echo reply message. An MPLS
echo request message and an MPLS echo reply message MUST NOT include
more than one LSR Capability object. Presence of an LSR Capability
object in an MPLS echo request message is a request that a responder
LSR includes an LSR Capability object in the MPLS echo reply message,
with the LSR Capability object describing features and extensions
supported. When the received MPLS echo request message contains an
LSR Capability object, an responder LSR MUST include the LSR
Capability object in the MPLS echo reply message.
LSR Capability TLV Type is TBD1. Length is 4. The value field of
the LSR Capability TLV has following format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LAG Interface Info Flags | Must Be Zero | | LSR Capability Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: LAG Interface Info TLV Figure 4: LSR Capability TLV
LAG Interface Info Flags
LAG Interface Info Flags field is a bit vector with following LSR Capability Flags
format.
0 1 The LSR Capability Flags field is a bit vector with following
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 format:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Must Be Zero (Reserved) |U|D|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Must Be Zero (Reserved) |U|D|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Two flags are defined: U and D. The remaining flags MUST be set Two flags are defined: U and D. The remaining flags MUST be set
to zero when sending and ignored on receipt. Both U and D flags to zero when sending and ignored on receipt. Both U and D flags
MUST be cleared in MPLS echo request message when sending, and MUST be cleared in MPLS echo request message when sending, and
ignored on receipt. Either or both U and D flags MAY be set in ignored on receipt. Neither, either or both U and D flags MAY be
MPLS echo reply message. set in MPLS echo reply message.
Flag Name and Meaning Flag Name and Meaning
---- ---------------- ---- ----------------
U Upstream LAG Info Accommodation U Upstream LAG Info Accommodation
When this flag is set, LSR is capable of placing Incoming An LSR sets this flag when the node is capable of
Interface Index Sub-TLV, describing LAG member link, in describing a LAG member link in the Incoming Interface
the Detailed Interface and Label Stack TLV. Index Sub-TLV in the in the Detailed Interface and
Label Stack TLV.
D Downstream LAG Info Accommodation D Downstream LAG Info Accommodation
When this flag is set, LSR is capable of placing Interface An LSR sets this flag when the node is capable of
Index Sub-TLV and Multipath Data Sub-TLV, describing LAG describing LAG member links in the Local Interface
member link, in the Downstream Detailed Mapping TLV. Index Sub-TLV and the Multipath Data Sub-TLV in the
Downstream Detailed Mapping TLV.
6. DDMAP TLV DS Flags: G 7. LAG Description Indicator Flag: G
One flag, G, is added in DS Flags field of the DDMAP TLV. The G flag One flag, G, is added in DS Flags field of the DDMAP TLV. The G flag
of the DS Flags field has no meaning in the MPLS echo request of the DS Flags field in the MPLS echo request message indicates the
message. The G flag MUST therefore be cleared when sending, and request for detailed LAG information from the responder LSR. In the
ignored on the receipt of the MPLS echo request message. In the MPLS MPLS echo reply message, the G flag MUST be set if the DDMAP TLV
echo reply message, G flag MUST be set if the DDMAP TLV describes a describes a LAG interface. It MUST be cleared otherwise.
LAG interface. It MUST be cleared otherwise.
DS Flags DS Flags
DS Flags G is added, in Bit Number TBD4, in DS Flags bit vector. DS Flags G is added, in Bit Number TBD5, in DS Flags bit vector.
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| MBZ |G|MBZ|I|N| | MBZ |G|MBZ|I|N|
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
RFC-Editor-Note: Please update above figure to place the flag G in RFC-Editor-Note: Please update above figure to place the flag G in
the bit number TBD4. the bit number TBD5.
Flag Name and Meaning Flag Name and Meaning
---- ---------------- ---- ----------------
G LAG Description Indicator G LAG Description Indicator
When this flag is set, DDMAP describes a LAG interface. When this flag is set in the MPLS echo request, responder is
requested to respond with detailed LAG information. When this
flag is set in the MPLS echo reply, the corresponding DDMAP
describes a LAG interface.
7. Interface Index Sub-TLV 8. Local Interface Index Sub-TLV
The Interface Index object is a Sub-TLV that MAY be included in a The Local Interface Index object is a Sub-TLV that MAY be included in
DDMAP TLV. Zero or more Interface Index object MAY appear in a DDMAP a DDMAP TLV. Zero or more Local Interface Index object MAY appear in
TLV. The Interface Index Sub-TLV describes the index assigned by a DDMAP TLV. The Local Interface Index Sub-TLV describes the index
local LSR to the egress interface. assigned by the local LSR to the egress interface.
Interface Index Sub-TLV Type is TBD2. Length is 8, and the Value The Local Interface Index Sub-TLV Type is TBD2. Length is 8, and the
field has following format: Value field has following format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Index Flags | Must Be Zero | | Interface Index Flags | Must Be Zero |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Index | | Local Interface Index |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5: Interface Index Sub-TLV Figure 5: Local Interface Index Sub-TLV
Interface Index Flags Interface Index Flags
Interface Index Flags field is a bit vector with following format. Interface Index Flags field is a bit vector with following format.
0 1 0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Must Be Zero (Reserved) |M| | Must Be Zero (Reserved) |M|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
One flag is defined: M. The remaining flags MUST be set to zero One flag is defined: M. The remaining flags MUST be set to zero
when sending and ignored on receipt. when sending and ignored on receipt.
Flag Name and Meaning Flag Name and Meaning
---- ---------------- ---- ----------------
M LAG Member Link Indicator M LAG Member Link Indicator
When this flag is set, interface index described in When this flag is set, interface index described in
this sub-TLV is member of a LAG. this sub-TLV is a member of a LAG.
Interface Index Local Interface Index
Index assigned by the LSR to this interface. An Index assigned by the LSR to this interface.
8. Detailed Interface and Label Stack TLV 9. Remote Interface Index Sub-TLV
The Remote Interface Index object is a Sub-TLV that MAY be included
in a DDMAP TLV. Zero or more Remote Interface Index object MAY
appear in a DDMAP TLV. The Remote Interface Index Sub-TLV describes
the index assigned by the downstream LSR to the ingress interface.
The Remote Interface Index Sub-TLV Type is TBD3. Length is 8, and
the Value field has following format:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Index Flags | Must Be Zero |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Remote Interface Index |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6: Remote Interface Index Sub-TLV
Interface Index Flags
Interface Index Flags field is a bit vector with following format.
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Must Be Zero (Reserved) |M|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
One flag is defined: M. The remaining flags MUST be set to zero
when sending and ignored on receipt.
Flag Name and Meaning
---- ----------------
M LAG Member Link Indicator
When this flag is set, interface index described in
this sub-TLV is a member of a LAG.
Remote Interface Index
An Index assigned by the downstream LSR to the ingress interface.
10. Detailed Interface and Label Stack TLV
The "Detailed Interface and Label Stack" object is a TLV that MAY be The "Detailed Interface and Label Stack" object is a TLV that MAY be
included in a MPLS echo reply message to report the interface on included in a MPLS echo reply message to report the interface on
which the MPLS echo request message was received and the label stack which the MPLS echo request message was received and the label stack
that was on the packet when it was received. A responder LSR MUST that was on the packet when it was received. A responder LSR MUST
NOT insert more than one instance of this TLV. This TLV allows the NOT insert more than one instance of this TLV. This TLV allows the
initiator LSR to obtain the exact interface and label stack initiator LSR to obtain the exact interface and label stack
information as it appears at the responder LSR. information as it appears at the responder LSR.
Detailed Interface and Label Stack TLV Type is TBD3. Length is K + Detailed Interface and Label Stack TLV Type is TBD4. Length is K +
Sub-TLV Length (sum of Sub-TLVs). K is the sum of all fields of this Sub-TLV Length (sum of Sub-TLVs). K is the sum of all fields of this
TLV prior to Sub-TLVs, but the length of K depends on the Address TLV prior to Sub-TLVs, but the length of K depends on the Address
Type. Details of this information is described below. The Value Type. Details of this information is described below. The Value
field has following format: field has following format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 14, line 33 skipping to change at page 18, line 51
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface (4 or 16 octets) | | Interface (4 or 16 octets) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Must Be Zero | Sub-TLV Length | | Must Be Zero | Sub-TLV Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . .
. List of Sub-TLVs . . List of Sub-TLVs .
. . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6: Detailed Interface and Label Stack TLV Figure 7: Detailed Interface and Label Stack TLV
The Detailed Interface and Label Stack TLV format is derived from the The Detailed Interface and Label Stack TLV format is derived from the
Interface and Label Stack TLV format (from [RFC4379]). Two changes Interface and Label Stack TLV format (from [RFC4379]). Two changes
are introduced. First is that label stack, which is of variable are introduced. First is that label stack, which is of variable
length, is converted into a sub-TLV. Second is that a new sub-TLV is length, is converted into a sub-TLV. Second is that a new sub-TLV is
added to describe an interface index. The fields of Detailed added to describe an interface index. The fields of Detailed
Interface and Label Stack TLV have the same use and meaning as in Interface and Label Stack TLV have the same use and meaning as in
[RFC4379]. A summary of the fields taken from the Interface and [RFC4379]. A summary of the fields taken from the Interface and
Label Stack TLV is as below: Label Stack TLV is as below:
skipping to change at page 15, line 34 skipping to change at page 20, line 4
IPv4 Unnumbered or IPv6 Unnumbered, the IP Address MUST be the IPv4 Unnumbered or IPv6 Unnumbered, the IP Address MUST be the
LSR's Router ID, and the Interface MUST be set to the index LSR's Router ID, and the Interface MUST be set to the index
assigned to the interface. assigned to the interface.
Note: Usage of IPv6 Unnumbered has the same issue as [RFC4379], Note: Usage of IPv6 Unnumbered has the same issue as [RFC4379],
described in Section 3.4.2 of [I-D.ietf-mpls-ipv6-only-gap]. A described in Section 3.4.2 of [I-D.ietf-mpls-ipv6-only-gap]. A
solution should be considered an applied to both [RFC4379] and solution should be considered an applied to both [RFC4379] and
this document. this document.
Sub-TLV Length Sub-TLV Length
Total length in octets of the sub-TLVs associated with this Total length in octets of the sub-TLVs associated with this
TLV. TLV.
8.1. Sub-TLVs 10.1. Sub-TLVs
This section defines the sub-TLVs that MAY be included as part of the This section defines the sub-TLVs that MAY be included as part of the
Detailed Interface and Label Stack TLV. Detailed Interface and Label Stack TLV.
Sub-Type Value Field Sub-Type Value Field
--------- ------------ --------- ------------
1 Incoming Label stack 1 Incoming Label stack
2 Incoming Interface Index 2 Incoming Interface Index
8.1.1. Incoming Label Stack Sub-TLV 10.1.1. Incoming Label Stack Sub-TLV
The Incoming Label Stack sub-TLV contains the label stack as received The Incoming Label Stack sub-TLV contains the label stack as received
by the LSR. If any TTL values have been changed by this LSR, they by the LSR. If any TTL values have been changed by this LSR, they
SHOULD be restored. SHOULD be restored.
Incoming Label Stack Sub-TLV Type is 1. Length is variable, and the Incoming Label Stack Sub-TLV Type is 1. Length is variable, and the
Value field has following format: Value field has following format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
skipping to change at page 16, line 22 skipping to change at page 20, line 40
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Label | TC |S| TTL | | Label | TC |S| TTL |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . .
. . . .
. . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Label | TC |S| TTL | | Label | TC |S| TTL |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 7: Incoming Label Stack Sub-TLV Figure 8: Incoming Label Stack Sub-TLV
8.1.2. Incoming Interface Index Sub-TLV 10.1.2. Incoming Interface Index Sub-TLV
The Incoming Interface Index object is a Sub-TLV that MAY be included The Incoming Interface Index object is a Sub-TLV that MAY be included
in a Detailed Interface and Label Stack TLV. The Incoming Interface in a Detailed Interface and Label Stack TLV. The Incoming Interface
Index Sub-TLV describes the index assigned by this LSR to the Index Sub-TLV describes the index assigned by this LSR to the
interface which received the MPLS echo request message. interface which received the MPLS echo request message.
Incoming Interface Index Sub-TLV Type is 2. Length is 8, and the Incoming Interface Index Sub-TLV Type is 2. Length is 8, and the
Value field has the same format as the Interface Index Sub-TLV Value field has the same format as the Local Interface Index Sub-TLV
described in Section 7, and has following format: described in Section 8, and has following format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Index Flags | Must Be Zero | | Interface Index Flags | Must Be Zero |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Index | | Incoming Interface Index |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 8: Incoming Interface Index Sub-TLV Figure 9: Incoming Interface Index Sub-TLV
Interface Index Flags Interface Index Flags
Interface Index Flags field is a bit vector with following format. Interface Index Flags field is a bit vector with following format.
0 1 0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Must Be Zero (Reserved) |M| | Must Be Zero (Reserved) |M|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
One flag is defined: M. The remaining flags MUST be set to zero One flag is defined: M. The remaining flags MUST be set to zero
when sent and ignored on receipt. when sending and ignored on receipt.
Flag Name and Meaning Flag Name and Meaning
---- ---------------- ---- ----------------
M LAG Member Link Indicator M LAG Member Link Indicator
When this flag is set, the interface index described in When this flag is set, interface index described in
this sub-TLV is a member of a LAG. this sub-TLV is a member of a LAG.
Interface Index Incoming Interface Index
Index assigned by the LSR to this interface. An Index assigned by the LSR to this interface.
9. Security Considerations 11. Security Considerations
This document extends LSP Traceroute mechanism to discover and This document extends LSP Traceroute mechanism to discover and
exercise L2 ECMP paths. As result of supporting the code points and exercise L2 ECMP paths. As a result of supporting the code points
procedures described in this document, additional processing are and procedures described in this document, additional processing are
required by initiator LSRs and responder LSRs, especially to compute required by initiator LSRs and responder LSRs, especially to compute
and handle increasing number of multipath information. Due to and handle increasing number of multipath information. Due to
additional processing, it is critical that proper security measures additional processing, it is critical that proper security measures
described in [RFC4379] and [RFC6424] are followed. described in [RFC4379] and [RFC6424] are followed.
The LSP Traceroute allows an initiator LSR to discover the paths of The LSP Traceroute allows an initiator LSR to discover the paths of
tested LSPs, providing deep knowledge of the MPLS network. Exposing tested LSPs, providing deep knowledge of the MPLS network. Exposing
such information to a malicious user is considered dangerous. To such information to a malicious user is considered dangerous. To
prevent leakage of vital information to untrusted users, a responder prevent leakage of vital information to untrusted users, a responder
LSR MUST only accept MPLS echo request messages from trusted sources LSR MUST only accept MPLS echo request messages from trusted sources
via filtering source IP address field of received MPLS echo request via filtering source IP address field of received MPLS echo request
messages. messages.
10. IANA Considerations 12. IANA Considerations
10.1. LAG Interface Info TLV 12.1. LSR Capability TLV
The IANA is requested to assign new value TBD1 for LAG Interface Info The IANA is requested to assign new value TBD1 for LSR Capability TLV
TLV from the "Multiprotocol Label Switching Architecture (MPLS) Label from the "Multiprotocol Label Switching Architecture (MPLS) Label
Switched Paths (LSPs) Ping Parameters - TLVs" registry. Switched Paths (LSPs) Ping Parameters - TLVs" registry.
Value Meaning Reference Value Meaning Reference
----- ------- --------- ----- ------- ---------
TBD1 LAG Interface Info TLV this document TBD1 LSR Capability TLV this document
10.1.1. LAG Interface Info Flags 12.1.1. LSR Capability Flags
The IANA is requested to create and maintain a registry entitled "LAG The IANA is requested to create and maintain a registry entitled "LSR
Interface Info Flags" with following registration procedures: Capability Flags" with following registration procedures:
Registry Name: LAG Interface Info Flags Registry Name: LAG Interface Info Flags
Bit number Name Reference Bit number Name Reference
---------- ---------------------------------------- --------- ---------- ---------------------------------------- ---------
15 D: Downstream LAG Info Accommodation this document 31 D: Downstream LAG Info Accommodation this document
14 U: Upstream LAG Info Accommodation this document 30 U: Upstream LAG Info Accommodation this document
0-13 Unassigned 0-29 Unassigned
Assignments of LAG Interface Info Flags are via Standards Action Assignments of LSR Capability Flags are via Standards Action
[RFC5226]. [RFC5226].
10.2. Interface Index Sub-TLV 12.2. Local Interface Index Sub-TLV
The IANA is requested to assign new value TBD2 for Interface Index The IANA is requested to assign new value TBD2 (from the range
Sub-TLV from the "Multiprotocol Label Switching Architecture (MPLS) 4-31743) for the Local Interface Index Sub-TLV from the
Label Switched Paths (LSPs) Ping Parameters - TLVs" registry, "Sub- "Multiprotocol Label Switching Architecture (MPLS) Label Switched
TLVs for TLV Types 20" sub-registry. Paths (LSPs) Ping Parameters - TLVs" registry, "Sub-TLVs for TLV
Types 20" sub-registry.
Value Meaning Reference Value Meaning Reference
----- ------- --------- ----- ------- ---------
TBD2 Interface Index Sub-TLV this document TBD2 Local Interface Index Sub-TLV this document
10.2.1. Interface Index Flags 12.2.1. Interface Index Flags
The IANA is requested to create and maintain a registry entitled The IANA is requested to create and maintain a registry entitled
"Interface Index Flags" with following registration procedures: "Interface Index Flags" with following registration procedures:
Registry Name: Interface Index Flags Registry Name: Interface Index Flags
Bit number Name Reference Bit number Name Reference
---------- ---------------------------------------- --------- ---------- ---------------------------------------- ---------
15 M: LAG Member Link Indicator this document 15 M: LAG Member Link Indicator this document
0-14 Unassigned 0-14 Unassigned
Assignments of Interface Index Flags are via Standards Action Assignments of Interface Index Flags are via Standards Action
[RFC5226]. [RFC5226].
Note that this registry is used by the Interface Index Flags field of Note that this registry is used by the Interface Index Flags field of
the Interface Index Sub-TLV which may be present in the "Downstream following Sub-TLVs:
Detailed Mapping" TLV and the Incoming Interface Index Sub-TLV which
may be present in the "Detailed Interface and Label Stack" TLV.
10.3. Detailed Interface and Label Stack TLV o The Local Interface Index Sub-TLV which may be present in the
"Downstream Detailed Mapping" TLV.
The IANA is requested to assign new value TBD3 for Detailed Interface o The Remote Interface Index Sub-TLV which may be present in the
"Downstream Detailed Mapping" TLV.
o The Incoming Interface Index Sub-TLV which may be present in the
"Detailed Interface and Label Stack" TLV.
12.3. Remote Interface Index Sub-TLV
The IANA is requested to assign new value TBD3 (from the range
32768-49161) for the Remote Interface Index Sub-TLV from the
"Multiprotocol Label Switching Architecture (MPLS) Label Switched
Paths (LSPs) Ping Parameters - TLVs" registry, "Sub-TLVs for TLV
Types 20" sub-registry.
Value Meaning Reference
----- ------- ---------
TBD3 Remote Interface Index Sub-TLV this document
12.4. Detailed Interface and Label Stack TLV
The IANA is requested to assign new value TBD4 for Detailed Interface
and Label Stack TLV from the "Multiprotocol Label Switching and Label Stack TLV from the "Multiprotocol Label Switching
Architecture (MPLS) Label Switched Paths (LSPs) Ping Parameters - Architecture (MPLS) Label Switched Paths (LSPs) Ping Parameters -
TLVs" registry ([IANA-MPLS-LSP-PING]). TLVs" registry ([IANA-MPLS-LSP-PING]).
Value Meaning Reference Value Meaning Reference
----- ------- --------- ----- ------- ---------
TBD3 Detailed Interface and Label Stack TLV this document TBD4 Detailed Interface and Label Stack TLV this document
10.3.1. Sub-TLVs for TLV Type TBD3 12.4.1. Sub-TLVs for TLV Type TBD4
The IANA is requested to create and maintain a sub-registry entitled The IANA is requested to create and maintain a sub-registry entitled
"Sub-TLVs for TLV Type TBD3" under "Multiprotocol Label Switching "Sub-TLVs for TLV Type TBD4" under "Multiprotocol Label Switching
Architecture (MPLS) Label Switched Paths (LSPs) Ping Parameters - Architecture (MPLS) Label Switched Paths (LSPs) Ping Parameters -
TLVs" registry. TLVs" registry.
Initial values for this sub-registry, "Sub-TLVs for TLV Types TBD3", Initial values for this sub-registry, "Sub-TLVs for TLV Types TBD4",
are described below. are described below.
Sub-Type Name Reference Sub-Type Name Reference
--------- ---------------------------------------- --------- ----------- -------------------------------------- ---------
1 Incoming Label Stack this document 1 Incoming Label Stack this document
2 Incoming Interface Index this document 2 Incoming Interface Index this document
4-65535 Unassigned 3-16383 Unassigned (mandatory TLVs)
16384-31743 Experimental
32768-49161 Unassigned (optional TLVs)
49162-64511 Experimental
Assignments of Sub-Types are via Standards Action [RFC5226]. Assignments of Sub-Types in the mandatory and optional spaces are are
via Standards Action [RFC5226]. Assignments of Sub-Types in the
experimental space is via Specification Required [RFC5226].
10.4. DS Flags 12.5. DS Flags
The IANA is requested to assign a new bit number from the "DS flags" The IANA is requested to assign a new bit number from the "DS flags"
sub-registry from the "Multi-Protocol Label Switching (MPLS) Label sub-registry from the "Multi-Protocol Label Switching (MPLS) Label
Switched Paths (LSPs) Ping Parameters - TLVs" registry Switched Paths (LSPs) Ping Parameters - TLVs" registry
([IANA-MPLS-LSP-PING]). ([IANA-MPLS-LSP-PING]).
Note: the "DS flags" sub-registry is created by Note: the "DS flags" sub-registry is created by
[I-D.ietf-mpls-lsp-ping-registry]. [I-D.ietf-mpls-lsp-ping-registry].
Bit number Name Reference Bit number Name Reference
---------- ---------------------------------------- --------- ---------- ---------------------------------------- ---------
TBD4 G: LAG Description Indicator this document TBD5 G: LAG Description Indicator this document
11. Acknowledgements 13. Acknowledgements
Authors would like to thank Nagendra Kumar and Sam Aldrin for The authors would like to thank Nagendra Kumar and Sam Aldrin for
providing useful comments and suggestions. Authors would like to providing useful comments and suggestions. The authors would like to
thank Loa Andersson for performing a detailed review and providing thank Loa Andersson for performing a detailed review and providing
number of comments. number of comments.
12. References The authors also would like to extend sincere thanks to the MPLS RT
review members who took time to review and provide comments. The
members are Eric Osborne, Mach Chen and Yimin Shen. The suggestion
by Mach Chen to generalize and create the LSR Capability TLV was
tremendously helpful for this document and likely for future
documents extending the MPLS LSP Ping and Traceroute mechanism. The
suggestion by Yimin Shen to create two separate validation procedures
had a big impact to the contents of this document.
12.1. Normative References 14. References
14.1. Normative References
[I-D.ietf-mpls-lsp-ping-registry] [I-D.ietf-mpls-lsp-ping-registry]
Decraene, B., Akiya, N., Pignataro, C., Andersson, L., and Decraene, B., Akiya, N., Pignataro, C., Andersson, L., and
S. Aldrin, "IANA registries for LSP ping Code Points", S. Aldrin, "IANA registries for LSP ping Code Points",
draft-ietf-mpls-lsp-ping-registry-00 (work in progress), draft-ietf-mpls-lsp-ping-registry-00 (work in progress),
November 2014. November 2014.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[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.
12.2. Informative References 14.2. Informative References
[I-D.ietf-mpls-ipv6-only-gap] [I-D.ietf-mpls-ipv6-only-gap]
George, W. and C. Pignataro, "Gap Analysis for Operating George, W. and C. Pignataro, "Gap Analysis for Operating
IPv6-only MPLS Networks", draft-ietf-mpls-ipv6-only-gap-04 IPv6-only MPLS Networks", draft-ietf-mpls-ipv6-only-gap-04
(work in progress), November 2014. (work in progress), November 2014.
[IANA-MPLS-LSP-PING] [IANA-MPLS-LSP-PING]
IANA, "Multi-Protocol Label Switching (MPLS) Label IANA, "Multi-Protocol Label Switching (MPLS) Label
Switched Paths (LSPs) Ping Parameters", Switched Paths (LSPs) Ping Parameters",
<http://www.iana.org/assignments/mpls-lsp-ping-parameters/ <http://www.iana.org/assignments/mpls-lsp-ping-parameters/
 End of changes. 142 change blocks. 
306 lines changed or deleted 548 lines changed or added

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