<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">I wanted to note some statements which appear to be factually inaccurate.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default"><font face="verdana, sans-serif">In "D," you state that the IETF Trust "is for the public benefit and the global internet society." I do not see that in the trust document. <b>The sole Beneficiary of the IETF Trust is the IETF</b> (see Article IV of the Trust Agreement). in other words, the Trust is for the benefit of the IETF. This cannot be ignored. </font></div><div class="gmail_default"><font face="verdana, sans-serif"><br></font></div><div class="gmail_default"><font face="verdana, sans-serif">The Purpose of the Trust is "the advancement of education and public interest by acquiring, maintaining and licensing certain existing and future intellectual property and other property used in c</font><span style="font-family:verdana,sans-serif">onnection with the Internet standards process and its administration, for the advancement of the science and technology associated with the Internet and related technology." Although this goes beyond benefiting the IETF, this does not support the statement in D either. </span></div><div class="gmail_default"><span style="font-family:verdana,sans-serif"><br></span></div><div class="gmail_default"><span style="font-family:verdana,sans-serif">It should also be noted that all the Trustees of the IETF Trust are members of the IETF Admin Committee. As such, it's clear that this is an IETF-centric trust, which is not consistent with owning an asset that is used in connection with the needs of all three communities.</span></div><div class="gmail_default"><span style="font-family:verdana,sans-serif"><br></span></div><div class="gmail_default"><span style="font-family:verdana,sans-serif">In "C," you state that "</span><font face="verdana, sans-serif">an underlying motivation was that the IPR should be held somehow “in trust” for future use by the relevant users of that IPR." This ignores the essential nature of what trademarks are. A trademark cannot be held in a a neutral manner "in trust" (although it can be owned by a Trust). A trademark is an identity, which must be actively assumed. A brand owner is the proprietor of the trademark and the businesses identified by the trademark, and needs to assume the obligations that come with donning that identity. </font></div><div class="gmail_default"><font face="verdana, sans-serif"><br></font></div><div class="gmail_default"><font face="verdana, sans-serif">For example, if you buy the Ralph Lauren trademark, then (for business purposes), you become Ralph Lauren. (He may be able sell clothes, etc. under the name Ralph Lipschitz, but not Ralph Lauren.) Here, if the IETF Trust takes over the INTERNET ASSIGNED NUMBERS AUTHORITY and IANA trademark d the trademarks transferred to the IETF Trust, <b>the IETF Trust becomes the INTERNET ASSIGNED NUMBERS AUTHORITY</b>. The IETF Trust is ultimately responsible for monitoring and assuring the quality of the work product and services of any licensee using the brand (currently ICANN). ICANN is then a mere licensee, providing services by permission of the IETF Trust under the IANA brand, which is an IETF Trust brand (just like Vaseline is a Unilever brand). By no means is ICANN the Internet Assigned Numbers Authority anymore.</font></div><div class="gmail_default"><font face="verdana, sans-serif"><br></font></div><div class="gmail_default"><font face="verdana, sans-serif">Second, you do not state who the "relevant users" of the IPR are. Currently, the only entity using the IANA and INTERNET ASSIGNED NUMBERS AUTHORITY trademarks as a trademark is ICANN. (Referring to IANA in an RFC is using it as a name ("nominative use") not using as a trademark to brand their work product.) I suppose the "future users" would be any replacements for ICANN -- but then it is not really being held "in trust" by the IETF Trust; the IETF Trust would continue to be the IANA brand owner and the "future users" would continue to be mere licensees, operating under the oversight and control of the IETF Trust, which in turn is accountable only to the IETF.</font></div><div class="gmail_default"><font face="verdana, sans-serif"><br></font></div><div class="gmail_default"><font face="verdana, sans-serif">Perhaps it's entirely acceptable to the CWG that the Internet Assigned Numbers Authority identity shift from ICANN to the IETF Trust, and that the IETF Trust becomes responsible for brand protection and quality control of all INTERNET ASSIGNED NUMBERS AUTHORITY and IANA brand services. Perhaps we have no choice but to find it acceptable, or to try to find ways to make it acceptable during the implementation phase (e.g., by overhauling the IETF Trust so it is an appropriate brand owner for this brand in which we have distinct interests) It certainly seems acceptable to the numbers and names community. But we should at least be accurate about what is happening.</font></div><div class="gmail_default"><font face="verdana, sans-serif"><br></font></div><div class="gmail_default"><font face="verdana, sans-serif">Greg</font></div><div class="gmail_default"><font face="verdana, sans-serif"><br></font></div><div class="gmail_default"><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 13, 2015 at 3:52 PM, Jonathan Robinson <span dir="ltr"><<a href="mailto:jrobinson@afilias.info" target="_blank">jrobinson@afilias.info</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-IE" link="#0563C1" vlink="#954F72"><div><p class="MsoNormal">All,<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Following the last CWG meeting, your co-chairs reached out to the chairs of the CRISP & IANAPLAN teams as well as the ICG chairs in order to discuss the overarching management of the IANA IPR issue. The purpose of the discussion was to focus, not on the substance of the issue, but rather to best understand the different backgrounds, the current status and the prospective routes forward, given where we are today.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">From the perspective of the co-chairs of the CWG, a number of key points emerge as follows:<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p>1.<span style="font-size:7.0pt;font-family:"Times New Roman",serif"> </span>There seemed to be an overarching sensitivity to where we ALL are in the process and the requirement to not let this IANA IPR issue derail us from a “programme management” perspective.<u></u><u></u></p><p>2.<span style="font-size:7.0pt;font-family:"Times New Roman",serif"> </span>A second overarching point, directly related to 1 above, is the desire (and effectively a requirement) not to do anything which will necessitate change any of the three RFP responses such that this change would require one or more of the three RFP respondents (names, numbers, protocols) to have to go back through their respective community processes with the associated risk of delaying the transition.<u></u><u></u></p><p>3.<span style="font-size:7.0pt;font-family:"Times New Roman",serif"> </span>Through the current public comment period on the ICG proposal, there is the opportunity (for the CWG) to comment on the ICG proposal, but subject to 1 & 2 above.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">We also sought to better understand the various tracks of work (including that of the CWG) which have seen us arrive at this point and some of the detail in that work. Key points from that include:<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p><u></u><span>A.<span style="font:7.0pt "Times New Roman""> </span></span><u></u>That there is a form of “backstop position” in the CRISP proposal that the IPR must not reside within the IFR in future. This underlying motivation derives from two points:<u></u><u></u></p><p style="margin-left:72.0pt"><u></u><span>a.<span style="font:7.0pt "Times New Roman""> </span></span><u></u>In order to facilitate a smooth potential future transition of the IANA function<u></u><u></u></p><p style="margin-left:72.0pt"><u></u><span>b.<span style="font:7.0pt "Times New Roman""> </span></span><u></u>To ensure that the IPR will be used in a non-discriminatory manner.<u></u><u></u></p><p><u></u><span>B.<span style="font:7.0pt "Times New Roman""> </span></span><u></u>An underlying motivation was that the IPR should be held somehow “in trust” for future use by the relevant users of that IPR<u></u><u></u></p><p><u></u><span>C.<span style="font:7.0pt "Times New Roman""> </span></span><u></u>That there seemed to be a strongly held view that the Sidley interpretation whereby ICANN could retain the IPR AND that this would be consistent with the CRISP proposal was not accurate. <br>The argument presented being that ICANN is in fact the IANA Functions Operator, at least in in the case of numbers.<u></u><u></u></p><p><u></u><span>D.<span style="font:7.0pt "Times New Roman""> </span></span><u></u>The IETF is willing to be the holder of the IPR in the IETF trust which is for the public benefit and the global internet society. Therefore no conflict is envisaged by having the IPR held within the IETF Trust.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Finally, we considered some next steps / actions as follows:<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p>-<span style="font-size:7.0pt;font-family:"Times New Roman",serif"> </span>That the same group agree to talk again in approximately one week<u></u><u></u></p><p>-<span style="font-size:7.0pt;font-family:"Times New Roman",serif"> </span>CRISP is likely to prepare and share some responses to the Sidley memo on IPR<u></u><u></u></p><p>-<span style="font-size:7.0pt;font-family:"Times New Roman",serif"> </span>We can expect to see some further detail / information on the IETF Trust<u></u><u></u></p><p>-<span style="font-size:7.0pt;font-family:"Times New Roman",serif"> </span>ICG & CRISP offers any knowledge, information and assistance that they can reasonably provide<u></u><u></u></p><p>-<span style="font-size:7.0pt;font-family:"Times New Roman",serif"> </span>A request for any guidance on timelines from the CWG<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">In summary, it seems that we (the CWG) need to separate our prospective contribution to implementation from any comment we may wish to make now – effectively to the ICG proposal. For now, we need to focus our attention on the ICG document and the urgent requirement is to consider whether or not the ICG proposal is consistent with the responses received and, if not, what comment we wish to submit. Moreover, to be mindful that any such comment must not require any of the three RFP responses to be referred back to the relevant responding community if we are to retain the current overarching timetable. Put simply, what can usefully be done now and what can usefully be done later during the implementation phase.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">For your reference, we have included some relevant extracts from the CRISP response, the ICG proposal and the Sidley memo which we have used in thinking about this issue.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Thank-you<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Jonathan & Lise<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><u></u> <u></u></p></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>