What's the plan for BFD over 802.3 datalink?

"Gupta, Bikram Kumar (Bikram)" <bgupta@lucent.com> Mon, 09 May 2005 07:11 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DV2Qg-0007Kc-6n; Mon, 09 May 2005 03:11:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DV2Qe-0007KX-QD for rtg-bfd@megatron.ietf.org; Mon, 09 May 2005 03:11:48 -0400
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 DAA08793 for <rtg-bfd@ietf.org>; Mon, 9 May 2005 03:11:47 -0400 (EDT)
Received: from hoemail1.lucent.com ([192.11.226.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DV2fh-0003Ch-ON for rtg-bfd@ietf.org; Mon, 09 May 2005 03:27:22 -0400
Received: from ii0015exch002u.wins.lucent.com (h135-254-246-205.lucent.com [135.254.246.205]) by hoemail1.lucent.com (8.12.11/8.12.11) with ESMTP id j497Bhm1019974 for <rtg-bfd@ietf.org>; Mon, 9 May 2005 02:11:44 -0500 (CDT)
Received: by ii0015exch002u.iprc.lucent.com with Internet Mail Service (5.5.2657.72) id <KLNG0NMM>; Mon, 9 May 2005 12:41:42 +0530
Message-ID: <3BE48DD0EC7D3948BC183931D9150C21067990@ii0015exch001u.iprc.lucent.com>
From: "Gupta, Bikram Kumar (Bikram)" <bgupta@lucent.com>
To: "'rtg-bfd@ietf.org'" <rtg-bfd@ietf.org>
Date: Mon, 09 May 2005 12:41:40 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain; charset="iso-8859-1"
X-Spam-Score: 2.2 (++)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Subject: What's the plan for BFD over 802.3 datalink?
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

Hi All,

After IEEE 802.3ah clause 57 (Ethernet OAM), what is the plan of BFD on
ethernet
physical links?


>From BFD base draft:
   However, there are media that do not provide this kind of signaling (such
as
   Ethernet), and some media may not detect certain kinds of failures in the
path,
   for example, failing interfaces or forwarding engine components.


And from description of working group (ref. IETF web site):
   Topics for Possible Future Work:
   1. Document BFD directly over 802.3 in close collaboration and
synchronization
      with the IEEE.


Please clarify. Many thanks in advance.

Regards,
Bikram.