[rfc-dist] RFC 5047 on DA: Datamover Architecture for the Internet Small Computer System Interface (iSCSI)
rfc-editor at rfc-editor.org
Wed Oct 31 15:54:33 PDT 2007
A new Request for Comments is now available in online RFC libraries.
Title: DA: Datamover Architecture for the
Internet Small Computer System Interface (iSCSI)
Author: M. Chadalapaka, J. Hufferd,
J. Satran, H. Shah
Date: October 2007
Mailbox: cbm at rose.hp.com,
jhufferd at brocade.com,
Julian_Satran at il.ibm.com, hemal at broadcom.com
I-D Tag: draft-ietf-ips-iwarp-da-05.txt
The Internet Small Computer System Interface (iSCSI) is a SCSI
transport protocol that maps the SCSI family
of application protocols onto TCP/IP. Datamover Architecture
for iSCSI (DA) defines an abstract model in which the
movement of data between iSCSI end nodes is logically
separated from the rest of the iSCSI protocol in order to
allow iSCSI to adapt to innovations available in new IP
transports. While DA defines the architectural functions
required of the class of Datamover protocols, it does not
define any specific Datamover protocols. Each such Datamover
protocol, defined in a separate document, provides a
reliable transport for all iSCSI PDUs, but actually moves the
data required for certain iSCSI PDUs without involving the
remote iSCSI layer itself. This document begins with an
introduction of a few new abstractions, defines a layered
architecture for iSCSI and Datamover protocols, and then
models the interactions within an iSCSI end node between the
iSCSI layer and the Datamover layer that happen in order to
transparently perform remote data movement within an IP
fabric. It is intended that this definition will help map
iSCSI to generic Remote Direct Memory Access (RDMA)-capable IP fabrics
in the future comprising TCP, the Stream Control Transmission Protocol
(SCTP), and possibly other underlying network transport layers, such as
InfiniBand. This memo provides information for the Internet community.
This document is a product of the IP Storage
Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution
of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at RFC-EDITOR.ORG
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
The RFC Editor Team
USC/Information Sciences Institute
More information about the rfc-dist