Browse Prior Art Database

Label Switched Path (LSP) Self-Ping (RFC7746) Disclosure Number: IPCOM000245094D
Original Publication Date: 2016-Jan-01
Included in the Prior Art Database: 2016-Feb-08
Document File: 24 page(s) / 25K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Bonica: AUTHOR [+5]


Ingress Label Switching Routers (LSRs) use RSVP-TE [RFC3209] to establish MPLS Label Switched Paths (LSPs). The following paragraphs describe RSVP-TE procedures.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 11% of the total text.

Internet Engineering Task Force (IETF)                         R. Bonica Request for Comments: 7746                              Juniper Networks Category: Standards Track                                       I. Minei ISSN: 2070-1721                                             Google, Inc.                                                                  M. Conn                                                               D. Pacella                                                              L. Tomotaki                                                                  Verizon                                                             January 2016

                   Label Switched Path (LSP) Self-Ping


   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.

 Bonica, et al.               Standards Track                    [Page 1]
 RFC 7746                      LSP Self-Ping                 January 2016

 Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC...