<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:"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:"Trebuchet MS";
panose-1:2 11 6 3 2 2 2 2 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;}
p.m-8712383239333417127msolistparagraph, li.m-8712383239333417127msolistparagraph, div.m-8712383239333417127msolistparagraph
{mso-style-name:m_-8712383239333417127msolistparagraph;
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.EmailStyle19
{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:2042901782;
mso-list-template-ids:-1857631190;}
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">All,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I strongly urge not using only councilors. You need to do work swiftly, but also you need to do it credibly. And in a manner that people will trust.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">But I have said this a million times (now 1,000,001 times). A small group of Councilors without a public mailing list acting in a non-fully transparent manner sounds like it will be faster in the short term, but MUCH longer in the long
term.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<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="177" height="81" style="width:1.8472in;height:.8402in" id="Picture_x0020_2" src="cid:image001.png@01D95682.69C00770"></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"><a href="http://jjnsolutions.com">http://jjnsolutions.com</a></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>Anne ICANN via council<br>
<b>Sent:</b> Tuesday, March 14, 2023 12:42 PM<br>
<b>To:</b> Sebastien@registry.godaddy<br>
<b>Cc:</b> gnso-secs@icann.org; GNSO-Chairs <gnso-chairs@icann.org>; COUNCIL@GNSO.ICANN.ORG<br>
<b>Subject:</b> Re: [council] SubPro Small Team<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Many thanks Sebastien. Comments for further discussion:<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">1. We had talked about a small team to triage the issues and make recommendations to the GNSO Council as to how to proceed. I'll call this the Triage Small Team. The summary below sounds as though we are thinking the small team will
have broad community participation and will itself resolve issues with the Board's concerns. I am not sure that is possible in the MSM process. I think the small team must identify whether there are policy issues that must be addressed and make a recommendation
to Council as to how to address the policy issues. Already there are complaints in the community about the small team process being "obscure" and not being part of an open policy process. Some of these surfaced in the current meetings in connection with
the Facilitated Dialogue on Closed Generics and are well-founded. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"> 2. I think it will in fact save time if the small team is just a Council subset at the start and does nothing but the triage exercise previously discussed and then quickly brings back its recommendations to the full Council regarding
how to proceed and how to include other SOs and ACs in the dialogue at that point. If not handled in this manner, there is a significant risk of this exercise not yielding timely results before ICANN 77. In short, it will appear that the Small Team itself
is making policy. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">3. Personally, I would recommend convening the Triage Small Team in person for a day or two of discussion on the 38 items as soon as possible in a central geographic location (with hybrid participation ) to determine (A) if we can conclude
that certain issues are actually implementation to be addressed by the IRT and (B) where the GNSO may want to stick by its policy recommendation and/or let the Board override that by 2/3 vote (per the ByLaws) if it is so inclined at ICANN 77. (FYI the foregoing
Item Bwas a point made in the joint CPH Board meeting that was just held at ICANN 77.) In this regard, i don't think there is anything that says that the Board cannot modify a Final Report Recommendation itself due to lack of feasibility from an organizational
feasibility point of view. Instead the Board has said "reconvene the Sub Pro WG and modify your Recommendations" but this is extremely inefficient and would cause great delay. I am concerned that the proposed Small Team structure below is essentially a reconvening
of a policy-making team or PDP without actually calling it that.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">So I believe that Council should<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">(1) stick with the Triage Small Team idea previously discussed<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">(2) convene that Triage Small Team in person for a day or two to go through the 38 issues. This can be a hybrid meeting of course. Best for Avri and Becky to participate at this meeting.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">(3) require the Triage Small Team to report back with its analysis , summary of each issue, and recommendation for moving forward by the Motion deadline for the April GNSO Council meeting. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Looking forward to tomorrow's discussion,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Anne<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">Anne Aikman-Scalese<o:p></o:p></p>
</div>
<p class="MsoNormal">GNSO Councilor<o:p></o:p></p>
<div>
<p class="MsoNormal">NomCom Non-Voting 2022-2024<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="mailto:anneicanngnso@gmail.com" target="_blank">anneicanngnso@gmail.com</a><o:p></o:p></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Mon, Mar 13, 2023 at 4:00 PM Sebastien--- via council <<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</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>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">Dear Council Colleagues,<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">I wanted to use some time tomorrow during our Informal Council Session to advance our conversation on the SubPro small team.<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">Following the few discussions we had with the Board on what they are looking for, following the discussion we had a week ago prior to getting to Cancun on the
very idea of a small team, but also following 3 days of intense discussions on the SubPro topic I wanted to propose a few principle:<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> <o:p></o:p></span></p>
<ol start="1" type="1">
<li class="m-8712383239333417127msolistparagraph" style="mso-list:l0 level1 lfo1">
<span lang="EN-AU">We, the GNSO Council, are asked by the Board to review a number of topics. The responses we will return will be GNSO Council responses. The small team should be tasked with formulating GNSO Council responses.<o:p></o:p></span></li><li class="m-8712383239333417127msolistparagraph" style="mso-list:l0 level1 lfo1">
<span lang="EN-AU">We want to be able to move fast, but given the importance of the topic of SubPro to the entire Community, we want to be diligent, thoughtful and transparent.<o:p></o:p></span></li><li class="m-8712383239333417127msolistparagraph" style="mso-list:l0 level1 lfo1">
<span lang="EN-AU">There is a strong interest from other SOACs to participate in these discussions and to have a voice. It is legitimate and I think we need to be able to hear those.<o:p></o:p></span></li><li class="m-8712383239333417127msolistparagraph" style="mso-list:l0 level1 lfo1">
<span lang="EN-AU">The small team that is gathered should, by definition, remain small, and I think focussed on Councillors.<o:p></o:p></span></li><li class="m-8712383239333417127msolistparagraph" style="mso-list:l0 level1 lfo1">
<span lang="EN-AU">We have identified that given the technicity of a large number of topics at hand, the small team should be able to consult with Subject Matter Experts from within the Council and beyond.<o:p></o:p></span></li><li class="m-8712383239333417127msolistparagraph" style="mso-list:l0 level1 lfo1">
<span lang="EN-AU">The small team will need to integrate with its peers on the Board and from ICANN Org.<o:p></o:p></span></li></ol>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">We should have about 20-30 minutes on this during our discussions tomorrow. I would like to be able to come from it with a clear view of what this small team
may be, to engage our counterparts and start working as early as possible. <o:p>
</o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">Kindly,<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> <o:p></o:p></span></p>
<div>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="65%" style="width:65.0%;border-collapse:collapse">
<tbody>
<tr>
<td width="500" valign="top" style="width:375.0pt;border:none;border-bottom:solid #0B3354 1.5pt;padding:0in 5.25pt 0in 0in">
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> <o:p></o:p></span></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="background:white;border-collapse:collapse">
<tbody>
<tr style="height:5.25pt">
<td width="500" style="width:375.0pt;padding:0in 0in 0in 0in;height:5.25pt"></td>
</tr>
</tbody>
</table>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;background:white">
<b><span lang="EN-AU" style="font-family:"Trebuchet MS",sans-serif;color:#444444">Sebastien Ducos</span></b><span lang="EN-AU"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;background:white">
<span lang="EN-AU" style="font-size:9.0pt;font-family:"Trebuchet MS",sans-serif;color:#444444">GoDaddy Registry | Senior Client Services Manager</span><span lang="EN-AU"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"><img border="0" width="215" height="34" style="width:2.243in;height:.3541in" id="m_-8712383239333417127Picture_x0020_1" src="cid:image002.png@01D95682.69C00770" alt="signature_3228593622"></span><span lang="EN-AU"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;background:white">
<span lang="EN-AU" style="font-size:9.0pt;font-family:"Trebuchet MS",sans-serif;color:#444444">+33612284445</span><span lang="EN-AU"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;background:white">
<span lang="EN-AU" style="font-size:9.0pt;font-family:"Trebuchet MS",sans-serif;color:#444444">France & Australia</span><span lang="EN-AU"><o:p></o:p></span></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="background:white;border-collapse:collapse">
<tbody>
<tr style="height:5.25pt">
<td width="500" style="width:375.0pt;padding:0in 0in 0in 0in;height:5.25pt"></td>
</tr>
</tbody>
</table>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;background:white">
<span lang="EN-AU" style="color:black"><a href="mailto:sebastien@registry.godaddy" target="_blank"><span style="font-size:9.0pt;font-family:"Trebuchet MS",sans-serif;color:#1976D2;text-decoration:none">sebastien@registry.godaddy</span></a></span><span lang="EN-AU"><o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> <o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal">_______________________________________________<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></p>
</div>
</blockquote>
</div>
</div>
</body>
</html>