%% You should probably cite rfc8539 instead of this I-D. @techreport{ietf-dhc-dhcp4o6-saddr-opt-02, number = {draft-ietf-dhc-dhcp4o6-saddr-opt-02}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcp4o6-saddr-opt/02/}, author = {Ian Farrer and Qi Sun and Yong Cui and Linhui Sun}, title = {{DHCPv4 over DHCPv6 Source Address Option}}, pagetotal = 14, year = 2018, month = mar, day = 18, abstract = {DHCPv4 over DHCPv6 is a mechanism for dynamically configuring IPv4 over an IPv6-only network. For DHCPv4 over DHCPv6 to function with some IPv4-over-IPv6 softwire mechanisms and deployment scenarios, the operator needs to know the IPv6 address that the client will use as the source of 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. This document updates "DHCPv6 Options for Configuration of Softwire Address and Port-Mapped Clients" to allow the DHCPv6 option OPTION\_S46\_BR (90) to appear outside of DHCPv6 softwire container options. This document updates RFC7598, allowing OPTION\_S46\_BR (90) to be enumerated in the DHCPv6 client's ORO request and appear directly within subsequent messages sent by the DHCPv6 server.}, }