October 2015 - council - lists.icann.org

Agendas GNSO Working Sessions Saturday & Sunday
by Glen de Saint Géry Oct. 16, 2015

Oct. 16, 2015

Dear All, Please find the links to the agendas for the GNSO Working Sessions on Saturday and Sunday that will take place in WICKLOW H2 https://community.icann.org/display/gnsocouncilmeetings/GNSO+Working+Sessio… https://community.icann.org/display/gnsocouncilmeetings/GNSO+Working+Sessio… See you there ! 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<http://gnso.icann.org/>

1 0

IETF issues relevant to the GNSO
by David Cake Oct. 16, 2015

Oct. 16, 2015

A couple of council meetings I undertook to keep council up to date on some issues relevant to the GNSO happening within the IETF DNSOP working group. As described in a previous update to council, a recent RFC has placed the .onion TLD on the Special Use Names registry, which is a list of TLD names (maintained by IANA) that the IETF has recommended to be retained for special uses, and therefore should not be delegated by ICANN. While this RFC did go through, it was controversial and there are several other names that have in the past been proposed for the Special Use Names that may still be proposed again. There is now a suggestion that the RFC 6761 process for reserving Special Use Names needs some work, and the DNSOP group is working on how to do this. Currently a small design group has been formed. How the RFC 6761 Special Use Names interacts with ICANN (and by implication, the GNSO, as such names are generally gTLDs) is expected to be clarified by these efforts, and I think it is important that we maintain aware of that process, and that documents produced are reviewed with a focus on GNSO/ICANN processes. I will endeavour to do so, and I will keep the GNSO Council informed. David

1 0

SSAC Activities Update ICANN 54 to the GNSO Council on 18 October
by Julie Hedlund Oct. 16, 2015

Oct. 16, 2015

Dear GNSO Councillors, For reference please see the attached slides for the SSAC Activities Update ICANN 54 to the GNSO Council on scheduled on Sunday, 18 October from 14:30 to 15:00. Details concerning the update and the slides also are posted to the wiki at: https://community.icann.org/display/gnsocouncilmeetings/GNSO+Working+Session +Dublin+Sunday+2015-10-18. Best regards, Julie Julie Hedlund, Director, SSAC Support

1 0

Updated GNSO Project list for your review
by Glen de Saint Géry Oct. 16, 2015

Oct. 16, 2015

Dear Councillors, Attached please find the updated GNSO Project list for your review. Please let us 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<http://gnso.icann.org/>

1 0

GNSO Wrap-Up Session Thursday
by Glen de Saint Géry Oct. 15, 2015

Oct. 15, 2015

Dear Councillors, The GNSO wrap-up session on Thursday will take place in Wicklow H2 from 12 :30-13 :30 (note time change please) and box lunches will be served. 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<http://gnso.icann.org/>

1 0

Proposed GNSO Public Council Meeting Part II: Administrative Agenda, 21st October 2015 at 14:15 UTC 15:15 IST.
by Glen de Saint Géry Oct. 15, 2015

Oct. 15, 2015

Dear Councillors Please find the proposed GNSO Public Council Meeting Part II: Administrative Agenda, Dublin meeting on 21st October 2015 at 14:15 UTC 15:15 IST. also published on the Wiki at: https://community.icann.org/display/gnsocouncilmeetings/GNSO+Public+Council… And on the meeting page https://meetings.icann.org/en/dublin54/schedule/wed-gnso-council-admin This agenda was established according to the GNSO Council Operating Procedures,<http://gnso.icann.org/en/council/op-procedures-24jun15-en.pdf> approved and updated on 24 June 2015. 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: 14:15 UTC 07:15 Los Angeles; 10:15 Washington; 15:15 London; 16:15 Paris; Meeting Times 14:15 UTC http://tinyurl.com/pqlrcga Main Meeting Page: https://meetings.icann.org/en/dublin54/schedule/wed-gnso-council-admin Dial-in numbers will be sent individually to Council members. Councillors should notify the GNSO Secretariat in advance if a dial out call is needed. Item 1: Seating of the 2015 / 2016 Council (20 mins) 1.1 Roll Call 1.2 Statements of interest Keith Drazek - SOI<https://community.icann.org/display/gnsosoi/Keith+Drazek+SOI> Registries Stakeholder Group Anthony Harris - SOI<https://community.icann.org/display/gnsosoi/Tony+Harris+SOI> Internet Service & Connectivity Providers Constituency Johan Helsingius - SOI<https://community.icann.org/display/gnsosoi/Johan+%28Julf%29+Helsingius+SOI> Nominating Committee Appointee Wolf-Ulrich Knoben - SOI<https://community.icann.org/display/gnsosoi/Wolf-Ulrich+Knoben+SOI> Internet Service & Connectivity Providers Constituency Rubens Kuhl - SOI<https://community.icann.org/display/gnsosoi/Rubens+Kuhl+SOI> Registries Stakeholder Group Paul McGrady- SOI<https://community.icann.org/display/gnsosoi/Paul+D.+McGrady%2C+Jr.+SOI> Intellectual Property Constituency Stefania Milan - SOI<https://community.icann.org/display/gnsosoi/Stefania+Milan+SOI> Non Commercial Stakeholder Group Jennifer Standiford -SOI<https://community.icann.org/display/gnsosoi/Jennifer+Standiford+SOI> Registrar Stakeholder Group Hsu Phen Valerie Tan - SOI<https://community.icann.org/display/gnsosoi/Hsu+Phen+Valerie+Tan+SOI> Nominating Committee Appointee 1.3 Review/amend agenda Item 2: Election of the Chair (30 mins) Two nominations were received for this position, James Bladel and Heather Forrest. The GNSO Council held a question & answer session over the weekend with both candidates. The Council will proceed to elect the chair according to the GNSO Operating Procedures. GNSO Operating Procedures http://gnso.icann.org/en/council/op-procedures-24jun15-en.pdf Note: Section 2.2 Officer Elections: Chair and Vice-Chairs (see Appendix 1 below) Item 3: Any Other Business (10 mins) Reminder: The Council development meeting will take place in Liffey MR2 in the Dublin Convention Center on Friday 23 October 2015, 09:00 for a prompt start at 09:30 Appendix 1: Excerpt from GNSO Operating Procedures (Section2.2) http://gnso.icann.org/en/council/op-procedures-24jun15-en.pdf 2.2 Officer Elections: Chair and Vice-Chairs The GNSO Council shall select the GNSO Chair and two Vice-Chairs as follows: 1. The GNSO Chair shall be elected by a 60 percent vote of each house. 2. Each house will be allowed to nominate one candidate for GNSO Council Chair. Each house is responsible for determining how to nominate its candidate. A candidate for GNSO Council Chair does not need to be a member of a house, but must be a member of the GNSO Council. Should a Chair be elected from outside of the houses that Chair will be a non-voting Chair. * All ballots will include the "none of the above" option. In the event that a 60 percent vote of each house selects the "none of the above" option, each house will commence a new nomination period of not longer than 15 days. An election for the new nominees will be scheduled for no sooner than 30 days after the unsuccessful vote. * In the case of a tie for the most votes between the two candidates, or between a candidate and "none of above," a second election will be held no sooner than 30 days. The candidates shall remain the same for this second election. In the case this second election also results in a tie, each house will commence a new nomination period of not longer than 15 days. An election for the new nominees will be rescheduled for no sooner than 30 days after the unsuccessful vote. * The leading candidate will be defined as the one with the highest score. The score is calculated by adding together the voting percentages attained from each house. The highest percentage attainable in each house is 100. Thus, the maximum score a candidate can achieve is 200 as a result of attaining 100 percent of the votes from the contracted party house and 100 percent from the non-contracted party house (100 percent + 100 percent = score of 200). In case neither candidate reaches the 60 percent of each house threshold, a second ballot will be held between the leading candidate and "none of the above." * In case neither candidate reaches the 60 percent of each house threshold and the candidates do not tie, a second runoff ballot will be held between the leading candidate and "none of the above." * If the single candidate does not reach the 60 percent of each house threshold in the runoff ballot, then each house will commence a new nomination period of not longer than 15 days. An election for the new nominees will be rescheduled for no sooner than 30 days after the unsuccessful runoff ballot. 3. Each house shall select a Council Vice-Chair from within its respective house. 4. A Chair may not be a member of the same Stakeholder Group of either of the Vice-Chairs. 5. The Chair and Vice-Chairs shall retain their votes (if any) in their respective houses (if any). 6. In the event that the GNSO Council has not elected a GNSO Council Chair by the end of the previous Chair's term, the Vice-Chairs will serve as Interim GNSO Co-Chairs until a successful election can be held. 7. The Council shall inform the Board and the Community appropriately and post the election results on the GNSO website within 2 business days following each election and runoff ballot, whether successful or unsuccessful. Appendix 2: GNSO Council Voting Thresholds (ICANN Bylaws, Article X, Section 3) http://gnso.icann.org/en/council/appendix-1-gnso-council-voting-results-25o… 9. Except as otherwise specified in these Bylaws, Annex A hereto, or the GNSO Operating Procedures, the default threshold to pass a GNSO Council motion or other voting action requires a simple majority vote of each House. The voting thresholds described below shall apply to the following GNSO actions: 1. Create an Issues Report: requires an affirmative vote of more than one-fourth (1/4) vote of each House or majority of one House. 2. 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. 3. Initiate a PDP Not Within Scope: requires an affirmative vote of GNSO Supermajority. 4. 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. 5. Approve a PDP Team Charter for a PDP Not Within Scope: requires an affirmative vote of a GNSO Supermajority. 6. 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. 7. 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. 8. 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. 9. Approve a PDP Recommendation With a GNSO Supermajority: requires an affirmative vote of a GNSO Supermajority, 10. 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. 11. 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. 12. 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." http://gnso.icann.org/en/council/appendix-1-gnso-council-voting-results-25o… Appendix 3: Absentee Voting Procedures (GNSO Operating Procedures 4.4<http://gnso.icann.org/council/gnso-operating-procedures-22sep11-en.pdf> [PDF, 380 KB]) 4.4.1 Applicability Absentee voting is permitted for the following limited number of Council motions or measures. 1. Initiate a Policy Development Process (PDP); 2. Approve a PDP recommendation; 3. Recommend amendments to the GNSO Operating Procedures (GOP) or ICANN Bylaws; 4. 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 14:15 ---------------------------------------------------------------------------- California, USA (PDT<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) UTC-7+1DST 07:15 San José, Costa Rica UTC-5+1DST 09:15 Iowa City, USA (CDT<http://fr.wikipedia.org/wiki/UTC%E2%88%9206:00>) UTC-5+1DST 09:15 New York/Washington DC, USA (EST) UTC-4+1DST 10:15 Rio de Janiero, Brazil (BRST) UTC-2+1DST 12:15 Buenos Aires, Argentina (ART<http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) UTC-3+0DST 11:15 London, United Kingdom (BST) UTC+0DST 15:15 Bonn, Germany (CET) UTC+1+0DST 16:15 Amsterdam, Netherlands(CET) UTC+1+0DST 16:15 Cairo, Egypt, (EET) UTC+2+0DST 16:15 Istanbul, Turkey (EEST) UTC+2+0DST 17:00 Singapore (SGT) UTC+8+0DST 22:15 Sydney, Australia (AEDT) UTC +01 :15 Perth, Australia (WST<http://timeanddate.com/library/abbreviations/timezones/au/wst.html>) UTC+8+0DST 22:15 (next day) ---------------------------------------------------------------------------- DST starts/ends on last Sunday of October 2015, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com http://tinyurl.com/pqlrcga 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<http://gnso.icann.org/>

1 0

Saturday, 17 October shuttles
by Glen de Saint Géry Oct. 15, 2015

Oct. 15, 2015

Dear all, We have arranged shuttles to transfer CCGW / ALAC / GNSO members for their Saturday ,17 October meetings. You can find below the schedule. Please communicate this with your groups. 17 October 2015 Shuttle - Jurys Inn Christchurch - Jurys Inn Parnell Street - CCD 07:30 - pick up from Jurys Inn Christchurch 07:45 - pick up from Jurys Inn Parnell Street 08:00 - Arrive to CCD 08:15 - pick up from Jurys Inn Christchurch 08:30 - pick up from Jurys Inn Parnell Street 08:45 - Arrive to CCD 09:00 - pick up from Jurys Inn Christchurch 09:15 - pick up from Jurys Inn Parnell Street 09:30 - Arrive to CCD Return from CCD to Jurys Inn Parnell Street and Jurys Inn Christchurch 18:00 18:45 Best Erhan Kiraner Senior Meeting Planner Internet Corporation for Assigned Names and Numbers ( ICANN ) Direct line : +90 212 999 62 11 Mobile : +90 533 341 90 50 Email : erhan.kiraner(a)icann.org<mailto:erhan.kiraner@icann.org> www.icann.org<http://www.icann.org>

1 0

Proposed Agenda for the GNSO Council Public Meeting Part 1 on 21st October 2015 at 13:00 IST (12:00 UTC)
by Glen de Saint Géry Oct. 15, 2015

Oct. 15, 2015

Dear Councillors, Welcome to Dublin! Please find the proposed Agenda for the GNSO Council Public Meeting Part 1 on 21st October 2015 at 13:00 IST (12:00 UTC) The Council meetings will take place in Liffey B. There will be the usual tea/coffee/pastries for the councilors only at the back of the meeting room. This agenda was established according to the GNSO Council Operating Procedures,<http://gnso.icann.org/en/council/op-procedures-24jun15-en.pdf> approved and updated on 24 June 2015. 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: 12:00 UTC http://tinyurl.com/nujcmrc 05:00 Los Angeles; 08:00 Washington; 13:00 Dublin; 15:00 Istanbul; 20:00 Perth https://meetings.icann.org/en/dublin54/schedule/wed-gnso-council Councilors should notify the GNSO Secretariat in advance if they will no able to attend and need a dial out call. ___________________________________________ Item 1: Administrative matters (5 minutes) 1.1 - Roll call 1.2 - Updates to Statements of Interest 1.3 - Review/amend agenda. 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes of the GNSO Council meetings of 24 June, 23 July 2015 and 24 September will be posted as approved on xxxxxx 2015 Minutes of the GNSO Council meeting of 3 September 2015 were posted as approved on 26 September 2015. Item 2: Opening Remarks / Review of Projects & Action List (10 minutes) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List<http://gnso.icann.org/meetings/projects-list.pdf> and Action List<https://community.icann.org/display/gnsocouncilmeetings/Action+Items> Item 3: Consent agenda (0 minutes) There are no items on the consent agenda for this meeting. Item 4: MOTION - Adoption of Final Report from the Data & Metrics for Policy Making Working Group (15 minutes) This Working Group was chartered<http://gnso.icann.org/en/issues/dmpm-charter-23jan14-en.pdf> by the GNSO Council in January 2014 to explore the development of reporting and metrics processes and/or appropriate standardized methodologies that can better inform fact-based policy development and decision making. The WG published<http://gnso.icann.org/en/issues/dmpm-initial-29jul15-en.pdf> its Initial Report for public comment on 29 May 2015, and submitted a Final Report<http://gnso.icann.org/en/issues/dmpm-final-09oct15-en.pdf> to the GNSO Council on 9 October that took into account the public comments received. Here the Council will discuss the WG's recommendations, and vote on whether or not to adopt the Final Report as submitted. 4.1 - Presentation of the motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+21+October+…> (Volker Greimann) 4.2 - Discussion 4.3 - Council Vote (threshold: simple majority) Item 5: MOTION - Adoption of Next Generation gTLD Registration Directory Services (RDS) to Replace WHOIS PDP WG Charter (15 minutes) In November 2012 the ICANN Board requested<https://www.icann.org/resources/board-material/resolutions-2012-11-08-en#1.a> an Issue Report on the purpose of collecting and maintaining gTLD registration data, and on solutions to improve accuracy and access to gTLD registration data, as part of a Board-initiated GNSO Policy Development Process (PDP). Concurrently, the Board directed the launch of a new effort to redefine the purpose of collecting, maintaining and providing access to gTLD registration data, and to consider safeguards for protecting data, as a foundation for new gTLD policy and contractual negotiations, as appropriate. In June 2014 the Expert Working Group convened as a result of the Board resolution published its Final Report<https://www.icann.org/en/system/files/files/final-report-06jun14-en.pdf>. In April 2015 a group comprising Board and GNSO Council members finalized a proposed Process Framework<https://community.icann.org/download/attachments/49359634/EWG-Process%20Gro…> to guide the work of the PDP. In July 2015 an updated Preliminary Issue Report was published at the Board's request for public comment, following which a Final Issue Report taking into account public comments received was prepared and submitted to the GNSO Council on 7 October 2015 (see http://<http://whois.icann.org/sites/default/files/files/final-issue-report-next-ge…>whois.icann.org/sites/default/files/files/final-issue-report-next-generatio…<http://whois.icann.org/sites/default/files/files/final-issue-report-next-ge…>). Here the Council will review the Final Issue Report and vote to approve the charter<http://gnso.icann.org/en/drafts/whois-ng-gtld-rds-charter-07oct15-en.pdf> for the Working Group to be formed to conduct this Board-initiated PDP. 5.1 - Presentation of the motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+21+October+…> (Susan Kawaguchi) 5.2 - Discussion 5.3 - Council Vote (threshold: an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House) Item 6: DISCUSSION - Letters from the Standing Committee on GNSO Improvements (10 minutes) In March 2015, the GNSO Council had requested that its Standing Committee on GNSO Improvements (SCI): (1) consider<http://gnso.icann.org/en/issues/sci-review-request-05mar15-en.pdf> whether or not the GNSO Operating Procedures needed further modifications to deal with questions relating to a possible overlap between the rules on resubmission of a motion and the Council's ability to waive the deadline for submission of motions; and (2) document<http://gnso.icann.org/en/drafts/sci-review-motions-05mar15-en.pdf> the Council's existing custom in relation to the proposal and seconding of motions for voting, with a further request that should the SCI believe that additions to the GNSO Operating Procedures are needed to handle the matter, it should propose appropriate language for that purpose. On 9 October 2015, the SCI responded to both of the Council's request by letter (see http://gnso.icann.org/en/correspondence/aikman-scalese-vansnick-to-robinson… and http://gnso.icann.org/en/correspondence/aikman-scalese-vansnick-to-robinson…) Here the Council will consider the SCI's recommendations, and determine whether or not further action is required. 6.1 - Update (Avri Doria) 6.2 - Discussion 6.3 - Next steps Item 7: DISCUSSION OF POSSIBLE ACTION - Request from ICANN Board concerning possible policy work on Replacement Insurance Requirements for ICANN-accredited Registrars (10 minutes) On 28 September 2015, the ICANN Board adopted a resolution<https://www.icann.org/resources/board-material/resolutions-2015-09-28-en#2.e> waiving the insurance requirement in the 2009 and 2013 Registrar Accreditation Agreements (RAAs). The resolution also requests that the GNSO consider whether policy work on replacement insurance requirements should be undertaken in light of ICANN's Statement of Registrar Accreditation Policy. Board Chairman Steve Crocker has since written<http://gnso.icann.org/en/correspondence/crocker-to-robinson-12oct15-en.pdf> to the GNSO Council confirming the Board's request. Here the Council will discuss the Board request and consider appropriate next steps. 7.1 - Update (Jonathan Robinson) 7.2 - Discussion 7.3 - Next steps Item 8: DISCUSSION OF POSSIBLE ACTION - Request from ICANN Board concerning possible policy work on Exclusive Registry Access to Generic Strings (10 minutes) On 27 July 2015 the ICANN Board requested<https://www.icann.org/en/system/files/correspondence/crocker-to-robinson-27…> that the GNSO specifically include the issue of exclusive registry access for generic strings serving a public interest goal as part of the policy work it is planning to initiate on subsequent rounds of the New gTLD Program. Following Council discussion, the GNSO Chair sent a letter<http://gnso.icann.org/en/correspondence/robinson-to-crocker-15sep15-en.pdf> to the Board requesting input on the subject, especially regarding the definition of the "global public interest". On 12 October the Board responded<http://gnso.icann.org/en/correspondence/crocker-to-robinson-gtld-strings-12…>, noting the GNSO's concerns and expressing its support for the GNSO's consideration of the issue of exclusive registry access to generic strings as part of its work on subsequent rounds of the New gTLD Program. Here the Council will discuss the Board's letter and consider appropriate next steps. 8.1 - Update (Jonathan Robinson) 8.2 - Discussion 8.3 - Next steps Item 9: DISCUSSION OF POSSIBLE ACTION - Final Report of the Independent Examiner on GNSO Review (10 minutes) As part of ICANN's Bylaws-mandated periodic review of its structures, the ICANN Board's Structural Improvements Committee appointed Westlake Governance as the independent examiner to conduct the current review of the performance and operations of the GNSO. A GNSO Working Party, chaired by former Councillor Jennifer Wolfe and comprising representatives of all the GNSO's Stakeholder Groups and Constituencies, was formed to consult with Westlake over the design and conduct of the review. Westlake's Draft Report was published<https://www.icann.org/public-comments/gnso-review-draft-2015-06-01-en> for public comment on 1 June 2015. Following feedback received, including from the GNSO Working Party, Westlake published its Final Report<https://www.icann.org/en/system/files/files/gnso-review-final-15sep15-en.pdf> on 15 September. Here the Council will discuss the recommendations of the GNSO Working Party on particular aspects of the Final Report, and consider possible implementation of some or all of these recommendations. 9.1 - Update (Jennifer Wolfe) 9.2 - Discussion 9.3 - Next steps Item 10: COUNCIL DISCUSSION - New ICANN Meeting Strategy (10 minutes) On 14 July 2015 the GNSO Chair had sent a letter<http://gnso.icann.org/en/correspondence/robinson-to-crocker-14jul15-en.pdf> to the ICANN Board, informing them of the GNSO's progress in developing and adapting community plans to conform to the new ICANN meeting strategy, particularly in relation to the new format for Meeting B. The GNSO's current draft plan<http://gnso.icann.org/en/drafts/gnso-council-proposal-new-meeting-strategy-…> has also been shared with other ICANN Supporting Organizations and Advisory Committees, each of which have also begun planning for the new meeting strategy within their communities. Here the Council will discuss any additional actions it may wish to take to ensure that its planning is coordinated with that of the Board's as well as the other SOs and ACs. 10.1 - Update (Volker Greimann / Marika Konings) 10.2 - Discussion 10.3 - Next steps Item 11: Any Other Business and Open Microphone 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.) Reference (Coordinated Universal Time) UTC 12:00 Local time between March and October, Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) UTC-7+1DST 05:00 San José, Costa Rica UTC-5+1DST 07:00 Iowa City, USA (CDT<http://fr.wikipedia.org/wiki/UTC%E2%88%9206:00>) UTC-5+1DST 07:00 New York/Washington DC, USA (EST) UTC-4+1DST 08:00 Rio de Janiero, Brazil (BRST) UTC-3+0DST 10:00 Montevideo, Uruguay (UYST<http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) UTC-3+0DST 09:00 Buenos Aires, Argentina (ART<http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) UTC-3+0DST 09:00 London, United Kingdom (BST) UTC+0DST 13:00 Bonn, Germany (CET) UTC+1+0DST 14:00 Cairo, Egypt, (EET) UTC+2+0DST 14:00 Istanbul, Turkey (EEST) UTC+3+0DST 15:00 Ramat Hasharon, Israel(IDT<http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.…>) UTC+3+0DST 15:00 Perth, Australia (WST<http://timeanddate.com/library/abbreviations/timezones/au/wst.html>) UTC+8+1DST 20:00 Sydney/Hobart, Australia (AEDT) UTC+11+1DST 23:00 ---------------------------------------------------------------------------- DST starts/ends on last Sunday of October 2015, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> http://tinyurl.com/oj7p77g 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<http://gnso.icann.org/>

1 0

FW: [Soac-infoalert] The CCWG-Accountability Co-Chairs finalized Schedule for ICANN54
by Jonathan Robinson Oct. 14, 2015

Oct. 14, 2015

From: David Olive [mailto:david.olive@icann.org] Sent: 14 October 2015 15:20 To: soac-infoalert(a)icann.org Cc: Mathieu Weill <mathieu.weill(a)afnic.fr>; León Felipe Sánchez Ambía <leonfelipe(a)sanchez.mx>; Hillary Jett <hillary.jett(a)icann.org>; Thomas Rickert <thomas(a)rickert.net> Subject: [Soac-infoalert] The CCWG-Accountability Co-Chairs finalized Schedule for ICANN54 The CCWG-Accountability co-Chairs finalized yesterday their schedule for ICANN54. Please see below for more details: Friday, 16 October 8:30-18:30 CCWG-Accountability Face-to-Face Meeting Goal: Finalize public comment assessments based on WP outcomes, list areas of consensus and refinements, identify a candidate way forward on outstanding issues. Saturday, 17 October 18:30-12:00 CCWG-Accountability Sub-Team Breakouts Goal: Break out sessions facilitated by XPlane to flesh out candidate way forward. Monday, 19 October 10:15-11:45 CCWG-Accountability Engagement Session I Goal: Present status of the work, solicitation of community feedback on specific aspects. Monday, 19 October 14:00-18:30 CCWG-Accountability Working Session I Goal: Review and refine outcome of break out sessions, initial assessment of timeline for finalization of report. Tuesday, 20 October Goal: SO/AC engagement (not a CCWG-Accountability session as such). Wednesday, 21 October 17:00-20:00 CCWG-Accountability Engagement Session II Goal: Present status of the work, solicitation of community feedback on specific aspects, particularly on progress made during the week and open issues. * Note: Given the concerns with the 60 minute overlap with the GAC Communiqué Drafting Session, no discussions on Stress Test 18 will take place prior to 18:00* Thursday, 22 October 08:00-10:30 CCWG-Accountability Working Session II Goal: Taking stock; finalizing work plan beyond Dublin including timeline. All resources (including blogs) are being updated in the next few hours to reflect these times. In addition, the CCWG-Accountability co-Chairs will be releasing a statement shortly. -- Hillary Jett Communications Coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 (202) 674-3403 Email: hillary.jett(a)icann.org <mailto:hillary.jett@icann.org>

1 0

FW: [CORRESPONDENCE] Letter from Steve Crocker to Jonathan Robinson RE: Exclusive Access/Public Interest
by Jonathan Robinson Oct. 13, 2015

Oct. 13, 2015

All, FYI and for further consideration. Jonathan From: Wendy Profit [mailto:wendy.profit@icann.org] Sent: 12 October 2015 19:29 To: Jonathan Robinson <jonathan.robinson(a)ipracon.com> Cc: Glen de Saint Géry <Glen(a)icann.org>; icann-board(a)icann.org; Nora Abusitta <nora.abusitta(a)icann.org>; Secretary <secretary(a)icann.org> Subject: [CORRESPONDENCE] Letter from Steve Crocker to Jonathan Robinson RE: Exclusive Access/Public Interest Dear Jonathan Robinson, Please find the attached letter from Steve Crocker in response to your letter dated 22 September 2015 concerning exclusive registry access for gTLDs and the topic of global public interest. Kind regards, Wendy Profit ICANN Board Operations Specialist 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 Mobile: 1-310-773-6811 Office: 1-310-578-8695

1 0