Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC

Erik Kline <ek@google.com> Fri, 03 February 2012 03:04 UTC

Return-Path: <ek@google.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2725C11E8072 for <v6ops@ietfa.amsl.com>; Thu, 2 Feb 2012 19:04:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.377
X-Spam-Level:
X-Spam-Status: No, score=-102.377 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, 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 beMfybg9jG2E for <v6ops@ietfa.amsl.com>; Thu, 2 Feb 2012 19:04:09 -0800 (PST)
Received: from mail-tul01m020-f172.google.com (mail-tul01m020-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id DE95311E8071 for <v6ops@ietf.org>; Thu, 2 Feb 2012 19:04:08 -0800 (PST)
Received: by obbwd15 with SMTP id wd15so4435585obb.31 for <v6ops@ietf.org>; Thu, 02 Feb 2012 19:04:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:x-system-of-record:content-type:content-transfer-encoding; bh=0asXAR0YJ9bNbQ7IYFFtRqiP3MiXdCmmQNZAbeXhRp0=; b=f2zluPHpfYblmRcgNJPkXJCJeBgwERaKHAzW+72SLtg5lWXi2OGf6bs0Kudl79uz77 hsaPlmHPXBUcl1HKx8Z5OpPopDNAzX0lTRyGK9VQxZywQ5I1RTUZtOfiCAYr8M7mp1K0 DcohRfcvD80NpbmQjwFk2io1+rDQRRqK3jFUg=
Received: by 10.182.75.65 with SMTP id a1mr4949922obw.32.1328237845535; Thu, 02 Feb 2012 18:57:25 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.75.65 with SMTP id a1mr4949861obw.32.1328237844017; Thu, 02 Feb 2012 18:57:24 -0800 (PST)
Received: by 10.182.97.4 with HTTP; Thu, 2 Feb 2012 18:57:23 -0800 (PST)
In-Reply-To: <20120201150911.25955.80172.idtracker@ietfa.amsl.com>
References: <20120201150911.25955.80172.idtracker@ietfa.amsl.com>
Date: Fri, 03 Feb 2012 11:57:23 +0900
Message-ID: <CAAedzxqXaPtNkyGt-P9xzdxvPkgLXcGOr-f3q7BuRq9555duaw@mail.gmail.com>
From: Erik Kline <ek@google.com>
To: ietf@ietf.org
X-System-Of-Record: true
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: v6ops@ietf.org, IETF-Announce <ietf-announce@ietf.org>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 03 Feb 2012 03:04:09 -0000

World IPv6 Launch changes the relevance of this document greatly, I
think.  Since this would be published after the announcement of World
IPv6 Launch, I think the document should be updated to discuss its own
applicability in a post- World IPv6 Launch Internet.

On 2 February 2012 00:09, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from the IPv6 Operations WG (v6ops) to
> consider the following document:
> - 'Considerations for Transitioning Content to IPv6'
>  <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> as an
> Informational RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-02-15. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>   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.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-v6ops-v6-aaaa-whitelisting-implications/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-v6ops-v6-aaaa-whitelisting-implications/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops