Re: [Ianaplan] Process concern regarding the IETF proposal development process

John Curran <jcurran@istaff.org> Sat, 24 January 2015 22:22 UTC

Return-Path: <jcurran@istaff.org>
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 9CA721A037B for <ianaplan@ietfa.amsl.com>; Sat, 24 Jan 2015 14:22:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level:
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_20=-0.001] 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 32vVsf3KGkAr for <ianaplan@ietfa.amsl.com>; Sat, 24 Jan 2015 14:22:17 -0800 (PST)
Received: from smtp4.ore.mailhop.org (smtp4.ore.mailhop.org [54.149.240.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDA181A004D for <ianaplan@ietf.org>; Sat, 24 Jan 2015 14:22:17 -0800 (PST)
Received: from pool-108-56-179-253.washdc.fios.verizon.net ([108.56.179.253] helo=[192.168.1.7]) by smtp4.ore.mailhop.org with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.82) (envelope-from <jcurran@istaff.org>) id 1YF95r-0002UK-Ou; Sat, 24 Jan 2015 22:22:15 +0000
X-Mail-Handler: DuoCircle Outbound SMTP
X-Originating-IP: 108.56.179.253
X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information)
X-MHO-User: U2FsdGVkX19aT2GSFIeaitDfOJ3kRXRL
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: John Curran <jcurran@istaff.org>
In-Reply-To: <54C3D305.6030705@acm.org>
Date: Sat, 24 Jan 2015 17:22:13 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <4C1F1D95-65FF-45A3-99FF-DD6D8719BDFA@istaff.org>
References: <C172BBB7-9BA4-4BA7-848C-C7FE5B66CBF7@cooperw.in> <F8FC64C8-6FC7-4672-B18B-46DF993A653A@cooperw.in> <54C091D2.9050608@gmail.com> <1F30A463-76A9-4854-952A-35C54E42D2C6@istaff.org> <CAOW+2dvd1QRC6xbDTZ6ah23HfX=K=SeXDc1kXr2NREAcy37SvQ@mail.gmail.com> <54C13630.3050601@meetinghouse.net> <54C3D305.6030705@acm.org>
To: Avri Doria <avri@acm.org>
X-Mailer: Apple Mail (2.1993)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/SaTkB9R7WLtbsc4T1Y0ccIt8Sac>
Cc: ianaplan@ietf.org
Subject: Re: [Ianaplan] Process concern regarding the IETF proposal development process
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: Sat, 24 Jan 2015 22:22:19 -0000

On Jan 24, 2015, at 12:14 PM, Avri Doria <avri@acm.org>; wrote:
> ...
> I know that in the Names community work, gaining an understanding of the legal environment and the way of actually dealing with the legal points of appeals and possible future decisions to remove the function from ICANN  before the crisis point, is a gating concern and part of the reason are still working on developing our response - we need legal advice before we can complete our work.  But in that case there is no doubt that the legal aspects are in scope for the Cross community WG.
> 
> Perhaps once the Names community has completed its work, and I hope it is real soon, there will be some clue that can be used on legal arrangements and appeals mechanisms by the other communities, upon recommendation from the ICG.

Please explain the above…  it almost appears that you are suggesting 
that the ICG would make some form of recommendation with respect to 
various legal implementation aspects (e.g. arbitration rules and location)

> As for whether ICG experts should be expected to understand the intricacies of the arrangements supplied by the 3 communities, I am sure that each group having picked its finest, they are certainly capable of doing so,  And I beleive that as a group coordinating the puzzle of the partial responses from all communities they need to do so to figure out how to fit the 3 answers (once the have the 3) into a consistent response for NTIA.

The ICG needs to make sure that the integrated proposal meets the NTIA
criteria.   The ICG charter does not include any form of proposal development 
work; if there are problems with the component proposals, then the ICG is to 
communicate that back to the relevant communities so that the communities
can address the issues.  

This is particularly important when if comes to contractual matters, since it
might easily be the case the optimum structure for the IETF/IAB to contract
for IANA protocol parameter services might truly be different than the optimum 
structure for the RIR community to contract for IANA services for the various
central number registries, or the names community to contract, etc.  There is 
no requirement these contractual structures be the same, only that the specific 
arrangements do not preclude assembly of a single combined proposal.

/John

Disclaimer: my views alone.