April 2014 - council - lists.icann.org

Please participate - Singapore meeting survey
by Marika Konings April 10, 2014

April 10, 2014

Reminder if you have not done so yet, please participate in this survey. For those of you that have responded, thank you very much! As indicated, please feel free to share the survey with your respective groups as we are also interested to hear the feedback of non-Council members. From: Marika Konings <marika.konings(a)icann.org> Date: Thursday 27 March 2014 08:21 To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] Please participate - Singapore meeting survey Dear All, As discussed, please participate in the following survey to provide your feedback on the GNSO related meetings at the ICANN meeting in Singapore that will help prepare us in our planning efforts for the ICANN meeting in London. Please feel free to share this with your respective communities. To participate, please go to: https://www.surveymonkey.com/s/JB5MDBH. Thanks, Marika

1 0

TR: GNSO Council Abstention Notification Form [#144]
by Glen de Saint Géry April 10, 2014

April 10, 2014

De : ICANN [mailto:no-reply@wufoo.com] Envoyé : jeudi 10 avril 2014 09:53 À : gnso.secretariat(a)icann.org; council(a)gnso.icann.org Objet : GNSO Council Abstention Notification Form [#144] Name of Officer: * Rafik Dammak Officer Email Address: * rafik.dammak(a)gmail.com<mailto:rafik.dammak@gmail.com> Date Prepared: * Thursday, April 10, 2014 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: * David Cake won't be able to attend the GNSO council call since he is travelling Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: * Avri Doria will submit David's vote by proxy for the motions to be approved, and any other matters needing a vote. 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, April 11, 2014 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: * Avri Doria

1 0

FW: BRG FAQ Specification 13 - GNSO Council Discussion 10 Apr.
by Jonathan Robinson April 9, 2014

April 9, 2014

All, Please see the note below (and associate attachment) from Martin Sutton. In the interests of achieving our objective tomorrow i.e. being as fully informed as possible, I propose to take him up on his offer of being available to answer questions. Thanks, Jonathan From: martinsutton(a)hsbc.com [mailto:martinsutton@hsbc.com] Sent: 09 April 2014 10:38 To: Jonathan Robinson Subject: BRG FAQ Specification 13 - GNSO Council Discussion 10 Apr. Dear Jonathan, I note that the next GNSO Council meeting is scheduled for 10 April and includes a discussion item for Specification 13 and the proposed incorporation of an additional clause, which the NGPC has referred to GNSO. In order to support these discussions, the Brand Registry Group (BRG) has prepared the following set of FAQs that I trust will assist the GNSO Council's deliberations: Furthermore, I would be glad to make myself available to join the the telephone meeting on 10 April to answer any resulting or related questions. If this would be helpful, please advise me of the time and contact information. Finally, you may have already seen that ICANN has recently posted the correspondence from Gretchen Olive, CSC, which was sent through on the morning of the NGPC meeting in Singapore. The correspondence includes letters from 48 .brand applicants, arranged in just a couple of days, urging ICANN to reinstate the exclusive registrar provision. Considering most of these companies are not BRG members and would have had to jump considerable hoops in order to issue public statements of this nature, I think it is useful for the GNSO Council to bear in mind when considering their response to spec 13 - there is a much broader impact than just the BRG. A copy of the correspondence can be found here - <http://www.icann.org/en/news/correspondence/olive-to-crocker-et-al-26mar14- en.pdf> http://www.icann.org/en/news/correspondence/olive-to-crocker-et-al-26mar14-e n.pdf. I look forward to hearing from you. Kind regards, Martin Sutton President, Brand Registry Group Martin C SUTTON Manager, Group Fraud Risk & Intelligence Global Security & Fraud Risk Level 8,1 Canada Square,Canary Wharf,London,E14 5AB,United Kingdom __________________________________________________________________ Phone +44 (0)207 991 8074 Mobile +44 (0)777 4556680 Email <mailto:martinsutton@hsbc.com> martinsutton(a)hsbc.com Website <http://www.hsbc.com/> www.hsbc.com __________________________________________________________________ Protect our environment - please only print this if you have to! ************************************************************ HSBC Holdings plc Registered Office: 8 Canada Square, London E14 5HQ, United Kingdom Registered in England number 617987 ************************************************************ ************************************************************ HSBC Holdings plc Registered Office: 8 Canada Square, London E14 5HQ, United Kingdom Registered in England number 617987 ************************************************************ ----------------------------------------- SAVE PAPER - THINK BEFORE YOU PRINT! This E-mail is confidential. It may also be legally privileged. If you are not the addressee you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return E-mail. Internet communications cannot be guaranteed to be timely secure, error or virus-free. The sender does not accept liability for any errors or omissions.

6 10

Updated GNSO Project List for review for Council meeting 10 April 2014
by Glen de Saint Géry April 9, 2014

April 9, 2014

Dear Councillors, Please find attached for your review the revised project list, both in redline and clean format, in preparation for the GNSO Council meeting on 10 April at 14:00 UTC. For reference, the updated project list is posted at: http://gnso.icann.org/meetings/projects-list.pdf on page : http://gnso.icann.org/en/council/project under the heading: Council activities 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

1 0

Updated draft agenda for the GNSO Council Meeting 10 April 2014 at 14:00 UTC
by Glen de Saint Géry April 9, 2014

April 9, 2014

Dear All, Please see the updated draft agenda for the GNSO Council Meeting 10 April 2014. The updates are as follows: · Item 3: Consent agenda [Confirmation of the NCPH election of Board Seat 14] has been removed and thus, there is nothing under the consent agenda for this meeting. · Item 6: AOB the following item has been added: 6.3 Consideration of a co-chair for the CWG on country names and territories as TLDs. To date two volunteers have come forward, Ching Chiao and Heather Forrest. Please let me know if you have any questions. Thank you very much. Kind regards, Glen Proposed Agenda for the GNSO Council Meeting 10 April 2014 http://gnso.icann.org/en/meetings/agenda-council-10apr14-en.htm https://community.icann.org/display/gnsocouncilmeetings/Agenda+10th+April+2… This agenda was established according to the GNSO Council Operating Procedures approved 13 September 2012 for the GNSO Council and updated. <http://gnso.icann.org/en/council/op-procedures-13jun13-en.pdf> 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. Meeting Times 14:00 UTC http://tinyurl.com/mfscjuu Coordinated Universal Time 14:00 UTC 07:00 Los Angeles; 10:00 Washington; 15:00 London; 16:00 Paris; 22:00 Perth; 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: Administrative matters (5 mins) 1.1 Roll Call 1.2 Statement of interest updates 1.3 Review/amend the Agenda Note the status of minutes for the previous Council meeting per the GNSO Operating Procedures: * Minutes of the GNSO Council meeting 27 February 2014 will be posted as approved on xxxx 2014 * Minutes of the GNSO Council meeting 26 March 2014 will be posted as approved on xxxx 2014 Item 2: Opening Remarks / Review of Projects & Action List (10 mins) Review focus areas and provide updates on specific key themes / topics Include review Action List<https://community.icann.org/display/gnsocouncilmeetings/Action+Items>. Comments or questions arising. Item 3: Consent agenda (0 mins) Item 4: DISCUSSION - GNSO Council advice regarding Specification 13 of the new gTLD registry agreement (20 mins) The ICANN new gTLD Programme Committee (NGPC) has approved Specification 13 to the New gTLD Registry Agreement, see link<http://www.icann.org/en/groups/board/documents/resolutions-new-gtld-annex-1…>. However, this does not currently include a proposed clause allowing a so-called .Brand registry operator to designate a limited number preferred registrars for the TLD. The NGPC has approved the incorporation of the additional proposed clause (allowing a .Brand registry operator to designate a limited number of preferred registrars) but its implementation will not take effect until 45 days from the publication of this resolution in order to: (i) provide the GNSO Council with an opportunity to advise ICANN as to whether the GNSO Council believes that this additional provision is inconsistent with the letter and intent of GNSO Policy Recommendation 19 on the Introduction of New Generic Top-Level Domains; OR (ii) advise ICANN that the GNSO Council needs additional time for review, including an explanation as to why additional time is required. In this item, the Council will receive background information in order to fully inform the discussion and to plan the next steps. 4.1 - Background 4.2 - Discussion 4.2 - Next steps Item 5: DISCUSSION - Internet Governance Issues (20 mins) The transition of stewardship of the IANA function from the US government is now firmly on the GNSO's agenda and the Council must determine its role and function with respect to this. In this item, the Council will take the opportunity to pick up from the meeting in Singapore, including inputs into the public forum on Thursday and decide on any next steps. 5.1 - Discussion 5.2 - Next steps Item 6: Any Other Business (15 mins) 6.1 Submission of Council input to the call for Public Comment on ICANN Strategy Panels - Draft Reports http://www.icann.org/en/news/public-comment/strategy-panels-25feb14-en.htm 6.2 Submission of Council input to the call for Public Comment on ICANN Future Meetings Strategy http://www.icann.org/en/news/public-comment/meetings-strategy-25feb14-en.htm 6.3 Consideration of a co-chair for the CWG on country names and territories as TLDs. To date two volunteers have come forward, Ching Chiao and Heather Forrest. 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.) ---------------------------------------------------------------------------- Local time between March and October, Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- Reference (Coordinated Universal Time) UTC 14:00 ---------------------------------------------------------------------------- California, USA (PDT<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) UTC-7+1DST 07:00 Iowa City, USA (CST<http://fr.wikipedia.org/wiki/UTC%E2%88%9206:00>) UTC-6+1DST 09:00 New York/Washington DC, USA (EST) UTC-4+1DST 10:00 Rio de Janiero, Brazil (BRST) UTC-2+1DST 11:00 Montevideo, Uruguay (UYST<http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) UTC-2+1DST 11:00 Buenos Aires, Argentina (ART<http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) UTC-3+0DST 11:00 London, United Kingdom (BST) UTC+0DST 15:00 Bonn, Germany (CET) UTC+1+0DST 16:00 Stockholm, Sweden (CET) UTC+1+0DST 16:00 Cairo, Egypt, (EET) UTC+2+0DST 16:00 Istanbul, Turkey (EEST) UTC+2+0DST 17:00 Ramat Hasharon, Israel(IST<http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.…>) UTC+2+0DST 17:00 Beijing/Hong Kong, China (HKT ) UTC+8+0DST 22:00 Perth, Australia (WST<http://timeanddate.com/library/abbreviations/timezones/au/wst.html>) UTC+8+0DST 22:00 ---------------------------------------------------------------------------- DST starts/ends on last Sunday of October 2014, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com http://tinyurl.com/mfscjuu Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

FW: [Soac-infoalert] Initial IANA Transition Process Draft Posted
by Jonathan Robinson April 9, 2014

April 9, 2014

All. FYI. Jonathan. From: soac-infoalert-bounces(a)icann.org [mailto:soac-infoalert-bounces@icann.org] On Behalf Of David Olive Sent: 09 April 2014 07:26 To: soac-infoalert(a)icann.org Subject: [Soac-infoalert] Initial IANA Transition Process Draft Posted 1. Initial Transition Process Draft Posted Public Comment Period Begins Read <http://www.icann.org/en/about/agreements/iana/transition/draft-proposal-08a pr14-en.htm> the Draft Proposal and Click <http://www.icann.org/en/about/agreements/iana/transition/draft-proposal-08a pr14-en.htm> Its Links Watch <http://youtu.be/xyYOFgyuxQc> Theresa Swinehart's Community Message Check Out <http://www.icann.org/en/about/agreements/iana/functions-basics-08apr14-en.p df> the IANA Basics Watch <https://www.youtube.com/watch?v=D__mAX-2sXo> IANA in 180 Seconds -- David A. Olive Vice President, Policy Development Support General Manager, ICANN Regional Headquarters -Istanbul Internet Corporation for Assigned Names and Numbers (ICANN) Hakki Yeten Cad. Selenium Plaza No:10/C K:5 34349 Fulya, Besiktas, Istanbul, Turkey Tel: +90.212.381.8727 - Fax: +90.212.381.8731 - Mobile: +1. 202.341.3611

1 0

Two page summary of the IANA functions
by Bruce Tonkin April 8, 2014

April 8, 2014

Hello All, From: http://www.icann.org/en/about/agreements/iana/functions-basics-07apr14-en.p… Attached is a short two page summary of the IANA functions that may be useful when trying to explain these functions to members of your communities. Regards, Bruce Tonkin

3 2

TR: GNSO Council Abstention Notification Form [#143]
by Glen de Saint Géry April 8, 2014

April 8, 2014

FYI De : ICANN [mailto:no-reply@wufoo.com] Envoyé : mardi 8 avril 2014 03:31 À : gnso.secretariat(a)icann.org; council(a)gnso.icann.org Objet : GNSO Council Abstention Notification Form [#143] Name of Officer: * Michele Neylon Officer Email Address: * michele(a)blacknight.com<mailto:michele@blacknight.com> Date Prepared: * Monday, April 7, 2014 GNSO Organization: * Registrars Stakeholder Group Officer Position or Title: * Chair Voting Remedy: * Proxy Reason(s) for or condition(s) leading to the remedy: * Yoav Keren unable to attend upcoming GNSO meeting Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: * Any motions requiring a vote 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] * Wednesday, April 30, 2014 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: * James Bladel

1 0

Resolution on .wine//vin/GAC Communique from new gTLD program committee meeting on 4 April 2014
by Bruce Tonkin April 7, 2014

April 7, 2014

http://www.icann.org/en/groups/board/documents/resolutions-new-gtld-04apr14… 1. Main Agenda: Meeting on 3 April 2014 at 22:00 UTC continued to 4 April 2014 at 21:00 UTC. The following resolutions were adopted on 4 April 2014: a. Applications for .vin and .wine/ GAC Communiqué - Singapore Whereas, on 9 September 2013, in a letter to the ICANN Board, the Governmental Advisory Committee (GAC) advised the Board that the GAC had finalized its consideration of the strings .WINE and .VIN, that there was no GAC consensus advice on additional safeguards for .WINE and .VIN, and that the applications for .WINE and .VIN should proceed through the normal evaluation process. Whereas, on 20 November 2013, the GAC issued its Buenos Aires Communiqué, wherein it suggested that the Board may wish to seek a clear understanding of the legally complex and politically sensitive background on its advice regarding .WINE and .VIN in order to consider the appropriate next steps of delegating the two strings. Whereas, the NGPC asked staff to commission an independent legal analysis ("Independent Legal Analysis") of the legally complex and politically sensitive background on the GAC's advice regarding .WINE and .VIN. Whereas, on 22 March 2014, in Resolution 2014.03.22.NG01, the NGPC "accept[ed] the GAC advice identified in the GAC Register of Advice as 2013-09-09-wine and vin, and direct[ed] the President and CEO, or his designee, that the applications for .WINE and .VIN should proceed through the normal evaluation process." Whereas, as noted in the Rationale of Resolution 2014.03.22.NG01, the NGPC considered the Independent Legal Analysis as part of its deliberations on the GAC's advice, which is published at http://www.icann.org/en/groups/board/documents/analysis-wine-vin-22mar14-en… [PDF, 771 KB]. Whereas, on 27 March 2014, in the Singapore Communiqué, the GAC noted that "there appears to be at least one process violation and procedural error, including in relation to ByLaws Article XI-A, Section 1 subsection 6" in the ICANN Board's final deliberation of Resolution 2014.03.22.NG01 and advised that the ICANN Board reconsider the matter before delegating these strings. Whereas, in the Singapore Communiqué, the GAC further advised that "concerned GAC members believe the applicants and interested parties should be encouraged to continue their negotiations with a view to reach an agreement on the matter." Whereas, the NGPC has reviewed and considered the matter set forth in the Singapore Communiqué, specifically the issue raised by the GAC relating to its suggestion of a possible process violation or procedural error under ICANN Bylaws Article XI-A, Section 1, subsection 6. Whereas, the NGPC recognizes that some GAC members remain concerned about the .WINE and .VIN applications, and the NGPC recognizes that this is a matter of great importance to these GAC members, as well as to the interested applicants for these top level domains. Resolved (2014.04.04.NG01), the NGPC accepts the GAC advice identified in the Singapore Communiqué as it relates to the applications for .WINE and .VIN. Resolved (2014.04.04.NG02), upon having considered the matter set forth in the GAC Singapore Communiqué suggesting that there may have been a process violation or procedural error, the NGPC concludes that there has been no process violation or procedural error under the Bylaws. Resolved (2014.04.04.NG03), the NGPC directs the President and CEO, or his designee, to not commence the contracting process for the applications for .WINE and .VIN for 60 days from the date of publication of these resolutions in order to provide additional time for the relevant impacted parties to negotiate, which they are encouraged to do. Resolved (2014.04.04.NG04), the NGPC recommends that the full Board consider the larger implications of legally complex and politically sensitive issues such as those raised by GAC members, including whether ICANN is the proper venue in which to resolve these issues, or whether there are venues or forums better suited to address concerns such as those raised by GAC members in relation to the .WINE and .VIN applications.

1 0

an announcement from Mikey -- i'm retiring from ICANN
by Mike O'Connor April 7, 2014

April 7, 2014

dear all, just a quick note to let you know that i am retiring from ICANN. right now. how about that? it’s spring here at the farm and i’ve realized that it’s time for me to redirect my attention to things closer to home and heart. as you can see by the number of mailing lists this note is addressed to, i’ve spread myself too thin. somewhere along the line i burned myself out. i never was very good at seeing this “burnout" thing coming. oops... as to the “immediately” timeframe — well, i’m burned out. which means that the prospect of ICANN-related work just leaves me cold. so rather than drag myself (and you) through some half-baked transition period where i do an even worse job than i’ve been doing lately, i’m just making a clean break of it. it will turn out fine. you’ll see. as of this note i’m setting down all the trappings. GNSO Councillor, ISPCP support, the working groups, all the leadership-development and newcomer-orientation projects. i’m not throwing them down, just placing them gently there for somebody else to pick up and run with. this is the place where i’m supposed to write about how i’ll miss you all. but i’m not going to do that. through the miracle of this Internet thing, i plan to stay connected to you and maintain all those friendships that have developed over the years. i’m just stopping the work, not the relationships. maybe some day i’ll even dip my toe back into a working group or two. but not right away. right now that goes on the Too Hard pile. here’s a link to a pictorial tour of the farm. http://www.aprairiehaven.com/?page_id=23369 see that bench? that’s where i’ll be sitting, thinking of you. come visit. Marcie and i will show you around. onward, mikey PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)

1 0