NCSG - GAC Meeting

[farzaneh badii]

Dear Ganga,

As much as the issues you raised are of importance, they are not within
ICANN mission and not what ICANN does.

At ICANN we do domain name policy so our questions should be related to
that.

We can talk about Domain Name Abuse and the role of Public Safety Working
Group at GAC.

Anything else members would want to discuss? I need to send them the topics
this week.









Farzaneh

On Tue, Feb 6, 2018 at 3:26 PM, gangadhar panday <
000004f7f8ca2221-dmarc-request at listserv.syr.edu> wrote:

> I suggest INTERNET SHUTDOWNS and CHEAPER CONNECTIVITY as  topics for
> discussion.
> Best wishes - Ganga
>
> On Feb 6, 2018 11:06 AM, Ayden Férdeline <icann at FERDELINE.COM> wrote:
>
> Thank you for arranging this bilateral, Farzaneh. It is great that we are
> continuing the dialogue with the GAC and that they have found the time to
> meet with us again. An excellent signal that our profile is rising within
> the community. Thanks for all your work making this happen!
>
> Best wishes,
>
> Ayden
>
>
> -------- Original Message --------
> On 6 February 2018 6:38 PM, farzaneh badii <farzaneh.badii at GMAIL.COM>
> wrote:
>
> Dear all,
>
> We will have a meeting with GAC in Puerto Rico during ICANN 61 on Monday,
> March 12. They have given us a nice early morning meeting, 8.30 to 9 before
> the opening ceremony.
>
> Other than GDPR and Privacy, what other topics would you like to
> discuss? Consider that we have a limited time, we will compile your
> suggested topics and see what will be approved by NCSG PC. When we have
> decided the topics, then we will choose some NCSG members who are the
> subject matter experts to be present on the podium.
>
> In our last meeting, I opened with a couple of words about NCUC (it was an
> NCUC meeting). This time I will tell them what NCSG is breifly.
>
>
>
> Best
>
>
>
>
> Farzaneh
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20180211/4a1cf1ed/attachment.htm>