[v6ops] RFC 7755 on SIIT-DC: Stateless IP/ICMP Translation for IPv6 Data Center Environments
rfc-editor@rfc-editor.org Thu, 18 February 2016 03:32 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91A1B1A0AC8; Wed, 17 Feb 2016 19:32:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.908
X-Spam-Level:
X-Spam-Status: No, score=-106.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.006, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xMElTlWctn0Z; Wed, 17 Feb 2016 19:31:59 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08C271A00CC; Wed, 17 Feb 2016 19:31:59 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 6FF63180013; Wed, 17 Feb 2016 19:31:44 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160218033144.6FF63180013@rfc-editor.org>
Date: Wed, 17 Feb 2016 19:31:44 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/jCLPNE0ehbNaIv479GhcJ4qLNRk>
Cc: v6ops@ietf.org, rfc-editor@rfc-editor.org
Subject: [v6ops] RFC 7755 on SIIT-DC: Stateless IP/ICMP Translation for IPv6 Data Center Environments
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Feb 2016 03:32:00 -0000
A new Request for Comments is now available in online RFC libraries. RFC 7755 Title: SIIT-DC: Stateless IP/ICMP Translation for IPv6 Data Center Environments Author: T. Anderson Status: Informational Stream: IETF Date: February 2016 Mailbox: tore@redpill-linpro.com Pages: 24 Characters: 54648 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-v6ops-siit-dc-03.txt URL: https://www.rfc-editor.org/info/rfc7755 DOI: http://dx.doi.org/10.17487/RFC7755 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. This document is a product of the IPv6 Operations Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC