RFC 7746: Label Switched Path (LSP) Self-Ping
In plain English — editorial summary, not part of the RFC
When certain RSVP-TE optimizations are implemented, ingress Label Switching Router (LSRs) can receive RSVP RESV messages before forwarding state has been installed on all downstream nodes. According to the RSVP-TE specification, the ingress LSR can forward traffic through a Label Switched Path (LSP) as soon as it receives a RESV message. However, if the ingress LSR forwards traffic through the LSP before forwarding state has been installed on all downstream nodes, traffic can be lost. This document describes LSP Self-ping. When an ingress LSR receives an RESV message, it can invoke LSP Self-ping procedures to ensure that forwarding state has been installed on all downstream nodes. LSP Self-ping is a new protocol. It is not an extension of LSP Ping. Although LSP Ping and LSP Self-ping are named similarly, each is designed for a unique purpose. Each protocol listens on its own UDP port and executes its own procedures. LSP Self-ping is an extremely lightweight mechanism. It does not consume control-plane resources on transit or egress LSRs.
Document record
- Document ID
- RFC7746
- Published
- January 2016
- Authors
- R. Bonica; I. Minei; M. Conn; D. Pacella; L. Tomotaki
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 12
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7743Relayed Echo Reply Mechanism for Label Switched Path (LSP) PingCurrent
January 2016
- RFC 7752North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGPObsoleted
March 2016
- RFC 7740Simulating Partial Mesh of Multipoint-to-Multipoint (MP2MP) Provider Tunnels with Ingress ReplicationCurrent
January 2016
- RFC 7737Label Switched Path (LSP) Ping and Traceroute Reply Mode SimplificationCurrent
January 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 7759Configuration of Proactive Operations, Administration, and Maintenance (OAM) Functions for MPLS-Based Transport Networks Using Label Switched Path (LSP) PingCurrent
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
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?