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

Milton L Mueller <mueller@syr.edu> Wed, 20 May 2015 13:14 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 7D9881A1A5A for <ianaplan@ietfa.amsl.com>; Wed, 20 May 2015 06:14:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.311
X-Spam-Level:
X-Spam-Status: No, score=-2.311 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, 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 DljHqGSomzJk for <ianaplan@ietfa.amsl.com>; Wed, 20 May 2015 06:14:33 -0700 (PDT)
Received: from smtp2.syr.edu (smtp2.syr.edu [128.230.18.92]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 58C2D1A1A69 for <ianaplan@ietf.org>; Wed, 20 May 2015 06:14:30 -0700 (PDT)
Received: from EX13-MBX-10.ad.syr.edu (ex13-mbx-10.ad.syr.edu [128.230.108.141]) by smtp2.syr.edu (8.14.7/8.14.7) with ESMTP id t4KDERX4002101 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 20 May 2015 09:14:27 -0400
Received: from EX13-MBX-13.ad.syr.edu (128.230.108.144) by EX13-MBX-10.ad.syr.edu (128.230.108.141) with Microsoft SMTP Server (TLS) id 15.0.847.32; Wed, 20 May 2015 09:14:26 -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; Wed, 20 May 2015 09:14:26 -0400
From: Milton L Mueller <mueller@syr.edu>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: [Ianaplan] CWG draft and its impact on the IETF
Thread-Index: AQHQjBpMEY3mz9BPA0WCyomEcYFu4J13fEsAgACeGQCAAGDXAP//wXfAgAC8H4CAALm3kIAD1/wAgAQiyoCAABXxEIAAT7wAgAANw4D//7750IAA+0WAgAA+JQCAAFIfkIAA5ESAgACRLEA=
Date: Wed, 20 May 2015 13:14:25 +0000
Message-ID: <031291ec0981414b94b625d1eed2fb62@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> <51ce19bc2a93443586adcdd2fac3888a@EX13-MBX-13.ad.syr.edu> <555BD28F.10402@gmail.com>
In-Reply-To: <555BD28F.10402@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [24.97.176.186]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
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-20_04:2015-05-19,2015-05-20,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-1505200175
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/j7jCicNrxpEBJ3oVM63VnP8L4NA>
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: Wed, 20 May 2015 13:14:35 -0000

> -----Original Message-----
> I've been mulling over the implications of this. Either PTI will be controlled
> by ICANN or it won't. If it *is* effectively controlled by ICANN, the IETF can
> sit back and relax until our SLA is no longer met, in which case we go to Plan
> B (i.e. no change in the state that has existed for 15 years).
> 
> If PTI is *not* effectively controlled by ICANN, we are straight into Plan B:
> giving notice to ICANN and bidding out a protocol parameter services
> contract, with PTI as an obvious bidder, hopefully at zero cost. (I would
> seriously expect several zero- cost bids to show up.)

Given current and past history, I am surprised that you find control by ICANN, as opposed to control by a more focused and independent PTI board that could, e.g., contain members from ICANN, ASO and IETF, so comfortable and secure. (Remember this would be a "new" ICANN unsupervised by NTIA). But if you really feel that way and have considered all the ramifications of various governance models for PTI, then by all means file comments in the proceeding saying so. That would be relevant input, assuming you had good reasons for your preference.

> What does 'effectively controlled' mean? I think it's an empirical question. As
> a counter-example, Ports of Auckland is wholly owned by Auckland Council
> Investments Limited, itself owned by the Auckland Council. But Ports of
> Auckland prefers to ignore the wishes of the community* that elected
> Auckland Council when it suits their commercial interests. This is a direct
> result of the transition from the port being in public ownership to being
> semi-privatized.

That is one of the reasons many of us favor incorporating PTI as a California Nonprofit Public Benefit Corp. 
The law under which PBCs are incorporated contain a lot of protections against commercial expropriation.  You can find discussion of this issue here: http://www.internetgovernance.org/2015/05/18/why-the-post-transition-iana-should-be-a-nonprofit-public-benefit-corporation/

In terms of what "control" means, there are various options on the table. A PTI incorporated as a PBC with a board the majority of which is not appointed by ICANN is the most independent option. A PTI inc as a PBC with a board appointed by ICANN but the selections governed by preset rules (e.g., you must appoint someone from IETF, someone from ASO, someone from names) is a slightly less independent option. A PTI with a so-called "insider" board, directly appointed by ICANN, including just ICANN staff members, is not independent at all. A PTI incorporated as a Delaware LLC is the least independent and the most susceptible to control and manipulation by ICANN unless strong protections are negotiated into the management agreement.