Multiple BFD sessions over one path

Mach Chen <mach@huawei.com> Sat, 19 September 2009 03:27 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 EF6CC3A68CC for <rtg-bfd@core3.amsl.com>; Fri, 18 Sep 2009 20:27:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.083
X-Spam-Level: *
X-Spam-Status: No, score=1.083 tagged_above=-999 required=5 tests=[AWL=-1.023, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, STOX_REPLY_TYPE=0.001]
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 Vi8no-Uhn0-G for <rtg-bfd@core3.amsl.com>; Fri, 18 Sep 2009 20:27:15 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 21D8C3A6824 for <rtg-bfd@ietf.org>; Fri, 18 Sep 2009 20:27:15 -0700 (PDT)
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KQ700MGN8AJBU@szxga01-in.huawei.com> for rtg-bfd@ietf.org; Sat, 19 Sep 2009 11:27:56 +0800 (CST)
Received: from m55527c ([10.111.12.100]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KQ700FO58AH2F@szxga01-in.huawei.com> for rtg-bfd@ietf.org; Sat, 19 Sep 2009 11:27:55 +0800 (CST)
Date: Sat, 19 Sep 2009 11:27:45 +0800
From: Mach Chen <mach@huawei.com>
Subject: Multiple BFD sessions over one path
To: rtg-bfd@ietf.org
Message-id: <B0D01528858543EF97B47C4B99BB775D@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="gb2312"; reply-type="original"
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3
X-MSMail-priority: Normal
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 03:27:16 -0000

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