IETF Logo Mail Archive

Re: Status on draft-chopps-isis-bfd-tlv-00.txt

David Ward <dward@cisco.com> Mon, 28 November 2005 18:52 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 1Ego79-0005wp-6N; Mon, 28 Nov 2005 13:52:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ego77-0005tz-Ow for rtg-bfd@megatron.ietf.org; Mon, 28 Nov 2005 13:52:33 -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 NAA19761 for <rtg-bfd@ietf.org>; Mon, 28 Nov 2005 13:51:50 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EgoQz-00029s-AG for rtg-bfd@ietf.org; Mon, 28 Nov 2005 14:13:06 -0500
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-3.cisco.com with ESMTP; 28 Nov 2005 10:52:12 -0800
X-IronPort-AV: i="3.97,385,1125903600"; d="scan'208"; a="371069289:sNHT805008826"
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id jASIq3eW021472; Mon, 28 Nov 2005 10:52:09 -0800 (PST)
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 28 Nov 2005 10:52:03 -0800
Received: from [171.71.139.200] ([171.68.225.134]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 28 Nov 2005 10:52:02 -0800
User-Agent: Microsoft-Entourage/10.1.6.040913.0
Date: Mon, 28 Nov 2005 12:52:15 -0600
From: David Ward <dward@cisco.com>
To: Saravana Kumar <saravanak@huawei.com>, 'Christian Hopps' <chopps@rawdofmt.org>, David Ward <dward@cisco.com>, Dave Katz <dkatz@juniper.net>
Message-ID: <BFB0ADFF.295C1%dward@cisco.com>
In-Reply-To: <000001c5f261$c76435b0$74666e0a@china.huawei.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 28 Nov 2005 18:52:02.0643 (UTC) FILETIME=[D1EA9230:01C5F44C]
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
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

Should this be in the ISIS WG since ISIS bits are changing? I think so as no
BFD bits are changing. I will contact the ISIS WG chairs.

-DWard


On 11/26/05 2:17 AM, "Saravana Kumar" <saravanak@huawei.com> wrote:

> 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.
>

v2.23.0 | Report a Bug | By Email