<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Steve,</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">The history you are recounting seems to be primarily the story of the IETF trademarks, not the IANA trademarks. This is based on my review of US Patent & Trademark Office records.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Specifically, it was the IETF trademarks that were originally applied for by CNRI. The IETF SECRETARIAT mark was applied for in 1999 by CNRI, and registered in 2000. The IETF and IETF Logo trademarks were applied for by CNRI in November 2005. On December 15, 2005, the IETF SECRETARIAT registration and the two IETF applications were assigned to the IETF Trust. (Assignment attached) The two applications subsequently registered in the name of the IETF Trust.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">The history of the IANA trademarks is quite different:</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default"><font face="verdana, sans-serif">USC applied to register two trademarks in 1997: IANA and INTERNET ASSIGNED NUMBERS AUTHORITY. These both registered in the name of USC in 1999. In 2000, USC and ICANN entered into a <span style="line-height:115%">“USC/ICANN Transition Agreement” in which</span><span style="line-height:115%"> USC
agreed to assign to ICANN the marks INTERNET ASSIGNED NUMBERS AUTHORITY, IANA and IANA (Logo form). USC also signed an assignment document, transferring to ICANN USC’s "entire right, title and interest” in
and to (i) Reg. No.
2,277,028 for IANA, (ii) Reg. No. 2,217978 for INTERNET ASSIGNED NUMBERS
AUTHORITY, and (iii) the common law trademark rights to the IANA Logo. (Assignment attached) ICANN filed its own applications for the IANA Logo (in 2001), INTERNET ASSIGNED NUMBERS AUTHORITY (in 2003) and IANA in 2007, all of which subsequently registered in the name of ICANN. (These newer registrations improved upon and replaced the original USC registrations.)</span></font></div><div class="gmail_default"><span style="line-height:115%"><font face="verdana, sans-serif"><br></font></span></div><div class="gmail_default" style=""><font face="verdana, sans-serif"><span style="line-height:115%">I see no evidence that CNRI or IETF ever had any ownership interest or other interest in the IANA marks, or that either entity engaged in any transaction with ICANN regarding the IANA marks. I find this very hard to reconcile with the claim that "</span><span style="line-height:16.8667px">The transfer of the IANA marks to ICANN was with the clear understanding these fundamentally belonged to the IETF.</span><span style="line-height:115%">" Perhaps you were thinking of the IETF marks?</span></font></div><div class="gmail_default" style=""><span style="line-height:115%"><font face="verdana, sans-serif"><br></font></span></div><div class="gmail_default" style=""><span style="line-height:16.8667px"><font face="verdana, sans-serif">Any help in clearing all this up would be most appreciated.</font></span></div><div class="gmail_default" style=""><span style="line-height:16.8667px"><font face="verdana, sans-serif"><br></font></span></div><div class="gmail_default" style=""><span style="line-height:16.8667px"><font face="verdana, sans-serif">Greg</font></span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jan 12, 2016 at 1:48 AM, Steve Crocker <span dir="ltr"><<a href="mailto:steve.crocker@icann.org" target="_blank">steve.crocker@icann.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Andrew,<br>
<br>
You’ve spoken too mildly. Setting up a lightweight trust that parallels the IETF Trust is indeed a small piece of work, but the direction of the proposal for a separate trust is implies a LOT of work, exploration of an unbounded and undefined set of issues, and an unclear but potentially substantial level of expenditure. So, your suggestion that expedient and workable should be given high value is indeed a strong point. But I will suggest the argument in favor of the IETF Trust is even stronger.<br>
<br>
The marks and domain names were transferred from the IETF to ICANN as part of the creation of the IETF Administrative Support Activity (IASA), in 2005. (I think I have the date correct.) Prior to that, the marks were held by the Corporation for National Research Initiatives (CNRI), Bob Kahn’s non-profit operation. There was a lengthy tussle between Bob Kahn and the IETF that lasted a few years. Bob had been providing the support for the IETF and had been controlling its funds. Eventually, Bob withdrew from providing these services and controlling the funds, and the IETF took control of its finances and its services. The transfer of the IANA marks to ICANN was with the clear understanding these fundamentally belonged to the IETF. In my view, it is entirely natural and appropriate for these marks to be placed in the IETF Trust and that arrangements for their continued use by ICANN in order to provide the IANA service is all that’s necessary.<br>
<span class="HOEnZb"><font color="#888888"><br>
Steve<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
<br>
On Jan 12, 2016, at 1:31 AM, Andrew Sullivan <<a href="mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a>> wrote:<br>
<br>
> Hi,<br>
><br>
> On Mon, Jan 11, 2016 at 01:56:41PM -0500, Greg Shatan wrote:<br>
><br>
>> But to my mind, it is expedient rather than preferable.<br>
><br>
> I won't speak for the IETF Trust, but speaking as a Trustee I can say<br>
> that _I_ think it is expedient rather than preferable, too. Given<br>
> that whatever we do has to be completely sewn up in time for a<br>
> transition in Q4 of 2016 (i.e. roughly 10 months from now), I think<br>
> that "expedient and workable" ought to be a high-value qualifying<br>
> criterion.<br>
><br>
>> Actually, I think it would be quite helpful. Furthermore, I don't think<br>
>> that there are significant economic or resource differences between working<br>
>> up an arrangement with the IETF and working up an arrangement for a new<br>
>> trust.<br>
><br>
> You are suggesting is that hammering out a new trust agreement among<br>
> three operational communities that will specify a new governance<br>
> structure, and then hammering out all the other issues that one needs<br>
> in an agreement, will take no more time than just doing the second of<br>
> those things. I would like to know why you think that. It's<br>
> certainly true that setting up a new trust is the work of an afternoon<br>
> for a competent lawyer. But I don't think that's the hard part here.<br>
> Given that we've had months to tackle this question and haven't yet<br>
> even agreed amongst ourselves what principles should apply, I cannot<br>
> say I'm optimistic that setting up a completely new legal entity in<br>
> collaboration with two other communities -- both of which have to go<br>
> through their own consensus processes in order to agree to do it --<br>
> will be the fast path.<br>
><br>
> Best regards,<br>
><br>
> A<br>
><br>
> --<br>
> Andrew Sullivan<br>
> <a href="mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a><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>
_______________________________________________<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>
</div></div></blockquote></div><br></div>