RFC 7341: DHCPv4-over-DHCPv6 (DHCP 4o6) Transport
In plain English — editorial summary, not part of the RFC
IPv4 connectivity is still needed as networks migrate towards IPv6. Users require IPv4 configuration even if the uplink to their service provider supports IPv6 only. This document describes a mechanism for obtaining IPv4 configuration information dynamically in IPv6 networks by carrying DHCPv4 messages over DHCPv6 transport. Two new DHCPv6 messages and two new DHCPv6 options are defined for this purpose.
Document record
- Document ID
- RFC7341
- Published
- August 2014
- Authors
- Q. Sun; Y. Cui; M. Siodelski; S. Krishnan; I. Farrer
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5619Softwire Security Analysis and RequirementsCurrent
August 2009
- RFC 7600IPv4 Residual Deployment via IPv6 - A Stateless Solution (4rd)Current
July 2015
- RFC 5569IPv6 Rapid Deployment on IPv4 Infrastructures (6rd)Current
January 2010
- RFC 7934Host Address Availability RecommendationsCurrent
July 2016
- RFC 7653DHCPv6 Active LeasequeryCurrent
October 2015
- RFC 6964Operational Guidance for IPv6 Deployment in IPv4 Sites Using the Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)Current
May 2013
- RFC 6519RADIUS Extensions for Dual-Stack LiteCurrent
February 2012
- RFC 8168DHCPv6 Prefix-Length Hint IssuesCurrent
May 2017
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?