RFC 7743: Relayed Echo Reply Mechanism for Label Switched Path (LSP) Ping
In plain English — editorial summary, not part of the RFC
In some inter-AS (Autonomous System) and inter-area deployment scenarios for RFC 4379 ("Label Switched Path (LSP) Ping and Traceroute"), a replying Label Switching Router (LSR) may not have the available route to an initiator, and the Echo Reply message sent to the initiator would be discarded, resulting in false negatives or a complete failure of operation of the LSP Ping and Traceroute. This document describes extensions to the LSP Ping mechanism to enable the replying LSR to have the capability to relay the Echo Response by a set of routable intermediate nodes to the initiator. This document updates RFC 4379.
Document record
- Document ID
- RFC7743
- Published
- January 2016
- Authors
- J. Luo; L. Jin; T. Nadeau; G. Swallow
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 18
- Also known as
- —
- Updates:
- RFC 4379
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7740Simulating Partial Mesh of Multipoint-to-Multipoint (MP2MP) Provider Tunnels with Ingress ReplicationCurrent
January 2016
- RFC 7746Label Switched Path (LSP) Self-PingCurrent
January 2016
- RFC 7737Label Switched Path (LSP) Ping and Traceroute Reply Mode SimplificationCurrent
January 2016
- RFC 7752North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGPObsoleted
March 2016
- RFC 7734Support for Shortest Path Bridging MAC Mode over Ethernet VPN (EVPN)Current
January 2016
- RFC 7733Applicability Statement: The Use of the Routing Protocol for Low-Power and Lossy Networks (RPL) Protocol Suite in Home Automation and Building ControlCurrent
February 2016
- RFC 7732Forwarder Policy for Multicast with Admin-Local Scope in the Multicast Protocol for Low-Power and Lossy Networks (MPL)Current
February 2016
- RFC 7731Multicast Protocol for Low-Power and Lossy Networks (MPL)Current
February 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?