RFC 8539

Softwire Provisioning Using DHCPv4 over DHCPv6, March 2019

Canonical URL:
https://www.rfc-editor.org/rfc/rfc8539.txt
File formats:
Plain TextPDF HTML
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

DOI:  10.17487/RFC8539

Discuss this RFC: Send questions or comments to dhcwg@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF


Abstract

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

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


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Download PDF Reader