From rtg-bfd-bounces@ietf.org Mon May 09 03:11:50 2005 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 ; 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 ; Mon, 9 May 2005 02:11:44 -0500 (CDT) Received: by ii0015exch002u.iprc.lucent.com with Internet Mail Service (5.5.2657.72) id ; Mon, 9 May 2005 12:41:42 +0530 Message-ID: <3BE48DD0EC7D3948BC183931D9150C21067990@ii0015exch001u.iprc.lucent.com> From: "Gupta, Bikram Kumar (Bikram)" To: "'rtg-bfd@ietf.org'" Date: Mon, 9 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" List-Unsubscribe: , List-Post: List-Help: List-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. From rtg-bfd-bounces@ietf.org Mon May 23 06:43:49 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DaAPV-0004TQ-88; Mon, 23 May 2005 06:43:49 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DaAPU-0004TL-Dc for rtg-bfd@megatron.ietf.org; Mon, 23 May 2005 06:43: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 GAA12140 for ; Mon, 23 May 2005 06:43:46 -0400 (EDT) Received: from bay21-f37.bay21.hotmail.com ([65.54.233.126] helo=hotmail.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DaAhR-0006M3-4k for rtg-bfd@ietf.org; Mon, 23 May 2005 07:02:22 -0400 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 23 May 2005 03:43:37 -0700 Message-ID: Received: from 57.250.229.136 by by21fd.bay21.hotmail.msn.com with HTTP; Mon, 23 May 2005 10:43:36 GMT X-Originating-IP: [57.250.229.136] X-Originating-Email: [elkou141061@hotmail.com] X-Sender: elkou141061@hotmail.com From: "M. ELK" To: rtg-bfd@ietf.org Date: Mon, 23 May 2005 10:43:36 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-OriginalArrivalTime: 23 May 2005 10:43:37.0342 (UTC) FILETIME=[4685C1E0:01C55F84] X-Spam-Score: 3.8 (+++) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Subject: Do we need "Demand Mode" X-BeenThere: rtg-bfd@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "RTG Area: Bidirectional Forwarding Detection DT" List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rtg-bfd-bounces@ietf.org Errors-To: rtg-bfd-bounces@ietf.org Hi The demand mode is a special use of async mode where the "desired min Tx Interval" and/or the "required min Rx interval" are set high enough. if any node (say X) wish to quickly verify the connection (on demand verification) , it could use/initiate the poll sequence . The node X transmitting (X) the poll sequence at an interval >= "Required Min Echo Rx Interval" advertised by "Y" Node Here the definition of "min Echo Rx Interval" is changing to specify the fastest rate the node could support receiving echo packer or BFD control with P bit set . Brgds _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/