RE: Status on draft-chopps-isis-bfd-tlv-00.txt
Saravana Kumar <saravanak@huawei.com> Sat, 26 November 2005 08:21 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EfvJI-00071h-9W; Sat, 26 Nov 2005 03:21:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EfvJF-000710-2z for rtg-bfd@megatron.ietf.org; Sat, 26 Nov 2005 03:21:27 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13624 for <rtg-bfd@ietf.org>; Sat, 26 Nov 2005 03:20:42 -0500 (EST)
Received: from szxga03-in.huawei.com ([61.144.161.55] helo=huawei.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Efvce-0000iz-JW for rtg-bfd@ietf.org; Sat, 26 Nov 2005 03:41:30 -0500
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IQJ001PRZ9E7Y@szxga03-in.huawei.com> for rtg-bfd@ietf.org; Sat, 26 Nov 2005 16:22:26 +0800 (CST)
Received: from szxml01-in ([172.24.1.3]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IQJ00CXVZ9E4H@szxga03-in.huawei.com> for rtg-bfd@ietf.org; Sat, 26 Nov 2005 16:22:26 +0800 (CST)
Received: from saravanapc ([10.110.102.116]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0IQJ00KNKZMJJQ@szxml01-in.huawei.com>; Sat, 26 Nov 2005 16:30:20 +0800 (CST)
Date: Sat, 26 Nov 2005 16:17:01 +0800
From: Saravana Kumar <saravanak@huawei.com>
In-reply-to: <A16B2DB8-1107-453F-A32B-B76344960D16@rawdofmt.org>
To: 'Christian Hopps' <chopps@rawdofmt.org>
Message-id: <000001c5f261$c76435b0$74666e0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook, Build 10.0.3416
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit
Cc: rtg-bfd@ietf.org
Subject: RE: Status on draft-chopps-isis-bfd-tlv-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
Chris, I went through the draft and I think it would be an useful addition to ISIS. However I have a couple of suggestions to add to the draft. - the behaviour in a multi topology scenario needs to be specified. - the new TLV should be able to specify the BFD capability for different data protocols. This would be useful if some implementation supports BFD for one particular protocol only. Thanks, Saravana -----Original Message----- From: rtg-bfd-bounces@ietf.org [mailto:rtg-bfd-bounces@ietf.org] On Behalf Of Christian Hopps Sent: Saturday, November 26, 2005 1:54 AM To: rtg-bfd@ietf.org Subject: Status on draft-chopps-isis-bfd-tlv-00.txt I would like to propose making draft-chopps-isis-bfd-tlv-00.txt a WG document. This was mentioned back at IETF 62 (although I think the draft was not present yet :); however, I don't recall if it has been brought up on the list or not. Chris.
- Status on draft-chopps-isis-bfd-tlv-00.txt Christian Hopps
- RE: Status on draft-chopps-isis-bfd-tlv-00.txt Saravana Kumar
- Re: Status on draft-chopps-isis-bfd-tlv-00.txt David Ward