draft-ietf-mpls-egress-tlv-for-nil-fec-00.txt   draft-ietf-mpls-egress-tlv-for-nil-fec-01.txt 
Routing area D. Rathi, Ed. Routing area D. Rathi, Ed.
Internet-Draft K. Arora Internet-Draft K. Arora
Intended status: Standards Track S. Hegde Intended status: Standards Track S. Hegde
Expires: March 25, 2022 Juniper Networks Inc. Expires: April 23, 2022 Juniper Networks Inc.
Z. Ali Z. Ali
N. Nainar N. Nainar
Cisco Systems, Inc. Cisco Systems, Inc.
September 21, 2021 October 20, 2021
Egress TLV for Nil FEC in Label Switched Path Ping and Traceroute Egress TLV for Nil FEC in Label Switched Path Ping and Traceroute
Mechanisms Mechanisms
draft-ietf-mpls-egress-tlv-for-nil-fec-00 draft-ietf-mpls-egress-tlv-for-nil-fec-01
Abstract Abstract
MPLS ping and traceroute mechanism as described in RFC 8029 and MPLS ping and traceroute mechanism as described in RFC 8029 and
related extensions for SR as defined in RFC 8287 is very useful to related extensions for SR as defined in RFC 8287 is very useful to
precisely validate the control plane and data plane synchronization. precisely validate the control plane and data plane synchronization.
There is a possibility that all intermediate or transit nodes may not There is a possibility that all intermediate or transit nodes may not
have been upgraded to support these validation procedures. A simple have been upgraded to support these validation procedures. A simple
mpls ping and traceroute mechanism comprises of ability to traverse mpls ping and traceroute mechanism comprises of ability to traverse
any path without having to validate the control plane state. RFC any path without having to validate the control plane state. RFC
skipping to change at page 2, line 12 skipping to change at page 2, line 12
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 March 25, 2022. This Internet-Draft will expire on April 23, 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 7, line 13 skipping to change at page 7, line 13
Stack sub-TLV at FEC-stack-depth is Nil FEC, set Best-return-code to Stack sub-TLV at FEC-stack-depth is Nil FEC, set Best-return-code to
8 ("Label switched at stack-depth") and Best-return-subcode to Label- 8 ("Label switched at stack-depth") and Best-return-subcode to Label-
stack-depth to report transit switching in MPLS Echo Reply message. stack-depth to report transit switching in MPLS Echo Reply message.
2. If the Label-stack-depth is 0 and the Target FEC Stack sub-TLV at 2. If the Label-stack-depth is 0 and the Target FEC Stack sub-TLV at
FEC-stack-depth is Nil FEC then do the look up for an exact match of FEC-stack-depth is Nil FEC then do the look up for an exact match of
the EGRESS TLV prefix to any of locally configured interfaces or the EGRESS TLV prefix to any of locally configured interfaces or
loopback addresses. loopback addresses.
2a. If EGRESS TLV prefix look up succeeds, set Best-return-code to 2a. If EGRESS TLV prefix look up succeeds, set Best-return-code to
TBD2 ("Replying router is an egress for EGRESS TLV") (Section 7.2)and TBD2 ("Replying router is an egress for the prefix in EGRESS-TLV")
Best-return-subcode to 1 to report egress ok in MPLS Echo Reply (Section 7.2) and Best-return-subcode to 1 to report egress ok in
message. MPLS Echo Reply message.
2b. If EGRESS TLV prefix look up fails, set the Best-return-code to 2b. If EGRESS TLV prefix look up fails, set the Best-return-code to
10, "Mapping for this FEC is not the given label at stack-depth" and 10, "Mapping for this FEC is not the given label at stack-depth" and
Best-return-subcode to 1. Best-return-subcode to 1.
5. Backward Compatibility 5. Backward Compatibility
The extension proposed in this document is backward compatible with The extension proposed in this document is backward compatible with
procedures described in [RFC8029]. Router that does not support procedures described in [RFC8029]. Router that does not support
EGRESS-TLV, will ignore it and use current NIL-FEC procedures EGRESS-TLV, will ignore it and use current NIL-FEC procedures
skipping to change at page 8, line 16 skipping to change at page 8, line 16
| Value | Description | Reference | | Value | Description | Reference |
+----------------+-------------+---------------+ +----------------+-------------+---------------+
| TBD1 | EGRESS TLV | Section 3 | | TBD1 | EGRESS TLV | Section 3 |
| (suggested 28) | | This document | | (suggested 28) | | This document |
+----------------+-------------+---------------+ +----------------+-------------+---------------+
Table 1: TLVs Sub-Registry Table 1: TLVs Sub-Registry
7.2. New Return code 7.2. New Return code
IANA need to assign new value for EGRESS TLV in the "Multi-Protocol IANA need to assign new Return Code for "Replying router is an egress
Label Switching (MPLS) Label Switched Paths (LSPs) Ping Parameters" for the prefix in EGRESS-TLV" in the "Multi-Protocol Label Switching
in "Return Codes" sub-registry. [IANA]. (MPLS) Label Switched Paths (LSPs) Ping Parameters" in "Return Codes"
sub-registry. [IANA].
+----------------+------------------------------+---------------+ +----------------+------------------------------+---------------+
| Value | Description | Reference | | Value | Description | Reference |
+----------------+------------------------------+---------------+ +----------------+------------------------------+---------------+
| TBD2 | Replying router is an egress | Section 4.2 | | TBD2 | Replying router is an egress | Section 4.2 |
| (suggested 36) | for the EGRESS-TLV | This document | | (suggested 36) | for the prefix in EGRESS-TLV | This document |
+----------------+------------------------------+---------------+ +----------------+------------------------------+---------------+
Table 2: Return code Sub-Registry Table 2: Return code Sub-Registry
8. Acknowledgements 8. Acknowledgements
TBD. TBD.
9. References 9. References
 End of changes. 7 change blocks. 
11 lines changed or deleted 12 lines changed or added

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