<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Comic Sans MS";
panose-1:3 15 7 2 3 3 2 2 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
font-size:10.0pt;
font-family:"Courier New";}
p.gmail-m8462047334025915652msolistparagraph, li.gmail-m8462047334025915652msolistparagraph, div.gmail-m8462047334025915652msolistparagraph
{mso-style-name:gmail-m_8462047334025915652msolistparagraph;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:120198896;
mso-list-template-ids:1074715908;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:481048674;
mso-list-template-ids:2102844238;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2
{mso-list-id:1792943430;
mso-list-template-ids:1049815784;}
@list l2:level1
{mso-level-start-at:3;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3
{mso-list-id:1873302628;
mso-list-template-ids:1993526576;}
@list l3:level1
{mso-level-start-at:2;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4
{mso-list-id:1925069550;
mso-list-template-ids:-142953884;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">I agree with Heather’s comments that a standing committee (if there is to be one) should review the SCI activities from 5 years ago if those recommendations are still relevant.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As the Chair of the PPSC that came up with the notion of the SCI, it was not intended to be a small group of Councilors only, but to members of the community familiar with PDPs, Working Groups, etc. Therefore I agree with Heather’s comment
that this is a good topic for the SG/C leaders to work on with Council Leadership.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Sincerely,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Jeff<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<table class="MsoTableGrid" border="1" cellspacing="0" cellpadding="0" style="border-collapse:collapse;border:none">
<tbody>
<tr>
<td width="192" valign="bottom" style="width:144.3pt;border:none;border-top:solid #06175F 3.0pt;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black;border:none windowtext 1.0pt;padding:0in"><img width="178" height="81" style="width:1.8489in;height:.8437in" id="Picture_x0020_1" src="cid:image001.png@01D6E80E.113C50C0"></span><o:p></o:p></p>
</td>
<td width="173" valign="bottom" style="width:129.95pt;border:none;border-top:solid #06175F 3.0pt;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:#06175F">Jeffrey J. Neuman</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black">Founder & CEO</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:#06175F">JJN Solutions, LLC</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black">p: +1.202.549.5079</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black">E:
</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><a href="mailto:jeff@jjnsolutions.com"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#1155CC">jeff@jjnsolutions.com</span></a><o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black">http://jjnsolutions.com</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> council <council-bounces@gnso.icann.org> <b>On Behalf Of
</b>Heather Forrest<br>
<b>Sent:</b> Sunday, January 10, 2021 10:23 PM<br>
<b>To:</b> Wolf-Ulrich Knoben <wuknoben@gmail.com><br>
<b>Cc:</b> Selli, Claudia <claudia.selli@intl.att.com>; Raoul Plommer <plommer@gmail.com>; GNSO Council List <council@gnso.icann.org>; Sue Schuler <secretariat@rysg.info>; Zoe Bonython <secretariat@icannregistrars.org>; Bruna Martins dos Santos <bruna.mrtns@gmail.com>;
Wolf-Ulrich Knoben <Wolf-Ulrich.Knoben@t-online.de>; Demetriou, Samantha <sdemetriou@verisign.com>; Brenda Brewer <brenda.brewer@icann.org>; GNSO Chairs <gnso-chairs@icann.org>; aheineman@godaddy.com; chair@rysg.info; Raphaël Beauregard-Lacroix <rbeauregardlacroix@gmail.com><br>
<b>Subject:</b> Re: [council] GNSO Standing Committee for Continuous Improvement – Ideas and Possible Approach<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Many thanks, Philippe, Pam and Tatiana, for initiating this discussion about the formation of a new standing committee.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I have some general reluctance based on the experience of the prior SCI, as well as specific thoughts about the Action Decision Radar. <o:p></o:p></p>
</div>
<div>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
While the Action Decision Radar is admittedly frighteningly long, here are relatively few items on that list that fall squarely into the bucket of "improvements", as opposed to policy development. I can see only these:<o:p></o:p></li></ul>
<ul type="disc">
<ul type="circle">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1">
Council to decide when to launch review of Policy & Implementation recommendations review <o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1">
Council to monitor for assignments related to the Evolution of Multi Stakeholder model (currently a watch-and-wait)<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1">
Council to monitor for ATRT3 implementation assignments; awaiting Board adoption of ATRT3 recommendations (to be updated following Board adoption, but as yet this too is a watch-and-wait, and is related to another item on this list, which is planning/scoping
the GNSO3 Review)<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1">
SSR2 Results to be reviewed <o:p></o:p></li></ul>
</ul>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
The first item on this list, a review of the SCI's recommendations of June 2015, must, in my view, be undertaken prior to any formation of a new Standing Committee on Improvements. This review should not be a 'kitchen sink' type review, but rather an identification
of any SCI recommendations that remain unimplemented (and an analysis of why/whether timely and appropriate to implement now, etc) and an identification of those which were implemented but perhaps may not be working optimally or as expected. This group could
also be tasked with <b>identifying</b> any other potential improvements. Like Wolf-Ulrich, my concern is that the rationale or justification for forming a new SCI-like body isn't yet made out. The numerous dot points on the
<a href="https://docs.google.com/document/d/1HBCXMkLb7vFkWClgCpsr8WjYScz3UDh4/edit">
SCCI Ideas and Possible Approach document</a> are not yet sufficiently tangible to justify forming a new group, in my opinion.<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
The Council in place at the time the SCI recommendations were approved in 2015 had difficulty bridging the gap between the SCI's recommendations and actual Council practice. Many members of the SCI had never served on Council and were not familiar with the
workaday processes of how Council operates. While I am always in favour of efforts that have Councilors and broader GNSO community members working together, we need to ensure that we don't end up with a relatively inexperienced group that makes idealised recommendations
for how Council can do its work better. I'm not suggesting that we do a post-mortem on the SCI 5 years after its closure, but simply that we as a community reflect carefully before launching any new initiative. <o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
I prefer the idea of task forces on a particular topic to another SCI. This enables those with expertise on particular matters to selectively volunteer their time to relevant efforts, while a generally-themed SCI-like body may actually repel such subject matter
experts. A small committee within the GNSO (not necessarily Council) could be set up to oversee this work. Unless there is a clear link to Council's remit under the Bylaws as manager of the PDP or to one of the narrow EC Responsibilities in which Council plays
an administrative function, I do not see many of the tasks in the proposed remit of this new body as falling resolutely within Council's remit. I'll copy this final comment into the SCCI Ideas and Possible Approach document to ensure these views are captured
there.<o:p></o:p></li></ul>
<div>
<p class="MsoNormal">I think this is an opportunity for the Council and GNSO SG/C leaders to work more closely together. One of the ways to make Council more efficient and effective is to slough off those tasks which are GNSO-related but not PDP- or EC-related
to the GNSO community. The more Council takes on, obviously the less well it can do everything it already has on its plate, and in any event, the Bylaws do not envisage such an all-encumbered body as the GNSO Council is becoming.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Best wishes,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Heather<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Mon, Jan 11, 2021 at 7:35 AM <<a href="mailto:wuknoben@gmail.com">wuknoben@gmail.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="DE" style="font-size:12.0pt">Dear Philippe and all,</span><span lang="DE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="DE" style="font-size:12.0pt"> </span><span lang="DE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:12.0pt">I’ve checked the paper, and it causes some questions regarding the target and the remit of the suggested SCCI which should cover GNSO “processes and
procedures”.</span><span lang="DE"><o:p></o:p></span></p>
<ol start="1" type="1">
<li class="gmail-m8462047334025915652msolistparagraph" style="mso-list:l4 level1 lfo2">
<span style="font-size:12.0pt">With the understanding that the Council including the related WGs is responsible for any kind of PDP and ICANN staff – together with the community – is responsible for the implementation the SCCI should not undertake any policy
and policy implementation tasks like</span><span lang="DE"><o:p></o:p></span></li></ol>
<p class="gmail-m8462047334025915652msolistparagraph" style="margin-left:53.4pt;text-indent:-.25in;mso-list:l1 level1 lfo3">
<![if !supportLists]><span lang="DE" style="font-size:10.0pt;font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:12.0pt;color:black">Implementation of WS2 recommendations that are not SG/C specific (if policy related)</span><span lang="DE"><o:p></o:p></span></p>
<p class="gmail-m8462047334025915652msolistparagraph" style="margin-left:53.4pt;text-indent:-.25in;mso-list:l1 level1 lfo3">
<![if !supportLists]><span lang="DE" style="font-size:10.0pt;font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:12.0pt;color:black">Review of Policy & Implementation WG recommendations</span><span lang="DE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:12.0pt"> </span><span lang="DE"><o:p></o:p></span></p>
<ol start="2" type="1">
<li class="gmail-m8462047334025915652msolistparagraph" style="mso-list:l3 level1 lfo4">
<span style="font-size:12.0pt">By deducting the a.m. items from the SCCI to do list the remaining remit would still cover an extremely broad range of items which – as suggested – may only be covered by specialized sub-teams. In this case I’d like to ask for
which purpose the SCCI is needed. Couldn’t the council themselves lay the ground for these sub-teams?</span><span lang="DE"><o:p></o:p></span></li></ol>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:12.0pt"> </span><span lang="DE"><o:p></o:p></span></p>
<ol start="3" type="1">
<li class="gmail-m8462047334025915652msolistparagraph" style="mso-list:l2 level1 lfo5">
<span style="font-size:12.0pt">I support the idea of “continuous improvement” and see also the need to institutionalize it. But don’t overload it.</span><span lang="DE"><o:p></o:p></span></li></ol>
<p class="gmail-m8462047334025915652msolistparagraph"><span style="font-size:12.0pt"> </span><span lang="DE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:12.0pt">Best regards</span><span lang="DE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:12.0pt">Wolf-Ulrich</span><span lang="DE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:12.0pt"> </span><span lang="DE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="DE"><o:p></o:p></span></p>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span lang="DE">Von:</span></b><span lang="DE"> Carlton Samuels <<a href="mailto:carlton.samuels@gmail.com" target="_blank">carlton.samuels@gmail.com</a>>
<br>
<b>Gesendet:</b> Sonntag, 3. Januar 2021 20:43<br>
<b>An:</b> Fouquart <<a href="mailto:philippe.fouquart@orange.com" target="_blank">philippe.fouquart@orange.com</a>><br>
<b>Cc:</b> GNSO Council List <<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a>>; Heather Forrest <<a href="mailto:haforrestesq@gmail.com" target="_blank">haforrestesq@gmail.com</a>>; Selli, Claudia <<a href="mailto:claudia.selli@intl.att.com" target="_blank">claudia.selli@intl.att.com</a>>;
Wolf-Ulrich Knoben <<a href="mailto:Wolf-Ulrich.Knoben@t-online.de" target="_blank">Wolf-Ulrich.Knoben@t-online.de</a>>; Bruna Martins dos Santos <<a href="mailto:bruna.mrtns@gmail.com" target="_blank">bruna.mrtns@gmail.com</a>>; Raoul Plommer <<a href="mailto:plommer@gmail.com" target="_blank">plommer@gmail.com</a>>;
Raphaël Beauregard-Lacroix <<a href="mailto:rbeauregardlacroix@gmail.com" target="_blank">rbeauregardlacroix@gmail.com</a>>;
<a href="mailto:aheineman@godaddy.com" target="_blank">aheineman@godaddy.com</a>; Demetriou, Samantha <<a href="mailto:sdemetriou@verisign.com" target="_blank">sdemetriou@verisign.com</a>>;
<a href="mailto:chair@rysg.info" target="_blank">chair@rysg.info</a>; Sue Schuler <<a href="mailto:secretariat@rysg.info" target="_blank">secretariat@rysg.info</a>>; Zoe Bonython <<a href="mailto:secretariat@icannregistrars.org" target="_blank">secretariat@icannregistrars.org</a>>;
Brenda Brewer <<a href="mailto:brenda.brewer@icann.org" target="_blank">brenda.brewer@icann.org</a>>;
<a href="mailto:gnso-chairs@icann.org" target="_blank">gnso-chairs@icann.org</a><br>
<b>Betreff:</b> Re: [council] GNSO Standing Committee for Continuous Improvement – Ideas and Possible Approach<o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="DE"> <o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="DE" style="font-family:"Tahoma",sans-serif">Thank you Chair. I made a few comments.</span><span lang="DE"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="DE" style="font-family:"Tahoma",sans-serif"> </span><span lang="DE"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="DE" style="font-family:"Tahoma",sans-serif">Carlton</span><span lang="DE"><o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="DE"><br>
==============================<br>
</span><i><span lang="DE" style="font-family:"Comic Sans MS"">Carlton A Samuels</span></i><span lang="DE"><br>
</span><i><span lang="DE" style="font-family:"Comic Sans MS"">Mobile: 876-818-1799<br>
<span style="color:#33CC00">Strategy, Process, Governance, Assessment & Turnaround</span></span></i><span lang="DE"><br>
=============================<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="DE"> <o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="DE"> <o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="DE">On Sun, Jan 3, 2021 at 8:39 AM <<a href="mailto:philippe.fouquart@orange.com" target="_blank">philippe.fouquart@orange.com</a>> wrote:<o:p></o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<p style="margin:0in"><span style="color:black">Dear Councilors, SG/C Chairs,</span><span lang="DE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="DE"><o:p></o:p></span></p>
<p style="margin:0in"><span style="color:black">As you may be aware, there are quite a number of projects on the Council’s Action Decision Radar (see
</span><span lang="FR"><a href="https://community.icann.org/x/14vzC" target="_blank"><span lang="EN-US" style="color:#0563C1">https://community.icann.org/x/14vzC</span></a></span><span style="color:black">) that deal with improvements to GNSO processes and
procedures. We heard from you during the Strategic Planning Session about the importance of prioritizing work as well as considering the resources available to conduct work as efficiently as possible. To this end, the suggestion was made to explore the possibility
of creating a Standing Committee that would be tasked with addressing projects or assignments that are mainly focused on improving existing GNSO processes and procedures. </span><span lang="DE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="DE"><o:p></o:p></span></p>
<p style="margin:0in"><span style="color:black">To further explore this possible approach, the Council leadership team has worked with the staff support team on developing a high-level outline for your review and input (see
</span><span lang="FR"><a href="https://docs.google.com/document/d/1HBCXMkLb7vFkWClgCpsr8WjYScz3UDh4/edit" target="_blank"><span lang="EN-US" style="color:#0563C1">https://docs.google.com/document/d/1HBCXMkLb7vFkWClgCpsr8WjYScz3UDh4/edit</span></a></span><span style="color:black">).
Although the Standing Committee would be chartered by and operate under the oversight of the GNSO Council, it is intended to be a GNSO effort which can only be successful with the full support and participation of all SG and Cs. We appreciate that it may be
challenging to comment on this approach without having all the details, but our hope is that by soliciting input at this point in time, we would be able to develop a more detailed proposal as a next step factoring in your suggestions and perspectives. </span><span lang="DE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="DE"><o:p></o:p></span></p>
<p style="margin-bottom:12.0pt"><span style="color:black">Some of the questions we hope you can focus on are:</span><span lang="DE"><o:p></o:p></span></p>
<p style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:.5in;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:Symbol;color:black">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black">
</span><span style="color:black">Is this the right approach to benefit from synergies? If not, how should all the projects listed be tackled instead?</span><span lang="DE"><o:p></o:p></span></p>
<p style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:.5in;vertical-align:baseline">
<span lang="FR" style="font-size:10.0pt;font-family:Symbol;color:black">·</span><span lang="FR" style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black">
</span><span style="color:black">How to ensure appropriate scoping of work? The idea is that the standing committee would tackle topics that cut across the GNSO community and/or would benefit from a cross-GNSO collaboration. A possible approach could be that
the charter provides an indication of the topics that are expected to be tackled, but specific assignments are confirmed in the form of a clear scoping document and work plan that is approved by the GNSO Council, with input from SG/Cs via their respective
Council members. </span><span lang="FR" style="color:black">Are there other approaches that could be considered?</span><span lang="DE"><o:p></o:p></span></p>
<p style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:.5in;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:Symbol;color:black">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black">
</span><span style="color:black">What should membership look like? How to ensure a balanced composition which at the same time is nimble enough to work effectively? How to introduce sufficient flexibility to allow for expert participation?</span><span lang="DE"><o:p></o:p></span></p>
<p style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:.5in;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:Symbol;color:black">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black">
</span><span style="color:black">What decision-making methodology should be applied? Or is this to be determined based on the assignment the Standing Committee is tasked with? </span><span lang="DE"><o:p></o:p></span></p>
<p style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:.5in;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:Symbol;color:black">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black">
</span><span style="color:black">Is it feasible to consider tackling some of the projects identified in parallel through different sub-committees?</span><span lang="DE"><o:p></o:p></span></p>
<p style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:.5in;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:Symbol;color:black">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black">
</span><span style="color:black">How should the work be prioritized if a Standing Committee is created? Each of the possible projects identified could take a substantial amount of time to address and resolve which means certain items could take a while to get
addressed.</span><span lang="DE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Times New Roman",serif"> </span><span lang="DE"><o:p></o:p></span></p>
<p style="margin:0in"><span style="color:black">Of course, there may be other topics you want to weigh in on.</span><span lang="DE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="DE"><o:p></o:p></span></p>
<p style="margin:0in"><span style="color:black">We hope to receive your feedback <i>
in advance of the next Council meeting</i> which is scheduled for Thursday 21 January, either via your input on the google doc (see
</span><span lang="FR"><a href="https://docs.google.com/document/d/1HBCXMkLb7vFkWClgCpsr8WjYScz3UDh4/edit" target="_blank"><span lang="EN-US" style="color:#0563C1">https://docs.google.com/document/d/1HBCXMkLb7vFkWClgCpsr8WjYScz3UDh4/edit</span></a></span><span style="color:black">)
or in response to this email. As you will have seen, a number of the possible projects for the Standing Committee are fairly high on the Council’s Action Decision Radar so we hope to agree on an approach for tackling these sooner rather than later. </span><span lang="DE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="DE"><o:p></o:p></span></p>
<p style="margin:0in"><span style="color:black">Best regards and happy holidays,</span><span lang="DE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="DE"><o:p></o:p></span></p>
<p style="margin:0in"><span lang="FR" style="color:black">Philippe Fouquart</span><span lang="DE"><o:p></o:p></span></p>
<p style="margin:0in"><span lang="FR" style="color:black">Chair, GNSO</span><span lang="DE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="FR" style="font-size:10.0pt;font-family:"Arial",sans-serif"> </span><span lang="DE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="FR" style="font-size:10.0pt;font-family:"Arial",sans-serif"> </span><span lang="DE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="FR" style="font-size:10.0pt;font-family:"Arial",sans-serif"> </span><span lang="DE"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="FR"> </span><span lang="DE"><o:p></o:p></span></p>
</div>
<pre><span lang="FR">_________________________________________________________________________________________________________________________</span><span lang="DE"><o:p></o:p></span></pre>
<pre><span lang="FR"> </span><span lang="DE"><o:p></o:p></span></pre>
<pre><span lang="FR">Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc</span><span lang="DE"><o:p></o:p></span></pre>
<pre><span lang="FR">pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler</span><span lang="DE"><o:p></o:p></span></pre>
<pre><span lang="FR">a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,</span><span lang="DE"><o:p></o:p></span></pre>
<pre><span lang="FR">Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.</span><span lang="DE"><o:p></o:p></span></pre>
<pre><span lang="FR"> </span><span lang="DE"><o:p></o:p></span></pre>
<pre><span lang="FR">This message and its attachments may contain confidential or privileged information that may be protected by law;</span><span lang="DE"><o:p></o:p></span></pre>
<pre><span lang="FR">they should not be distributed, used or copied without authorisation.</span><span lang="DE"><o:p></o:p></span></pre>
<pre><span lang="FR">If you have received this email in error, please notify the sender and delete this message and its attachments.</span><span lang="DE"><o:p></o:p></span></pre>
<pre><span lang="FR">As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.</span><span lang="DE"><o:p></o:p></span></pre>
<pre><span lang="FR">Thank you.</span><span lang="DE"><o:p></o:p></span></pre>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="DE">_______________________________________________<br>
council mailing list<br>
<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/council" target="_blank">https://mm.icann.org/mailman/listinfo/council</a><br>
<br>
_______________________________________________<br>
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 (<a href="https://www.icann.org/privacy/policy" target="_blank">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" target="_blank">https://www.icann.org/privacy/tos</a>). 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.<o:p></o:p></span></p>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</body>
</html>