RFC 5047: DA: Datamover Architecture for the Internet Small Computer System Interface (iSCSI)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC5047
- Published
- October 2007
- Authors
- M. Chadalapaka; J. Hufferd; J. Satran; H. Shah
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 49
- Also known as
- —
- Updated by:
- RFC 7146
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4545Definitions of Managed Objects for IP Storage User Identity AuthorizationCurrent
May 2006
- RFC 4544Definitions of Managed Objects for Internet Small Computer System Interface (iSCSI)Obsoleted
May 2006
- RFC 3980T11 Network Address Authority (NAA) Naming Format for iSCSI Node NamesObsoleted
February 2005
- RFC 3366Advice to link designers on link Automatic Repeat reQuest (ARQ)Current
September 2002
- RFC 5065Autonomous System Confederations for BGPUpdated
August 2007
- RFC 5966DNS Transport over TCP - Implementation RequirementsObsoleted
August 2010
- RFC 3498Definitions of Managed Objects for Synchronous Optical Network (SONET) Linear Automatic Protection Switching (APS) ArchitecturesCurrent
March 2003
- RFC 7766DNS Transport over TCP - Implementation RequirementsUpdated
March 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?