April 2013 - council - lists.icann.org

Proposed Motion on RAA
by Wendy Seltzer 04 Apr '13

04 Apr '13

I'd like to propose the following motion for the Beijing meeting (resending from the correct address): Whereas the most recently posted draft Registrar Accreditation Agreement (RAA) has raised serious concerns of policy among most of the stakeholder groups in the GNSO [see Minutes of March call]; Whereas ICANN negotiators have held it out as a blocker to the implementation of the New gTLD Program; Resolved, Council recommends that ICANN permit Registrars to extend the rights and obligations in the current RAA and its renewals to new gTLDs until such time as the GNSO adopts a consensus supporting the policy changes in any proposed new RAA. Thanks, --Wendy -- Wendy Seltzer -- wendy(a)seltzer.org +1 617.863.0613 Policy Counsel, World Wide Web Consortium (W3C) Fellow, Berkman Center for Internet & Society at Harvard University Visiting Fellow, Yale Law School Information Society Project http://wendy.seltzer.org/ https://www.chillingeffects.org/ https://www.torproject.org/ http://www.freedom-to-tinker.com/

3 3

Dial in details for the GNSO Council Public Meeting and GNSO Wrap up Session in Beijing.
by Nathalie Peregrine 04 Apr '13

04 Apr '13

Dear all, Please find below the dial in details for the GNSO Council Public Meeting and the GNSO Wrap up session in Beijing . The meetings will be audio streamed, recorded and there will be a transcript available. For audio streaming please click on the link to the Adobe Connect on the meeting node below. · Wednesday 10th April - GNSO Council Public Meeting http://beijing46.icann.org/node/37155 Room: Grand Hall A 15:15 - 18:30 Password: COUNCIL · Thursday 11th April - GNSO Wrap-up session http://beijing46.icann.org/node/37201 Room: Function 8AB 10:30 - 12:30 Password: GNSO Dial in numbers: Country Toll Numbers Freephone/ Toll Free Number ARGENTINA 0800-777-0519 AUSTRALIA ADELAIDE: 61-8-8121-4842 1-800-657-260 AUSTRALIA BRISBANE: 61-7-3102-0944 1-800-657-260 AUSTRALIA CANBERRA: 61-2-6100-1944 1-800-657-260 AUSTRALIA MELBOURNE: 61-3-9010-7713 1-800-657-260 AUSTRALIA PERTH: 61-8-9467-5223 1-800-657-260 AUSTRALIA SYDNEY: 61-2-8205-8129 1-800-657-260 AUSTRIA 43-1-92-81-113 0800-005-259 BELGIUM 32-2-400-9861 0800-3-8795 BRAZIL 0800-7610651 CHILE 1230-020-2863 CHINA CHINA A: 86-400-810-4789 10800-712-1670 CHINA CHINA B: 86-400-810-4789 10800-120-1670 COLOMBIA 01800-9-156474 CZECH REPUBLIC 420-2-25-98-56-64 800-700-177 DENMARK 45-7014-0284 8088-8324 ESTONIA 800-011-1093 FINLAND Land Line: 106-33-203 0-800-9-14610 FINLAND Mobile: 09-106-33-203 0-800-9-14610 FRANCE LYON: 33-4-26-69-12-85 080-511-1496 FRANCE MARSEILLE: 33-4-86-06-00-85 080-511-1496 FRANCE PARIS: 33-1-70-70-60-72 080-511-1496 GERMANY 49-69-2222-20362 0800-664-4247 GREECE 30-80-1-100-0687 00800-12-7312 HONG KONG 852-3001-3863 800-962-856 HUNGARY 06-800-12755 INDIA INDIA A: 000-800-852-1268 INDIA INDIA B: 000-800-001-6305 INDIA INDIA C: 1800-300-00491 INDONESIA 001-803-011-3982 IRELAND 353-1-246-7646 1800-992-368 ISRAEL 1-80-9216162 ITALY 39-02-3600-6007 800-986-383 JAPAN OSAKA: 81-6-7739-4799 0066-33-132439 JAPAN TOKYO: 81-3-5539-5191 0066-33-132439 LATVIA 8000-3185 LUXEMBOURG 352-27-000-1364 MALAYSIA 1-800-81-3065 MEXICO 001-866-376-9696 NETHERLANDS 31-20-718-8588 0800-023-4378 NEW ZEALAND 64-9-970-4771 0800-447-722 NORWAY 47-21-590-062 800-15157 PANAMA 011-001-800-5072065 PERU 0800-53713 PHILIPPINES 63-2-858-3716 POLAND 00-800-1212572 PORTUGAL 8008-14052 RUSSIA 8-10-8002-0144011 SAUDI ARABIA 800-8-110087 SINGAPORE 65-6883-9230 800-120-4663 SLOVAK REPUBLIC 421-2-322-422-25 SOUTH AFRICA 080-09-80414 SOUTH KOREA 82-2-6744-1083 00798-14800-7352 SPAIN 34-91-414-25-33 800-300-053 SWEDEN 46-8-566-19-348 0200-884-622 SWITZERLAND 41-44-580-6398 0800-120-032 TAIWAN 886-2-2795-7379 00801-137-797 THAILAND 001-800-1206-66056 UNITED KINGDOM BIRMINGHAM: 44-121-210-9025 0808-238-6029 UNITED KINGDOM GLASGOW: 44-141-202-3225 0808-238-6029 UNITED KINGDOM LEEDS: 44-113-301-2125 0808-238-6029 UNITED KINGDOM LONDON: 44-20-7108-6370 0808-238-6029 UNITED KINGDOM MANCHESTER: 44-161-601-1425 0808-238-6029 URUGUAY 000-413-598-3421 USA 1-517-345-9004 866-692-5726 VENEZUELA 0800-1-00-3702 Kind regards 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

Root Zone Scaling Measurements at L-Root
by Glen de Saint Géry 04 Apr '13

04 Apr '13

http://www.icann.org/en/news/announcements/announcement-03apr13-en.htm Root Zone Scaling Measurements at L-Root 3 April 2013 ICANN is the operator of L-Root, one of the thirteen root servers in the Domain Name System (DNS). To better be able to identify any performance impact on L-Root caused by a larger root zone, work has been done to implement additional instrumentation of L-Root's infrastructure. A plan for implementation of this additional measurement was published<http://www.icann.org/en/news/announcements/announcement-3-07dec12-en.htm> in December 2012. Statistics about growth of the root zone<http://dns.icann.org/services/root-zone-scaling-report-zone-contents/> were published on 31 January 2013. Results of measurements of L-Root's performance<http://dns.icann.org/services/root-zone-scaling-root-zone-system/> were published on 31 March 2013. All statistics published in the two companion reports update weekly. Comments and questions on the data presented are very welcome -- please send to Terry Manderson<mailto:terry.manderson@icann.org>. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/>

1 0

Questions to the Community on Accountability and Transparency within ICANN
by Glen de Saint Géry 04 Apr '13

04 Apr '13

http://www.icann.org/en/news/announcements/announcement-2-02apr13-en.htm Questions to the Community on Accountability and Transparency within ICANN Comment / Reply Periods (*) Comment Open Date: 2 April 2013 Comment Close Date: 2 May 2013 - 23:59 UTC Reply Open Date: 3 May 2013 Reply Close Date: 24 May 2013 - 23:59 UTC Important Information Links Public Comment Announcement<http://www.icann.org/en/news/announcements/announcement-2-02apr13-en.htm> To Submit Your Comments (Forum)<mailto:comments-atrt2-02apr13@icann.org> View Comments Submitted<http://forum.icann.org/lists/comments-atrt2-02apr13/> Brief Overview Originating Organization: Accountability and Transparency Review Team 2 (ATRT 2) Categories/Tags: * AoC * ATRT * Reviews/Improvements * Transparency/Accountability Purpose (Brief): With the goal of producing final recommendations by 31 December 2013, the second Accountability and Transparency Review Team (ATRT 2), mandated by paragraph 9.1 of the Affirmation of Commitments (AoC), is currently in the process of defining its scope, roadmap and work program. To inform its work, the ATRT 2 now seeks input from the Community on a set of questions<http://www.icann.org/about/aoc-review/atrt/community-questions-02apr13-en.p…> [PDF, 129 KB] compiled for the Community's consideration. Community participation is essential to the success of the review and all input will be carefully considered. The ATRT 2 welcomes any additional feedback. Current Status: Questions to the ICANN Community Next Steps: Public comments are requested to inform Accountability and Transparency Review Team 2 (ATRT 2) actions. Staff Contact: Alice Jansen Email Staff Contact<mailto:alice.jansen@icann.org?subject=More%20information%20on%20the%20Questions%20to%20the%20Community%20on%20Accountability%20and%20Transparency%20within%20ICANN%20public%20comment%20period> Detailed Information Section I: Description, Explanation, and Purpose: The second Accountability and Transparency Review Team (ATRT 2), mandated by paragraph 9.1 of the Affirmation of Commitments (AoC), commenced its activities in February 2013. With the goal of producing final recommendations by 31 December 2013, the Review Team is currently in the process of defining its scope, roadmap and work program. To date, the Review Team has identified issues, projects to review in light of the AoC requirements and divided the work into four work streams: 1. ATRT1 - review of implementation of ATRT1 Review Team recommendations + any new recommendations - AoC 9.1 (a)-(e); 2. Security, Stability and and Resiliency - review of implementation of SSR Review Team recommendations - AoC 9.2(a)-(c); 3. WHOIS - review of implementation of WHOIS Review Team Team recommendations AoC 9.3.1; 4. Consider the extent to which assessments and actions undertaken by ICANN have been successful in ensuring that ICANN is acting transparently, is accountable for its decision-making, and acts in the public interest. To inform its work, the ATRT 2 now seeks input from the Community on a set of questions<http://www.icann.org/about/aoc-review/atrt/community-questions-02apr13-en.p…> [PDF, 129 KB] compiled for the Community's consideration. Community participation is essential to the success of the review and all input will be carefully considered. The ATRT 2 welcomes any additional feedback. Section II: Background: As prescribed by the Affirmation of Commitments<http://www.icann.org/en/about/agreements/aoc/affirmation-of-commitments-30s…> (AoC), ICANN is to organize a review of its accountability and transparency commitments no less frequently than every three years. The first Accountability and Transparency Review Team (ATRT) was launched in early 2010, delivered its final report on 31 December 2010, and ICANN's Board approved implementation of the report's recommendations on 24 June 2011 (for further information, refer to: http://www.icann.org/en/about/aoc-review/atrt). On 5 October 2012, ICANN invited<http://www.icann.org/en/news/announcements/announcement-05oct12-en.htm> interested individuals to apply for a position of Volunteer Review Team Member, representing a Supporting Organization or Advisory Committee, or for a position of Independent Expert on the second Accountability and Transparency Review Team (ATRT 2), consistent with the AoC timeframe. The ATRT 2 composition was announced<http://www.icann.org/en/news/announcements/announcement-2-15feb13-en.htm> on 15 February 2013 and held its first face-to-face meeting in Los Angeles on 14-15 March 2013. Section III: Document and Resource Links: * Questions for the ICANN Community on the Impact of Previous Reviews and Inputs for the ATRT2<http://www.icann.org/about/aoc-review/atrt/community-questions-02apr13-en.p…> [PDF, 129 KB] * Affirmation of Commitments (AoC)<http://www.icann.org/en/about/agreements/aoc/affirmation-of-commitments-30s…> [PDF, 356 KB] Section IV: Additional Information: Please submit your comments to comments-atrt2-02apr13(a)icann.org<mailto:comments-atrt2-02apr13@icann.org> by 2 May 2013. The reply period will open on 3 May 2013 and will close on 24 May 2013. The ATRT 2 activities and materials may be viewed on the Team's public wiki<https://community.icann.org/pages/viewpage.action?pageId=40176025>. The ATRT 2 invites the Community to share their unique feedback with them in Beijing on Wednesday, 10 April - 11:00-12:30 (Grand Hall A) - please refer to session details for full information: http://beijing46.icann.org/node/37175 ________________________________ (*) 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<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/>

1 0

Revised Registry Agreement Posted for Review
by Alan Greenberg 04 Apr '13

04 Apr '13

Perhaps I missed it, but do not recall seeing this posted to this list. http://blog.icann.org/2013/04/revised-registry-agreement-posted-for-review/ Alan

2 2

Flight Cancellation
by Jonathan Robinson 04 Apr '13

04 Apr '13

All, My (BA) flight tomorrow has just been cancelled without reason. That suggests a security issue but this is conjecture on my part at this point. I will update you as and when I know more. Jonathan

3 3

Introduction of temporary replacement.
by Alan Greenberg 04 Apr '13

04 Apr '13

As I will be busy with ATRT2 activities on Saturday and possibly other times this week, Evan Leibovitch will be sitting in for me as ALAC Liaison wen I cannot make it (with Jonathan's agreement). I hope that you will give him the same warm welcome that I always receive. Alan

1 0

RE: [council] Request for agenda item for Beijing GNSO Council meeting
by Winterfeldt, Brian 03 Apr '13

03 Apr '13

Dear all: The IPC opposes this motion and fervently disagrees with statements proposed therein. We will follow up in due course with additional details on the IPC's position. Thank you, Brian Brian J. Winterfeldt Partner bwinterfeldt(a)steptoe.com<mailto:bwinterfeldt@steptoe.com> Steptoe From: owner-council(a)gnso.icann.org<mailto:owner-council@gnso.icann.org> on behalf of Jonathan Robinson[SMTP:JONATHAN.ROBINSON@IPRACON.COM] Sent: Tuesday, April 02, 2013 11:40:47 PM To: 'Maria Farrell'; council(a)gnso.icann.org<mailto:council@gnso.icann.org> Subject: RE: [council] Request for agenda item for Beijing GNSO Council meeting Auto forwarded by a Rule Thanks Maria, One practical question, I believe you are not going to be at the meeting in Beijing. So, is it your intention that someone else leads the making of the motion and the initial discussion or will you do so remotely? Jonathan From: owner-council(a)gnso.icann.org<mailto:owner-council@gnso.icann.org> [mailto:owner-council@gnso.icann.org] On Behalf Of Maria Farrell Sent: 02 April 2013 23:30 To: council(a)gnso.icann.org<mailto:council@gnso.icann.org> Subject: [council] Request for agenda item for Beijing GNSO Council meeting Dear Jonathan and fellow Council members, I would like to request the addition of an item to the draft Beijing GNSO Council meeting agenda, circulated earlier today, by proposing a motion for discussion and adoption, copied below. "The GNSO Council registers its disappointment and concern at the recent adoption in significant parts by ICANN staff of the Trademark Clearing House "Strawman Solution", despite the proposal's flawed genesis and the strong opposition to it voiced by both the GNSO council and a significant portion of the public comments. The expansion of rights protection mechanisms in the new gTLDs, following the comprehensive policy processes of the GNSO that had appeared to settle these issues, and also the clear determination by the GNSO Council that specific measures therein represent substantive policy-making rather than purely technical or operational implementation, represent an unwarranted extension into the policy-making function by ICANN staff. The GNSO Council strongly regrets the decision to circumvent the established, transparent and rules-based policy development process in a top-down decision-making process, to the detriment of the GNSO Council's bylaw-defined role and the multi-stakeholder model more broadly. As ICANN staff also currently seeks to endow the Board with top-down and unilateral policy authority in the new RA and RAA, without substantive justification, the GNSO Council is deeply concerned by the implications of this extension of executive privilege, in the adoption of the "Strawman Solution", and in other issues, and for the future of the multi-stakeholder model. The GNSO council therefore requests that the Board re-consider the proposed course of action regarding the TMCH, and, specifically, that the the extension of the TMCH claims procedure to 90 days and the inclusion of 50 additional terms not to be implemented until these proposals have been approved by a majority of the GNSO Council after careful consideration of their implications." Best regards, Maria

2 1

Key Meetings in Beijing
by Jonathan Robinson 03 Apr '13

03 Apr '13

All, By my reckoning, we have five key meetings coming up which need some more work or development. 1. 09h00 -10h30 Saturday - Open Discussion & Preparation Session 2. 11h00 - 12h20 Sunday - GNSO / GAC - Joining the GAC at the BGRI WG Meeting 3. 13h00 - 14h30 Sunday - GNSO Council Meeting with ICANN Board 4. 14h30 - 15h00 Sunday - GNSO Council Meeting with ICANN CEO 5. 12h30 - 14h00 Monday - GNSO Council / ccNSO Joint Meeting In order to keep responses coherent and in a single-thread, I'll send out an update on each one and highlight the status and potential for future work or input. It will be very helpful to have input on each of these. Please look out for the emails and I look forward to any input councillors feel willing or able to give. Safe travels to Beijing and look forward to working with you there. Jonathan Jonathan Robinson Chair ICANN GNSO Council jrobinson(a)afilias.info skype: jonathan.m.r

1 0

Request for agenda item for Beijing GNSO Council meeting
by Maria Farrell 03 Apr '13

03 Apr '13

Dear Jonathan and fellow Council members, I would like to request the addition of an item to the draft Beijing GNSO Council meeting agenda, circulated earlier today, by proposing a motion for discussion and adoption, copied below. "The GNSO Council registers its disappointment and concern at the recent adoption in significant parts by ICANN staff of the Trademark Clearing House "Strawman Solution", despite the proposal's flawed genesis and the strong opposition to it voiced by both the GNSO council and a significant portion of the public comments. The expansion of rights protection mechanisms in the new gTLDs, following the comprehensive policy processes of the GNSO that had appeared to settle these issues, and also the clear determination by the GNSO Council that specific measures therein represent substantive policy-making rather than purely technical or operational implementation, represent an unwarranted extension into the policy-making function by ICANN staff. The GNSO Council strongly regrets the decision to circumvent the established, transparent and rules-based policy development process in a top-down decision-making process, to the detriment of the GNSO Council's bylaw-defined role and the multi-stakeholder model more broadly. As ICANN staff also currently seeks to endow the Board with top-down and unilateral policy authority in the new RA and RAA, without substantive justification, the GNSO Council is deeply concerned by the implications of this extension of executive privilege, in the adoption of the "Strawman Solution", and in other issues, and for the future of the multi-stakeholder model. The GNSO council therefore requests that the Board re-consider the proposed course of action regarding the TMCH, and, specifically, that the the extension of the TMCH claims procedure to 90 days and the inclusion of 50 additional terms not to be implemented until these proposals have been approved by a majority of the GNSO Council after careful consideration of their implications." Best regards, Maria

3 2