<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">The <a href="http://iana.org">iana.org</a> registration dates back to 1996. A spot check confirms that "iana" is available in certain other delegations. (I guess the string was never put on the reserved list.) Strings with iana plus other characters were also available.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">It's an issue in the sense that third parties could acquire the string in other TLDs, which could be used for various purposes (including fan sites, I guess). This could lead to enforcement concerns (a discussion of which is not necessary for current purposes). It should not raise operational issues (unless a third party engaged in some unsavory behavior).</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><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jun 20, 2015 at 7:13 PM, manning <span dir="ltr"><<a href="mailto:bmanning@karoshi.com" target="_blank">bmanning@karoshi.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">A couple of thoughts. I don;t think that someone “insisting” they have an active voice has always been a precondition for being selected.<br>
Second, there is or was a choice made about two decades ago (looking backwards) to reserve the string iana.[com,net,org].<br>
I am not at all sure that the string “iana” is protected in _ALL_ other delegations in the DNS. Or even could be. Is that going to be an<br>
issue?<br>
<span class="HOEnZb"><font color="#888888"><br>
manning<br>
<a href="mailto:bmanning@karoshi.com">bmanning@karoshi.com</a><br>
PO Box 12317<br>
Marina del Rey, CA 90295<br>
<a href="tel:310.322.8102" value="+13103228102">310.322.8102</a><br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
<br>
On 20June2015Saturday, at 10:47, Milton L Mueller <<a href="mailto:mueller@syr.edu">mueller@syr.edu</a>> wrote:<br>
<br>
> Greg:<br>
> Here I am speaking as a CWG participant and not as an ICG member.<br>
> Let me call to your attention that the ICG letter asks CWG to “review the proposals from the protocol parameters and numbers communities” and then to “determine if it can adopt an approach taken by those communities.”<br>
><br>
> I suggest that we start with that. Is there anything preventing the CWG from quickly and easily resolving the incompatibility by simply going along with the proposal to turn the trademarks over to the IETF Trust as requested? Frankly I don’t think there is. No one has argued that there is any problem or harm to the names community hat would come from adhering to the CRISP proposal.<br>
><br>
> I was interested in this part of your response:<br>
><br>
> I also think we as a community need to decide what our desired outcome would be (whatever the facts are, and whatever the law may be (as long we recognize that a trademark identifies where the goods and services come from)).<br>
><br>
> MM: This is a discussion that never happened the first time around. No one has ever explained how PTI or ICANN holding the trademarks accomplishes anything of value for the names community. On the contrary, it was pointed out by several people that the principle of separability is violated by having a specific IFO hold the trademark.<br>
><br>
> I suggest we put together an ad hoc team to deal with this.<br>
><br>
> MM: I would insist on being on this team.<br>
><br>
</div></div><div class="HOEnZb"><div class="h5">> _______________________________________________<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>
</div></div></blockquote></div><br></div>