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

Jari Arkko <jari.arkko@piuha.net> Fri, 22 May 2015 20:32 UTC

Return-Path: <jari.arkko@piuha.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 008261A87E9 for <ianaplan@ietfa.amsl.com>; Fri, 22 May 2015 13:32:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Gpa_atkVzpgv for <ianaplan@ietfa.amsl.com>; Fri, 22 May 2015 13:32:46 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id A612F1A87E2 for <ianaplan@ietf.org>; Fri, 22 May 2015 13:32:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 9C3142CC5F; Fri, 22 May 2015 23:32:43 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mgCT8VHy6cBP; Fri, 22 May 2015 23:32:43 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id C30D92CC5A; Fri, 22 May 2015 23:32:42 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
Content-Type: multipart/signed; boundary="Apple-Mail=_56C72D68-2A04-4419-9822-2992D5661D23"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <DFB75267-68D0-41D8-BFDC-3602BCE223A0@LStAmour.org>
Date: Fri, 22 May 2015 23:32:41 +0300
Message-Id: <FF9F9F1D-5225-4BDC-8AB9-C7E3B9BF081B@piuha.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> <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> <DM2PR0301MB065543B4DCBCB 751656B563DA8C20@DM2PR0301MB0655.namprd03.prod.outlook.com> <66F939A5-C6B0-48C4-9D12-5B1C2ADC4B69@gmail.com> <DFB75267-68D0-41D8-BFDC-3602BCE223A0@LStAmour.org>
To: "Lynn St.Amour" <Lynn@LStAmour.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/sjTcxRbTAOelu8M1uZJqrD2swoc>
Cc: "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 20:32:48 -0000

Lynn,

> Many of the postings on this thread seem to assume unfavorable conditions for the PTI/PTI Board, etc.   That is because the Names community has not had time to complete all their work..  I think we can help them advance their work, which frankly is our work as well, and is in the interest of a global public Internet.
> 
> Here are my working assumptions, please correct them if they are off the mark.  They are obviously missing lots of detail.
> 
> 1 - We support (as good practice) separation between policy, oversight, and implementation for the 3 components of the IANA function (in each of the 3 areas - the so-called 3x3)
> 2 - Protocol Parameters has this (and btw, this PTI proposal was modeled heavily on the IETF)
> 3 - Numbers also largely has this.
> 4 - The Names community is trying to get to this.
> 5 - There is a preference for the 3 IANA functions to stay together at the IMPLEMENTATION role (only), but it is not seen as necessary from any of the operating communities (OC's).
> 
> More specific to the CWG proposal:
> 
> A - The PTI would be a narrow purposed organization built to house only the IANA IMPLEMENTATION functions (preferably for all three operating communities?, and I believe the IETF and RIR's assume the work would be done within the PTI *if* that structure goes forward (that is the IANA staff would be housed within the PTI even while their contracts may remain with ICANN).    This should be clarified as soon as their processes allow, as this seems to be one of the points of confusion.  
> B - The PTI would have its own board and would be responsible for the PTI  (many models to accomplish this - even with the funding considerations)
> C - The PTI Board need not have a majority of ICANN Board members - this is the current discussion within Names about ‘inside’ and ‘outside'.   The options would allow, I believe, for a full spectrum of:  no special role for ICANN to a strong central role for ICANN.   
> 
> I believe the Names community would appreciate input/specific questions from the IETF - and I believe it would be useful to all of us if we could look at the proposal and see what we might be able to live with (or not be able to live with).  Either way we advance the discussion if we can share some concrete questions/preferences.   If we identify too many hurdles, well at least we can be specific on why it won't work for us, and again that will help the OC's and the ICG to advance the transition proposal.  For example, could the IETF identify some preferences re Board composition/by-laws/policies, etc.  Frankly, I can see some benefits to working with a purpose built PTI vs. the full-bodied ICANN :-) . 
> 
> If the 3 operating communities could come to agreement on how the proposals fit together, it would help advance the Transition proposal work significantly - for the OC's as well as the ICG.  

Thank you for this. I agree.

Jari