<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I mean neutral with respect to a specific IFO. I don’t mean neutral wrt the identity of the IANA.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">This theoretical debate is really pointless and begs the question: what is accomplished by keeping it in ICANN? We already know what is impeded (separability)
<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></a></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Greg Shatan [mailto:gregshatanipc@gmail.com]
<br>
<b>Sent:</b> Sunday, June 21, 2015 11:07 AM<br>
<b>To:</b> Milton L Mueller<br>
<b>Cc:</b> avri@acm.org; cwg-stewardship@icann.org<br>
<b>Subject:</b> Re: [CWG-Stewardship] ICG request concerning IANA trademark and iana.org domain name<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana",sans-serif">A neutral repository _might_ be appropriate for copyrights or patents; it's not appropriate for a trademark, which by definition is not "neutral." It represents the entity from which the services
are provided. Even when used by a licensee, the owner/licensor is considered to be the origin of the licensee's goods and services (thus the requirement of active approval and quality control of a licensee's processes and output, as well as the use of their
mark).<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana",sans-serif">I'll stick with my earlier suggestion that a group should collaborate to develop a common understanding of the facts, rather than cite certain facts for the purpose of advocacy. I'd also like
to identify issues and work together to resolve them, rather than try work through this solely in advocacy mode.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana",sans-serif">It was in that spirit that I stated that we do not know whether the IETF Trust has the ability to take on the duties of a trademark owner. I did not assert that they lacked that capacity,
only that it is an unknown. That said, we cannot rely on an unknown. (I would also note that the IETF Trust is not the IETF; rather it is a trust set up for the benefit of the IETF. To the extent that the Trust is not seen as a legal entity, the trustees
(not IETF) would be seen as the owner of the trust's assets.)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana",sans-serif">I think I've already responded to the other point here (recognizing that the email was a response to Avri), so I'll stop here.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana",sans-serif">Greg<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Sun, Jun 21, 2015 at 10:54 AM, Milton L Mueller <<a href="mailto:mueller@syr.edu" target="_blank">mueller@syr.edu</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">> -----Original Message-----<br>
><br>
> Milton, since you are insisting so much from a Names perspective that we<br>
> agree to transfer this from ICANN to the IETT Trust, I would like to<br>
> understand what advantage you see for the Names commuity in this from<br>
> the CWG perspective. I understand why you might take the position you do<br>
<br>
That's a fair request and a fairly easy one to answer. In two words the answer is 'enhanced separability.' I've said this before so perhaps you need a better explanation.<br>
<br>
The mixture of policy making and implementation functions within one names-centric organization (ICANN) has been recognized as problematic. One of the key principles underlying the current reforms is that the IFO for names should be separate from the policy
maker, and further that the current IFO should not have a permanent monopoly. We should be able to switch to a new names IFO if justified. And numbers and protocols already have this arrangement. If you want the capacity to switch, then the current IFO cannot
control or own the IPR associated with IANA; they are users of the IPR not its owners. That, I suggest, is the correct model for the names community.<br>
<br>
If we want to consistently implement the basic model that the Internet community as a whole recognizes as proper (RFC 7500) we cannot have the names-related policy making entity - which is also an IFO for all 3 communities at the moment - hold the trademarks
that need to be used by all three communities and which may need to be used by different IFOs. The IETF trust is a neutral repository for this IPR that allows the rights to be assigned to any IFO as needed.<br>
<br>
> Also I think you misinterpret the IANAPLAN position. They say they are<br>
> willing. They do not request the move.<br>
<br>
'Willingness' means that their proposal is compatible with the numbers proposal. CWG's is not. There's no way around the fact that CWG names has worked without regard to what the other two communities proposed, and that its proposal is out of step. That by
itself does not mean it's wrong, but it does suggest that we _first_ need to think of changing what randomly made its way into our proposal rather than forcing two other communities to change. No one has advanced a good reason why a names community entity
should control it all. The idea that IETF Trust cannot defend or monitor the trademark is a mere assertion for which there is no concrete evidence, and flies in the face of the fact that the source and origin of the IANA registries is the IETF, not ICANN.<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><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" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>