RFC 3831: Transmission of IPv6 Packets over Fibre Channel
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4338.
Current document in this lineage: 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 packets over Fibre Channel, and the method of forming IPv6 link-local addresses and statelessly autoconfigured addresses on Fibre Channel networks. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3831
- Published
- July 2004
- Authors
- C. DeSanti
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 24
- Also known as
- —
- Obsoleted by:
- RFC 4338
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
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 2529Transmission of IPv6 over IPv4 Domains without Explicit TunnelsCurrent
March 1999
- RFC 2470Transmission of IPv6 Packets over Token Ring NetworksUpdated
December 1998
- RFC 2467Transmission of IPv6 Packets over FDDI NetworksUpdated
December 1998
- RFC 2464Transmission of IPv6 Packets over Ethernet NetworksUpdated
December 1998
- RFC 3315Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Obsoleted
July 2003
- RFC 3146Transmission of IPv6 Packets over IEEE 1394 NetworksUpdated
October 2001
- RFC 2663IP Network Address Translator (NAT) Terminology and ConsiderationsCurrent
August 1999
- RFC 2590Transmission of IPv6 Packets over Frame Relay Networks SpecificationUpdated
May 1999
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?