[council] FW: Modifying consensus policies

[philippe.fouquart at orange.com]

Dear Councilors,

Please see Theresa's email and attached document developed by ICANN org to the Board's intention on the policy lifecyle.

Beyond its educational goal, the paper also identifies potential gaps, shortcomings and room for improvement for which our community's input is sought. It is certainly something we can use for our SPS to plan for the work of the year ahead.

Thank you.
Regards,
Philippe



Orange Restricted
From: Theresa Swinehart <theresa.swinehart at icann.org>
Sent: Saturday, October 23, 2021 1:21 AM
To: FOUQUART Philippe INNOV/NET <philippe.fouquart at orange.com>
Cc: Karen Lentz <karen.lentz at icann.org>; Steve Chan <steve.chan at icann.org>; David Olive <david.olive at icann.org>; Mary Wong <mary.wong at icann.org>
Subject: Modifying consensus policies

Dear Philippe,

I would like to share with you and the GNSO Council a discussion draft of the attached paper, Modifying Consensus Policies. The ICANN organization has developed this paper as a thought exercise to share with the community for information and input on existing processes.  As mentioned in some of our previous interactions, this piece has been developed within the org, considering what procedures are in place for modifying consensus policies, and where there may be gaps, ambiguities, or opportunities for additional collaboration.

The Board has expressed interest in understanding these processes and discussing possible mechanisms to address where there are identified and agreed needs for greater clarity or elaboration.  As the GNSO's processes are interwoven with those of the Board and org in the consensus policy lifecycle, the org is seeking input from GNSO stakeholders before taking this paper to the Board.

To date for the org, this review of applicable procedures to modify policies has been helpful in identifying gaps that might benefit from further clarification or discussion, relating to how to modify an existing policy in varying circumstances. Some possible gaps are further described in section 3 of this paper, to provide an opportunity for community discussions on identifying the source of gaps and confirming where they exist.  In the spirit of sharing ideas and observations, we hope you also find this useful, and the org looks forward to hearing from GNSO stakeholders on these topics.

I appreciate that this comes at a busy time, and look forward to engaging on this in due course.

And, wishing the best for a successful ICANN72 meeting.

Kind regards,

Theresa


_________________________________________________________________________________________________________________________

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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/council/attachments/20211025/d6317a45/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DiscussionDraft-ModifyingConsensusPolicies-22oct21.pdf
Type: application/pdf
Size: 405493 bytes
Desc: DiscussionDraft-ModifyingConsensusPolicies-22oct21.pdf
URL: <https://mm.icann.org/pipermail/council/attachments/20211025/d6317a45/DiscussionDraft-ModifyingConsensusPolicies-22oct21-0001.pdf>