RFC 7746 on Label Switched Path (LSP) Self-Ping
rfc-editor@rfc-editor.org Fri, 29 January 2016 02:05 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 624F51B36BF; Thu, 28 Jan 2016 18:05:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.903
X-Spam-Level:
X-Spam-Status: No, score=-101.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pDR49wNSUUwZ; Thu, 28 Jan 2016 18:05:44 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC1181B36BE; Thu, 28 Jan 2016 18:05:44 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id B361618000D; Thu, 28 Jan 2016 18:04:06 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7746 on Label Switched Path (LSP) Self-Ping
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160129020406.B361618000D@rfc-editor.org>
Date: Thu, 28 Jan 2016 18:04:06 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/7fNSrTzb_pncVwLWZP1GWoCA72Y>
Cc: drafts-update-ref@iana.org, mpls@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2016 02:05:46 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7746
Title: Label Switched Path (LSP) Self-Ping
Author: R. Bonica, I. Minei,
M. Conn, D. Pacella, L. Tomotaki
Status: Standards Track
Stream: IETF
Date: January 2016
Mailbox: rbonica@juniper.net,
inaminei@google.com,
meconn26@gmail.com,
dante.j.pacella@verizon.com,
luis.tomotaki@verizon.com
Pages: 12
Characters: 25146
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-mpls-self-ping-06.txt
URL: https://www.rfc-editor.org/info/rfc7746
DOI: http://dx.doi.org/10.17487/RFC7746
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.
This document is a product of the Multiprotocol Label Switching Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC