Re: iSCSI Plugfest at UNH

["Julian Satran" <Julian_Satran@il.ibm.com>]

+++ in text Thanks, Julo

"Robert D. Russell" <rdr@mars.iol.unh.edu> on 19-07-2001 17:58:47

Please respond to "Robert D. Russell" <rdr@mars.iol.unh.edu>

To:   Julian Satran/Haifa/IBM@IBMIL
cc:   ips <ips@ece.cmu.edu>
Subject:  Re: iSCSI Plugfest at UNH





Julian:

Thank you for changing the last example in Appendix A to require the
SecurityContextComplete=yes handshake, and adding the phrase to 4.2:
"The Security Context Complete handshake MUST be performed if any of
the negotiating parties has offered a security/integrity item (even if it
is not selected)."

As part of this same change, you need to also delete the 3rd point in
section 4.3 quoted below (deletion marked with X):

>
>    Operational parameter negotiation during the login MAY be done:
>
>     - starting with the Login command if the initiator does not offer
>     any security/ integrity option
>     - starting immediately after the security/integrity negotiation if
>     the initiator and target perform such a negotiation
>  X  - starting immediately after the Login response with Final bit 0 if
>  X  the initiator does offer  security/integrity options but the target
>  X  chose none.

------
+++ Done +++
>
> +++ OK  (that is from the plugfest or personal?)+++

It acually came up -- someone was arguing that as stated he had to include
all session sepcific parameters in the first login command (literally).


-------

refering to section 1.2.4:

>  What do we have add. I assume that if we add more text the amount of
>  overlooked text will only increase +++


What about the wording:

   In "list" negotiation, the offering party sends for each key a list of
   values (which may include "none") in its order of preference.

+++ if that helps +++
Bob