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

Milton L Mueller <mueller@syr.edu> Mon, 18 May 2015 15:12 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 64EA11A9151 for <ianaplan@ietfa.amsl.com>; Mon, 18 May 2015 08:12:48 -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 Hix3FaayJNX3 for <ianaplan@ietfa.amsl.com>; Mon, 18 May 2015 08:12:45 -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 EEC911A914C for <ianaplan@ietf.org>; Mon, 18 May 2015 08:12:44 -0700 (PDT)
Received: from EX13-MBX-08.ad.syr.edu (ex13-mbx-08.ad.syr.edu [128.230.108.139]) by smtp1.syr.edu (8.14.7/8.14.7) with ESMTP id t4IFCfjQ000788 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 18 May 2015 11:12:41 -0400
Received: from EX13-MBX-13.ad.syr.edu (128.230.108.144) by EX13-MBX-08.ad.syr.edu (128.230.108.139) with Microsoft SMTP Server (TLS) id 15.0.847.32; Mon, 18 May 2015 11:12:40 -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; Mon, 18 May 2015 11:12:40 -0400
From: Milton L Mueller <mueller@syr.edu>
To: John C Klensin <john-ietf@jck.com>
Thread-Topic: [Ianaplan] CWG draft and its impact on the IETF
Thread-Index: AQHQjBpMEY3mz9BPA0WCyomEcYFu4J13fEsAgACeGQCAAGDXAP//wXfAgAC8H4CAALm3kIAD1/wAgAQiyoCAABXxEIAAT7wAgAANw4D//7750A==
Date: Mon, 18 May 2015 15:12:40 +0000
Message-ID: <ad1d0707ff1b44eb9e48fef18d8e1268@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>
In-Reply-To: <A026656644A030B7130B94B5@JcK-HP8200.jck.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [108.26.56.166]
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-18_04:2015-05-18,2015-05-18,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-1505180188
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/YpRNh9DWRYOuM0w-ATSRgo1pqKU>
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: Mon, 18 May 2015 15:12:48 -0000

> -----Original Message-----
> Yes.  See the response I just sent to Olaf, but it seems to me that a "PTI" as a
> subcontracting arrangement to (more or less) an internal department is
> inconsistent with the (apparent) CWG of separation and independence and,

Wrong. This has been explained repeatedly; PTI provides separation, a limited amount of independence and mirrors the relationship numbers and protocols already have. Complete independence would be preferable but is not politically feasible. 

> as you have pointed out a separately-managed and accountable PTI that
> operates as a mostly-independent affiliate or subsidary of ICANN would not
> be plausible without IETF and address community consent and that there
> are reasons why it might not be in the interest of those bodies to provide
> that consent.

Except that you have not provided any plausible reasons why they shouldn't. The numbers contract doesn't exist yet and thus could easily specify either ICANN or PTI as its counterparty. The protocols MoU and SLA could be assigned to PTI without any change in its substance. 

> Assuming that consent will not be lightly or quickly given, the question for
> me becomes whether the independent-affiliate version of the PTI concept is
> valuable enough to the Names community to justify splitting up the IANA
> function.  And, if it is, whether the result is a sufficiently consistent and

As I've said before, there will be an independent-affiliate PTI or there won't be a transition in the next two years. Take your pick.