<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.im
{mso-style-name:im;}
span.EmailStyle18
{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">Greg<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">You are just wrong here. The IETF is the source or origin of the root registries for names, numbers and protocols by virtue of its protocol design/ standards
development work. Neither ICANN, nor PTI nor any future IFO is the source or origin of the IANA functions. They are but operators or implementors of those functions.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Anyway it is not your call; no one in the CWG, no one in the CRISP team, and no one in the protocols community have advocated or accepted your approach. As far
as I can tell you made this change unilaterally. Please change it.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><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"> cwg-stewardship-bounces@icann.org [mailto:cwg-stewardship-bounces@icann.org]
<b>On Behalf Of </b>Greg Shatan<br>
<b>Sent:</b> Wednesday, June 10, 2015 3:06 PM<br>
<b>To:</b> manning<br>
<b>Cc:</b> cwg-stewardship@icann.org IANA<br>
<b>Subject:</b> Re: [CWG-Stewardship] drift in v5<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">ICANN is an appropriate owner of the IANA trademarks. PTI is also an appropriate owner of the IANA trademarks. The IETF Trust does not appear to be an appropriate owner of the IANA trademarks.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana",sans-serif">A trademark is an indicator of source or origin. The owner of a trademark should be the ultimate source of the goods and services offered under that trademark. In the most straightforward
case, the trademark owner offers those goods and services themselves or through a subsidiary. The trademark owner can license the mark to third parties to offer goods and services under the mark; but, consistent with their status as the ultimate source, the
trademark owner is required by law to exercise continuing quality controls over the goods and services offered by the licensee
<u>and</u> the use of the trademark by the licensee. A trademark owner cannot merely "hold the asset" as CRISP proposed. </span><span style="font-size:9.5pt;font-family:"Verdana",sans-serif">Ownership of a trademark fundamentally involves being the “source
or origin” of the goods and services and fulfilling the “quality control” oversight role, among other things. </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana",sans-serif">Quality control generally involves approvals by the licensor of any potential new products or services, and approvals of any changes in products or services (what they are, how they are offered,
methods and processes, etc.), as well as ongoing monitoring of quality. The benchmark typically is that licensee's level of quality should be at least as high as the goods and services offered by the licensor (i.e., the owner of the mark and the ultimate
source/origin of the goods/services). This is all set forth in a trademark license between the licensee ans licensor. </span><span style="font-size:9.5pt;font-family:"Verdana",sans-serif">If a trademark license has no quality control provisions, or the quality
control provisions are not adequate or not adequately exercised, the license may be deemed a “naked license,” exposing the trademark to the risk of abandonment (loss of validity as a trademark, and loss of the right to claim ownership and usage rights of the
mark). When a licensee uses a trademark, all goodwill (brand reputation) goes to the owner, not the licensee. The owner is the holder of that goodwill.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana",sans-serif">I don't see how the IETF Trust makes legal sense as the owner of the IANA Trademarks. The IETF Trust is not and does not intend to be the ultimate source and origin of IANA services. Unlike
copyrights and patents, trademarks can't be owned by administrators; they need to be owned by the source of the services. Further, the IETF Trust is clearly not granting ICANN the right to provide the IANA Services, so it is even more inappropriate for the
IETF Trust to be the owner of the mark associated with those services.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana",sans-serif">An acceptable alternative may be to have PTI, rather than ICANN, own the IANA trademarks. This is actually a simpler solution and is consistent with trademark law and practice. This also
contributes to separability, since all of the IFO-related assets would be in a single entity.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto"><span style="font-size:9.5pt;font-family:"Verdana",sans-serif">If we assume for a moment that the IETF Trust were to own the IANA trademarks, significant issues arise.</span><span style="font-size:9.5pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"><span style="font-size:9.5pt;font-family:"Verdana",sans-serif"> </span><span style="font-size:9.5pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"><span style="font-size:9.5pt;font-family:"Verdana",sans-serif">In a trademark license, the IETF Trust, as licensor, would have the power to terminate the license according to its terms (e.g., for material
breach of the agreement, misuse of the trademark, etc.) or to decide not to renew the license, in which case ICANN would no longer have the right to use the IANA trademark in the provision of services. It would be inappropriate for the IETF Trust to have
this power, without accountability to and oversight by the names and numbers communities. A mechanism would need to built for that. </span><span style="font-size:9.5pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"><span style="font-size:9.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"><span style="font-family:"Verdana",sans-serif">Quality control presents another challenge. </span><span style="font-size:9.5pt;font-family:"Verdana",sans-serif">In virtually all circumstances, a licensor
exercises these quality control obligations through an employee or employees knowledgeable and capable of exercising quality control over the licensee and its services. .It may also be appropriate for the operational communities to be involved in quality
control and other aspects of the license as well, especially since quality control and trademark usage guidelines can be changed from time to time, typically at the licensor’s discretion, and since the IETF is not in a position to exercise quality control
in the names and numbers space. This may require amendment of the IETF Trust Agreement, as well as the drafting of a somewhat unusual trademark license.</span><span style="font-size:9.5pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"><span style="font-size:9.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"><span style="font-size:9.5pt;font-family:"Verdana",sans-serif">Furthermore, the IETF Trust would also be responsible for policing and enforcement of the trademark against third parties and for maintenance
of trademark registrations. </span><span style="font-size:9.5pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"><span style="font-size:9.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"><span style="font-size:9.5pt;font-family:"Verdana",sans-serif">It is not clear how the IETF Trust intends to carry out any of these roles.</span><span style="font-size:9.5pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"><span style="font-size:9.5pt;font-family:"Verdana",sans-serif"> </span><span style="font-size:9.5pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"><span style="font-size:9.5pt;font-family:"Verdana",sans-serif">Also, for the IETF Trust to become the owner of the IANA trademark, ICANN would need to assign all of its right, title and interest in and to
the IANA trademark to the IETF Trust, along with all goodwill relating to the mark (typically, in exchange for good and valuable consideration). This may require a valuation of the IANA trademark and its associated goodwill, which in turn may have tax or
other financial consequences for one or both parties. </span><span style="font-size:9.5pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"><span style="font-size:9.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"><span style="font-size:9.5pt;font-family:"Verdana",sans-serif">Finally, the IETF Trust, as such, may not be capable of owning the IANA Trademark, since the IETF Trust does not appear to be a “legal entity.”
If this is correct, the Trustees (in their role as Trustees) are the collective owners of the IANA Trademark (in trust for the IETF, as Beneficiaries of the IETF Trust), and would need to enter into the trademark license (again, in their role as Trustees of
the Trust). This appears to be consistent with Section 9.5 of the Amended and Restated Trust Agreement and the ownership of the IETF trademarks (which are owned by “The Trustees of the IETF Trust”) in the USPTO database. (Oddly, this is inconsistent with
the IETF General Trademark License (on the IETF Trust website) which states that the IETF Trust is the licensor of the IETF marks, and which also lacks appropriate quality control provisions.) </span><span style="font-size:9.5pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"><span style="font-size:9.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"><span style="font-size:9.5pt;font-family:"Verdana",sans-serif">Greg Shatan</span><span style="font-size:9.5pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"><span style="font-size:9.5pt"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"><span style="font-size:9.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"><span style="font-size:9.5pt"> <o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Wed, Jun 10, 2015 at 3:18 AM, manning <<a href="mailto:bmanning@karoshi.com" target="_blank">bmanning@karoshi.com</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" style="margin-bottom:12.0pt">Missed the attachment… which now is attached!<br>
<br>
<br>
<span class="im">manning</span><br>
<span class="im"><a href="mailto:bmanning@karoshi.com">bmanning@karoshi.com</a></span><br>
<span class="im">PO Box 12317</span><br>
<span class="im">Marina del Rey, CA 90295</span><br>
<span class="im"><a href="tel:310.322.8102">310.322.8102</a></span><br>
<br>
<br>
<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">On 10June2015Wednesday, at 0:12, manning <<a href="mailto:bmanning@karoshi.com">bmanning@karoshi.com</a>> wrote:<br>
<br>
><br>
> On 19 May 2015, the number community provided specific feedback regarding the need for alignment on the IETF trademark and domain (see attached email from Izumi to the CWG call for comments).<br>
><br>
> Did you notice that the most recent draft (v5) for discussion that came out yesterday morning specifically moves farther away from this direction, leaving these marks in ICANN rather than moving them to the IETF Trust?<br>
><br>
> CWG email re new draft - -<<a href="http://mm.icann.org/pipermail/cwg-stewardship/2015-June/003650.html" target="_blank">http://mm.icann.org/pipermail/cwg-stewardship/2015-June/003650.html</a>><br>
> Draft Document - <<a href="http://mm.icann.org/pipermail/cwg-stewardship/attachments/20150609/aea1179e/FinalTransitionProposal_v5-Redline-commentsandeditsfordiscussion-0001.docx" target="_blank">http://mm.icann.org/pipermail/cwg-stewardship/attachments/20150609/aea1179e/FinalTransitionProposal_v5-Redline-commentsandeditsfordiscussion-0001.docx</a>><br>
><br>
> Proposed text in most recent document -<br>
><br>
>> " ICANN grants to PTI an exclusive, royalty-free, fully-paid, worldwide license to use the IANA trademark and all related trademarks, and all applications and registrations therefor, for use in connection with PTI’s activities under the ICANN-PTI Contract.
“<br>
><br>
> this moves the draft farther away from the received comments, and would this make the ICG’s job of aligning the various proposals from the affected parties into a cohesive plan even more difficult?<br>
><br>
> It might be premature to go to BA with this as an accepted direction, without concurrence from the affected parties.<br>
><br>
><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">310.322.8102</a><br>
><br>
><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" target="_blank">
https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><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>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>