Re: iSCSI: DLB's [T.33] 10.5 Challenge Handshake Authentication Protocol (CHAP)

["Ofer Biran" <BIRAN@il.ibm.com>]

Rod,

Section 10 has a lot of such MUSTs for the required steps
of each authentication method. All these are applied of course
only when the relevant authentication method have been chosen
in the negotiation.

(or maybe you confused the "Algorithm" with "authentication method",
i.e., in

"For the Algorithm, as stated in [RFC1994], one value is required
to be implemented:
       5       (CHAP with MD5)..."

 the Algorithm is the CHAP_A key sent on the first CHAP step. )


 Regards,
  Ofer



Ofer Biran
Storage and Systems Technology
IBM Research Lab in Haifa
biran@il.ibm.com  972-4-8296253


"Rod Harrison" <rod.harrison@windriver.com>@ece.cmu.edu on 07/07/2002
18:03:32

Please respond to "Rod Harrison" <rod.harrison@windriver.com>

Sent by:    owner-ips@ece.cmu.edu


To:    <ips@ece.cmu.edu>
cc:
Subject:    iSCSI: DLB's [T.33] 10.5 Challenge Handshake Authentication
       Protocol (CHAP)



David,

 A MUST here seems to preclude the initiator not offering CHAP due to
administrative configuration. In fact the original SHOULD seems a bit
strong.

 I.e. is ...

 AuthMethod=none

 no longer to be valid?

 If so perhaps the text should change to require CHAP and / or none.7

 - Rod