- ispcp - lists.icann.org

RV: Catering Options
by Novoa, Osvaldo Aug. 3, 2018

Aug. 3, 2018

Hello Chantelle and all, Sorry, I thought you had all received the catering quotation. I am enclosing Gonzalo's mail with it. There are several options. For coffee break, the cheapest (only something to drink) would be Euros 2.68 per person, including some pastries it would be Euros 4.57 per person. For lunch the cheapest would be Euros 18.90 per person, I think this is a good option. According to Gonzalo's mail, to this you have to add 21% VAT and 2 waiters (100 Euros each) Best regards, Osvaldo De: GONZALO LOPEZ-BARAJAS HUDER [mailto:gonzalo.lopezbarajashuder@telefonica.com] Enviado el: martes, 24 de julio de 2018 12:52 p.m. Para: Novoa, Osvaldo; 'Anthony Harris' Asunto: Catering Options Osvaldo, Anthony, These are the catering options I got from our organisation at the Telefonica Auditorium in Barcelona. The quotation I gave you for the coffe was based on Coffe break number 1 for 100 persons. On of the prices you had to include 21% of taxes (VAT) and 2 waiters (aprox. 100 euros/each). The 3 lunch options are all priced at 18.9 euros per person (aprox. 23euros including taxes). So for one hundred persons price would be 2.500 euros aprox. This is indicative. If you indicate me an exact number of persons, two options as you mention, I can ask for a precise quotation. Regards, Gonzalo Gonzalo Lopez-Barajas | Telefónica, S.A. Manager Public Policy and Internet <https://www.telefonica.com/en/web/public-policy/blog> g.lopezbarajas(a)telefonica.com<mailto:g.lopezbarajas@telefonica.com> Office: (+34) 91 482 88 10 Mobile: (+34) 629 59 24 48 @Gonzalo_LB [rrss_blog]<https://www.telefonica.com/en/web/public-policy/blog?p_l_id=2367319&p_p_id=…>[rrss_twitter]<https://twitter.com/tefpublicpolicy/>[rrss_linkedin]<https://www.linkedin.com/company/10587207?trk=tyah&trkInfo=clickedVertical%…>[rrss_youtube]<https://www.youtube.com/user/telefpublicpolicy>[Screenshot_2] ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição ________________________________ El presente correo y cualquier posible archivo adjunto está dirigido únicamente al destinatario del mensaje y contiene información que puede ser confidencial. Si Ud. no es el destinatario correcto por favor notifique al remitente respondiendo anexando este mensaje y elimine inmediatamente el e-mail y los posibles archivos adjuntos al mismo de su sistema. Está prohibida cualquier utilización, difusión o copia de este e-mail por cualquier persona o entidad que no sean las específicas destinatarias del mensaje. ANTEL no acepta ninguna responsabilidad con respecto a cualquier comunicación que haya sido emitida incumpliendo nuestra Política de Seguridad de la Información This e-mail and any attachment is confidential and is intended solely for the addressee(s). If you are not intended recipient please inform the sender immediately, answering this e-mail and delete it as well as the attached files. Any use, circulation or copy of this e-mail by any person or entity that is not the specific addressee(s) is prohibited. ANTEL is not responsible for any communication emitted without respecting our Information Security Policy.

1 0

REMINDER TO REGISTER IN ADVANCE - Announcement: Pre-ICANN62 Policy Webinar, register by 11 June
by Chantelle Doerksen June 4, 2018

June 4, 2018

https://www.icann.org/news/announcement-2018-05-23-en Register Now: Pre-ICANN62 Policy Webinar – 12 June 2018 The Policy Development Support Team is pleased to announce two webinar sessions to assist with the community's preparations for the ICANN62 Policy Forum: Pre-ICANN62 Policy Webinar Tuesday, 12 June 2018 10:00 and 19:00 Coordinated Universal Time (UTC) The webinar will run in English with simultaneous Spanish interpretation. The presentation materials will be translated into Spanish, and posted following the Webinar with the recordings of the sessions here. Please register via this form by 11 June 2018! In this 90-minute webinar, the Policy Development Support Team will summarize the key policy activities taking place across the ICANN community. The Team will also answer your questions about ongoing community policy and advisory work and discuss what to expect at the ICANN62Policy Forum. To ensure that your questions about policy activities are addressed during the session, the Policy Team invites you to submit your questions through the registration form or by email to policyinfo(a)icann.org. To assist with your preparation for this webinar and for ICANN62, the "Pre-ICANN62 Policy Report" and "Generic Names Supporting Organization Policy Briefing: ICANN62 Edition" will be published by Tuesday, 5 June 2018. Please be sure to download and review these materials beforehand for helpful background on policy activities and topics that the Policy Development Support Team will cover during the webinar, such as: · The cross-community discussions that will take place at ICANN62: · Geographic Names at the Top-Level (Work Track 5) · Update from the Registration Directory Service-WHOIS2 Review Team · General Data Protection Regulation (GDPR) Compliance, Access to WHOIS and Accreditation · The expected Initial Report from the New generic Top-Level Domain (gTLD) Auction Proceeds Cross Community Working Group · Presentation of the Final CCWG-Accountability Work Stream 2 Recommendations · The various policy development processes underway in the Country Code Names Supporting Organization (ccNSO), the Generic Names Supporting Organization (GNSO) and the Address Supporting Organization (ASO): · Retirement of Country Code Top-Level Domains · Review of All Rights Protection Mechanisms in All gTLDs · Next steps in relation to Registration Directory Services policy work · Curative Rights Protections for International Governmental Organizations and International Non-Governmental Organizations · New gTLD Subsequent Procedures · Regional Internet Registry policy development activities · Advisory Committee activities within the At Large Advisory Committee (ALAC), Governmental Advisory Committee (GAC), Root Server System Advisory Committee (RSSAC) and Security & Stability Advisory Committee (SSAC): · Organizational Review of the At-Large community: Next steps, implementation, and ALACsessions during ICANN62 · GDPR and Key Signing Key (KSK) Rollover discussions · At-Large discussion on new gTLDs and Work Tracks 1-5 · Regional At-Large Organization (RALO) Policy Hot Topics · GAC discussions on .amazon, IGO protections and 2-character codes at the second level · Board-GAC GDPR consultations · RSSAC statement on the distinction between RSSAC and Root-Ops (RSSAC033) · SSAC work concerning name collisions · Other topics of note: · Organizational Review of the ASO · ccNSO sessions on disaster and recovery and business continuity, ccNSO members meeting sessions, and Tech Day. · GAC onboarding initiatives · Report from the RSSAC May 2018 Workshop (RSSAC034) To complement this Pre-ICANN62 Policy Webinar, the GNSO Policy Development Support Team will host, with the Council leadership and Policy Development Process (PDP) working group chairs, a GNSOpolicy-focused webinar on Monday, 18 June 2018 at 21:00 UTC for 90 minutes. This webinar is intended to serve as a replacement for the previously-offered GNSO PDP updates provided during the GNSO weekend sessions and will assist the community in preparing for GNSO policy-related discussions at ICANN62. If you would like to participate in the GNSO Policy Webinar, please register here. The Policy Development Support Team looks forward to helping the ICANN community prepare for ICANN62!

1 0

RV: Comments from the Internet Service Providers and Connectivity Providers constituency
by Novoa, Osvaldo May 7, 2018

May 7, 2018

Dear Wolf-Ulrich, I fully support Alain’s report. If nobody objects it should be sent today to ICANN. Best regards, Osvaldo Novoa De: alain.bidron(a)orange.com [mailto:alain.bidron@orange.com] Enviado el: viernes, 04 de mayo de 2018 01:13 p.m. Para: WUKnoben; Tony Holmes; Novoa, Osvaldo; Harris Anthony Asunto: Fwd: Comments from the Internet Service Providers and Connectivity Providers constituency Dear colleagues. As promised, I have tried to draft an ISPCP response (see document attached) to the draft report on NomCom review. The deadline is May 7 23:59 UTC. Unfortunately (for ISPCP) I am still in the US and my availability and connectivity will be limited. My flight back to France will be May 7 th. I have not circulated it to the whole ISPCP list because I may not be in a position to respond, to modify or post an improved document to ICANN . Please I need some help. Regards Alain. Début du message transféré : Expéditeur: gmail <alain.bidron(a)gmail.com<mailto:alain.bidron@gmail.com>> Date: 4 mai 2018 à 10:02:02 UTC−6 Destinataire: <alain.ipad(a)orange.fr<mailto:alain.ipad@orange.fr>>, <alain.bidron(a)orange.com<mailto:alain.bidron@orange.com>> Objet: Comments from the Internet Service Providers and Connectivity Providers constituency _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. ________________________________ El presente correo y cualquier posible archivo adjunto está dirigido únicamente al destinatario del mensaje y contiene información que puede ser confidencial. Si Ud. no es el destinatario correcto por favor notifique al remitente respondiendo anexando este mensaje y elimine inmediatamente el e-mail y los posibles archivos adjuntos al mismo de su sistema. Está prohibida cualquier utilización, difusión o copia de este e-mail por cualquier persona o entidad que no sean las específicas destinatarias del mensaje. ANTEL no acepta ninguna responsabilidad con respecto a cualquier comunicación que haya sido emitida incumpliendo nuestra Política de Seguridad de la Información This e-mail and any attachment is confidential and is intended solely for the addressee(s). If you are not intended recipient please inform the sender immediately, answering this e-mail and delete it as well as the attached files. Any use, circulation or copy of this e-mail by any person or entity that is not the specific addressee(s) is prohibited. ANTEL is not responsible for any communication emitted without respecting our Information Security Policy.

2 1

Fwd: NomCom2 Review Draft Report
by Novoa, Osvaldo April 27, 2018

April 27, 2018

Dear Alain, Tom Barrett sent me this recommendation regarding the NomCom review which he would like us to support. What are your considerations on it. I think it might be a good idea to have a NomCom Standing Committee to be the continuing thread between different NomComs. Best regards, Osvaldo Inicio del mensaje reenviado: De: Tom Barrett <tbarrett(a)encirca.com<mailto:tbarrett@encirca.com>> Asunto: Re: NomCom2 Review Draft Report Fecha: 24 de abril de 2018, 15:47:26 UYT Para: "Novoa, Osvaldo" <onovoa(a)antel.com.uy<mailto:onovoa@antel.com.uy>> Dear Osvaldo, The new recommendation is described in the attached draft comment from the RrSG. I would be happy to join you and your team on a call to discuss. best regards, Tom -- Thomas Barrett President EnCirca, Inc +1.781.942.9975 (office) 400 W. Cummings Park, Suite 1725 Woburn, MA 01801 USA ________________________________ El presente correo y cualquier posible archivo adjunto está dirigido únicamente al destinatario del mensaje y contiene información que puede ser confidencial. Si Ud. no es el destinatario correcto por favor notifique al remitente respondiendo anexando este mensaje y elimine inmediatamente el e-mail y los posibles archivos adjuntos al mismo de su sistema. Está prohibida cualquier utilización, difusión o copia de este e-mail por cualquier persona o entidad que no sean las específicas destinatarias del mensaje. ANTEL no acepta ninguna responsabilidad con respecto a cualquier comunicación que haya sido emitida incumpliendo nuestra Política de Seguridad de la Información This e-mail and any attachment is confidential and is intended solely for the addressee(s). If you are not intended recipient please inform the sender immediately, answering this e-mail and delete it as well as the attached files. Any use, circulation or copy of this e-mail by any person or entity that is not the specific addressee(s) is prohibited. ANTEL is not responsible for any communication emitted without respecting our Information Security Policy.

1 0

Pre-ICANN61 Policy Report and GNSO Policy Briefing
by Chantelle Doerksen Feb. 26, 2018

Feb. 26, 2018

[cid:image001.png@01D3AF26.9C48C870] --Pre-ICANN61 Policy report: http://go.icann.org/pre61 --GNSO Policy Briefing for ICANN61 is now available: http://go.icann.org/gnsobriefing

1 0

Register Now: Pre-ICANN61 Policy Open House – 1 March 2018 - ICANN
by Chantelle Doerksen Feb. 8, 2018

Feb. 8, 2018

https://www.icann.org/news/announcement-2-2018-02-08-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Register Now: Pre-ICANN61 Policy Open House – 1 March 2018 The Policy Development Support Team is pleased to announce two sessions for an upcoming webinar: Pre-ICANN61 Policy Open House Thursday, 1 March 2018 10:00 and 19:00 Coordinated Universal Time (UTC) The webinar will run in English and will be conducted in Adobe Connect along with a dial-in conference bridge for audio. Recordings of the sessions will be made available here[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. Please register via this form[goo.gl]<https://urldefense.proofpoint.com/v2/url?u=https-3A__goo.gl_vZw8kM&d=DwMGaQ…> by 26 February 2018! In this interactive 60-minute open house, the focus will be an active question and answer session with the Policy Development Support Team. To ensure that your questions about policy activities are addressed during the session, the Policy Team invites you to submit your questions through the registration form[goo.gl]<https://urldefense.proofpoint.com/v2/url?u=https-3A__goo.gl_forms_dVbmhQOT8…> or email them to policyinfo(a)icann.org<mailto:policyinfo@icann.org>. To assist with your preparation for this webinar and for ICANN61, the "Pre-ICANN61 Policy Report" and "Generic Names Supporting Organization Policy Briefing: ICANN61 Edition" will be published by Monday, 26 February 2018. Please be sure to download and review these materials beforehand for helpful background on policy activities and topics that the Policy Development Support Team will discuss during the open house, such as: * An overview of the cross-community discussions that will take place at ICANN61: * General Data Protection Regulation (GDPR): WHOIS Compliance Models * A Walk in the Shoes of a New Generic Top-Level Domain (gTLD) Registry Operator * Name Collisions * Open Data at ICANN * Policy development processes underway in the Country Code Names Supporting Organization (ccNSO), the Generic Names Supporting Organization (GNSO) and the Address Supporting Organization (ASO): * Retirement of Country Code Top-Level Domains (ccTLDs) * Review of All Rights Protection Mechanisms in All gTLDs * Next-Generation Registration Directory Service to Replace WHOIS * International Governmental Organizations and International Non-Governmental Organizations Access to Curative Rights Dispute Resolution Mechanisms * Protections for Red Cross National Society Names in the Domain Name System * New gTLD Subsequent Procedures * Regional Internet Registry policy development activities * Advisory Committee activities within the At Large Advisory Committee (ALAC), Governmental Advisory Committee (GAC), Root Server System Advisory Committee (RSSAC) and Security & Stability Advisory Committee (SSAC): * Organizational Review of the At-Large community * At-Large Summit (ATLAS) III * GAC discussion on the .amazon Independent Review Process * GAC discussion on evolving relationships with ICANN Board and ICANN Org * RSSAC statement on entries in DNS Root Sources * RSSAC & SSAC Response to the GNSO's New gTLD Subsequent Procedures Working Group on Root Scaling * SSAC Response to the ICANN Internationalized Domain Name Guidelines Working Group * SSAC work concerning the use of emoji in domain names * Other topics of note: * Organizational Review of the ASO * ccNSO Rejection Action Procedure as a Decisional Participant in the ICANN Empowered Community * Impact of ICANN's Implementation of the General Data Protection Regulation (GDPR) on ccTLDs The Policy Development Support Team looks forward to helping the ICANN community prepare for ICANN61! Please register via this form[goo.gl]<https://urldefense.proofpoint.com/v2/url?u=https-3A__goo.gl_vZw8kM&d=DwMGaQ…> by 26 February 2018! About ICANN ICANN's mission is to help ensure a stable, secure and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world.

1 0

Fwd: [Gnso-igo-ingo-crp] IGO-INGO Curative Rights Working Group co-chairs
by Novoa, Osvaldo Jan. 12, 2018

Jan. 12, 2018

Dear all, For your information, there’s been a conflict in this WG between the chairs and some members regarding the Chairs objectivity the transparency, which has caused a delay in the work of the group. Unfortunately I wasn’t able to participate in yesterday`s call, but it seems that it was totally unproductive and there is going to be a new call next week, in which I will try to participate. One of the main issues is the use of anonymous polling to reach decisions, which some say is against Working Groups Guidelines and others that it restricts the transparency of the WG decisions. I hope it can be solve quickly and we can continue with our work. I will keep you all informed of the results of the call. Best regards, Osvaldo ________________________________ El presente correo y cualquier posible archivo adjunto está dirigido únicamente al destinatario del mensaje y contiene información que puede ser confidencial. Si Ud. no es el destinatario correcto por favor notifique al remitente respondiendo anexando este mensaje y elimine inmediatamente el e-mail y los posibles archivos adjuntos al mismo de su sistema. Está prohibida cualquier utilización, difusión o copia de este e-mail por cualquier persona o entidad que no sean las específicas destinatarias del mensaje. ANTEL no acepta ninguna responsabilidad con respecto a cualquier comunicación que haya sido emitida incumpliendo nuestra Política de Seguridad de la Información This e-mail and any attachment is confidential and is intended solely for the addressee(s). If you are not intended recipient please inform the sender immediately, answering this e-mail and delete it as well as the attached files. Any use, circulation or copy of this e-mail by any person or entity that is not the specific addressee(s) is prohibited. ANTEL is not responsible for any communication emitted without respecting our Information Security Policy.

1 0

WG: [council] ICANN60: GNSO Sessions How to Get Organized and Remote Participation Details
by wolf-ulrich.knoben＠t-online.de Oct. 17, 2017

Oct. 17, 2017

FYI Best regards Wolf-Ulrich -----Original-Nachricht----- Von: Nathalie Peregrine <nathalie.peregrine(a)icann.org <mailto:nathalie.peregrine@icann.org> > Betreff: [council] ICANN60: GNSO Sessions How to Get Organized and Remote Participation Details Datum: 17.10.2017, 16:29 Uhr An: council(a)gnso.icann.org <council(a)gnso.icann.org <mailto:council@gnso.icann.org> > CC: gnso-secs(a)icann.org <gnso-secs(a)icann.org <mailto:gnso-secs@icann.org> > Dear all, The one-stop wiki page for all your Remote Participation queries is now available. This wiki page covers remote participation details for all GNSO open and public meetings. In addition to this, ICANN meetings’ team has put together a new ICANN meeting website which allows you to download all GNSO-related meetings to your inbox calendar in one go. 2 LINKS TO BOOKMARK NOW: ICANN60 Meeting Schedule[schedule.icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__schedule.icann.org_&d=…> GNSO Remote Participation wiki page <https://community.icann.org/x/7ichB> Step 1 – Create a profile and your personalized ICANN60 schedule Go to the Meeting Schedule webpage, and if not done yet for previous meetings, create a profile and login. Every session on the schedule can be selected and added to your individual schedule. By clicking to the left of each meeting, this adds it to your individual schedule which you can then email to yourself or add to your calendar. See next step. Step 2 At the top right-hand corner of the page click on the ‘Mobile App + ical” icon to download the mobile app and choose from various options how to sync your personalized schedule to your phone or laptop calendars. Step 3 All Adobe Connect rooms (which can be found on the session information on the Meeting Schedule and on the GNSO Remote Participation wiki page) will provide audio streaming. If you cannot join an Adobe Connect room for a session, and will need to dial in with your phone, please refer to the GNSO Remote Participation wiki page for the audio pass codes and dial in numbers. Please also follow the previous steps if you wish to take part in the session over the phone. Nathalie Peregrine and Terri Agnew will be onsite to assist you directly. For all GNSO meeting related queries (RP or others), please email us at: gnso-secs(a)icann.org <applewebdata://FB60497E-61D8-4FE9-BF9C-EB238191E416/gnso-secs@icann.org> and we will be more than happy to assist! Kind regards, GNSO SO/AC Support team _______________________________________________ council mailing list council(a)gnso.icann.org https://mm.icann.org/mailman/listinfo/council

1 0

WG: [So-ac-sg-cleaders] ICANN61 Still Slated for Puerto Rico - ICANN
by wolf-ulrich.knoben＠t-online.de Oct. 7, 2017

Oct. 7, 2017

FYI Best regards Wolf-Ulrich -----Original-Nachricht----- Von: David Olive <david.olive(a)icann.org <mailto:david.olive@icann.org> > Betreff: [So-ac-sg-cleaders] ICANN61 Still Slated for Puerto Rico - ICANN Datum: 07.10.2017, 04:12 Uhr An: so-ac-sg-cleaders(a)icann.org <so-ac-sg-cleaders(a)icann.org <mailto:so-ac-sg-cleaders@icann.org> >, soac-leaders-icannmeeting-planning(a)icann.org < soac-leaders-icannmeeting-planning(a)icann.org <mailto:soac-leaders-icannmeeting-planning@icann.org> > https://www.icann.org/news/blog/icann61-still-slated-for-puerto-rico <https://www.icann.org/news/blog/icann61-still-slated-for-puerto-rico> ICANN61 Still Slated for Puerto Rico <https://www.icann.org/news/blog/icann61-still-slated-for-puerto-rico#> <https://www.icann.org/news/blog/icann61-still-slated-for-puerto-rico#> <https://www.icann.org/news/blog/icann61-still-slated-for-puerto-rico#> <https://www.icann.org/news/blog/icann61-still-slated-for-puerto-rico#> <https://www.icann.org/news/blog/icann61-still-slated-for-puerto-rico#> <https://www.icann.org/news/blog/icann61-still-slated-for-puerto-rico#> Author: Nick Tomasso, Vice President, Global Meeting Operations & Mana It took less than 24 hours—one day—for Hurricane Maria to devastate Puerto Rico and many of its neighbors, but it will take years for them to recover. It is an understatement to say that for everyone affected, the journey back to their once normal lives will be long, painful, and economically challenging. ICANN joins the rest of the world in extending heartfelt hopes that Puerto Rico will experience a speedy recovery. We want to back up that sentiment by publicly expressing our strong desire to keep ICANN61 in the Puerto Rican capital of San Juan. The public meeting is scheduled for 10-15 March 2018. Our sincere hope is that by that time, recovery on the island will have advanced to the point where our meeting can proceed as scheduled. It is one way that we can all show meaningful economic support for this storm-battered U.S. territory. We are working with our hosts to closely monitor the recovery efforts on Puerto Rico, and will keep the ICANNcommunity apprised as the date of our meeting draws nearer. If it is determined that the recovery efforts don’t advance to the point where San Juan can reasonably support a conference that will likely draw several thousand, we will then look for an alternative location. At this point however, that is neither our desire nor our intention. Sent from my iPhone David A. Olive Senior Vice President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) _______________________________________________ So-ac-sg-cleaders mailing list So-ac-sg-cleaders(a)icann.org https://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders

1 0

Fwd: [council] GNSO Council Resolution 20 September 2017
by Wolf-Ulrich.Knoben Sept. 21, 2017

Sept. 21, 2017

FYI! -------- Weitergeleitete Nachricht -------- Betreff: [council] GNSO Council Resolution 20 September 2017 Datum: Thu, 21 Sep 2017 02:02:27 +0000 Von: Terri Agnew <terri.agnew(a)icann.org> An: council(a)gnso.icann.org <council(a)gnso.icann.org> Kopie (CC): gnso-secs(a)icann.org <gnso-secs(a)icann.org> Dear all, The following resolution was adopted by the GNSO Council at its meeting on Wednesday, 20 September 2017. These resolutions are also published on page: https://gnso.icann.org/en/council/resolutions <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> 20170920-1** *GNSO Council Approval of Data Collection Request from RPM Review PDP Working Group * *Submitted by Heather Forrest* *Seconded by James Bladel, Wolf-Ulrich Knoben* WHEREAS: 1. In October 2015, the GNSO Council adopted all the consensus recommendations from the Data & Metrics for Policy Making (DMPM) Working Group and instructed ICANN staff to commence implementation of the recommendations (https://gnso.icann.org/en/council/resolutions#20151021-1) 2. The Metrics Request Decision Tree and Working Group Metrics Request Form developed by the DMPM Working Group were consequently incorporated into the GNSO’s Working Group Guidelines (https://gnso.icann.org/en/council/annex-1-gnso-wg-guidelines-01sep16-en.pdf) 3. The Working Group chartered by the GNSO Council to conduct the Policy Development Process (PDP) to review all Rights Protection Mechanisms (RPMs) in All gTLDs has, after extensive deliberations, developed a list of data collection tasks that it believes are critical in order for it to fulfill its Charter (https://gnso.icann.org/en/drafts/rpm-charter-15mar16-en.pdf) 4. As part of its chartered tasks, the PDP Working Group was urged to bear in mind that a fundamental underlying objective of its work is to “create a framework for consistent and uniform reviews of these [RPMs] in the future”; 5. The Competition, Consumer Protection and Consumer Trust (CCT) Review Team convened under the ICANN Bylaws has noted the lack of, and need for, data in order to evaluate the effectiveness of the various RPMs that were created for ICANN’s 2012 New gTLD Program round (https://www.icann.org/en/system/files/files/cct-rt-draft-report-07mar17-en.…) and 6. The PDP Working Group has developed and submitted a DMPM data request form, as required by the GNSO’s Working Group Guidelines, to the GNSO Council for its approval on 16 September 2017 (https://gnso.icann.org/en/drafts/rpm-sunrise-trademark-claims-07sep17-en.pdf) RESOLVED: 1. The GNSO Council approves the DMPM request as submitted by the Review of All RPMs in All gTLDs PDP Working Group. 2. The GNSO Council instructs the leadership of the RPM PDP to work with ICANN staff and any outside experts to structure the data request in such a way that the value and relevance of the data is maximised. 3. The GNSO Council directs ICANN policy staff to forward the DMPM request to the appropriate department of ICANN Organization for the requisite budget and resource approvals, with a further request that the matter be considered and approved in as timely a fashion as practicable. 4. The GNSO Council requests a follow up report from the Review of All RPMs in All gTLDs PDP Working Group on the progress and outcomes of its DMPM request in time for the GNSO Council’s meeting scheduled for 21 December 2017, and a regular written report thereafter, at intervals of not less frequently than monthly, followed by a detailed status report on the Working Group’s view of the utility of the data collection exercise on the progress and timeline of Phase One of the PDP by ICANN61. Vote results <https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-20sep17-en.…>– friendly amendment Vote results <https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-20sep17-en.…>– original request 20170920-2 *GNSO Adoption of the Final Report of the Cross-Community Working Group Framework for the Use of Country and Territory names as TLDs* *Submitted by: Heather Forrest* *Seconded by: James Bladel* Whereas, 1. The GNSO and ccNSO chartered the Cross-community Working Group Framework for the Use of Country and Territory names as TLDs (CWG UCTN) in March, 2014 (https://ccnso.icann.org/workinggroups/unct-framework-charter-27mar14-en.pdf) The formation of a cross-community working group to evaluate the feasibility of developing an overarching framework on the use of country and territory names as TLDs was the principal recommendation of a preceding ccNSO Study Group (Final Report of 8 September 2013: https://ccnso.icann.org/workinggroups/unct-final-08sep12-en.pdf) 2. The CWG UCTN published an Interim Paper dated 9 February 2017 (https://ccnso.icann.org/workinggroups/ccwg-ctn-interim-paper-09feb17-en.pdf) setting out the history and context of ICANN policy-making on country and territory names, and proposing four recommendations, with Recommendation 3 articulated in three alternatives. A public comment period on the Interim Paper was held from 24 February 2017 to 21 April 2017, with comments summarised in a report dated 3 May 2017 (https://www.icann.org/en/system/files/files/report-comments-cwg-uctn-interi…) 3. In addition to comments submitted by individual GNSO stakeholders, the GNSO Registry Stakeholder Group, Business Constituency and Intellectual Property Constituency submitted comments supporting Recommendations 1, 2 and 4, as follows: 1. Close this CWG in accordance with and as foreseen in the charter. 2. Recommend that the ICANN community consolidate all policy efforts relating to geographic names (as that term has traditionally very broadly been defined in the ICANN environment to this point) to enable in-depth analyses and discussions on all aspects related to all geographic-related names. This is the only way, in our view, to determine whether a harmonized framework is truly achievable. 4. Recommend that future policy development work must facilitate an all-inclusive dialogue to ensure that all members of the community have the opportunity to participate. Again, we believe that this is the only way to determine whether a harmonized framework is truly achievable. 4.Notably, no objections were raised in any submission during the public comment period to the above Recommendations 1, 2 and 4. 5. A range of support was expressed for each of the alternative wordings of Recommendation 3, with all GNSO commenters expressing support for Alternative A, as follows: Alternative A Future work should take place with the authority of a policy development process under ICANN’s Bylaws, with a clearly drafted Charter or scope of work that sets out how conclusions and recommendations will inform that policy development process. This addresses a key deficiency of this CWG, as it has not been made clear how the group’s work can or will be incorporated in policy-making pursuant to ICANN’s Bylaws. 6. On 24 June 2015, the GNSO adopted the Resolution on the Request for a Preliminary Issue Report on New gTLDs Subsequent Rounds. (https://gnso.icann.org/en/council/resolutions#201506) The Preliminary Issue Report, which identified the “requirements around geographic names” as meriting discussion, was adopted by the GNSO Council on 17 December 2015 (https://gnso.icann.org/en/council/resolutions#201512) The Preliminary Issue Report notably recommended that: “A potential PDP-WG on New gTLD Subsequent Procedures could consider collaborating with other parts of the ICANN community, such as the GAC or ccNSO in particular, in determining if strings described above should be allowed and if so, what requirements would be needed to govern that process. The PDP-WG should also consider the work of the Cross-Community Working Group on Use of Country/Territory Names as TLDs before reaching any conclusions.” (Preliminary Issue Report at page 59, https://gnso.icann.org/en/issues/new-gtlds/subsequent-procedures-prelim-iss…) 7. The GNSO Policy Development Process on New gTLD Subsequent Procedures (“Subsequent Procedures PDP”) was chartered on 21 January 2016 to, inter alia: “Review whether geographic names requirements are appropriate.” (https://gnso.icann.org/en/issues/new-gtlds/subsequent-procedures-charter-21…) This issue formed part of Work Track 2, covering legal issues. 8. Following two cross-community sessions led by the leadership of the Subsequent Procedures PDP WG at ICANN59 in Johannesburg on the topic of the use of geographic names, the formation of a new Work Track 5 was proposed to better facilitate broad community participation in the discussion of policy on geographic name use. Resolved, 1. The GNSO Council adopts Recommendations 1, 2 and 4 of the Final Report of the Cross-Community Working Group Framework for the Use of Country and Territory names as TLDs. 2. The GNSO Council adopts the underlying objective of Recommendation 3, and in particular supports Recommendation 3 Alternative A, recognizing that the use of geographic names as gTLDs is clearly within the GNSO’s mandate as per ICANN’s Bylaws, and also recognizing that this is a matter of interest for the ICANN community as a whole. 3. The GNSO Council instructs the leadership of the Subsequent Procedures PDP to consider the Final Report of the Cross-Community Working Group Framework for the Use of Country and Territory names as TLDs, and to ensure continued collaboration with other parts of the ICANN community in addressing issues relating to the use of geographic names. 4. The GNSO Council recognizes the significant contribution of the CWG UCTN to the ongoing development of policy on the use of geographic names in the DNS, and thanks the members of the CWG UCTN for their Final Report, which clearly documents the history and context of policy-making in relation to geographic names. 5. The GNSO Council instructs the GNSO Secretariat to communicate these resolutions to the ccNSO Council, as co-chartering organization of the CWG UCTN, as soon as possible. Vote results <https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-20sep17-en.…> 20170920-3 *Nomination of GNSO Candidates for the Third Review of ICANN Accountability and Transparency (ATRT3)* *Submitted by: Susan Kawaguchi* *Seconded: James Bladel* Whereas, 1. On 31 January 2017, ICANN launched a call for volunteers seeking individuals interested in serving as a volunteer Review Team member on the ATRT3 (see https://www.icann.org/news/announcement-2017-01-31-en) 2. Under the new Bylaws, each SO/AC participating in the Specific Review may nominate up to 7 members to the Review Team, for consideration by the SO/AC leadership, for a review team of no more than 21 members, plus an ICANN Board member (designated by the ICANN Board). Any SO/AC nominating up to 3 individuals are entitled to have those nominees selected as members to the review team, so long as the nominees meet the applicable criteria for service on the team. 3. The GNSO Council tasked the GNSO Standing Selection Committee (SSC) to carry out the review and selection of GNSO endorsed candidates for the ATRT3 for Council consideration. 4. The SSC reviewed the candidates that requested GNSO endorsement (see https://community.icann.org/display/GSSC/ATRT3) taking into account the criteria outlined in the call for volunteers as well as the desire to ensure a RT that is balanced for diversity and expertise. The SSC submitted its full consensus recommendations to the GNSO Council on 13 September 2017 (http://mm.icann.org/pipermail/council/2017-September/020381.html) which confirmed the ranking of the 1-7 candidates as well as the expectation that, at a minimum, the 1-3 candidates would be considered primary candidates with a guaranteed seat for the ATRT3. 5. The GNSO Council considered the recommendations of the SSC. Resolved, 1. The GNSO Council nominates, ranked in order: Brian Cute (RySG), Wolfgang Kleinwächter (NCSG), Stéphane Van Gelder (RySG) as its primary three candidates for the ATRT3. Furthermore, the GNSO nominates, in ranked order: Tatiana Tropina (NCSG), Michael Karanicolas (NCSG), Adetola Sogbesan (BC), Erica Varlese (RySG) to be considered for inclusion in the ATRT3 by the SO-AC Chairs should additional places be available that need to be filled. 2. The GNSO Council acknowledges concerns raised by the SSC about the general lack of diversity (gender, geographic) in the pool of candidates for Review Teams, and will encourage SG/Cs to widely publicize calls for volunteers and make efforts to promote sufficient diversity in the pool of applicants for future application processes. 3. The GNSO Council instructs the GNSO Secretariat to communicate resolved #1 to the staff supporting the ATRT3. 4. The GNSO Council instructs the GNSO Secretariat to inform the applicants that have received endorsement that the GNSO Council expects that, if selected for the ATRT3, the applicant will represent the views of the entire GNSO community in their work on the ATRT3, and provide regular feedback as a group on the discussions taking place in the ATRT3, as well as the positions being taken by GNSO Review Team members. 5. The GNSO Council requests staff supporting the ATRT3 and application process to send a response to those applicants who did not receive endorsement for this Review Team, thanking them for their interest. The response should also encourage them to follow the ATRT3 work, and participate in Public Comments and community discussions and to apply for future opportunities within the GNSO Community as they arise. Vote results <https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-20sep17-en.…> Thank you, Terri

1 0