RFC 6589 on Considerations for Transitioning Content to IPv6
rfc-editor@rfc-editor.org Fri, 20 April 2012 23:20 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 8042121E8039; Fri, 20 Apr 2012 16:20:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.274
X-Spam-Level:
X-Spam-Status: No, score=-102.274 tagged_above=-999 required=5 tests=[AWL=0.326, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ryZXhPOdXRHw; Fri, 20 Apr 2012 16:20:18 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 3CED021E8064; Fri, 20 Apr 2012 16:20:17 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A263EB1E017; Fri, 20 Apr 2012 16:19:07 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6589 on Considerations for Transitioning Content to IPv6
From: rfc-editor@rfc-editor.org
Message-Id: <20120420231907.A263EB1E017@rfc-editor.org>
Date: Fri, 20 Apr 2012 16:19:07 -0700
Cc: v6ops@ietf.org, 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: Fri, 20 Apr 2012 23:20:18 -0000
A new Request for Comments is now available in online RFC libraries. RFC 6589 Title: Considerations for Transitioning Content to IPv6 Author: J. Livingood Status: Informational Stream: IETF Date: April 2012 Mailbox: jason_livingood@cable.comcast.com Pages: 27 Characters: 68822 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-11.txt URL: http://www.rfc-editor.org/rfc/rfc6589.txt This document describes considerations for the transition of end-user content on the Internet to IPv6. While this is tailored to address end-user content, which is typically web-based, many aspects of this document may be more broadly applicable to the transition to IPv6 of other applications and services. This document explores the challenges involved in the transition to IPv6, potential migration tactics, possible migration phases, and other considerations. The audience for this document is the Internet community generally, particularly IPv6 implementers. This document is not an Internet Standards Track specification; it is published for informational purposes. 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 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