IPv4/IPv6 Transition Practice in OpenStack

Document Type Expired Internet-Draft (individual)
Authors Yi Bai  , Congxiao Bao  , Kevin Yin  , Xing Li 
Last updated 2015-03-25 (latest revision 2014-09-21)
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


OpenStack is a free and open-source software cloud computing platform. It is primarily deployed as an infrastructure as a service (IaaS) solution. However, OpenStack is designed mainly for IPv4, it internally uses [RFC1918] addresses and heavily relies on NAT to map RFC1918 addresses to public IPv4 addresses known as floating IP addresses for the external access. Due to the different nature of IPv6 and IPv4, the IPv6 support for the OpenStack is still in the early stage. In this document, two mechanisms are presented to provide IPv4/IPv6 dual stack external access for the OpenStack, one scenario is internal IPv4 and uses stateful IPv4/IPv6 translator for the external IPv6 access, and another scenario is internal IPv6 and uses stateless IPv4/IPv6 translation for the external IPv4 access. Both mechanisms have been deployed in CERNET and providing services to the global IPv4/IPv6 Internet.


Yi Bai (yibai.thu@gmail.com)
Congxiao Bao (congxiao@cernet.edu.cn)
Kevin Yin (wkyin@cisco.com)
Xing Li (xing@cernet.edu.cn)

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