November 2016 - council - lists.icann.org

Fwd: GNSO Council Abstention Notification Form [#225]
by Glen de Saint Géry Nov. 6, 2016

Nov. 6, 2016

Début du message transféré : Expéditeur: "ICANN" <no-reply(a)wufoo.com<mailto:no-reply@wufoo.com>> Date: 6 novembre 2016 22:01:09 UTC+5:30 Destinataire: gnso.secretariat(a)icann.org<mailto:gnso.secretariat@icann.org>, council(a)gnso.icann.org<mailto:council@gnso.icann.org> Objet: GNSO Council Abstention Notification Form [#225] Répondre à: <no-reply(a)wufoo.com<mailto:no-reply@wufoo.com>> Name of Officer: * Paul Diaz Officer Email Address: * pdiaz(a)pir.org<mailto:pdiaz@pir.org> Date Prepared: * Sunday, November 6, 2016 GNSO Organization: * Registries Stakeholder Group Officer Position or Title: * Chairman Voting Remedy: * Proxy Reason(s) for or condition(s) leading to the remedy: * Valerie Tan cannot attend GNSO Council meeting, Donna Austin will serve as her proxy. Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: * For GNSO Council sessions on 7-8 November 2016. 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] * Tuesday, November 8, 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: * Donna Austin

1 0

Re: [council] Fwd: Appointment of ALAC Liaison to the GNSO
by Michele Neylon - Blacknight Nov. 6, 2016

Nov. 6, 2016

Welcome Cheryl ☺ -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains http://www.blacknight.host/ http://blacknight.blog/ http://ceo.hosting/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265, Ireland Company No.: 370845 From: <owner-council(a)gnso.icann.org> on behalf of James Bladel <jbladel(a)godaddy.com> Date: Sunday 6 November 2016 at 17:31 To: GNSO Council List <council(a)gnso.icann.org> Cc: Cheryl Langdon-Orr <langdonorr(a)gmail.com> Subject: [council] Fwd: Appointment of ALAC Liaison to the GNSO Councilors, FYI. And welcome, Cheryl! Sent via iPhone. Blame Siri. Begin forwarded message: From: Alan Greenberg <alan.greenberg(a)mcgill.ca<mailto:alan.greenberg@mcgill.ca>> Date: November 6, 2016 at 16:22:03 GMT+5:30 Subject: Appointment of ALAC Liaison to the GNSO Dear James, Please accept this as the formal notice that the ALAC has appointed Cheryl Langdon-Orr as it Liaison to the GNSO for the year starting at the end of the ICANN57 Meeting in Hyderabad. Regards, Alan

1 0

Fwd: Appointment of ALAC Liaison to the GNSO
by James M. Bladel Nov. 6, 2016

Nov. 6, 2016

Councilors, FYI. And welcome, Cheryl! Sent via iPhone. Blame Siri. Begin forwarded message: From: Alan Greenberg <alan.greenberg(a)mcgill.ca<mailto:alan.greenberg@mcgill.ca>> Date: November 6, 2016 at 16:22:03 GMT+5:30 Subject: Appointment of ALAC Liaison to the GNSO Dear James, Please accept this as the formal notice that the ALAC has appointed Cheryl Langdon-Orr as it Liaison to the GNSO for the year starting at the end of the ICANN57 Meeting in Hyderabad. Regards, Alan

1 0

Draft agenda for the GNSO Council Public Meeting (Part2) on Monday 7 November at 15:15.
by Glen de Saint Géry Nov. 6, 2016

Nov. 6, 2016

Dear Councillors, Please find the draft agenda for the GNSO Council Public Meeting (Part2) on Monday 7 November at 15:15. This agenda was established according to the GNSO Operating Procedures<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> v3.2, updated on 01 September 2016. For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. Coordinated Universal Time: 09:45 UTC 01:45 Los Angeles; 04:45 Washington; 09:45 London; 15:15 Hyderabad Meeting Times 09:45 UTC http://tinyurl.com/jds8zkh Main Meeting Page: https://icann572016.sched.org/event/8cz1/gnso-council-public-meeting-part-2 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 2016 / 2017Council (20 mins) 1.1 - Roll call 1.2 - Statements of interest Darcy Southwell - SOI<https://community.icann.org/display/gnsosoi/Darcy+Southwell+SOI> Registrars Stakeholder Group Michele Neylon- SOI<https://community.icann.org/display/gnsosoi/Michele+Neylon+SOI> Registrars Stakeholder Group Rafik Dammak- SOI<https://community.icann.org/display/gnsosoi/Rafik+Dammak+SOI> Non Commercial Stakeholder Group Erika Mann - SOI Nominating Committee Appointee 1.3 - Review/amend agenda Item 2: Election of the Chair (15 mins) One nomination was received for this position, James Bladel from the Contracted Parties House. The GNSO Council held a question & answer session with the candidate on [INSERT DATE]. Here the GNSO Council will proceed to elect its Chair for 2017-2018, according to the GNSO Operating Procedures (note Section 2.2 of the GNSO Operating Procedures on 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 Granite 1, Hyderabad International Convention Center on Wednesday, 9 November 2016, 08:30 for 09:00 Appendix 1: Excerpt from GNSO Operating Procedures (Section2.2) https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf Officer Elections: Chair and Vice-Chairs The GNSO Council shall select the GNSO Chair and two Vice-Chairs as follows: * The GNSO Chair shall be elected by a 60 percent vote of each house. * 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 current or incoming 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. * Each house shall select a Council Vice-Chair from within its respective house. * A Chair may not be a member of the same Stakeholder Group of either of the Vice-Chairs. * The Chair and Vice-Chairs shall retain their votes (if any) in their respective houses (if any). * 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 to jointly oversee the new Chair election and conduct Council business until a successful election can be held. In the event that one or both Vice-Chairs' terms ends concurrently with the term of the previous Chair, the procedures described in Section 2.2.1 below shall apply. * 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,<https://www.icann.org/resources/pages/governance/bylaws-en/#article11> Article 11, Section 3) (i) Except as otherwise specified in these Bylaws, Annex A, Annex A-1 or Annex A-2 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: (i) Create an Issues Report: requires an affirmative vote of more than one-fourth (1/4) vote of each House or majority of one House. (ii) Initiate a Policy Development Process ("PDP") Within Scope (as described in Annex A): requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. (iii) Initiate a PDP Not Within Scope: requires an affirmative vote of GNSO Supermajority (as defined in Section 11.3(i)(xix)). (iv) 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. (v) Approve a PDP Team Charter for a PDP Not Within Scope: requires an affirmative vote of a GNSO Supermajority. (vi) Changes to an Approved PDP Team Charter: For any PDP Team Charter approved under (iv) or (v) above, the GNSO Council may approve an amendment to the Charter through a simple majority vote of each House. (vii) 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. (viii) 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. (ix) Approve a PDP Recommendation With a GNSO Supermajority: requires an affirmative vote of a GNSO Supermajority, (x) 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. (xi) Modification of Approved PDP Recommendation: Prior to Final Approval by the Board, an Approved PDP Recommendation may be modified or amended by the GNSO Council with a GNSO Supermajority vote. (xii) Initiation of an Expedited Policy Development Process ("EPDP"): requires an affirmative vote of a GNSO Supermajority. (xiii) Approve an EPDP Team Charter: requires an affirmative vote of a GNSO Supermajority. (xiv) Approval of EPDP Recommendations: requires an affirmative vote of a GNSO Supermajority. (xv) Approve an EPDP 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. (xvi) Initiation of a GNSO Guidance Process ("GGP"): requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. (xvii) Rejection of Initiation of a GGP Requested by the Board: requires an affirmative vote of a GNSO Supermajority. (xviii) Approval of GGP Recommendations: requires an affirmative vote of a GNSO Supermajority. (xix) A "GNSO Supermajority" shall mean: (A) two-thirds (2/3) of the Council members of each House, or (B) three-fourths (3/4) of the Council members of one House and a majority of the Council members of the other House. https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf Appendix 1 GNSO Council Voting Results table Absentee Voting Procedures https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf 4.4 Absentee Voting * Applicability Absentee voting is permitted for the following limited number of Council motions or measures. * Initiate a Policy Development Process (PDP); * Approve a PDP recommendation; * Recommend amendments to the GNSO Operating Procedures (GOP) or ICANN Bylaws; * Fill a Council position open for election. * 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. * 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. * Absentee balloting does not affect quorum requirements. ---------------------------------------------------------------------------- Local time between October and March, Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- Reference (Coordinated Universal Time) UTC 09:45 ---------------------------------------------------------------------------- California, USA (PDT<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) UTC-7+1DST 01:45 San José, Costa Rica UTC-5+1DST 03:45 Iowa City, USA (CDT<http://fr.wikipedia.org/wiki/UTC%E2%88%9206:00>) UTC-5+1DST 03:45 New York/Washington DC, USA (EST) UTC-4+1DST 04:45 Rio de Janiero, Brazil (BRST) UTC-2+1DST 07:45 Buenos Aires, Argentina (ART<http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) UTC+0DST 06:45 London, United Kingdom (BST) UTC+0DST 09:45 Bonn, Germany (CET) UTC+1+0DST 10:45 Amsterdam, Netherlands(CET) UTC+1+0DST 10:45 Cairo, Egypt, (EET) UTC+2+0DST 11:45 Istanbul, Turkey (EEST) UTC+2+0DST 12:45 Singapore (SGT) UTC+8+0DST 17:45 Tokyo, Japan (JST) UTC+9+0DST 18:45 Sydney, Australia (AEDT) UTC +20:45 ---------------------------------------------------------------------------- DST starts/ends on last Sunday of March 2017, 2:00 or 3:00 local time (with exceptions) For other places see http://www.timeanddate.com<http://www.timeanddate.com/> http://tinyurl.com/jds8zkh Glen de Saint Géry Manager Supporting Organisations Advisory Committees Internet Corporation for Assigned Names & Numbers - ICANN glen(a)icann.org<mailto:glen@icann.org> http://www.icann.org<http://www.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

RE: [council] Informal council session Sunday 6 November 19:00 20:00
by Glen de Saint Géry Nov. 6, 2016

Nov. 6, 2016

Dear Julf, There is no adobe connect for the informal meeting. This meeting has no services. Thank you Kind regards, Glen -----Original Message----- From: Johan Helsingius [mailto:julf@julf.com] Sent: Sunday, November 6, 2016 11:15 AM To: Glen de Saint Géry <Glen(a)icann.org>; council(a)gnso.icann.org Subject: Re: [council] Informal council session Sunday 6 November 19:00 20:00 Dear Glen (and everybody), Is there an adobe connect link for this session? Julf On 03-11-16 13:44, Glen de Saint Géry wrote: > > > Dear All, > > > > There will be an informal Council meeting to discuss the feedback from > the Constituencies and Stakeholder groups in preparation for the > Council meeting on Monday 7 November at 13:45. We would like to invite > the Chairs of the constituencies and Stakeholder Groups, or if you > are not able to attend, please let us know who will be representing > you at this meeting which will take place on Sunday 6 November at > 19:00 - 20:00 in Hall 6. There will be drinks and nibbles. > > > > Of course all Councillors are expected to attend as well as those who > are standing in for absent Councillors as temporary alternates. > > > > 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> > > https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org&d=D > QID-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=U4IBJYYYko8geLjS > lTyOXbvtmoVER-_lK-PAQ64rKHs&m=_MzvlNnhOeCNLpGT7PvYOf4XRsMLvJ99KmmtUDl7 > mdY&s=C8SBBzicxrqM37F7Qu9lLYRR5qRNsrPhKGyV84zoXmE&e= > <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_&d > =DQID-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=U4IBJYYYko8geL > jSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=_MzvlNnhOeCNLpGT7PvYOf4XRsMLvJ99KmmtUD > l7mdY&s=KlN50OvWS_f-TuytvKW6CZucM1zYvBHNvfWqKPvdCjc&e= > > > > > /Follow the GNSO via Twitter @ICANN_GNSO/ > > /Find out more about the GNSO by taking our interactive courses > <https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_c > ourses_gnso&d=DQID-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=U > 4IBJYYYko8geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=_MzvlNnhOeCNLpGT7PvYOf4XR > sMLvJ99KmmtUDl7mdY&s=0nIJZPHo28EV863yJWQN-poJYRWzJT4owsQw5LBVHRM&e= > > and visiting the GNSO Newcomer pages > <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_si > tes_gnso.icann.org_files_gnso_presentations_policy-2Defforts.htm-23new > comers&d=DQID-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=U4IBJY > YYko8geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=_MzvlNnhOeCNLpGT7PvYOf4XRsMLvJ > 99KmmtUDl7mdY&s=U6Sd8OE2uFgaWEmD9-FjTEczx391sdqsVo3zuqvjsII&e= >./ > > > > >

1 0

Message from GNSO Council Chairs regarding GNSO and the "small group" proposal
by James M. Bladel Nov. 6, 2016

Nov. 6, 2016

Dear Thomas – Thank you for your email and accompanying clarifications. We do not dispute the chronology of events as you have outlined in your message. However, we would like to clarify a few key points relating to GNSO awareness and participation: · Despite several discussions and email exchanges covering some of the general aspects of the “small group,” the Board letter of 4 October 2016 was the first opportunity for the GNSO Council to review any aspect of the proposal, and consider our response. · Originally we expected a proposal from the “small group” by late 2014 or early 2015, which would have allowed for more timely review action from the GNSO Council and the PDP working group. Unfortunately, the significant delay in receiving the final proposal has created new challenges, and limited the GNSO Council’s options for a response. · ICANN Policy Staff has the full confidence of the GNSO Council. We acknowledge that Staff (and in some instances, the GNSO liaison to the GAC) were involved in some discussions and email exchanges. However, there appears to be a miscommunication about the nature of their involvement. Neither were authorized to represent the GNSO Council in these discussions, nor were the details of “small group” deliberations shared with them. We acknowledge, and to a large degree, we share the frustrations regarding the length of time taken to get to this point. Be assured that the GNSO Council has prioritized this issue, but due to the unprecedented complexity of this topic, we respectfully request that the GAC and the broader community allow us the necessary time to diligently consider our options to move this work towards resolution. Thank you--- Donna Austin, GNSO Council Vice Chair James Bladel, GNSO Council Chair Heather Forrest, GNSO Council Vice Chair Cc: GNSO Council, ICANN Board

1 0

Dinner after our informal meeting
by policy＠paulmcgrady.com Nov. 6, 2016

Nov. 6, 2016

7 6

Draft Response to Board - GNSO Review of IGO/INGO "Small Group" Proposal
by James M. Bladel Nov. 6, 2016

Nov. 6, 2016

Council Colleagues – Attached, please find a draft letter developed by a subteam of Councilors in response to the Board’s letter on IGO Acronyms, and the accompanying “small group” proposal. I recognize that many of you are already en route to Hyderabad, but hopefully you’ll have a chance to review prior to our meeting on 7 NOV. Here are a few highlights: · The Council believes that elements of the “small group” proposal relating to IGO Acronyms were previously and effectively considered in the PDP that was adopted in 2013. · The Council has no current plans to reconsider its standing recommendations to the Board. · While the Council does have a procedure for amending policy recommendations in extraordinary circumstances, this process could have significant implications for future PDPs. o Additionally, any review of previous recommendations is complicated by the nearly 3 year delay since this PDP was adopted. · Those elements that are within scope for the current Curative Rights PDP Working Group have been referred to that WG, which reviewed them during its call on 13 OCT. Finally, we have included a staff-prepared comparison table, highlighting the differences between the PDP, the proposal, and GAC advice, including references to relevant areas of the original PDP Final Report. I hope that these materials will help inform our discussion on 7 NOV, and our response to the Board on this topic. Safe travels, and see you in Hyderabad! Thank you-- J. James Bladel

3 2

DRAFT AGENDA FOR GNSO COUNCIL PUBLIC MEETING (PART 1)7 NOVEMBER 2016 (as at 5 November 2016)
by Glen de Saint Géry Nov. 5, 2016

Nov. 5, 2016

Dear Councillors, Please find the updated draft agenda for the GNSO Council Public Meeting (Part 1) on 7 November 2016 (as at 5 November 2016) The updates are: Two motions<https://community.icann.org/display/gnsocouncilmeetings/Motions+7+November+…> have been moved to the consent agenda. 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/ww_sAw[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> This agenda was established according to the GNSO Operating Procedures<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> v3.2, updated on 01 September 2016. For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. Coordinated Universal Time: 08:15 UTC http://tinyurl.com/zbh2z3m[tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__tinyurl.com_zbh2z3m&d=D…> 00:15 Los Angeles; 03:15 Washington; 08:15 London; 11:15 Istanbul; 13:45 Hyderabad 19:15 Hobart Main Meeting Page https://icann572016.sched.org/event/8cyy/gnso-council-public-meeting[icann5…<https://urldefense.proofpoint.com/v2/url?u=https-3A__icann572016.sched.org_…> Item 1. Administrative Matters (5 mins) 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 13 October 2016 and posted on 4 November 2016. Item 2. Opening Remarks / Review of Projects & Action List (5 mins) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_meetings…> List [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_meetings…> and Action List[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…> Item 3. Consent Agenda (5 mins) See motions<https://community.icann.org/display/gnsocouncilmeetings/Motions+7+November+…> 3.1 - Adopt the GAC-GNSO Consultation Group on GAC Early Engagement in GNSO Policy Development Processes Final Status Report & Recommendations; 3.2 - Approve appointment of a GNSO Liaison to the Governmental Advisory Committee (Carlos Gutiérrez). Item 4. COUNCIL VOTE - Adoption of Consensus Recommendations from the GNSO Bylaws Drafting Team (20 minutes) On 30 June 2016, the GNSO Council created a Drafting Team (DT) to work with ICANN staff to identify the GNSO's new rights and obligations under the revised ICANN Bylaws, and prepare an implementation plan to address any needed changes by 30 September (https://gnso.icann.org/en/council/resolutions#20160630-2)<https://gnso.icann.org/en/council/resolutions#20160630-2%29>. On 29 September 2016, the Council received an update on the status of the DT's work and, pending the completion of the DT's work, the Council voted to appoint the GNSO Chair as its interim representative to the Empowered Community (EC) Administration. At its meeting on 13 October, the Council reviewed the DT's report and recommendations (Final Report: https://gnso.icann.org/en/drafts/bylaws-drafting-team-final-report-12oct16-…; Minority Statement: https://gnso.icann.org/en/drafts/bylaws-drafting-team-minority-report-10oct…) Here the Council will vote on on whether or not to adopt the DT's consensus recommendations. Following the GNSO Council's review and approval of the DT's recommendations, the GNSO is expected to confirm its process for appointing its EC representative going forward. 4.1 - Presentation of the motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+13+October+…> (James Bladel) 4.2 - Council discussion 4.3 - Council vote (voting threshold: simple majority) Item 5. COUNCIL VOTE - Next Steps for the GNSO as a Chartering Organization for the Cross Community Working Group on Internet Governance (20 minutes) The Cross-Community Working Group on Internet Governance Charter<https://community.icann.org/download/attachments/52888213/Charter%20ccWG%20…> for the Cross Community Working Group on Internet Governance (CCWG-IG) was ratified by the ALAC and the ccNSO and GNSO Councils between September 2014 and April 2015. Under its Charter, the CCWG-IG is to "do whatever it deems necessary to facilitate and ensure engagement and participation of the ICANN community in the global Internet governance scene and multi-stakeholder decision-making processes", including providing input to ICANN staff, Supporting Organizations and Advisory Committees on issues pertaining to Internet governance discussions and processes and informing the community about ICANN-related issues arising in Internet governance discussions and processes. As part of its Charter-mandated review of the work of the CCWG-IG, the GNSO Council in 2016 requested and received activity reports from the CCWG co-chairs. Here the Council will evaluate the appropriateness of continuing with the CCWG-IG in light of the deliverables prescribed under the Charter and in the context of the recently adopted Uniform Framework of Principles for Cross Community Working Groups<https://gnso.icann.org/en/drafts/uniform-framework-principles-recommendatio…>. 5.1 - Presentation of the motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+7+November+…> (James Bladel) 5.2 - Council discussion 5.3 - Council vote (voting threshold: simple majority) ---------- BREAK (15 MINUTES) ---------- Item 6: COUNCIL VOTE - Chartering of a New Cross Community Working Group on New gTLD Auction Proceeds (20 minutes) The 2012 New gTLD Program established auctions as a mechanism of last resort to resolve string contention. Although most string contention sets have been resolved through other means prior to reaching the stage of an auction conducted by ICANN's authorized auction service provider, it was recognized from the outset that significant funds could accrue as a result of several auctions. As such, any and all auction proceeds have been reserved and earmarked until the Board authorizes a plan for the appropriate use of the funds. The Board, staff, and community are expected to work together in designing the appropriate processes for addressing the use of the new gTLD auction proceeds. To this end, a cross-community Drafting Team (DT) was formed which has now submitted a proposed Charter<https://community.icann.org/x/mRuOAw> for a cross-community working group to all SO/ACs for consideration. The proposed charter is the result of extensive community input and DT deliberations and the DT presented it in the belief that it represents a careful balance between the different viewpoints and perspectives, including from the DT members and the ICANN Board liaisons to the DT. At its meeting on 29 September 2016, the GNSO Council received a briefing and update on the draft Charter and the work of the DT from Jonathan Robinson, the DT chair. As there were no substantive suggested edits to the draft Charter received consequently from the GNSO, the Council will here consider whether or not to become one of the Chartering Organizations for the proposed new CCWG. 6.1 - Presentation of the motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+7+November+…> 6.2 - Council discussion 6.3 - Council vote (voting threshold: simple majority) Item 7. COUNCIL DISCUSSION - ICANN Board Letter regarding policy implications of the Final Report of the Internationalized Registration Data (IRD) Expert Working Group (15 minutes) On 11 May 2016, ICANN Board Chair Dr. Steve Crocker sent a letter to the GNSO Council following up on the Board's 10 March 2016 Resolution (see https://gnso.icann.org/en/correspondence/crocker-to-bladel-11may16-en.pdf)<https://gnso.icann.org/en/correspondence/crocker-to-bladel-11may16-en.pdf%29>. The Board's request was for the GNSO Council to "review the broader policy implications of the IRD Final Report<http://whois.icann.org/sites/default/files/files/ird-expert-wg-final-23sep1…> 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 GNSO Council sought input from the co-chairs of the recently completed GNSO Policy Development Process on the Translation and Transliteration of gTLD Contact Data, requesting feedback on several specific points: (1) how certain recommendations in the IRD Final Report were considered, if at all, in the Final Report<https://gnso.icann.org/en/issues/gtlds/translation-transliteration-contact-…> of the T&T PDP Working Group; (2) how those recommendations could potentially conflict with the T&T PDP Working Group's recommendations that have been adopted by the GNSO Council and the ICANN Board; and (3) What steps are recommended to the GNSO Council in considering the policy implications of the IRD Final Report. Here the Council will discuss the input received from a member of the T&T PDP Working Group (https://gnso.icann.org/en/drafts/ird-tt-recs-10oct16-en.pdf) [CHECK THAT LINK IS CORRECT], and decide on next steps. 7.1 - Status update (GNSO Council chairs) 7.2 - Council discussion 7.3 - Next steps Item 8. Discussion - Results of GNSO Newcomer Survey (5 minutes) On 30 June 2016, the GNSO Council directed<https://gnso.icann.org/en/council/resolutions#20160630-1> ICANN staff to develop a survey to "assess the familiarity that the community has with the different newcomer and training tools as well as their perceived usefulness", as part of the permanent integration of successful Policy Development Process (PDP) pilot project improvements into the overall structure of PDPs. Here the Council will receive a report on the results of the survey (https://gnso.icann.org/en/drafts/newcomer-tools-survey-04oct16-en.pdf) and consider whether staff should proceed with implementing some of the suggested improvements following additional input (if any) from GNSO Stakeholder Groups and Constituencies. 8.1 - Summary and update (David Tait) 8.2 - Council discussion 8.3 - Next steps Item 9. Open Microphone (10 Minutes) Item 10: 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[icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_en_about_…>): 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[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_council_…>) 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) 08:15 UTC Local time between October and March Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT)UTC-7+0DST 00:15 San José, Costa Rica UTC-5+0DST 02:15 Iowa City, USA (CDT<https://urldefense.proofpoint.com/v2/url?u=http-3A__fr.wikipedia.org_wiki_U…>) UTC-5+0DST 02:15 New York/Washington DC, USA (EST) UTC-4+0DST 03:15 Buenos Aires, Argentina (ART) UTC-3+0DST 09:00 Rio de Janiero, Brazil (BRST) UTC-3+0DST 09:00 London, United Kingdom (BST) UTC+0DST 08:15 Bonn, Germany (CET) UTC+1+0DST 09:15 Cairo, Egypt, (EET) UTC+2+0DST 10:15 Istanbul, Turkey (EEST) UTC+3+0DST 11:15 Perth, Australia (WST) UTC+8+0DST 16:15 Singapore (SGT) UTC +8 +0DST 16:15 Sydney/Hobart, Australia (AEDT) UTC+11+0DST 19:15 ---------------------------------------------------------------------------- DST starts/ends on last Sunday of March 2017, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com[timeanddate.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.timeanddate.com&d=D…> http://tinyurl.com/zbh2z3m ________________________________

1 0

Proposed Scope of RDS Review
by James M. Bladel Nov. 5, 2016

Nov. 5, 2016

Council Colleagues – Attached, please find a proposal for the scope of the upcoming RDS (WHOIS2) Review Team. This was buried in my inbox, so apologies for the delay in sending. We should discuss & submit our feedback to Staff before the doc is finalized. Thanks— J.

1 0