<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=us-ascii">
<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;}
@font-face
{font-family:Garamond;
panose-1:2 2 4 4 3 3 1 1 8 3;}
/* 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.hoenzb
{mso-style-name:hoenzb;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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">Maarten,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The simple rationale for the numbers proposal, and the protocol community’s acceptance of it, was that both of them insist on having the right to switch IANA
functions operator at some time in the future. If the IANA trademarks and domains are “owned” by a single IFO we cannot have that separability. If we want the IFO to be able to change, then the trademarks and domains must not he owned by either ICANN (which
is the “owner’/controller of PTI) or any subsequent IFO. It’s that simple.<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">--MM<o:p></o:p></span></a></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></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>Maarten Simon<br>
<b>Sent:</b> Wednesday, June 10, 2015 4:22 PM<br>
<b>To:</b> Seun Ojedeji; Greg Shatan<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>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Next to Seun’s argument, I think the trademarks should remain with ICANN as it is ICANN that will grant PTI the right to operate the IANA functions through the
contract. It seems logical to me that ICANN only provides a license to PTI to use the trademarks through the same contract and not transfer the trademarks themselves.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">The further question is if in the case of a separation the assets will go from PTI to the new entity (probably in practise: yes) but in a legal sense I would assume
that PTI returns the assets to ICANN and that ICANN provide these to the new operator.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">From:
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Seun Ojedeji <</span><a href="mailto:seun.ojedeji@gmail.com"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">seun.ojedeji@gmail.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">><br>
<b>Date: </b>Wednesday 10 June 2015 22:05<br>
<b>To: </b>Greg Shatan <</span><a href="mailto:gregshatanipc@gmail.com"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">gregshatanipc@gmail.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">><br>
<b>Cc: </b>SIDN SIDN <</span><a href="mailto:maarten.simon@sidn.nl"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">maarten.simon@sidn.nl</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">>, "</span><a href="mailto:cwg-stewardship@icann.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">cwg-stewardship@icann.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">"
<</span><a href="mailto:cwg-stewardship@icann.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">cwg-stewardship@icann.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">><br>
<b>Subject: </b>Re: [CWG-Stewardship] drift in v5<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Hi Greg,<o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Perhaps its worth noting that the other 2 operational communities are still considering whether to contract directly with PTI as their
proposals currently indicates contracting with ICANN. So if for instance there is a need for numbers community to move its functions, it would be appropriate that the entity its contracting with provides access to the IANA trademarks accordingly.
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">As far as PTI is concerned at the moment, its separation mechanisms as proposed by CWG is largely based on the names community (with
the other 2 communities having optional liaison roles). Based on that, i don't see the other 2 communities agreeing to transfer the IANA transdemarks (which is for all 3 operational communities) to PTI whose accountability mechanism is largely names based.<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Regards<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">On Wed, Jun 10, 2015 at 8:52 PM, Greg Shatan <</span><a href="mailto:gregshatanipc@gmail.com" target="_blank"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">gregshatanipc@gmail.com</span></a><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">>
wrote:<o:p></o:p></span></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Verdana",sans-serif;color:black">Maarten,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Verdana",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Verdana",sans-serif;color:black">That is not my understanding of separation. If ICANN selects a new provider, that provider would take all of the assets of PTI (including the trademarks, under
this scenario), so it could provide the IANA services. PTI would then be wound down and ultimately dissolved by ICANN. Recall that PTI is a controlled entity of ICANN and would remain so throughout. In this case, the IANA operations are separated from PTI.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Verdana",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Verdana",sans-serif;color:black">If PTI is actually separated (spun out) from ICANN so that it is no longer under ICANN control, it would be done to further separate the IANA Functions from ICANN
and IANA would continue as a going concern (active business).<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Verdana",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Verdana",sans-serif;color:black">Under no circumstances does PTI become separated from ICANN without continuing to serve as the IANA operator, yet continue to hold IANA-related assets.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Verdana",sans-serif;color:#888888"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Verdana",sans-serif;color:#888888">Greg<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">On Wed, Jun 10, 2015 at 3:44 PM, Maarten Simon <</span><a href="mailto:maarten.simon@sidn.nl" target="_blank"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">maarten.simon@sidn.nl</span></a><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">>
wrote:<o:p></o:p></span></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Hi Greg,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">I would like to respond to your suggestion:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">'</span><span style="font-size:10.5pt;font-family:"Verdana",sans-serif;color:black">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><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">If PTI is separated, ICANN will select a new IANA provider. Am I correct that if the IANA trademarks rest with PTI, we will than have to rename the services after
the separation and they will not any longer be named the IANA services ?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">If that is correct, I rather keep the rights in ICANN.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Best,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Maarten<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">From:
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Greg Shatan <</span><a href="mailto:gregshatanipc@gmail.com" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">gregshatanipc@gmail.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">><br>
<b>Date: </b>Wednesday 10 June 2015 21:06<br>
<b>To: </b>manning <</span><a href="mailto:bmanning@karoshi.com" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">bmanning@karoshi.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">><br>
<b>Cc: </b>"</span><a href="mailto:cwg-stewardship@icann.org" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">cwg-stewardship@icann.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">" <</span><a href="mailto:cwg-stewardship@icann.org" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">cwg-stewardship@icann.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">><br>
<b>Subject: </b>Re: [CWG-Stewardship] drift in v5<o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Verdana",sans-serif;color:black">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><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Verdana",sans-serif;color:black">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;color:black">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><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Verdana",sans-serif;color:black">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;color:black">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><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Verdana",sans-serif;color:black">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><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Verdana",sans-serif;color:black">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><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto"><span style="font-size:9.5pt;font-family:"Verdana",sans-serif;color:black">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;color:black"><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;color:black"> </span><span style="font-size:9.5pt;color:black"><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;color:black">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;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"><span style="font-size:9.5pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"><span style="font-family:"Verdana",sans-serif;color:black">Quality control presents another challenge. </span><span style="font-size:9.5pt;font-family:"Verdana",sans-serif;color:black">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;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"><span style="font-size:9.5pt;color:black"><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;color:black">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;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"><span style="font-size:9.5pt;color:black"><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;color:black">It is not clear how the IETF Trust intends to carry out any of these roles.</span><span style="font-size:9.5pt;color:black"><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;color:black"> </span><span style="font-size:9.5pt;color:black"><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;color:black">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;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"><span style="font-size:9.5pt;color:black"><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;color:black">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;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"><span style="font-size:9.5pt;color:black"><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;color:black">Greg Shatan</span><span style="font-size:9.5pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"><span style="font-size:9.5pt;color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"><span style="font-size:9.5pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"><span style="font-size:9.5pt;color:black"> <o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">On Wed, Jun 10, 2015 at 3:18 AM, manning <</span><a href="mailto:bmanning@karoshi.com" target="_blank"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">bmanning@karoshi.com</span></a><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">>
wrote:<o:p></o:p></span></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Missed the attachment… which now is attached!<br>
<br>
<br>
manning<br>
</span><a href="mailto:bmanning@karoshi.com" target="_blank"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">bmanning@karoshi.com</span></a><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><br>
PO Box 12317<br>
Marina del Rey, CA 90295<br>
</span><a href="tel:310.322.8102" target="_blank"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">310.322.8102</span></a><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><br>
<br>
<br>
<o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">On 10June2015Wednesday, at 0:12, manning <</span><a href="mailto:bmanning@karoshi.com" target="_blank"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">bmanning@karoshi.com</span></a><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">>
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 - -<</span><a href="http://mm.icann.org/pipermail/cwg-stewardship/2015-June/003650.html" target="_blank"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">http://mm.icann.org/pipermail/cwg-stewardship/2015-June/003650.html</span></a><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">><br>
> Draft Document - <</span><a href="http://mm.icann.org/pipermail/cwg-stewardship/attachments/20150609/aea1179e/FinalTransitionProposal_v5-Redline-commentsandeditsfordiscussion-0001.docx" target="_blank"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">http://mm.icann.org/pipermail/cwg-stewardship/attachments/20150609/aea1179e/FinalTransitionProposal_v5-Redline-commentsandeditsfordiscussion-0001.docx</span></a><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">><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>
> </span><a href="mailto:bmanning@karoshi.com" target="_blank"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">bmanning@karoshi.com</span></a><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><br>
> PO Box 12317<br>
> Marina del Rey, CA 90295<br>
> </span><a href="tel:310.322.8102" target="_blank"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">310.322.8102</span></a><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><br>
><br>
><br>
><br>
> _______________________________________________<br>
> CWG-Stewardship mailing list<br>
> </span><a href="mailto:CWG-Stewardship@icann.org" target="_blank"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">CWG-Stewardship@icann.org</span></a><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><br>
> </span><a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">https://mm.icann.org/mailman/listinfo/cwg-stewardship</span></a><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><br>
_______________________________________________<br>
CWG-Stewardship mailing list<br>
</span><a href="mailto:CWG-Stewardship@icann.org" target="_blank"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">CWG-Stewardship@icann.org</span></a><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><br>
</span><a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">https://mm.icann.org/mailman/listinfo/cwg-stewardship</span></a><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
</blockquote>
</div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><br>
_______________________________________________<br>
CWG-Stewardship mailing list<br>
</span><a href="mailto:CWG-Stewardship@icann.org"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">CWG-Stewardship@icann.org</span></a><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><br>
</span><a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">https://mm.icann.org/mailman/listinfo/cwg-stewardship</span></a><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
</blockquote>
</div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><br>
<br clear="all">
<br>
-- <o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">------------------------------------------------------------------------</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:#888888"><o:p></o:p></span></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<p class="MsoNormal" style="margin-bottom:12.0pt"><i><span style="font-size:10.5pt;font-family:"Garamond",serif;color:#006600">Seun Ojedeji,<br>
Federal University Oye-Ekiti<br>
web: </span></i><a href="http://www.fuoye.edu.ng" target="_blank"><i><span style="font-size:10.5pt;font-family:"Garamond",serif">http://www.fuoye.edu.ng</span></i></a><i><span style="font-size:10.5pt;font-family:"Garamond",serif;color:#888888"><br>
</span></i><i><span style="font-size:10.5pt;font-family:"Garamond",serif;color:#006600">Mobile: +2348035233535</span></i><i><span style="font-size:10.5pt;font-family:"Garamond",serif;color:#888888"><br>
</span></i><i><span style="font-size:10.5pt;font-family:"Garamond",serif;color:#006600">alt email:</span></i><a href="mailto:seun.ojedeji@fuoye.edu.ng" target="_blank"><i><span style="font-size:10.5pt;font-family:"Garamond",serif">seun.ojedeji@fuoye.edu.ng</span></i></a><span style="font-size:10.5pt;font-family:"Garamond",serif;color:#888888"><o:p></o:p></span></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Garamond",serif;color:#888888">The key to understanding is humility - my view !<o:p></o:p></span></p>
</blockquote>
</blockquote>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>