Hi Alejandra and all!

I'm ok with the informal working session on the 19th of August.

Best regards,




De: Ccnso-council <ccnso-council-bounces@icann.org> en nombre de Alejandra Reynoso via Ccnso-council <ccnso-council@icann.org>
Enviado: viernes, 30 de julio de 2021 4:02 p. m.
Para: Joke Braeken <joke.braeken@icann.org>
Cc: ccnso-council <ccnso-council@icann.org>
Asunto: Re: [ccnso-council] Report ccNSO Council Mini-Workshop on DNS Abuse
 
Dear Councillors

We had a very productive mini-workshop during our last meeting. As a result, we have a suggested list of items to implement while they are still fresh in our minds ;)

Would you like to discuss the next steps in an informal working session on the 19th of August at 18:00 UTC? Please let me know by Tuesday 3 of August.

Hope you have a wonderful weekend :)

Best regards,
Alejandra

--

Photograph
Alejandra Reynoso
Investigación & Desarrollo Dominios .gt
P: +502 23688565
E: alejandra.reynoso@cctld.gt
18 Ave. 11-95 Zona 15, V.H. III. (A-109)
Guatemala, Guatemala
www.gt



On Wed, Jul 28, 2021 at 8:37 AM Joke Braeken via Ccnso-council <ccnso-council@icann.org> wrote:

Dear All,

 

At the request of Alejandra, please find enclosed a report on the ccNSO Council Mini-Workshop on DNS Abuse, held at the occasion of ccNSO Council Meeting 175 | 22 July 2021 (noon UTC).

 

You may recall that Item 12 on the agenda of Council meeting # 175 focused on the following question: “Is there a role for the ccNSO in facilitating the discussion across the ccTLD community with respect to DNS Abuse?”

 

This document summarizes the discussion and includes a staff recommendation with a suggested way forward for Council to discuss and consider. 

 

Best regards.

 

Joke Braeken

ccNSO Policy Advisor

joke.braeken@icann.org

 

_______________________________________________
Ccnso-council mailing list
Ccnso-council@icann.org
https://mm.icann.org/mailman/listinfo/ccnso-council
_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
***************Este mensaje (y sus adjuntos), en adelante "mensaje", ha sido enviado exclusivamente a su(s) destinatario(s) y es confidencial. Si usted recibe este mensaje por error, por favor bórrelo y comunique inmediatamente al remitente. Toda utilización o publicación, total o parcial, queda prohibida salvo autorización expresa. La UTP no podrá ser considerada responsable si el mensaje ha sido modificado y/o utilizado sin autorización. This message (and any attachments), are confidential intended solely for the people whose addresses appear. If you have received this message by error, please delete it and immediately notify the sender. Any use, dissemination or disclosure, either whole or partial, without formal approval is prohibited. The UTP will not therefore be liable for the message if modified and/or used without approval.**************
***************Este mensaje (y sus adjuntos), en adelante "mensaje", ha sido enviado exclusivamente a su(s) destinatario(s) y es confidencial. Si usted recibe este mensaje por error, por favor bórrelo y comunique inmediatamente al remitente. Toda utilización o publicación, total o parcial, queda prohibida salvo autorización expresa. La UTP no podrá ser considerada responsable si el mensaje ha sido modificado y/o utilizado sin autorización. This message (and any attachments), are confidential intended solely for the people whose addresses appear. If you have received this message by error, please delete it and immediately notify the sender. Any use, dissemination or disclosure, either whole or partial, without formal approval is prohibited. The UTP will not therefore be liable for the message if modified and/or used without approval.**************