Definition of Time to Live TLV for LSP-Ping Mechanisms
This RFC 7394 was published in 2014
LSP-Ping is a widely deployed Operation, Administration, and Maintenance (OAM) mechanism in MPLS networks.
However, in the present form, this mechanism is inadequate to verify connectivity of a segment of a Multi-Segment Pseudowire (MS-PW) and/or bidirectional co-routed Label Switched Path (LSP) from any node on the path of the MS-PW and/or bidirectional co-routed LSP.
This document defines a TLV to address this shortcoming.
RFC 7394 introduction
An MS-PW may span across multiple service provider networks.
In order to allow Service Providers (SPs) to verify segments of such MS-PWs from any node on the path of the MS-PW, any node along the path of the MS-PW, should be able to originate an MPLS Echo Request packet to any other node along the path of the MS-PW and receive the corresponding MPLS Echo Reply.
If the originator of the MPLS Echo Request is at the end of a MS-PW, the receiver of the request can send the reply back to the sender without knowing the hop-count distance of the originator.
The reply will be intercepted by the originator regardless of the TTL value on the reply packet.
But, if the originator is not at the end of the MS-PW, the receiver of the MPLS Echo Request may need to know how many hops away the originator
Click here to download RFC 7394: TXT format PDF format (coming soon)
Related Request for Comments
©2015 RFC-Base.org - all rights reserved.