February 2012 - council - lists.icann.org

Draft Agenda GNSO Council meeting on 16 February 2012 at 15:00
by Glen de Saint Géry 08 Feb '12

08 Feb '12

Dear Councillors, Please find the draft agenda for the GNSO Council meeting on 16 February 2012 at 15:00 attached, below in text: and posted on the Wiki at: https://community.icann.org/display/gnsocouncilmeetings/Agenda+16+February+… Agenda for GNSO Council Meeting – 16 February 2012 This agenda was established according to the GNSO Council Operating Procedures approved 22 September 2011 for the GNSO Council and updated. http://gnso.icann.org/council/gnso-operating-procedures-16dec11-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 15:00 UTC<http://www.timeanddate.com/worldclock/fixedtime.html?msg=GNSO+Council+meeti…> Coordinated Universal Time: 15:00 UTC 07:00 Los Angeles; 10:00 Washington DC; 15:00 London; 16:00 Paris; 00:00 Tokyo; 17 February 2012 04:00 Wellington 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 Statement of interest updates 1.3 Review/amend agenda 1.4. Note the status of minutes for the previous Council meeting per the GNSO Operating Procedures: · 19 January 2012 GNSO Council minutes –approved on 16 February 2012. http://gnso.icann.org/mailing-lists/archives/council/msg12612.html 1.5. GNSO Pending Projects List http://gnso.icann.org/meetings/pending-projects-list.pdf · Review main changes. · Comments and/or questions. Item 2: Consent agenda (5 minutes) A consent agenda item is being added as a standard agenda item to provide for a simplified process to obtain Council approval on specific tasks. • Approval of the Recommendations Report on IRTP B Rec 9 part 2 that Staff is proposing be sent to the Board. Refer to the Recommendations Report: http://gnso.icann.org/drafts/gnso-council-report-irtp-part-b-recommendation… Item 3: 'thick' Whois Final Issue Report (10 minutes) As recommended by the IRTP Part B Working Group, the GNSO Council requested ICANN Staff to prepare an Issue Report on the requirement of ‘thick’ WHOIS for all incumbent gTLDs. The Preliminary Issue Report was published for public comment (see http://www.icann.org/en/announcements/announcement-2-21nov11-en.htm). Staff has now submitted the Final Issue Report,<http://gnso.icann.org/issues/whois/final-report-thick-whois-02feb12-en.pdf> which includes the report of comments received and additional updates as a result of the comments made. The GNSO Council will now consider the Final Issue Report<http://gnso.icann.org/issues/whois/final-report-thick-whois-02feb12-en.pdf> and decide whether or not to initiate a PDP. 3.1 Presentation of Final Issue Report<http://gnso.icann.org/issues/whois/final-report-thick-whois-02feb12-en.pdf> (Marika Konings) http://gnso.icann.org/issues/whois/final-report-thick-whois-02feb12-en.pdf Refer to motion: https://community.icann.org/display/gnsocouncilmeetings/Motions+16+February… 3.2 Reading of the motion (XY) 3.3 Discussion 3.3 Vote Item 4: IRTP B Rec 8 (15 minutes) As adopted by the Council on 22 June 2011 http://gnso.icann.org/resolutions#201106-1 the Council requested Staff to provide a proposal designed to ensure a technically feasible approach can be developed to meet the following recommendation "prior to the consideration of approval of the recommendation regarding the standardizing and clarifying WHOIS status messages regarding Registrar Lock status". Staff submitted its recommendation on January 3, 2012 http://gnso.icann.org/mailing-lists/archives/council/msg12545.html A motion was presented at the Jan 19, 2012 meeting, but was withdrawn to give Staff and Council more time to fine tune. A new motion is presented today. Refer to motion https://community.icann.org/display/gnsocouncilmeetings/Motions+16+February… 4.1 Reading of the motion (X Y). 4.2 Discussion 4.3 Vote Item 5: Cross Community Working Group Drafting Team (CCWG DT) (10 minutes) On January 4, 2012, the CCWG Drafting Team sent the Council Chair its final recommendations with regard to the GNSO's approach on Community Working Groups. Refer to: Draft Principles for Cross‐Community Working Groups (CWGs) http://gnso.icann.org/drafts/draft-principles-for-cwgs-23dec11-en.pdf Council must now consider whether to approve these recommendations. A motion to that effect was made at the Jan 19 meeting and deferred to this meeting. Refer to motion https://community.icann.org/display/gnsocouncilmeetings/Motions+16+February… 5.1 Reading of the motion (Jonathan Robinson). 5.2 Discussion 5.3 Vote Item 6: JIG letter to the Board (10 minutes) The ccNSO has not approved the joint letter the GNSO suggested sending to the Board on the JIG. As a way forward, the ccNSO is proposing two options: 1. Sending their proposed letter https://community.icann.org/display/gnsocouncilmeetings/Motions+16+February… as a joint letter to the Board. 2. If the GNSO does not approve option 1, the ccNSO will send a letter on its own. In that case, the GNSO must decide on what it wants to do, as we had approved sending a joint letter before http://gnso.icann.org/resolutions/#201112 6.1 Update by staff (X Y) 6.2 Discussion 6.3 Next steps Item 7: Costa Rica Weekend agenda (20 minutes) At the Jan 19 Council meeting, it was suggested that our weekend sessions need to be focussed more on preparation work for the Council's week and less on updates. This is a discussion item on the proposed agenda. 7.1 Update and presentation of agenda (Wolf Knoben Ulrich) 7.2 Agenda for GNSO Council meeting with the Board 7.3 Agenda for GNSO Council meeting with the GAC 7.4 Agenda for GNSO Council lunch with the ccNSO 7.5 Discussion Item 8: Red Cross and Olympic Committee names (20 minutes) A GNSO Drafting Team is working on a charter to determine how to handle the protection of RC and IOC names under the new gTLD program. This agenda item is to provide the Council with an update on that work. 8.1 Update by staff (X Y) 8.2 Discussion Item 9: GNSO liaison to the ccNSO (5 minutes) Olga Cavalli had served as GNSO Council liaison to the ccNSO, but has now left the GNSO Council. Therefore the GNSO Council must now appoint a new liaison to the ccNSO. 9.1 Call for volunteers 9.2 Discussion Item 10: Any Other Business (5 minutes) 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<http://gnso.icann.org/council/gnso-operating-procedures-22sep11-en.pdf>) 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 October & March, Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- Reference (Coordinated Universal Time) UTC 15:00 ---------------------------------------------------------------------------- California, USA (PST<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) UTC-8+0DST 07:00 New York/Washington DC, USA (EST) UTC-5+0DST 10:00 Buenos Aires, Argentina (ART<http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) UTC-3+0DST 12:00 Montevideo, Uruguay (UYST<http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) UTC-3+1DST 13:00 London, United Kingdom (BST) UTC+0DST 15:00 Abuja,Nigeria (WAT<http://www.timeanddate.com/library/abbreviations/timezones/africa/wat.html>) UTC+1+0DST 16:00 Tunis, Tunisia (CET) UTC+1+0DST 16:00 Bonn, Germany (CET) UTC+1+0DST 16:00 Paris, France (CET) UTC+1+0DST 16:00 Ramat Hasharon, Israel(IST<http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.…>) UTC+2+0DST 17:00 Karachi, Pakistan (PKT<http://www.timeanddate.com/library/abbreviations/timezones/asia/pkt.html> ) UTC+5+0DST 20:00 Beijing, China (CST<http://www.timeanddate.com/library/abbreviations/timezones/asia/cst.html> ) UTC+8+0DST 23:00 Tokyo, Japan (JST<http://www.timeanddate.com/library/abbreviations/timezones/asia/jst.html>) UTC+9+0DST 00:00 Wellington, New Zealand (NZDT<http://www.timeanddate.com/library/abbreviations/timezones/pacific/nzdt.html> ) UTC+12+1DST 04:00 next day ---------------------------------------------------------------------------- The DST starts/ends on last Sunday of March 2012, 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(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org

4 3

RE: [council] Re: [gnso-chairs] AW: [soac-discussion] SOPA Discussions
by john＠crediblecontext.com 08 Feb '12

08 Feb '12

3 2

RE: [council] Re: [gnso-chairs] AW: [soac-discussion] SOPA Discussions
by john＠crediblecontext.com 07 Feb '12

07 Feb '12

1 0

Draft Minutes GNSO Council meeting 19 January 2012
by Glen de Saint Géry 07 Feb '12

07 Feb '12

Dear Councillors, Please find the draft minutes of the GNSO Council meeting held on 19 January 2012. "If there are no comments, these minutes will be published on the website as approved, according to the GNSO Rules of Procedure http://gnso.icann.org/council/gnso-operating-procedures-22sep11-en.pdf section 3.5 "If no objections are received within 10 days, the minutes will be deemed to have been approved for posting." on 16 February 2012. " Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org

1 0

Fwd: [soac-discussion] ICANN 43 Public Forum Agenda Building
by Stéphane Van Gelder 07 Feb '12

07 Feb '12

Councillors, FYI and please pass on to your respective groups. Thanks, Stéphane Van Gelder Directeur Général / General manager INDOM Group NBT France ---------------- Head of Domain Operations Group NBT Début du message réexpédié : > De : Filiz Yilmaz <filiz.yilmaz(a)icann.org> > Objet : [soac-discussion] ICANN 43 Public Forum Agenda Building > Date : 6 février 2012 19:40:53 HNEC > À : "soac-discussion(a)icann.org" <soac-discussion(a)icann.org> > Cc : "steve.crocker(a)icann.org" <steve.crocker(a)icann.org> > > [Sent on behalf of Steve Crocker] > > > Dear ICANN Community Leaders, > > We are approaching ICANN 43 in Costa Rica, San José. > > As usual, we will have a Public Forum that will take place on Thursday, 15 March 2012, where Community members can make comments and ask questions to the Board and in front of the rest of the community. > > We believe building the agenda with your input facilitates this forum process and results in a productive session with the subjects that the Community thinks are important to talk about.This has been the practice in the recent meetings and we would like to repeat it again for Costa Rica. > > We believe publishing the agenda as early as possible facilitates more informed discussions during the Public Forum as we have experienced in Dakar, allowing the Community ample time to be aware of the agenda topics before the meeting actually starts. > > Please let Filiz Yilmaz (filiz.yilmaz(a)icann.org) know of one or two suggested topics that your groups would like to see included in the Public Forum agenda in Costa Rica, before the end of Friday, 2 March 2012. > > We will then review the suggestions, accommodate them as much as possible, combine common or related topics under one agenda topic and publish the agenda for the Public Forum after my approval. > > Thanks for your consideration and input. > > Kind regards, > Steve Crocker

1 0

RE: [council] Recommendations Report to the Board - IRTP Part B Recommendation #9 part 2
by john＠crediblecontext.com 07 Feb '12

07 Feb '12

2 1

Recommendations Report to the Board - IRTP Part B Recommendation #9 part 2
by Marika Konings 06 Feb '12

06 Feb '12

Dear All, Per the new GNSO Policy Development Process, the GNSO Council needs to approve the Recommendations Report to the Board (which has replaced the Council Report to the Board in the old PDP) before it is submitted to the ICANN Board for its consideration. Following the adoption of IRTP Part B Recommendation #9 part 2 and the ICANN Staff proposal, we have prepared the attached Recommendations Report for your consideration. Please note that this report does not contain any new information, but aims to provide an overview of all the relevant information in order for the Board to take an informed decision. As the new PDP does not prescribe how such a Recommendations Report should be structured, we would also like to take this opportunity to ask your input on the elements the Recommendations Report should contain so this can be turned into a template which can be used for future Recommendations Reports. For your information, you will find the relevant section of the PDP Manual relating to the Recommendations Report below. With best regards, Marika =================== >From the PDP Manual 13. Preparation of the Board Report If the PDP Recommendations contained in the Final Report are approved by the GNSO Council, the GNSO Council may designate a person or group responsible for drafting a Recommendations Report to the Board. If feasible, the Recommendations Report to the Board should be submitted to the Board in time for consideration at the next GNSO Council meeting following adoption of the Final Report. Staff should inform the GNSO Council from time to time of the format requested by the Board. These GNSO Council Reports supplement any Staff Reports that may highlight any legal, implementability, financial, and other operational concerns related to the PDP recommendations contained in the Final Report. In order to enhance ICANN’s accountability and transparency, Staff is encouraged to publish its Staff Reports with minimal redactions wherever possible, without jeopardizing information that may be protected under attorney/client or other legal privileges.

2 2

Motion to initiate a PDP on thick Whois
by Stéphane Van Gelder 04 Feb '12

04 Feb '12

Councillors, Please find attached a motion on thick whois that I wish to make. Please note that, although I have discussed with the registrars before making the motion, I am making it in my capacity as Chair of the GNSO Council in order to make sure work that has been undertaken in this area continues to move forwards. The motion simply follows the staff recommendation outlined in the issue report. I would ask all of you to take this motion back to your respective groups and confer with them prior to our next meeting. This motions suggests the initiation of a new PDP, so it should not be taken lightly. Thanks, Stéphane

1 0

Pre-Costa Rica ICANN Policy Update Webinar Invitation
by Glen de Saint Géry 03 Feb '12

03 Feb '12

http://www.icann.org/en/announcements/announcement-03feb12-en.htm Pre-Costa Rica ICANN Policy Update Webinar Invitation 3 February 2012 In order to participate, please RSVP via email to the GNSO Secretariat (gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org>) to receive the call details. Whether you plan to participate in the upcoming ICANN meeting in Costa Rica remotely or in person, you're invited to a quick reminder of the background and current status of each major policy issue currently under discussion in ICANN. The ICANN Policy Staff will provide a briefing on Thursday 1 March at 13.00 UTC and Thursday 1 March at 20.00 UTC, summarizing policy issues across the different ICANN Supporting Organizations, namely the Generic Names Supporting Organization (GNSO), Country Code Names Supporting Organization (ccNSO) and Address Supporting Organization (ASO). Amongst other topics, updates will be provided on: * Inter-Registrar Transfer Policy * RAA Improvements * Consumer Choice, Competition and Innovation * Study Group on Use of Names for Countries and Territories * Framework of Interpretation Working Group for the delegation and re-delegation of ccTLDs * Joint DNS Security and Stability Analysis Working Group * Participation and Engagement activities in Costa Rica The two sessions are duplicates, scheduled to accommodate different time zones. Each session, scheduled to run for 90 minutes, will be conducted in English only. The meeting will be run in Adobe Connect with a slide presentation along with a dial-in conference bridge for audio. Participants will have the opportunity to ask questions at the end of each session. During the course of the webinar, questions may be submitted using the chat function of Adobe Connect. If you are not able to participate in either of the live sessions, the recording of the session will be made available shortly after the meeting. The policy staff is always available to answer any questions that you email to policy-staff(a)icann.org<mailto:policy-staff@icann.org>. In order to participate, please RSVP via email to the GNSO Secretariat (gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org>) to receive the call details. Please indicate which call you would like to join, Thursday at 13.00 UTC or Thursday at 20.00 UTC (to convert those times into your local time, see: http://www.timeanddate.com/worldclock/fixedform.html). We will send you an e-mail reminder before the event with log-in and dial-in details. Please DO NOT RSVP to any other ICANN staff members e-mail address. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org

1 0

Fwd: SSAC Advisory on Delegation of Single-Character Internationalized Domain Name Top-Level Domains
by Ching Chiao 02 Feb '12

02 Feb '12

FYI http://www.icann.org/en/committees/security/sac052.pdf The SSAC makes two recommendations: 1. Given the potential for user confusion and the currently unfinished work on string similarity and IDN variants, the SSAC recommends a very conservative approach to the delegation of single-character IDN top-level domains. In particular, ICANN should disallow by default the delegation of all single-character IDN TLDs in all scripts; exceptions are possible, but only after careful consideration of each individual case. 2. Because important relevant work on string similarity, IDN variant issues, and TLD label syntax is currently underway within ICANN, the Internet Engineering Task Force (IETF), and other bodies, ICANN should review the Findings of this report, and any policies that it adopts in response to recommendations made in this document, no later than one year after the three work items mentioned above have been completed. -- Ching CHIAO Vice President, DotAsia Organisation LTD. Chair, Asia Pacific Networking Group Member of ICANN GNSO Council & RySG ===================================== Email: chiao(a)registry.asia Skype: chiao_rw Mobile: +886-918211372 | +86-13520187032 www.registry.asia | www.apngcamp.asia www.facebook.com/ching.chiao

1 0