[mpls] I-D Action: draft-ietf-mpls-self-ping-06.txt
internet-drafts@ietf.org Sun, 01 November 2015 21:03 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AFA41A8A6E; Sun, 1 Nov 2015 13:03:43 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.7.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20151101210343.30817.89677.idtracker@ietfa.amsl.com>
Date: Sun, 01 Nov 2015 13:03:43 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/nMxqUMSQ_QULZruvAZfYl_HNs2I>
Cc: mpls@ietf.org
Subject: [mpls] I-D Action: draft-ietf-mpls-self-ping-06.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Nov 2015 21:03:43 -0000
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF. Title : LSP Self-Ping Authors : Ron Bonica Ina Minei Michael Conn Dante Pacella Luis Tomotaki Filename : draft-ietf-mpls-self-ping-06.txt Pages : 12 Date : 2015-11-01 Abstract: When certain RSVP-TE optimizations are implemented, ingress 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 an 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 light-weight mechanism. It does not consume control plane resources on transit or egress LSRs. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-mpls-self-ping/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-mpls-self-ping-06 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-mpls-self-ping-06 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/
- [mpls] I-D Action: draft-ietf-mpls-self-ping-06.t… internet-drafts