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

Joel jaeggli <joelja@bogus.com> Wed, 08 February 2012 15:37 UTC

Return-Path: <joelja@bogus.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 1F80B21F8701; Wed, 8 Feb 2012 07:37:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.849
X-Spam-Level:
X-Spam-Status: No, score=-101.849 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, 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 PFwByYVouxow; Wed, 8 Feb 2012 07:37:09 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 95AF021F8700; Wed, 8 Feb 2012 07:37:09 -0800 (PST)
Received: from Joels-MacBook-Pro.local (115.sub-166-250-77.myvzw.com [166.250.77.115]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q18Fb5Ot039504 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Wed, 8 Feb 2012 15:37:06 GMT (envelope-from joelja@bogus.com)
Message-ID: <4F329696.6000505@bogus.com>
Date: Wed, 08 Feb 2012 07:36:54 -0800
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
References: <20120201150911.25955.80172.idtracker@ietfa.amsl.com> <CAAedzxqXaPtNkyGt-P9xzdxvPkgLXcGOr-f3q7BuRq9555duaw@mail.gmail.com> <8EA035DE-DAB9-4920-9BD6-75944848CA5D@cisco.com> <CAKD1Yr2xgkEeK7SaRjMZSbdJPs0u5FTozo0qa5MA4fda+SBcyw@mail.gmail.com>
In-Reply-To: <CAKD1Yr2xgkEeK7SaRjMZSbdJPs0u5FTozo0qa5MA4fda+SBcyw@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Wed, 08 Feb 2012 15:37:07 +0000 (UTC)
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 15:37:10 -0000

On 2/8/12 05:54 , Lorenzo Colitti wrote:
> On Sat, Feb 4, 2012 at 01:35, Fred Baker <fred@cisco.com
> <mailto: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.

Ops is not marketing.

If you're saying some flag day makes the contents of the document no
longer operationally relevant after a given date, I'll take the point
but disagree.

The document in it's present form has a wider audience than the
operators at 5 of the ton 10 websites.

> Cheers,
> Lorenzo
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops