RFC 3721: Internet Small Computer Systems Interface (iSCSI) Naming and Discovery
In plain English — editorial summary, not part of the RFC
This document provides examples of the Internet Small Computer Systems Interface (iSCSI; or SCSI over TCP) name construction and discussion of discovery of iSCSI resources (targets) by iSCSI initiators. This document complements the iSCSI protocol document. Flexibility is the key guiding principle behind this document. That is, an effort has been made to satisfy the needs of both small isolated environments, as well as large environments requiring secure/scalable solutions. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3721
- Published
- April 2004
- Authors
- M. Bakke; J. Hafner; J. Hufferd; K. Voruganti; M. Krueger
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 22
- Also known as
- —
- Updated by:
- RFC 7143
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 4018Finding Internet Small Computer Systems Interface (iSCSI) Targets and Name Servers by Using Service Location Protocol version 2 (SLPv2)Updated
May 2005
- RFC 4173Bootstrapping Clients using the Internet Small Computer System Interface (iSCSI) ProtocolUpdated
September 2005
- RFC 4544Definitions of Managed Objects for Internet Small Computer System Interface (iSCSI)Obsoleted
May 2006
- RFC 5048Internet Small Computer System Interface (iSCSI) Corrections and ClarificationsObsoleted
October 2007
- RFC 3720Internet Small Computer Systems Interface (iSCSI)Obsoleted
April 2004
- RFC 3722String Profile for Internet Small Computer Systems Interface (iSCSI) NamesCurrent
April 2004
- RFC 3723Securing Block Storage Protocols over IPUpdated
April 2004
- RFC 3726Requirements for Signaling ProtocolsCurrent
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?