RFC 4173: Bootstrapping Clients using the Internet Small Computer System Interface (iSCSI) Protocol
In plain English — editorial summary, not part of the RFC
Internet Small Computer System Interface (iSCSI) is a proposed transport protocol for Small Computer Systems Interface (SCSI) that operates on top of TCP. This memo describes a standard mechanism for enabling clients to bootstrap themselves using the iSCSI protocol. The goal of this standard is to enable iSCSI boot clients to obtain the information to open an iSCSI session with the iSCSI boot server. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4173
- Published
- September 2005
- Authors
- P. Sarkar; D. Missimer; C. Sapuntzakis
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 12
- 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 4172iFCP - A Protocol for Internet Fibre Channel Storage NetworkingUpdated
September 2005
- RFC 4992XML Pipelining with Chunks for the Internet Registry Information ServiceUpdated
August 2007
- RFC 4018Finding Internet Small Computer Systems Interface (iSCSI) Targets and Name Servers by Using Service Location Protocol version 2 (SLPv2)Updated
May 2005
- RFC 4544Definitions of Managed Objects for Internet Small Computer System Interface (iSCSI)Obsoleted
May 2006
- RFC 3721Internet Small Computer Systems Interface (iSCSI) Naming and DiscoveryUpdated
April 2004
- 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 3347Small Computer Systems Interface protocol over the Internet (iSCSI) Requirements and Design ConsiderationsCurrent
July 2002
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?