Egress TLV for Nil FEC in Label Switched Path Ping and Traceroute Mechanisms
draft-rathi-mpls-egress-tlv-for-nil-fec-06

Document Type Replaced Internet-Draft (individual)
Authors Deepti Rathi  , Kapil Arora  , Shraddha Hegde  , Zafar Ali  , Nagendra Nainar 
Last updated 2021-08-19
Replaced by draft-ietf-mpls-egress-tlv-for-nil-fec
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-mpls-egress-tlv-for-nil-fec
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-rathi-mpls-egress-tlv-for-nil-fec-06.txt

Abstract

MPLS ping and traceroute mechanism as described in RFC 8029 and related extensions for SR as defined in RFC 8287 is very useful to precisely validate the control plane and data plane synchronization. There is a possibility that all intermediate or transit nodes may not have been upgraded to support these validation procedures. A simple mpls ping and traceroute mechanism comprises of ability to traverse any path without having to validate the control plane state. RFC 8029 supports this mechanism with Nil FEC. The procedures described in RFC 8029 are mostly applicable when the Nil FEC is used as intermediate FEC in the label stack. When all labels in label stack are represented using single Nil FEC, it poses some challenges. This document introduces new TLV as additional extension to exisiting Nil FEC and describes mpls ping and traceroute procedures using Nil FEC with this additional extensions to overcome these challenges.

Authors

Deepti Rathi (deeptir@juniper.net)
Kapil Arora (kapilaro@juniper.net)
Shraddha Hegde (shraddha@juniper.net)
Zafar Ali (zali@cisco.com)
Nagendra Nainar (naikumar@cisco.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)