Re: [Ianaplan] CWG draft and its impact on the IETF

Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 21 May 2015 14:09 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ianaplan@ietfa.amsl.com
Delivered-To: ianaplan@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74C561A0334 for <ianaplan@ietfa.amsl.com>; Thu, 21 May 2015 07:09:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EVELkKfNqhQw for <ianaplan@ietfa.amsl.com>; Thu, 21 May 2015 07:09:52 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D26A1A0277 for <ianaplan@ietf.org>; Thu, 21 May 2015 07:09:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 16AE3BEC6; Thu, 21 May 2015 15:09:51 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J4k78LJ3Rb0M; Thu, 21 May 2015 15:09:50 +0100 (IST)
Received: from [10.87.48.73] (unknown [86.46.24.221]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id E05F5BEAF; Thu, 21 May 2015 15:09:49 +0100 (IST)
Message-ID: <555DE72D.20509@cs.tcd.ie>
Date: Thu, 21 May 2015 15:09:49 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>, ianaplan@ietf.org
References: <687222FF507C0D3EDBD9CAAA@JcK-HP8200.jck.com> <000001d091f7$266de3f0$7349abd0$@ch> <51ce19bc2a93443586adcdd2fac3888a@EX13-MBX-13.ad.syr.edu> <555BD28F.10402@gmail.com> <97E5874491A30994EC386C37@JcK-HP8200.jck.com> <555CEDFF.5010601@gmail.com> <51E8C05D9CFB07754ECD13F5@JcK-HP8200.jck.com> <DM2PR0301MB065543B4DCBCB751656B563DA8C20@DM2PR0301MB0655.namprd03.prod.outlook.com> <a78386a2666240d48be0aba1fb543e75@EX13-MBX-13.ad.syr.edu> <555DE2E7.2010201@cs.tcd.ie> <20150521140411.GC20218@mx2.yitter.info>
In-Reply-To: <20150521140411.GC20218@mx2.yitter.info>
OpenPGP: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/efIhzSOqeOxxxcjVDtxi_1GftVs>
Subject: Re: [Ianaplan] CWG draft and its impact on the IETF
X-BeenThere: ianaplan@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IANA Plan <ianaplan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ianaplan/>
List-Post: <mailto:ianaplan@ietf.org>
List-Help: <mailto:ianaplan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 May 2015 14:09:53 -0000


On 21/05/15 15:04, Andrew Sullivan wrote:
> On Thu, May 21, 2015 at 02:51:35PM +0100, Stephen Farrell wrote:
>> So I'd be interested in hearing from other folks who agree
>> with what might be the position Milton has (after all the
>> overstatement is discounted:-). Or who think that the IETF
>> ought do something directly involving the PTI (e.g. to
>> re-open the MoU to change the partner involved or something.)
> 
> I don't know that Avri's message actually meets those criteria, but it
> is in my opinion the clearest and best statement of the argument in
> this thread as to why the IETF might want to get involved in PTI
> directly.  (I, for one, appreciated it.)

I also read Avri's message but she didn't seem to be arguing
that we ought do any specific thing now. And when I read that
I mostly thought: "hmm, sounds like we should let the CWG thing
play out and if a PTI is setup we should see how that pans
out and in the meantime, doing nothing (for the IETF) seems
right."

S.


> 
> A
>