draft-ietf-ips-iwarp-da-00.txt   draft-ietf-ips-iwarp-da-01.txt 
INTERNET DRAFT Mallikarjun Chadalapaka INTERNET DRAFT Mallikarjun Chadalapaka
draft-ietf-ips-iwarp-da-00.txt HP draft-ietf-ips-iwarp-da-01.txt HP
John Hufferd John Hufferd
IBM IBM
Julian Satran Julian Satran
IBM IBM
Hemal Shah Hemal Shah
Intel Intel
Expires March 2005 Expires September 2005
Datamover Architecture for iSCSI (DA) Datamover Architecture for iSCSI (DA)
1 Status of this Memo 1 Status of this Memo
By submitting this Internet-Draft, we certify that any By submitting this Internet-Draft, we certify that any
applicable patent or other IPR claims of which we are aware applicable patent or other IPR claims of which we are aware
have been disclosed, or will be disclosed, and any of which have been disclosed, or will be disclosed, and any of which
we become aware will be disclosed, in accordance with RFC we become aware will be disclosed, in accordance with RFC
3668. 3668.
skipping to change at page 3, line 49 skipping to change at page 3, line 49
11 Datamover Interface (DI) ..............................29 11 Datamover Interface (DI) ..............................29
11.1 Overview.............................................29 11.1 Overview.............................................29
11.2 Interactions for handling asynchronous notifications.29 11.2 Interactions for handling asynchronous notifications.29
11.2.1 Connection termination .............................29 11.2.1 Connection termination .............................29
11.2.2 Data transfer completion ...........................29 11.2.2 Data transfer completion ...........................29
11.2.3 Data acknowledgement ...............................30 11.2.3 Data acknowledgement ...............................30
11.3 Interactions for sending an iSCSI PDU................31 11.3 Interactions for sending an iSCSI PDU................31
11.3.1 SCSI Command .......................................31 11.3.1 SCSI Command .......................................31
11.3.2 SCSI Response ......................................32 11.3.2 SCSI Response ......................................32
11.3.3 Task Management Function Request ...................32 11.3.3 Task Management Function Request ...................32
11.3.4 Task Management Function Response ..................32 11.3.4 Task Management Function Response ..................33
11.3.5 SCSI Data-out & SCSI Data-in .......................33 11.3.5 SCSI Data-out & SCSI Data-in .......................33
11.3.6 Ready To Transfer (R2T) ............................33 11.3.6 Ready To Transfer (R2T) ............................33
11.3.7 Asynchronous Message ...............................34 11.3.7 Asynchronous Message ...............................34
11.3.8 Text Request .......................................34 11.3.8 Text Request .......................................34
11.3.9 Text Response ......................................34 11.3.9 Text Response ......................................34
11.3.10 Login Request ....................................34 11.3.10 Login Request ....................................35
11.3.11 Login Response ...................................35 11.3.11 Login Response ...................................35
11.3.12 Logout Command ...................................36 11.3.12 Logout Command ...................................36
11.3.13 Logout Response ..................................36 11.3.13 Logout Response ..................................36
11.3.14 SNACK Request ....................................36 11.3.14 SNACK Request ....................................36
11.3.15 Reject ...........................................36 11.3.15 Reject ...........................................37
11.3.16 NOP-Out ..........................................37 11.3.16 NOP-Out ..........................................37
11.3.17 NOP-In ...........................................37 11.3.17 NOP-In ...........................................37
11.4 Interactions for receiving an iSCSI PDU..............37 11.4 Interactions for receiving an iSCSI PDU..............37
11.4.1 SCSI Command .......................................37 11.4.1 SCSI Command .......................................38
11.4.2 SCSI Response ......................................38 11.4.2 SCSI Response ......................................38
11.4.3 Task Management Function Request ...................38 11.4.3 Task Management Function Request ...................38
11.4.4 Task Management Function Response ..................38 11.4.4 Task Management Function Response ..................38
11.4.5 SCSI Data-out & SCSI Data-in .......................38 11.4.5 SCSI Data-out & SCSI Data-in .......................38
11.4.6 Ready To Transfer (R2T) ............................39 11.4.6 Ready To Transfer (R2T) ............................39
11.4.7 Asynchronous Message ...............................39 11.4.7 Asynchronous Message ...............................40
11.4.8 Text Request .......................................39 11.4.8 Text Request .......................................40
11.4.9 Text Response ......................................40 11.4.9 Text Response ......................................40
11.4.10 Login Request ....................................40 11.4.10 Login Request ....................................40
11.4.11 Login Response ...................................40 11.4.11 Login Response ...................................40
11.4.12 Logout Command ...................................40 11.4.12 Logout Command ...................................41
11.4.13 Logout Response ..................................41 11.4.13 Logout Response ..................................41
11.4.14 SNACK Request ....................................41 11.4.14 SNACK Request ....................................41
11.4.15 Reject ...........................................41 11.4.15 Reject ...........................................41
11.4.16 NOP-Out ..........................................41 11.4.16 NOP-Out ..........................................41
11.4.17 NOP-In ...........................................41 11.4.17 NOP-In ...........................................41
12 Security Considerations ...............................42 12 Security Considerations ...............................42
13 IANA Considerations ...................................43 13 IANA Considerations ...................................43
14 References and Bibliography ...........................44 14 References and Bibliography ...........................44
14.1 Normative References.................................44 14.1 Normative References.................................44
14.2 Informative References...............................44 14.2 Informative References...............................44
skipping to change at page 19, line 5 skipping to change at page 18, line 9
level of assurance of data integrity as the CRC32C iSCSI level of assurance of data integrity as the CRC32C iSCSI
data digest), reliable, in-order delivery transport data digest), reliable, in-order delivery transport
mechanism over IP fabrics in performing the data transfer, mechanism over IP fabrics in performing the data transfer,
and asynchronously notify the iSCSI layer upon iSCSI and asynchronously notify the iSCSI layer upon iSCSI
connection termination. connection termination.
Note that this architecture expects that each compliant Note that this architecture expects that each compliant
Datamover protocol will define the precise means of Datamover protocol will define the precise means of
satisfying the requirements specified in this section. satisfying the requirements specified in this section.
In order to meet the functional requirements listed in this
section, certain Datamover protocols may require pre-posted
buffers from the local iSCSI protocol layer via mechanisms
outside the scope of this document and in some
implementations, the absence of such buffers may result in a
connection failure. Datamover protocols may also realize
these functional requirements via methods not explicitly
listed in this document.
9 Operational Primitives provided by the Datamover layer 9 Operational Primitives provided by the Datamover layer
While the iSCSI specification itself does not have a notion While the iSCSI specification itself does not have a notion
of Operational Primitives, any iSCSI layer implementing the of Operational Primitives, any iSCSI layer implementing the
iSCSI specification functionally requires the following iSCSI specification functionally requires the following
Operational Primitives from its Datamover layer. These Operational Primitives from its Datamover layer. These
Operational Primitives are invoked by the iSCSI layer as Operational Primitives are invoked by the iSCSI layer as
appropriate. Unless otherwise stated, all the following appropriate. Unless otherwise stated, all the following
Operational Primitives may be used both on the initiator side Operational Primitives may be used both on the initiator side
and the target side. In general programming terminology, and the target side. In general programming terminology,
skipping to change at page 31, line 15 skipping to change at page 31, line 15
11.3 Interactions for sending an iSCSI PDU 11.3 Interactions for sending an iSCSI PDU
This section discusses the interactions model for sending This section discusses the interactions model for sending
each of the iSCSI PDUs defined in [RFC3720]. A each of the iSCSI PDUs defined in [RFC3720]. A
Connection_Handle (see section 7.3) is assumed to qualify Connection_Handle (see section 7.3) is assumed to qualify
each of these interactions so that the Datamover layer can each of these interactions so that the Datamover layer can
route it to the appropriate Transport Connection. The route it to the appropriate Transport Connection. The
qualifying Connection_Handle is not explicitly listed in the qualifying Connection_Handle is not explicitly listed in the
subsequent sections. subsequent sections.
Note that the defined list of input qualifiers represents the
semantically required set for the Datamover layer to consider
in implementing the Primitive in each interaction described
in this section. Some implementations may choose to deduce
the qualifiers in other ways that are optimized for the
implementation specifics. Two examples of this are:
1. For SCSI Command (section 11.3.1), deducing the
ImmediateDataSize input qualifier from the
DataSegmentLength field of the SCSI Command PDU.
2. For SCSI Data-Out (section 11.3.5.1), deducing the
DataDescriptorOut input qualifier from the associated
SCSI Command invocation qualifiers (assuming such state
is maintained) in conjunction with BHS fields of the
SCSI Data-out PDU.
11.3.1 SCSI Command 11.3.1 SCSI Command
The Send_Control Operational Primitive with the following The Send_Control Operational Primitive with the following
input qualifiers is used for requesting the transmission of a input qualifiers is used for requesting the transmission of a
SCSI Command PDU. SCSI Command PDU.
a) BHS and AHS, if any, of the SCSI Command PDU as defined in a) BHS and AHS, if any, of the SCSI Command PDU as defined in
[RFC3720] [RFC3720]
b) DataDescriptorOut: that defines the I/O Buffer meant for b) DataDescriptorOut: that defines the I/O Buffer meant for
skipping to change at page 31, line 31 skipping to change at page 32, line 4
a) BHS and AHS, if any, of the SCSI Command PDU as defined in a) BHS and AHS, if any, of the SCSI Command PDU as defined in
[RFC3720] [RFC3720]
b) DataDescriptorOut: that defines the I/O Buffer meant for b) DataDescriptorOut: that defines the I/O Buffer meant for
Data-out for the entire command, in the case of a write or Data-out for the entire command, in the case of a write or
bidirectional command bidirectional command
c) DataDescriptorIn: that defines the I/O Buffer meant for c) DataDescriptorIn: that defines the I/O Buffer meant for
Data-in for the entire command, in the case of a read or Data-in for the entire command, in the case of a read or
bidirectional command bidirectional command
d) ImmediateDataSize: that defines the number of octets of d) ImmediateDataSize: that defines the number of octets of
immediate unsolicited data for a write/bidirectional immediate unsolicited data for a write/bidirectional
command command
e) UnsolicitedDataSize: that defines the number of octets of e) UnsolicitedDataSize: that defines the number of octets of
immediate and non-immediate unsolicited data for a immediate and non-immediate unsolicited data for a
write/bidirectional command. write/bidirectional command.
Note that some implementations may choose to ascertain the
ImmediateDataSize input qualifier from the DataSegmentLength
field of the SCSI Command PDU. The defined list of input
qualifiers represents the semantically required set for the
Datamover layer to consider in implementing the Primitive.
11.3.2 SCSI Response 11.3.2 SCSI Response
The Send_Control Operational Primitive with the following The Send_Control Operational Primitive with the following
input qualifiers is used for requesting the transmission of a input qualifiers is used for requesting the transmission of a
SCSI Response PDU. SCSI Response PDU.
a) BHS of the SCSI Response PDU as defined in [RFC3720] a) BHS of the SCSI Response PDU as defined in [RFC3720]
b) DataDescriptorStatus: that defines the iSCSI buffer which b) DataDescriptorStatus: that defines the iSCSI buffer which
contains the sense and response information for the command contains the sense and response information for the command
skipping to change at page 44, line 17 skipping to change at page 44, line 17
14.1 Normative References 14.1 Normative References
[RFC3720] J. Satran, K. Meth, C. Sapuntzakis, M. Chadalapaka, [RFC3720] J. Satran, K. Meth, C. Sapuntzakis, M. Chadalapaka,
E. Zeidner, "Internet Small Computer Systems Interface E. Zeidner, "Internet Small Computer Systems Interface
(iSCSI)", RFC 3720, April 2004. (iSCSI)", RFC 3720, April 2004.
14.2 Informative References 14.2 Informative References
[DDP] H. Shah et al., "Direct Data Placement over Reliable [DDP] H. Shah et al., "Direct Data Placement over Reliable
Transports", IETF Internet Draft draft-ietf-rddp-ddp- Transports", IETF Internet Draft draft-ietf-rddp-ddp-
00.txt (work in progress), February 2003. 04.txt (work in progress), February 2005.
[iSER] M. Ko et al., "iSCSI Extensions for RDMA", IETF [iSER] M. Ko et al., "iSCSI Extensions for RDMA", IETF
Internet Draft draft-ko-iwarp-iser-02.txt (work in Internet Draft draft-ietf-ips-iser-00.txt (work in
progress), July 2004. progress), September 2004.
[MPA] P. Culley et al., "Marker PDU Aligned Framing for TCP [MPA] P. Culley et al., "Marker PDU Aligned Framing for TCP
Specification", IETF Internet Draft draft-culley-iwarp- Specification", IETF Internet Draft draft-ietf-rddp-mpa-
mpa-02.txt (work in progress), February 2003. 02.txt (work in progress), February 2004.
[RDMAP] R. Recio et al., "An RDMA Protocol Specification", [RDMAP] R. Recio et al., "An RDMA Protocol Specification",
IETF Internet Draft draft-ietf-rddp-rdmap-00.txt (work in IETF Internet Draft draft-ietf-rddp-rdmap-03.txt (work in
progress), February 2003. progress), February 2005.
[RFC2119] Bradner, S. "Key Words for use in RFCs to Indicate [RFC2119] Bradner, S. "Key Words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[SAM] ANSI X3.270-1998, SCSI-3 Architecture Model (SAM). [SAM] ANSI X3.270-1998, SCSI-3 Architecture Model (SAM).
[SCTP] R. Stewart et al., "Stream Control Transmission [SCTP] R. Stewart et al., "Stream Control Transmission
Protocol", RFC 2960, October 2000. Protocol", RFC 2960, October 2000.
[SPC3]T10/1416-D, SCSI Primary Commands-3. [SPC3]T10/1416-D, SCSI Primary Commands-3.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/