September 2016 - council - lists.icann.org

FW: For your review - proposed charter new gTLD Auction Proceeds CCWG
by James M. Bladel Oct. 1, 2016

Oct. 1, 2016

Councilors - See message below, sent on behalf of the gTLD Auction Proceeds Charter Drafting Team. Their Draft Charter for a proposed CCWG is attached, and they are requesting feedback by 30 September. If time allows, lets plan to add this as a discussion point for our next call (29 SEP). Thank you, J. From: Marika Konings <marika.konings(a)icann.org<mailto:marika.konings@icann.org>> Date: Tuesday, September 13, 2016 at 12:41 Subject: For your review - proposed charter new gTLD Auction Proceeds CCWG Sending on behalf of Jonathan Robinson, new gTLD Auction Proceeds Drafting Team Chair & Alan Greenberg, DT Vice-Chair: Dear SO/AC Chairs, On behalf of the new gTLD Auction Proceeds Drafting Team (DT), we are delighted to submit to you and your respective SO/ACs, the proposed charter for a Cross-Community Working Group on new gTLD Auction Proceeds. As you may recall, representatives of all ICANN SO/ACs, apart from the ccNSO (which decided not to take part in the DT effort), participated in the DT deliberations (see https://community.icann.org/x/AR_AAw for DT members). This proposed charter is the result of extensive input and deliberations, including careful review of input that was received as part of the cross-community session at ICANN 56 in Helsinki (see https://community.icann.org/x/fgmbAw) and we believe it now represents a careful balance between the different viewpoints and perspectives, including from both the DT Members and the ICANN Board liaisons to the DT. As such, the DT would like to request you review the proposed charter with this careful balance in mind and only flag to the DT any pertinent issues that would prevent your respective SO/AC from adopting this charter. We would like to request you highlight such pertinent issues by 30 September 2016 at the latest, including an indication of when you anticipate your respective SO/AC to be in a position to consider the charter for adoption following 30 September, provided that no pertinent issues have been identified by any of the ICANN SO/ACs. Of course, should you have any clarifying questions, please do not hesitate to respond to this message. The DT looks forward to receiving your feedback. Best wishes, Jonathan Robinson, DT Chair & Alan Greenberg, DT Vice-Chair

3 3

FW: IPC Support for Letter of Instruction regarding IANA IPR
by James M. Bladel Oct. 1, 2016

Oct. 1, 2016

Councilors – Please see the note below from Greg Shatan on behalf of the IPC, and also some important context on the CWG Instruction Letter. Thank you, J. From: Greg Shatan <gregshatanipc(a)gmail.com> Date: Friday, September 30, 2016 at 17:16 To: "James M. Bladel" <jbladel(a)godaddy.com>, Heather Forrest <Heather.Forrest(a)acu.edu.au>, "Donna Austin (Donna.Austin(a)neustar.biz)" <Donna.Austin(a)neustar.biz>, Glen de Saint Géry <glen(a)icann.org> Cc: Kiran Malancharuvil <Kiran.Malancharuvil(a)markmonitor.com>, Lori Schulman <lschulman(a)inta.org>, "Paul McGrady (Policy)" <policy(a)paulmcgrady.com>, "Steven J. Metalitz" <met(a)msk.com>, "Vayra, Fabricio (Perkins Coie)" <FVayra(a)perkinscoie.com> Subject: IPC Support for Letter of Instruction regarding IANA IPR James, On behalf of the IPC, I would like to convey to you and to the GNSO Council that the IPC supports GNSO inclusion in the Letter of Instruction and responding "yes" to the CWG Co-Chairs. Speaking as a GNSO-appointed member of the CWG and as a member of the IANA IPR collaborative team that worked with the numbers and protocol parameters communities to complete this aspect of transition planning and implementation: I'd like to clarify the limited but significant role that this Letter plays. The Letter of Instruction directs ICANN to sign the Community Agreement, one of several agreements that are part of the IANA IPR transfer, which in turn is part of the IANA transition. The Community Agreement gives the three operational communities oversight of the IETF Trust, as the new owner of the IANA IPR. As the Names Community has no legal entity to act on its behalf, ICANN is being directed to do so in this Letter, which also constrains ICANN from taking other actions that might seem possible based on having its signature on the agreement. (More simply put, ICANN is acting as the Names Community's avatar.) This small act by the GNSO further smooths the way for the IANA transition. Since the request to enjoin the IANA transition in federal court in Texas has been DENIED, now is the time to move forward. Best regards, Greg Shatan IPC President

2 1

The transition is ON!! Texas court rejected request for temporary restraining order
by Burr, Becky Sept. 30, 2016

Sept. 30, 2016

J. Beckwith Burr Neustar, Inc. / Deputy General Counsel & Chief Privacy Officer 1775 Pennsylvania Avenue NW, Washington D.C. 20006 Office: +1.202.533.2932 Mobile: +1.202.352.6367 / neustar.biz<http://www.neustar.biz> From: James Bladel <jbladel(a)godaddy.com<mailto:jbladel@godaddy.com>> Date: Friday, September 30, 2016 at 5:49 PM To: GNSO Council List <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Cc: Jonathan Robinson <jrobinson(a)afilias.info<mailto:jrobinson@afilias.info>> Subject: Re: [council] Re: Note from CWG-Stewardship Chairs to the Chairs of the CWG-Stewardship Chartering Organizations Regarding IANA Intellectual Property Right Thanks to everyone who weighed in. Given that there are no objections and several expressions of support, I will ask that the GNSO be added to the other SO and AC organizations on the letter instructing ICANN to execute the IANA IPR agreements. Thanks again for your assistance on this short-schedule task, and have a great weekend. J. From: Keith Drazek <kdrazek(a)verisign.com<mailto:kdrazek@verisign.com>> Date: Thursday, September 29, 2016 at 20:42 To: "James M. Bladel" <jbladel(a)godaddy.com<mailto:jbladel@godaddy.com>> Cc: GNSO Council List <council(a)gnso.icann.org<mailto:council@gnso.icann.org>>, Jonathan Robinson <jrobinson(a)afilias.info<mailto:jrobinson@afilias.info>> Subject: Re: [council] Re: Note from CWG-Stewardship Chairs to the Chairs of the CWG-Stewardship Chartering Organizations Regarding IANA Intellectual Property Right No objection from the RySG. Full support. Keith On Sep 30, 2016, at 2:12 AM, James M. Bladel <jbladel(a)godaddy.com<mailto:jbladel@godaddy.com>> wrote: Dear Council Colleagues – As discussed during our call today, please respond by COB tomorrow (and preferably sooner) if you have any objections to adding the GNSO to the list of SO/ACs instructing ICANN to execute these agreements. If there are no objections received, we will give Staff the green light to proceed. Thank you, J. From: "James M. Bladel" <jbladel(a)godaddy.com<mailto:jbladel@godaddy.com>> Date: Thursday, September 29, 2016 at 10:10 To: GNSO Council List <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: FW: Note from CWG-Stewardship Chairs to the Chairs of the CWG-Stewardship Chartering Organizations Regarding IANA Intellectual Property Right Dear Councilors– Please see the note below, in which the leadership of CWG-Stewardship is asking all chartering organizations (incl. the GNSO) for their approval to being included as signatories on a letter, instructing ICANN to execute the three IANA IPR agreements referenced & attached. They are asking for a response by 30 SEP (tomorrow). While acknowledging the last-minute nature of this request, this should be a non-controversial issue and I’d like to include a discussion of it under AOB for today’s call. Thanks— J. From: Trang Nguyen <trang.nguyen(a)icann.org<mailto:trang.nguyen@icann.org>> Date: Thursday, September 29, 2016 at 9:37 Subject: Note from CWG-Stewardship Chairs to the Chairs of the CWG-Stewardship Chartering Organizations Regarding IANA Intellectual Property Right Dear Chairs, Please see below a note from the Jonathan Robinson and Lise Fuhr, Co-Chairs of the CWG-Stewardship. -- Dear SO/AC chairs and co-chairs, As part of the transition implementation work, representatives from the names community, the numbers community, the protocol parameters community, the IETF Trust, and ICANN have drafted a set of agreements to effectuate the transfer of the IANA IPR from ICANN to the IETF Trust and to govern the relationships amongst the parties with respect to the IPR after the transfer. These agreements are: - IANA IPR Assignment Agreement: This agreement transfers the IPR from ICANN to the IETF Trust. - 3 IANA IPR License Agreements (one each for the names, numbers, and protocol parameters IANA services.): These agreements allows for the IANA functions operator to use the IPR. - IANA - IPR Community Agreement: This agreement explains the rights and obligations of the IETF Trust and each operational community as regards the IPR. After a public comment period last month, the agreements have been finalized and are ready to be executed. One of the decisions that the CWG had to make as part of the work was to identify who would be the signatory of the Community Agreement on behalf of the Naming Community. The decision made by the group, with input from CWG external counsel, was to ask ICANN to play that role. An instruction letter has been assembled for that purpose. The Instruction Letter says: "This letter confirms the request of the Cross Community Working Group to Develop an IANA Stewardship Transition Proposal on Naming Related Functions (“CWG”) for the benefit of those of its listed chartering organizations – the Country Code Names Supporting Organization (“ccNSO”), the Security and Stability Advisory Committee (“SSAC”), the Generic Names Supporting Organization (“GNSO”), the At Large Advisory Committee (“ALAC”) and the Governmental Advisory Committee (“GAC”) – that have affirmed or hereafter affirm in writing that they agree to be included herein (each a “Consenting SO/AC” and collectively, the “Names Community”) that ICANN serve as the signatory for the Names Community under the Community Agreement." This makes reference to the COs affirming in writing that they agree to be included in the instruction letter as a consenting SO/AC. As ICANN might formally reach out to us to obtain confirmation that one or more COs have agreed to be a consenting SO/AC, we hereby kindly ask that you provide such a written confirmation as a matter of urgency by replying to this email, preferably on or before September 30th, 2016, so that the signing of the agreement may proceed as planned. Thank you for your cooperation, Lise Fuhr & Jonathan Robinson, CWG co-chairs.

1 0

Council Resolutions Thursday 29 September 2016
by Glen de Saint Géry Sept. 30, 2016

Sept. 30, 2016

Dear Councillors, Please find below the resolutions the Council adopted at its meeting on Thursday 29 September 2016. 1 GNSO Validation of CCWG-Accountability Budget Request WHEREAS, 1. Per its Charter, the Project Cost Support Team (PCST) has supported the CCWG-Accountability in developing a draft budget and cost-control processes for the CCWG-Accountability activities for FY17, and has also developed a historical analysis of all the transition costs to date (see https://gnso.icann.org/mailing-lists/archives/council/pdfpklU5q6Ojg.pdf) 2. The CCWG-Accountability FY17 budget was presented at its plenary meeting of June 21st and approved for transmission to the Chartering Organizations for validation as per the process agreed with the PCST. This request for validation was received on 23 June. 3. Following review and discussion during ICANN56, the GNSO Council requested a webinar on this topic which was held on 23 August (see transcript at https://gnso.icann.org/en/meetings/transcript-ccwg-accountability-webinar-2…, recording at http://audio.icann.org/gnso/gnso-ccwg-accountability-webinar-23aug16-en.mp3 and AC recording at https://icann.adobeconnect.com/p8fu99qpt7d/) 4. The GNSO Council notes that many members of the GNSO community have expressed the view that the projected budget does not likely support revisiting the topic of the jurisdiction of ICANN's organization in that such exploration would likely require substantial independent legal advice on alternative jurisdictions and their potential impact on the text and structure of ICANN's Bylaws. 5. The GNSO Council has discussed and reviewed all the relevant materials. RESOLVED, 1. The GNSO Council hereby accepts the proposed CCWG-Accountability FY17 budget, as well as the cost-control processes presented in conjunction with the CCWG budget, expects the working groups to be restrained and judicious in their use of outside legal assistance, and believes that the Legal Committee should exercise reasonable and effective controls in evaluating requests for outside legal assistance and should approve them only when deemed essential to assist a working group to fully and objectively understand and develop a particular course of action for which the group has reached a substantial degree of consensus and requires legal advice on its risks and feasibility. 2. The GNSO Council expects to receive regular updates on actual expenditures as tracked against this adopted budget, and reserves the right to provide further input on the budget allocation in relation to the CCWG-Accountability related activities. 3. The GNSO Council expects ICANN staff, including its office of General Counsel, to provide the assistance requested by the CCWG and its working groups in an expeditious, comprehensive, and unbiased manner. 4. The GNSO Council expects the CCWG-Accountability and staff to work within the constraints of this approved budget, and that excess costs or requests for additional funding beyond said budget should be recommended by the Legal Committee only when deemed essential to completion of the CCWG's work and objectives. . 5. It is the position of the GNSO Council that revisiting the jurisdiction or organization of the ICANN legal entity, as established by CCWG-Accountability Work Stream 1, would not likely be supported by this projected budget and, further, that such inquiry should not be undertaken at this time because the new accountability measures are all premised and dependent on California jurisdiction for their effective operation, and any near-term changes in organizational jurisdiction could be extremely destabilizing for ICANN and its community. 6. The GNSO Council requests the GNSO Secretariat to communicate this resolution to the CCWG-Accountability Chairs, and to the office of the ICANN CFO. Voting results<https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-29sep16-en.…> 2. Interim appointment of the GNSO Representative on the Empowered Community Administration WHEREAS 1. As stated in Section 1.1(a) of Article 6 of the new ICANN Bylaws, concerning the composition and organization of the Empowered Community (EC), "The Empowered Community ("EC") shall be a nonprofit association formed under the laws of the State of California consisting of the ASO, the ccNSO, the GNSO, the ALAC and the GAC (each a "Decisional Participant" or "associate," and collectively, the "Decisional Participants")." 2. The sole purpose of the EC is to exercise its rights and perform its obligations under ICANN's Articles of Incorporation and the ICANN Bylaws, and the EC shall have no other powers or rights except as expressly provided in the ICANN Bylaws. The EC may only act as provided in these Bylaws. Any act of the EC that is not in accordance with these Bylaws shall not be effective. 3. As outlined in section 6.3 of the new ICANN Bylaws, the GNSO, as a Decisional Participant, shall act through its respective chair or such other person as may be designated by the GNSO (collectively, such persons from all communities are the "EC Administration"). Each Decisional Participant shall deliver annually a written certification from its chair or co-chairs to the ICANN Secretary designating the individual who shall represent the Decisional Participant on the EC Administration. 4. The GNSO created a Drafting Team (DT) on 30 June 2016 to identify the GNSO's new rights and obligations, and work with ICANN staff to prepare an implementation plan to address any needed changes by 30 September (see http://gnso.icann.org/en/council/resolutions - 201606). RESOLVED 1. The GNSO Council hereby confirms that the GNSO Chair (currently James Bladel) will represent the GNSO as the Decisional Participant on the Empowered Community Administration on an interim basis. 2. The GNSO representative shall act solely as directed by the GNSO Council in accordance with the ICANN Bylaws and other related GNSO Operating Procedures. 3. Within three months after the completion of the work of the GNSO Rights & Obligations under Revised ICANN Bylaws Drafting Team and adoption of its recommendations by the GNSO Council, the GNSO is expected to finalize its decision on the appointment of the person designated to represent the GNSO as the Decisional Participant on the Empowered Community Administration and will communicate this accordingly to the ICANN Secretary. 4. The GNSO Council requests the GNSO Secretariat to communicate this decision to the ICANN Secretary which will serve as the required written certification from the GNSO Chair designating the individual who shall represent the Decisional Participant on the EC Administration. Voting Results<https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-29sep16-en.…> Please let me know if you have any questions. 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/> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>.

1 0

Quick turn for next call
by James M. Bladel Sept. 30, 2016

Sept. 30, 2016

Council Colleagues – First, thanks for a thoughtful and productive meeting yesterday. I particularly appreciated your patience as we went approx. 20 minutes beyond our scheduled time. Thanks again. Coming up: Our next GNSO Call is on 13 OCT, which means the cutoff for documents and motions is this Monday (3 OCT). This presents an unusually small window between meetings, so please be sure that any motions, documents or follow-up items from yesterday that you’d like us to consider during the next call are submitted to the list by Monday. Thanks, and have a great weekend! J.

1 0

FW: Note from CWG-Stewardship Chairs to the Chairs of the CWG-Stewardship Chartering Organizations Regarding IANA Intellectual Property Right
by James M. Bladel Sept. 30, 2016

Sept. 30, 2016

Dear Councilors– Please see the note below, in which the leadership of CWG-Stewardship is asking all chartering organizations (incl. the GNSO) for their approval to being included as signatories on a letter, instructing ICANN to execute the three IANA IPR agreements referenced & attached. They are asking for a response by 30 SEP (tomorrow). While acknowledging the last-minute nature of this request, this should be a non-controversial issue and I’d like to include a discussion of it under AOB for today’s call. Thanks— J. From: Trang Nguyen <trang.nguyen(a)icann.org> Date: Thursday, September 29, 2016 at 9:37 Subject: Note from CWG-Stewardship Chairs to the Chairs of the CWG-Stewardship Chartering Organizations Regarding IANA Intellectual Property Right Dear Chairs, Please see below a note from the Jonathan Robinson and Lise Fuhr, Co-Chairs of the CWG-Stewardship. -- Dear SO/AC chairs and co-chairs, As part of the transition implementation work, representatives from the names community, the numbers community, the protocol parameters community, the IETF Trust, and ICANN have drafted a set of agreements to effectuate the transfer of the IANA IPR from ICANN to the IETF Trust and to govern the relationships amongst the parties with respect to the IPR after the transfer. These agreements are: - IANA IPR Assignment Agreement: This agreement transfers the IPR from ICANN to the IETF Trust. - 3 IANA IPR License Agreements (one each for the names, numbers, and protocol parameters IANA services.): These agreements allows for the IANA functions operator to use the IPR. - IANA - IPR Community Agreement: This agreement explains the rights and obligations of the IETF Trust and each operational community as regards the IPR. After a public comment period last month, the agreements have been finalized and are ready to be executed. One of the decisions that the CWG had to make as part of the work was to identify who would be the signatory of the Community Agreement on behalf of the Naming Community. The decision made by the group, with input from CWG external counsel, was to ask ICANN to play that role. An instruction letter has been assembled for that purpose. The Instruction Letter says: "This letter confirms the request of the Cross Community Working Group to Develop an IANA Stewardship Transition Proposal on Naming Related Functions (“CWG”) for the benefit of those of its listed chartering organizations – the Country Code Names Supporting Organization (“ccNSO”), the Security and Stability Advisory Committee (“SSAC”), the Generic Names Supporting Organization (“GNSO”), the At Large Advisory Committee (“ALAC”) and the Governmental Advisory Committee (“GAC”) – that have affirmed or hereafter affirm in writing that they agree to be included herein (each a “Consenting SO/AC” and collectively, the “Names Community”) that ICANN serve as the signatory for the Names Community under the Community Agreement." This makes reference to the COs affirming in writing that they agree to be included in the instruction letter as a consenting SO/AC. As ICANN might formally reach out to us to obtain confirmation that one or more COs have agreed to be a consenting SO/AC, we hereby kindly ask that you provide such a written confirmation as a matter of urgency by replying to this email, preferably on or before September 30th, 2016, so that the signing of the agreement may proceed as planned. Thank you for your cooperation, Lise Fuhr & Jonathan Robinson, CWG co-chairs.

6 7

Special Meeting of the ICANN Board - 30 Sept 2016to discuss IANA Intellectual Property Agreements
by Bruce Tonkin Sept. 30, 2016

Sept. 30, 2016

From https://www.icann.org/resources/board-material/agenda-2016-09-30-en Agenda | Special Meeting of the ICANN Board 30 Sep 2016 Main Agenda * IANA Intellectual Property Agreements * Discussion on Finalization of IANA Stewardship Transition Implementation * AOB Published on 28 September 2016

1 0

Re: [council] FW: Note from CWG-Stewardship Chairs to the Chairs of the CWG-Stewardship Chartering Organizations Regarding IANA Intellectual Property Right
by Marika Konings Sept. 29, 2016

Sept. 29, 2016

As discussed on the call, please communicate to the list within 24 hours if there are any objections for the GNSO approval to being included as signatories on this letter. If no objections are received within the 24 hour timeframe, the GNSO’s approval will be communicated. 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: <owner-council(a)gnso.icann.org> on behalf of "James M. Bladel" <jbladel(a)godaddy.com> Date: Thursday 29 September 2016 at 09:10 To: GNSO Council List <council(a)gnso.icann.org> Subject: [council] FW: Note from CWG-Stewardship Chairs to the Chairs of the CWG-Stewardship Chartering Organizations Regarding IANA Intellectual Property Right Dear Councilors– Please see the note below, in which the leadership of CWG-Stewardship is asking all chartering organizations (incl. the GNSO) for their approval to being included as signatories on a letter, instructing ICANN to execute the three IANA IPR agreements referenced & attached. They are asking for a response by 30 SEP (tomorrow). While acknowledging the last-minute nature of this request, this should be a non-controversial issue and I’d like to include a discussion of it under AOB for today’s call. Thanks— J. From: Trang Nguyen <trang.nguyen(a)icann.org> Date: Thursday, September 29, 2016 at 9:37 Subject: Note from CWG-Stewardship Chairs to the Chairs of the CWG-Stewardship Chartering Organizations Regarding IANA Intellectual Property Right Dear Chairs, Please see below a note from the Jonathan Robinson and Lise Fuhr, Co-Chairs of the CWG-Stewardship. -- Dear SO/AC chairs and co-chairs, As part of the transition implementation work, representatives from the names community, the numbers community, the protocol parameters community, the IETF Trust, and ICANN have drafted a set of agreements to effectuate the transfer of the IANA IPR from ICANN to the IETF Trust and to govern the relationships amongst the parties with respect to the IPR after the transfer. These agreements are: - IANA IPR Assignment Agreement: This agreement transfers the IPR from ICANN to the IETF Trust. - 3 IANA IPR License Agreements (one each for the names, numbers, and protocol parameters IANA services.): These agreements allows for the IANA functions operator to use the IPR. - IANA - IPR Community Agreement: This agreement explains the rights and obligations of the IETF Trust and each operational community as regards the IPR. After a public comment period last month, the agreements have been finalized and are ready to be executed. One of the decisions that the CWG had to make as part of the work was to identify who would be the signatory of the Community Agreement on behalf of the Naming Community. The decision made by the group, with input from CWG external counsel, was to ask ICANN to play that role. An instruction letter has been assembled for that purpose. The Instruction Letter says: "This letter confirms the request of the Cross Community Working Group to Develop an IANA Stewardship Transition Proposal on Naming Related Functions (“CWG”) for the benefit of those of its listed chartering organizations – the Country Code Names Supporting Organization (“ccNSO”), the Security and Stability Advisory Committee (“SSAC”), the Generic Names Supporting Organization (“GNSO”), the At Large Advisory Committee (“ALAC”) and the Governmental Advisory Committee (“GAC”) – that have affirmed or hereafter affirm in writing that they agree to be included herein (each a “Consenting SO/AC” and collectively, the “Names Community”) that ICANN serve as the signatory for the Names Community under the Community Agreement." This makes reference to the COs affirming in writing that they agree to be included in the instruction letter as a consenting SO/AC. As ICANN might formally reach out to us to obtain confirmation that one or more COs have agreed to be a consenting SO/AC, we hereby kindly ask that you provide such a written confirmation as a matter of urgency by replying to this email, preferably on or before September 30th, 2016, so that the signing of the agreement may proceed as planned. Thank you for your cooperation, Lise Fuhr & Jonathan Robinson, CWG co-chairs.

1 0

Document and Motion deadline Monday, 3 October 2016 at 23:59 UTC for the GNSO Council Meeting 13 October 2016 at 12:00 UTC
by Glen de Saint Géry Sept. 29, 2016

Sept. 29, 2016

Dear Councillors, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. MONDAY, 3 October 2016 at 23:59 UTC) of the GNSO Council Meeting on 13 October 2016 at 12:00UTC Motions should be sent to the Council mailing list and will then be posted on the Wiki at: https://community.icann.org/display/gnsocouncilmeetings/Motions+13+October+… 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/> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>.

1 0

FW: GNSO Council Abstention Notification Form [#215]
by Glen de Saint Géry Sept. 29, 2016

Sept. 29, 2016

FYI From: ICANN [mailto:no-reply@wufoo.com] Sent: Thursday, September 29, 2016 4:11 PM To: gnso.secretariat(a)icann.org; council(a)gnso.icann.org Subject: GNSO Council Abstention Notification Form [#215] Name of Officer: * Tapani Tarvainen Officer Email Address: * ncsg(a)tapani.tarvainen.info<mailto:ncsg@tapani.tarvainen.info> Date Prepared: * Thursday, September 29, 2016 GNSO Organization: * Non-Commercial Stakeholder Group Officer Position or Title: * NCSG Chair Voting Remedy: * Proxy Reason(s) for or condition(s) leading to the remedy: * Marilia Maciel is unable to attend the council meeting. Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: * Any and all. Date upon which the remedy will expire or terminate: [Note: may not exceed 3 months initially; may be renewed by sending an email with explanation to GNSO Secretariat] * Friday, September 30, 2016 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: * Stephanie Perrin

1 0