[storm] Consolidated iSCSI draft and TaskReporting

[Patrick MacArthur <[e-mail]>]

Hi,

I wanted to ask for clarification on an item appearing in the
consolidated iSCSI draft.

    "All keys defined in [RFC3720] MUST be supported by all
    compliant implementations; a NotUnderstood answer on any of the
    [RFC3720] keys therefore MUST be considered a protocol error and
    handled accordingly. For all other later keys, a NotUnderstood
    answer concludes the negotiation for a negotiated key whereas for
    a declarative key, a NotUnderstood answer simply informs the
    declarer of a lack of comprehension by the receiver."

I would like to request that the references to RFC3720 above be changed
to RFC3720 and RFC5048.  The comments on this list seem to indicate that
the baseline for the iSCSI work is on the combination of RFC 3720 and
RFC 5048, which I interpret to mean that it would be applicable only to
implementations compliant with both RFCs.  An implementation that claims
to be RFC 5048-compliant and responds with TaskReporting=NotUnderstood
is broken IMHO. In that case, is there a reason that we allow a
NotUnderstood response on an RFC 5048 key (TaskReporting)?

If the STORM WG is trying to ensure compatibility with the requirements
of RFC 3720 and RFC 5048 combined, it seems strange to be allowing
implementers not to implement the key requirement of RFC 5048.

Thanks,

-- 
Patrick MacArthur
Research and Development
iSCSI/OFA/IPv6 Consortia
UNH InterOperability Laboratory