RE: New Version Notification for draft-mirsky-mpls-bfd-directed-00.txt

Mach Chen <mach.chen@huawei.com> Wed, 02 July 2014 01:57 UTC

Return-Path: <mach.chen@huawei.com>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B5041B27FC for <rtg-bfd@ietfa.amsl.com>; Tue, 1 Jul 2014 18:57:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level:
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] 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 f1C6lC2INxG8 for <rtg-bfd@ietfa.amsl.com>; Tue, 1 Jul 2014 18:57:24 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 187F21B27B3 for <rtg-bfd@ietf.org>; Tue, 1 Jul 2014 18:57:23 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BJL98363; Wed, 02 Jul 2014 01:57:22 +0000 (GMT)
Received: from SZXEMA409-HUB.china.huawei.com (10.82.72.41) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 2 Jul 2014 02:57:21 +0100
Received: from SZXEMA510-MBX.china.huawei.com ([169.254.3.190]) by SZXEMA409-HUB.china.huawei.com ([10.82.72.41]) with mapi id 14.03.0158.001; Wed, 2 Jul 2014 09:57:18 +0800
From: Mach Chen <mach.chen@huawei.com>
To: Gregory Mirsky <gregory.mirsky@ericsson.com>
Subject: RE: New Version Notification for draft-mirsky-mpls-bfd-directed-00.txt
Thread-Topic: New Version Notification for draft-mirsky-mpls-bfd-directed-00.txt
Thread-Index: AQHPlLkmcHLo4kmCjEWzfUskF7x6bpuLglYggAB+rEA=
Date: Wed, 02 Jul 2014 01:57:17 +0000
Message-ID: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE25DA34A5A@SZXEMA510-MBX.china.huawei.com>
References: <20140630231508.5203.4775.idtracker@ietfa.amsl.com> <7347100B5761DC41A166AC17F22DF1121B7E50F6@eusaamb103.ericsson.se>
In-Reply-To: <7347100B5761DC41A166AC17F22DF1121B7E50F6@eusaamb103.ericsson.se>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.97.72]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/rtg-bfd/Wk8eSHUW80znwDztW9u5zP1tvvU
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jul 2014 01:57:26 -0000

Hi Greg,

I have a quick review on the draft, well written and useful draft!

Couple years ago, we submitted a draft (http://tools.ietf.org/html/draft-chen-mpls-bfd-enhancement-01) that intend to solve the similar issue, glad we have the similar thought:-).

It also defines extensions to LSP Ping to direct the choose of the return path of BFD control packets. Please take a look.

Best regards,
Mach

> -----Original Message-----
> From: Rtg-bfd [mailto:rtg-bfd-bounces@ietf.org] On Behalf Of Gregory Mirsky
> Sent: Wednesday, July 02, 2014 2:19 AM
> To: mpls@ietf.org; rtg-bfd@ietf.org
> Subject: FW: New Version Notification for draft-mirsky-mpls-bfd-directed-00.txt
> 
> Dear All,
> we've posted a new draft. LSP Ping already is used to bootstrap a BFD session
> with BFD Discriminator TLV. A new BFD Reverse Path TLV is introduced in order to
> instruct a far-end BFD peer to use particular path for reverse direction of the BFD
> session.
> 
> Greatly appreciate your questions, comments.
> 
> 	Regards,
> 		Greg
> 
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Monday, June 30, 2014 4:15 PM
> To: Gregory Mirsky; Ilya Varlashkin; Jeff Tantsura; Gregory Mirsky; Jeff Tantsura;
> Ilya Varlashkin
> Subject: New Version Notification for draft-mirsky-mpls-bfd-directed-00.txt
> 
> 
> A new version of I-D, draft-mirsky-mpls-bfd-directed-00.txt
> has been successfully submitted by Greg Mirsky and posted to the IETF
> repository.
> 
> Name:		draft-mirsky-mpls-bfd-directed
> Revision:	00
> Title:		Bidirectional Forwarding Detection (BFD) Directed Return Path
> Document date:	2014-06-30
> Group:		Individual Submission
> Pages:		8
> URL:
> http://www.ietf.org/internet-drafts/draft-mirsky-mpls-bfd-directed-00.txt
> Status:
> https://datatracker.ietf.org/doc/draft-mirsky-mpls-bfd-directed/
> Htmlized:       http://tools.ietf.org/html/draft-mirsky-mpls-bfd-directed-00
> 
> 
> Abstract:
>    Bidirectional Forwarding Detection (BFD) is expected to monitor bi-
>    directional paths.  When forward direction of a BFD session is to
>    monitor explicitly routed path there is\ a need to be able to direct
>    far-end BFD peer to use specific path as reverse direction of the BFD
>    session.
> 
> 
> 
> 
> 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.
> 
> The IETF Secretariat