Why need single hop BFD? Does single Hop BFD requires to travese all possoble links beween the two neighbors?
Linda Dunbar <ldunbar@huawei.com> Sun, 08 November 2009 13:10 UTC
Return-Path: <ldunbar@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 89D0F3A68B5 for <rtg-bfd@core3.amsl.com>; Sun, 8 Nov 2009 05:10:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.668
X-Spam-Level:
X-Spam-Status: No, score=-1.668 tagged_above=-999 required=5 tests=[AWL=-0.929, BAYES_20=-0.74, HTML_MESSAGE=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 DxK0Gvj-Ix2y for <rtg-bfd@core3.amsl.com>; Sun, 8 Nov 2009 05:10:40 -0800 (PST)
Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211]) by core3.amsl.com (Postfix) with ESMTP id 19B073A684A for <rtg-bfd@ietf.org>; Sun, 8 Nov 2009 05:10:40 -0800 (PST)
Received: from huawei.com (usaga01-in [172.18.4.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KSS00ITFKMHNC@usaga01-in.huawei.com> for rtg-bfd@ietf.org; Sun, 08 Nov 2009 05:11:05 -0800 (PST)
Received: from L735042 (host-128-155.meeting.ietf.org [133.93.128.155]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KSS00FOJKLKHK@usaga01-in.huawei.com> for rtg-bfd@ietf.org; Sun, 08 Nov 2009 05:11:05 -0800 (PST)
Date: Sun, 08 Nov 2009 07:10:34 -0600
From: Linda Dunbar <ldunbar@huawei.com>
Subject: Why need single hop BFD? Does single Hop BFD requires to travese all possoble links beween the two neighbors?
To: 'Dave Katz' <dkatz@juniper.net>, dward@cisco.com
Message-id: <001001ca6074$ef084590$9b805d85@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/alternative; boundary="Boundary_(ID_pE0TtUEMAUx0oh0C0T6eyg)"
Thread-index: Acpf6bt91lV0hlfDT6Gq94XiiKQf+g==
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: Sun, 08 Nov 2009 13:10:43 -0000
Dave and David, Forgive me for not aware of the history of the BFD development. Reading through the "BFD for IPv4 and IPv6 (Single Hop)" (draft-ietf-bfd-v4v6-1hop-10.txt), I am not clear why single hop BFD is needed, especially for two immediately connected neighbors. There is Hello message between two immediate neighbors. If two immediate neighbors need logical layer to detect any failure between the two immediate neighbors, they can use the Hello message to achieve this purpose. Even though Hello message is from control Plane, it would be much less work for routers/LSRs to monitor the Hello messages than creating a new BFD session. Any physical media, like 802.3, SONET, DWDM wavelength all have physical failure indication. Each neighbor can also use the physical failure indication to declare the connectivity between two immediate neighbors, which is much faster than a BFD session, isn't it? It also needs less processing on the router/LSR, there won't be any proactive periodical sending BFD over the link anymore. Can you explain (or add to the document) what is the reason for having single hop BFD? Is single Hop BFD only for the Tunnel scenario? In Section 2 (Application and Limitation), the last paragraph does indicate that the transmitted packets are immediately routed back towards the sender on the interface over which they where sent if BFD Echo function is used. But when Link Aggregation is used to bundle the multiple parallel links between two neighbors, how does the network layer enforce which link to send back the "echo" message? Even if BFD ECHO can be enforced to be sent back on the same interface port so that the individual link's failure can be detected, what can this fault do when this fault can't affect the connectivity between the two immediate neighbors in control plane's view? All the links are bundled and two immediate neighbors are still connected? Thank you very much, Linda Dunbar Advanced Technology Dept, Wireline Networks, Huawei Technologies, Inc.