ICANN/GNSO GNSO Email List Archives

[council]


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

Re: [council] Agenda for GNSO Council Meeting 21 July 2011.


I think this is being worked on Tim. It will appear in due course...

Stéphane



Le 12 juil. 2011 à 14:52, Tim Ruiz a écrit :

> The only motion that shows up on the motion page is the IRTP-B motion on
> thick whois:
> https://community.icann.org/display/gnsocouncilmeetings/Motions+2011-07-21
> 
> Tim
> 
> > -------- Original Message --------
> > Subject: [council] Agenda for GNSO Council Meeting 21 July 2011.
> > From: Glen de Saint Géry
> > Date: Mon, July 11, 2011 5:50 pm
> > To: Council GNSO 
> > 
> > Dear Councillors,
> >  
> > Please find the proposed draft agenda for the Council meeting on 
> > Thursday,21 July 2011.
> > 
> > Wiki reference for the latest updates:
> > https://community.icann.org/display/gnsocouncilmeetings/GNSO+Council+Meeting+2011-07-21
> > 
> > Please let me know if you have any questions.
> > Thank you.
> > Kind regards,
> >  
> > Glen
> > 
> > Agenda for GNSO Council Meeting 21 July 2011.
> > http://gnso.icann.org/meetings/agenda-council-21jul11-en.htm
> > 
> > This agenda was established according to the GNSO Council Operating 
> > Procedures approved 7 April 2011 for the GNSO Council.
> > http://gnso.icann.org/council/gnso-op-procedures-08apr11-en.pdf
> > For convenience:
> > * An excerpt of the ICANN Bylaws defining the voting thresholds is provided 
> > in Appendix 1 at the end of this agenda.
> > * An excerpt from the Council Operating Procedures defining the absentee 
> > voting procedures is provided in Appendix 2 at the end of this agenda.
> > Meeting Time 11:00 UTC
> > 
> > Coordinated Universal Time:11:00 UTC - see below for local times
> > (04:00 Los Angeles, 07:00 Washington DC, 12:00 London, 13:00 Brussels, 
> > 20:00 Tokyo; 21:00 Melbourne 
> > 
> > Dial-in numbers will be sent individually to Council members. Councilors 
> > should notify the GNSO Secretariat in advance if a dial out call is needed.
> > 
> > GNSO Council meeting audiocast 
> > http://stream.icann.org:8000/gnso.m3u
> > Item 1: Administrative matters (10 minutes)
> > 
> > 1.1 Roll Call 
> > 
> > 1.2 Updated statement of interest 
> > Rosemary Sinclair
> > http://gnso.icann.org/council/soi/sinclair-soi-22jun11.htm
> > 
> > 1.3 Review/amend agenda
> > 
> > 1.4. Note the status of minutes for the previous Council meeting per the 
> > GNSO Operating Procedures:
> > � 22 June 2011 Council minutes � approved on 6 July 2011.
> > http://gnso.icann.org/meetings/minutes-council-22jun11-en.htm
> > 
> > Item 2: Pending Projects � Inter-Registrar Transfer Policy Part B Working 
> > Group (10 minutes)
> > Standard agenda item to update the Council on the GNSO's Pending Projects.
> > Refer to Pending Projects list 
> > http://gnso.icann.org/meetings/pending-projects-list.pdf
> > This item to discuss the implementation of the resolutions passed by the 
> > GNSO Council at its June 22 meeting in Singapore and in particular action 
> > items arising from Resolved D, Resolved E and Resolved G.
> > Refer to June 22 motion: 
> > https://community.icann.org/display/gnsocouncilmeetings/Motions+22+June+2011
> > 2.1 Update from Staff (Marika Konings).
> > 2. 2 Discussion/Questions
> > 
> > 2. 3 Next steps?
> > 
> > 2.4 Reading of motion to address IRTP Part B recommendation #3 (XXXXX)
> > 
> > 2.5 Discussion
> > 
> > 2.6 Vote
> > 
> > 2.7 Changes to Pending Projects List since last Council meeting (Stéphane 
> > Van Gelder)
> > 
> > 
> > � GNSO activities: 10 (9 � Open Council Meeting DT added).
> > � Other activities: 9 (7 � GNSO toolkit of services removed, IRTP B rec 
> > 8, IRTP B rec 9 and IRTP C issues report added).
> > � Joint SO/AC WGs: 7 (7 � no change).
> > � Outstanding recommendations: 2 (1 � IRTP B remaining recs added).
> > 
> > 
> > Item 3: Joint ccNSO-GNSO Internationalized Domain Names Working Group (JIG) 
> > (10 minutes)
> > 
> > Action item from the Singapore ICANN meeting: the JIG's current charter 
> > does not allow it to continue working, yet the JIG reported to the GNSO 
> > Council in Singapore that it still has some work to do.
> > 
> > A motion is being submitted to extend the JIG's charter 
> > https://community.icann.org/display/gnsocouncilmeetings/Motions+2011-07-21
> > 3.1 Reading of the motion (XXXXXXX)
> > 3.2 Discussion
> > 3.3 Vote
> > Item 4: June 20 Board resolution on new gTLDs (15 minutes)
> > 
> > As part of its resolutions on the new gTLD program, the ICANN Board passed 
> > a resolved clause during its June 20 meeting in Singapore which contained 
> > the following excerpt (Resolved 1.b):
> > 
> > Incorporation of text concerning protection for specific requested Red 
> > Cross and IOC names for the top level only during the initial application 
> > round, until the GNSO and GAC develop policy advice based on the global 
> > public interest.
> > 
> > As an action item, the GNSO therefore needs to look at providing the 
> > requested advice or at least consider whether it wants to provide advice 
> > and if so, how should these entities' names be handled at the second level 
> > in new gTLDs?
> > Refer to Board June 20 2011 motion on new gTLDs: 
> > http://www.icann.org/en/minutes/resolutions-20jun11-en.htm
> > 4.1 Discussion
> > 4.2 Next steps
> > Item 5: Joint SO/AC WG on New gTLD Applicant Support (JAS) (15 minutes)
> > 
> > As part of its resolutions on the new gTLD program, the ICANN Board passed 
> > a resolved clause during its June 20 meeting in Singapore which contained 
> > the following excerpt (Resolved 4.d):
> > 
> > The review of additional community feedback, advice from ALAC, and 
> > recommendations from the GNSO following their receipt of a Final Report 
> > from the JAS Working Group (requested in time to allow staff to develop an 
> > implementation plan for the Board�s consideration at its October 2011 
> > meeting in Dakar, Senegal), with the goal of having a sustainable applicant 
> > support system in place before the opening of the application window.
> > 
> > At its Singapore wrap-up meeting, the GNSO Council identified the following 
> > timeline if the Board request is to be answered in time: For the Board to 
> > approve the JAS implementation plan in Dakar on October 28, the Staff must 
> > publish all documents for the Dakar meeting 15 business days before Dakar, 
> > so October 7. So that means the Council must approve the JAS Final Report 
> > at its September 8 meeting.
> > 
> > This discussion item aims at identifying how these objectives can best be 
> > met.
> > Refer to Board June 20 2011 motion on new gTLDs: 
> > http://www.icann.org/en/minutes/resolutions-20jun11-en.htm
> > 5.1 Discussion
> > 5.2 Next steps
> > Item 6: Interaction with ccNSO (15 minutes)
> > Action item from the Singapore ICANN meeting: the ccNSO and the GNSO agreed 
> > to try and work together more closely on some projects of common interest. 
> > Two were discussed: the work the ccNSO is currently doing on ICANN's 
> > strategic plan and budget, and the work the GNSO is currently doing on CWGs.
> > This is a discussion item to ascertain how to push these two initiatives 
> > forward.
> > 6.1 Discussion
> > 6.2 Next steps
> > Item 7: Post-Expiration Domain Name Recovery (PEDNR) (15 minutes)
> > The group has sent its Final Report for the GNSO Council's consideration on 
> > June 14, 2011 
> > http://gnso.icann.org/issues/pednr-final-report-14jun11-en.pdf
> > 
> > A motion has been made to approve this report.
> > 
> > Refer to motion 
> > https://community.icann.org/display/gnsocouncilmeetings/Motions+2011-07-21
> > 7.1 Reading of the motion (XXXXX)
> > 7.2 Discussion
> > 7.3 Vote
> > Item 8: Policy Development Process Work Team (PDP-WT) (10 minutes)
> > The group has put its proposed Final Report out for public comment 
> > http://gnso.icann.org/issues/pdp-wt-final-report-final-31may11-en.pdf
> > 
> > A public comment period closed on July 9.
> > Summary of public comments 
> > http://forum.icann.org/lists/pdp-final-report/msg00004.html 
> > 
> > A motion has been made for the Council to consider this report.
> > 
> > Refer to motion 
> > https://community.icann.org/display/gnsocouncilmeetings/Motions+2011-07-21
> > 8.1 Reading of the motion (Jeff Neuman)
> > 8.2 Discussion
> > 8.3 Vote
> > Item 9: Registration abuse (RAP) (15 minutes)
> > Following recent discussions on the matter, the Council is being asked to 
> > consider a motion to address the remaining recommendations of the RAP WG.
> > This motion is being presented for discussion only at this meeting, in 
> > order to give the Council and its SGs sufficient time to properly assess 
> > it. 
> > 
> > Refer to motion 
> > https://community.icann.org/display/gnsocouncilmeetings/Motions+2011-07-21
> > 9.1 Reading of the motion (XXXXXX)
> > 9.2 Discussion
> > Item 10. Any Other Business (5 minutes) 
> > 10.1 Possibility of a special meeting of the Council in August (first week 
> > of the month) on the JAS final report.
> > 
> > Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article X, 
> > Section 3)
> > 
> > 9. Except as otherwise specified in these Bylaws, Annex A hereto, or the 
> > GNSO Operating Procedures, the default threshold to pass a GNSO Council 
> > motion or other voting action requires a simple majority vote of each 
> > House. The voting thresholds described below shall apply to the following 
> > GNSO actions:
> > 1. Create an Issues Report: requires an affirmative vote of more than 25% 
> > vote of each House or majority of one House;
> > 2. Initiate a Policy Development Process (�PDP�) Within Scope (as 
> > described in Annex A): requires an affirmative vote of more than 33% of 
> > each House or more than 66% of one House;
> > 3. Initiate a PDP Not Within Scope: requires an affirmative vote of more 
> > than 75% of one House and a majority of the other House (�GNSO 
> > Supermajority�);
> > 4. Approve a PDP Recommendation Without a GNSO Supermajority: requires an 
> > affirmative vote of a majority of each House and further requires that one 
> > GNSO Council member representative of at least 3 of the 4 Stakeholder 
> > Groups supports the Recommendation;
> > 5. Approve a PDP Recommendation With a GNSO Supermajority: requires an 
> > affirmative vote of a GNSO Supermajority; and
> > 6. Approve a PDP Recommendation Imposing New Obligations on Certain 
> > Contracting Parties: where an ICANN contract provision specifies that �a 
> > two-thirds vote of the council� demonstrates the presence of a consensus, 
> > the GNSO Supermajority vote threshold will have to be met or exceeded with 
> > respect to any contracting party affected by such contract provision.
> > 
> > Appendix 2: Absentee Voting Procedures (GNSO Operating Procedures 4.4)
> > 4.4.1 Applicability
> > Absentee voting is permitted for the following limited number of Council 
> > motions or measures.
> > a. Initiate a Policy Development Process (PDP);
> > b. Approve a PDP recommendation;
> > c. Recommend amendments to the GNSO Operating Procedures (GOP) or ICANN 
> > Bylaws;
> > d. Fill a Council position open for election.
> > 4.4.2 Absentee ballots, when permitted, must be submitted within the 
> > announced time limit, which shall be 72 hours from the meeting�s 
> > adjournment. In exceptional circumstances,announced at the time of the 
> > vote, the Chair may reduce this time to 24 hours or extend the time to 7 
> > calendar days, provided such amendment is verbally confirmed by all 
> > Vice-Chairs present.
> > 4.4.3 The GNSO Secretariat will administer, record, and tabulate absentee 
> > votes according to these procedures and will provide reasonable means for 
> > transmitting and authenticating absentee ballots, which could include 
> > voting by telephone, e- mail, web-based interface, or other technologies as 
> > may become available.
> > 4.4.4 Absentee balloting does not affect quorum requirements. (There must 
> > be a quorum for the meeting in which the vote is initiated.
> > Local time between March & October, Summer in the NORTHERN hemisphere 
> > ----------------------------------------------------------------------------
> >  
> > Reference (Coordinated Universal Time) UTC 11:00 
> > ----------------------------------------------------------------------------
> > California, USA (PDT) UTC-7+1DST 04:00 
> > Cedar Rapids, USA (CDT) UTC-5+1DST 06:00 
> > New York/Washington DC, USA (EDT) UTC-5+1DST 07:00
> > Buenos Aires, Argentina UTC-3+0DST 08:00 
> > Rio de Janeiro/Sao Paulo Brazil UTC-3+0DST 08:00 
> > London, United Kingdom (BST) UTC+1DST 12:00 
> > Tunis, Tunisia (CET)UTC+1+0DST 12:00 
> > Darmstadt, Germany (CET) UTC+1+1DST 13:00 
> > Paris, France (CET) UTC+1+1DST 13:00 
> > Moscow, Russian Federation UTC+3+1DST 15:00 
> > Karachi, Pakistan UTC+5+0DST 16:00 
> > Beijing, China UTC+8+0DST 19:00
> > Tokyo, Japan UTC+9+0DST 20:00 
> > Melbourne,/Sydney Australia (EST) UTC+10+0DST 21:00 
> > ----------------------------------------------------------------------------
> >  
> > The DST starts/ends on last Sunday of October 2011, 2:00 or 3:00 local time 
> > (with exceptions)
> > ---------------------------------------------------------------------- 
> > For other places see http://www.timeanddate.com
> >   
> >  
> >  
> >  
> > Glen de Saint Géry
> > GNSO Secretariat
> > gnso.secretariat@xxxxxxxxxxxxxx
> > http://gnso.icann.org
> >  
> >  
> > 
> > 
> 





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