Re: Multiple BFD sessions over one path

Mach Chen <mach@huawei.com> Sat, 19 September 2009 08:06 UTC

Return-Path: <mach@huawei.com>
X-Original-To: rtg-bfd@core3.amsl.com
Delivered-To: rtg-bfd@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A02093A6A42 for <rtg-bfd@core3.amsl.com>; Sat, 19 Sep 2009 01:06:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.731
X-Spam-Level:
X-Spam-Status: No, score=0.731 tagged_above=-999 required=5 tests=[AWL=-0.263, BAYES_05=-1.11, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id og981z1ehzOh for <rtg-bfd@core3.amsl.com>; Sat, 19 Sep 2009 01:06:35 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id CBBA23A6A37 for <rtg-bfd@ietf.org>; Sat, 19 Sep 2009 01:06:34 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KQ700AMDL887G@szxga03-in.huawei.com> for rtg-bfd@ietf.org; Sat, 19 Sep 2009 16:07:20 +0800 (CST)
Received: from m55527c ([10.111.12.100]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KQ700HE0L87FI@szxga03-in.huawei.com> for rtg-bfd@ietf.org; Sat, 19 Sep 2009 16:07:20 +0800 (CST)
Date: Sat, 19 Sep 2009 16:07:16 +0800
From: Mach Chen <mach@huawei.com>
Subject: Re: Multiple BFD sessions over one path
In-reply-to: <52B6048D-137E-4B97-A688-686134B32D92@juniper.net>
To: Dave Katz <dkatz@juniper.net>
Message-id: <96CF4B519831459FAEE47FB142EE2BB0@m55527c>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V14.0.8064.206
X-Mailer: Microsoft Windows Live Mail 14.0.8064.206
Content-type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="response"
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3
X-MSMail-priority: Normal
References: <B0D01528858543EF97B47C4B99BB775D@m55527c> <52B6048D-137E-4B97-A688-686134B32D92@juniper.net>
Cc: rtg-bfd@ietf.org
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 19 Sep 2009 08:06:35 -0000

Hi Dave,

Thanks for your response!

Based on your explanation, the point is whether there is a way to 
demultiplex the initial patcket, if there is, means no need to limit the BFD 
sesion. So, IMHO, it's better to clarify this in 1hop(since the draft is 
still in IESG review state, seems not too late to do it:-).

Have a good weekend!

Best regards,
Mach


--------------------------------------------------
From: "Dave Katz" <dkatz@juniper.net>
Sent: Saturday, September 19, 2009 2:39 PM
To: "Mach Chen" <mach@huawei.com>
Cc: <rtg-bfd@ietf.org>
Subject: Re: Multiple BFD sessions over one path

> The point of the text in 1hop is that there isn't any use in having  more 
> than one session over a "path", and in any case it can't be done  because 
> there would be no way to demultiplex the initial packet of  multiple 
> sessions on the same "path" (because the first packet carries 
> discriminator 0).
>
> But diffserv is essentially a tunnel of sorts;  each service level has 
> potentially different forwarding characteristics, so it may be useful  to 
> run BFD over more than one level (and the sessions can be  demultiplexed 
> because they are contextualized by the diffserv level).
>
> Essentially, each diffserv service level is considered to be a  separate 
> path, not unlike GRE or IPsec or what have you.
>
> Implementors are free to do as they please;  the point of the text is  to 
> not preclude creative use of BFD where it can be useful.
>
> --Dave
>
>
>
> On Sep 18, 2009, at 9:27 PM, Mach Chen wrote:
>
>> Hi,
>>
>> After reading the two drafts (draft-ietf-bfd-generic-05 and draft- 
>> ietf-bfd-v4v6-1hop-09), I have some confusion about the session 
>> limitation over a specific network-layer path.
>>
>> Section 2 of draft-ietf-bfd-v4v6-1hop-09 says:
>> "Each BFD session between a pair of systems MUST traverse a separate 
>> network-layer path in both directions..."
>>
>> But section 6 of draft-ietf-bfd-generic-05 says:
>> "...if multiple differentiated services [DIFFSERV] are being  operated 
>> over IPv4, an independent BFD session may be run for each  service 
>> level...", this implicates that there may be mulitiple BFD  sessions over 
>> one network-layer(ipv4) path, but it seems that this  is not allowed in 
>> draft-ietf-bfd-v4v6-1hop-09. How to understand  this conflict?  or do I 
>> miss something?
>>
>> Best regards,
>> Mach Chen
>>
>>
>>
>>
>