January 2017 - council - lists.icann.org

Please Review: Project List
by Nathalie Peregrine 17 Jan '17

17 Jan '17

Dear Councillors, Attached please find the updated Project List in both red-line and clean version for your review before the Council meetings. If there are no comments, the list will be posted on the website on page: http://gnso.icann.org/en/council/project<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_counc…> and be directly viewed at :http://gnso.icann.org/meetings/projects-list.pdf<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_meetings…> Thanks so much. Kind regards, Nathalie

2 1

REVIEW: GNSO Council minutes Part 2 Hyderabad
by Glen de Saint Géry 17 Jan '17

17 Jan '17

Dear Councillors, Attached please find the draft minutes of the GNSO Council Public Meeting Part 2 that took place in Hyderabad on 7 November 2016 for your review. If there are no comments, these minutes will be published on the website as approved, according to the GNSO Rules of Procedure https://gnso.icann.org/en/council/op-procedures-01sep16-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 18 January 2017. The Board has been notified https://gnso.icann.org/en/correspondence/gnso-council-to-crocker-board-06ja… and the notification has also been posted on page https://gnso.icann.org/en/council/elections under 'Results'. Thank you very much. Kind regards, Glen Glen de Saint Géry Manager Supporting Organisations Advisory Committees Internet Corporation for Assigned Names & Numbers - ICANN glen(a)icann.org<mailto:glen@icann.org> http://www.icann.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFAw…> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>.

2 1

FW: [Ext] RySG SECRETARIAT NEWS ...
by Glen de Saint Géry 16 Jan '17

16 Jan '17

On behalf of Cherie Stubbs, RySG Secretariat to the GNSO Council. ******************************** As I wrapped up 2016, and after long and deliberate thought, I reached a decision to step down as the RySG Secretariat. I met with the Executive Committee Officers in Hyderabad, and my news was announced to the full RySG Executive Committee and membership this past week. I have been the RySG Secretariat for 16 years which was truly a second career for me! Prior to this position, I was a Health Care Administrator at the University of California, San Diego, Medical Centers, for 21 years. For those who have been in the ICANN community for some time, you can relate to my thought of watching the equivalent of a child starting to crawl and walk, going through childhood, adolescence, a teenager, and now a young adult who is ready to launch a whole new chapter in life. It has been a wonderful adventure and one I hope to continue to be a part of, even in some small way, for some time to come. I have given a 12-month notice to the RySG in order to assure as smooth a transition as possible. This will be a transitional effort over the coming months as there is too much to pass along at one time. I am then planning to stay on to assist with special projects, perhaps meeting planning and outreach, but stepping away from the day-to-day business. Sue Schuler, RySG Data Management Assistant, is starting to become more involved in some of the daily activities of the Stakeholder Group. However, as you can imagine, much is up in the air about next steps. The RySG Executive Committee will be further discussing the transition plan and timeline. Until further planning is settled, it will be business as usual for us! I'll look forward to seeing you at ICANN 58 in Copenhagen! Every best, Cherie

1 0

FW: [Ext] GNSO Council Abstention Notification Form [#234]
by Glen de Saint Géry 16 Jan '17

16 Jan '17

FYI From: ICANN [mailto:no-reply@wufoo.com] Sent: Monday, January 16, 2017 11:49 PM To: gnso.secretariat(a)icann.org; council(a)gnso.icann.org Subject: [Ext] GNSO Council Abstention Notification Form [#234] Name of Officer: * Steve DelBianco Officer Email Address: * sdelbianco(a)netchoice.org<mailto:sdelbianco@netchoice.org> Date Prepared: * Monday, January 16, 2017 GNSO Organization: * Business Constituency Officer Position or Title: * Vice Chair for Policy Coordination Voting Remedy: * Proxy Reason(s) for or condition(s) leading to the remedy: * BC Councilor Susan Kawaguchi will be on vacation during the 19-Jan-2017 Council teleconference. Susan will attempt to dial-in for the Council meeting, but we will designate a proxy in case Susan is unable to connect or cannot be heard. Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: * All matters that may come before the Council on 19-Jan-2017 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, January 20, 2017 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: * Phiip Corwin

1 0

Final Agenda GNSO Council Meeting 19 January at 21:00UTC
by Nathalie Peregrine 16 Jan '17

16 Jan '17

Dear councilors, Please find the Proposed Final Agenda for the GNSO Council Meeting on 19 January at 21:00UTC. With added item 1.4. FINAL AGENDA FOR GNSO COUNCIL MEETING 19 January 2017 Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/YqzDAw[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> This agenda was established according to the GNSO Operating Procedures<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> v3.2, updated on 01 September 2016. 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. Coordinated Universal Time: 21:00 UTC http://tinyurl.com/zocj4py[tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__tinyurl.com_zocj4py&d=D…> 13:00 Los Angeles; 16:00 Washington; 21:00 London; (Friday 20 January 2017) 00:00 Istanbul; 08:00 Hobart GNSO Council Meeting Audio Cast To join the event click on the link: http://stream.icann.org:8000/gnso.m3u[stream.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ Item 1. Administrative Matters (5 mins) 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Observer status on GNSO Council mailing list 1.5 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes of the meeting of the GNSO Council part II on 7 November 2016, posted on XXXXXXXX. Minutes of the meeting of the GNSO Council on 1 December 2016, posted on 19 December 2016. Minutes of the meeting of the GNSO Council on 15 December 2016, posted on 4 January 2017. Item 2. Opening Remarks / Review of Projects & Action List (10 mins) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…>and Action Item List[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> Item 3. Consent Agenda (0 mins) Item 4. COUNCIL VOTE – Endorsement of GNSO Representatives to the Second Security, Stability & Resiliency Review Team (SSR-2 RT) (20 minutes) The ICANN Bylaws mandate a periodic review of ICANN’s commitment to “enhance the operational stability, reliability, resiliency, security, and global interoperability of the systems and processes, both internal and external, that directly affect and/or are affected by the Internet's system of unique identifiers that ICANN coordinates”, to be conducted by a community-led Review Team. This security, stability and resiliency (SSR) review has to be conducted no less frequently than once every five years, measured from the date the previous SSR Review Team (RT) was convened. The first SSR RT was formed in October 2010, and it delivered its final report in June 2012. A Call for Volunteers to the SSR-2 RT was issued on 30 June 2016, with applications closing on 15 September 2016. A total of 12 applicants indicated that they were seeking endorsement from the GNSO, for a possible maximum of 7 out of 21 slots on the SSR-2 RT. Under the selection process agreed among the ICANN Supporting Organizations and Advisory Committees (SO/ACs), the top 3 nominees from each SO/AC will be guaranteed a slot. A small group of volunteer Councilors have reviewed the list and qualifications of the candidates who are seeking the GNSO’s endorsement. The current slate of applicants can be viewed at https://community.icann.org/x/xRqsAw[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…>. Here the Council will decide whether to approve the proposed slate of nominees for GNSO endorsement, as circulated to the Council list on 9 January 2017. 4.1 – Presentation of the motion https://community.icann.org/x/YKzDAw[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> (James Bladel) 4.2 – Council discussion 4.3 – Council vote (voting threshold: simple majority) Item 5. COUNCIL DISCUSSION – Proposal for a Facilitated Discussion between the GAC and the GNSO to Resolve Outstanding Differences in GAC Advice and GNSO Policy Recommendations concerning Second Level Protections for International Governmental Organization (IGO) Acronyms and Certain Names and Acronyms of the Red Cross Movement (25 minutes) On 20 December 2016, the GNSO Council Chairs participated in a teleconference with several members of the ICANN Board, the GAC Chair and several GAC member representatives. The purpose of the call was to discuss possible objectives for, and the scope of, a possible facilitated discussion between the GAC and the GNSO in order to resolve the inconsistencies between GAC advice and GNSO policy recommendations on the topic of IGO and Red Cross protections. These inconsistencies mainly concern second level protections for IGO acronyms and the following Red Cross identifiers: the names of 189 Red Cross National Societies, the names International Federation of Red Cross and Red Crescent Societies and International Committee of the Red Cross, and the acronyms associated with the two international names (IFRC/FICR and ICRC/CICR). The idea for a facilitated discussion had been suggested by the ICANN Board during the second Public Forum at ICANN57, in November 2016. Following the call, the GNSO Chair requested feedback from Councilors regarding any concerns or questions about GNSO participation in the proposed discussion. Board members who had participated in the 20 December call are preparing to circulate a proposed process outline describing the objectives and scope of the proposed discussion. Here the Council will continue its deliberations on the topic, including the timing of the discussions in relation to the work of the ongoing Working Group that is conducting the GNSO’s Policy Development Process on IGO curative rights protection issues. 5.1 – Summary and update (Council Chairs) 5.2 – Council discussion 5.3 – Next steps Item 6. COUNCIL DISCUSSION – Letter from Thick WHOIS Implementation Review Team on Privacy Issues relating to Implementation of the Thick WHOIS Consensus Policy Recommendations (10 minutes) On 15 December 2016, the Thick WHOIS Implementation Review Team (IRT) sent a letter to the GNSO Council describing a number of privacy law developments and how the IRT has considered them (see https://gnso.icann.org/en/correspondence/irt-to-gnso-council-15dec16-en.pdf…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_corr…>. The letter noted that the IRT’s implementation plan has been published for public comment (see https://www.icann.org/public-comments/proposed-implementation-gnso-thick-rd…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> and that the IRT does not currently expect the developments in question to affect the timeline for transition to thick WHOIS. Here the Council will discuss the letter, and any actions it may wish to take or feedback it may wish to provide to the IRT on this topic. 6.1 – Summary and update (Amr Elsadr) 6.2 – Council discussion 6.3 – Next steps Item 7: COUNCIL DISCUSSION – Community Budget Requests for Financial Year 2018 (15 minutes) On 15 December 2016, ICANN launched the FY18 SO-AC Community Additional Budget Request process. This process concerns a dedicated part of the overall ICANN annual budget that is set aside to fund specific requests from the community for activities in that specific Financial Year not already included in the recurring ICANN budget. The deadline for submission of community budget requests for FY2018 is 30 January 2017. Following preliminary review by ICANN staff and community consultations at ICANN58 in March 2018, final assessments are expected to be made by mid-April in time for Board approval by the end of May. The proposed timeline, guidelines and request templates can be found at https://community.icann.org/x/aqXDAw[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…>. Here the Council will discuss whether, and what, additional specific FY18 budget requests it may wish to make (distinct from any requests individual GNSO Stakeholder Groups or Constituencies may submit). 7.1 – Summary (GNSO Council Chairs/ Rob Hoggarth) 7.2 – Council discussion 7.3 – Next steps Item 8: COUNCIL DISCUSSION – Planning for ICANN58 (15 minutes) The GNSO Council had agreed previously on the need to start planning early for ICANN58, and to confirm certain important sessions (including joint meetings with other SO/ACs and the ICANN Board) as fixed in the overall meeting schedule. Advance planning will be helpful for scheduling purposes, including for GNSO Stakeholder Groups and Constituencies, coordination between and with other SO/ACs, and ensuring that sufficient time is given over to policy development work. To assist in the Council’s deliberations, staff compiled all GNSO Council input received on the ICANN58 Council Planning Survey: https://gnso.icann.org/en/drafts/icann58-council-planning-survey-30nov16-en…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_draf…>. Based on the Council’s deliberations at ICANN58 and its two December 2016 meetings, the Council Chairs, with the assistance of staff, have been developing a proposed ICANN58 schedule for the GNSO Council. The draft GNSO schedule was circulated on [INSERT DATE] (see [INSERT LINK]), and attempts to take into account the current overall block schedule (see https://meetings.icann.org/sites/default/files/icann58_blocksched_draft2.pd…<https://urldefense.proofpoint.com/v2/url?u=https-3A__meetings.icann.org_sit…>. Here the Council will continue its discussion of scheduling priorities for the GNSO at ICANN58. 8.1 – Status summary (GNSO Council leadership) 8.2 – Council discussion 8.3 – Next steps Item 9: ANY OTHER BUSINESS (10 minutes) Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i)) See https://www.icann.org/resources/pages/governance/bylaws-en/#article11[icann…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4) See https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf[gnso.icann.o…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…>. References for Coordinated Universal Time of 21:00 UTC Local time between October and March Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PST) UTC-8 +0DST 13:00 San José, Costa Rica UTC-6 +0DST 15:00 Iowa City, USA (CST) UTC-6 +0DST 15:00 New York/Washington DC, USA (EST) UTC-5 +0DST 16:00 Buenos Aires, Argentina (ART) UTC-3+0DST 18:00 Rio de Janeiro, Brazil (BRST) UTC-2 +0DST 19:00 London, United Kingdom (GMT) UTC+0DST 21:00 Bonn, Germany (CET) UTC+1+0DST 22:00 Cairo, Egypt, (EET) UTC+2 +0DST 23:00 Istanbul, Turkey (TRT) UTC+3+0DST (20 Jan 2017) 00:00 Singapore (SGT) UTC +8 +0DST (20 Jan 2017) 05:00 Tokyo, Japan (JST) UTC+9+0DST (20 Jan 2017) 06:00 Sydney/Hobart, Australia (AEDT) UTC+11+0DST (20 Jan 2017) 08:00 ---------------------------------------------------------------------------- DST starts/ends on last Sunday of March 2017, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com[timeanddate.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.timeanddate.com&d=D…> and http://tinyurl.com/zocj4py[tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__tinyurl.com_zocj4py&d=D…> Please let me know if you have any questions. Thank you very much Kind regards, Nathalie -- Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

FW: [Soac-infoalert] ICANN News Alert -- ICANN Quarterly Stakeholder Report Register for the FY17 Q2 Call on 15 February, 15:00 UTC
by James M. Bladel 16 Jan '17

16 Jan '17

Councilors, FYI. Please share with your SG/C. Thanks- J. From: <soac-infoalert-bounces(a)icann.org> on behalf of David Olive <david.olive(a)icann.org> Date: Monday, January 16, 2017 at 02:21 Subject: [Soac-infoalert] ICANN News Alert -- ICANN Quarterly Stakeholder Report Register for the FY17 Q2 Call on 15 February, 15:00 UTC [CANN][icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DgMFaQ…> News Alert https://www.icann.org/news/announcement-2017-01-12-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> ________________________________ ICANN Quarterly Stakeholder Report – Register for the FY17 Q2 Call on 15 February, 15:00 UTC 12 January 2017 ICANN has announced its FY17 Q2 Stakeholder Call, which will take place on 15 February 2017 at 15:00 UTC. The call will focus on how ICANN has implemented community policy for the quarter ending 31 December 2016. The call will also provide an Africa and Middle East update, as part of a new format aimed at spotlighting regional activities. Please click here[docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_forms_…> to register for the call and to receive joining instructions. If you are unable to access the form, please email us<mailto:icann.communications@icann.org> to register with your full name and an email address. The call is open for all to attend and live interpretation is offered in Arabic, Chinese, English, French, Portuguese, Russian and Spanish. There will be a Questions & Answers (Q&A) session and all materials (recordings, transcripts and presentations) will be archived and made available on the ICANN website[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. These calls were set up to enhance ICANN's accountability and transparency efforts, and are a great way for you to stay informed on what the organization has done in line with ICANN's mission of keeping the Internet secure, stable and interoperable. More information Please visit the Reporting page[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> on the ICANN website for more information, including recordings of previous calls. The presentation will be posted 24-48 hours in advance. ______________________________________________

1 0

Fwd: Call for Volunteers for the Registration Directory Service (formerly WHOIS) Review Team
by James M. Bladel 14 Jan '17

14 Jan '17

Councilors - Please see below for an announcement, extending the deadline for application to the RDS Review Team. Thank you, J. ------------- James Bladel _____________________________ From: Karen Mulberry <karen.mulberry(a)icann.org<mailto:karen.mulberry@icann.org>> Sent: Friday, January 13, 2017 16:37 Subject: Call for Volunteers for the Registration Directory Service (formerly WHOIS) Review Team Dear SO/AC Leaders, I wanted to call your attention to the updated RDS Call for Volunteers announcement that was released this week. We have extended the deadline for applications to 20 January 2017 so that you might share this within your communities to solicit volunteers. Thank you, Karen Mulberry Multistakeholder Strategy and Strategic Initiatives (MSSI) ICANN [CANN][icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DgMFaQ…> News Alert https://www.icann.org/news/announcement-2017-01-11-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> ________________________________ Call for Volunteers for the Registration Directory Service (formerly WHOIS) Review Team 11 January 2017 DEADLINE EXTENSION – Applications to be appointed to the Registration Directory Service (RDS) Review Team are due on20 January 2017, 23:59 UTC. ICANN is seeking volunteers to serve on the second review of Registration Directory Service (formerly known as the WHOIS Review). Interested individuals are invited to provide the following information, in the template[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_rdsapply…> [PDF, 2.66 MB] provided: * A biography, detailing relevant work and/or academic experience, as well as subject matter knowledge; * Your motivation for detailing your interest in serving on the Review Team and what you will bring to the team; * Specify the Supporting Organization (SO) or Advisory Committee (AC) that you would like to have consider you for nomination. Candidates are asked to submit their application materials toreviews(a)icann.org<mailto:reviews@icann.org> by 20 January 2017, 23:59 UTC. Note that all applications and supporting materials will be published as they are received on theRDS wiki page[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_pa…>. Limited Scope Proposal Recent discussions among the leadership of the ICANN Supporting Organizations and Advisory Committees (SO/AC) and the Board Working Group on Registration Directory Service have highlighted concerns with the expected workload and community bandwidth in light of all the WHOIS related activities currently underway. To address these concerns, and to ensure that the RDS Review is conducted efficiently and effectively, the SO/AC leaders are considering a proposal to limit the scope and timeline for this review. The current proposal would ask that the RDS Review Team limit its review to conducting an investigation of the implementation results from the last WHOIS Review Team. Selection of the Review Team Under the new Bylaws[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>, each SO/AC will have an opportunity to nominate up to seven applicants to serve on the Review Team. An applicant's name will only be presented to the SO/AC identified by the applicant for consideration. After SO/AC nomination process concludes, all nominations will be provided to the SO/AC Leaders to conduct the selection process for the Review Team according to the specified expertise and diversity (gender and geographic) requirements from the nominations received, the Review Team may contain up to 21 members, plus an ICANN Board member (designated by the ICANN Board). Timeline Call for volunteers published 28 October 2016 Deadline to apply for Review Team 20 January 2017 Time Commitment Applicants should be prepared to devote their time to the review process. Review Team work is expected to include regular conference calls (some of which may not be held during business hours in all time zones), and possibly up to three face-to-face meetings, each lasting two to three days. Under the Limited Scope Proposal, the RDS Review Team may be asked to complete its work within six months of its first meeting. Compensation RDS Review Team members will not receive compensation from ICANN for their service on the team. However, travel, meal and lodging costs for Review Team members who participate in Review Team meetings will be reimbursed upon request in accordance with ICANN's community travel support guidelines[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_news_…>. Responsibilities * Participate in creation of charter documents for the Review Team; * Select appropriate performance indicators and benchmarks; * Consider public, community and Board input and incorporate it as appropriate in Review Team recommendations; * Determine whether additional data or analysis is needed and participate in an ensuing provider selection, if necessary; * Provide timely updates to the community on the status of the Review Team's work; * Analyze findings; * Draw conclusions based on findings, develop useful and feasible recommendations; * Provide guidance on prioritization of recommendations and definition of desired outcomes; * Post the draft report of the Review Team for public review and comment; * Deliver a final Review Team report; and * Designate Review Team members to participate in the implementation planning work that follows the delivery of the final Review Team report. Skills and Experience To compose a well-balanced Review Team, ICANN seeks members who, in the aggregate, possess the following skills and experience: * Prior member of the 1st WHOIS Review Team or was an active contributor to its work * Prior member of the Expert Working Group on Registration Directory Service * Familiarity with operation of the Domain Name System (DNS) * Familiarity with WHOIS registrant data collection, compliance, directory service (RDDS) management * Familiarity with Translation and Transliteration of WHOIS Contact Information * Familiarity with ICANN Procedure for Handling WHOIS Conflicts with Privacy Law * Familiarity with malware and abuse vectors and mitigations, including cybercrime * Familiarity with WHOIS Data Retention Waiver Process Composition of the Review Team, depending on expertise and skills required, will aim to achieve: * Diversity in general, with particular attention on: * Geographic diversity; and * Gender diversity. Desired Attributes Applicants should possess the following professional and personal attributes: * Multistakeholder community understanding * Team spirit, adaptability, consensus-seeking attitude * Willingness to learn * Readiness to contribute * Capacity to reason objectively, putting aside personal opinions or preconceptions * Analytical skills Methodology, Budget & Support ICANN will provide the Review Team with a clearly articulated review budget at the start. Throughout the review, there will be periodic reporting by the Review Team on its progress relative to planned schedule and budget. A clear and focused review scope is expected to assist the Review Team with prioritizing recommendations in order to optimize finite ICANN resources (time and budget). ICANN organizational support will be made available to the Review Team. Support could include assistance with project management; organization of work, documents and activities; as well as sharing of tools and best practices for conducting an effective review. English is the working language of the Review Team. Key communications and documents will be translated in accordance with the ICANN Language Services policies. Background Community-led reviews are an important mechanism for furthering ICANN's obligations outlined in the newBylaws[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> that went into force on 1 October 2016. * Ensuring accountability, transparency and the interests of global Internet users; * Preserving security, stability and resiliency of the DNS; * Promoting competition, consumer trust and consumer choice; * Registration Directory Service (WHOIS) policy. These Specific Reviews replace the reviews that were formerly mandated under the Affirmation of Commitments (AoC). The specific objectives for the Registration Directory Service (RDS) Review are to review the effectiveness of WHOIS, and whether its implementation meets the legitimate needs of law enforcement, promoting consumer trust and safeguarding registrant data. The first WHOIS review concluded in 2012 and was conducted under the AOC. TheFinal Report[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> [PDF, 1.44 MB] from the First Review Team was submitted to the ICANN Board on 11 May 2012, with Board action to approve the report and recommendations, including theimplementation plan[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> [PDF, 119 KB] occurred on 8 November 2012. For more information on the status of the implementation activities arising out of the 1st WHOIS Review team, please visit the WHOIS ImplementationWiki[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…>. Additional Materials RDS Call for Volunteers presentation[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_pa…> Contact If you have any questions, please contact Margie Milam or Karen Mulberry atreviews(a)icann.org<mailto:reviews@icann.org>.

1 0

ICANN Policy staff Workshop 23 - 27 January 2017
by Nathalie Peregrine 12 Jan '17

12 Jan '17

Dear all, ICANN Policy staff will be holding its annual Policy Workshop in Los Angeles from Monday 23 January 2017 to Friday 27 January 2017. Staff will be replying to email requests, but there will be delays. Thank you for your understanding, GNSO SO/AC Support

1 0

FOR REVIEW & DISCUSSION: Draft GNSO Block Schedule for ICANN58
by Mary Wong 12 Jan '17

12 Jan '17

Dear Councilors, Please find attached the draft GNSO Block Schedule for ICANN58 that the Council leadership has been working on. I believe they will have additional suggestions and updates for everyone shortly, but the idea was to get it out to you all now to aid in planning, especially in relation to any session requests that your respective Stakeholder Groups and Constituencies may be submitting for this meeting. This will also be a discussion item for the Council meeting scheduled for 19 January. Thanks and cheers Mary Mary Wong Senior Policy Director Internet Corporation for Assigned Names and Numbers (ICANN) Email: mary.wong(a)icann.org Telephone: +1-603-5744889

1 0

Re: [council] GNSO Council Mailing list migration & new archives
by Marika Konings 10 Jan '17

10 Jan '17

Dear All, Please note that this transition will now also allow for observer subscription to the Council mailing list. As a reminder, observer status allows for receiving emails but does not provide any posting rights. This may facilitate those interested in Council activities to follow Council discussions instead of having to go and check the mailing list archives. This is already a standard feature for all GNSO WG mailing lists. Please let staff know if you have any concerns about going ahead and implementing this feature and communicating this accordingly to SG/Cs as well as on the GNSO web-site. Best regards, Marika From: <owner-council(a)gnso.icann.org> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Tuesday, January 10, 2017 at 8:35 AM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org>, Berry Cobb <mail(a)berrycobb.com> Subject: [council] GNSO Council Mailing list migration & new archives Dear councilors, The mailing list software (Majordomo) used for running the GNSO Council mailing list is at the end of its life. For security reasons ICANN IT, will be migrating the list to a new platform (Mailman) on which all of the GNSO mailing lists will now be hosted. The list migration will take place on Saturday, January 14, 2017 at 01:00 am UTC. You should see only cosmetic differences between the old and the new platform. The email address will remain the same. However, the web archive will be at a new URL: https://mm.icann.org/pipermail/council/ For historical purposes the old URL and data will remain intact but it will no longer receive updates: https://gnso.icann.org/mailing-lists/archives/council/[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_mailing…> Staff will ensure that both old and new archives be visible both on the wiki and on the website. Please let us know if you have any questions, Kind regards, Nathalie

1 0