RFC 2529: Transmission of IPv6 over IPv4 Domains without Explicit Tunnels
In plain English — editorial summary, not part of the RFC
This memo specifies the frame format for transmission of IPv6 (IPV6) packets and the method of forming IPv6 link-local addresses over IPv4 domains. It also specifies the content of the Source/Target Link-layer Address option used in the Router Solicitation, Router Advertisement, Neighbor Solicitation, and Neighbor Advertisement and Redirect messages, when those messages are transmitted on an IPv4 multicast network. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2529
- Published
- March 1999
- Authors
- B. Carpenter; C. Jung
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- 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 2497Transmission of IPv6 Packets over ARCnet NetworksUpdated
January 1999
- RFC 2590Transmission of IPv6 Packets over Frame Relay Networks SpecificationUpdated
May 1999
- RFC 2675IPv6 JumbogramsCurrent
August 1999
- RFC 3146Transmission of IPv6 Packets over IEEE 1394 NetworksUpdated
October 2001
- RFC 8504IPv6 Node RequirementsCurrent
January 2019
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?