[mpls] I-D Action: draft-ietf-mpls-self-ping-05.txt

internet-drafts@ietf.org Fri, 02 October 2015 15:25 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E2281B2C16; Fri, 2 Oct 2015 08:25:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 JN4ZJviuaZb8; Fri, 2 Oct 2015 08:25:31 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EA3FF1B2C0F; Fri, 2 Oct 2015 08:25:30 -0700 (PDT)
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.4.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20151002152530.24961.40716.idtracker@ietfa.amsl.com>
Date: Fri, 02 Oct 2015 08:25:30 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/qVtZ5DQJPHSgocuOzTqr5_Z5KBs>
Cc: mpls@ietf.org
Subject: [mpls] I-D Action: draft-ietf-mpls-self-ping-05.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: Fri, 02 Oct 2015 15:25:32 -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-05.txt
	Pages           : 12
	Date            : 2015-10-02

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-05

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mpls-self-ping-05


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/