RFC 4338: Transmission of IPv6, IPv4, and Address Resolution Protocol (ARP) Packets over Fibre Channel
In plain English — editorial summary, not part of the RFC
This document specifies the way of encapsulating IPv6, IPv4, and Address Resolution Protocol (ARP) packets over Fibre Channel. This document also specifies the method of forming IPv6 link-local addresses and statelessly autoconfigured IPv6 addresses on Fibre Channel networks, and a mechanism to perform IPv4 address resolution over Fibre Channel networks. This document obsoletes RFC 2625 and RFC 3831. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4338
- Published
- January 2006
- Authors
- C. DeSanti; C. Carlson; R. Nixon
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 33
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 2625 (1999)
- RFC 3831 (2004)
- RFC 4338 (2006)
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 4862IPv6 Stateless Address AutoconfigurationUpdated
September 2007
- RFC 4944Transmission of IPv6 Packets over IEEE 802.15.4 NetworksUpdated
September 2007
- RFC 4339IPv6 Host Configuration of DNS Server Information ApproachesCurrent
February 2006
- RFC 4323Data Over Cable System Interface Specification Quality of Service Management Information Base (DOCSIS-QoS MIB)Updated
January 2006
- RFC 4319Definitions of Managed Objects for High Bit-Rate DSL - 2nd generation (HDSL2) and Single-Pair High-Speed Digital Subscriber Line (SHDSL) LinesCurrent
December 2005
- RFC 4318Definitions of Managed Objects for Bridges with Rapid Spanning Tree ProtocolCurrent
December 2005
- RFC 4363Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering, and Virtual LAN ExtensionsCurrent
January 2006
- RFC 4384BGP Communities for Data CollectionCurrent
February 2006
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?