May 2012 - council - lists.icann.org

Prague - please read!
by Stéphane Van Gelder 23 Jun '12

23 Jun '12

Councillors, I would like to strongly request your help in coming up with two things in preparation for our Prague week: 1. Topics for our interactions with the Board/GAC and ccNSO and 2. Ideas for sessions for our work weekend. As added context, I should say that the Council leadership is under greater pressure than usual to provide this earlier than usual (Staff have been put under pressure due to the delay in publishing the CR agenda that people complained about there). I should also add that I have asked Jeff, who has kindly volunteered (or was kindly volunteered by me, whichever way you want to see it ;) ) to look after our Prague agenda, to ensure that we cut down on pure working lunch sessions. I find these sessions are an organizational nightmare as people need time to have their lunch, which cost down on the time afforded to the topic we are scheduled to work on. So in short, please make a greater effort than usual to provide ideas for 1 and 2 above. These sessions, both our interactions with other groups and our own working sessions, should be the result of Council-wide deliberations so that they are truly effective and have greater meaning for the Council as a whole. Thanks for your help in this endeavor. Stéphane Van Gelder Directeur Général / General manager INDOM Group NBT France ---------------- Head of Domain Operations Group NBT

7 9

Motion
by KnobenW＠telekom.de 07 Jun '12

07 Jun '12

On behalf of the ISPCP constituency I'd like to introduce the motion attached to the 07 June council meeting. Mit freundlichen Grüßen Best regards Wolf-Ulrich

5 5

Action points from May 10 meeting
by Stéphane Van Gelder 05 Jun '12

05 Jun '12

Councillors, We have a few action points from our last meeting that I'd like to remind us all of. On ALAC's Icann academy, I had an action to inform the ALAC CHair that I would be joining the group. That has been done. I also had an action to draft some general guideline points that the Council would feel comfortable with me portraying to the group as a GNSO position. That has been done. On the decision to cancel Fridays at Icann meetings, Wendy had an action point to draft an initial message for me to send to the Board on behalf of the GNSO. On the URS in the draft budget, Wendy had an action point to draft an initial message for me to send to the Board on behalf of the GNSO. On the IOC/RC, we have yet to determine a common Council position. Thanks, Stéphane Van Gelder Directeur Général / General manager INDOM Group NBT France ---------------- Head of Domain Operations Group NBT

3 5

Draft GNSO Council Agenda 7 June 2012
by Glen de Saint Géry 31 May '12

31 May '12

Dear All, Please find the draft agenda for the GNSO Council Meeting 7 June 2012 which is also posted on the Wiki at: https://community.icann.org/display/gnsocouncilmeetings/Agenda+07+June+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 Times 20:00 UTC<http://www.timeanddate.com/worldclock/fixedtime.html?msg=GNSO+Council+Meeti…> http://www.timeanddate.com/worldclock/fixedtime.html?msg=GNSO+Council+Meeti… Coordinated Universal Time 20:00 UTC 13:00 Los Angeles; 16:00 Washington; 21:00 London; 22:00 Paris; 05:00 Tokyo next day 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: Draft Minutes of the GNSO Council meeting 10 May 2012 approved on 28 May 2012. http://gnso.icann.org/meetings/minutes-council-10may12-en.htm 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. 2.1 GAC/GNSO Issues Related to International Olympic Committee (IOC) & Red Cross (RC) Names Drafting Team. Approve sending of note to GAC. Item 3: Best practices for addressing abusive registrations (15 minutes) Following the recommendation of the Registration Abuse Policies (RAP) Working Group, the GNSO Council requested a discussion paper on the creation of non-binding best practices to help registrars and registries address the abusive registrations of domain names. The discussion paper recommended the creation of two Working Groups, one to establish the framework for best practices and one to propose candidate best practices to address the abusive registration of domain names. The Council must now consider a motion to set up a drafting team to create the charter for these groups. This motion was deferred from the May 10, 2012 meeting. Refer to motion 1 https://community.icann.org/display/gnsocouncilmeetings/Motions+10+May+2012 3.1 Reading of the motion (Zahid Jamil) 3.2 Discussion 3.3 Vote Item 4: WHOIS Access recommendation (10 minutes) The WHOIS access recommendation was considered as part of the consent agenda at the Council's 16 February 2012 meeting. At that meeting, the ISP constituency requested that the proposal to end this work be removed from the consent agenda and considered as part of the GNSO's main agenda. A further suggestion was suggested that constituency/stakeholder members work with Staff to identify a path forward and that the topic be further discussed at the Costa Rica meetings. A motion has been made to consider next steps. Refer to motion 2 https://community.icann.org/display/gnsocouncilmeetings/Motions+07+June+2012 4.1 Reading of the motion (Wolf-Ulrich Knoben) 4.2 Discussion 4.3 Vote Item 5: Outreach Task Force (OTF) (10 minutes) The Council has set up a drafting team to develop a charter for an OTF. A motion to approve that charter did not pass when made at the Dakar meeting. A second motion was made at the December 15, 2011 meeting and was not seconded, which meant it was not considered. In Costa Rica, the Council decided to form a group to discuss options on how to proceed. This is an update item on the work of that group. 5.1 Update from (X Y) 5.2 Discussion 5.3 Next steps Item 6: Fake Renewal Notices (10 minutes) The GNSO Council requested that a small group prepare a request for information concerning Fake Renewal Notices for the RrSG to help inform its deliberations on the RAP WG Recommendation on Fake Renewal Notices (#2). The drafting team submitted its report<http://gnso.icann.org/issues/frn/fake-renewal-notices-report-06mar12-en.pdf> to the GNSO Council on 6 March. Following a presentation of the report to the GNSO Council at the ICANN Meeting in Costa Rica, the GNSO Council decided to put the report out for public comment. A public comment forum was opened (see http://www.icann.org/en/news/public-comment/fake-renewal-notices-report-21m…) and has now closed. The Council is now expected to consider next steps. 6.1 Public comment forum submissions overview (Marika Konings) Report of Public Comments on Fake Renewal Notices<http://www.icann.org/en/news/public-comment/report-comments-fake-renewal-no…> 6.2 Discussion 6.3 Next steps Item 7: Uniformity of Reporting (10 minutes) To help inform its consideration of the RAPWG Recommendation on Uniformity of Reporting, the GNSO Council requested the ICANN Compliance Department to report on existing systems to report and track violations and/or complaints; improvements made since the RAPWG Report or foreseen in the near future, and: identify gaps and any improvements that might be desirable but not foreseen at this stage. The ICANN Compliance Team submitted its report<http://gnso.icann.org/issues/rap/contractual-compliance-report-reporting-un…> on 18 March and presented it to the GNSO Council at its meeting on 12 April. ICANN Staff also provided a background presentation on the RAP WG Recommendation (see https://gnso.icann.org/node/30809) The GNSO Council is now expected to consider next steps, if any. 7.1 Discussion 7.2 Next steps Item 8: Update on the Joint Supporting Organisations/Advisory Committee on New gTLD Applicant Support Working Group (JAS WG) (15 minutes) This item aims to provide the Council with a status update on the JAS WG so that next steps for the group can be determined. This was discussed at the May 10, 2012 Council meeting but as Kurt was unable to attend, the Council felt another discussion point was needed on this subject. Also, a number of questions were asked by the Council during its previous meeting and it was felt that it would be useful to get responses from Kurt to them. 8.1 WG update from Staff, and answers to Council questions (Kurt Pritz) 8.2 Discussion 8.3 Next steps Item 9: Update on the Internationalised Registration Data (IRD) Working Group (WG) (10 minutes) The IRD submitted its final report to the GNSO Council and SSAC on March 3, 2012 for review and approval. However, SSAC has recommend some substantial changes and more work may now be needed by the IRD before its final report can be considered. This agenda item is to provide an update on these latest developments in the IRD WG's work to the Council. 9.1 WG update from Staff<https://gnso.icann.org/correspondence/status-update-ird-wg-final-report-sli…> (Steve Sheng) 9.2 Discussion Item 10: UDRP Domain Locking WG (5 minutes) As per the GNSO WG Guidelines, the Chairs of a WG need to be confirmed by the GNSO Council. The Council may wish to note that Michele Neylon (Proposed Chair) and Alan Greenberg (Proposed Vice-Chair) were selected with unanimous support from the Working Group. 10.1 WG update from Staff (Marika Konings) 10.2 Council approval of proposed WG Chair and VC. Item 11: Consumer Metrics WG (5 minutes) The Consumer Metrics WG has prepared a draft advice document for discussion in Prague in order to finalise the document before sending it to the Council. As part of that process, the WG would like to solicit the GAC's input. A letter http://gnso.icann.org/issues/cci-draft-letter-gnso-to-gac-23may12-en.pdf has been drafted for the Council Chair to send to the GAC Chair. The Council must decide whether to send that letter. 11.1 WG update from Council Liaison (Rosemary Sinclair) 11.2 Council approval of sending proposed letter. Item 12: 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: a. Create an Issues Report: requires an affirmative vote of more than one-fourth (1/4) vote of each House or majority of one House. b. Initiate a Policy Development Process ("PDP") Within Scope (as described in Annex A<http://www.icann.org/en/about/governance/bylaws#AnnexA>): requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. c. Initiate a PDP Not Within Scope: requires an affirmative vote of GNSO Supermajority. d. Approve a PDP Team Charter for a PDP Within Scope: requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. e. Approve a PDP Team Charter for a PDP Not Within Scope: requires an affirmative vote of a GNSO Supermajority. f. Changes to an Approved PDP Team Charter: For any PDP Team Charter approved under d. or e. above, the GNSO Council may approve an amendment to the Charter through a simple majority vote of each House. g. Terminate a PDP: Once initiated, and prior to the publication of a Final Report, the GNSO Council may terminate a PDP only for significant cause, upon a motion that passes with a GNSO Supermajority Vote in favor of termination. h. 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. i. Approve a PDP Recommendation With a GNSO Supermajority: requires an affirmative vote of a GNSO Supermajority, j. 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. k. Modification of Approved PDP Recommendation: Prior to Final Approval by the ICANN Board, an Approved PDP Recommendation may be modified or amended by the GNSO Council with a GNSO Supermajority vote. l. A "GNSO Supermajority" shall mean: (a) two-thirds (2/3) of the Council members of each House, or (b) three-fourths (3/4) of one House and a majority of the other House." 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 March and October, Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- Reference (Coordinated Universal Time) UTC 20:00 ---------------------------------------------------------------------------- California, USA (PDT<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) UTC-8+1DST 13:00 New York/Washington DC, USA (EDT) UTC-5+1DST 16:00 – next day Buenos Aires, Argentina (ART<http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) UTC-3+0DST 17:00 Montevideo, Uruguay (UYT<http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) UTC-3+0DST 17:00 London, United Kingdom (BST) UTC+1DST 21:00 Abuja,Nigeria (WAT<http://www.timeanddate.com/library/abbreviations/timezones/africa/wat.html>) UTC+1+0DST 21:00 Tunis, Tunisia (CET) UTC+1+0DST 21:00 Bonn, Germany (CEST) UTC+1+1DST 22:00 Paris, France (CEST) UTC+1+1DST 22:00 Ramat Hasharon, Israel(IST<http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.…>) UTC+2+0DST 23:00 Karachi, Pakistan (PKT<http://www.timeanddate.com/library/abbreviations/timezones/asia/pkt.html> ) UTC+5+0DST 01:00 – next day Beijing/Hong Kong, China (HKT ) UTC+8+0DST 04:00 – next day Tokyo, Japan (JST<http://www.timeanddate.com/library/abbreviations/timezones/asia/jst.html>) UTC+9+0DST 05:00 – next day Wellington, New Zealand (NZDT<http://www.timeanddate.com/library/abbreviations/timezones/pacific/nzdt.html> ) UTC+12+0DST 08:00 – next day ---------------------------------------------------------------------------- The DST starts/ends on last Sunday of October 2012, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

WHOIS Technical Requirements Survey - Draft - Request for community input
by Glen de Saint Géry 31 May '12

31 May '12

Public Comment Box Link: http://www.icann.org/en/news/public-comment/draft-whois-requirements-survey… WHOIS Technical Requirements Survey - Draft Comment/Reply Periods (*) Important Information Links Comment Open: 30 May 2012 Comment Close: 20 June 2012 Close Time (UTC): 23:59 Public Comment Announcement<http://www.icann.org/en/news/announcements/announcement-30may12-en.htm> Reply Open: 20 June 2012 To Submit Your Comments (Forum)<mailto:draft-whois-requirements-survey@icann.org> Reply Close: 16 July 2012 View Comments Submitted<http://forum.icann.org/lists/draft-whois-requirements-survey/> Close Time (UTC): 23:59 Report of Public Comments Brief Overview Originating Organization: GNSO Council - WHOIS Survey Working Group Categories/Tags: Policy Processes Purpose (Brief): The Generic Names Supporting Organization (GNSO) Council's WHOIS Survey Working Group (WSWG) requests community input on the draft WHOIS Technical Requirements Survey. The Working Group is soliciting input from experts on technical requirements for a new WHOIS protocol, in particular people knowledgeable about technical aspects of WHOIS who can help assess if the survey asks the right questions and in the right style to elicit technical feedback. The Working Group seeks specific suggestions on changes to language and questions that will make it clearer for experts to complete. Current Status: This Public Comment solicitation represents an opportunity for the community to share perspectives on the proposed draft WHOIS Technical Requirements Survey. In parallel, the WSWG will conduct a Webinar to promote the survey and solicit additional feedback. Next Steps: The WSWG will consider the comments received as part of their deliberations and creation of the final version of the WHOIS Requirements Survey. Upon submission to the GNSO Council, the survey will be announced and released for community participation. The survey will be available for 30 days. Afterwards, the WSWG will compile, analyze and report on the survey results to produce a final report outlining possible WHOIS Technical requirements. Staff Contact: Liz Gasster Email: policy.staff(a)icann.org<mailto:policy.staff@icann.org?subject=More%20information%20on%20the%20WHOIS%20Technical%20Requirements%20Survey%20-%20Draft%20public%20comment%20period> Detailed Information Section I: Description, Explanation, and Purpose The WHOIS Survey Working Group produced a draft survey of WHOIS Technical Requirements at the request of the GNSO Council Resolution (http://gnso.icann.org/resolutions#20111006-1) The Working Group is seeking community feedback on the draft, which will be considered by GNSO Council and later released to the community for participation in the WHOIS survey. The Survey can be accessed here: http://icann.isoc.ug/whoissurvey/?sid=71483 The Working Group will accept community feedback via the public comment forum. Additionally, users of the survey will see a free-form text dialogue box at the bottom of each section of the survey. Users may use this space to provide specific feedback with respect to the questions loaded for that section. If you use this feature, be sure to include your identity so that we may relate your response to the public comment review process. Section II: Background The Working Group aims to draft, implement, and analyze the results of a survey measuring the level of support for various technical requirements outlined in the GNSO WHOIS Service Requirement Report (http://gnso.icann.org/issues/whois/whois-service-requirements-final-report-… [PDF, 633 KB]). The WHOIS Survey Working Group will produce a Report to be delivered to the GNSO Council describing the results of the survey and recommendations for next steps for the GNSO Council's consideration concerning the WHOIS service requirements. Section III: Document and Resource Links 1. WHOIS Requirements Survey - http://icann.isoc.ug/whoissurvey/?sid=71483 2. WSWG Charter - http://gnso.icann.org/issues/whois/charter-wswg-06oct11-en.pdf [PDF, 476 KB] 3. WSWG Wiki - https://community.icann.org/display/WSDT/WHOIS+Survey+Working+Group+-+Home 4. GNSO WHOIS Service Requirement Report - http://gnso.icann.org/issues/whois/whois-service-requirements-final-report-… [PDF, 633 KB] Section IV: Additional Information None (*) Comments submitted after the posted Close Date/Time are not guaranteed to be considered in any final summary, analysis, reporting, or decision-making that takes place once this period lapses. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

The TLD Application System, or TAS, has now closed.
by Glen de Saint Géry 31 May '12

31 May '12

http://www.icann.org/en/news/announcements/announcement-2-30may12-en.htm New gTLD Update by Akram Atallah, COO 30 May 2012 The TLD Application System, or TAS, has now closed. As of 23.00 GMT/UTC today, with one hour remaining before the system closed, just over 1900 applications had been submitted in TAS. We will reconcile all payments and submitted applications, and will release the final numbers when the applied-for domain names are published. As we said yesterday, our target date for publishing the list of applied-for domain names is 13 June 2012. We thank all applicants and the ICANN community for their support throughout the application process. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

RE: [council] Motion
by john＠crediblecontext.com 30 May '12

30 May '12

On behalf of the Business Constituency, I will second. John Berard Founder Credible Context 58 West Portal Avenue, #291 San Francisco, CA 94127 m: 415.845.4388 -------- Original Message -------- Subject: [council] Motion From: <KnobenW(a)telekom.de> Date: Wed, May 30, 2012 8:30 am To: <council(a)gnso.icann.org> On behalf of the ISPCP constituency I'd like to introduce the motion attached to the 07 June council meeting. Mit freundlichen Grüßen Best regards Wolf-Ulrich

1 0

TR: GNSO Council Abstention Notification Form [#93]
by Glen de Saint Géry 30 May '12

30 May '12

FYI De : ICANN [mailto:no-reply@wufoo.com] Envoyé : mercredi 30 mai 2012 23:38 À : gnso.secretariat(a)icann.org Objet : GNSO Council Abstention Notification Form [#93] Name of Officer: * Matt Serlin Officer Email Address: * matt.serlin(a)markmonitor.com<mailto:matt.serlin@markmonitor.com> Date Prepared: * Wednesday, May 30, 2012 GNSO Organization: * Registrars Stakeholder Group Officer Position or Title: * Vice-Chair Voting Remedy: * Proxy Reason(s) for or condition(s) leading to the remedy: * Mason Cole unable to attend teleconference Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: * June 7 teleconference Date upon which the remedy will expire or terminate: [Note: may not exceed 3 months initially; may be renewed by sending an email with explanation to GNSO Secretariat] * Friday, June 8, 2012 I affirm that a voting position has been established on the matter(s) at issue pursuant to provisions contained in our Charter or Bylaws. * Yes Our GNSO Councilor has been instructed on how to vote on the matter(s). * Yes Please identify the GNSO Councilor who will serve as the voting proxy: * Stephane VanGelder

1 0

Notice of Extension of ICANN Comment Period: ICANN Draft FY13 Operating Plan and Budget until 8 June 2012, with the reply period closing on June 15th 2012
by Glen de Saint Géry 30 May '12

30 May '12

http://www.icann.org/en/news/announcements/announcement-29may12-en.htm Notice of Extension of ICANN Comment Period: ICANN Draft FY13 Operating Plan and Budget 29 May 2012 * Français<http://www.icann.org/fr/news/announcements/announcement-01may12-fr.htm> * Español<http://www.icann.org/es/news/announcements/announcement-01may12-es.htm> * Русский<http://www.icann.org/ru/news/announcements/announcement-01may12-ru.htm> * 简体中文<http://www.icann.org/zh/news/announcements/announcement-01may12-zh.htm> * العربية<http://www.icann.org/ar/news/announcements/announcement-01may12-ar.htm> http://www.icann.org/en/news/public-comment/op-budget-fy13-01may12-en.htm In response to comments made by community members regarding time required to complete quantitative comments on the ICANN draft FY13 Operating Plan and Budget, ICANN has extended this public comment period until 8 June 2012, with the reply period closing on June 15th 2012. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

WHOIS Technical Requirements Survey - Draft
by Glen de Saint Géry 30 May '12

30 May '12

http://www.icann.org/en/news/announcements/announcement-30may12-en.htm WHOIS Technical Requirements Survey - Draft 30 May 2012 Forum Announcement: Comment Period Opens on Date: 30 May 2012 Categories/Tags: Policy Processes Purpose (Brief): The Generic Names Supporting Organization (GNSO) Council's WHOIS Survey Working Group (WSWG) requests community input on the draft WHOIS Technical Requirements Survey. The Working Group is soliciting input from experts on technical requirements for a new WHOIS protocol, in particular people knowledgeable about technical aspects of WHOIS who can help assess if the survey asks the right questions and in the right style to elicit technical feedback. The Working Group seeks specific suggestions on changes to language and questions that will make it clearer for experts to complete. Public Comment Box Link: http://www.icann.org/en/news/public-comment/draft-whois-requirements-survey… Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0