[registrars] WG: [council] GNSO Council resolutions 20 November 2007

[Ross Rader]

Happy to help. Glad to see this move forward.

---
Warm regards,

-Ross





Sent from my iPhone



On Nov 21, 2007, at 10:58 AM, Tim Ruiz <tim at godaddy.com> wrote:

>
> So Resolution 2 has intiated a PDP on the reasons for denial of
> transfers. Since it was decided to do it without a Task Force (as was
> the case with the Tasting PDP), we once again need to appoint a
> representative (this is not a task force rep) to solicit RC views and
> draft a statement.
>
> The appointment is supposed to be done within 10 calendar days, and  
> the
> statement submitted within 35 calendar days of the initiation of the  
> PDP
> on 20 Nov. Of course, once again, there is no way to hold an election
> for a representative within 10 days.
>
> I propose that based on 4.1, 4.1.1. and 4.1.4. of our bylaws (quoted
> below) that the ExCom request that any members interested in  
> performing
> this function let them know and then the ExCom would discuss and  
> make an
> appointment. It will still be a tight fit to solicit views, create a
> statement, and get it submitted within the 35 days even if it is fast
> tracked. But it we hold an election first, we will be at least a month
> late if not more.
>
> 4.1. The Executive Committee may divide its duties and  
> responsibilities
> among the Members as it sees fit and conduct its business as it finds
> necessary. Responsibilities of the Executive Committee shall include:
>
> 4.1.1. Coordinators; Sub-Committees. The Executive Committee may  
> appoint
> "Coordinators" charged with functional supervision of activities  
> such as
> membership.
>
> 4.1.4. Policy Recommendations. The Executive Committee shall be  
> charged
> with broadly considering Constituency policies and making appropriate
> recommendations to the Members.
>
>
> Tim
>
>
> -------- Original Message --------
> Subject: [registrars] WG: [council] GNSO Council resolutions 20
> November 2007
> From: "Thomas Keller" <tom at 1und1.de>
> Date: Wed, November 21, 2007 8:16 am
> To: <registrars at gnso.icann.org>
>
>
>
> fyi, the outcome of yesterdays council call.
>
> Best,
>
> tom
>
> -----Ursprüngliche Nachricht-----
> Von: owner-council at gnso.icann.org [mailto:owner- 
> council at gnso.icann.org]
> Im
> Auftrag von GNSO.SECRETARIAT at GNSO.ICANN.ORG
> Gesendet: Mittwoch, 21. November 2007 15:13
> An: 'Council GNSO'
> Betreff: [council] GNSO Council resolutions 20 November 2007
>
>
> Dear Council Members,
>
> Ahead of the complete minutes, please find the resolutions that were
> passed
> by the GNSO Council teleconference on Tuesday 20 November 2007.
>
> Please let me know if you have any questions.
>
> Thank you.
> Kind regards,
>
> Glen
> ... 
> ... 
> ... 
> ....................................................................
> Resolution 1
>
> Whereas, the Council has previously requested and received both the 15
> June
> 2007 "GNSO Issues Report on Dispute Handling for IGO Names and
> Abbreviations"
> http://www.gnso.icann.org/issues/igo-names/issues-report-igo-drp-15jun07.pdf
> and the 28 September 2007 "Staff Report on Draft IGO Domain Name  
> Dispute
> Resolution Procedure;"
> http://gnso.icann.org/drafts/gnso-igo-drp-report-v2-28sep07.pdf
>
> and
>
> Whereas, the Council believes that further work on the draft IGO  
> Domain
> Name
> Dispute Resolution Procedure is appropriate before voting on whether  
> to
> initiate a policy development process on this issue; and
>
> Whereas, the Intellectual Property Constituency is drafting and  
> expects
> to
> distribute not later than 28 November a revised proposed draft dispute
> resolution procedure,
>
> Now, therefore, be it resolved that the Council postpones until its 20
> December meeting the vote on whether to initiate a policy development
> process.
>
> Resolution 2
>
> Whereas the issues report on Inter-Registrar Transfers
> http://gnso.icann.org/issues/transfers/issues-report-transfer-denial-clarifi
> cations-19oct07.pdf
>
> has been released and discussed
>
> The GNSO council resolves to initiate a PDP to address the issues set
> forth
> in the Issues Report by the Staff.
>
> Resolution 3 failed
>
> Whereas the Council has decided to initiate a PDP on Inter-registrar
> Transfers, a Task Force will be created according to the By-laws,
> section 5
> of Annex A of the GNSO Policy Development Process.
>
> Thus
>
> Pursuant to the ICANN Bylaws
> http://www.icann.org/general/bylaws.htm#AnnexA-8
> 8. Procedure if No Task Force is Formed
>
> a. If the Council decides not to convene a task force, the Council  
> will
> request that, within ten (10) calendar days thereafter, each
> constituency
> appoint a representative to solicit the constituency's views on the
> issue.
> Each such representative shall be asked to submit a Constituency
> Statement
> to the Staff Manager within thirty-five (35) calendar days after
> initiation
> of the PDP.
>
> b. The Council may also pursue other options that it deems appropriate
> to assist in the PDP, including appointing a particular individual or
> organization to gather information on the issue or scheduling meetings
> for
> deliberation or briefing. All such information shall be submitted to  
> the
> Staff Manager within thirty-five (35) calendar days after initiation  
> of
> the
> PDP.
>
> c. The Staff Manager will take all Constituency Statements, Public
> Comment Statements, and other information and compile (and post on the
> Comment Site) an Initial Report within fifty (50) calendar days after
> initiation of the PDP. Thereafter, the PDP shall follow the provisions
> of
> Item 9 below in creating a Final Report.
>
> --
> Glen de Saint Géry
> GNSO Secretariat - ICANN
> gnso.secretariat[at]gnso.icann.org
> http://gnso.icann.org
>
>
>
>
>
>