June 2016 - council - lists.icann.org

FW: [CCWG-ACCT] [Blog] Launching Work Stream 2 in Helsinki
by James M. Bladel 23 Jun '16

23 Jun '16

Councilors - Please see announcement/blog article below, regarding the launch of Accountability WS2. Thanks- J. Launching Work Stream 2 in Helsinki It has been a momentous month for the ICANN community. On behalf of the Cross Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability), we welcome the U.S. Government report<https://www.ntia.doc.gov/report/2016/iana-stewardship-transition-proposal-a…> that our recommendations meet their requirements. We are actively engaged in the prep work needed for a timely implementation of these new accountability mechanisms into ICANN's ecosystem. Looking ahead, our ongoing work to advance ICANN's accountability is not complete. The CCWG-Accountability identified nine additional areas where community, staff and Board accountability can be improved. These target areas, recognized as Work Stream 2, are outlined in Recommendation #12<https://community.icann.org/pages/viewpage.action?pageId=58723723&preview=/…> of the Work Stream 1 Report. To launch Work Stream 2, the CCWG-Accountability will be holding a full-day face-to-face meeting in Helsinki on the Sunday before ICANN56 (26 June 2016). All Work Stream 2 topics<https://community.icann.org/pages/viewpage.action?pageId=58723723&preview=/…> will be covered during the session. The full agenda can be found here<mailto:https://community.icann.org/x/rBWOAw>. The topics that will be discussed are: · Additional transparency considerations · Diversity across ICANN · Clarifying the lines of accountability for ICANN staff · A work plan to enhance accountability of Supporting Organizations and Advisory Committees · A Framework of Interpretation on respecting human rights within ICANN's limited mission and scope · Expanding the list of jurisdictions identified in ICANN's contracts, for purposes of resolving contractual disputes [1]<https://www.icann.org/news/blog/launching-work-stream-2-in-helsinki#_ftn1> · Role and function of the Ombudsman · Guidelines for good faith conduct in ICANN Board member removal discussions · Engagement process between a complainant and ICANN prior to an Independent Review Process We encourage all members, participants and interested observers that are not attending ICANN56 to follow along with our discussions via our Adobe Room<https://icann.adobeconnect.com/hel56-halla>. In addition, we will be circulating notes on each of the topics to the publicly archived<http://mm.icann.org/pipermail/accountability-cross-community/> CCWG-Accountability mailing list to serve as the base of our discussions moving forward. If you are interested in debating these Work Stream 2 topics and want to become a participant or observer of the CCWG-Accountability, please send an email to acct-staff(a)icann.org<mailto:acct-staff@icann.org>. For those of you who will be joining us in Helsinki, safe travels and we look forward to seeing you soon! CCWG-Accountability co-Chairs, Thomas Rickert, León Sanchez, Mathieu Weill ________________________________ [1]<https://www.icann.org/news/blog/launching-work-stream-2-in-helsinki#_ftnref1> ICANN's jurisdiction, place of incorporation and headquarters location are not within the scope of Work Stream 2 deliberations.

1 0

CCWG - Accountability Members, and Work Stream 2
by James M. Bladel 23 Jun '16

23 Jun '16

Dear Council Colleagues - At the establishment of the CCWG-Accountability In November 2014, each GNSO Stakeholder Group confirmed a member to join this CCWG, in addition to the GNSO appointed co-chair (Thomas Rickert), the members are/were: Becky Burr, Steve DelBianco, Robin Gross, and myself. Now, the CCWG-Accountability is transitioning from Work Stream 1 (WS1) items associated with the IANA transition, and beginning work on Work Stream 2 (WS2). This is therefore an appropriate opportunity to ask each Stakeholder Group to re-confirm that its member selection for this CCWG. There are two questions at hand for each SG: Will the current GNSO appointed member continue to serve through Work Stream 2? If not, who will assume this role beginning in Helsinki and going forward? From my own view, I do not plan to continue as a member, and plan to ask the RrSG to find a replacement. Other members may have similar plans. Finally, once we have confirmed or re-confirmed the slate CCWG members, we might also take this opportunity to discuss the Council¹s expectations of its appointed members, if any. Please coordinate with your respective ExComs and report back to the Council with either (a) re-confirmation of your SG's current CCWG-ACCT member or (b) the name and affiliation of their replacement for WS2. We need this information in advance of Helsinki, so please respond on the list by 20 JUN 2016. Thank you, J.

2 2

REVIEW: WORKING GROUP UPDATE – Activities of the Cross Community Working Group on Internet Governance
by Glen de Saint Géry 23 Jun '16

23 Jun '16

Dear Councillors, In preparation for the GNSO Council Public meeting, please find attached the Cross Community Working Group report on Internet Governance which Rafik Dammak and Olivier Crépin-Leblond will speak to in Item 9: WORKING GROUP PROGRESS REPORT – Activities of the Cross Community Working Group on Internet Governance Thank you. Kind regards, Glen

1 0

Re: [council] FW: [community-finance] Report on Draft ICANN FY17 Operating Plan & Budget and Five-Year Operating Plan Update
by Marika Konings 23 Jun '16

23 Jun '16

GNSO Councilors, Please find attached and extraction of the responses by ICANN Finance staff to the Council’s public comment submission regarding ICANN’s FY17 draft budget. The MS Word document only contains responses to the GNSO Council, as the original Public Comment report is well over 150 pages. I also attached the original submission to the PCF for your reference. Links to the PCF and report are posted below. It is expected that the ICANN Board will deliberate and vote on the FY17 Draft budget at its next meeting. Public Comment Forum: https://www.icann.org/public-comments/op-budget-fy17-five-year-2016-03-05-en PCF Report from staff: https://www.icann.org/en/system/files/files/report-comments-op-budget-fy17-… Please let the Policy staff know if you have any additional questions or require clarification. Thank you. Marika Marika Konings Senior Policy Director & Team Leader for the GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses and visiting the GNSO Newcomer pages. From: <owner-council(a)gnso.icann.org> on behalf of Marika Konings <marika.konings(a)icann.org> Date: Tuesday 7 June 2016 at 02:07 To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] FW: [community-finance] Report on Draft ICANN FY17 Operating Plan & Budget and Five-Year Operating Plan Update For your information. Best regards, Marika Marika Konings Senior Policy Director & Team Leader for the GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses and visiting the GNSO Newcomer pages. From: <community-finance-bounces(a)icann.org> on behalf of Leo Vegoda <leo.vegoda(a)icann.org> Date: Monday 6 June 2016 at 17:33 To: "community-finance(a)icann.org" <community-finance(a)icann.org> Subject: [community-finance] Report on Draft ICANN FY17 Operating Plan & Budget and Five-Year Operating Plan Update Dear Community Leaders and Members, I have attached the Report on Public Comments for the Draft ICANN FY17 Operating Plan & Budget and Five-Year Operating Plan Update to this message. The scale of comments we received this year is much higher than last year. Providing substantive responses to the comments means that the report is over 100 pages long. There is a high-level summary of the comments we received, organized by theme, at the start of the report. The detailed responses are structured using the same themes in an appendix to the main report. We appreciate that people might want to sort through the responses differently, so we have also provided them in a spreadsheet that can be sorted in a variety of ways, for the convenience of readers. As spreadsheets are not an ideal publication format for structured text, some of the formatting in the formal report is not present in this format. We hope you find this report helpful. Kind regards, Leo Vegoda

1 0

ICANN56: GNSO Sessions How to Get Organised and Remote Participation Details
by Nathalie Peregrine 22 Jun '16

22 Jun '16

Dear all, Pre-ICANN meeting email inboxes are full at the best of times, so the GNSO SO/AC Support team has done away with the individual Remote Participation (RP) details and have created a one-stop wiki page for all your RP queries. In addition to this, ICANN meetings' team has put together a new ICANN meeting website which allows you to download all GNSO-related meetings to your inbox calendar in one go. 2 LINKS TO BOOKMARK NOW: ICANN56 Meeting Schedule<https://icann562016.sched.org/> <https://community.icann.org/x/yCWOAw>GNSO Remote Participation w<https://community.icann.org/x/yCWOAw>iki page<https://community.icann.org/x/yCWOAw> Step 1 Go to the Meeting Schedule webpage, and if not done yet, create a log in when prompted. Every session on the schedule ca be selected and added to your calendar inbox. To get a general description of the session, please hover your mouse over the session title and a summary of the session will appear as well as a "add to my schedule" option. Step 2 Please download the ICANN56 Mobile App to automatically receive the latest updates to your schedule (available on Apple and Android products, look for "ICANN56") Step 3 All Adobe Connect rooms (which can be found on the session information on the Meeting Schedule and on the GNSO Remote Participation wikip age) will provide audio streaming. If you cannot join an Adobe Connect room for a session, and will need to dial in with your phone, please refer to the GNSO Remote Participation wiki page for the audio pass codes and dial in numbers. Please also follow the previous steps if you wish to take part in the session over the phone. Glen de St Gery and Terri Agnew will be onsite to assist you directly. For all GNSO meeting related queries (RP or others), please email us at: gnso-secs(a)icann.org<applewebdata://FB60497E-61D8-4FE9-BF9C-EB238191E416/gnso-secs@icann.org> and we will be more than happy to assist! Kind regards, GNSO SO/AC Support team

1 0

Proposed agenda for the GNSO Council Public Meeting in Helsinki 30 June 2016 at 10:45
by Glen de Saint Géry 21 Jun '16

21 Jun '16

Dear Councillors, Please find the proposed agenda for the GNSO Council Public Meeting in Helsinki on 30 June 2016 at 10:45 UTC. Also published on the Wiki at: https://community.icann.org/display/gnsocouncilmeetings/Agenda+30+June+2016 and the GNSO website at: http://gnso.icann.org/en/meetings/agenda-council-30jun16-en.htm 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/aCOOAw 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: 07:45 UTC http://tinyurl.com/jgzq34d 00:45 Los Angeles; 03:45 Washington; 08:45 London; 10:45 Helsinki; 10:45 Istanbul; Hobart 17:45 https://meetings.icann.org/en/icann56-sched To join the event click on the link: Adobe Connect https://icann.adobeconnect.com/hel56-hallb 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 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 meeting of the GNSO Council on 12 May 2016 to be approved on 30 June 2016. Item 2: Opening Remarks / Review of Projects & Action List (5 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) Item 4: COUNCIL VOTE - Approval to Permanently Integrate Successful PDP Improvements into the GNSO Policy Development Process (10 minutes) In 2013, the GNSO Council in collaboration with ICANN staff gathered a number of ideas and suggestions that could be explored in order to improve and streamline the existing GNSO Policy Development Process (PDP). These ideas and suggestions were refined into ten possible PDP Improvements (see http://gnso.icann.org/en/drafts/pdp-improvements-table-16jan14-en.pdf). Many of these improvements were closely aligned with the recommendations of the ATRT2<https://www.icann.org/en/system/files/files/final-recommendations-31dec13-e…> in relation to the GNSO PDP. Staff was tasked to analyze and implement next steps for each of the ten items, including their launch in pilot format. The implementation status of these PDP Improvements was the subject of regular staff updates to the GNSO Council at ICANN Public Meetings. On 9 June 2016, staff submitted a memo<http://gnso.icann.org/en/drafts/memo-pdp-improvements-09jun16-en.pdf> to the GNSO Council that was intended to provide a final status update, including proposed next steps on how to integrate those Improvements that have been determined to be successful into permanent features of the GNSO PDP, and close out this project until such time as the Council either identifies further new improvements it deems worth exploring and/or elects to revisit those improvements that are currently considered unsuitable for implementation at this stage. 4.1 - Presentation of the motion<file:///C:\Users\Glen\AppData\Local\Microsoft\Windows\Temporary%20Internet%20Files\Content.Outlook\BTHAHPWK\community.icann.org\display\gnsocouncilmeetings\Motions+30+June+2016> (Donna Austin) 4.2 - Discussion 4.3 - Council vote (voting threshold: simple majority) Item 5: COUNCIL VOTE - Approval to Form a Drafting Team to Develop an Implementation Plan for New and Additional GNSO Powers and Obligations under the Revised ICANN Bylaws (15 minutes) On 21 April 2016 a revised version of the ICANN Bylaws was posted for public comment (see https://www.icann.org/public-comments/draft-new-bylaws-2016-04-21-en). The revisions were intended to reflect the proposals from the IANA Stewardship Transition Coordination Group (ICG) and Cross Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability), to be consistent with the community proposals relating to the IANA Stewardship Transition. On 25 May 2016, a further revised version of the Bylaws was posted, reflecting changes made as a result of public comments received (see https://www.icann.org/en/system/files/files/revised-new-bylaws-25may16-en.p…). To facilitate the Council's review of the new, additional and amended powers and obligations of the GNSO under the revised Bylaws, ICANN staff prepared a table<http://gnso.icann.org/en/drafts/revised-bylaws-notes-comments-procedures-14…> for discussion at ICANN56. In view of the fact that some of these powers and obligations will require additions and changes to the GNSO's procedures, the Council will consider a proposal to form a Drafting Team comprised of GNSO community members, to report back to the Council with an implementation plan no later than 31 July 2016. 5.1 - Presentation of the motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+30+June+2016> (Paul McGrady) 5.2 - Discussion 5.3 - Council vote (voting threshold: simple majority) Item 6: COUNCIL VOTE - Temporary Extension of Term of Current GNSO Liaison to the Governmental Advisory Committee (10 minutes) As part of a two-year pilot program initiated in June 2014, the GNSO Council and the Governmental Advisory Committee (GAC) had agreed, through its joint GAC-GNSO Consultation Group<https://community.icann.org/x/phPRAg>, to appoint a GNSO Liaison to the GAC. The purpose of the Liaison role was to facilitate more effective early engagement by the GAC in GNSO policy activities and to contribute toward better information flow between the two bodies. Following Consultation Group review<http://gnso.icann.org/en/drafts/review-liaison-gac-pilot-29feb16-en.pdf> of the pilot program, the Consultation Group recommended that the Liaison role be made a permanent one in March 2016. At its meeting on 14 April 2016, the Council approved the creation of this permanent Liaison role and a process for the application, selection and confirmation of a Liaison (see http://gnso.icann.org/en/drafts/request-liaison-gac-30mar16-en.pdf). As there were few applications received by the closing date that the Selection Committee (comprising the GNSO Chair and Vice-Chairs) believed met all the criteria that had been approved, however, the Council has been asked to approve an extension of the current Liaison's term through the Annual General Meeting in Hyderabad in November 2016, at which meeting the Council will be expected to review and appoint a permanent Liaison recommended by the Selection Committee for a renewable one-year term. 6.1 - Presentation of the motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+30+June+2016> (James Bladel) 6.2 - Discussion 6.3 - Council vote (voting threshold: simple majority) Item 7: COUNCIL DISCUSSION - Response to ICANN Board Request concerning Expert Working Group Final Report on Internationalized Registration Data (15 minutes) At its meeting during ICANN55 in Marrakech, the ICANN Board requested that the GNSO Council "review the broader policy implications of the IRD Final Report<https://whois.icann.org/sites/default/files/files/ird-expert-wg-final-23sep…> as they relate to other GNSO policy development work on WHOIS issues, and, at a minimum, forward the IRD Final Report as an input to the GNSO PDP on the Next Generation Registration Directory Services to Replace WHOIS that is currently underway". The Board also directed ICANN staff to "work with the implementation review team for the new consensus policy on translation and transliteration to consider the IRD Working Group's data model and requirements and incorporate them, where appropriate, to the extent that the IRD's recommendations are consistent with, and facilitate the implementation of the new consensus policy on translation and transliteration" (see https://www.icann.org/resources/board-material/resolutions-2016-03-10-en#1.e). In relation to the Board direction regarding implementation, ICANN staff from the Global Domains Division (GDD) proposed to the GNSO Council that one approach could be to merge the ongoing implementation team for Thick WHOIS with that to be formed to implement the new Translation and Transliteration of gTLD Contact Information consensus policy; however, community consultations indicated that there was no consensus on the proposal such that GDD staff is now proceeding with two separate implementation teams (see http://gnso.icann.org/mailing-lists/archives/council/pdffIuTrOsGIs.pdf). Here the GNSO Council will discuss the Board's request relating to the IRD Final Report, and decide on next steps. 7.1 - Council discussion 7.2 - Next steps Item 8: COMMITTEE UPDATE - Selection of Primary and Alternate Delegates from the GNSO to the New Bylaws-mandated Customer Standing Committee (10 minutes) The package of proposals<https://www.icann.org/en/system/files/files/iana-stewardship-transition-pac…> that was developed by the community in relation to the IANA Stewardship Transition called for the creation of a new structure to provide operational oversight of the performance of the IANA naming function, a role currently performed by the United States government through the National Telecommunications and Information Authority (NTIA). This new oversight structure is to be called the Customer Standing Committee (CSC), and its role is to monitor the performance of the IANA naming function against agreed service level targets. The CSC may also initiate review and make recommendations for changes to service level targets. On 1 June 2016, ICANN sent a request<https://www.icann.org/iana_imp_docs/51-csc-request-for-appointment-v-v1> to the ICANN Supporting Organizations (SOs), Advisory Committees (ACs) and Registry Stakeholder Group (RySG) to initiate their respective organization's processes and appoint candidates to serve as members and liaisons on the CSC. As a ICANN SO, the GNSO may appoint a liaison to the CSC, in addition to the two gTLD registry operator members to be selected by the RySG. For the liaison, a primary and a secondary candidate that meet the qualification requirements in the expression of interest, and are geographically diverse, needs to be appointed. The final composition of members of and liaisons to the CSC is approved first by the RySG and ccNSO, and secondly by the GNSO and ccNSO, who will also decide which members and liaisons will serve the inaugural three-year term. In their review, the ccNSO and GNSO Councils are expected to ensure diversity when approving the final composition of members and liaisons. Liaison candidates are to be confirmed by 22 July 2016, and the final slate as determined by the ccNSO and GNSO Councils to be sent to ICANN on 10 August. On 2 June 2016, the GNSO Council confirmed a selection committee for the primary and secondary GNSO liaison appointment consisting of Councilors Susan Kawaguchi, David Cake, Wolf-Ulrich Knoben and Rubens Kuhl. Here the Selection Committee will update the Council on its work to date, and confirm the timeline for selection, including consideration of any Special Meeting that may be necessary to enable the GNSO to meet the timelines for the appointment of CSC members and liaisons. 8.1 - Update (Donna Austin / CSC Selection Committee members) 8.2 - Next steps Item 9: WORKING GROUP PROGRESS REPORT - Activities of the Cross Community Working Group on Internet Governance (10 minutes) The Charter<https://community.icann.org/download/attachments/52888213/Charter%20ccWG%20…> for this Cross Community Working Group was ratified<https://community.icann.org/x/oQInAw> by the ccNSO Council (September 2014), the GNSO Council (October 2014), and the ALAC (April 2015). The CCWG Charter states its scope as doing "whatever it deems relevant and necessary to facilitate and ensure engagement and participation of the ICANN community in the global Internet governance scene and multi-stakeholder decision-making processes", with regular monthly updates to be provided to its Chartering Organizations and a periodic Progress Paper where appropriate. The Charter also provides that the Chartering Organizations should review the Charter and CCWG deliverables in order to determine whether the group should continue or be dissolved, with the proviso that the CCWG will continue if at least two of its Chartering Organizations extend the Charter and notify the other Chartering Organizations accordingly. At ICANN55, there was some discussion over the most appropriate forum for SO/AC interaction on Internet governance matters, especially given the expected forthcoming finalization of a Uniform Framework of Principles for Future CCWGs. The Council has since continued that discussion, with a view toward agreeing on the appropriate next steps for the CCWG on Internet Governance. Here the co-chairs of the CCWG-IG will provide the Council with a Progress Report on its recent activities, as required by its Charter. 9.1 - Update (Olivier Crepin-Leblond & Rafik Dammak) 9.2 - Council discussion 9.3 - Next steps Item 10: COUNCIL DISCUSSION - Next Steps relating to Implementation of Recommendations for the GNSO Review (10 minutes) In September 2015, the Independent Examiner that had been appointed to conduct the GNSO organizational review published its Final Report. At its meeting in April 2016, the GNSO Council adopted, with one modification, the proposed Feasibility and Prioritization Analysis of the Independent Examiner's recommendations that was prepared by the GNSO Working Party (see http://gnso.icann.org/en/council/resolutions#201604). The Working Party had been formed to liaise between the GNSO, the Board's Organizational Effectiveness Committee (OEC) and the Independent Examiner. The OEC considered the Final Report and the GNSO's modified Feasibility and Prioritization Analysis at its meeting in May 2016, and is expected to recommend action by the Board on the GNSO organizational review in Helsinki. To prepare for implementation of the recommendations that may be adopted by the ICANN Board, ICANN staff was requested to prepare a Discussion Paper for the GNSO. The Discussion Paper<http://gnso.icann.org/en/drafts/review-implementation-recommendations-22jun…> was circulated to the Council on 20 June 2016. Here the Council is expected to discuss and agree on possible mechanisms for implementation of the adopted recommendations, following consideration of the Discussion Paper. 10.1 - Council Discussion 10.2 - Next steps Item 11: STAFF UPDATE TO COUNCIL - Next Steps relating to the Final Report of the Implementation Advisory Group on Review of the WHOIS Conflicts with National Law Procedure (10 Minutes) The GNSO's 2005 Policy on WHOIS Conflicts with National Laws (see http://gnso.icann.org/en/issues/whois-privacy/council-rpt-18jan06.htm) recommended the creation of a procedure to address conflicts between a contracted party's WHOIS obligations and local/national privacy laws or regulations. Under the existing procedure dating from January 2008, a contracted party that credibly demonstrates that it is legally prevented from complying with its WHOIS obligations can invoke the procedure, which defines a credible demonstration as one in which the contracted party has received "notification of an investigation, litigation, regulatory proceeding or other government or civil action that might affect its compliance." The procedure has never been invoked. ICANN launched a review of the procedure in May 2014. An Implementation Advisory Group (IAG) was formed and began its work in January 2015. The IAG's Initial Report was published for public comment in November 2015 (see https://www.icann.org/public-comments/iag-whois-conflicts-privacy-2015-10-0…). On 25 May 2016, the IAG's Final Report<http://gnso.icann.org/mailing-lists/archives/council/pdf1nt18yPBer.pdf>, accompanying Appendices<http://gnso.icann.org/mailing-lists/archives/council/pdfC9Dr9B5OBO.pdf> and a summary Memo to the GNSO Council<http://gnso.icann.org/mailing-lists/archives/council/pdfZPGKEDdzDq.pdf> was delivered to the GNSO Council. The IAG is proposing modifications to the procedure that do not affect the underlying Policy. Here the Council will receive a brief update on its expected next steps, which may include confirming that the IAG's proposed modifications conform with the GNSO Policy. 11.1 - Staff update (Marika Konings) 11.2 - Council discussion 11.3 - Next steps Item 12: Any Other Business (5 minutes) ____________________________ Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article X, Section 3) 9. Except as otherwise specified in these Bylaws, Annex A hereto, or the GNSO Operating Procedures, the default threshold to pass a GNSO Council motion or other voting action requires a simple majority vote of each House. The voting thresholds described below shall apply to the following GNSO actions: a. Create an Issues Report: requires an affirmative vote of more than one-fourth (1/4) vote of each House or majority of one House. b. Initiate a Policy Development Process ("PDP") Within Scope (as described in Annex A<http://www.icann.org/en/about/governance/bylaws#AnnexA>): requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. c. Initiate a PDP Not Within Scope: requires an affirmative vote of GNSO Supermajority. d. Approve a PDP Team Charter for a PDP Within Scope: requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. e. Approve a PDP Team Charter for a PDP Not Within Scope: requires an affirmative vote of a GNSO Supermajority. f. Changes to an Approved PDP Team Charter: For any PDP Team Charter approved under d. or e. above, the GNSO Council may approve an amendment to the Charter through a simple majority vote of each House. g. Terminate a PDP: Once initiated, and prior to the publication of a Final Report, the GNSO Council may terminate a PDP only for significant cause, upon a motion that passes with a GNSO Supermajority Vote in favor of termination. h. Approve a PDP Recommendation Without a GNSO Supermajority: requires an affirmative vote of a majority of each House and further requires that one GNSO Council member representative of at least 3 of the 4 Stakeholder Groups supports the Recommendation. i. Approve a PDP Recommendation With a GNSO Supermajority: requires an affirmative vote of a GNSO Supermajority, j. Approve a PDP Recommendation Imposing New Obligations on Certain Contracting Parties: where an ICANN contract provision specifies that "a two-thirds vote of the council" demonstrates the presence of a consensus, the GNSO Supermajority vote threshold will have to be met or exceeded. k. Modification of Approved PDP Recommendation: Prior to Final Approval by the ICANN Board, an Approved PDP Recommendation may be modified or amended by the GNSO Council with a GNSO Supermajority vote. l. A "GNSO Supermajority" shall mean: (a) two-thirds (2/3) of the Council members of each House, or (b) three-fourths (3/4) of one House and a majority of the other House." Appendix 2: Absentee Voting Procedures (GNSO Operating Procedures 4.4<http://gnso.icann.org/council/gnso-operating-procedures-22sep11-en.pdf>) 4.4.1 Applicability Absentee voting is permitted for the following limited number of Council motions or measures. a. Initiate a Policy Development Process (PDP); b. Approve a PDP recommendation; c. Recommend amendments to the GNSO Operating Procedures (GOP) or ICANN Bylaws; d. Fill a Council position open for election. 4.4.2 Absentee ballots, when permitted, must be submitted within the announced time limit, which shall be 72 hours from the meeting's adjournment. In exceptional circumstances, announced at the time of the vote, the Chair may reduce this time to 24 hours or extend the time to 7 calendar days, provided such amendment is verbally confirmed by all Vice-Chairs present. 4.4.3 The GNSO Secretariat will administer, record, and tabulate absentee votes according to these procedures and will provide reasonable means for transmitting and authenticating absentee ballots, which could include voting by telephone, e- mail, web-based interface, or other technologies as may become available. 4.4.4 Absentee balloting does not affect quorum requirements. (There must be a quorum for the meeting in which the vote is initiated.) Reference (Coordinated Universal Time) UTC 07:45 Local time between October and March Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) UTC-7+1DST 00:45 San José, Costa Rica UTC-6+0DST 02:45 Iowa City, USA (CDT<http://fr.wikipedia.org/wiki/UTC%E2%88%9206:00>) UTC-6+0DST 02:45 New York/Washington DC, USA (EST) UTC-5+0DST 03:45 Buenos Aires, Argentina (ART<http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) UTC-3+0DST 04:45 Rio de Janiero, Brazil (BRST) UTC-2+0DST 04:45 Helsinki, Finland (EEST) UTC +3 10:45 London, United Kingdom (BST) UTC+0DST 08:45 Bonn, Germany (CET) UTC+1+0DST 09:45 Cairo, Egypt, (EET) UTC+2+0DST 09:45 Istanbul, Turkey (EEST) UTC+3+0DST 10:45 Perth, Australia (WST<http://timeanddate.com/library/abbreviations/timezones/au/wst.html>) UTC+8+1DST 15:45 Singapore (SGT) UTC +8 15:45 Sydney/Hobart, Australia (AEDT) UTC+11+0DST 17:45 ---------------------------------------------------------------------------- DST starts/ends on last Sunday of October 2016, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> http://tinyurl.com/jgzq34d Please let us know if you have any questions. Thank you. Kind regards, Glen de Saint Géry Manager Supporting Organisations Advisory Committees Internet Corporation for Assigned Names & Numbers - ICANN glen(a)icann.org http://www.icann.org<http://www.icann.org/>

1 0

Follow up: Red Cross and IGO Protections webinar
by Mary Wong 21 Jun '16

21 Jun '16

Dear all, Here is an update on the two action items requested of staff that were made during the webinar: (1) Prepare a consolidated table of all the inconsistent recommendations (as presented during the webinar), with additional information on what names/acronyms have been temporarily reserved and what others adopted as permanent policy – this has been done (see attached document). (2) Further information to be sought regarding the composition and status of the IGO-GAC-Board “small group” developing a proposal for IGO acronyms – we have noted this to colleagues working with the “small group” and expect some further information to be provided to the Council and GNSO community by Helsinki. 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 From: <owner-council(a)gnso.icann.org> on behalf of Glen de Saint Géry <Glen(a)icann.org> Date: Monday, June 6, 2016 at 12:01 To: "GNSO Council List (council(a)gnso.icann.org)" <council(a)gnso.icann.org> Subject: [council] Slides : Red Cross and IGO Protections webinar presented to the GNSO Council 2 June 2016 Dear Councillors, Please find below the slides used during the Red Cross and IGO Protections webinar presented to the GNSO Council on the 2nd June 2016. Published on page http://gnso.icann.org/en/council/correspondence<http://mailer.samanage.com/wf/click?upn=KTB340yHI8DoUtMP4BGJnral-2F6hkupRgT…> And can be directly viewed at http://gnso.icann.org/en/correspondence/background-status-igo-protection-02…<http://mailer.samanage.com/wf/click?upn=KTB340yHI8DoUtMP4BGJnral-2F6hkupRgT…> Reminder Mp3:https://icann.box.com/shared/static/v7yap1be29eez4ijz2qyv6yq1ewixm3y.mp3<https://icann.box.com/shared/static/v7yap1be29eez4ijz2qyv6yq1ewixm3y.mp3%20> <https://icann.box.com/shared/static/v7yap1be29eez4ijz2qyv6yq1ewixm3y.mp3%20> AC recording: ttps://icann.adobeconnect.com/p2yedtv28uv/<https://icann.adobeconnect.com/p2yedtv28uv/?OWASP_CSRFTOKEN=446542c865c6eb3…> 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/>

3 3

REVIEW: Draft GNSO Council minutes 12 May 2016
by Glen de Saint Géry 21 Jun '16

21 Jun '16

Dear Councillors, Attached, please find the draft minutes of the GNSO Council meeting on 12 May 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 <http://gnso.icann.org/en/council/op-procedures-24jun15-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 30 June 2016. Thank you very much. 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

MOTION - To extend the term of the current GNSO Liaison to the GAC
by James M. Bladel 21 Jun '16

21 Jun '16

Councilors - As discussed on the list a couple of weeks ago, please see this Motion (attached and copied below) to extend the term of the current GNSO-GAC Liaison (Mason) through ICANN57 in Hyderabad, and to adopt a new timeline for selecting a successor liaison. I¹ve also added a new action item (Whereas #5 and Resolved #3) which calls for the development of a ³uniform selection process² as part of the post-transition implementation work. If adopted, this uniform selection process would be employed in some capacity to fill future appointments to Liaisons, Review Teams, and other working groups as necessary. Thank you, J. ________________________________________ Motion to extend the term of the current GNSO Liaison to the GAC and confirm the extended timeline for the selection process for the next GNSO liaison to the GAC. Whereas: 1.The GNSO Council adopted the ŒRequest for Candidates GNSO Liaison to the GAC¹ which includes the proposed call for volunteers, application and evaluation process (see http://gnso.icann.org/en/drafts/request-liaison-gac-30mar16-en.pdf during its meeting on 14 April 2016. 2.The subsequent call for volunteers resulted in one incomplete application by the Deadline. 3. The GNSO Leadership team shared with the Council its assessment concerning the misalignment of the current deadline and the fact that the terms of possible candidates (e.g. former Council members) end at the ICANN AGM and as a result proposed to extend the selection timeline as follows: Nominations Accepted for Candidates - 1 OCT 2016; Council Chairs consider candidates and notify first choice - 20 OCT; Chairs submit motion to Council by 29 OCT for consideration during Council meeting on 8 NOV; GAC Leadership notified of new Liaison by 9 NOV. 4. The current GNSO Liaison to the GAC has agreed to extend his term until the ICANN AGM in Hyderabad. 5. The GNSO Council leadership expects that appointments of this nature will continue to be necessary in the future, and these selections would benefit from a uniform selection process. Additionally, the Council notes the upcoming implementation work associated with the post-transition bylaws will include work on drafting a uniform selection process, and this could be expanded to cover additional roles. Resolved: 1. The GNSO Council hereby confirms the extension of the term of the current GNSO Liaison to the GAC, Mason Cole, until the end of the ICANN AGM in Hyderabad. 2. The GNSO Council instructs the GNSO Secretariat to inform the GNSO Stakeholder Groups and Constituencies of the extended selection timeline (Nominations Accepted for Candidates - 1 OCT 2016; Council Chairs consider candidates and notify first choice - 20 OCT; Chairs submit motion to Council by 29 OCT for consideration during Council meeting on 8 NOV; GAC Leadership notified of new Liaison by 9 NOV). 3. The Council instructs Staff to include consideration of a uniform selection process as part of the work associated with implementing the post-transition bylaws

6 10

Update on SCI Activities June 2016
by Amr Elsadr 21 Jun '16

21 Jun '16

Dear Councilors, In my role as the GNSO Liaison to the Standing Committee on Improvements Implementation (SCI), I am providing the following written update on SCI activities as of June 2016. Due to the shorter length of the ICANN 56 Policy Forum meeting, this update is provided in lieu of a face-to-face report as is normally provided by the SCI to the Council at ICANN meetings. The purpose of this update is to inform the GNSO Council of the SCI’s activities and is not a request for a particular action. After extensive deliberations the SCI has agreed, by full consensus, proposed revisions to the GNSO Operating Procedures for the following two issues assigned to it by the GNSO Council. The original Issue Requests for these items are attached and I have included some background information below. 1. Documented procedures for submitting, seconding, and amending motions 2. New procedures relating to Chair and Vice Chair elections Next steps: · Per our standard process, the SCI has asked staff to initiate a Public Forum for these combined proposed revised procedures. · Following the close of the Forum the SCI will consider any comments received and then submit a motion to adopt the procedures for GNSO Council consideration at its meeting on 01 September. · Note: With respect to the Chair and Vice Chair election procedures, the SCI and staff have determined that if these are adopted at the 01 September meeting they will be in place in time for the necessary steps to occur leading up to and including the election at the Annual General Meeting at ICANN 57, 3-9 November 2016. In addition to the background below, the SCI has attached for your reference the proposed revisions to the GNSO Operating Procedures as redlines to the current procedures. If you should have any comments or questions concerning these proposed revisions please let me know. Thank you very much for the opportunity to provide this update. Thanks. Amr —————————————— Background Procedures for Submitting, Seconding, and Amending Motions: · On 05 March 2015 the SCI submitted to the GNSO Council a Review Request concerning the fact that there are currently no formal procedures on (i) whether, how and by whom a properly submitted motion is to be seconded, and (ii) treatment of proposed amendments to such motions as either “friendly” or “unfriendly”. The Review Request was one of two that the Council approved at its meeting on 16 April 2015. In the attached Review Request the GNSO Council asked that the SCI codify the existing customary practices of the GNSO Council and consider new processes to govern the seconding of motions and amendments to motions. · On 09 October 2015 the SCI agreed on a documentation of the Current Practice Relating to Motions and sent a letter along with the original Review Request and the documentation to Jonathan Robinson, GNSO Council Chair. · In December 2015 the SCI established a Sub Team to review the current practice and the Sub Team submitted its recommendations to the SCI on 02 March 2016. The SCI discussed the recommendations in Marrakech on 05 March and asked staff to draft revisions to the GNSO Operating Procedures per the recommendations. · The revisions were agreed to by full consensus on 14 April. Chair and Vice Chair Procedures: · In its motion approved on 19 November 2015 the GNSO Council requested the SCI: 1. To review Sections 2.2(b), (f) and (g) of the GNSO Operating Procedures with respect to clarifying: (i) the eligibility of incoming Council members to run for the position of GNSO Chair; (ii) the start and end dates and the duration of the Chair and Vice-Chair terms in accordance with the ICANN Bylaws; and (iii) the timing of publication of the election results; and 2. To recommend a general time table for election of the GNSO Council Chair to be approved by the GNSO Council and added to the GNSO Operating Procedures. · In December 2015 the SCI created Sub Team to discuss and draft possible new procedures. The Sub Team submitted its recommendations to the SCI to consider at its meeting during ICANN 55 in Marrakech, Morocco on 05 March 2016. · After further extensive consideration and modification the revisions were agreed to by full consensus on 20 June.

1 0