Re: (no subject)

Reshad Rahman <rrahman@cisco.com> Tue, 25 October 2005 15:19 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUQa7-0005c9-Nz; Tue, 25 Oct 2005 11:19:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUQa6-0005bR-8x for rtg-bfd@megatron.ietf.org; Tue, 25 Oct 2005 11:19:18 -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 LAA28926 for <rtg-bfd@ietf.org>; Tue, 25 Oct 2005 11:19:03 -0400 (EDT)
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUQn4-0007np-1y for rtg-bfd@ietf.org; Tue, 25 Oct 2005 11:32:43 -0400
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-2.cisco.com with ESMTP; 25 Oct 2005 11:19:08 -0400
X-IronPort-AV: i="3.97,250,1125892800"; d="scan'208,217"; a="74375776:sNHT40810068"
Received: from cisco.com (dhcp-161-44-212-187.cisco.com [161.44.212.187]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j9PFJ6Ei025051; Tue, 25 Oct 2005 11:19:06 -0400 (EDT)
Message-ID: <435E4CEA.2080304@cisco.com>
Date: Tue, 25 Oct 2005 11:19:06 -0400
From: Reshad Rahman <rrahman@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20030208 Netscape/7
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: kalpana.yenishetti@wipro.com
References: <BD6DEA8C77182E4586B6BE33532EA48D38CD67@HYD-MKD-MBX01.wipro.com>
Content-Type: multipart/alternative; boundary="------------050900030003010608060303"
X-Spam-Score: 0.6 (/)
X-Scan-Signature: cd3fc8e909678b38737fc606dec187f0
Cc: rtg-bfd@ietf.org
Subject: Re: (no subject)
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

Mechanism for key exchange etc is outside the scope of the BFD protocol.

Regards,
Reshad.

kalpana.yenishetti@wipro.com wrote:

> Hi
>
>  
>
> How BFD handles simple password authentication?
>
>  
>
> Draft says,
>
>  
>
>In this method of authentication,
>
>   one or more Passwords (with corresponding Key IDs) are configured in
>
>   each system and one of these Password/ID pairs is carried in each BFD
>
>   Control packet.  The receiving system accepts the packet if the
>
>   Password and Key ID matches one of the Password/ID pairs configured
>
>   in that system.
>
>  
>
>  
>
> How the Node B knows about the configured Password/IDs in Node A, to 
> validate?
>
>  
>
> Thanks & Regards
>
> -Kalpana
>
>  
>