<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
<div dir="auto"><span style="font-family: Calibri, sans-serif; font-size: 12pt; white-space: pre-wrap;">Dear SG/C Chairs,</span></div>
<div dir="auto"><br>
<p style="margin-top:0.0pt;margin-bottom:0.0pt;" dir="ltr"><span style="font-size: 12pt; font-family: Calibri, sans-serif; font-variant-numeric: normal; font-variant-east-asian: normal; vertical-align: baseline; white-space: pre-wrap;">As you may be aware,
we received a discussion draft of the attached paper, Modifying Consensus Policies from ICANN org on 23 October (see
</span><a style="text-decoration-line: none;" href="https://mm.icann.org/pipermail/council/2021-October/025106.html"><span style="font-size: 12pt; font-family: Calibri, sans-serif; color: rgb(5, 99, 193); font-variant-numeric: normal; font-variant-east-asian: normal; text-decoration-line: underline; text-decoration-skip-ink: none; vertical-align: baseline; white-space: pre-wrap;">https://mm.icann.org/pipermail/council/2021-October/025106.html</span></a><span style="font-size: 12pt; font-family: Calibri, sans-serif; font-variant-numeric: normal; font-variant-east-asian: normal; vertical-align: baseline; white-space: pre-wrap;">).
The ICANN organization has developed this paper as a thought exercise to share with the community for information and input on existing processes. The paper 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. </span></p>
<br>
<p style="margin-top:0.0pt;margin-bottom:0.0pt;" dir="ltr"><span style="font-size: 12pt; font-family: Calibri, sans-serif; font-variant-numeric: normal; font-variant-east-asian: normal; vertical-align: baseline; white-space: pre-wrap;">The message also notes
that the ICANN 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. </span></p>
<br>
<p style="margin-top:0.0pt;margin-bottom:0.0pt;" dir="ltr"><span style="font-size: 12pt; font-family: Calibri, sans-serif; font-variant-numeric: normal; font-variant-east-asian: normal; vertical-align: baseline; white-space: pre-wrap;">The Council discussed
during its wrap up session at ICANN72 that, as this touches upon the GNSO PDP, it would be important to engage on this topic with SG/Cs. As a result, we would like to invite you to identify a representative to join the small team that is in the process of
forming (see small team assignment document attached). Please let gnso-secs know by 10 November at the latest who from your group will be joining this effort as the small team is expected to commence its discussions shortly thereafter.</span></p>
<br>
<p style="margin-top:0.0pt;margin-bottom:0.0pt;" dir="ltr"><span style="font-size: 12pt; font-family: Calibri, sans-serif; font-variant-numeric: normal; font-variant-east-asian: normal; vertical-align: baseline; white-space: pre-wrap;">Best regards,</span></p>
<br>
<p style="margin-top:0.0pt;margin-bottom:0.0pt;" dir="ltr"><span style="font-size: 12pt; font-family: Calibri, sans-serif; font-variant-numeric: normal; font-variant-east-asian: normal; vertical-align: baseline; white-space: pre-wrap;">Philippe </span></p>
<br>
</div>
<div dir="auto"><br>
</div>
<div id="composer_signature" dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div><br>
</div>
<PRE>_________________________________________________________________________________________________________________________
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.
</PRE></body>
</html>