[ALAC] [CPWG] PIR and Dot Org

[Jonathan Zuck]

Thanks Maureen. Jacob has quickly fallen into the clutches of Godwin's Law. Reductio ad Nazium. The At-Large mandate is specifically NOT to represent organizations but instead individual end users. There is, in fact, an entity within the ICANN community which DOES represent the interests of not for profit organizations, NPOC. I had a long and involved conversation with Jacob, at Evan's behest and was coming around to some of his points and and we concluded he would make other introductions. Comparing us sticking to our remit to being antisemitic is beyond the pale!

We need to find our own way on this, with a focus on individual end users, and perhaps some concerns over organizational practices, but we owe SAVEDOTORG absolutely nothing and, after that op-ed, we should tell them to go to Hell. Just my two cents.



Jonathan Zuck
Executive Director
Innovators Network Foundation
www.Innovatorsnetwork.org<http://www.Innovatorsnetwork.org>

________________________________
From: ALAC <alac-bounces at atlarge-lists.icann.org> on behalf of Olivier MJ Crepin-Leblond <ocl at gih.com>
Sent: Sunday, January 5, 2020, 8:53 PM
To: Maureen Hilyard
Cc: ALAC; ALAC Members; CPWG; ALT-Plus
Subject: Re: [ALAC] [CPWG] PIR and Dot Org

Dear Maureen,

Just a thought, historically, when the DotMobi TLD was created, a formal DotMobi liaison with At-Large was mandated. Others will have details.
Best wishes,

Olivier

Sent from my iPad

On 6 Jan 2020, at 01:40, Maureen Hilyard <maureen.hilyard at gmail.com<mailto:maureen.hilyard at gmail.com>> wrote:

 http://www.circleid.com/posts/20200105_hilyard_has_a_historic_chance_to_activate_icann_at_large/

Well that is certainly forcing our hand to take some action. But with arrows flying in all sorts of directions it has been difficult to know which one to follow, and I note there has been a break in the conversations on this topic.

Interesting and very timely that Roberto raised the .org issue again in an earlier email today. I started a response until JZ reminded us that the thread was about .com

I agree with Roberto's approach  - that we should focus on our role as the voice of At-Large end-users and offer some creative advice on how we might influence the behaviour of PIR and any future decisions they make that will impact on .org end-users. PIR/Ethos already presented a webinar and said all the right things.. but how can we be assured that they will stick to what they said that they would do in the future? Who will monitor this on behalf of ordinary end-users? Who will be represented on the Stewardship Council?

At the same time we may also need to advise the ICANN Board about how they might deal with the ICANN-PIR/Ethos contract - especially Roberto's recommendation of some commitment from ICANN that ethical behaviour towards .org end-users will be built into it.

We are aware that the Board is looking into every legal issue relating to how they can deal with matters that are being raised by letters that are flowing their way. We don't need to add more of the same.

While i think it might be seen to be a simplistic approach, I believe that we should stick to what our job is and focus on advice to the Board and to PIR- but lets try to be creative about how we advise them, looking at the impacts on end-users from all perspectives.

My 2c
M


  *

_______________________________________________
CPWG mailing list
CPWG at icann.org<mailto:CPWG at icann.org>
https://mm.icann.org/mailman/listinfo/cpwg

_______________________________________________
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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://atlarge-lists.icann.org/pipermail/alac/attachments/20200106/639da13d/attachment.html>