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

John Curran <jcurran@arin.net> Mon, 18 May 2015 14:08 UTC

Return-Path: <jcurran@arin.net>
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 50D401A8A01 for <ianaplan@ietfa.amsl.com>; Mon, 18 May 2015 07:08:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.01
X-Spam-Level:
X-Spam-Status: No, score=-0.01 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HTML_MESSAGE=0.001, 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 KjaOzBAvDVNs for <ianaplan@ietfa.amsl.com>; Mon, 18 May 2015 07:08:11 -0700 (PDT)
Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id C6FCB1A8AA7 for <ianaplan@ietf.org>; Mon, 18 May 2015 07:08:10 -0700 (PDT)
Received: by smtp1.arin.net (Postfix, from userid 323) id 4CBB8164F29; Mon, 18 May 2015 10:08:10 -0400 (EDT)
Received: from chaedge02.corp.arin.net (chaedge02.corp.arin.net [192.149.252.119]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp1.arin.net (Postfix) with ESMTP id 8B83C164F12; Mon, 18 May 2015 10:08:09 -0400 (EDT)
Received: from CHACAS01.corp.arin.net (10.1.30.107) by chaedge02.corp.arin.net (192.149.252.119) with Microsoft SMTP Server (TLS) id 14.3.210.2; Mon, 18 May 2015 10:13:56 -0400
Received: from CHAMBX01.corp.arin.net ([fe80::1cef:1d7:cca9:5953]) by CHACAS01.corp.arin.net ([fe80::a98b:1e52:e85a:5979%13]) with mapi id 14.03.0224.002; Mon, 18 May 2015 10:08:08 -0400
From: John Curran <jcurran@arin.net>
To: Milton L Mueller <mueller@syr.edu>
Thread-Topic: [Ianaplan] CWG draft and its impact on the IETF
Thread-Index: AQHQkXQQ6mbfotxNbkO1G1Gw+JTR5g==
Date: Mon, 18 May 2015 14:08:08 +0000
Message-ID: <D17525F2-190B-4D00-AEBE-5AD96BA79E79@arin.net>
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>
In-Reply-To: <14ff00ba1aae45f2a8f4befb896e2a08@EX13-MBX-13.ad.syr.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.149.252.96]
Content-Type: multipart/alternative; boundary="_000_D17525F2190B4D00AEBE5AD96BA79E79arinnet_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/jKQJ70YJsiiYdsZpysaHxa-GNGY>
Cc: John C Klensin <john-ietf@jck.com>, "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 14:08:12 -0000

On May 18, 2015, at 9:35 AM, Milton L Mueller <mueller@syr.edu<mailto:mueller@syr.edu>> wrote:
MM: Yes - as long as you remember that PTI, while a legally separate entity, is also an affiliate of ICANN; i.e., it is indirectly under its control. Further, I don’t think most people on this list are committed to model 1, because from a simple efficiency standpoint PTI will include all the IANA functions. So Mental Model 1 and 2 could co-exist, as long as ICANN assigns its contract with IETF and NRO to PTI. What is not viable is to keep protocols and numbers out of PTI.

Milton -

   Your statement -

         “So Mental Model 1 and 2 could co-exist, as long as ICANN assigns its contract with IETF and NRO to PTI.”

   may be accurate but is quite different than -

         “So Mental Model 1 and 2 could co-exist, as long as ICANN has PTI perform the protocol and number registries work on ICANN’s behalf.”

  i.e. an internal subcontracting from ICANN to PRI versus agreement _assignment_ from
  ICANN to PTI.   A internal subcontracting arrangement is unlikely to be material for the IETF
  and the RIRs, whereas an agreement assignment is visible, has some significant implications,
  and would require consent of the parties.

FYI,
/John