RFC 3783: Small Computer Systems Interface (SCSI) Command Ordering Considerations with iSCSI
In plain English — editorial summary, not part of the RFC
Internet Small Computer Systems Interface (iSCSI) is a Small Computer Systems Interface (SCSI) transport protocol designed to run on top of TCP. The iSCSI session abstraction is equivalent to the classic SCSI "I_T nexus", which represents the logical relationship between an Initiator and a Target (I and T) required in order to communicate via the SCSI family of protocols. The iSCSI session provides an ordered command delivery from the SCSI initiator to the SCSI target. This document goes into the design considerations that led to the iSCSI session model as it is defined today, relates the SCSI command ordering features defined in T10 specifications to the iSCSI concepts, and finally provides guidance to system designers on how true command ordering solutions can be built based on iSCSI. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3783
- Published
- May 2004
- Authors
- M. Chadalapaka; R. Elliott
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3722String Profile for Internet Small Computer Systems Interface (iSCSI) NamesCurrent
April 2004
- RFC 3720Internet Small Computer Systems Interface (iSCSI)Obsoleted
April 2004
- RFC 3980T11 Network Address Authority (NAA) Naming Format for iSCSI Node NamesObsoleted
February 2005
- RFC 3347Small Computer Systems Interface protocol over the Internet (iSCSI) Requirements and Design ConsiderationsCurrent
July 2002
- RFC 4939Definitions of Managed Objects for iSNS (Internet Storage Name Service)Current
July 2007
- RFC 7143Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)Current
April 2014
- RFC 4174The IPv4 Dynamic Host Configuration Protocol (DHCP) Option for the Internet Storage Name ServiceUpdated
September 2005
- RFC 3759RObust Header Compression (ROHC): Terminology and Channel Mapping ExamplesCurrent
April 2004
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?