Skip to main content

DHCPv6 Options for Discovery NAT64 Prefixes

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
Authors Lishan Li , Yong Cui , Cong Liu , Jianping Wu , Fred Baker , Jordi Palet Martinez
Last updated 2017-09-27 (Latest revision 2017-03-26)
RFC stream (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


Several IPv6 transition mechanisms require the usage of stateless or stateful translators (commonly named as NAT64) able to allow IP/ICMP communication between IPv4 and IPv6 networks. Those translators are using either a default Well-Known Prefix (WKP), and/or one or several additional Network Specific Prefix (NSP), which need to be configured into the nodes willing to use the translator. Different translators will likely have different IPv6 prefixes, to attract traffic to the correct translator. Thus, an automatic translator prefix discovery method is necessary. This document defines a DHCPv6-based method to inform DHCPv6 clients the set of IPv6 and IPv4 prefixes it serves. This DHCPv6 option can be used by several transition mechanisms such as SIIT, 464XLAT, EAM.


Lishan Li
Yong Cui
Cong Liu
Jianping Wu
Fred Baker
Jordi Palet Martinez

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)