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

Milton L Mueller <mueller@syr.edu> Tue, 19 May 2015 15:19 UTC

Return-Path: <mueller@syr.edu>
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 E028E1B3068 for <ianaplan@ietfa.amsl.com>; Tue, 19 May 2015 08:19:04 -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 GrBQep8mPH1W for <ianaplan@ietfa.amsl.com>; Tue, 19 May 2015 08:19:02 -0700 (PDT)
Received: from smtp1.syr.edu (smtp1.syr.edu [128.230.18.82]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2703E1B305F for <ianaplan@ietf.org>; Tue, 19 May 2015 08:19:00 -0700 (PDT)
Received: from EX13-MBX-01.ad.syr.edu (ex13-mbx-01.ad.syr.edu [128.230.108.131]) by smtp1.syr.edu (8.14.7/8.14.7) with ESMTP id t4JFIuKm023026 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 19 May 2015 11:18:56 -0400
Received: from EX13-MBX-13.ad.syr.edu (128.230.108.144) by EX13-MBX-01.ad.syr.edu (128.230.108.131) with Microsoft SMTP Server (TLS) id 15.0.847.32; Tue, 19 May 2015 11:18:36 -0400
Received: from EX13-MBX-13.ad.syr.edu ([128.230.108.144]) by EX13-MBX-13.ad.syr.edu ([128.230.108.144]) with mapi id 15.00.0847.030; Tue, 19 May 2015 11:18:37 -0400
From: Milton L Mueller <mueller@syr.edu>
To: 'Richard Hill' <rhill@hill-a.ch>
Thread-Topic: [Ianaplan] CWG draft and its impact on the IETF
Thread-Index: AQHQjBpMEY3mz9BPA0WCyomEcYFu4J13fEsAgACeGQCAAGDXAP//wXfAgAC8H4CAALm3kIAD1/wAgAQiyoCAABXxEIAAT7wAgAANw4D//7750IAA+0WAgAA+JQCAAFIfkA==
Date: Tue, 19 May 2015 15:18:36 +0000
Message-ID: <51ce19bc2a93443586adcdd2fac3888a@EX13-MBX-13.ad.syr.edu>
References: <5550F809.80200@cisco.com> <55511064.2000300@gmail.com> <CAOW+2dvBb4n4W=q7NoO_V1X+JoqvO1TWYBqPAEseY9T7vybj9Q@mail.gmail.com> <CAKFn1SEkBSfk5H5ZjOqfiyaxPak_62cNcRR-SDFH2JJ2HxQumA@mail.gmail.c > <om@mac.com> <59edd953c1d349cfa377bcd72b514b7f@EX13-MBX-13.ad.syr.edu> <C3D17473E06220755959AB78@JcK-HP8200.jck.com> <27ed27614a6b47729043610f09ac197f@EX13-MBX-13.ad.syr.edu> <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>
In-Reply-To: <000001d091f7$266de3f0$7349abd0$@ch>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [128.230.182.126]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.14.151, 1.0.33, 0.0.0000 definitions=2015-05-19_06:2015-05-19,2015-05-19,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1505190193
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/jDnHLjBZB9cOj6ToJTQ3KYtXP6U>
Cc: "'ianaplan@ietf.org'" <ianaplan@ietf.org>, 'Olaf Kolkman' <kolkman@isoc.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: Tue, 19 May 2015 15:19:05 -0000

> -----Original Message-----
> 
> I agree with John. If PTI is a wholly owned subsidiary of ICANN, then I
> don't see how it provides any meaningful separation.

First, let me correct an error: there is no ownership of public benefit corps. If PTI is a public benefit corp. (PBC) it is an affiliate, not a "wholly owned subsidiary." If it is a PBC it can have an insider board or an "outsider" board. An insider board is appointed by and controlled by ICANN; an outsider board is not. If a PBC has an outsider board it can be quite independent. Indeed, the apologists for ICANN have lobbied very strongly against such a proposal for precisely that reason. The issue of PBC vs. LLC is still to be made; and the issue of insider vs outsider board is also not made. So there is a spectrum of separation and independence from ICANN. If your goal is a better proposal (rather than to obstruct a solution) I would interpret your comment to mean that you favor a more independent PTI, as do I. 

However, no matter where the names community locates itself on that spectrum, PTI is still "meaningfully" separated from ICANN. The assets and staff and operations management of PTI would have been moved out of ICANN corporate, 94% of which is names policy related, and into a separately run entity. The work flow process, as John Curran noted yesterday, would become explicit and that would be a meaningful change in terms of separating policy from implementation. By creating a separate affiliate, a contract and creating a periodic review process which has rebidding the contract possible, we also make it more feasible to fire PTI and use a different IANA functions provider. 

> I don't think that it addresses the number 1 priority issue identified by
> the Working Group on Internet Governance back in 2005, namely the
> asymmetric role of the USA, because it seems that ICANN and PTI will
> be based in the US and subject to US law.

I understand that this is your real concern, so perhaps that explains why you are taking off-target pot shots at PTI. 
But let's confront the real issue, and not make the corporate structure of PTI a proxy. 

My answer to you is:
1) the number 1 concern of the WGIG (and it was 2004, not 2005) was NOT U.S. jurisdiction, but unilateral U.S. government control over the IANA contract. The stewardship transition does address that. 

2) There is surprisingly little support in the names community for moving ICANN or PTI out of U.S. jurisdiction. There would be fervent opposition to doing so from the U.S. Congress and many others. As you know, I am agnostic on that issue; I think PTI could be jurisdictionally domiciled anywhere especially if it is just an independent contractor of ICANN. But as a practical political matter, it probably won't be, at least not in the initial stages of this change.