RFC 6180 on Guidelines for Using IPv6 Transition Mechanisms during IPv6 Deployment
rfc-editor@rfc-editor.org Sat, 28 May 2011 00:54 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46E13E06BA for <ietf-announce@ietfa.amsl.com>; Fri, 27 May 2011 17:54:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.366
X-Spam-Level:
X-Spam-Status: No, score=-102.366 tagged_above=-999 required=5 tests=[AWL=0.234, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aWBQjCOKZH4k for <ietf-announce@ietfa.amsl.com>; Fri, 27 May 2011 17:54:25 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfa.amsl.com (Postfix) with ESMTP id AA963E0618 for <ietf-announce@ietf.org>; Fri, 27 May 2011 17:54:25 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A0C3AE0777; Fri, 27 May 2011 17:54:25 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6180 on Guidelines for Using IPv6 Transition Mechanisms during IPv6 Deployment
From: rfc-editor@rfc-editor.org
Message-Id: <20110528005425.A0C3AE0777@rfc-editor.org>
Date: Fri, 27 May 2011 17:54:25 -0700
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 May 2011 00:54:26 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6180
Title: Guidelines for Using IPv6 Transition
Mechanisms during IPv6 Deployment
Author: J. Arkko, F. Baker
Status: Informational
Stream: IETF
Date: May 2011
Mailbox: jari.arkko@piuha.net,
fred@cisco.com
Pages: 20
Characters: 49679
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-arkko-ipv6-transition-guidelines-14.txt
URL: http://www.rfc-editor.org/rfc/rfc6180.txt
The Internet continues to grow beyond the capabilities of IPv4. An
expansion in the address space is clearly required. With its
increase in the number of available prefixes and addresses in a
subnet, and improvements in address management, IPv6 is the only real
option on the table. Yet, IPv6 deployment requires some effort,
resources, and expertise. The availability of many different
deployment models is one reason why expertise is required. This
document discusses the IPv6 deployment models and migration tools,
and it recommends ones that have been found to work well in
operational networks in many common situations. This document
is not an Internet Standards Track specification; it is
published for informational purposes.
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
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
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