<div dir="ltr"><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small">Hi Jeff,</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small">Thank you for drafting the letter! I've made some minor edits under suggestion mode.</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small">As the Chair of CCOICI, I inevitably feel we should elaborate more on the compromise language we had and why it didn't stick in the recommendation report. But as a member of the Council, I agree with your decision to leave them out to avoid confusion. We can probably dive deeper into this during our next bilateral with the GAC if they remain interested in this topic.</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small">Also agree with removing the unnecessary aggressive language in some SG/C's responses. I didn't feel the grouping was necessary, but don't mind it either now that it's presented this way. </div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small">I would vote for keeping the summaries, although it kind of contradicts what you originally suggested to be a short, 1-page summary. :P</div><br><font face="arial, sans-serif"><span class="gmail_default" style="font-family:arial,sans-serif;font-size:small"></span></font><div><font face="arial, sans-serif"><span class="gmail_default" style="font-family:arial,sans-serif;font-size:small"><br></span></font></div><div><font face="arial, sans-serif"><span class="gmail_default" style="font-family:arial,sans-serif;font-size:small">Best,</span></font></div><div><font face="arial, sans-serif"><span class="gmail_default" style="font-family:arial,sans-serif;font-size:small">Manju</span></font></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Mar 22, 2024 at 4:36 AM Jeff Neuman via council <<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div dir="ltr">
<div dir="ltr">All,</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">I feel like I should explain why I drafted the letter in the way that I have since I have gotten some informal feedback. Yes, I understand the Council did not want to paraphrase the CCOICI statements and just send over the report to the GAC
telling them it is in there. But, I thought I would send an example of using a different approach for the letter for the following reasons:</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">
<ol>
<li style="list-style-type:"1. ""><span>After reviewing the documentation, I realized that a number of the Cs and SGs in their statements were responding to an original report (that is not attached to the C and SG statements). That original report had language
that was considered a “compromise proposal” The compromise proposal was ultimately not accepted and is not described in detail in the C and SG statements or really in the CCOICI Recommendation Report. But because the C and SG statements were responding to
the compromise proposal as part of the original report, there is a lot of language in the C and SG statements about that compromise language. If we just referred the GAC to the statements, the would not have the context of what this compromise proposal was
and therefore it would be very confusing to the GAC members. Therefore, in my summaries, I did not include the C and SG views on the compromise proposal (since that no longer exists).</span>
<div style="list-style-type:"2. ""><span><br>
</span></div>
</li><li style="list-style-type:"2. ""><span>Some of the C and SG statements (and I am not making a judgment here) are written in a semi-aggressive and combative tone in how they address other Cs and SGs. Statements like “I find it ironic that this particular
C supports X, when it supports Y in some other situation.” It is not related to the ultimate debate for this issue and frankly to just send it over without explanation to me seems like airing dirty laundry to persons outside of the GNSO. So, in the summaries
I removed that language.</span>
<div style="list-style-type:"3. ""><span><br>
</span></div>
</li><li style="list-style-type:"3. ""><span>The C and SG statements in the Annex of the report are in no particular order. They are not grouped in any logical way and I thought grouping them into 2 categories, statements in support of the current exemption,
and statements opposed to the current exemption, would make for an easier review.</span>
<div style="list-style-type:"4. ";font-size:inherit"><span style="font-size:inherit"><br>
</span></div>
</li><li style="list-style-type:"4. ";font-size:inherit"><span style="font-size:inherit">All of the language I used in the “summary” of the C and SG positions are direct quotes and not my own language because I recognize the importance of keeping that language
in place and I did not want to paraphrase anyone’s opinions.</span></li></ol>
</div>
<div id="m_-1002810937845833698ms-outlook-mobile-signature">
<div dir="ltr"><br>
</div>
<div dir="ltr">If the Council wants to take the summaries out the of the letter, that is the Council’s prerogative, and it should do what it wants. But in light of the view that the GAC wanted the GNSO Council to explain the different positions (to understand
why the GNSO did not get consensus), and the fact that when the GAC sends us talking points and other documents they: (a) are well organized, (b) provide rationale, and (c) rarely just say “look at what we said before” (even if they are just stating what the
said before), we could reciprocate and provide a helpful document back. </div>
<div dir="ltr"><br>
</div>
<div dir="ltr">Again, I understand it is more than what was asked for but it is easy enough to pear down should you wish to do so.</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">
<div dir="ltr">Sincerely,</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">Jeffrey J. Neuman</div>
<div dir="ltr">Founder & CEO</div>
<div dir="ltr">JJN Solutions, LLC</div>
<div dir="ltr">+1.202.549.5079</div>
<div dir="ltr"><a href="mailto:Jeff@jjnsolutions.com" target="_blank">Jeff@jjnsolutions.com</a></div>
</div>
</div>
<div id="m_-1002810937845833698mail-editor-reference-message-container">
<hr style="display:inline-block;width:98%">
<div id="m_-1002810937845833698divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif"><b>From:</b> Jeff Neuman <Jeff@JJNSolutions.com><br>
<b>Sent:</b> Wednesday, March 20, 2024 10:39 AM<br>
<b>To:</b> <a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a> <<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a>><br>
<b>Subject:</b> Proposed Letter to GAC re: SOI
<div> </div>
</font></div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
All,</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Please find at the link below a proposed <a href="https://docs.google.com/document/d/145cXGFHFVChWZSd8-tL1ce5xNRafLwYHfIe4PImN3IQ/edit?usp=sharing" id="m_-1002810937845833698LPlnk" title="https://docs.google.com/document/d/145cXGFHFVChWZSd8-tL1ce5xNRafLwYHfIe4PImN3IQ/edit?usp=sharing" target="_blank">
first draft of a letter to the GAC</a> as discussed during the last GNSO Council meeting. The letter attempts to summarize the positions of each SG/C on the professional ethics exemption to the SOI as expressed in Annex A of the CCOICI's Task Force's Recommendations
Report. </div>
<div>
<div id="m_-1002810937845833698LPBorder_GTaHR0cHM6Ly9kb2NzLmdvb2dsZS5jb20vZG9jdW1lbnQvZC8xNDVjWEdGSEZWQ2hXWlNkOC10TDFjZTV4TlJhZkx3WUhmSWU0UEltTjNJUS9lZGl0P3VzcD1zaGFyaW5n" style="width:100%;margin-top:16px;margin-bottom:16px;max-width:800px;min-width:424px">
<table id="m_-1002810937845833698LPContainer571415" role="presentation" style="padding:12px 36px 12px 12px;width:100%;border-width:1px;border-style:solid;border-color:rgb(200,200,200);border-radius:2px">
<tbody>
<tr valign="top" style="border-spacing:0px">
<td>
<div id="m_-1002810937845833698LPImageContainer571415" style="margin-right:12px;height:126px;overflow:hidden;width:240px">
<a id="m_-1002810937845833698LPImageAnchor571415" href="https://docs.google.com/document/d/145cXGFHFVChWZSd8-tL1ce5xNRafLwYHfIe4PImN3IQ/edit?usp=sharing" target="_blank"><img id="m_-1002810937845833698LPThumbnailImageId571415" alt="" height="126" width="240" src="https://lh7-us.googleusercontent.com/docs/AHkbwyJh3R_SqwlFmn3nMXJV2fTpwVSmVqNAntfMpV-xoUjEK_AxLrIdYwRTf5NAE_KB3TC2B2HRMKJxwyc3lCfkgBLf7SAhiu2fkhpYX9CoL3ZQ0LQ=w1200-h630-p" style="display: block;"></a></div>
</td>
<td style="width:100%">
<div id="m_-1002810937845833698LPTitle571415" style="font-size:21px;font-weight:300;margin-right:8px;font-family:wf_segoe-ui_light,"Segoe UI Light","Segoe WP Light","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif;margin-bottom:12px">
<a id="m_-1002810937845833698LPUrlAnchor571415" href="https://docs.google.com/document/d/145cXGFHFVChWZSd8-tL1ce5xNRafLwYHfIe4PImN3IQ/edit?usp=sharing" style="text-decoration:none" target="_blank">SOI Letter from GNSO Council</a></div>
<div id="m_-1002810937845833698LPMetadata571415" style="font-size:14px;font-weight:400;font-family:wf_segoe-ui_normal,"Segoe UI","Segoe WP",Tahoma,Arial,sans-serif;color:rgb(166,166,166)">
<a href="http://docs.google.com" target="_blank">docs.google.com</a></div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Yes, we can just send a letter attaching word for word what Annex A states (and I do attach it to this letter). However, I believe I have accurately summarized those 7 pages or so into just over 2 pages. I essentially use mostly quotes from the actual positions
taken, but eliminated some of the examples and restatements in those positions. I believe the summaries, however, will be much more easily digestible by those that may not have the time to read every word.</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
This is just a first draft and I hand it over to the Council to take it from here if it finds this helpful. [The Google Doc itself has a link to the Recommendations Report]</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Sincerely,</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Jeff Neuman</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
GNSO Liaison to GAC</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Google Link: <a href="https://docs.google.com/document/d/145cXGFHFVChWZSd8-tL1ce5xNRafLwYHfIe4PImN3IQ/edit?usp=sharing" id="m_-1002810937845833698OWA0ed9cf7a-dd38-3e47-81a2-7787ba51e896" target="_blank">
https://docs.google.com/document/d/145cXGFHFVChWZSd8-tL1ce5xNRafLwYHfIe4PImN3IQ/edit?usp=sharing</a></div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div id="m_-1002810937845833698Signature">
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<img src="cid:ii_18e63de693d21e4fd771" style="max-width: 429px;"></div>
</div>
</div>
</div>
</div>
_______________________________________________<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" rel="noreferrer" 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" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" 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.</blockquote></div>