Input request: Upcoming Meeting with ICANN CEO and w/ the ICANN Board at ICANN70

[Stephanie E Perrin]

Indeed, and the least they can do is make a publically archived list so 
we can see their deliberations.  I would add that financial transparency 
for these initiatives would be a fine thing, what did the last technical 
group led by Mohan, to basically test RDAP, cost us?

Stephanie Perrin

On 2021-02-07 10:30 a.m., farzaneh badii wrote:
> *EXTERNAL EMAIL:*
> Thank you Bruna.
>
> We can also discuss DNS abuse and ask the CEO about this initiative: 
> https://www.icann.org/news/blog/introducing-the-dns-security-facilitation-initiative-technical-study-group 
> <https://www.icann.org/news/blog/introducing-the-dns-security-facilitation-initiative-technical-study-group>
>
> This initiative was formed similar to the “strawberry tech group” in a 
> top-down manner and at the request of the CEO (I believe that is the 
> case).
> The group’s responsibilities are very expansive
>
> And predictably, there is no digital rights scholar or advocate on 
> this team (not asking for NCSG rep but someone with at least some kind 
> of expertise in this area) 
> https://community.icann.org/download/attachments/136120045/DSFI%20TSG%20Bios%20%287%29.pdf?version=1&modificationDate=1593546327000&api=v2 
> <https://community.icann.org/download/attachments/136120045/DSFI%20TSG%20Bios%20%287%29.pdf?version=1&modificationDate=1593546327000&api=v2>
>
> The CEO might tell you that this is a solely technical group. We have 
> heard this argument before. Unfortunately, a lot of these technical 
> decisions are entangled with policy matters as we saw at SSR2. Another 
> assertion is that this work is much broader than DNS abuse and doesn’t 
> have much to do with it.
> Well, broader means inclusive of DNS abuse.
>
> Note that the group’s meetings are not recorded. The group makes 
> recommendations to the CEO for consideration. We will have the chance 
> to “review” the recommendations which is a vague term. Review as in 
> have a look at it or actually comment on it.
>
> One argument in support of this group is that the Board set the 
> security matters as a priority for the CEO and he is acting upon that. 
> That is fine but at least it would be good to have some observers from 
> civil society to monitor the process.
>
>
>
> On Sunday, February 7, 2021, Raphael Beauregard-Lacroix 
> <rbeauregardlacroix at gmail.com <mailto:rbeauregardlacroix at gmail.com>> 
> wrote:
>
>     +1 for Farzaneh's suggestions :)
>
>     On Fri, Feb 5, 2021 at 9:20 PM Bruna Martins dos Santos
>     <bruna.mrtns at gmail.com <mailto:bruna.mrtns at gmail.com>> wrote:
>
>         Dear NCSG,
>
>         Hope this email finds you well!
>
>         We have two important interactions with ICANN executives
>         coming up - NCSG 1:1 Meeting with the CEO and out meeting with
>         the Board at ICANN70 - for the two, I need to provide icann
>         staff with talking points.
>
>         The date of our meeting with the board at ICANN70 is not yet
>         defined but my meeting with Goran is taking place on Monday,
>         22 February.
>
>         Are there any ideas of discussion points or questions you
>         would like us to propose to any of these meetings ?
>
>         I recall @farzaneh badii
>         <mailto:farzaneh.badii at gmail.com> suggested something about
>         the SSAD and EDPB interactions and we also have an ongoing
>         interest in learning a little more about the ICANN Org
>         interaction with the EU Commission for data protection
>         purposes. Besides that, maybe DNS Abuse is something else that
>         can come up in these conversations, anything else ?
>
>         Looking forward to hearing from you!
>
>         best,
>         -- 
>         */Bruna Martins dos Santos /*
>
>         Skype ID: bruna.martinsantos
>         @boomartins
>
>
>
> -- 
> Farzaneh
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20210207/884f9c7d/attachment.htm>