RFC 6172: Deprecation of the Internet Fibre Channel Protocol (iFCP) Address Translation Mode
In plain English — editorial summary, not part of the RFC
Changes to Fibre Channel have caused the specification of the Internet Fibre Channel Protocol (iFCP) address translation mode to become incorrect. Due to the absence of usage of iFCP address translation mode, it is deprecated by this document. iFCP address transparent mode remains correctly specified. iFCP address transparent mode has been implemented and is in current use; therefore, it is not affected by this document. This document also records the state of Protocol Number 133, which was allocated for a pre-standard version of the Fibre Channel Internet Protocol (FCIP). [STANDARDS-TRACK]
Document record
- Document ID
- RFC6172
- Published
- March 2011
- Authors
- D. Black; D. Peterson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 6
- Also known as
- —
- Updates:
- RFC 4172
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3822Finding Fibre Channel over TCP/IP (FCIP) Entities Using Service Location Protocol version 2 (SLPv2)Updated
July 2004
- RFC 3821Fibre Channel Over TCP/IP (FCIP)Updated
July 2004
- RFC 6173Definitions of Managed Objects for the Internet Fibre Channel Protocol (iFCP)Current
March 2011
- RFC 6181Threat Analysis for TCP Extensions for Multipath Operation with Multiple AddressesCurrent
March 2011
- RFC 6182Architectural Guidelines for Multipath TCP DevelopmentCurrent
March 2011
- RFC 6156Traversal Using Relays around NAT (TURN) Extension for IPv6Obsoleted
April 2011
- RFC 6147DNS64: DNS Extensions for Network Address Translation from IPv6 Clients to IPv4 ServersCurrent
April 2011
- RFC 6146Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 ServersCurrent
April 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?