Today, I had a brief chat with Brian Cute – he explained how the process is going: he is summarising the comments (thanked the ccNSO), then there will be another webinar and then another session in Marrakech. The general idea is to arrive to Montreal with a clearer path forward. He also mentioned that if anyone sees a better path, he is very willing to hear it. So, if there are suggestions how to make the process faster and simpler, this is the right moment to mention it ☺

He also said that the deadline has been moved. I said that this is one thing I find really demotivating about ICANN. Before ICANN, I thought that deadline is a deadline and anyone who couldn’t meet it, has missed it and should blame no one but him/herself. It turned out that I was wrong - a deadline, at least at ICANN, is more like a moving target. I also said that those who put extra efforts to meet the deadline feel really stupid when it is moved because somebody has asked for it or because “the comments period unfortunately overlapped with a holiday season and people did not have time to prepare their comments” (“it was Xmas holiday season” as an excuse to extend the process amuses me the most) and “we NEED more feedback – everybody should have a change to submit their comments”. Luckily, every time the comments period is extended, there is no need to worry because “the schedule has been developed taking into account that there MIGHT be a need for extension”. Why it is not possible to allocate more time for comments but stick to deadlines, still is a mystery to me. I think that at the end, people just stop trying to meet any deadline because they know that deadlines are going to be moved anyway – so, why bother? And then we end up discussing how to make our multi-stakeholder model more efficient…

Ah, yes, I submitted ccNSO Council’s comments yesterday… yesterday was the deadline, btw.

Regards,

]{atrina

P.S. If there is anything anyone would like to add to our comments, please do! We’re lucky - the deadline was unexpectedly moved to 13 June!

From: Ccnso-council <ccnso-council-bounces@icann.org> on behalf of Nick Wenban-Smith <Nick.Wenban-Smith@nominet.uk>
Date: Wednesday, 5 June 2019 at 21:22
To: Joke Braeken <joke.braeken@icann.org>, Bart Boswinkel <bart.boswinkel@icann.org>, "ccnso-council@icann.org" <ccnso-council@icann.org>
Subject: Re: [ccnso-council] for your final review : draft council statement regarding evolving ICANN’s Multistakeholder Model

I heard that the closing dates for comments was extended to 13 June – in case we do want to add further comments.

The statement is fine from my perspective as far as it goes, and it’s hard anyway to disagree with the general thrust of the issues list.

I am finding this whole process quite time-consuming and complex in itself! The irony … 😊

From: Ccnso-council <ccnso-council-bounces@icann.org> On Behalf Of Joke Braeken
Sent: 03 June 2019 14:46
To: Bart Boswinkel <bart.boswinkel@icann.org>; ccnso-council@icann.org
Subject: [ccnso-council] for your final review : draft council statement regarding evolving ICANN’s Multistakeholder Model

Dear all,

I am following up on the email below.

Please find here the proposed draft council statement (clean version) regarding evolving ICANN’s Multistakeholder Model: https://docs.google.com/document/d/1nbKFm1f_eK23tz7E_ym7C-t_2n0XrQWDEx049Fb-poc/edit?usp=sharing

A word copy can be found in attachment.

Kindly provide me with your input by the end of today, Monday, 3 June 2019, 23:59 UTC, in case you do not agree with the proposed council statement.

Close date for public comments is tomorrow, 4 Jun 2019 23:59 UTC. Read more:

https://www.icann.org/news/announcement-2019-04-25-en

Best regards,

Joke Braeken

ccNSO Policy Advisor

joke.braeken@icann.org

Follow @ccNSO on Twitter: https://twitter.com/ccNSO

Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/

http://ccnso.icann.org

From: Ccnso-council <ccnso-council-bounces@icann.org> on behalf of Joke Braeken <joke.braeken@icann.org>
Date: Thursday, 30 May 2019 at 11:10
To: Bart Boswinkel <bart.boswinkel@icann.org>, ccnso-council <ccnso-council@icann.org>
Subject: Re: [ccnso-council] invitation to draft a council statement : your action is required by Friday, 31 May 2019 (noon UTC)

Dear councillors,

This is reminder regarding the email below.

Your action is required by Friday, 31 May 2019 (noon UTC).

Best regards,

Joke Braeken

ccNSO Policy Advisor

joke.braeken@icann.org

Follow @ccNSO on Twitter: https://twitter.com/ccNSO [twitter.com]

Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ [facebook.com]

http://ccnso.icann.org [ccnso.icann.org]

From: Ccnso-council <ccnso-council-bounces@icann.org> on behalf of Bart Boswinkel <bart.boswinkel@icann.org>
Date: Friday, 24 May 2019 at 11:43
To: ccnso-council <ccnso-council@icann.org>
Subject: [ccnso-council] invitation to draft a council statement : your action is required by Friday, 31 May 2019 (noon UTC)

Dear Council members,

On behalf of Joke:

I am following up on Triage recommendation 25-2019 (Evolving ICANN’s Multistakeholder Model), which was recently approved by the ccNSO Council.

Your action is required by Friday, 31 May 2019 (noon UTC).

The recommendation specified that a Council statement is needed, as defined in https://ccnso.icann.org/sites/default/files/filefield_47783/guidelines-statements-30mar16-en.pdf [ccnso.icann.org] Close date for public comments is 4 Jun 2019 23:59 UTC

Short summary:

Building on the conversation at ICANN64, a public comment invites the community to further define issues that challenge the effectiveness of ICANN's multistakeholder model.

= = = = =

|||| Your action is required |||

Kindly review the instructions included below, and provide input to the google document with the draft council statement.https://docs.google.com/document/d/1nbKFm1f_eK23tz7E_ym7C-t_2n0XrQWDEx049Fb-poc/edit?usp=sharing [docs.google.com]

Deadline for this: Friday, 31 May 2019 (noon UTC), allowing for sufficient time to produce a final version of the Council statement.

= = = = =

Instructions

Commenters should refer to the draft "Issues List" that reflects input received from the ICANN community about how to improve the effectiveness of ICANN's multistakeholder model. We welcome all comments, and encourage you to focus on the following:

For each issue, or your issues of interest, provide a specific example about how the issue hampers the effectiveness of ICANN's multistakeholder model. Be sure to provide a specific and clear articulation of the issue so that it is clearly and fully defined. Please provide fact-based examples only. If offering a "new" issue to be considered, provide a clear articulation of the issue along with fact-based examples and a rationale about how the issue is hampering the effectiveness of ICANN's multistakeholder model. If you believe that an issue or issues do not belong on the Issues List, provide a rationale as to why the issue or issues should be removed.

Commenters are also invited to offer prioritization of the issues on the Issues List. When offering prioritization, carefully consider the following:

Issues that, if they are constructively addressed and solutions can be found, would have the greatest impact in making ICANN's multistakeholder model more effective and efficient.
Whether there are interdependencies between any of the issues that you are prioritizing. That is to say, for issue "A" to be addressed a solution for issue "B" must be addressed as well to achieve improvements in the effective functioning of ICANN's multistakeholder model.
Which issues could favorably impact the effectiveness of ICANN's multistakeholder model at a potentially lower cost?
Which issues could favorable impact the effectiveness of ICANN's multistakeholder model without introduction of unnecessary layers of process or bureaucracy?
Which issues could be combined or consolidated because their nature is so similar? When considering consolidating issues, carefully consider whether there are any interdependencies that argue against consolidation.

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