IPv4/IPv6 Transition Practice in OpenStack
draft-ybai-v6ops-ipv6-for-openstack-04

Document Type Active Internet-Draft (individual)
Last updated 2016-09-20
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                             Y. Bai
Internet-Draft                                                    C. Bao
Intended status: Informational         CERNET Center/Tsinghua University
Expires: March 24, 2017                                           K. Yin
                                                           Cisco Systems
                                                                   X. Li
                                       CERNET Center/Tsinghua University
                                                      September 20, 2016

               IPv4/IPv6 Transition Practice in OpenStack
                 draft-ybai-v6ops-ipv6-for-openstack-04

Abstract

   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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on March 24, 2017.

Bai, et al.              Expires March 24, 2017                 [Page 1]
Internet-Draft IPv4/IPv6 Transition Practice in OpenStack September 2016

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  IPv4/IPv6 access to IPv4-only Cloud . . . . . . . . . . . . .   3
     2.1.  Current IPv4 OpenStack Network Structures . . . . . . . .   3
     2.2.  IPv4 Accessibility directly . . . . . . . . . . . . . . .   3
     2.3.  IPv6 Accessibility via IPv4/IPv6 translator . . . . . . .   4
   3.  IPv4/IPv6 access to IPv6-only Cloud . . . . . . . . . . . . .   5
     3.1.  Analysis and recommendations for the Internal Structure
           of IPv6 OpenStack . . . . . . . . . . . . . . . . . . . .   5
     3.2.  IPv4 Accessibility via Translation  . . . . . . . . . . .   6
       3.2.1.  1:N Stateless Translation . . . . . . . . . . . . . .   7
       3.2.2.  HTTP Redirection for Web Servers  . . . . . . . . . .   8
   4.  Summary . . . . . . . . . . . . . . . . . . . . . . . . . . .   9
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   9
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   The concept of cloud is growing rapidly, and open-source cloud
   platforms such as OpenStack are more and more popular.  The network
   models inside OpenStack cloud requires public IPv4 addresses for
   external access.  It's foreseeable that the exhaustion of IPv4 global
   addresses would be one of the bottlenecks on deploying clouds in the
Show full document text