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

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 22 May 2015 03:54 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 947741A90C2 for <ianaplan@ietfa.amsl.com>; Thu, 21 May 2015 20:54:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 lVYF60J6vhT1 for <ianaplan@ietfa.amsl.com>; Thu, 21 May 2015 20:54:25 -0700 (PDT)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D5D61A90C1 for <ianaplan@ietf.org>; Thu, 21 May 2015 20:54:25 -0700 (PDT)
Received: by pdfh10 with SMTP id h10so8772111pdf.3 for <ianaplan@ietf.org>; Thu, 21 May 2015 20:54:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ey2b1uR4mG3+3W959coKpyluu8jvtRxwuYYNfd11twc=; b=DA1I/Ajb7GC6rmzo34yubDiMaZr+oNw78/j74yGdev7SBC96YEmFRLWgNl/8VNrnP7 FDGfQj/pTtgORtN6o3gvvCXB3TFr+R4pMOOObaz0QJ6MFDG0H2KYUP4SjKN7k8U2uJz4 pOL3xAvy5EKHx4JD5NXTXsDNGWTeHqdqSS3owUXG2izaKhJ8UegL6mIp0oevhfRd5Fl7 ZPfJphpv6aZWV4lmEYOywgMR97FzqbSLeHCRew44JriN4JjHByG8DA0+60HKkJfAL5mz L66ettxylDLE0xw0Rav7bPNL35sgrAQIjneCdCEZdbDoKLmwSfRdahgfVumbT5HswnXJ Br5Q==
X-Received: by 10.68.215.35 with SMTP id of3mr11620612pbc.50.1432266865133; Thu, 21 May 2015 20:54:25 -0700 (PDT)
Received: from ?IPv6:2406:e007:78f3:1:28cc:dc4c:9703:6781? ([2406:e007:78f3:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id zt9sm545716pac.9.2015.05.21.20.54.20 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 21 May 2015 20:54:23 -0700 (PDT)
Message-ID: <555EA874.5040804@gmail.com>
Date: Fri, 22 May 2015 15:54:28 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: John Curran <jcurran@istaff.org>, John C Klensin <john-ietf@jck.com>
References: <5550F809.80200@cisco.com> <88F741BF3D4C2A597622A70C@JcK-HP8200.jck.com> <44A0F230-A98C-4060-88E2-B20FE1DE1FC5@isoc.org> <14ff00ba1aae45f2a8f4befb896e2a08@EX13-MBX-13.ad.syr.edu> <D17525F2-190B-4D00-AEBE-5AD96BA79E79@arin.net> <A026656644A030B7130B94B5@JcK-HP8200.jck.com> <ad1d0707ff1b44eb9e48fef18d8e1268@EX13-MBX-13.ad.syr.edu> <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> <DM2PR0301MB065543B4DCBCB7 51656B563DA8C20@DM2PR0301MB0655.namprd03.prod.outlook.com> <a78386a2666240d48be0aba1fb543e75@EX13-MBX-13.ad.syr.edu> <9F5DADEC7B0F069BA5BCB67A@JcK-HP8200.jck.com> <90712DBB-A97F-48AA-91D5-E1E18A395B33@istaff.org> <748A065C2DEF6DC717B0E802@JcK-HP8200.jck.com> <B8A5D91B-68E7-4EE1-BFA5-40764EF84F86@istaff.org>
In-Reply-To: <B8A5D91B-68E7-4EE1-BFA5-40764EF84F86@istaff.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/4Vwv0att4JGhPGft7MPvulrYKHA>
Cc: Milton L Mueller <mueller@syr.edu>, Christian Huitema <huitema@microsoft.com>, "ianaplan@ietf.org" <ianaplan@ietf.org>
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: Fri, 22 May 2015 03:54:27 -0000

On 22/05/2015 03:33, John Curran wrote:
> On May 21, 2015, at 9:47 AM, John C Klensin <john-ietf@jck.com> wrote:
>> ...
>>  Without either of those two kinds of
>> information, I do have an opinion about impact and risks to the
>> IETF, and have expressed it before, I think in my first note on
>> the subject: this is too complex, it introduces new risks of
>> non-transparent behavior that may be accountable to small groups
>> but is not even as accountable to the broader community as
>> ICANN's operation of IANA is today, and therefore should not be
>> considered acceptable.  
> 
> John -
> 
> You do not consider IETF's MOU for IANA services sufficient to 
> mitigate the risks associated with the CWG proposal? It would 
> be very useful for this community to understand what risks you 
> believe are not addressed by the present RFC 2860 MOU...

I definitely can't speak for John, but empirically, if some new
structure under ICANN can continue the good technical service we
get today under that MoU (and the subsequent additional IETF/ICANN
agreements), we should be happy and the IANAPLAN consensus should
stand. How ICANN organizes and delegates the work isn't our business,
*except* that we need the excellent direct contact with the actual
IANA staff that we have today. I think that's what Stephen Farrell,
Bob Hinden and Avri Doria said too.

But for me at least it is an empirical question; details of
Californian corporation law are remarkably uninteresting.

John Klensin, I suspect, is concerned about the risk that the future
service would fail the empirical test as a result of the proposed
changes. That's clearly a valid concern.

    Brian