Internet Small Computer System Interface (iSCSI) Corrections and Clarifications
draft-ietf-ips-iscsi-impl-guide-09

[Ballot comment]
From Gen-ART Review by From: Suresh Krishnan

  Summary: This draft is ready for publication, but I have some
  suggestions.

  Comments: Overall the draft is well written and has a really well
  written IANA Considerations section.

  Minor
  =====

  * Section 4.1.2 c

  "c. Should receive the TMF Response concluding all the tasks in
      the set of affected tasks. "

  I am not sure of the intent of the sentence, but I believe it to be
  normative. So I think the "Should" needs to be replaced with a SHOULD.

  * It is really unclear from the draft how to differentiate between
  the following types of information
    - Updates to RFC3720
    - New behavior on top of RFC3720
    - Clarifications and implementation advice
  since they are intermingled throughout the document.

  * For section 11.2 iSCSI Opcodes, the document mentions the following

    "Fields to record in the registry: Assigned value, Who can
    originate (Initiator or Target), Operation Name and its
    associated RFC reference"

  Since the op codes can also be assigned using the Expert Review
  process, it should probably mention that the RFC reference is
  optional.

  Editorial
  =========

  * RFC2119 occurs twice in the references. Once as normative and once
  as informative

[Ballot discuss]
Please add a section that lists the updates to RFC 3720.  It will
  really help people trying to make updates to an implementation of
  RFC 3720.

[Ballot discuss]
Section 14 says:
  >
  > The type of authentication deployed is a local decision made by the
  > server operator.  Clients are likely to face authentication schemes
  > that vary across server deployments.  At a minimum, client and server
  > implementations MUST be capable of being configured to use HTTP Basic
  > Authentication [RFC2617] in conjunction with a TLS [RFC2246]
  > connection as defined in [RFC2818] (but note that [RFC2246] has been
  > superseded by [RFC4346]).  See [RFC4346] for more information on TLS.
  >
  The specification ought to say that it MUST support TLS 1.0 [RFC2246]
  or a sunsequent standards-track version of TLS, and that it MUST
  also support the conventions for using HTTP over TLS [RFC2818].

Last Call Comments:

Upon approval of this document, the IANA will
take the following Actions:

Action 1 (Section 11.2)

Upon approval of this document, the IANA will
in the following registry "iSCSI Parameters"
located at

http://www.iana.org/assignments/iscsi-parameters

create a new sub-registry "iSCSI Opcodes"


Namespace details: Numerical values that can fit
in one octet with most significant two bits
(bits 0 and 1) already designated  by [RFC3720],
bit 0 being reserved and bit 1 for immediate
delivery. Bit 2 is designated to identify the
originator of the opcode. Bit 2 = 0 for initiator
and Bit 2 = 1 for target


Allocation request guidance to requesters:

1) If initiator opcode and target opcode to
  identify the request and response of a
  new type of protocol operation are requested,
  assign the same lower five bits (i.e. Bit 3
  through Bit 7) for both opcodes, e.g. 0x13 and 0x33

2) If only the initiator opcode or target
  opcode is requested to identify a one-way
  protocol message (i.e. request without a
  response or a "response" without a request),
  assign an unused number from the appropriate
  category (i.e. Bit 2 set to 0 or 1 for
  initiator category or target category) and
  add the other pair member (i.e. same opcode
  with Bit 2 set to 1 or 0, respectively) to
  "Reserved to IANA" list.

3) If there are no other opcodes available to
  assign on a request for a new opcode except
  the reserved opcodes in the "Reserved to IANA"
  list, allocate the opcodes from the appropriate
  category (initiator or target).

Initial contents of this sub-registry will be:

Opcode Originator Operation Name Reference
------ ---------- -------------- ---------
0x00 Initiator NOP-Out [RFC3720]
0x01 Initiator SCSI Command [RFC3720]
0x02 Initiator SCSI Task Management [RFC3720]
function request
0x03 Initiator Login Request [RFC3720]
0x04 Initiator Text Request [RFC3720]
0x05 Initiator SCSI Data-Out [RFC3720]
0x06 Initiator Logout Request [RFC3720]
0x10 Initiator SNACK Request [RFC3720]
0x1c-0x1e Initiator Vendor specific codes [RFC3720]
0x20 Target NOP-In [RFC3720]
0x21 Target SCSI Response [RFC3720]
0x22 Target SCSI Task Management [RFC3720]
function response
0x23 Target Login Response [RFC3720]
0x24 Target Text Response [RFC3720]
0x25 Target SCSI Data-In [RFC3720]
0x26 Target Logout Response [RFC3720]
0x31 Target Ready To Transfer (R2T) [RFC3720]
0x32 Target Asynchronous Message [RFC3720]
0x3c-0x3e Target Vendor specific codes [RFC3720]
0x3f Target Reject [RFC3720]

"Reserved to IANA" opcodes: 0x11, 0x12, 0x1f, 0x30

Allocation Policy: Standards Action ([IANA]),
                  Expert Review ([IANA])

NOTE: Expert Assignment Required


Action 2 (Section 11.3):

Upon approval of this document, the IANA will
in the following registry "iSCSI Parameters"
located at

http://www.iana.org/assignments/iscsi-parameters

create a new sub-registry "iSCSI Text Keys"

Initial contents of this sub-registry will be:

Key Reference
---------- ---------
AuthMethod [RFC3720]
HeaderDigest [RFC3720]
DataDigest [RFC3720]
MaxConnections [RFC3720]
SendTargets [RFC3720]
TargetName [RFC3720]
InitiatorName [RFC3720]
TargetAlias [RFC3720]
InitiatorAlias [RFC3720]
TargetAddress [RFC3720]
TargetPortalGroupTag [RFC3720]
InitialR2T [RFC3720]
ImmediateData [RFC3720]
MaxRecvDataSegmentLength [RFC3720]
MaxBurstLength [RFC3720]
FirstBurstLength [RFC3720]
DefaultTime2Wait [RFC3720]
DefaultTime2Retain [RFC3720]
MaxOutstandingR2T [RFC3720]
DataPDUInOrder [RFC3720]
DataSequenceInOrder [RFC3720]
ErrorRecoveryLevel [RFC3720]
SessionType [RFC3720]
RDMAExtensions [iSER]
TargetRecvDataSegmentLength [iSER]
InitiatorRecvDataSegmentLength [iSER]
MaxOutstandingUnexpectedPDUs [iSER]
TaskReporting [RFC-ips-iscsi-impl-guide-08]

Allocation Policy: Standards Action ([IANA])

[ NOTE: Should this registry get alphabetized? ]


Action 3 (Section 11.4):

Upon approval of this document, the IANA will in
the following registry "iSCSI Parameters" located at

http://www.iana.org/assignments/iscsi-parameters

create a new sub-registry "iSCSI Asynchronous Events"

Initial contents of this sub-registry will be:

Event Number Description Reference
(one octet)
------------ ----------------------- ---------
0 SCSI Async Event [RFC3720]
1 Logout Request [RFC3720]
2 Connection drop notification [RFC3720]
3 Session drop notification [RFC3720]
4 Negotiation Request [RFC3720]
5 Task termination [RFC-ips-iscsi-impl-guide-08]
6-247 Reserved to IANA [RFC-ips-iscsi-impl-guide-08]
248-254 Vendor-unique [RFC-ips-iscsi-impl-guide-08]
255 Vendor-unique [RFC3720]

Allocation Policy: Standards Action ([IANA])


Action 4 (Section 11.5):

Upon approval of this document, the IANA will
in the following registry "iSCSI Parameters"
located at

http://www.iana.org/assignments/iscsi-parameters

create a new sub-registry "iSCSI TMF Codes"

Initial contents of this sub-registry will be:

TMF Code Description Reference
(7 bits)
-------- ----------- ---------
1 ABORT TASK [RFC3720]
2 ABORT TASK SET [RFC3720]
3 CLEAR ACA [RFC3720]
4 CLEAR TASK SET [RFC3720]
5 LOGICAL UNIT RESET [RFC3720]
6 TARGET WARM RESET [RFC3720]
7 TARGET COLD RESET [RFC3720]
8 TASK REASSIGN [RFC3720]
9-127 Reserved to IANA [RFC-ips-iscsi-impl-guide-08]

Allocation Policy: Standards Action ([IANA])


Action 5 (Section 11.6):

Upon approval of this document, the IANA will
in the following registry "iSCSI Parameters"
located at

http://www.iana.org/assignments/iscsi-parameters

create a new sub-registry "iSCSI Login Response
Status Codes"

Initial contents of this sub-registry will be:

Status Class Description Reference
(one octet)
----------- -------------------- ---------
0x00 Success [RFC3720]
0x01 Redirection [RFC3720]
0x02 Initiator Error [RFC3720]
0x03 Target Error [RFC3720]
0x04-0x0e Reserved to IANA [RFC-ips-iscsi-impl-guide-08]
0x0f Vendor-Unique [RFC-ips-iscsi-impl-guide-08]
0x10-0xff Reserved to IANA [RFC-ips-iscsi-impl-guide-08]

Allocation Policy: Standards Action ([IANA])


Action 6 (Section 11.6):

Upon approval of this document, the IANA will
in the following registry "iSCSI Parameters"
located at

http://www.iana.org/assignments/iscsi-parameters

in the sub-registry "iSCSI Login Response Status Codes"
create a new sub-sub-registry "Status-Detail
for Status-Class=0x00"

Initial contents of this sub-registry will be:

Status Class Status Code Description Reference
(fixed) (one octet)
----------- ----------- -------------------- ---------
0x00 0x00 Success [RFC3720]
0x00 0x01-0xff Reserved to IANA [RFC-ips-iscsi-impl-guide-08]

Allocation Policy: Standards Action ([IANA])


Action 7 (Section 11.6):

Upon approval of this document, the IANA will
in the following registry "iSCSI Parameters"
located at

http://www.iana.org/assignments/iscsi-parameters

in the sub-registry "iSCSI Login Response Status Codes"

create a new sub-sub-registry "Status-Detail
for Status-Class=0x01"

Initial contents of this sub-registry will be:

Status Class Status Code Description Reference
(fixed) (one octet)
----------- ----------- -------------------- ---------
0x01 0x01 Temporary move [RFC3720]
0x01 0x02 Permanent move [RFC3720]
0x01 0x03-0xff Reserved to IANA [RFC-ips-iscsi-impl-guide-08]

Allocation Policy: Standards Action ([IANA])


Action 8 (Section 11.6):

Upon approval of this document, the IANA will
in the following registry "iSCSI Parameters"
located at

http://www.iana.org/assignments/iscsi-parameters

in the sub-registry "iSCSI Login Response
Status Codes"

create a new sub-sub-registry "Status-Detail
for Status-Class=0x02"

Initial contents of this sub-registry will be:

Status Class Status Code Description Reference
(fixed) (one octet)
----------- ----------- -------------------- ---------
0x02 0x00 Miscellaneous [RFC3720]
0x02 0x01 Authentication failure [RFC3720]
0x02 0x02 Authorization failure [RFC3720]
0x02 0x03 Not found [RFC3720]
0x02 0x04 Target removed [RFC3720]
0x02 0x05 Unsupported version [RFC3720]
0x02 0x06 Too many connections [RFC3720]
0x02 0x07 Missing parameter [RFC3720]
0x02 0x08 Can't include in session [RFC3720]
0x02 0x09 Unsupported session type [RFC3720]
0x02 0x0a Non-existent session [RFC3720]
0x02 0x0b Invalid during login [RFC3720]
0x02 0x0c-0xff Reserved to IANA [RFC-ips-iscsi-impl-guide-08]


Allocation Policy: Standards Action ([IANA])


Action 9 (Section 11.6):

Upon approval of this document, the IANA will
in the following registry "iSCSI Parameters"
located at

http://www.iana.org/assignments/iscsi-parameters

in the sub-registry "iSCSI Login Response
Status Codes"

create a new sub-sub-registry "Status-Detail for
Status-Class=0x03"

Initial contents of this sub-registry will be:

Status Class Status Code Description Reference
(fixed) (one octet)
----------- ----------- -------------------- ---------
0x03 0x00 Target error [RFC3720]
0x03 0x01 Service unavailable [RFC3720]
0x03 0x02 Out of resources [RFC3720]
0x03 0x03-0xff Reserved to IANA [RFC-ips-iscsi-impl-guide-08]


Allocation Policy: Standards Action ([IANA])


Action 10 (Section 11.7):

Upon approval of this document, the IANA will
in the following registry "iSCSI Parameters"
located at

http://www.iana.org/assignments/iscsi-parameters

create a new sub-registry "iSCSI Reject
Reason Codes"

Initial contents of this sub-registry will be:

Reason Code Description Reference
(one octet)
----------- ------------------ ---------
0x01 Reserved [RFC3720]
0x02 Data digest error [RFC3720]
0x03 SNACK Reject [RFC3720]
0x04 Protocol Error [RFC3720]
0x05 Command not supported [RFC3720]
0x06 Immediate command reject [RFC3720]
0x07 Task in progress [RFC3720]
0x08 Invalid data ack [RFC3720]
0x09 Invalid PDU field [RFC3720]
0x0a Long op reject [RFC3720]
0x0b "Deprecated reason code" [RFC-ips-iscsi-impl-guide-08]
0x0c Waiting for Logout [RFC3720]
0x0d-oxff Reserved to IANA [RFC-ips-iscsi-impl-guide-08]

Allocation Policy: Standards Action ([IANA])


Action 11 (Section 11.8):

Upon approval of this document, the IANA will
in the following registry "iSCSI Parameters"
located at

http://www.iana.org/assignments/iscsi-parameters

create a new sub-registry "iSER Opcodes"

Initial contents of this sub-registry will be:

Opcode Operation Name Reference
(4 bits)
-------- ------------------- ---------
0x1 iSCSI control-type [iSER]
0x2 iSER Hello [iSER]
0x3 iSER HelloReply [iSER]
0x4-0xf Reserved to IANA [RFC-ips-iscsi-impl-guide-08]

Allocation Policy: Standards Action ([IANA])


We understand the above to be the only IANA
Actions for this document.


[ Note: reference to iSER is from draft normative
references in section 12.1, draft-ietf-ips-iser-04.txt ]

Last Call Comments:

Upon approval of this document, the IANA will
take the following Actions:

Action 1 (Section 11.2)

Upon approval of this document, the IANA will
in the following registry "iSCSI Parameters"
located at

http://www.iana.org/assignments/iscsi-parameters

create a new sub-registry "iSCSI Opcodes"


Namespace details: Numerical values that can fit
in one octet with most significant two bits
(bits 0 and 1) already designated  by [RFC3720],
bit 0 being reserved and bit 1 for immediate
delivery. Bit 2 is designated to identify the
originator of the opcode. Bit 2 = 0 for initiator
and Bit 2 = 1 for target


Allocation request guidance to requesters:

1) If initiator opcode and target opcode to
  identify the request and response of a
  new type of protocol operation are requested,
  assign the same lower five bits (i.e. Bit 3
  through Bit 7) for both opcodes, e.g. 0x13 and 0x33

2) If only the initiator opcode or target
  opcode is requested to identify a one-way
  protocol message (i.e. request without a
  response or a "response" without a request),
  assign an unused number from the appropriate
  category (i.e. Bit 2 set to 0 or 1 for
  initiator category or target category) and
  add the other pair member (i.e. same opcode
  with Bit 2 set to 1 or 0, respectively) to
  "Reserved to IANA" list.

3) If there are no other opcodes available to
  assign on a request for a new opcode except
  the reserved opcodes in the "Reserved to IANA"
  list, allocate the opcodes from the appropriate
  category (initiator or target).

Initial contents of this sub-registry will be:

Opcode Originator Operation Name Reference
------ ---------- -------------- ---------
0x00 Initiator NOP-Out [RFC3720]
0x01 Initiator SCSI Command [RFC3720]
0x02 Initiator SCSI Task Management [RFC3720]
function request
0x03 Initiator Login Request [RFC3720]
0x04 Initiator Text Request [RFC3720]
0x05 Initiator SCSI Data-Out [RFC3720]
0x06 Initiator Logout Request [RFC3720]
0x10 Initiator SNACK Request [RFC3720]
0x1c-0x1e Initiator Vendor specific codes [RFC3720]
0x20 Target NOP-In [RFC3720]
0x21 Target SCSI Response [RFC3720]
0x22 Target SCSI Task Management [RFC3720]
function response
0x23 Target Login Response [RFC3720]
0x24 Target Text Response [RFC3720]
0x25 Target SCSI Data-In [RFC3720]
0x26 Target Logout Response [RFC3720]
0x31 Target Ready To Transfer (R2T) [RFC3720]
0x32 Target Asynchronous Message [RFC3720]
0x3c-0x3e Target Vendor specific codes [RFC3720]
0x3f Target Reject [RFC3720]

"Reserved to IANA" opcodes: 0x11, 0x12, 0x1f, 0x30

Allocation Policy: Standards Action ([IANA]),
                  Expert Review ([IANA])

NOTE: Expert Assignment Required


Action 2 (Section 11.3):

Upon approval of this document, the IANA will
in the following registry "iSCSI Parameters"
located at

http://www.iana.org/assignments/iscsi-parameters

create a new sub-registry "iSCSI Text Keys"

Initial contents of this sub-registry will be:

Key Reference
---------- ---------
AuthMethod [RFC3720]
HeaderDigest [RFC3720]
DataDigest [RFC3720]
MaxConnections [RFC3720]
SendTargets [RFC3720]
TargetName [RFC3720]
InitiatorName [RFC3720]
TargetAlias [RFC3720]
InitiatorAlias [RFC3720]
TargetAddress [RFC3720]
TargetPortalGroupTag [RFC3720]
InitialR2T [RFC3720]
ImmediateData [RFC3720]
MaxRecvDataSegmentLength [RFC3720]
MaxBurstLength [RFC3720]
FirstBurstLength [RFC3720]
DefaultTime2Wait [RFC3720]
DefaultTime2Retain [RFC3720]
MaxOutstandingR2T [RFC3720]
DataPDUInOrder [RFC3720]
DataSequenceInOrder [RFC3720]
ErrorRecoveryLevel [RFC3720]
SessionType [RFC3720]
RDMAExtensions [iSER]
TargetRecvDataSegmentLength [iSER]
InitiatorRecvDataSegmentLength [iSER]
MaxOutstandingUnexpectedPDUs [iSER]
TaskReporting [RFC-ips-iscsi-impl-guide-08]

Allocation Policy: Standards Action ([IANA])

[ NOTE: Should this registry get alphabetized? ]


Action 3 (Section 11.4):

Upon approval of this document, the IANA will in
the following registry "iSCSI Parameters" located at

http://www.iana.org/assignments/iscsi-parameters

create a new sub-registry "iSCSI Asynchronous Events"

Initial contents of this sub-registry will be:

Event Number Description Reference
(one octet)
------------ ----------------------- ---------
0 SCSI Async Event [RFC3720]
1 Logout Request [RFC3720]
2 Connection drop notification [RFC3720]
3 Session drop notification [RFC3720]
4 Negotiation Request [RFC3720]
5 Task termination [RFC-ips-iscsi-impl-guide-08]
6-247 Reserved to IANA [RFC-ips-iscsi-impl-guide-08]
248-254 Vendor-unique [RFC-ips-iscsi-impl-guide-08]
255 Vendor-unique [RFC3720]

Allocation Policy: Standards Action ([IANA])


Action 4 (Section 11.5):

Upon approval of this document, the IANA will
in the following registry "iSCSI Parameters"
located at

http://www.iana.org/assignments/iscsi-parameters

create a new sub-registry "iSCSI TMF Codes"

Initial contents of this sub-registry will be:

TMF Code Description Reference
(7 bits)
-------- ----------- ---------
1 ABORT TASK [RFC3720]
2 ABORT TASK SET [RFC3720]
3 CLEAR ACA [RFC3720]
4 CLEAR TASK SET [RFC3720]
5 LOGICAL UNIT RESET [RFC3720]
6 TARGET WARM RESET [RFC3720]
7 TARGET COLD RESET [RFC3720]
8 TASK REASSIGN [RFC3720]
9-127 Reserved to IANA [RFC-ips-iscsi-impl-guide-08]

Allocation Policy: Standards Action ([IANA])


Action 5 (Section 11.6):

Upon approval of this document, the IANA will
in the following registry "iSCSI Parameters"
located at

http://www.iana.org/assignments/iscsi-parameters

create a new sub-registry "iSCSI Login Response
Status Codes"

Initial contents of this sub-registry will be:

Status Class Description Reference
(one octet)
----------- -------------------- ---------
0x00 Success [RFC3720]
0x01 Redirection [RFC3720]
0x02 Initiator Error [RFC3720]
0x03 Target Error [RFC3720]
0x04-0x0e Reserved to IANA [RFC-ips-iscsi-impl-guide-08]
0x0f Vendor-Unique [RFC-ips-iscsi-impl-guide-08]
0x10-0xff Reserved to IANA [RFC-ips-iscsi-impl-guide-08]

Allocation Policy: Standards Action ([IANA])


Action 6 (Section 11.6):

Upon approval of this document, the IANA will
in the following registry "iSCSI Parameters"
located at

http://www.iana.org/assignments/iscsi-parameters

in the sub-registry "iSCSI Login Response Status Codes"
create a new sub-sub-registry "Status-Detail
for Status-Class=0x00"

Initial contents of this sub-registry will be:

Status Class Status Code Description Reference
(fixed) (one octet)
----------- ----------- -------------------- ---------
0x00 0x00 Success [RFC3720]
0x00 0x01-0xff Reserved to IANA [RFC-ips-iscsi-impl-guide-08]

Allocation Policy: Standards Action ([IANA])


Action 7 (Section 11.6):

Upon approval of this document, the IANA will
in the following registry "iSCSI Parameters"
located at

http://www.iana.org/assignments/iscsi-parameters

in the sub-registry "iSCSI Login Response Status Codes"

create a new sub-sub-registry "Status-Detail
for Status-Class=0x01"

Initial contents of this sub-registry will be:

Status Class Status Code Description Reference
(fixed) (one octet)
----------- ----------- -------------------- ---------
0x01 0x01 Temporary move [RFC3720]
0x01 0x02 Permanent move [RFC3720]
0x01 0x03-0xff Reserved to IANA [RFC-ips-iscsi-impl-guide-08]

Allocation Policy: Standards Action ([IANA])


Action 8 (Section 11.6):

Upon approval of this document, the IANA will
in the following registry "iSCSI Parameters"
located at

http://www.iana.org/assignments/iscsi-parameters

in the sub-registry "iSCSI Login Response
Status Codes"

create a new sub-sub-registry "Status-Detail
for Status-Class=0x02"

Initial contents of this sub-registry will be:

Status Class Status Code Description Reference
(fixed) (one octet)
----------- ----------- -------------------- ---------
0x02 0x00 Miscellaneous [RFC3720]
0x02 0x01 Authentication failure [RFC3720]
0x02 0x02 Authorization failure [RFC3720]
0x02 0x03 Not found [RFC3720]
0x02 0x04 Target removed [RFC3720]
0x02 0x05 Unsupported version [RFC3720]
0x02 0x06 Too many connections [RFC3720]
0x02 0x07 Missing parameter [RFC3720]
0x02 0x08 Can't include in session [RFC3720]
0x02 0x09 Unsupported session type [RFC3720]
0x02 0x0a Non-existent session [RFC3720]
0x02 0x0b Invalid during login [RFC3720]
0x02 0x0c-0xff Reserved to IANA [RFC-ips-iscsi-impl-guide-08]


Allocation Policy: Standards Action ([IANA])


Action 9 (Section 11.6):

Upon approval of this document, the IANA will
in the following registry "iSCSI Parameters"
located at

http://www.iana.org/assignments/iscsi-parameters

in the sub-registry "iSCSI Login Response
Status Codes"

create a new sub-sub-registry "Status-Detail for
Status-Class=0x03"

Initial contents of this sub-registry will be:

Status Class Status Code Description Reference
(fixed) (one octet)
----------- ----------- -------------------- ---------
0x03 0x00 Target error [RFC3720]
0x03 0x01 Service unavailable [RFC3720]
0x03 0x02 Out of resources [RFC3720]
0x03 0x03-0xff Reserved to IANA [RFC-ips-iscsi-impl-guide-08]


Allocation Policy: Standards Action ([IANA])


Action 10 (Section 11.7):

Upon approval of this document, the IANA will
in the following registry "iSCSI Parameters"
located at

http://www.iana.org/assignments/iscsi-parameters

create a new sub-registry "iSCSI Reject
Reason Codes"

Initial contents of this sub-registry will be:

Reason Code Description Reference
(one octet)
----------- ------------------ ---------
0x01 Reserved [RFC3720]
0x02 Data digest error [RFC3720]
0x03 SNACK Reject [RFC3720]
0x04 Protocol Error [RFC3720]
0x05 Command not supported [RFC3720]
0x06 Immediate command reject [RFC3720]
0x07 Task in progress [RFC3720]
0x08 Invalid data ack [RFC3720]
0x09 Invalid PDU field [RFC3720]
0x0a Long op reject [RFC3720]
0x0b "Deprecated reason code" [RFC-ips-iscsi-impl-guide-08]
0x0c Waiting for Logout [RFC3720]
0x0d-oxff Reserved to IANA [RFC-ips-iscsi-impl-guide-08]

Allocation Policy: Standards Action ([IANA])


Action 11 (Section 11.8):

Upon approval of this document, the IANA will
in the following registry "iSCSI Parameters"
located at

http://www.iana.org/assignments/iscsi-parameters

create a new sub-registry "iSER Opcodes"

Initial contents of this sub-registry will be:

Opcode Operation Name Reference
(4 bits)
-------- ------------------- ---------
0x1 iSCSI control-type [iSER]
0x2 iSER Hello [iSER]
0x3 iSER HelloReply [iSER]
0x4-0xf Reserved to IANA [RFC-ips-iscsi-impl-guide-08]

Allocation Policy: Standards Action ([IANA])


We understand the above to be the only IANA
Actions for this document.


[ Note: reference to iSER is from draft normative
references in section 12.1, draft-ietf-ips-iser-04.txt ]

PROTO Write-up

(1.a) Who is the Document Shepherd for this document?

David L. Black (ips WG Chair)

Has the
Document Shepherd personally reviewed this version of the
document and, in particular, does he or she believe this
version is ready for forwarding to the IESG for publication?

Yes, mostly. The Document Shepherd has been delayed in reviewing the
document, and has a number of comments on the document. The Document
Shepherd is comfortable having his review comments treated as initial
IETF Last Call comments in order to not further delay publication of
this draft, unless the IANA registry issue requires the draft to be
revised prior to IETF Last Call - see (1.i) below.

(1.b) Has the document had adequate review both from key WG members
and from key non-WG members?

Yes.

Does the Document Shepherd have
any concerns about the depth or breadth of the reviews that
have been performed?

No. Portions of this document deal with iSCSI task management
and iSCSI error handling, where there are a limited number of
individuals with expertise sufficient to perform a thorough review.
This document has received sufficient review from such individuals,
including the document author and the principal author/editor of
RFC 3720, the main iSCSI specification.

(1.c) Does the Document Shepherd have concerns that the document
needs more review from a particular or broader perspective,
e.g., security, operational complexity, someone familiar with
AAA, internationalization or XML?

No.

(1.d) Does the Document Shepherd have any specific concerns or
issues with this document that the Responsible Area Director
and/or the IESG should be aware of? For example, perhaps he
or she is uncomfortable with certain parts of the document, or
has concerns whether there really is a need for it. In any
event, if the WG has discussed those issues and has indicated
that it still wishes to advance the document, detail those
concerns here.

No.

Has an IPR disclosure related to this document
been filed? If so, please include a reference to the
disclosure and summarize the WG discussion and conclusion on
this issue.

No.

(1.e) How solid is the WG consensus behind this document? Does it
represent the strong concurrence of a few individuals, with
others being silent, or does the WG as a whole understand and
agree with it?

The WG as a whole understands and agrees with this document.

(1.f) Has anyone threatened an appeal or otherwise indicated extreme
discontent? If so, please summarise the areas of conflict in
separate email messages to the Responsible Area Director. (It
should be in a separate email because this questionnaire is
entered into the ID Tracker.)

No.

(1.g) Has the Document Shepherd personally verified that the
document satisfies all ID nits? (See
http://www.ietf.org/ID-Checklist.html and
http://tools.ietf.org/tools/idnits/). Boilerplate checks are
not enough; this check needs to be thorough.

idnits 2.03.6 finds no problems.

Has the document
met all formal review criteria it needs to, such as the MIB
Doctor, media type and URI type reviews?

None are applicable.

(1.h) Has the document split its references into normative and
informative?

Yes.

Are there normative references to documents that
are not ready for advancement or are otherwise in an unclear
state? If such normative references exist, what is the
strategy for their completion?

No.

Are there normative references
that are downward references, as described in [RFC3967]? If
so, list these downward references to support the Area
Director in the Last Call procedure for them [RFC3967].

No, the possible downward reference found by idnits is to a published
ANSI standard (T10 SPC-3 is ANSI INCITS 408-2005), and hence is
not a concern.

(1.i) Has the Document Shepherd verified that the document IANA
consideration section exists and is consistent with the body
of the document?

Yes.

If the document specifies protocol
extensions, are reservations requested in appropriate IANA
registries? Are the IANA registries clearly identified?

No, as no such registries exist. The Responsible Area Director and/
or the IESG need to determine whether this draft warrants creation
of a set of iSCSI registries based on RFC 3720 and this document.

If the document creates a new registry, does it define the
proposed initial contents of the registry and an allocation
procedure for future registrations? Does it suggest a
reasonable name for the new registry? See [RFC2434].

Not applicable.

If the
document describes an Expert Review process has Shepherd
conferred with the Responsible Area Director so that the IESG
can appoint the needed Expert during the IESG Evaluation?

Not applicable.

(1.j) Has the Document Shepherd verified that sections of the
document that are written in a formal language, such as XML
code, BNF rules, MIB definitions, etc., validate correctly in
an automated checker?

Not applicable.

(1.k) The IESG approval announcement includes a Document
Announcement Write-Up. Please provide such a Document
Announcement Write-Up? Recent examples can be found in the
"Action" announcements for approved documents. The approval
announcement contains the following sections:

Technical Summary

iSCSI is a SCSI transport protocol that maps the SCSI
architecture and command sets onto TCP/IP. RFC 3720 defines the
iSCSI protocol. This document compiles the clarifications to
the original protocol definition in RFC 3720 to serve as a
companion document for the iSCSI implementers. This document
updates RFC 3720 and the text in this document supersedes the
text in RFC 3720 when the two differ.

Working Group Summary

This document consists of clarification items collected during
a period of more than one year based on implementation experience.
A number of the items have engendered significant working group
discussion about the appropriate clarification or change. The
ips WG strongly supports the resulting clarifications and changes
in this document.

Document Quality

There are numerous implementations of iSCSI, and the entire
content of this document is based on issues that have arisen
from implementation experience. There are a large number of
individuals listed in the acknowledgements section who have
contributed to this document based on their expertise and/or
implementation experience.

David Black (ips WG chair) and Julian Satran (RFC 3720 editor)
have reviewed this document for the ips WG.

Personnel

Document Shepherd: David Black (ips WG chair)
Responsible Area Director: Lars Eggert (Transport Area)