Re: [Ianaplan] control and negotiation (was Re: draft-ietf-ianaplan-icg-response-02 working group last call)

Alissa Cooper <alissa@cooperw.in> Fri, 07 November 2014 22:47 UTC

Return-Path: <alissa@cooperw.in>
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 85CD71A1A56 for <ianaplan@ietfa.amsl.com>; Fri, 7 Nov 2014 14:47:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 K9y9tLMUgFo7 for <ianaplan@ietfa.amsl.com>; Fri, 7 Nov 2014 14:47:20 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9762B1A1A1F for <ianaplan@ietf.org>; Fri, 7 Nov 2014 14:47:19 -0800 (PST)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 00E462099B for <ianaplan@ietf.org>; Fri, 7 Nov 2014 17:47:18 -0500 (EST)
Received: from frontend2 ([10.202.2.161]) by compute5.internal (MEProxy); Fri, 07 Nov 2014 17:47:19 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h= x-sasl-enc:content-type:mime-version:subject:from:in-reply-to :date:cc:message-id:references:to; s=mesmtp; bh=bQzmsv5SGi9cM4yW qFD3xRjbgsg=; b=q9XXKmw2djD3rpHQtDeQ+TfhB2OMB21VzvnwOCx4wTfDkXN9 F9Q+++ExXQ+ajpR+7e51EWz68lzr4RVOfvWOen5gG3LKTkqSKDNIh7SVeKbMDcqy RJYMWzayOFUm22gR8yjDB4w+jfAg+sZredKzcktKBVctm3nhVgUAVTUqujk=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=x-sasl-enc:content-type:mime-version :subject:from:in-reply-to:date:cc:message-id:references:to; s= smtpout; bh=bQzmsv5SGi9cM4yWqFD3xRjbgsg=; b=j5Lhl8VA1j6Vrpp4MSGZ nBbXwEOc8lm6pwrB1DpM4bSUY4LULSRPiwwxK7Wn5HZ11AXvQtwWZQxbOZs2f4jG JFCuNzo/HcLGBKJeHdEJC0ZIz/mq+Y+Ylv7xTJQOweqbe9l8rBnNVQmHzTyYkKdS W/CWRT4NJbKBA+RDrp/iQAg=
X-Sasl-enc: QCWEldLTEXpsemo0K0NiAfSN5hGUEunkISTaO/COg0/O 1415400438
Received: from [10.35.132.83] (unknown [128.107.239.236]) by mail.messagingengine.com (Postfix) with ESMTPA id 43328680106; Fri, 7 Nov 2014 17:47:18 -0500 (EST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_AAC5663A-33EC-4720-9FB3-A6590466DF49"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <89E194B2-726A-440F-814D-8BC91D8C82D3@virtualized.org>
Date: Fri, 07 Nov 2014 14:47:17 -0800
Message-Id: <AB1FBE7C-73E1-4CA4-BE6D-64A67935B10F@cooperw.in>
References: <54594A50.4090305@meetinghouse.net> <20141105001731.GA30186@mx1.yitter.info> <54597BDB.7040305@meetinghouse.net> <5459BA98.1070006@gmail.com> <545A208A.7040304@meetinghouse.net> <631e3e3d29c843bd9c23151c63612989@EX13-MBX-13.ad.syr.edu> <20141105154903.GI30379@mx1.yitter.info> <498a39b81b774192bd2d609b3feab35f@EX13-MBX-13.ad.syr.edu> <20141105234444.GM31320@crankycanuck.ca> <0d10ba336c984561a1a5d6d81db5f26c@EX13-MBX-13.ad.syr.edu> <20141106144333.GA33081@mx1.yitter.info> <6e19bf2618a54b27bb1b859842e98144@EX13-MBX-13.ad.syr.edu> <89E194B2-726A-440F-814D-8BC91D8C82D3@virtualized.org>
To: David Conrad <drc@virtualized.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/aZVVmyK-I9gtN5v4RAZU4Ph6Lfc
Cc: Milton L Mueller <mueller@syr.edu>, "ianaplan@ietf.org" <ianaplan@ietf.org>
Subject: Re: [Ianaplan] control and negotiation (was Re: draft-ietf-ianaplan-icg-response-02 working group last call)
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, 07 Nov 2014 22:47:32 -0000

Hi David,

On Nov 7, 2014, at 12:55 PM, David Conrad <drc@virtualized.org> wrote:

> Milton,
> 
> On Nov 6, 2014, at 6:37 AM, Milton L Mueller <mueller@syr.edu> wrote:
>> It is completely invalid to call a final ICG proposal that was developed by the entire community, is endorsed consensually by all 3 operational communities, has survived one or more public comment periods, and is accepted by the NTIA  - as a kind of extortion, especially when ICANN itself was fully represented in the development of the proposal and had the ability to publicly comment on it. 
> 
> I was told ICANN staff on the ICG are forbidden to speak unless in response to a question.  Was I told incorrectly?

I think you’re confusing several different roles here:

* There is an ICANN staff member (Elise) who is an appointed liaison to the ICG. She and the ICANN Board liaison (Kuo Wei) participate in all ICG deliberations other than consensus calls on substantive matters. https://www.icann.org/en/system/files/files/icg-guidelines-decision-making-17sep14-en.pdf

* The ICG is currently supported by an ICANN staff secretariat. Their roles are not specified anywhere specifically but they are quite proactive in terms of getting their secretarial duties done (e.g., posting things to the appropriate web sites). They don’t participate in substantive discussions, but then I don’t think anyone would expect them to.

* There is an ICANN staff member (Theresa Swinehart) who attends the ICG meetings and is subscribed to the ICG mailing list. In terms of the ICG’s own deliberations, perhaps this is what you were referring to, as Theresa is available to answer ICANN-specific questions or to coordinate things with other parts of the ICANN staff. But she does not proactively participate in the ICG’s own deliberations, in the same way that no other non-ICG members participate.

* As far as the operational community processes, the ICG is encouraging everyone to participate as much as they want. This is reflected in the ICG charter <https://www.icann.org/en/system/files/files/charter-icg-27aug14-en.pdf> and in the RFP itself <https://www.icann.org/en/system/files/files/rfp-iana-stewardship-08sep14-en.pdf>. That participation includes ICANN staff, and I’m sure you’ve seen how active the staff have been in the CWG-IANA concerning naming resources. The ICG is working on a specific statement to encourage participation from ICANN staff and board members in the community processes if they are so inclined <http://mm.icann.org/pipermail/internal-cg/2014-October/002162.html>, but this statement was motivated more by concerns regarding the board than the staff, and the generic statements made in the charter and RFP of course extend to anyone who wants to participate.

Best,
Alissa

> 
> Thanks,
> -drc
> (ICANN CTO, but speaking only for myself. Really.)
> 
> _______________________________________________
> Ianaplan mailing list
> Ianaplan@ietf.org
> https://www.ietf.org/mailman/listinfo/ianaplan