Re: draft-ietf-bfd-base-03.txt comments

Dave Katz <dkatz@juniper.net> Wed, 17 August 2005 19:43 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E5Tom-0006Qi-KB; Wed, 17 Aug 2005 15:43:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E5Tol-0006Qd-EG for rtg-bfd@megatron.ietf.org; Wed, 17 Aug 2005 15:43:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20780 for <rtg-bfd@ietf.org>; Wed, 17 Aug 2005 15:43:17 -0400 (EDT)
Received: from colo-dns-ext2.juniper.net ([207.17.137.64]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E5UOL-0001SY-VU for rtg-bfd@ietf.org; Wed, 17 Aug 2005 16:20:07 -0400
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id j7HJh8Bm069234; Wed, 17 Aug 2005 12:43:08 -0700 (PDT) (envelope-from dkatz@juniper.net)
Received: from [172.16.12.13] (nimbus-sc.juniper.net [172.16.12.13]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id j7HJh8G78096; Wed, 17 Aug 2005 12:43:08 -0700 (PDT) (envelope-from dkatz@juniper.net)
In-Reply-To: <43038C20.7000102@redback.com>
References: <4303778F.1080304@redback.com> <A3ECA8A9-8183-4200-9F8E-5D7C13F717FA@juniper.net> <43038C20.7000102@redback.com>
Mime-Version: 1.0 (Apple Message framework v734)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <0AE90888-5651-4272-8D0D-FF1536ADA3A4@juniper.net>
Content-Transfer-Encoding: 7bit
From: Dave Katz <dkatz@juniper.net>
Date: Wed, 17 Aug 2005 12:43:07 -0700
To: Chezhian Renganathan <chezhian@redback.com>
X-Mailer: Apple Mail (2.734)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit
Cc: rtg-bfd@ietf.org
Subject: Re: draft-ietf-bfd-base-03.txt comments
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

> Would it help the processing cost if done similar to the auth field  
> which is controlled by the "A" flag.?
> Apart from reducing the overhead there is some bandwidth being  
> saved too. For instance, when
> asynchronous mode is active across end systems (and potentially  
> multiple sessions),
> with no echo support, with a 10 msecs tx interval, we could be  
> sending these 4 bytes
> unnecessarily over the period of the session(s) uptime which could  
> run into several days
> between interruptions.

The authentication stuff was made optional partly because of its size  
and complexity (there are environments in which it is unnecessary and  
would stand in the way of efficient implementation in silicon) and  
partly for backward compatibility (the authentication stuff was added  
later in the process.)

The bandwidth savings is essentially invisible (it's totally  
invisible on Ethernet given the minimum packet size requirements.)   
Even at 10 msec intervals at 10Mbps it consumes only an additional . 
03% of the bandwidth, if my math serves.  Just not worth the trouble.

--Dave