rfc8611v3.txt   rfc8611.txt 
skipping to change at page 3, line 5 skipping to change at page 3, line 5
12. Security Considerations . . . . . . . . . . . . . . . . . . . 21 12. Security Considerations . . . . . . . . . . . . . . . . . . . 21
13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
13.1. LSR Capability TLV . . . . . . . . . . . . . . . . . . . 21 13.1. LSR Capability TLV . . . . . . . . . . . . . . . . . . . 21
13.1.1. LSR Capability Flags . . . . . . . . . . . . . . . . 22 13.1.1. LSR Capability Flags . . . . . . . . . . . . . . . . 22
13.2. Local Interface Index Sub-TLV . . . . . . . . . . . . . 22 13.2. Local Interface Index Sub-TLV . . . . . . . . . . . . . 22
13.2.1. Interface Index Flags . . . . . . . . . . . . . . . 22 13.2.1. Interface Index Flags . . . . . . . . . . . . . . . 22
13.3. Remote Interface Index Sub-TLV . . . . . . . . . . . . . 23 13.3. Remote Interface Index Sub-TLV . . . . . . . . . . . . . 23
13.4. Detailed Interface and Label Stack TLV . . . . . . . . . 23 13.4. Detailed Interface and Label Stack TLV . . . . . . . . . 23
13.4.1. Sub-TLVs for TLV Type 6 . . . . . . . . . . . . . . 23 13.4.1. Sub-TLVs for TLV Type 6 . . . . . . . . . . . . . . 23
13.4.2. Interface and Label Stack Address Types . . . . . . 24 13.4.2. Interface and Label Stack Address Types . . . . . . 24
13.5. DS Flags . . . . . . . . . . . . . . . . . . . . . . . . 24 13.5. DS Flags . . . . . . . . . . . . . . . . . . . . . . . . 25
14. References . . . . . . . . . . . . . . . . . . . . . . . . . 24 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 25
14.1. Normative References . . . . . . . . . . . . . . . . . . 24 14.1. Normative References . . . . . . . . . . . . . . . . . . 25
14.2. Informative References . . . . . . . . . . . . . . . . . 25 14.2. Informative References . . . . . . . . . . . . . . . . . 25
Appendix A. LAG with Intermediate L2 Switch Issues . . . . . . . 25 Appendix A. LAG with Intermediate L2 Switch Issues . . . . . . . 26
A.1. Equal Numbers of LAG Members . . . . . . . . . . . . . . 25 A.1. Equal Numbers of LAG Members . . . . . . . . . . . . . . 26
A.2. Deviating Numbers of LAG Members . . . . . . . . . . . . 26 A.2. Deviating Numbers of LAG Members . . . . . . . . . . . . 26
A.3. LAG Only on Right . . . . . . . . . . . . . . . . . . . . 26 A.3. LAG Only on Right . . . . . . . . . . . . . . . . . . . . 27
A.4. LAG Only on Left . . . . . . . . . . . . . . . . . . . . 26 A.4. LAG Only on Left . . . . . . . . . . . . . . . . . . . . 27
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 26 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 27
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27
1. Introduction 1. Introduction
1.1. Background 1.1. Background
The MPLS Label Switched Path (LSP) Ping and Traceroute mechanisms The MPLS Label Switched Path (LSP) Ping and Traceroute mechanisms
[RFC8029] are powerful tools designed to diagnose all available [RFC8029] are powerful tools designed to diagnose all available
Layer 3 (L3) paths of LSPs, including diagnostic coverage of L3 Layer 3 (L3) paths of LSPs, including diagnostic coverage of L3
Equal-Cost Multipath (ECMP). In many MPLS networks, Link Aggregation Equal-Cost Multipath (ECMP). In many MPLS networks, Link Aggregation
skipping to change at page 13, line 44 skipping to change at page 13, line 44
One or two MPLS echo request messages sent by the initiator LSR One or two MPLS echo request messages sent by the initiator LSR
cannot reach the immediate downstream LSR, or the two MPLS echo cannot reach the immediate downstream LSR, or the two MPLS echo
request messages reach at the immediate downstream LSR from the request messages reach at the immediate downstream LSR from the
same LAG member link. same LAG member link.
Note that the procedures defined above will provide a deterministic Note that the procedures defined above will provide a deterministic
result for LAG interfaces that are back-to-back connected between result for LAG interfaces that are back-to-back connected between
LSRs (i.e., no L2 switch in between). If there is an L2 switch LSRs (i.e., no L2 switch in between). If there is an L2 switch
between the LSR at TTL=n and the LSR at TTL=n+1, there is no between the LSR at TTL=n and the LSR at TTL=n+1, there is no
guarantee that traversal of every LAG member link at TTL=n will guarantee that traversal of every LAG member link at TTL=n will be
result in reaching from different interface at TTL=n+1. Issues reachable from any LAG member link at TTL=n+1. Issues resulting from
resulting from LAG with an L2 switch in between are further described LAG with an L2 switch in between are further described in Appendix A.
in Appendix A. LAG provisioning models in operator networks should LAG provisioning models in operator networks should be considered
be considered when analyzing the output of LSP Traceroute that is when analyzing the output of LSP Traceroute that is exercising L2
exercising L2 ECMPs. ECMPs.
5.2. Individual End-to-End Path Verification 5.2. Individual End-to-End Path Verification
When the Remote Interface Index Sub-TLVs are available from an LSR When the Remote Interface Index Sub-TLVs are available from an LSR
with TTL=n, then the validation of LAG member link traversal can be with TTL=n, then the validation of LAG member link traversal can be
performed by the downstream LSR of TTL=n+1. The initiator LSR performed by the downstream LSR of TTL=n+1. The initiator LSR
follows the procedures described in Section 4.3. follows the procedures described in Section 4.3.
The DDMAP validation procedures for the downstream responder LSR are The DDMAP validation procedures for the downstream responder LSR are
then updated to include the comparison of the incoming LAG member then updated to include the comparison of the incoming LAG member
skipping to change at page 23, line 36 skipping to change at page 23, line 36
Interface and Label Stack TLV from the "TLVs" registry in the Interface and Label Stack TLV from the "TLVs" registry in the
"Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) "Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs)
Ping Parameters" registry [IANA-MPLS-LSP-PING]. Ping Parameters" registry [IANA-MPLS-LSP-PING].
Type TLV Name Reference Type TLV Name Reference
----- -------- --------- ----- -------- ---------
6 Detailed Interface and Label Stack RFC 8611 6 Detailed Interface and Label Stack RFC 8611
13.4.1. Sub-TLVs for TLV Type 6 13.4.1. Sub-TLVs for TLV Type 6
RFC 8029 changed the registration procedures for TLV and sub-TLV
registries for LSP Ping.
IANA has created a new "Sub-TLVs for TLV Type 6" subregistry under IANA has created a new "Sub-TLVs for TLV Type 6" subregistry under
the "TLVs" registry of the "Multiprotocol Label Switching (MPLS) the "TLVs" registry of the "Multiprotocol Label Switching (MPLS)
Label Switched Paths (LSPs) Ping Parameters" registry Label Switched Paths (LSPs) Ping Parameters" registry
[IANA-MPLS-LSP-PING]. [IANA-MPLS-LSP-PING].
Initial values for the "Sub-TLVs for TLV Type 6" subregistry are This registry conforms with RFC 8029.
shown below:
Sub-Type Sub-TLV Name Reference The registration procedures for this sub-TLV registry are:
----------- -------------------------------------- ---------
0 Reserved RFC 8611
1 Incoming Label Stack RFC 8611
2 Incoming Interface Index RFC 8611
3-16383 Unassigned (mandatory TLVs)
16384-31743 Specification Required
32768-49161 Unassigned (optional TLVs)
49162-64511 Specification Required
Assignments of Sub-Types in the mandatory and optional spaces are via Range Registration Procedure Note
Standards Action [RFC8126]. Assignments of Sub-Types in the ----- ---------------------- -----
Specification Required space are via Specification Required 0-16383 Standards Action This range is for mandatory
[RFC8126]. TLVs or for optional TLVs that
require an error message if
not recognized.
16384-31743 RFC Required This range is for mandatory
TLVs or for optional TLVs that
require an error message if
not recognized.
31744-32767 Private Use Not to be assigned
32768-49161 Standards Action This range is for optional TLVs
that can be silently dropped if
not recognized.
49162-64511 RFC Required This range is for optional TLVs
that can be silently dropped if
not recognized.
64512-65535 Private Use Not to be assigned
The initial allocations for this registry are:
Sub-Type Sub-TLV Name Reference Comment
-------- ------------ --------- -------
0 Reserved RFC 8611
1 Incoming Label Stack RFC 8611
2 Incoming Interface Index RFC 8611
3-31743 Unassigned
31744-32767 RFC 8611 Reserved for Private Use
32768-64511 Unassigned
64511-65535 RFC 8611 Reserved for Private Use
Note: IETF does not prescribe how the Private Use sub-TLVs are
handled; however, if a packet containing a sub-TLV from a Private Use
ranges is received by an LSR that does not recognize the sub-TLV, an
error message MAY be returned if the sub-TLV is from the range
31744-32767, and the packet SHOULD be silently dropped if it is from
the range 64511-65535.
13.4.2. Interface and Label Stack Address Types 13.4.2. Interface and Label Stack Address Types
The Detailed Interface and Label Stack TLV shares the Interface and The Detailed Interface and Label Stack TLV shares the Interface and
Label Stack Address Types with the Interface and Label Stack TLV. To Label Stack Address Types with the Interface and Label Stack TLV. To
reflect this, IANA has updated the name of the registry from reflect this, IANA has updated the name of the registry from
"Interface and Label Stack Address Types" to "Interface and Label "Interface and Label Stack Address Types" to "Interface and Label
Stack and Detailed Interface and Label Stack Address Types". Stack and Detailed Interface and Label Stack Address Types".
13.5. DS Flags 13.5. DS Flags
 End of changes. 8 change blocks. 
29 lines changed or deleted 56 lines changed or added

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