Browse Prior Art Database

SIIT-DC: Stateless IP/ICMP Translation for IPv6 Data Center Environments (RFC7755) Disclosure Number: IPCOM000245190D
Original Publication Date: 2016-Feb-01
Included in the Prior Art Database: 2016-Feb-18
Document File: 48 page(s) / 55K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

T. Anderson: AUTHOR


Historically, dual stack [RFC4213] [RFC6883] has been the recommended way to transition from a legacy IPv4-only environment to one capable of serving IPv6 users. However, for IDC operators, dual-stack operation has a number of disadvantages compared to single-stack operation. In particular, running two protocols rather than one results in increased complexity and operational overhead with little return on investment for as long as large parts of the public Internet remains predominantly IPv4 only. Furthermore, the dual- stack approach does not in any way help with the depletion of the IPv4 address space, which at the time of writing is a pressing concern in most parts of the world.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 5% of the total text.

Internet Engineering Task Force (IETF)                       T. Anderson Request for Comments: 7755                                Redpill Linpro Category: Informational                                    February 2016 ISSN: 2070-1721

 SIIT-DC: Stateless IP/ICMP Translation for IPv6 Data Center Environments


   This document describes the use of the Stateless IP/ICMP Translation    Algorithm (SIIT) in an IPv6 Internet Data Center (IDC).  In this    deployment model, traffic from legacy IPv4-only clients on the    Internet is translated to IPv6 upon reaching the IDC operator's    network infrastructure.  From that point on, it may be treated the    same as traffic from native IPv6 end users.  The IPv6 endpoints may    be numbered using arbitrary (non-IPv4-translatable) IPv6 addresses.    This facilitates a single-stack IPv6-only network infrastructure, as    well as efficient utilization of public IPv4 addresses.

   The primary audience is IDC operators who are deploying IPv6, running    out of available IPv4 addresses, and/or feeling that dual stack    causes undesirable operational complexity.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Not all documents    approved by the IESG are a candidate for any level of Internet    Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at

 Anderson                      Informational                     [Page 1]
 RFC 7755                         SIIT-DC                   February 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    ( 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  . . . . . . . . . . . . . . ....