[council] SSAD Light Impact Council - draft response

Thu Jun 30 04:12:56 UTC 2022

Hi all,

Sorry, I know it must be because of my inadequacy in English as a
non-native speaker, but I'm having trouble understanding what this
paragraph means:

We have monitored the considerable community discussions devoted to this
prioritisation topic. In each instance, community members were heard to ask
specific operations questions to aid in their consideration. We think this
is not the best use of the community’s time, nor does the topic fall within
its expertise.

Are we saying the community is being asked specific operation questions to
aid in ICANN org or the Board's consideration? I think I understand the
last 2 sentences where we say we don't think those questions are
appropriate to be directed to us/ the community. It's just the sentence
marked in yellow I have trouble comprehending.

Would be grateful for any explanation and sorry again if this is after the
deadline!

Best,
Manju

On Wed, Jun 29, 2022 at 10:16 PM DiBiase, Gregory via council <
council at gnso.icann.org> wrote:

> Hi All,
>
>
>
> A couple other small edits attached that I think capture our conversation
> in The Hague.
>
>
>
> Thanks,
>
> Greg
>
>
>
> *From:* council <council-bounces at gnso.icann.org> *On Behalf Of *philippe.fouquart---
> via council
> *Sent:* Tuesday, June 28, 2022 5:34 AM
> *To:* kurt kjpritz.com <kurt at kjpritz.com>
> *Cc:* gnso-secs at icann.org; council at gnso.icann.org
> *Subject:* RE: [EXTERNAL][council] SSAD Light Impact Council - draft
> response
>
>
>
> *CAUTION*: This email originated from outside of the organization. Do not
> click links or open attachments unless you can confirm the sender and know
> the content is safe.
>
>
>
> Correction: we did say _*tomorrow*_ Wednesday 29th cob as deadline for
> this, not today.
>
>
>
> Thanks,
>
> Philippe
>
>
>
>
>
> Orange Restricted
>
> *From:* FOUQUART Philippe INNOV/NET
> *Sent:* Tuesday, June 28, 2022 2:27 PM
> *To:* 'kurt kjpritz.com' <kurt at kjpritz.com>
> *Cc:* council at gnso.icann.org; gnso-secs at icann.org
> *Subject:* RE: [council] SSAD Light Impact Council - draft response
>
>
>
> Hi Kurt.
>
>
>
> Thanks for sorting out the order of priorities in the letter, this is
> helpful. Some of the elements of the first iteration being more records of
> the discussion, we will see whether there’s benefit in bringing some of
> them back without losing in conciseness or being repetitive.
>
>
>
> Everyone,
>
>
>
> please share any other comment you may have by the end of the day, for us
> to send this later this week.
>
>
>
> Thanks.
>
> Regards,
>
> Philippe
>
>
>
>
>
> Orange Restricted
>
> *From:* kurt kjpritz.com <kurt at kjpritz.com>
> *Sent:* Monday, June 27, 2022 10:52 PM
> *To:* FOUQUART Philippe INNOV/NET <philippe.fouquart at orange.com>
> *Cc:* council at gnso.icann.org; gnso-secs at icann.org
> *Subject:* Re: [council] SSAD Light Impact Council - draft response
>
>
>
> Hi Philippe:
>
>
>
> Thanks for the opportunity to comment on this draft. Please consider the
> attached and feel free to use some, all or none of it.
>
>
>
> I have added a brief bit of context at the start as this issue did not
> arise from the Board-Council interaction but rather came in separately from
> the staff. I maintained the two main messages:
>
>    1. to emphasize the importance of both (SSAD and SubPro) initiatives,
>    and
>    2. that the Council does not view itself in a position, nor does it
>    consider it the role of the Council, to dictate the allocation of ICANN org
>    resources now that these policy recommendations are with the ICANN Board.
>
>
>
> There was some re-arranging / re-wording that would render a redline
> somewhat ineffective but I can produce one.
>
>
>
> I hope you find this constructive and helpful.
>
>
>
> Best regards,
>
>
>
> Kurt
>
>
>
>
>
> On Jun 22, 2022, at 3:22 AM, philippe.fouquart--- via council <
> council at gnso.icann.org> wrote:
>
>
>
> Dear Councilors,
>
>
>
> For you review, please find attached a draft letter to the Board regarding
> the impact of the development of an SSAD Light Design Paper on other
> ongoing work, including the SubPro ODP. This is intended to capture the
> conclusions of last week’s discussion item.
>
>
>
> Please provide your comments within a week, by Wednesday 29th COB UTC.
>
>
>
> Hope all those who could attend the The Hague meeting travelled safe and
> well back home.
>
>
>
> Regards,
>
> Philippe
>
>
>
> _________________________________________________________________________________________________________________________
>
>
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
>
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
>
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
>
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
>
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
>
> they should not be distributed, used or copied without authorisation.
>
> If you have received this email in error, please notify the sender and delete this message and its attachments.
>
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
>
> Thank you.
>
> <SSAD Light Impact Council Response - upd 16 June 2022.docx>
> _______________________________________________
> council mailing list
> council at gnso.icann.org
> https://mm.icann.org/mailman/listinfo/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.
>
>
>
> _________________________________________________________________________________________________________________________
>
>
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
>
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
>
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
>
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
>
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
>
> they should not be distributed, used or copied without authorisation.
>
> If you have received this email in error, please notify the sender and delete this message and its attachments.
>
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
>
> Thank you.
>
> _______________________________________________
> council mailing list
> council at gnso.icann.org
> https://mm.icann.org/mailman/listinfo/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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/council/attachments/20220630/5917c825/attachment-0001.html>