LC comments <single hop>
Suping Zhai <zhaisuping@huawei.com> Fri, 08 July 2005 03:22 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DqjS4-0004iD-JC; Thu, 07 Jul 2005 23:22:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DqjS2-0004fy-Ma for rtg-bfd@megatron.ietf.org; Thu, 07 Jul 2005 23:22:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29812 for <rtg-bfd@ietf.org>; Thu, 7 Jul 2005 23:22:51 -0400 (EDT)
Received: from szxga01-in.huawei.com ([61.144.161.53] helo=huawei.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DqjtK-0002ZC-JR for rtg-bfd@ietf.org; Thu, 07 Jul 2005 23:51:08 -0400
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IJA00681HG2X8@szxga01-in.huawei.com> for rtg-bfd@ietf.org; Fri, 08 Jul 2005 11:24:02 +0800 (CST)
Received: from szxml01-in ([172.24.1.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IJA001PAHG18Q@szxga01-in.huawei.com> for rtg-bfd@ietf.org; Fri, 08 Jul 2005 11:24:01 +0800 (CST)
Received: from z11024 ([10.110.100.95]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0IJA00H5QHN52G@szxml01-in.huawei.com>; Fri, 08 Jul 2005 11:28:17 +0800 (CST)
Date: Fri, 08 Jul 2005 11:19:51 +0800
From: Suping Zhai <zhaisuping@huawei.com>
To: David Ward <dward@cisco.com>
Message-id: <0IJA00H5RHN52G@szxml01-in.huawei.com>
Organization: huawei
MIME-version: 1.0
X-Mailer: Foxmail 4.2 [cn]
Content-type: text/plain; charset="GB2312"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
Subject: LC comments <single hop>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: zhaisuping@huawei.com
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
Dear David and all bfd, I don't attend the last 62th IETF meeting, and I don't know the scope of "generic applicability" draft. But as I understand, if it's a "generic applicability" draft, if the IS-IS and OSPF application with BFD in draft-ietf-bfd-v4v6-1hop-02.txt should be extracted and to fill in that "generic applicabitly" and let draft-ietf-bfd-v4v6-1hop-02.txt dedicating to just the generally single hop issues? Best Regards, suping zhai July 8, 2005 >All - > As the base specifiction for BFD has stabilized as well as the >single hop specification, we are going to have a 3 week WG Last Call ending >July 31st. Assuming no major revisions (famous last words) will be required, >we will shepherd the drafts forward at that time. > >If you have comments, please reply to the WG and authors with the subject line: > >subject: LC comments < base spec | single hop> > >Here are the pointers to the docs. > >http://www.ietf.org/internet-drafts/draft-ietf-bfd-v4v6-1hop-02.txt > >http://www.ietf.org/internet-drafts/draft-ietf-bfd-base-02.txt > >In other news, as Dave and I agreed in the last WG meeting, we will be >submitting a "generic applicability" draft on how an app can boostrap BFD >sessions so that we don't need individual drafts for each of our favorite >protocols. Stay tuned. > >The new draft MIB may or may not be published in time for Paris. > > >-DWard
- LC comments <single hop> Suping Zhai