January 2013 - council - lists.icann.org

Registrar roundtable event in Los Angeles on Thursday 17 Jan 2012
by Bruce Tonkin Jan. 21, 2013

Jan. 21, 2013

Hello All, Fadi has provided a brief summary of the meeting held last week in his blog: http://blog.icann.org/2013/01/dns-industry-ceo-roundtable-event Regards, Bruce Tonkin

1 0

POLICY VERSUS IMPLEMENTATION DRAFT FRAMEWORK FOR DISCUSSION
by David Olive Jan. 18, 2013

Jan. 18, 2013

Dear GNSO Council Members: As mentioned previously, I would like to share with you a staff paper concerning the topic of policy vs. implementation which outlines a draft framework for community discussion. In addition, the paper aims to identify a number of principles, questions as well as possible improvements that will hopefully facilitate further consideration of this issue. In addition to sharing this with you, we are also planning to circulate this to the other ICANN Supporting Organizations and Advisory Committees for their consideration. Further to any steps the GNSO may want to take in relation to this issue, our idea would be to solicit volunteers from the different SO/ACs to set up a small organizing committee to plan a session in Beijing on this topic so further consideration can be given to possible next steps and/or recommendations. If you have any comments and/or questions, please feel free to share those with the list. This topic is also expected to be on the agenda for the next GNSO Council meeting. Best regards, David -- David A. Olive Vice President, Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) 1101 New York Avenue, NW - Suite 930 Washington, D.C. 20005 Office: 202.570.7126 Mobile: 202.341.3611

2 2

TR: GNSO Council Abstention Notification Form [#112]
by Glen de Saint Géry Jan. 18, 2013

Jan. 18, 2013

FYI De : ICANN [mailto:no-reply@wufoo.com] Envoyé : vendredi 18 janvier 2013 19:47 À : gnso.secretariat(a)icann.org; council(a)gnso.icann.org Objet : GNSO Council Abstention Notification Form [#112] Name of Officer: * Matt Serlin Officer Email Address: * matt.serlin(a)markmonitor.com<mailto:matt.serlin@markmonitor.com> Date Prepared: * Friday, January 18, 2013 GNSO Organization: * Registrars Stakeholder Group Officer Position or Title: * Chair Voting Remedy: * Proxy Reason(s) for or condition(s) leading to the remedy: * Unavailability of Mason Cole Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: * Entire Council meeting 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] * Tuesday, January 22, 2013 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: * Volker Greimann

1 0

GNSO Council Meeting Agenda Monday, 21 January 2013 at 15:00UTC:
by Glen de Saint Géry Jan. 18, 2013

Jan. 18, 2013

Dear Councillors, Please find the draft agenda for the GNSO Council Meeting on Monday, 21 January 2013 at 15:00UTC: The agenda is published on pages: http://gnso.icann.org/en/group-activities/calendar#jan http://gnso.icann.org/en/meetings/agenda-council-21jan13-en.htm On the Wiki at: https://community.icann.org/display/gnsocouncilmeetings/Agenda+21+January+2… Agenda for the Special GNSO Council Meeting on 21 January 2012 This agenda was established according to the GNSO Council Operating Procedures approved 13 September 2012 for the GNSO Council and updated. http://gnso.icann.org/en/council/gnso-operating-procedures-13sep12-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 15:00 UTC<http://tinyurl.com/bojlrbx> http://tinyurl.com/a5z86y3 Coordinated Universal Time 15:00 UTC 07:00 Los Angeles; 10:00 Washington; 15:00 London; 16:00 Paris; 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 audio cast 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 Item 2: Review and potentially add endorsements to the list of SG endorsed GNSO applicants to the ATRT (20 minutes) The call for applicants to serve on the next Accountability and Transparency Review Team (ATRT) has closed. ICANN has forwarded all applications received to the GNSO Council and placed them on a web site for inspection by the four GNSO stakeholder groups. According to the Process for GNSO Endorsement of Nominees to the Affirmation of Commitments Review Teams, each stakeholder group (SG) may endorse one applicant to serve as a representative in a given review team. The Council must consider the resulting list of up to four nominees. If the list does not meet the required diversity objectives, the Council as a whole may choose to endorse up to two additional candidates from the applicant pool, who will help to give the list of GNSO nominees the desired balance. In this case, the Council will hold a vote, with sixty percent support of both houses represented in the Council being required for endorsement. If no candidate obtains that level of support, the list of endorsements obtained via the bottom-up process of stakeholder group nominations will be deemed final and forwarded to ICANN. 2.1 Review SG endorsed applicants against specfied diversity requirements 2.2 Consider additional candidates 2.4 Vote on addtional candidates (To approve the addition of a candidate/s to the list of endorsed candidates in order to meet geographic and/or gender diversity coondition: An affirmative vote of 60% or more of each House). 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 October and 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 Rio de Janiero, Brazil (BRST) UTC-3+1DST 13:00 Montevideo, Uruguay (UYST<http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) UTC-3+1DST 13:00 Edinburgh, Scotland (BST) UTC+0DST 11: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 Bonn, Germany (CEST) UTC+1+0DST 16:00 Stockholm, Sweden (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/Hong Kong, China (HKT ) UTC+8+0DST 23:00 Perth, Australia (WST<http://timeanddate.com/library/abbreviations/timezones/au/wst.html>) UTC+8+0DST 23: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 2013, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com http://tinyurl.com/a5z86y3 Please let me know if you have any questions. 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

ICANN Board response to the GAC Toronto Communiqué
by Bruce Tonkin Jan. 18, 2013

Jan. 18, 2013

Hello All, The ICANN Board has responded to the GAC's Toronto Communiqué. See attached. It is also available at: http://www.icann.org/en/news/correspondence/crocker-to-dryden-16jan13-en Regards, Bruce Tonkin

1 0

New gTLD Objection & Dispute Resolution Webinar - 29 January 2013 - 16:00 UTC
by Bruce Tonkin Jan. 18, 2013

Jan. 18, 2013

http://newgtlds.icann.org/en/announcements-and-media/webinars New gTLD Objection & Dispute Resolution Webinar Date: 29 January 2013 Time: 16:00 - 17:30 UTC (8:00am - 9:30am PST) Adobe Connect: To be announced Dial In: Dial in numbers are available: http://newgtlds.icann.org/en/announcements-and-media/webinars/dial-in-29jan… The New gTLD Objection and Dispute Resolution window will be open until 13 March 2013. This webinar will give you an overview of the new gTLD objection process, and let you meet and ask questions of the Dispute Resolution Service Providers. Join this webinar and gain an understanding of what happens during the dispute resolution process. Review the Objection & Dispute Resolution webpage for more information. http://newgtlds.icann.org/en/program-status/objection-dispute-resolution Regards, Bruce Tonkin

1 0

MP3 recording GNSO Council teleconference, Thursday, 17 January 2013
by Glen de Saint Géry Jan. 18, 2013

Jan. 18, 2013

[To: liaison6c[at]gnso.icann.org; council[at]gnso.icann.org] Please find the MP3 recording of the GNSO Council teleconference, held on Thursday, 17 January, 2013 at: http://audio.icann.org/gnso/gnso-council-20130117-en.mp3 on page http://gnso.icann.org/calendar/#jan Happy listening! 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

TR: GNSO Council Abstention Notification Form [#111]
by Glen de Saint Géry Jan. 17, 2013

Jan. 17, 2013

FYI De : ICANN [mailto:no-reply@wufoo.com] Envoyé : jeudi 17 janvier 2013 23:34 À : gnso.secretariat(a)icann.org; council(a)gnso.icann.org Objet : GNSO Council Abstention Notification Form [#111] Name of Officer: * Robin Gross Officer Email Address: * robin(a)ipjustice.org<mailto:robin@ipjustice.org> Date Prepared: * Thursday, January 17, 2013 GNSO Organization: * Non-Commercial Stakeholder Group Officer Position or Title: * Chair Voting Remedy: * Proxy Reason(s) for or condition(s) leading to the remedy: * Magaly Pazello will be absent from the GNSO Council Mtg on 21 January 2013. David Cake will hold Magaly's proxy for that meeting. Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: * All. 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] * Monday, January 21, 2013 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: * David Cake

1 0

TR: GNSO Council Abstention Notification Form [#110]
by Glen de Saint Géry Jan. 17, 2013

Jan. 17, 2013

FYI De : ICANN [mailto:no-reply@wufoo.com] Envoyé : jeudi 17 janvier 2013 23:31 À : gnso.secretariat(a)icann.org; council(a)gnso.icann.org Objet : GNSO Council Abstention Notification Form [#110] Name of Officer: * Robin Gross Officer Email Address: * robin(a)ipjustice.org<mailto:robin@ipjustice.org> Date Prepared: * Thursday, January 17, 2013 GNSO Organization: * Non-Commercial Stakeholder Group Officer Position or Title: * Chair Voting Remedy: * Proxy Reason(s) for or condition(s) leading to the remedy: * Wolfgang Kleinwachter will be absent from the GNSO Council Mtg on 21 January 2013. Maria Farrell will hold Wolfgang's proxy for that meeting. Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: * All. 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] * Monday, January 21, 2013 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: * Maria Farrell

1 0

GNSO Council resolutions 17 January 2013
by Glen de Saint Géry Jan. 17, 2013

Jan. 17, 2013

Dear Councillors, Ahead of the GNSO Council minutes, the following resolutions were passed by the GNSO Council at the meeting held on 17 January 2013. 1. Initiation of a Policy Development Process (PDP) on the Inter-Registrar Transfer Policy (IRTP) Part D Whereas The Inter-Registrar Transfer Policy (IRTP) is an existing consensus policy under review by the GNSO; The GNSO Transfers Working Group identified a number of issues in its review of the current Policy and those issues have been grouped into suggested PDPs, set A-E, as per the Council's resolution of 8 May 2008; The GNSO Council requested an Issue Report on IRTP Part D at its meeting on 17 October 2012 (see http://gnso.icann.org/en/resolutions#20121017-4) A Preliminary Issue Report on IRTP Part D was published on 14 November 2012 for public comment (see http://www.icann.org/en/news/public-comment/irtp-d-prelim-issue-report-14no…) A Final Issue Report on IRTP Part D was published on 8 January 2012 (see http://gnso.icann.org/en/issues/issue-report-irtp-d-08jan13-en.pdf) The Final Issue Report recommends that the GNSO Council proceed with a Policy Development Process limited to consideration of the issues discussed in this report, and the General Counsel of ICANN has indicated the topic is properly within the scope of the ICANN policy process and within the scope of the GNSO RESOLVED: The GNSO will initiate a PDP on the issues defined in the Final Issue Report on the Inter-Registrar Transfer Policy Part D (http://gnso.icann.org/en/issues/issue-report-irtp-d-08jan13-en.pdf) A Working Group will be created for the purpose of fulfilling the requirements of the PDP. 2. Motion for Approval of a Charter for the Inter-Registrar Transfer Policy (IRTP) Part D Working Group (WG) Whereas On 17 January 2013 the GNSO Council initiated a Policy Development Process (PDP) on the Inter-Registrar Transfer Policy (IRTP) Part D and decided to create a PDP Working Group for the purposes of fulfilling the requirements of the PDP; The GNSO Council has reviewed the charter. RESOLVED, The GSNO Council approves the charter and appoints [to be confirmed] as the GNSO Council Liaison to the IRTP Part D PDP Working Group. The GNSO Council further directs that the work of the IRTP Part D WG be initiated no later then 14 days after the approval of this motion. Until such time as the WG can select a chair and that chair can be confirmed by the GNSO Council, the GNSO Council Liaison shall act as interim chair. Charter The Working Group shall consider the following questions as outlined in the Final Issue Report http://gnso.icann.org/en/issues/issue-report-irtp-d-08jan13-en.pdf and make recommendations to the GNSO Council: IRTP Dispute Policy Enhancements a) Whether reporting requirements for registries and dispute providers should be developed, in order to make precedent and trend information available to the community and allow reference to past cases in dispute submissions; b) Whether additional provisions should be included in the TDRP (Transfer Dispute Resolution Policy) on how to handle disputes when multiple transfers have occurred; c) Whether dispute options for registrants should be developed and implemented as part of the policy (registrants currently depend on registrars to initiate a dispute on their behalf); d) Whether requirements or best practices should be put into place for registrars to make information on transfer dispute resolution options available to registrants; Penalties for IRTP Violations e) Whether existing penalties for policy violations are sufficient or if additional provisions/penalties for specific violations should be added into the policy; Need for FOAs f) Whether the universal adoption and implementation of EPP AuthInfo codes has eliminated the need of FOAs. The Working Group shall follow the rules outlined in the GNSO Working Group Guidelines http://gnso.icann.org/council/annex-1-gnso-wg-guidelines-07apr11-en.pdf Let me know if you have any questions. Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0