Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updates:

RFC 7598

Authors:

I. Farrer
Q. Sun
Y. Cui
L. Sun

Stream:

IETF

Source:

dhc (int)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC8539

Discuss this RFC: Send questions or comments to the mailing listdhcwg@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 8539

Abstract

DHCPv4 over DHCPv6 (RFC 7341) is a mechanism for dynamicallyconfiguring IPv4 for use as an over-the-top service in an IPv6-onlynetwork. Softwires are an example of such a service. For DHCPv4over DHCPv6 (DHCP 4o6) to function with some IPv4-over-IPv6 softwiremechanisms and deployment scenarios (e.g., RFC 7596 or RFC 7597), theoperator needs to know the IPv6 address that the client will use asthe source of an IPv4-in-IPv6 softwire tunnel. This address, inconjunction with the client's IPv4 address, and (in some deployments)the Port Set ID are used to create a binding table entry in theoperator's softwire tunnel concentrator. This memo defines a DHCPv6option to convey IPv6 parameters for establishing the softwire tunneland a DHCPv4 option (to be used only with DHCP 4o6) to communicatethe source tunnel IPv6 address between the DHCP 4o6 client andserver. It is designed to work in conjunction with the IPv4 addressallocation process.

"DHCPv6 Options for Configuration of Softwire Address and Port-Mapped Clients" (RFC 7598) describes a deterministic DHCPv6-based mechanismfor provisioning softwires. This document updates RFC 7598, allowingOPTION_S46_BR (90) to be enumerated in the DHCPv6 client's OptionRequest Option (ORO) request and to appear directly within subsequentmessages sent by the DHCPv6 server.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.