[Internet-Drafts@ietf.org: I-D ACTION:draft-suping-bfd-mpls-fecmismatch-00.txt]

Jeffrey Haas <jhaas@nexthop.com> Thu, 24 February 2005 02:52 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13883; Wed, 23 Feb 2005 21:52:09 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D49Ta-0001wo-6s; Wed, 23 Feb 2005 22:15:46 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3z30-0006ty-3j; Wed, 23 Feb 2005 11:07:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3z2v-0006tf-UB for rtg-bfd@megatron.ietf.org; Wed, 23 Feb 2005 11:07:32 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03066 for <rtg-bfd@ietf.org>; Wed, 23 Feb 2005 11:07:20 -0500 (EST)
Received: from dns.nexthop.com ([65.247.36.216] helo=aa-mx1.nexthop.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3zPX-0006Oo-ST for rtg-bfd@ietf.org; Wed, 23 Feb 2005 11:30:52 -0500
Received: from localhost (localhost [127.0.0.1]) by aa-mx1.nexthop.com (Postfix) with ESMTP id 323972D4D18; Wed, 23 Feb 2005 11:07:13 -0500 (EST)
Received: from aa-mx1.nexthop.com ([127.0.0.1]) by localhost (aa-mx1.nexthop.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 74523-02-4; Wed, 23 Feb 2005 11:07:11 -0500 (EST)
Received: from jhaas.nexthop.com (jhaas.nexthop.com [65.247.36.31]) by aa-mx1.nexthop.com (Postfix) with ESMTP id E53D92D4D2F; Wed, 23 Feb 2005 11:07:11 -0500 (EST)
Received: (from jhaas@localhost) by jhaas.nexthop.com (8.11.6/8.11.6) id j1NG7AO18807; Wed, 23 Feb 2005 11:07:10 -0500 (EST)
Date: Wed, 23 Feb 2005 11:07:10 -0500
From: Jeffrey Haas <jhaas@nexthop.com>
To: rtg-bfd@ietf.org
Message-ID: <20050223160710.GJ24296@nexthop.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i
X-Virus-Scanned: by amavisd-new at nexthop.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Subject: [Internet-Drafts@ietf.org: I-D ACTION:draft-suping-bfd-mpls-fecmismatch-00.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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e

It would appear that at least 3 of our core documents have cleared the
Internet-Drafts people:  The base draft, single hop v4/v6, MPLS LSP.

There is an independent submission targeted towards some changes to the
BFD protocol.  I would like to request that the working group take a first
pass at commenting on this proposal.  If WG discussion warrants it, we'll
allocate a timeslot at the upcoming meeting for further discussion.

----- Forwarded message from Internet-Drafts@ietf.org -----

Date: Fri, 18 Feb 2005 15:20:55 -0500
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-suping-bfd-mpls-fecmismatch-00.txt
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: internet-drafts@ietf.org
List-Id: i-d-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=subscribe>
Errors-To: i-d-announce-bounces@ietf.org
X-Virus-Scanned: by amavisd-new at nexthop.com
X-OriginalArrivalTime: 18 Feb 2005 21:04:54.0180 (UTC) FILETIME=[7E6B5640:01C515FD]

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: BFD Extensions for MPLS FEC mismatch detection
	Author(s)	: Z. Suping
	Filename	: draft-suping-bfd-mpls-fecmismatch-00.txt
	Pages		: 6
	Date		: 2005-2-18
	
BFD mechanism [BFD] was original designed to detect failures in 
   communication with a forwarding plane next hop. BFD operates on top 
   of any data protocol being forwarded between two systems. 

   This document describes how to use the BFD mechanism for detecting 
   the MPLS FEC mismatch. The proposal is based on the FEC mismatch
   mechanism of ITU-T Y.1713. 

   The proposed solution covers the mpls network when use BFD as the
   fault detection mechanism.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-suping-bfd-mpls-fecmismatch-00.txt

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-suping-bfd-mpls-fecmismatch-00.txt".

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-suping-bfd-mpls-fecmismatch-00.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
Internet-Draft.


_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce


----- End forwarded message -----

-- 
Jeff Haas 
NextHop Technologies