ICANN/GNSO GNSO Email List Archives

[council]


<<< Chronological Index >>>    <<< Thread Index >>>

Re: [council] Draft Statement for Public Forum

  • To: Jonathan Robinson <jrobinson@xxxxxxxxxxxx>
  • Subject: Re: [council] Draft Statement for Public Forum
  • From: Wendy Seltzer <wendy@xxxxxxxxxxx>
  • Date: Wed, 10 Apr 2013 19:38:43 -0400
  • Cc: GNSO Council List <council@xxxxxxxxxxxxxx>
  • Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=s3dZluhbqni3VPpqYZusXMqho7SjoK84iv0UROsXzAI=; b=ljct3R3iArTorks+wHoy2rHKmyo6g0nVmLhmIGgsGQmAjijt0c49Bp0MzpGGCe58Qo LTxD2hqqXODGK+ZcktYEE0OmVTdjT0zj8Iobkx/57xu0EIUBYMXgQ8eJqdjIFJE6wv4C y7zAUxRBfJ94BsKEH2VjNehh7r+y5Omury0+kgoJZ0vVdkmb8d1hJgs9IP1AB3mCa4Mz dJ71dWcQ6AgFBKrIxTMW5Qxymd5Q/54oC40VodiQD+xJlBL1YgzzOnCHPOP6t7gWxtEb h/NNtxtvDDSDi3F1B8DdHdXchJ8AFwrDKEhiSrke4hkA38m9u71nPK1Qh7qlcH7oXw9K XOgg==
  • In-reply-to: <826B2C41-9377-4709-9254-38835DA2255A@5x5com.com>
  • List-id: council@xxxxxxxxxxxxxx
  • References: <CAJZFnPrz6Fy7YbjSQLkdgc_e-CZqP-0MR4vhnQTLVfy0ivetEQ@mail.gmail.com> <1C4C1D63EA1A814AA391AEFD88199A3E0103679627@STNTEXCH01.cis.neustar.com> <826B2C41-9377-4709-9254-38835DA2255A@5x5com.com>
  • Sender: owner-council@xxxxxxxxxxxxxx
  • User-agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130308 Thunderbird/17.0.4

Agree. Thanks Jonathan and Jeff.

--Wendy

On 04/10/2013 05:23 PM, Mason Cole wrote:
> This looks good to me. 
> 
> Sent from my iPhone
> 
> On Apr 10, 2013, at 11:19 PM, "Neuman, Jeff" <Jeff.Neuman@xxxxxxxxxx> wrote:
> 
>> Some revisions: 
>>  
>> The GNSO Council would like to remind the ICANN staff and Board that it is 
>> the only entity charged with policy development and providing 
>> recommendations to the Board on substantive policies relating to generic top 
>> level domains. The GNSO Council recently provided advice in response to a 
>> letter from the CEO to the effect that an issue being considered was a 
>> matter of policy, rather than implementation. It was Staff’s view that the 
>> issue was implementation and not policy, and accordingly it was the Staff’s 
>> decision to proceed with implementation of what the majority of the Council 
>> believed was policy. It is the Council’s firmly held view that when there is 
>> not an agreement on whether or not such an item is policy, as in this case, 
>> that the Staff and/or the ICANN Board must refer back to the Council before 
>> proceeding further.
>>
>> Indeed, as a general point, it is the Council’s view that should it provide 
>> policy advice to the Staff and/or the Board in the future, then in the event 
>> that Staff and/or Board seek to act in a manner that is not consistent with 
>> the Council’s advice, then the Staff and/or Board must consult with the GNSO 
>> Council, explain the rationale behind its decision, and allow the Council, 
>> at a minimum, to respond to the Staff or Board’s decision.
>>
>>  
>>
>>  
>> Jeffrey J. Neuman 
>> Neustar, Inc. / Vice President, Business Affairs
>>
>>  
>> From: owner-council@xxxxxxxxxxxxxx [mailto:owner-council@xxxxxxxxxxxxxx] On 
>> Behalf Of Jonathan Robinson
>> Sent: Wednesday, April 10, 2013 6:54 PM
>> To: GNSO Council List
>> Subject: [council] Draft Statement for Public Forum
>>  
>> Draft Statement for Public Forum:
>>
>> The GNSO Council recently provided advice in response to a letter from the 
>> CEO to the effect that an issue being considered was a matter of policy, 
>> rather than implementation. It was Staff’s view that the issue was 
>> implementation and not policy, and accordingly it was the Staff’s decision 
>> to proceed with the first steps of implementation. It is the Council’s 
>> firmly held view that when there is not an agreement on whether or not such 
>> an item is policy, as in this case, that the Staff must refer back to the 
>> Council before proceeding further.
>>
>> Indeed, as a general point, it is the Council’s view that should it provide 
>> policy advice to the Staff and/or the Board in the future, then in the event 
>> that Staff and/or Board seek to act adverse to the Council’s advice, they 
>> should certainly not do so without further reference back to the Council.
> 




<<< Chronological Index >>>    <<< Thread Index >>>