April 2017 - ispcp - lists.icann.org

Fwd: [council] Submission of GNSO Council Comment on Draft FY18 Operating Plan and Budget
by Wolf-Ulrich.Knoben April 27, 2017

April 27, 2017

Dear all, The GNSO Council Comment on Draft FY18 Operating Plan and Budget had been posted: https://www.icann.org/public-comments/fy18-budget-2017-03-08-en It can be viewed in the Public Comment Forum: http://mm.icann.org/pipermail/comments-fy18-budget-08mar17/2017-April/date.…

1 0

SubPro Community Comment 2 (CC2) Public Comment extended - note to community leadership
by Chantelle Doerksen April 25, 2017

April 25, 2017

Dear all, The leadership team of the New gTLD Subsequent Procedures PDP WG would like to inform you that the deadline for response to Community Comment 2 has been extended to 22 May 2017. This extended deadline applies to both the public comment period (https://www.icann.org/news/announcement-2017-04-24-en) as well as to ICANN community responses sent directly to the PDP WG. While the deadline is being extended, the PDP WG leadership would like to encourage you to submit your comments as early as possible so that the WG and sub teams can begin considering them. In addition, the PDP WG leadership would like to reiterate a point made in its original message to you on 20 March 2017: recognizing that this survey is extensive, respondents may want to only provide answers to select questions that relate to their own interests or concerns. If you have any questions or concerns, please let us know. Kind Regards, GNSO-SECS

1 0

Fwd: [council] FW: ATRT3: Extension of Deadline
by Wolf-Ulrich.Knoben April 20, 2017

April 20, 2017

FYI Wolf-Ulrich -------- Weitergeleitete Nachricht -------- Betreff: [council] FW: ATRT3: Extension of Deadline Datum: Tue, 18 Apr 2017 21:36:17 +0000 Von: James M. Bladel <jbladel(a)godaddy.com> An: GNSO Council List <council(a)gnso.icann.org> Councilors – Please see below. The call for volunteers to serve on the Third Accountability and Transparency Review Team (ATRT3) has been extended to 2 JUN. Please feel free to share with your SG/C. Thank you— J. *From: *Lars Hoffmann <lars.hoffmann(a)icann.org> *Date: *Monday, April 17, 2017 at 15:56 ** *Subject: *ATRT3: Extension of Deadline Dear SO/AC Chairs, I wanted to thank you for participating in the ATRT3 Panel in Copenhagen – or for sending a stand-in. We thought the discussion was very productive; you can find the recording/transcript here <https://schedule.icann.org/event/9npV/accountability-and-transparency-revie…>. The 21 April deadline for the ATRT3 Call for Volunteers <https://www.icann.org/news/announcement-2017-01-31-en> is approaching, and, so far, we have received only four responses <https://community.icann.org/display/atrt/Applications+Received>. Therefore, we wanted to give you the heads up that we are going to *extend the deadline until 2 June 2017*. We will send out an official announcement over the coming days. In addition, we will continue to promote the ATRT3 Call for Volunteers via blogs, newsletters, and in all MSSI updates to the SO/ACs and other groups. We would very much appreciate it if you could help promote the call – and our efforts to publicize it – among your peers. Finally, working under the assumption that, once the Call for Volunteers closes, the SO/ACs will need about 4-6 weeks to make their nominations/endorsements, we suggest to facilitate a conference call in mid-July for you, the Chairs, to make the final selection of the ATRT Review Team. Please, let us know if you have any feedback, questions, or comments. We are looking forward to hearing back from you. Many thanks and best wishes, Lars

1 0

CCWG Accountability Work Stream 2: please complete the Ombudsman Survey
by Chantelle Doerksen April 19, 2017

April 19, 2017

** sent on behalf of CCWG Accountability Work Stream 2** Dear all, As part of the CCWG Accountability Work Stream 2 assignments, the ICANN Office of the Ombudsman is currently being assessed by an independent assessor. It would be great if you could spare 5-10min maximum to take part in the survey that closes at the end of this week. Survey link: http://www.surveygizmo.com/s3/3462816/ICANN Kind regards, Nathalie Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

The Chairman’s Blog: Reconsideration Requests, the Board Governance Committee and the Empowered Community - ICANN
by Chantelle Doerksen April 19, 2017

April 19, 2017

https://www.icann.org/news/blog/the-chairman-s-blog-reconsideration-request…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…> The Chairman’s Blog: Reconsideration Requests, the Board Governance Committee and the Empowered Community [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…>[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…>[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…>[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…>[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…>[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…> In February this year, the Board passed a resolution[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> to move reconsideration requests out of the Board Governance Committee (BGC) and create a separate Board committee specifically devoted to oversight of ICANN’s accountability mechanisms, including the reconsideration responsibilities. The BGC’s reconsideration responsibilities are specified in ICANN’s fundamental bylaws, so this change requires affirmative approval by the Empowered Community. This recommendation is out for public comment[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> now, and will be closing 10 May 2017. I want to make sure that everyone knows about this from the beginning, because it’s the first time the Empowered Community power may be used. One of the BGC’s primary role is the administration of the Board’s internal structure. Each year, it polls Board members on their preferences for committee memberships and their interests in the positions of Board chair and vice-chair, and then offers potential slates to the Board for their consideration. The BGC is also responsible for helping the Board implement its Conflicts of Interest Policy, which has included the use of Conflicts and Ethics subcommittees to help Board members evaluate how potential or perceived conflicts of interest might impact decisions. In its role of enhancing Board effectiveness, the BGC has overseen the development of training opportunities for Board members. In addition to these, and other governance-related activities, the BGC has also handled appeals when someone challenges one of the Board’s or ICANN Org’s decisions. This appeals process is known as “reconsideration.” Over the past several years, the number of reconsideration requests has grown. Moreover, during the Enhancing ICANN Accountability work, the ICANN community proposed enhancements to the Reconsideration Process, including expanding the times when reconsideration can be sought and placing more direct responsibility on the BGC for substantive work in resolving requests within a shorter time frame. The Board fully supports improvements in the reconsideration process and has focused on how best to continue to implement the recommendations of the Cross Community Working Group (CCWG) on Accountability. In anticipation of increased future workloads, as well as a need to have a group that is focused on the appeals process, the Board recommends moving the reconsideration process into a committee responsible for the oversight of ICANN’s accountability mechanisms. You can read about the resolution and our rationale for putting it forward in a blog[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…> that BGC Committee Chair Chris Disspain and I posted in February. After the public comment period, the Board will review the proposed Fundamental Bylaws amendments, and, if approved, the Empowered Community will then have an opportunity to consider whether it supports the amendments. It will be up to the Empowered Community to choose how to approach this task. One possibility includes hosting a Community Forum on the amendments to the Fundamental Bylaws during ICANN59<https://meetings.icann.org/en/johannesburg59> in Johannesburg, South Africa, in June 2017. Information on the Empowered Community can be found in Article 6[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> of ICANN’s bylaws, and information on the Fundamental Bylaws Approval Process can be found in Annex D[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>, Article 1.

1 0

WG: [council] FW: Participation in the ccNSO PDP WG on Retirement of ccTLDs
by wolf-ulrich.knoben＠t-online.de April 13, 2017

April 13, 2017

FYI! Best regards Wolf-Ulrich -----Original-Nachricht----- Von: James M. Bladel <jbladel(a)godaddy.com <mailto:jbladel@godaddy.com> > Betreff: [council] FW: Participation in the ccNSO PDP WG on Retirement of ccTLDs Datum: 13.04.2017, 16:29 Uhr An: GNSO Council List <council(a)gnso.icann.org <mailto:council@gnso.icann.org> > Councilors – See note below from Katrina Sataki, chair of the ccNSO, inviting members of the GNSO Community are invited to participate in an upcoming ccNSO PDP working group. Please distribute to your SGs/Cs. Thank you, J. From: Katrina Sataki <katrina(a)nic.lv> Date: Thursday, April 13, 2017 at 7:49 To: "James M. Bladel" <jbladel(a)godaddy.com> Cc: 'Ben Fuller' <ben(a)fuller.na>, 'Nathalie Peregrine' <nathalie.peregrine(a)icann.org>, 'Marika Konings' <marika.konings(a)icann.org> Subject: Participation in the ccNSO PDP WG on Retirement of ccTLDs Dear James, On behalf of the ccNSO Council I would like to invite individual members from the GNSO to participate in the ccNSO PDP Working Group on the Retirement of ccTLDs. Participants are entitled to participate on equal footing with members, unless the charter states otherwise. In addition, participants are not expected to represent the view or views of your group, they participate in their personal capacity. We expect that the WG will be hold its first meeting at the end of May 2017. The group will meet in person during ICANN 59 in Johannesburg. If someone from the GNSO is interested, please let me or the ccNSO Secretariat (ccnsosecretariat(a)icann.org) know. Kindest regards, ]{atrina Chair of the ccNSO --- Background --- At its meeting on 13 March 2017 the ccNSO Council initiated its 3rd ccNSO policy development process (ccPDP). This ccPDP is intended to develop and recommend policies for the: - Retirement of ccTLDs - Review mechanism with respect to decisions on delegation, transfer, revocation and retirement of ccTLDs. Under the ccPDP the focus will first be on the retirement of ccTLDs. Only after completion of the development work relating to retirement, work on the review mechanism will begin. As part of the decisions on the initiation, the ccNSO Council has also adopted the charter for the working group on retirement of the ccTLDs (https://ccnso.icann.org/workinggroups/charter-wg-retirement-cctlds-10apr17-…) The goal of the working group (WG) is to report on and recommend a policy for the retirement of the delegated Top Level Domains associated with the country codes assigned to countries and territories listed in the ISO 3166-1 within the framework of the ccNSO Policy Development Process. We are now in the process to seek volunteers for the WG, including participants and observers (see charter section 2.1.2). By applying all commit to participate actively and regularly in the work of the WG and express to have at least a basic understanding of the Reference Material*. By applying, members, participants and observers also commit to the charter of the WG, including but not limited to its Internal decision making and standards of behavior. * Reference Material - RFC 1591 (https://www.ietf.org/rfc/rfc1591.txt ) - The ccNSO Framework of Interpretation working group Final Report, (http://ccnso.icann.org/workinggroups/foi-final-07oct14-en.pdf ) - ISO 3166 standard (http://www.iso.org/iso/country_codes) - CWG-Stewardship Final Report, Annex O: ccTLD Appeals Mechanism Background and supporting Findings Sections 1414- 1428, (https://community.icann.org/download/attachments/53779816/FinalTransitionPr… ). Issue paper to explore retirement of ccTLDs (January 2017): https://community.icann.org/download/attachments/64068742/Issues%20to%20exp… _______________________________________________ council mailing list council(a)gnso.icann.org https://mm.icann.org/mailman/listinfo/council

1 0

ICANN Quarterly Stakeholder Call for FY17 Q3 takes place on 27 April 1500 UTC. Register now.
by Chantelle Doerksen April 13, 2017

April 13, 2017

[CANN][icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFaQ…> News Alert https://www.icann.org/news/announcement-2017-04-12-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> ________________________________ ICANN Quarterly Stakeholder Call for FY17 Q3 takes place on 27 April 1500 UTC. Register now. 12 April 2017 ICANN has announced its FY17 Q3 Stakeholder Call, which will take place on 27 April 1500 UTC. The call will focus on how ICANN has implemented community policy for the quarter ending 31 March 2017, as well as provide an update from our European engagement team. This European update is part of a new format to spotlight regional activities. Please click here[survey.clicktools.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__survey.clicktools.com_a…> to register for the call and receive instructions on how to join. If you are unable to access the form, please email us<mailto:icann.communications@icann.org> your full name and an email address to be registered. The call is open to anyone and live interpretation will be offered in Arabic, Chinese, English, French, Portuguese, Russian and Spanish. There will be a question & answer (Q&A) session and all materials (recordings, transcripts and presentations) will be made available on the ICANN website[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. ?These calls were organized to enhance ICANN's accountability and transparency efforts. They are also a great way for you to stay informed on what the organization has done in line with ICANN's mission of keeping the Internet secure, stable and interoperable. More information Please visit the Reporting page[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> on the ICANN website for more information, including recordings of previous calls. The presentation will be posted 24-48 hours in advance.

1 0

WG: [council] FW: [Soac-infoalert] ICANN Clarifies its Position in Response to Purported Threats Posed by Children-Related New gTLDs - ICANN
by wolf-ulrich.knoben＠t-online.de April 11, 2017

April 11, 2017

FYI Best regards Wolf-Ulrich Knoben -----Original-Nachricht----- Von: James M. Bladel <jbladel(a)godaddy.com <mailto:jbladel@godaddy.com> > Betreff: [council] FW: [Soac-infoalert] ICANN Clarifies its Position in Response to Purported Threats Posed by Children-Related New gTLDs - ICANN Datum: 11.04.2017, 00:47 Uhr An: GNSO Council List <council(a)gnso.icann.org <mailto:council@gnso.icann.org> > Councilors - Please see this announcement / statement from ICANN that was released Friday. Thank you, J. From: <soac-infoalert-bounces(a)icann.org> on behalf of David Olive <david.olive(a)icann.org> Date: Friday, April 7, 2017 at 15:02 Subject: [Soac-infoalert] ICANN Clarifies its Position in Response to Purported Threats Posed by Children-Related New gTLDs - ICANN https://www.icann.org/news/blog/icann-clarifies-its-position-in-response-to… <https://www.icann.org/news/blog/icann-clarifies-its-position-in-response-to…> ICANN Blog by Akram Atallah ICANN Clarifies its Position in Response to Purported Threats Posed by Children-Related New gTLDs Recently, the Children’s Charities Coalition on Internet Safety raised concerns that new generic Top Level Domains (gTLDs) may become new grounds for the functioning and distributing of child abuse content. ICANN wants to confirm its position. Child abuse and child pornography is a crime. It is illegal and as such there are many appropriate, already available, forms of law enforcement mechanisms to address issues like these. All ICANN’s contracted parties are required to abide by the laws of countries they operate in and laws that address these areas. This is not an issue ICANN takes lightly. The organization’s authority, with respect to registries and registrars, is derived solely by contract, and ICANN acts as an administrator of those contractual arrangements. There are safeguards in the new gTLD Registry Agreements (RA) related to highly-regulated or sensitive strings which were incorporated, as identified by the Governmental Advisory Committee <https://gacweb.icann.org/display/gacweb/Governmental+Advisory+Committee> (GAC). As an organization, ICANN is governed by a bottom up, consensus-driven multistakeholder model. The ICANN organization cannot unilaterally impose guidelines or requirements on registries, registrars or other stakeholders in a top-down manner. Policy recommendations, as per ICANN’s bylaws (see section 6.1) <https://www.icann.org/resources/pages/governance/bylaws-en#VI> are developed and refined by the ICANN community through its Supporting Organizations and influenced by Advisory Committees – all comprised of volunteers from across the world – in a "bottom-up," multistakeholder, open and transparent process. Each Supporting Organization has its own specific policy development process. For anything unlawful, we rely on courts and governmental regulatory authorities to police illegal activity. As an organization, ICANN does not require registries to regulate web content, but some registries have voluntarily promised the community that they would do so and have asked ICANN to make these commitments enforceable via the registry agreement. ICANN is cognizant of the seriousness of this issue and others, which is why we have been working closely with the public safety community, including law enforcement, to ensure that they understand and make correct use of policies and processes. ICANN and the Governmental Advisory Committee <https://gacweb.icann.org/display/gacweb/Governmental+Advisory+Committee> ’s (GAC) Public Safety Working Group <https://gacweb.icann.org/display/gacweb/GAC+Public+Safety+Working+Group> have been working together to create awareness on how to participate in ICANN and engage effectively in the GAC and ICANN’s policy making processes. One of the main areas of work has been capacity building within law enforcement agencies and the review of the Domain Name System (DNS) and its impact on public safety. Additionaly, ICANN takes steps to remind all new gTLD registry operators of the Governmental Advisory Committee’s view expressed in Buenos Aires Communiqué on the importance of protecting children and their rights, consistent with the UN Convention on the Rights of the Child. (For more on this important topic, see entry #13 in Annex 1 to ICANN NGPC Resolution No. 2014.02.05.NG01 at http://www.icann.org/en/groups/board/documents/resolutions-new-gtld-annex-1… <http://www.icann.org/en/groups/board/documents/resolutions-new-gtld-annex-1…> . ICANN’s mission is to ensure the stable and secure operation of the Internet's unique identifier systems. As a global organization, we aim to realize our mission through our multistakeholder model, which depends on open, inclusive, transparent and accountable engagement, participation and policy development contributions from all stakeholders, ranging from businesses to governments to individual Internet users. David A. Olive Senior Vice President Policy Development Support Managing Director, ICANN Regional Headquarters –Istanbul Internet Corporation for Assigned Names and Numbers (ICANN) _______________________________________________ council mailing list council(a)gnso.icann.org https://mm.icann.org/mailman/listinfo/council

1 0

RDS Review Team GNSO Candidates
by Novoa, Osvaldo April 6, 2017

April 6, 2017

Dear all, The SSC is tasked to provide its recommendations on GNSO nominations for the RDS Review Team to the GNSO Council. The GNSO Council can nominate up to 7 people to the review team. However, if it would only nominate 3, these would have a guaranteed place on the review team. Per the Bylaws, a Review Team consists of maximum 21 members (3 members per SO/AC), so this means that if an SO/AC does not nominate up to 3 candidates, additional slots may be available that can be filled by the SO/AC Chairs who make the final selection based on the nominations that have been received by the SO/ACs. So the task of the SSC is to review the candidates that have indicated that they want to be considered for GNSO nomination which are 14 candidates in total. Per the SSC Charter, you are expected to, following your review of the candidates, to rank the candidates according to the criteria listed in the call for applications. Following the review and ranking, you will need to decide whether you recommend the GNSO Council that it endorses the top 7 ranked candidates, or less, noting that the top three ranked candidates if endorsed by the GNSO Council would be automatically selected for the review team. We have yet to received the confirmation from the GNSO, SG or Constituency if these candidates are supported by the GNSO or its members, so the final selection is conditioned to this. These are the 14 candidates and their ranking after the first round of voting. We have consensus on the first three, so it seems that this is what we will propose to the GNSO Council, unless our constituencies have other opinion. So I am asking if anyone in the ISPCP has any objection to me accompanying this proposal or should I vote to change anything, tomorrow we are having another call to discuss the candidates. For now we have until next Monday, April 10, to submit our proposal. Name of Candidate Rank Affiliation Geograpic Region Gender Susan Kawaguchi 1 BC NA F Erika Mann 1 Nom-Com Appointee to the GNSO EUR F Stephanie Perrin 3 NCUC EUR F Volker Greimann 4 RrSG EUR M Marc Anderson 5 RySG NA M Stefania Milan 6 NCUC EUR F Timothy Chen 7 BC NA M Juan Manuel Rojas 8 NPOC LAC M Ayden Ferdeline 8 NCUC EUR M Brian Scarpelli 10 IPC NA M Remmy Nweke 11 NPOC AF M Pitinan Kooamornpatana 12 ? AP M Vignesh Pamu 13 ? AP M Subham Charan 14 ? AP M 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.

2 3

Fwd: [Gnso-ssc] Your input needed - proposed SSC agreements
by Novoa, Osvaldo April 5, 2017

April 5, 2017

Dear All, Regarding my previous mail, this is what we are ask to support or object. If I don’t receive any comment I will support both agreements. Best regards, Osvaldo Inicio del mensaje reenviado: De: Marika Konings <marika.konings(a)icann.org<mailto:marika.konings@icann.org>> Asunto: [Gnso-ssc] Your input needed - proposed SSC agreements Fecha: 5 de abril de 2017, 11:18:27 GMT-4 Para: "gnso-ssc(a)icann.org<mailto:gnso-ssc@icann.org>" <gnso-ssc(a)icann.org<mailto:gnso-ssc@icann.org>> Dear All, Following the SSC call today I would hereby like to share the tentative agreements that those on the call reached based on the review of the survey results (see also the notes and survey results which were circulated earlier today): 1. Proposed agreement #1: Recommend the following three candidates (in no particular order) for GNSO endorsement for the RDS Review Team with a guaranteed seat: 1) Susan Kawaguchi, 2) Erika Mann and 3) Stephanie Perrin 2. Proposed agreement #2: Recommend the following four candidates, in the following order, for GNSO endorsement for the RDS Review Team for any additional slots that may be available for consideration by the SO/AC Chairs: 4) Volker Greimann, 5) Marc Anderson, 6) Stefania Milan, 7) Timothy Chen You are now all requested, and especially those that were not able to attend, to indicate your support or lack thereof for these proposed agreements. As a reminder, the top three ranked candidates will automatically get a seat on the RDS Review Team while the candidates ranked 4-7 may be considered by the SO/AC Chairs for addition to the review team should seats remain available and there is a need to add additional members to ensure diversity. Please respond to this message as soon as possible. Your feedback will determine whether or not a call is needed tomorrow. To facilitate a determination on whether a call is needed, please fill out the following doodle poll: https://icannorg.doodle.com/poll/crcyit68qkbvgmwp. We will keep the slot that is currently scheduled for Monday 10 April at 13.00 UTC to allow for further discussion, if needed, regardless of whether the call tomorrow goes ahead or not. In parallel, staff will start work on a draft motion that would capture the SSC recommendations to the GNSO Council which can be submitted once the SSC reaches agreement on its recommendations. Thank you, Marika Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>. _______________________________________________ Gnso-ssc mailing list Gnso-ssc(a)icann.org<mailto:Gnso-ssc@icann.org> https://mm.icann.org/mailman/listinfo/gnso-ssc ________________________________ 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