Skip to main content

Provisioning IPv4 Configuration Over IPv6 Only Networks

Document Type Replaced Internet-Draft (dhc WG)
Expired & archived
Authors Branimir Rajtar, Ian Farrer
Last updated 2013-05-16 (Latest revision 2013-04-16)
Replaced by draft-ietf-dhc-v4configuration
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Additional resources Mailing list discussion
Stream WG state Adopted by a WG
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-dhc-v4configuration
Consensus boilerplate Unknown
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:


As IPv6 becomes more widely adopted, some service providers are taking the approach of deploying IPv6 only networks, without dual- stack functionality for IPv4. However, access to IPv4 based services is still an ongoing requirement and approaches such as IPv4-in-IPv6 softwire tunnels are being developed to meet this need. In order to provision end-user's hosts with the necessary IPv4 configuration, a number of different mechanisms have been proposed. This memo discusses the benefits and drawbacks of each, with the aim of recommending a single approach as the basis for future work.


Branimir Rajtar
Ian Farrer

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