<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Replies inline.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Greg</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jul 28, 2016 at 4:42 PM, Seun Ojedeji <span dir="ltr"><<a href="mailto:seun.ojedeji@gmail.com" target="_blank">seun.ojedeji@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Hello,</p>
<p dir="ltr">First apologies again for missing the meeting today as I expect what I am about to say must have been discussed at length. I just had a brief look on the community agreement and I was like wow! I cannot help but wonder whether we are still talking about IANA IPR or the actual ownership of the IANA functions.</p>
<p dir="ltr">My first general impression about this is that i think this is too complicated and too unnecessarily detailed and cumbersome. </p></blockquote><div><div class="gmail_default" style="font-family:verdana,sans-serif">Which parts have too much detail? Detail is helpful in avoiding misinterpretation. Much of the detail (and cumbersomeness) is around escalation procedures, which are frankly designed to protect the interests of the Trust in most instances. </div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">There are quite a number of segments in the agreement that makes it clear that the CCG is in control while the trust is just an implementation medium; </p></blockquote><div><div class="gmail_default" style="font-family:verdana,sans-serif">I really don't think this is an accurate characterization of the agreements. The Trust initiates virtually all activities. The exceptions are quite limited (either around the transfer to a new IANA operator or in the particular case where one or more communities would like a trademark registered in a different jurisdiction (or potentially, a domain name registered in a different TLD). The CCG's approval role is not complex and is required to be reasonable (ie, not at the CCG's sole discretion).</div><br></div><div> I liken the trust role to that of the sole member. One of such sections is quoted below:</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p dir="ltr">"Accordingly, the IETF Trust agrees, as set forth below, to seek the advice and *consent* of the CCG with respect to *all* matters concerning the IANA Intellectual Property,..."</p>
<p dir="ltr">Will I have no problem with notification to the operational communities, the above implies requirement for approval of CCG for everything the IETF does relating to IANA IPR and domain. </p></blockquote><div><div class="gmail_default" style="font-family:verdana,sans-serif">Here I would note that these agreements are still a work in progress. If something is imperfect, that is something we'll work out. The first draft tilted strongly in the other direction -- there were no consents or approvals whatsoever, which did not reflect what was in the Principal Terms document.<span style="font-family:arial,sans-serif"> </span></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">This IMO is an overkill and is not acceptable, not just because i feel it's technical wrong to control a Trust in such manner but because it's improper to put such power in the hands of volunteer community (Infact it's in the hand of 1 person from each community since the agreement suggests that the trust should not question communication from respective Co-Chairs)</p></blockquote><div class="gmail_default" style="font-family:verdana,sans-serif">That particular feature (regarding communications from the co-Chairs) was in the first draft; (we did change this to require the Chair(s) to represent that they were speaking on behalf of their community). In any event, I think it is exceptionally unlikely that the one or more Chairs will go rogue; they would be criticized (and probably removed) by their community. At the same time, there need to be relatively streamlined communications, so the right balance needs to be achieved.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">I don't see the objection to "volunteer communities" being involved -- that is the basis of the multistakeholder process. Even many who are here in their professional capacity are to a greater or lesser extent volunteers. In an important sense, the IETF are all volunteers, and I doubt you object to their oversight of the IETF Trust.</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p dir="ltr">I thought the CCG was going to act in a review mode; while providing advice to their respective communities(or directly to the trust) whenever issues are identified but this is way beyond the scope. I believe any official communication to the Trust that are critical MUST always come from executives of the respective communities and NOT from CCG. Afterall the executives will be the signatories to the agreement.</p></blockquote><div class="gmail_default" style="font-family:verdana,sans-serif">This is not what was envisioned and it's entirely consistent with the way other representative groups in this space work. "Executives" (and I'm not sure who that would even be in some communities or parts thereof) are free to be part of the CCG.</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p dir="ltr">Overall i am quite uncomfortable with the community agreement and I hope that this issue would be addressed amicably. </p></blockquote><div><div class="gmail_default" style="font-family:verdana,sans-serif">I don't think addressing issues "amicably" is in any way at odds with having a robust agreement. I do hope that the differences in how the agreement works will be addressed amicably, and I have every confidence they will be.</div></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">As I have always said, the protocol is the source of all these and I don't see why we are overloading this particular part of the transition unnecessarily.</p>
<p dir="ltr">Regards<br>
Sent from my LG G4<br>
Kindly excuse brevity and typos</p>
<div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On 28 Jul 2016 11:29 a.m., "Jonathan Robinson" <<a href="mailto:jrobinson@afilias.info" target="_blank">jrobinson@afilias.info</a>> wrote:<br type="attribution"></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div lang="EN-IE" link="blue" vlink="purple"><div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">All,<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Please see attached for the revised drafts of the </span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">IPR License and the Community Agreement.<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Jonathan</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><div><div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Hofheimer, Joshua T. [mailto:<a href="mailto:jhofheimer@sidley.com" target="_blank">jhofheimer@sidley.com</a>] <br><b>Sent:</b> 27 July 2016 01:03<br><b>To:</b> Client Committee <<a href="mailto:cwg-client@icann.org" target="_blank">cwg-client@icann.org</a>><br><b>Subject:</b> [client com] IANA IPR License & Community Agreement Template<u></u><u></u></span></p></div></div><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Greg and all,<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Attached are the final CWG revised drafts of the IPR License and the Community Agreement, clean and marked against the originals. Per my prior note Greg, are you going to post, or do you want Sidley to do so.<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Cheers,<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Josh<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><div><p class="MsoNormal"><i><span lang="EN-US" style="font-size:9.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Joshua Hofheimer<u></u><u></u></span></i></p><p class="MsoNormal"><i><span lang="EN-US" style="font-size:9.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Sidley Austin LLP<u></u><u></u></span></i></p><p class="MsoNormal"><i><span lang="EN-US" style="font-size:9.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><a href="mailto:jhofheimer@sidley.com" target="_blank">jhofheimer@sidley.com</a><u></u><u></u></span></i></p><p class="MsoNormal"><i><span lang="EN-US" style="font-size:9.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><a href="tel:%28213%29%20896-6061" value="+12138966061" target="_blank">(213) 896-6061</a> (LA direct)<u></u><u></u></span></i></p><p class="MsoNormal"><i><span lang="EN-US" style="font-size:9.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><a href="tel:%28650%29%20565-7561" value="+16505657561" target="_blank">(650) 565-7561</a> (Palo Alto direct)<u></u><u></u></span></i></p><p class="MsoNormal"><i><span lang="EN-US" style="font-size:9.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><a href="tel:%28323%29%20708-2405" value="+13237082405" target="_blank">(323) 708-2405</a> (cell)<u></u><u></u></span></i></p></div><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><p><span lang="EN-US"> <u></u><u></u></span></p><p><span lang="EN-US">****************************************************************************************************<br>This e-mail is sent by a law firm and may contain information that is privileged or confidential.<br>If you are not the intended recipient, please delete the e-mail and any attachments and notify us<br>immediately.<br><br>****************************************************************************************************<u></u><u></u></span></p></div></div><br></div></div><span class="">_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a href="mailto:CWG-Stewardship@icann.org" target="_blank">CWG-Stewardship@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><br>
<br></span></blockquote></div></div>
<br>_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><br>
<br></blockquote></div><br></div></div>