RFC 4174: The IPv4 Dynamic Host Configuration Protocol (DHCP) Option for the Internet Storage Name Service
In plain English — editorial summary, not part of the RFC
This document describes the Dynamic Host Configuration Protocol (DHCP) option to allow Internet Storage Name Service (iSNS) clients to discover the location of the iSNS server automatically through the use of DHCP for IPv4. iSNS provides discovery and management capabilities for Internet SCSI (iSCSI) and Internet Fibre Channel Protocol (iFCP) storage devices in an enterprise-scale IP storage network. iSNS provides intelligent storage management services comparable to those found in Fibre Channel networks, allowing a commodity IP network to function in a similar capacity to that of a storage area network. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4174
- Published
- September 2005
- Authors
- C. Monia; J. Tseng; K. Gibbons
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 13
- 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 4939Definitions of Managed Objects for iSNS (Internet Storage Name Service)Current
July 2007
- RFC 4171Internet Storage Name Service (iSNS)Current
September 2005
- RFC 3783Small Computer Systems Interface (SCSI) Command Ordering Considerations with iSCSICurrent
May 2004
- RFC 3722String Profile for Internet Small Computer Systems Interface (iSCSI) NamesCurrent
April 2004
- RFC 3720Internet Small Computer Systems Interface (iSCSI)Obsoleted
April 2004
- RFC 3347Small Computer Systems Interface protocol over the Internet (iSCSI) Requirements and Design ConsiderationsCurrent
July 2002
- RFC 7143Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)Current
April 2014
- RFC 4191Default Router Preferences and More-Specific RoutesCurrent
November 2005
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?