RFC 4172: iFCP - A Protocol for Internet Fibre Channel Storage Networking
In plain English — editorial summary, not part of the RFC
This document specifies an architecture and a gateway-to-gateway protocol for the implementation of fibre channel fabric functionality over an IP network. This functionality is provided through TCP protocols for fibre channel frame transport and the distributed fabric services specified by the fibre channel standards. The architecture enables internetworking of fibre channel devices through gateway-accessed regions with the fault isolation properties of autonomous systems and the scalability of the IP network. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4172
- Published
- September 2005
- Authors
- C. Monia; R. Mullendore; F. Travostino; W. Jeong; M. Edwards
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 111
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4173Bootstrapping Clients using the Internet Small Computer System Interface (iSCSI) ProtocolUpdated
September 2005
- RFC 4992XML Pipelining with Chunks for the Internet Registry Information ServiceUpdated
August 2007
- 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
- RFC 3155End-to-end Performance Implications of Links with ErrorsCurrent
August 2001
- RFC 3135Performance Enhancing Proxies Intended to Mitigate Link-Related DegradationsCurrent
June 2001
- RFC 6356Coupled Congestion Control for Multipath Transport ProtocolsCurrent
October 2011
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?