RFC 4171: Internet Storage Name Service (iSNS)
In plain English — editorial summary, not part of the RFC
This document specifies the Internet Storage Name Service (iSNS) protocol, used for interaction between iSNS servers and iSNS clients, which facilitates automated discovery, management, and configuration of iSCSI and Fibre Channel devices (using iFCP gateways) on a TCP/IP network. iSNS provides intelligent storage discovery and management services comparable to those found in Fibre Channel networks, allowing a commodity IP network to function in a capacity similar to that of a storage area network. iSNS facilitates a seamless integration of IP and Fibre Channel networks due to its ability to emulate Fibre Channel fabric services and to manage both iSCSI and Fibre Channel devices. iSNS thereby provides value in any storage network comprised of iSCSI devices, Fibre Channel devices (using iFCP gateways), or any combination thereof. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4171
- Published
- September 2005
- Authors
- J. Tseng; K. Gibbons; F. Travostino; C. Du Laney; J. Souza
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 123
- Also known as
- —
Topics
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 4174The IPv4 Dynamic Host Configuration Protocol (DHCP) Option for the Internet Storage Name ServiceUpdated
September 2005
- RFC 4172iFCP - A Protocol for Internet Fibre Channel Storage NetworkingUpdated
September 2005
- RFC 4173Bootstrapping Clients using the Internet Small Computer System Interface (iSCSI) ProtocolUpdated
September 2005
- RFC 4164RObust Header Compression (ROHC): Context Replication for ROHC ProfilesCurrent
September 2005
- RFC 4163RObust Header Compression (ROHC): Requirements on TCP/IP Header CompressionCurrent
August 2005
- RFC 4224RObust Header Compression (ROHC): ROHC over Channels That Can Reorder PacketsCurrent
January 2006
- RFC 4230RSVP Security PropertiesCurrent
December 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?