RFC 3347: Small Computer Systems Interface protocol over the Internet (iSCSI) Requirements and Design Considerations
In plain English — editorial summary, not part of the RFC
The IP Storage Working group is chartered with developing comprehensive technology to transport block storage data over IP protocols. This effort includes a protocol to transport the Small Computer Systems Interface (SCSI) protocol over the Internet (iSCSI). The initial version of the iSCSI protocol will define a mapping of SCSI transport protocol over TCP/IP so that SCSI storage controllers (principally disk and tape arrays and libraries) can be attached to IP networks, notably Gigabit Ethernet (GbE) and 10 Gigabit Ethernet (10 GbE).
Document record
- Document ID
- RFC3347
- Published
- July 2002
- Authors
- M. Krueger; R. Haagens
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 26
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3720Internet Small Computer Systems Interface (iSCSI)Obsoleted
April 2004
- RFC 4850Declarative Public Extension Key for Internet Small Computer Systems Interface (iSCSI) Node ArchitectureObsoleted
April 2007
- RFC 7143Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)Current
April 2014
- RFC 3390Increasing TCP's Initial WindowCurrent
November 2002
- RFC 3293General Switch Management Protocol (GSMP) Packet Encapsulations for Asynchronous Transfer Mode (ATM), Ethernet and Transmission Control Protocol (TCP)Current
June 2002
- RFC 3430Simple Network Management Protocol Over Transmission Control Protocol Transport MappingCurrent
December 2002
- RFC 3465TCP Congestion Control with Appropriate Byte Counting (ABC)Current
February 2003
- RFC 3517A Conservative Selective Acknowledgment (SACK)-based Loss Recovery Algorithm for TCPObsoleted
April 2003
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?