Hi Juan,
For Sally:
As Comms Chair:
- What are the resources/support that ICANN could provide extra to NPOC in terms of exposure? Can we work with ICANN's comms team?
- How does she think NPOC can have better impact in ICANN processes? What is her current take on our participation?
As TIOF:
- Any updates on the platform/channel to have access to ICANN data?
Thanks.

Dear Members,
Just a heads up that I've got my 1:1 meeting with Sally Costerton on May
7th. If there's anything specific you want me to bring up or ask her
about during our chat, just let me know!
JUAN MANUEL ROJAS P.
Director - MINKA DIGITAL Colombia
NPOC Chair - NCSG/GNSO
MSc. Information Technology
Registered Linux User No.533108.
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GIT d- s: a+ C+++ UL P+ L+++ !E !W+++ !N !o K+++ w-- !O M- V PS+ PE-- Y+
PGP+ t+ 5 X++ R tv+ b+ DI D G e+++(+++)>+++ h+ r++ y+
------END GEEK CODE BLOCK------
_______________________________________________
Npoc-discuss mailing list
Npoc-discuss@icann.org
https://mm.icann.org/mailman/listinfo/npoc-discuss
_______________________________________________
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.
DISCLAIMER
The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message.