Authentication

Chris Nogradi <cnogradi@laurelnetworks.com> Thu, 17 March 2005 14:10 UTC

From: Chris Nogradi <cnogradi@laurelnetworks.com>
Organization: Laurel Networks
To: Dave Katz <dkatz@juniper.net>
Date: Thu, 17 Mar 2005 09:08:53 -0500
User-Agent: KMail/1.6.2
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-Id: <200503170908.53160.cnogradi@laurelnetworks.com>
Content-Transfer-Encoding: 7bit
Cc: rtg-bfd@ietf.org
Subject: Authentication
Precedence: list
Sender: rtg-bfd-bounces@ietf.org
Errors-To: rtg-bfd-bounces@ietf.org
Content-Transfer-Encoding: 7bit

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?

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

Thanks,

Chris

Authentication Chris Nogradi
Re: Authentication Pekka Savola
Re: Authentication Dave Katz
Re: Authentication Dave Katz
RE: Authentication Gray, Eric
Re: Authentication Dave Katz
Re: Authentication David Ward