RFC 6434: IPv6 Node Requirements
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8504.
Current document in this lineage: RFC 8504 — IPv6 Node Requirements
In plain English — editorial summary, not part of the RFC
This document defines requirements for IPv6 nodes. It is expected that IPv6 will be deployed in a wide range of devices and situations. Specifying the requirements for IPv6 nodes allows IPv6 to function well and interoperate in a large number of situations and deployments. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6434
- Published
- December 2011
- Authors
- E. Jankiewicz; J. Loughney; T. Narten
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 30
- 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 4294 (2006)
- RFC 6434 (2011)
- RFC 8504 (2019) ✓
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 4113Management Information Base for the User Datagram Protocol (UDP)Current
June 2005
- RFC 3678Socket Interface Extensions for Multicast Source FiltersCurrent
January 2004
- RFC 2728The Transmission of IP Over the Vertical Blanking Interval of a Television SignalCurrent
November 1999
- RFC 2685Virtual Private Networks IdentifierCurrent
September 1999
- RFC 2625IP and ARP over Fibre ChannelObsoleted
June 1999
- RFC 2529Transmission of IPv6 over IPv4 Domains without Explicit TunnelsCurrent
March 1999
- RFC 2507IP Header CompressionCurrent
February 1999
- RFC 2337Intra-LIS IP multicast among routers over ATM using Sparse Mode PIMCurrent
April 1998
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?