Label Switched Path (LSP) Self-Ping | Zendy

R. Bonica | Zendy; Ina Minei | Zendy; Michael Conn | Zendy; Dante Pacella | Zendy; Luis Tomotaki | Zendy

AI Assistant Blog Pricing

Home ZAIA Blog

Open Access

Label Switched Path (LSP) Self-Ping

Author(s) -

R. Bonica,

Ina Minei,

Michael Conn,

Dante Pacella,

Luis Tomotaki

Publication year - 2016

Publication title -

rfc

Language(s) - English

Resource type - Reports

DOI - 10.17487/rfc7746

Subject(s) - ping (video games) , computer science , computer network , router , internet control message protocol , path (computing) , downstream (manufacturing) , state (computer science) , network packet , engineering , operations management , algorithm

When certain RSVP-TE optimizations are implemented, ingress LabelSwitching Router (LSRs) can receive RSVP RESV messages beforeforwarding state has been installed on all downstream nodes. Accordingto the RSVP-TE specification, the ingress LSR can forward trafficthrough a Label Switched Path (LSP) as soon as it receives a RESVmessage. However, if the ingress LSR forwards traffic through the LSPbefore forwarding state has been installed on all downstream nodes,traffic can be lost. This document describes LSP Self-ping. When aningress LSR receives an RESV message, it can invoke LSP Self-pingprocedures to ensure that forwarding state has been installed on alldownstream nodes. LSP Self-ping is a new protocol. It is not anextension of LSP Ping. Although LSP Ping and LSP Self-ping are namedsimilarly, each is designed for a unique purpose. Each protocollistens on its own UDP port and executes its own procedures. LSPSelf-ping is an extremely lightweight mechanism. It does not consumecontrol-plane resources on transit or egress LSRs.

The content you want is available to Zendy users.

Already have an account? Click here to sign in.

Having issues? You can contact us here

Accelerating Research