October 2014 - council - lists.icann.org

Global Domains Division update
by Bruce Tonkin 13 Oct '14

13 Oct '14

Hello All, From: http://la51.icann.org/en/schedule/mon-gdd/presentation-gdd-13oct14-en I have attached the presentation from the Global Domains Division (GDD) Update session. Regards, Bruce Tonkin

1 0

ccNSO-GNSO Council meeting will start at 17.15, not 17.00
by Marika Konings 13 Oct '14

13 Oct '14

Dear All, Please note that today¹s ccNSO-GNSO Council meeting will start at 17.15 instead of 17.00 as noted in the schedule. The meeting takes place in Constellation. Please inform your respective groups accordingly. Thanks, Marika

1 0

FW: New Liaison Statement, "Liaison Statement from the IAB to the ICANN Board on Technical Use of Domain Names"
by Jonathan Robinson 12 Oct '14

12 Oct '14

All, Sincere apologies, it looks like I missed this when it was sent to me. Jonathan -----Original Message----- From: Jonne Soininen [mailto:jonne.soininen@icann.org] Sent: 15 September 2014 12:59 To: ICANN Board of Directors ICANN; jonathan.robinson(a)ipracon.com Cc: Russ Housley Subject: Fwd: New Liaison Statement, "Liaison Statement from the IAB to the ICANN Board on Technical Use of Domain Names" Dear Board and the chair of the GNSO council, please, see enclosed a liaison statement the IETF/IAB has sent to the ICANN Board. Though, the main recipient is the ICANN board, I believe it is useful for the GNSO council to see this as well. Best Regards, Jonne. Begin forwarded message: > From: Liaison Statement Management Tool <lsmt(a)ietf.org> > Subject: New Liaison Statement, "Liaison Statement from the IAB to the ICANN Board on Technical Use of Domain Names" > Date: 15 Sep 2014 18:10:25 GMT+3 > To: <jonne.soininen(a)icann.org> > Cc: Jonne Soininen <jonne.soininen(a)nsn.com>, The IAB Chair > <iab-chair(a)iab.org>, The IAB <iab(a)iab.org>, The IAB Executive Director > <execd(a)iab.org> > > Title: Liaison Statement from the IAB to the ICANN Board on Technical > Use of Domain Names Submission Date: 2014-09-15 URL of the IETF Web > page: http://datatracker.ietf.org/liaison/1351/ > > From: The IAB (Russ Housley <housley(a)vigilsec.com>) > To: ICANN Board of Directors (jonne.soininen(a)icann.org) > Cc: Jonne Soininen <jonne.soininen(a)nsn.com>,The IAB Chair > <iab-chair(a)iab.org>,The IAB <iab(a)iab.org>,The IAB Executive Director <execd(a)iab.org> Response Contact: > Technical Contact: > Purpose: For information > > Body: Dear colleagues, > > We are writing this note in order to share with you some work in the > IETF regarding domain names for "technical use," as described in RFC > 2860. > > In RFC 2860 ("Memorandum of Understanding Concerning the Technical > Work of the Internet Assigned Numbers Authority," June 2000), the IAB > acknowledged the authority of ICANN for policies relating to the > assignment of domain names, but retained authority over "assignments > of domain names for technical use" (Section 4.3, pg 2): > > >> 4.3. Two particular assigned spaces present policy issues in addition >> to the technical considerations specified by the IETF: the assignment >> of domain names, and the assignment of IP address blocks. These >> policy issues are outside the scope of this MOU. >> >> Note that (a) assignments of domain names for technical uses (such as >> domain names for inverse DNS lookup), (b) assignments of specialised >> address blocks (such as multicast or anycast blocks), and (c) >> experimental assignments are not considered to be policy issues, and >> shall remain subject to the provisions of this Section 4. > > In order to support appropriate technical use of domain names in the > context of its protocol development work, the IETF approved RFC 6761 > ("Special-Use Domain Names," February 2013). As directed, IANA > established and populated a registry for such special-use names > (http://www.iana.org/assignments/special-use-domain-names/special-use-domain -names.xhtml). > > Recently, several requests have come to the IETF for names to be added > to the special-use domain names registry > (See: > http://www.ietf.org/archive/id/draft-chapin-additional-reserved-tlds-0 > 1.txt > and > http://www.ietf.org/archive/id/draft-grothoff-iesg-special-use-p2p-names-02. txt). > > Discussion of these requests under the process established in RFC 6761 > has revealed difficulties in applying its guidelines in practice. > Under its current charter, the DNSOP working group in the IETF is > responsible to review and clarify the overlap between (among other > things) the special names registry from RFC 6761 and the public DNS > root. This could include consideration of the problem of existing name > collisions, provision of additional guidelines, or further > modification to the process in RFC 6761 to reduce the potential for > collisions in the future. Any changes are to be kept within the > constraints of RFC 2860 (or any future modification to RFC 2860). > > All such discussion and any modification will be open and transparent > to participation by interested parties, in accordance with established > IETF processes. We invite participation of interested parties, > including members of the ICANN community, in this work. > > On behalf of the IAB, > Russ Housley > IAB Chair > Attachments: > > No document has been attached > -- Jonne Soininen Tel: +358 40 527 4634 E-mail: jonne.soininen(a)icann.org

1 0

Translations Services
by john＠crediblecontext.com 12 Oct '14

12 Oct '14

All, I wonder if the Council specifically and the GNSO generally has grown and diversified to the point where its meetings ought to deploy real-time translation services. The current Council has native German and Swedish and Spanish and Portuguese and Hebrew and Chinese speakers on whose good will we now rely for our English-only meetings. This diversity likely will only get more so as ICANN becomes the global organization it was chartered to be. We have had the good fortune of having Councillors who are able to handle the proceedings in English, but is that the image we want to portray and does it limit others from even seeking a seat? Such a move would also help us better make the case for the work of the GNSO and its Council to the expanding number of people who attend these meetings from a growing number of nations. I think this might be a good item for the wrap-up session. Cheers, Berard

8 10

Proposed GNSO Council LA Public Meeting, Part 2 agenda 15 October 2014 at 15:15 PDT (22:15)
by Glen de Saint Géry 12 Oct '14

12 Oct '14

Dear Councillors, Please find the proposed agenda for the GNSO Council Public Meeting, Part 2 in Los Angeles on 15 October 2014 at 15:15 PDT. 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 22:15 UTC http://tinyurl.com/plgz5gl Coordinated Universal Time 22:15 UTC 15:15 Los Angeles; 18:15 Washington; 23:15 London; 00:15 Paris; Main Meeting Page: http://la51.icann.org/en/schedule/wed-gnso-council-admin Dial-in numbers will be sent individually to Council members. Councillors should notify the GNSO Secretariat in advance if a dial out call is needed. Item 1: Seating of the 2014 / 2015 Council (20 mins) 1.1 Roll Call 1.2 Statements of interest · Carlos Raul Guterriez - SOI<https://community.icann.org/display/gnsosoi/Carlos+Raul+Gutierrez+SOI> Nominating Committee Appointee · Donna Austin - SOI<https://community.icann.org/display/gnsosoi/Donna+Austin+SOI> Registries Stakeholder Group · Edward Morris - SOI<https://community.icann.org/display/gnsosoi/Edward+Morris+SOI> Non Commercial Stakeholder Group · Heather Forrest - SOI<https://community.icann.org/display/gnsosoi/Heather+Forrest+SOI> Intellectual Property Constituency · Marilia Ferreira Maciel - SOI<https://community.icann.org/pages/viewpage.action?pageId=49353624> Non Commercial Stakeholder Group · Stephanie Perrin - SOI<https://community.icann.org/display/gnsosoi/Stephanie+Perrin+SOI> Non Commercial Stakeholder Group · Susan Kawaguchi - SOI<https://community.icann.org/display/gnsosoi/Susan+Kawaguchi+SOI> Commercial and Business Users Constituency 1.3 Review/amend agenda Item 2: Election of the Chair (30 mins) One nomination was received for this position, Jonathan Robinson. The GNSO Council held a question & answer session over the weekend with Jonathan Robinson. The Council to proceed to elect the chair according to the GNSO Operating Procedures. GNSO Operating Procedures http://gnso.icann.org/en/council/gnso-operating-procedures-13sep12-en.pdf Note: Section 2.2 Officer Elections: Chair and Vice-Chairs (see Appendix 1 below) Item 3: Any Other Business (10 mins) Reminder: The Council development meeting will take place at 12025 Waterfront Drive, 2nd Floor, Los Angeles, CA 90094-2536 on Friday 17 October 2014, 10h00. Appendix 1: Excerpt from GNSO Operating Procedures (Section2.2) http://gnso.icann.org/en/council/gnso-operating-procedures-13sep12-en.pdf 2.2 Officer Elections: Chair and Vice-Chairs The GNSO Council shall select the GNSO Chair and two Vice-Chairs as follows: a. The GNSO Chair shall be elected by a 60 percent vote of each house. b. Each house will be allowed to nominate one candidate for GNSO Council Chair. Each house is responsible for determining how to nominate its candidate. A candidate for GNSO Council Chair does not need to be a member of a house, but must be a member of the GNSO Council. Should a Chair be elected from outside of the houses that Chair will be a non-voting Chair. i. 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. ii. 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. iii. 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." iv. 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." v. 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. c. Each house shall select a Council Vice-Chair from within its respective house. d. A Chair may not be a member of the same Stakeholder Group of either of the Vice-Chairs. e. The Chair and Vice-Chairs shall retain their votes (if any) in their respective houses (if any). f. In the event that the GNSO Council has not elected a GNSO Council Chair by the end of the previous Chair's term, the Vice-Chairs will serve as Interim GNSO Co-Chairs until a successful election can be held. g. The Council shall inform the Board and the Community appropriately and post the election results on the GNSO website within 2 business days following each election and runoff ballot, whether successful or unsuccessful. Appendix 2: GNSO Council Voting Thresholds (ICANN Bylaws, Article X, Section 3) 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 3: 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 October and March, Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- ---------------------------------------------------------------------------- Reference (Coordinated Universal Time) UTC 22:15 ---------------------------------------------------------------------------- California, USA (PDT<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) UTC-7+1DST 15:15 San José, Costa Rica UTC-6+0DST 16:15 Iowa City, USA (CDT<http://fr.wikipedia.org/wiki/UTC%E2%88%9206:00>) UTC-5+1DST 17:15 New York/Washington DC, USA (EST) UTC-4+1DST 18:15 Rio de Janiero, Brazil (BRST) UTC-2+1DST 19:15 Montevideo, Uruguay (UYST<http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) UTC-2+1DST 20:15 Buenos Aires, Argentina (ART<http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) UTC-3+0DST 19:15 London, United Kingdom (BST) UTC+0DST 23:15 Bonn, Germany (CET) UTC+1+0DST 00:15 (next day) Cairo, Egypt, (EET) UTC+2+0DST 00:15 (next day) Istanbul, Turkey (EEST) UTC+2+0DST 01:15 (next day) Ramat Hasharon, Israel(IDT<http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.…>) UTC+3+0DST 01:15 (next day) Beijing/Hong Kong, China (HKT ) UTC+8+0DST 06:15 (next day) Perth, Australia (WST<http://timeanddate.com/library/abbreviations/timezones/au/wst.html>) UTC+8+1DST 06:15 (next day) Melbourne, Australia UTC+11+1DST 09:15 (next day) ---------------------------------------------------------------------------- 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/plgz5gl Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/>

1 0

Theresa's slides
by Marika Konings 12 Oct '14

12 Oct '14

Dear All, Please find attached the slides from Theresa's presentation this morning. Best regards, Marika

1 0

Slides from Theresa Swinehart Update
by Lars Hoffmann 12 Oct '14

12 Oct '14

Dear all, Please find attached the slides presented today by Theresa Swinehart. You can also find all slide decks from yesterday¹s and today¹s sessions here: http://bit.ly/LA51GNSOSat http://bit.ly/LA51GNSOSun Best wishes, Lars

1 0

Blog post: what's up with Whois
by Marika Konings 12 Oct '14

12 Oct '14

For your information, please find below a blog post from Margie Milam in relation to Whois Accuracy. Please note that the pilot study will be further discussed during Monday's All Things Whois Session (see http://la51.icann.org/en/schedule/mon-whois). Best regards, Marika What's Up with WHOIS? <https://www.addthis.com/bookmark.php?v=300&winname=addthis&pub=ra-52fcc7eb 243d6d89&source=tbx32-300&lng=en-US&s=linkedin&url=https%3A%2F%2Fwww.icann.o rg%2Fnews%2Fblog%2Fwhat-s-up-with-whois&title=What%27s%20Up%20with%20WHOIS%3 F%20-%20ICANN&ate=AT-ra-52fcc7eb243d6d89/-/-/543aabd43b830f7f/2&frommenu=1&u id=543aabd44d2e65e2&ct=1&pre=https%3A%2F%2Fwww.icann.org%2Fnews%2Fblog%3Flan guage%3Den&tt=0&captcha_provider=nucaptcha> <https://www.icann.org/news/blog/what-s-up-with-whois#> <https://www.icann.org/news/blog/what-s-up-with-whois#> <https://www.addthis.com/bookmark.php?v=300&winname=addthis&pub=ra-52fcc7eb2 43d6d89&source=tbx32-300&lng=en-US&s=sinaweibo&url=https%3A%2F%2Fwww.icann.o rg%2Fnews%2Fblog%2Fwhat-s-up-with-whois&title=What%27s%20Up%20with%20WHOIS%3 F%20-%20ICANN&ate=AT-ra-52fcc7eb243d6d89/-/-/543aabd43b830f7f/3&frommenu=1&u id=543aabd439220ece&ct=1&pre=https%3A%2F%2Fwww.icann.org%2Fnews%2Fblog%3Flan guage%3Den&tt=0&captcha_provider=nucaptcha> <https://www.icann.org/news/blog/what-s-up-with-whois#> <https://www.icann.org/news/blog/what-s-up-with-whois#> After several years of reporting on the status of WHOIS related activities, I have good news to share. WHOIS Accuracy Rates are slowly improving, as reflected in the latest Preliminary Findings paper <http://whois.icann.org/sites/default/files/files/accuracy-reporting-pilot-p relim-10oct14-en.pdf> [PDF, 668 KB] published today by the National Opinion Research Council (NORC) at the University of Chicago. These findings suggest that there is still more work to be done to bring up accuracy rates. After examining nearly 100,000 WHOIS records, NORC's Preliminary Findings highlight important observations regarding the Pilot Study: * Operationally, Registrars under the 2013 RAA have more accuracy for email addresses than Registrars under the 2009 RAA; * New gTLDs have slightly better operational email accuracy rates than prior gTLDs; * Prior gTLDs have more operational accuracy on telephone numbers, but the two groups are equal on operational postal address accuracy. The Preliminary Findings paper <http://whois.icann.org/sites/default/files/files/accuracy-reporting-pilot-p relim-10oct14-en.pdf> [PDF, 668 KB] describes the analysis conducted by NORC, after collaborating with intergovernmental and private sector firms. Relying on expertise from the Universal Postal Union, the UN agency responsible for coordinating global postal policies, and commercial service providers such as StrikeIron, DigiCert and Whibse, NORC applied the latest technology available to validate email addresses, telephone numbers and postal addresses to varying degrees, each at a syntactical and operational level. This expertise is reflected in the methodology adopted by NORC in assigning the different accuracy rates described in the Preliminary Findings paper. The purpose of the Pilot Study is to test assumptions using real data. The methodology can be adjusted based upon the consultations in Los Angeles, as well as the public comments received. The paper <http://whois.icann.org/sites/default/files/files/accuracy-reporting-pilot-p relim-10oct14-en.pdf> [PDF, 668 KB] is published for the LA Meeting to demonstrate how ICANN's WHOIS Accuracy Reporting System (ARS) is being designed. The ARS, when fully developed, will produce periodic accuracy reports to enable you to track whether policy changes or changing contract terms produce measurable improvements in accuracy. It will also include a feedback mechanism where potentially inaccurate records are forwarded to registrars for action and it will include a tracking mechanism to see if the records are appropriately updated. A full study report, with updated findings and statistics, will be published for Public Comment following the ICANN Los Angeles Meeting. Join us in Los Angeles at the All Things WHOIS Session <http://la51.icann.org/en/schedule/mon-whois> to explore these findings in detail, as well as to share your perspective on how the ARS should be developed in the future. The session will also cover the latest developments <http://whois.icann.org/en/file/final-recommendations-implementation-status- 08oct14-en> related to WHOIS Improvement activities, and it will explore the future of WHOIS, in light of the Recommendations of the Expert Working Group (EWG) on gTLD Directory Services <https://www.icann.org/resources/pages/gtld-directory-services-2013-02-14-en > . To learn more about the EWG's Recommendations from their Final Report <https://www.icann.org/en/system/files/files/final-report-06jun14-en.pdf> [5.11 MB], a series of short videos <https://community.icann.org/display/WG/EWG+Multimedia+FAQs> have been recorded to answer key aspects of their Final Report <https://www.icann.org/en/system/files/files/final-report-06jun14-en.pdf> [5.11 MB]. We look forward to seeing you in Los Angeles.

1 0

FW: ICANN LA Wine Tasting Reception Invitation 15 October 2014
by Glen de Saint Géry 12 Oct '14

12 Oct '14

On behalf of:Taylor, David Dear GNSO Council Please find attached an invitation to a Wine Tasting event on Wednesday at 5.30pm. It will be held in the Grand Salon Ballroom at the Intercontinental. In this way we can drink some decent wine rather than just talking about .WINE! Organized by the wine regions, there will be wine and senior representatives from Napa Valley, Santa Barbara County, Long Island, Oregon and Champagne. In addition to the applicants being invited, ICANN staff and Board are also invited. Numbers are limited so if you wish to attend please do RSVP to the email contact(a)wineorigins.com<mailto:contact@wineorigins.com> with "ICANN LA Wine Tasting" in the subject line and also please do copy me in (david.taylor(a)hoganlovells.com<mailto:david.taylor@hoganlovells.com>). [Description: Description: Description: Description: Description: http://www.designab.com/protectplace/html/Postcard-Invitation-digital-01.jpg]<http://r20.rs6.net/tn.jsp?f=001PHsaNSmiOBDShD1mTc3TKlr7uQ57tj5WIWFgp38g2QIF…> Kind regards David Dr. David Taylor Partner ________________________________ Hogan Lovells International LLP 17, avenue Matignon 75008 Paris Tel: +33 1 53 67 47 47 Fax: +33 1 53 67 47 48 Email: drd(a)hoganlovells.com<mailto:drd@hoganlovells.com> www.hoganlovells.com<http://www.hoganlovells.com/> ________________________________ ________________________________ Hogan Lovells (Paris) LLP is a limited liability partnership registered in England and Wales with registered number OC353350, and is authorised and regulated by the Solicitors Regulation Authority of England and Wales. Registered office: Atlantic House, Holborn Viaduct, London EC1A 2FG. Hogan Lovells (Paris) LLP is an affiliated business of Hogan Lovells International LLP, a limited liability partnership registered in England and Wales. "Hogan Lovells" is an international legal practice that includes Hogan Lovells International LLP, Hogan Lovells US LLP and their affiliated businesses. The word "partner" is used to describe a partner or member of Hogan Lovells International LLP, Hogan Lovells US LLP or any of their affiliated entities or any employee or consultant with equivalent standing. Certain individuals, who are designated as partners, but who are not members of Hogan Lovells International LLP, do not hold qualifications equivalent to members. For more information about Hogan Lovells, the partners and their qualifications, see www.hoganlovells.com<http://www.hoganlovells.com>. CONFIDENTIALITY. This email and any attachments are confidential, except where the email is marked "officiel". It may also be privileged. If received in error, please do not disclose the contents to anyone, but notify the sender by return email and delete this email (and any attachments) from your system.

1 0

Prposed GNSO Council Public Meeting Agenda 15 October 2014 13:00 PDT. (20:00 UTC)
by Glen de Saint Géry 11 Oct '14

11 Oct '14

Dear Councillors, Please find the proposed GNSO Council Public Meeting Agenda on 15 October 2014 at 20:00 UTC. 13:00 PDT. 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 20:00 UTC: http://tinyurl.com/k4e8m2k Coordinated Universal Time 20:00 UTC 13:00 Los Angeles; 16:00 Washington; 21:00 London; 22:00 Brussels; 04:00 Perth Dial-in numbers will be sent individually to Council members who cannot be physically present at the meeting. Councillors should notify the GNSO Secretariat in advance if a dial out call is needed. http://la51.icann.org/en/schedule/wed-gnso-council Item 1: Administrative matters (5 mins) 1.1 Roll Call 1.2 Statement of interest updates 1.3 Review/amend agenda 1.4. Note the status of minutes for the previous Council meeting per the GNSO Operating Procedures: Minutes of the GNSO Council meeting 4<http://gnso.icann.org/mailing-lists/archives/council/msg16716.html> and 25 September 2014<http://gnso.icann.org/mailing-lists/archives/council/msg16717.html> will be posted as approved on 11 October 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 of Projects List<http://gnso.icann.org/meetings/projects-list.pdf> and Action List<https://community.icann.org/display/gnsocouncilmeetings/Action+Items>. Comments or questions arising. Item 3: Consent agenda (5 mins) Item 4: MOTION - On the adoption of the IRTP Part D Final Report and Recommendations (15 mins) The final report<http://gnso.icann.org/en/issues/transfers/irtp-d-final-25sep14-en.pdf> of the policy work on the inter-registrar transfer process has been published. The Inter-Registrar Transfer Policy (IRTP) provides the policy framework for domain name transfers between registrars. The IRTP also provides standardized requirements for inter-registrar transfer disputes - through the Transfer Dispute Resolution Policy (TDRP). The policy is an existing community consensus policy that was implemented in late 2004 and has been revised numerous times since then. The IRTP Part D Policy Development Process (PDP) is the fourth and final PDP of this series of revisions. The Generic Names Supporting Organization (GNSO) Council resolved at its meeting on 17 October 2012 to launch an Issue Report on IRTP Part D, "which should include all the remaining issues identified by the original transfers Working Groups as well as the additional issue identified by the IRTP Part C WG." Here the Council will vote on whether or not to adopt the IRTP Part D Final Report and Recommendations. 4.1 - Review the motion: Motion 1<https://community.icann.org/display/gnsocouncilmeetings/Motions+15+October+…> 4.2 - Discussion 4.3 - Vote Item 5: MOTION - To adopt the Charter for a Cross Community Working Group to discuss Internet governance (CWG-IG) issues affecting ICANN and to make recommendations to the chartering organisation on these issues (15 mins) The Internet Governance Cross Community Working Group CWG has been established by the participating SO's and AC's to coordinate, facilitate, and increase the participation of the ICANN community in discussions and processes pertaining to Internet Governance. All issues, processes and discussions regarding the Transition of NTIA's Stewardship of the IANA Functions, and/or current and future accountability and accountability mechanisms related to the aforementioned Transition, are deemed to be out of scope of the objective of the WG. The CWG has a charter<http://ccnso.icann.org/workinggroups/ccwg-ig-charter-20may14-en.pdf> which has previously been adopted by ICANN's ALAC, ccNSO and SSAC. In this item the GNSO Council will vote on whether or not to adopt the charter of the CWG. 5.1 - Review the motion: Motion 2<https://community.icann.org/display/gnsocouncilmeetings/Motions+15+October+…> 5.2 - Discussion 5.3 - Vote Item 6: UPDATE - A GNSO liaison to the GAC (10 mins) The council voted to appoint Mason Cole as the GNSO Liaison to the GAC with immediate effect such that he can be well informed and up to speed in order to participate effectively as soon as possible and, in particular, at ICANN 51. Here the Council will have an opportunity to hear from Mason Cole with any initial input and feedback derived from the ICANN meeting in Los Angeles. 6.1 - Update (Mason Cole) 6.2 - Discussion Item 7: UPDATE - A letter to the ICANN NGPC regarding the proposed modification of GNSO consensus recommendations relating to IGO acronyms and Red Cross identifiers (10 mins) On 10 November 2013 the PDP Working Group (IGO-INGO PDP WG) delivered its Final Report<http://gnso.icann.org/en/issues/igo-ingo-final-10nov13-en.pdf> to the GNSO Council that included twenty-five consensus recommendations. On 20 November 2013 the GNSO Council unanimously adopted<http://gnso.icann.org/en/council/resolutions#20131120-2> all twenty-five consensus recommendations of the IGO-INGO PDP WG and forwarded them to the ICANN Board in January 2014 with a recommendation for their adoption. On 30 April 2014 the Board resolved<https://www.icann.org/resources/board-material/resolutions-2014-04-30-en> to adopt those of the GNSO's recommendations that are not inconsistent with GAC advice, and to facilitate dialogue between the affected parties in order to reconcile the remaining differences, as further detailed in Annex A<https://www.icann.org/en/groups/board/documents/resolutions-annex-a-30apr14…> and Annex B<https://www.icann.org/en/groups/board/documents/resolutions-annex-b-30apr14…> of the Board's resolution. The GNSO's recommendations and GAC advice are largely consistent except in relation to the duration and mechanism of protection for IGO acronyms and the full names and acronyms of 189 Red Cross national societies and the international Red Cross and Red Crescent movement, for which the GNSO had recommended<http://gnso.icann.org/en/council/resolutions#20131120-2> a 90-day period of protection by way of a claim notification service utilising the Trademark Clearinghouse (TMCH). On 16 June 2014 the NGPC sent<http://gnso.icann.org/en/correspondence/chalaby-to-robinson-16jun14-en.pdf> a letter to the GNSO Council requesting that the GNSO consider modifying its recommendations relating to the duration and mechanism of protection for IGO acronyms and national society names of the Red Cross. This modification to be in accordance with and as envisaged by Section 16 of the GNSO's PDP Manual<http://gnso.icann.org/council/annex-2-pdp-manual-13jun13-en.pdf>. On 24 July 2014, the Chair of the NGPC followed up with a note to the Chair of the GNSO Council and offered to provide a written or oral briefing to provide greater clarity on the GAC's advice and expectations with respect to protections of IGO-INGO Identifiers. As a result of the briefing it was agreed to send a follow-up letter to the NGPC which has now been done (see http://gnso.icann.org/en/correspondence/robinson-to-chalaby-disspain-07oct1…) . Here the Council will have the opportunity to receive an update and discuss any next steps. 7.1 - Update (Thomas Rickert / Mary Wong) 7.2 - Next steps Item 8: - UPDATE - Name Collision On the 30 July 2014, the New gTLD Program Committee of the ICANN Board directed staff to "provide information to, and work with the GNSO to consider whether policy work on developing a long-term plan to manage gTLD name collision issues should be undertaken." ICANN Staff submitted this paper to the GNSO Council on 7 October 2014 (see https://www.icann.org/en/system/files/files/name-collision-gnso-policy-07oc…). This is an opportunity for the Council to discuss which steps, if any, it would like to take in relation to this topic. 8.1 Discussion 8.2 Next steps Item 9: UPDATE - A cross community working group to develop a transition proposal for IANA stewardship on naming related functions (10 mins) A drafting team (DT) was formed with participants from the ccNSO, GNSO, SSAC and ALAC to develop a charter for a Cross Community Working Group to Develop an IANA Stewardship Transition Proposal on Naming Related Functions. Following adoption of the charter<http://gnso.icann.org/en/drafts/iana-stewardship-naming-function-charter-14…> at the previous meeting, this is an opportunity for the Council to receive a brief update on the next steps. 9.1 - Update (Jonathan Robinson) 9.2 - Next steps Item 10: Thanks to outgoing councillors and ALAC Liaison (5 mins) * Jennifer Wolfe (NCA) * Ching Chiao (RySG) * John Berard (CSG / BC) * Magaly Pazello (NCSG) * Klaus Stoll (NCSG) * Alan Greenberg (ALAC Liaison) * Maria Farrell (NCSG) * Petter Rindforth (IPC) Item 11: Any Other Business (5 mins) Item 12: Open microphone 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 20:00 ---------------------------------------------------------------------------- California, USA (PDT<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) UTC-7+1DST 13:00 Iowa City, USA (CDT<http://fr.wikipedia.org/wiki/UTC%E2%88%9206:00>) UTC-5+1DST 15:00 New York/Washington DC, USA (EST) UTC-4+1DST 16:00 Rio de Janiero, Brazil (BRST) UTC-2+1DST 17:00 Montevideo, Uruguay (UYST<http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) UTC-2+1DST 18:00 Buenos Aires, Argentina (ART<http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) UTC-3+0DST 17:00 London, United Kingdom (BST) UTC+0DST 21:00 Bonn, Germany (CET) UTC+1+0DST 22:00 Stockholm, Sweden (CET) UTC+1+0DST 22:00 Cairo, Egypt, (EET) UTC+2+0DST 22:00 Istanbul, Turkey (EEST) UTC+2+0DST 23:00 Ramat Hasharon, Israel(IDT<http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.…>) UTC+3+0DST 23:00 Beijing/Hong Kong, China (HKT ) UTC+8+0DST 04:00 (next day) Perth, Australia (WST<http://timeanddate.com/library/abbreviations/timezones/au/wst.html>) UTC+8+0DST 04:00 (next day) ---------------------------------------------------------------------------- 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/k4e8m2k Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/>

1 0