Re: some comment to draft-ietf-bfd-base-02.txt

Dave Katz <dkatz@juniper.net> Sat, 26 March 2005 06:56 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 BAA05702; Sat, 26 Mar 2005 01:56:00 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DF5JI-00014t-06; Sat, 26 Mar 2005 02:02:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DF5By-0007UB-LR; Sat, 26 Mar 2005 01:54:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DF5Bv-0007Tz-9V for rtg-bfd@megatron.ietf.org; Sat, 26 Mar 2005 01:54:40 -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 BAA05634 for <rtg-bfd@ietf.org>; Sat, 26 Mar 2005 01:54:38 -0500 (EST)
Received: from colo-dns-ext1.juniper.net ([207.17.137.57]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DF5Hw-00012Y-Qo for rtg-bfd@ietf.org; Sat, 26 Mar 2005 02:00:54 -0500
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id j2Q6s9959354; Fri, 25 Mar 2005 22:54:15 -0800 (PST) (envelope-from dkatz@juniper.net)
Received: from [172.16.12.139] (nimbus-sf.juniper.net [172.16.12.139]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id j2Q6s3e09619; Fri, 25 Mar 2005 22:54:03 -0800 (PST) (envelope-from dkatz@juniper.net)
In-Reply-To: <0IDX00G7IX2LQZ@szxml01-in.huawei.com>
References: <0IDX00G7IX2LQZ@szxml01-in.huawei.com>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset="ISO-2022-JP"; format="flowed"
Message-Id: <7a4b43d33a21cd43a3f80cbba38fef94@juniper.net>
Content-Transfer-Encoding: 7bit
From: Dave Katz <dkatz@juniper.net>
Date: Fri, 25 Mar 2005 23:54:01 -0700
To: zhaisuping@huawei.com
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit
Cc: "'rtg-bfd@ietf.org'" <rtg-bfd@ietf.org>, David Ward <dward@cisco.com>
Subject: Re: some comment to draft-ietf-bfd-base-02.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: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit

On Mar 25, 2005, at 8:41 PM, zhaisuping wrote:

> Dave2,
> In the draft-ietf-bfd-base-02.txt, 6.3. (Demultiplexing and the 
> Discriminator Fields), it reads as following,  
>
>    The method of demultiplexing the initial packets (in which Your
>    Discriminator is zero) is application-dependent, and is thus outside
>    the scope of this specification.  
>
> One problem is that when the two nodes running BFD session are belong 
> to different providers, So there should be some specification on the 
> interworking problem. I propose to add some general description about 
> this some like the following,
>
>    When use OSPF as the BFD bootstrap mechanism, the method fo 
> demutipexing the initail packets is......
>    When use IS-IS as the BFD bootstrap mechanism, the method fo 
> demutipexing the initail packets is......
>    When use MPLS-Ping as the BFD bootstrap mechanism, the method fo 
> demutipexing the initail packets is......
>
>    Or the common TLV can be defined to these mechanism to bootstrap 
> BFD session.
>
> So I don't know if this is appropriate to the BFD base draft?

This is all specified in the application drafts.

--Dave