I-D ACTION:draft-ietf-bfd-mpls-02.txt

Internet-Drafts@ietf.org Mon, 18 July 2005 22:50 UTC

Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DueRQ-0002Th-M0; Mon, 18 Jul 2005 18:50:28 -0400
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DueR1-0002Lm-KB; Mon, 18 Jul 2005 18:50:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06955; Mon, 18 Jul 2005 18:50:00 -0400 (EDT)
Received: from [] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DueuW-0000qx-Na; Mon, 18 Jul 2005 19:20:33 -0400
Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1DueR0-0008Bq-27; Mon, 18 Jul 2005 18:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1DueR0-0008Bq-27@newodin.ietf.org>
Date: Mon, 18 Jul 2005 18:50:02 -0400
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: rtg-bfd@ietf.org
Subject: I-D ACTION:draft-ietf-bfd-mpls-02.txt
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
Sender: rtg-bfd-bounces@ietf.org
Errors-To: rtg-bfd-bounces@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Bidirectional Forwarding Detection Working Group of the IETF.

	Title		: BFD For MPLS LSPs
	Author(s)	: R. Aggarwal, et al.
	Filename	: draft-ietf-bfd-mpls-02.txt
	Pages		: 11
	Date		: 2005-7-18
One desirable application of Bi-directional Forwarding Detection
   (BFD) is to detect a MPLS LSP data plane failure. LSP-Ping is an
   existing mechanism for detecting MPLS data plane failures and for
   verifying the MPLS LSP data plane against the control plane. BFD can
   be used for the former, but not for the latter. However the control
   plane processing required for BFD control packets is relatively
   smaller than the processing required for LSP-Ping messages. A
   combination of LSP-Ping and BFD can be used to provide faster data
   plane failure detection and/or make it possible to provide such
   detection on a greater number of LSPs. This document describes the
   applicability of BFD in relation to LSP-Ping for this application. It
   also describes procedures for using BFD in this environment.

A URL for this Internet-Draft is:

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-bfd-mpls-02.txt".

A list of Internet-Drafts directories can be found in
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
In the body type:
	"FILE /internet-drafts/draft-ietf-bfd-mpls-02.txt".
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the