Re: [storm] iSER - one last issue

[<[e-mail]>]

Mike,

Thank you for the explanation, but I don't believe you've correctly stated
the intent of RFC 5046.  Here are some examples from RFC 5046's text:

1.5.  SCSI Read Overview

   The iSER Message is transferred to the target using a SendSE Message.

   The iSER layer at the target uses a SendInvSE Message to transfer the
   SCSI Response PDU back to the iSER layer at the initiator.

Similar language occurs in 1.6 SCSI Write Overview.

5.2.1.  Normal Connection Termination at the Initiator

   The iSER layer at the initiator MUST
   use a SendSE Message to send the Logout Request PDU to the target.

Similar language occurs in 5.2.2 for target side normal connection termination,
and more importantly in 7.3.1 SCSI Command:

   The iSER layer at the initiator MUST send the SCSI command in a
   SendSE Message to the target.

None of the quoted text permits use of Send instead of SendSE or SendInv
instead of SendInvSE.

What you propose to do effectively changes "MUST" to "should" (lower case,
weaker than "SHOULD"), and that sure looks like a change to RFC 5046.

Are there good implementation-based reasons to weaken these requirements now?

Does anyone else have a viewpoint on this topic?

Thanks,
--David

From: Michael Ko [mailto:[e-mail]]
Sent: Wednesday, January 18, 2012 2:22 PM
To: Black, David; [e-mail]
Subject: Re: iSER - one last issue

David,

Here is my rationale for using the lower case "should".

The intent of RFC5046 is that the Send Message type must be used instead of RDMA Reads or Writes.  The Solicited Event feature of the Send Message is provided as a convenience.  The receiver must still do the right thing in handling the Send Message regardless of whether the SE feature is used.  In other words, the sender is responsible for using the right format for the message (Send vs RDMA) but the receiver must not rely on the sender to determine how to handle the received message.  The same rationale goes for the Invalidate feature.

Mike
----- Original Message -----
From: [e-mail]<mailto:[e-mail]>
To: [e-mail]<mailto:[e-mail]> ; [e-mail]<mailto:[e-mail]>
Sent: Monday, January 16, 2012 2:06 PM
Subject: iSER - one last issue

Mike,

Thanks for getting the -08 version of the iSER draft posted.  I think that
draft addresses all of the open issues, but I have a question for the WG
about how to express the SendSE and SendInvSE requirements from RFC 5046.

The -08 version of the iSER draft expresses requirements for the SendSE
and SendInvSE messages (this is primarily for iSER over RDDP/iWARP) as:

The SendSE Message should be used if
supported by the RCaP layer (e.g., iWARP).

My reading of RFC 5046 is that its requirements are tighter - to accurately
reflect RFC 5046, I would replace "should" with "MUST" in the above text,
at least for iWARP.

In the alternative, if the "should"s remain, an explanatory item
needs to be added to the Appendix A list of changes from RFC 5046.

What do others think the right course of action is here, use "MUST" or
explain weakening of requirement to "should" ?

Thanks,
--David

From: [e-mail] [mailto:[e-mail]] On Behalf Of Michael Ko
Sent: Sunday, January 15, 2012 8:43 AM
To: [e-mail]
Subject: Re: [storm] I-D Action: draft-ietf-storm-iser-08.txt

This version contains all the updates as discussed in the latest exchanges with Hemal Shah and David Black.

Mike
----- Original Message -----
From: [e-mail]<mailto:[e-mail]>
To: [e-mail]<mailto:[e-mail]>
Cc: [e-mail]<mailto:[e-mail]>
Sent: Sunday, January 15, 2012 5:40 AM
Subject: [storm] I-D Action: draft-ietf-storm-iser-08.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the STORage Maintenance Working Group of the IETF.

Title           : iSCSI Extensions for RDMA Specification
Author(s)       : Michael Ko
                          Alexander Nezhinsky
Filename        : draft-ietf-storm-iser-08.txt
Pages           : 95
Date            : 2012-01-15

   iSCSI Extensions for RDMA provides the RDMA data transfer capability
   to iSCSI by layering iSCSI on top of an RDMA-Capable Protocol.  An
   RDMA-Capable Protocol provides RDMA Read and Write services, which
   enable data to be transferred directly into SCSI I/O Buffers without
   intermediate data copies.  This document describes the extensions to
   the iSCSI protocol to support RDMA services as provided by an RDMA-
   Capable Protocol.

   This document obsoletes RFC 5046.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-storm-iser-08.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-storm-iser-08.txt

_______________________________________________
storm mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/storm