Re: Authentication

Dave Katz <dkatz@juniper.net> Thu, 17 March 2005 18:27 UTC

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 NAA03521; Thu, 17 Mar 2005 13:27:43 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DBzn3-0001xa-Jy; Thu, 17 Mar 2005 13:32:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DBzi5-0007ux-Mc; Thu, 17 Mar 2005 13:27:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DBzi4-0007up-0r for rtg-bfd@megatron.ietf.org; Thu, 17 Mar 2005 13:27:04 -0500
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 NAA03492 for <rtg-bfd@ietf.org>; Thu, 17 Mar 2005 13:27:00 -0500 (EST)
Received: from colo-dns-ext2.juniper.net ([207.17.137.64]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DBzmL-0001ws-0G for rtg-bfd@ietf.org; Thu, 17 Mar 2005 13:31:30 -0500
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 j2HIQrBm039841; Thu, 17 Mar 2005 10:26:53 -0800 (PST) (envelope-from dkatz@juniper.net)
Received: from [172.16.12.139] (nimbus-sf.juniper.net [172.16.12.139]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id j2HIQje48107; Thu, 17 Mar 2005 10:26:45 -0800 (PST) (envelope-from dkatz@juniper.net)
In-Reply-To: <200503170908.53160.cnogradi@laurelnetworks.com>
References: <200503170908.53160.cnogradi@laurelnetworks.com>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <13a4e73cebe5495e4785368aefb0dfb2@juniper.net>
Content-Transfer-Encoding: 7bit
From: Dave Katz <dkatz@juniper.net>
Date: Thu, 17 Mar 2005 11:29:17 -0700
To: Chris Nogradi <cnogradi@laurelnetworks.com>
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit
Cc: rtg-bfd@ietf.org
Subject: Re: Authentication
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit

On Mar 17, 2005, at 7:08 AM, Chris Nogradi wrote:

> Dave,
>
> I just noticed that you have added the following sentence to the base 
> draft in
> section 6.6:
>
> "Implementations MUST support SHA1 authentication.  Other froms of
> authentication are optional."
>
> Since you did not make mention of this in the document changes 
> sections, I
> assume that this does not mean that all implementations must support 
> at least
> this form of authentication.  Is the purpose of this sentence to say 
> that if
> an implementation uses authentication, it must support SHA1?

Sorry, I forgot to list that in the changes.

This is in there because the IESG will not allow the document to 
advance without it.  It's an interesting question as to whether they 
would allow the spec to say that an implementation could have no 
authentication at all;  my guess is that their stand is that the spec 
must require that all implementations support SHA1 authentication.

I also expect that vendors will make their own choices, as there is no 
significant difference between an implementation in which nobody turns 
on authentication and an implementation that does not even include it.

But that's the word from on high.

>
> BTW, there is a typo in this sentence as it should say "forms" instead 
> of
> "froms".

Thanks...

--Dave