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

Lorenzo Colitti <lorenzo@google.com> Wed, 08 February 2012 13:54 UTC

Return-Path: <lorenzo@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 32F4321F865B for <v6ops@ietfa.amsl.com>; Wed, 8 Feb 2012 05:54:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.676
X-Spam-Level:
X-Spam-Status: No, score=-102.676 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 49HdVvrCXb1S for <v6ops@ietfa.amsl.com>; Wed, 8 Feb 2012 05:54:51 -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 A02E421F85D9 for <v6ops@ietf.org>; Wed, 8 Feb 2012 05:54:51 -0800 (PST)
Received: by obbwd15 with SMTP id wd15so1023543obb.31 for <v6ops@ietf.org>; Wed, 08 Feb 2012 05:54:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:x-system-of-record:content-type; bh=ENct9zuBM/KtSoi788U61wDlvFKkk+3auCus6P3AbdA=; b=bm2E4v5g3eYiOW9JD9yTZW7XYWzx9DJSH8no7P65BLiu3+8FAJOky5Hii/LQXZJoTh +3pKmX88U/MGCtwsTwZSAlTbqMKqhHvXzVT3XvLpNc8NW34eceQtgBU5jTjwy+xrB7KY ugCW6TKc9KtWWdfGQvObmQI1cecKPsiUBKtE0=
Received: by 10.182.8.69 with SMTP id p5mr25761754oba.28.1328709291319; Wed, 08 Feb 2012 05:54:51 -0800 (PST)
Received: by 10.182.8.69 with SMTP id p5mr25761741oba.28.1328709291188; Wed, 08 Feb 2012 05:54:51 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.81.71 with HTTP; Wed, 8 Feb 2012 05:54:31 -0800 (PST)
In-Reply-To: <8EA035DE-DAB9-4920-9BD6-75944848CA5D@cisco.com>
References: <20120201150911.25955.80172.idtracker@ietfa.amsl.com> <CAAedzxqXaPtNkyGt-P9xzdxvPkgLXcGOr-f3q7BuRq9555duaw@mail.gmail.com> <8EA035DE-DAB9-4920-9BD6-75944848CA5D@cisco.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 08 Feb 2012 22:54:31 +0900
Message-ID: <CAKD1Yr2xgkEeK7SaRjMZSbdJPs0u5FTozo0qa5MA4fda+SBcyw@mail.gmail.com>
To: Fred Baker <fred@cisco.com>
X-System-Of-Record: true
Content-Type: multipart/alternative; boundary="f46d0444ec4b4fa32b04b8743d3a"
Cc: v6ops v6ops WG <v6ops@ietf.org>, IETF Discussion <ietf@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: Wed, 08 Feb 2012 13:54:52 -0000

On Sat, Feb 4, 2012 at 01:35, Fred Baker <fred@cisco.com> wrote:

> The IESG again decided it needed a revised draft, and that draft - in
> large part, a rewrite - arrived in October. v6ops had a second WGLC, in
> which you again declined to comment, although you may have seen Lorenzo's
> comments, which were picked up in a November version of the draft. Ralph
> and Jari finally cleared their "discuss" ballots a couple of weeks ago, and
> we are having a second IETF last call.
>
> I'd like to understand your objective here. I know that you don't care for
> the draft, and at least at one point took it as a somewhat-personal attack.
> Is your objective to prevent the draft's publication entirely, or do you
> think that there is value in publishing it given a productive response to
> this comment? At what point are you willing to either participate in the
> public dialog or choose to not comment at all?


Ok, let me see if I can rephrase Erik's objection.

The draft needs to take World IPv6 Launch into account, because it's a key
piece of the puzzle.

We can't publish an RFC on how to transition content to IPv6 if the RFC
ignores the event when 5 of the top 10 websites in the world (and probably
many more) will permanently enable IPv6 for everyone.

Cheers,
Lorenzo