<div dir="ltr">Hi David,<div><br></div><div>What is your justification for treating definitions differently in Sec. 9 vs. Sec. 11?</div><div><br></div><div>Re the Auerbach comment, it seems to me that the definition of "materially affected" might alleviate the concern stated in the comment -- <i style="font-size:12.8px">To be materially affected by a Dispute, the Claimant must suffer an injury or harm that is directly and causally connected to the alleged violation</i>. </div><div><br></div><div>Thanks,</div><div>Mike</div><div><br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div style="font-family:arial;font-size:small">Mike Rodenbaugh</div><div style="font-family:arial;font-size:small">RODENBAUGH LAW</div><div style="font-family:arial;font-size:small">tel/fax: +1.415.738.8087</div><div style="font-family:arial;font-size:small"><a href="http://rodenbaugh.com" target="_blank">http://rodenbaugh.com</a> </div></div></div></div>
<br><div class="gmail_quote">On Tue, Aug 15, 2017 at 11:53 AM, McAuley, David via IOT <span dir="ltr"><<a href="mailto:iot@icann.org" target="_blank">iot@icann.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div class="m_922115467857982212WordSection1">
<p class="MsoNormal">Dear members of the IRP IOT,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">One of the issues I wish to get to First Reading on this coming Thursday is the issue regarding Standing – i.e., materially affected.
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Please see my prior email below.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">In addition, we previously discussed this issue at our meeting on May 11<sup>th</sup>, the transcript of which you can access here:
<a href="https://community.icann.org/pages/viewpage.action?pageId=64084338&preview=/64084338/66063101/IRP_IOT_0512ICANN1300UTC.pdf" target="_blank">
https://community.icann.org/<wbr>pages/viewpage.action?pageId=<wbr>64084338&preview=/64084338/<wbr>66063101/IRP_IOT_<wbr>0512ICANN1300UTC.pdf</a><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">The discussion on materiality is about two-thirds of the way in.
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Here are the slides that were presented: <a href="https://community.icann.org/pages/viewpage.action?pageId=64084338&preview=/64084338/64950115/IRP%20slides%20for%20meeting%20May%2011%2C%202017.pdf" target="_blank">
https://community.icann.org/<wbr>pages/viewpage.action?pageId=<wbr>64084338&preview=/64084338/<wbr>64950115/IRP%20slides%20for%<wbr>20meeting%20May%2011%2C%<wbr>202017.pdf</a><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I propose to handle this materiality issue as per my mail below and also with these points:<u></u><u></u></p>
<p class="m_922115467857982212MsoListParagraphCxSpFirst"><u></u> <u></u></p>
<ul style="margin-top:0in" type="disc">
<li class="m_922115467857982212MsoListParagraphCxSpMiddle" style="margin-left:0in">
As for standing with respect to “imminent harm” recommend: <u></u><u></u></li></ul>
<p class="m_922115467857982212MsoListParagraphCxSpMiddle"><u></u> <u></u></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="m_922115467857982212MsoListParagraphCxSpMiddle" style="margin-left:0in">
Revise the definition of Claimant (Section 1 of USPs) to take into account the strict provisions of bylaw section 4.3(p) (even though the definition of Claimant in the USPs follows the provision of bylaw section 4.3(b)(i)).<u></u><u></u></li></ol>
<p class="m_922115467857982212MsoListParagraphCxSpMiddle" style="margin-left:.75in">
<u></u> <u></u></p>
<ol style="margin-top:0in" start="2" type="1">
<li class="m_922115467857982212MsoListParagraphCxSpMiddle" style="margin-left:0in">
Make corresponding changes in Section 9 of the USPs as required. <u></u><u></u></li></ol>
<p class="m_922115467857982212MsoListParagraphCxSpMiddle" style="margin-left:.75in">
<u></u> <u></u></p>
<ol style="margin-top:0in" start="3" type="1">
<li class="m_922115467857982212MsoListParagraphCxSpLast" style="margin-left:0in">
Recommend against changing provisions of Section 11.d of the USPs and recommend that they be left unchanged<u></u><u></u></li></ol>
<p class="MsoNormal">Best regards,<u></u><u></u></p>
<p class="MsoNormal">David<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">David McAuley<u></u><u></u></p>
<p class="MsoNormal">Sr International Policy & Business Development Manager<u></u><u></u></p>
<p class="MsoNormal">Verisign Inc.<u></u><u></u></p>
<p class="MsoNormal"><a href="tel:(703)%20948-4154" value="+17039484154" target="_blank">703-948-4154</a><u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> <a href="mailto:iot-bounces@icann.org" target="_blank">iot-bounces@icann.org</a> [mailto:<a href="mailto:iot-bounces@icann.org" target="_blank">iot-bounces@icann.org</a>]
<b>On Behalf Of </b>McAuley, David via IOT<br>
<b>Sent:</b> Monday, May 08, 2017 3:04 PM<br>
<b>To:</b> <a href="mailto:iot@icann.org" target="_blank">iot@icann.org</a><br>
<b>Subject:</b> [EXTERNAL] [IOT] "Standing - Materially Affected" comments<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Dear members of the IRP IOT:<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Here below is my suggestion for handing comments listed in our summary table as “<b>Standing – Materially Affected</b>”. [We have briefly discussed this issue under #’s 5 and 6 of the “<a href="http://mm.icann.org/pipermail/iot/2017-March/000172.html" target="_blank">segmenting
email</a>” but both Malcolm and Becky have since weighed in and so we should discuss this a bit further.]<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">The public comments repository for the proposed rules can be accessed
<a href="https://www.icann.org/public-comments/irp-supp-procedures-2016-11-28-en" target="_blank">
here</a>. <u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">This suggestion deals with these specific comments and related emails from members of our team:<u></u><u></u></p>
<p class="m_922115467857982212MsoListParagraphCxSpFirst"><u></u> <u></u></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="m_922115467857982212MsoListParagraphCxSpMiddle" style="margin-left:0in">
>From <span style="color:black;background:white">Karl Auerbach</span> (<a href="https://forum.icann.org/lists/comments-irp-supp-procedures-28nov16/msg00003.html" target="_blank">Auerbach comment</a>);
<u></u><u></u></li></ol>
<p class="m_922115467857982212MsoListParagraphCxSpMiddle"><u></u> <u></u></p>
<ol style="margin-top:0in" start="2" type="1">
<li class="m_922115467857982212MsoListParagraphCxSpMiddle" style="margin-left:0in">
>From the International Trademark Association (<a href="https://forum.icann.org/lists/comments-irp-supp-procedures-28nov16/pdfyVMCP8h4dU.pdf" target="_blank">INTA comment</a>);<u></u><u></u></li></ol>
<p class="m_922115467857982212MsoListParagraphCxSpMiddle"><u></u> <u></u></p>
<ol style="margin-top:0in" start="3" type="1">
<li class="m_922115467857982212MsoListParagraphCxSpMiddle" style="margin-left:0in">
>From Malcolm Hutty’s related <a href="http://mm.icann.org/pipermail/iot/2017-April/000200.html" target="_blank">
email</a>; and <u></u><u></u></li></ol>
<p class="m_922115467857982212MsoListParagraphCxSpMiddle"><u></u> <u></u></p>
<ol style="margin-top:0in" start="4" type="1">
<li class="m_922115467857982212MsoListParagraphCxSpLast" style="margin-left:0in">
>From Becky Burr’s related <a href="http://mm.icann.org/pipermail/iot/2017-April/000202.html" target="_blank">
email</a>. <u></u><u></u></li></ol>
<p class="MsoNormal"><b>Summary of Comments:<u></u><u></u></b></p>
<p class="MsoNormal"><b><u></u> <u></u></b></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="m_922115467857982212MsoListParagraph" style="margin-left:0in">
The Auerbach comment says, in part:<i><u></u><u></u></i></li></ol>
<p class="MsoNormal" style="margin-left:.75in"><i>The </i><tt><i><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black;background:white">standing requirement that one be " materially affected" is</span></i></tt><span class="m_922115467857982212apple-converted-space"><i><span style="color:black;background:white"> </span></i></span><tt><i><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black;background:white">excessively
legalistic and narrow.</span></i></tt><tt><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black;background:white"><u></u><u></u></span></tt></p>
<p class="MsoNormal" style="margin-left:.75in"><tt><i><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black;background:white"><u></u> <u></u></span></i></tt></p>
<p class="MsoNormal" style="margin-left:.75in"><tt><i><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black;background:white">… The proposed "materially affected" standing limit will further empower</span></i></tt><span class="m_922115467857982212apple-converted-space"><i><span style="color:black;background:white"> </span></i></span><tt><i><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black;background:white">those
who have financial interests in matters regulated by ICANN and</span></i></tt><span class="m_922115467857982212apple-converted-space"><i><span style="color:black;background:white"> </span></i></span><tt><i><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black;background:white">correspondingly
disempower those who merely suffer, en masse, a shared</span></i></tt><span class="m_922115467857982212apple-converted-space"><i><span style="color:black;background:white"> </span></i></span><tt><i><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black;background:white">harm
that is difficult to measure on an individual basis.<u></u><u></u></span></i></tt></p>
<p class="MsoNormal" style="margin-left:.75in"><tt><i><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black;background:white"><u></u> <u></u></span></i></tt></p>
<p class="MsoNormal" style="margin-left:.75in"><tt><i><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black;background:white">… The foundation for standing should be broadened to recognize several</span></i></tt><span class="m_922115467857982212apple-converted-space"><i><span style="color:black;background:white"> </span></i></span><tt><i><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black;background:white">factors.
At a minimum it should encompass any person who uses a domain</span></i></tt><span class="m_922115467857982212apple-converted-space"><i><span style="color:black;background:white"> </span></i></span><tt><i><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black;background:white">name,
IP address, or IANA protocol parameter. At a minimum it should</span></i></tt><span class="m_922115467857982212apple-converted-space"><i><span style="color:black;background:white"> </span></i></span><tt><i><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black;background:white">encompass
any person or entity listed in any "whois" entry. It ought to</span></i></tt><span class="m_922115467857982212apple-converted-space"><i><span style="color:black;background:white"> </span></i></span><tt><i><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black;background:white">encompass
any person or entity that constitutes the "public" as</span></i></tt><span class="m_922115467857982212apple-converted-space"><i><span style="color:black;background:white"> </span></i></span><tt><i><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black;background:white">construed
by the California law of "public benefit" corporations under</span></i></tt><span class="m_922115467857982212apple-converted-space"><i><span style="color:black;background:white"> </span></i></span><tt><i><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black;background:white">which
ICANN has obtained its legal existence.</span></i></tt><span class="m_922115467857982212apple-converted-space"><i><span style="color:black;background:white"> …</span></i><u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.75in"><u></u> <u></u></p>
<ol style="margin-top:0in" start="2" type="1">
<li class="m_922115467857982212MsoListParagraphCxSpFirst" style="margin-bottom:0in;margin-left:0in;margin-bottom:.0001pt;line-height:normal;text-autospace:none">
The INTA comment says, in part:<u></u><u></u></li></ol>
<p class="m_922115467857982212MsoListParagraphCxSpMiddle" style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal;text-autospace:none">
<u></u> <u></u></p>
<p class="m_922115467857982212MsoListParagraphCxSpMiddle" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt;line-height:normal;text-autospace:none">
The “materially affected” standard is essentially too restrictive because it fails to offer a remedy for imminent injury or harm. INTA asks that we change the definition of CLAIMANT to be:<u></u><u></u></p>
<p class="m_922115467857982212MsoListParagraphCxSpMiddle" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt;line-height:normal;text-autospace:none">
<u></u> <u></u></p>
<p class="m_922115467857982212MsoListParagraphCxSpMiddle" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt;line-height:normal;text-autospace:none">
<i>A CLAIMANT is any legal or natural person, group, or entity including, but not limited to the Empowered Community, a Supporting Organization, or an Advisory Committee, that has been materially affected by a Dispute. To be materially affected by a Dispute,
the Claimant must suffer an actual <b>or imminent</b> injury or harm that is directly and causally connected to the
<b>conduct complained of</b>.<u></u><u></u></i></p>
<p class="m_922115467857982212MsoListParagraphCxSpMiddle" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt;line-height:normal;text-autospace:none">
<i><u></u> <u></u></i></p>
<p class="m_922115467857982212MsoListParagraphCxSpMiddle" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt;line-height:normal;text-autospace:none">
INTA<i> </i>goes on to suggest that the same definition apply in Section 9 of the USPs which allows for a summary dismissal for lack of standing. It also suggests the new standard apply in USPs Section 11.d regarding claims for breach of the IANA Naming Functions
Contract. <i><u></u><u></u></i></p>
<p class="m_922115467857982212MsoListParagraphCxSpMiddle" style="margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt;line-height:normal;text-autospace:none">
<i><u></u> <u></u></i></p>
<ol style="margin-top:0in" start="3" type="1">
<li class="m_922115467857982212MsoListParagraphCxSpLast" style="margin-bottom:0in;margin-left:0in;margin-bottom:.0001pt;line-height:normal;text-autospace:none">
Malcolm’s email says, in part:<u></u><u></u></li></ol>
<p class="MsoNormal" style="text-autospace:none"><u></u> <u></u></p>
<pre style="margin-left:1.0in"><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">... It is in nobody's interest to prevent an IRP case being brought over the mere technicality that something that is certain and imminent has not yet occurred, but becomes irreversible and so moot the instant it does occur. ...</span></i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><u></u><u></u></span></pre>
<p class="MsoNormal" style="margin-left:1.0in;text-autospace:none"><u></u> <u></u></p>
<pre style="margin-left:1.0in"><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">I would therefore like to ask our group to explore whether there is anything that might be done within the existing bylaws that might go at least some way towards addressing INTA's underlying concern, even if not in quite the manner they proposed.</span></i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><u></u><u></u></span></pre>
<p class="m_922115467857982212MsoListParagraphCxSpFirst" style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal;text-autospace:none">
<u></u> <u></u></p>
<ol style="margin-top:0in" start="4" type="1">
<li class="m_922115467857982212MsoListParagraphCxSpMiddle" style="margin-bottom:0in;margin-left:0in;margin-bottom:.0001pt;line-height:normal;text-autospace:none">
Becky’s email says, “<i><span style="color:black">I would have thought that the provision of injunctive relief addresses this issue</span></i><span style="color:black">”.</span><u></u><u></u></li></ol>
<p class="m_922115467857982212MsoListParagraphCxSpLast" style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal;text-autospace:none">
<u></u> <u></u></p>
<p class="MsoNormal"><b>Draft USP Rule:<u></u><u></u></b></p>
<p class="MsoNormal"><b><u></u> <u></u></b></p>
<p class="MsoNormal">The draft rule being commented upon is section 1. Definitions (definition of Claimant, footnote omitted):<u></u><u></u></p>
<p class="MsoNormal" style="margin-left:1.0in"><i><u></u> <u></u></i></p>
<p class="MsoNormal" style="margin-left:1.0in"><i>A CLAIMANT is any legal or natural person, group, or entity including, but not limited to the Empowered Community, a Supporting Organization, or an Advisory Committee, that has been materially affected by a
Dispute. To be materially affected by a Dispute, the Claimant must suffer an injury or harm that is directly and causally connected to the alleged violation.<u></u><u></u></i></p>
<p class="MsoNormal"><b><u></u> <u></u></b></p>
<p class="MsoNormal"><b>Bylaw Section 4.3(p) </b>provides:<u></u><u></u></p>
<p style="margin-left:1.0in;background:white"><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#333333">(p) A Claimant may request interim relief. Interim relief may include prospective relief, interlocutory relief, or declaratory or
injunctive relief, and specifically may include a stay of the challenged<span class="m_922115467857982212apple-converted-space"> </span>ICANN<span class="m_922115467857982212apple-converted-space"> </span>action or decision until such time as the opinion of the IRP Panel is considered as described
in<span class="m_922115467857982212apple-converted-space"> </span><u>Section 4.3(o)(iv)</u>, in order to maintain the<span class="m_922115467857982212apple-converted-space"> </span></span></i><em><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#333333;font-style:normal">status
quo</span></em><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#333333">. A single member of the Standing Panel ("<strong><span style="font-family:"Calibri",sans-serif">Emergency Panelist</span></strong>") shall be selected to adjudicate
requests for interim relief. In the event that no Standing Panel is in place when an Emergency Panelist must be selected, the IRP Provider's rules shall apply to the selection of the Emergency Panelist. Interim relief may only be provided if the Emergency
Panelist determines that the Claimant has established all of the following factors:<u></u><u></u></span></i></p>
<p style="margin-left:1.5in;background:white;box-sizing:border-box;line-height:1.4rem;font-size:1rem;margin:1.25rem">
<i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#333333">(i) A harm for which there will be no adequate remedy in the absence of such relief;<u></u><u></u></span></i></p>
<p style="margin-left:1.5in;background:white;box-sizing:border-box;line-height:1.4rem;font-size:1rem;margin:1.25rem">
<i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#333333">(ii) Either: (A) likelihood of success on the merits; or (B) sufficiently serious questions related to the merits; and<u></u><u></u></span></i></p>
<p style="margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt;background:white;box-sizing:border-box;line-height:1.4rem;font-size:1rem">
<i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#333333">(iii) A balance of hardships tipping decidedly toward the party seeking relief.</span></i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#333333"><u></u><u></u></span></p>
<p class="MsoNormal"><b><u></u> <u></u></b></p>
<p class="MsoNormal"><b>Our IRP IOT role:<u></u><u></u></b></p>
<p class="MsoNormal"><b><u></u> <u></u></b></p>
<p class="MsoNormal">As we do our work we are instructed by the bylaws, among other things, to provide rules that will facilitate the “just resolution of disputes” (Bylaw Section 4.3(a)(vii)) and ensure “fundamental fairness and due process” (Bylaw Section
4.3(n)(iv)). <u></u><u></u></p>
<p class="MsoNormal"><b><u></u> <u></u></b></p>
<p class="MsoNormal"><b>My recommendations (as participant, not as lead):<u></u><u></u></b></p>
<p class="MsoNormal"><b><u></u> <u></u></b></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="m_922115467857982212MsoListParagraphCxSpFirst" style="margin-left:0in">
With respect to the Auerbach comment, it seems to go beyond bylaws provisions and should be rejected as beyond our scope.
<u></u><u></u></li></ol>
<p class="m_922115467857982212MsoListParagraphCxSpMiddle"><u></u> <u></u></p>
<ol style="margin-top:0in" start="2" type="1">
<li class="m_922115467857982212MsoListParagraphCxSpMiddle" style="margin-left:0in">
With respect to the INTA comment, I think INTA, Becky, and Malcolm have a good point. I suggest we ask our drafters at Sidley to:<u></u><u></u></li></ol>
<p class="m_922115467857982212MsoListParagraphCxSpMiddle"><u></u> <u></u></p>
<ol style="margin-top:0in" start="2" type="1">
<ol style="margin-top:0in" start="1" type="a">
<li class="m_922115467857982212MsoListParagraphCxSpMiddle" style="margin-left:0in">
Revise the definition of Claimant to take into account the provisions of bylaw section 4.3(p) (even though the definition of Claimant in the USPs follows the provision of bylaw section 4.3(b)(i)).
<u></u><u></u></li></ol>
</ol>
<p class="m_922115467857982212MsoListParagraphCxSpMiddle" style="margin-left:1.0in">
<u></u> <u></u></p>
<ol style="margin-top:0in" start="2" type="1">
<ol style="margin-top:0in" start="2" type="a">
<li class="m_922115467857982212MsoListParagraphCxSpMiddle" style="margin-left:0in">
Make corresponding changes in Section 9 of the USPs as required.<u></u><u></u></li></ol>
</ol>
<p class="m_922115467857982212MsoListParagraphCxSpMiddle"><u></u> <u></u></p>
<ol style="margin-top:0in" start="2" type="1">
<ol style="margin-top:0in" start="3" type="a">
<li class="m_922115467857982212MsoListParagraphCxSpLast" style="margin-left:0in">
I am not convinced that we should change Section 11.d of the USPs and recommend that they be left unchanged.
<u></u><u></u></li></ol>
</ol>
<p class="MsoNormal"><b>Differing views:<u></u><u></u></b></p>
<p class="MsoNormal"><b><u></u> <u></u></b></p>
<p class="MsoNormal">If you have a concern with what I propose or have another suggestion, please make it on list
<b>as soon as possible </b>and <b>as specifically as possible</b>. Please couch it in terms/language that can be acted upon as a decision if adopted (i.e. in language that would be a sufficient instruction to our outside lawyers that they could draft appropriate
language). <u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Best regards,<u></u><u></u></p>
<p class="MsoNormal">David<u></u><u></u></p>
<p class="MsoNormal" style="margin-left:1.0in;text-autospace:none"><i><u></u> <u></u></i></p>
<p class="MsoNormal">David McAuley<u></u><u></u></p>
<p class="MsoNormal">Sr International Policy & Business Development Manager<u></u><u></u></p>
<p class="MsoNormal">Verisign Inc.<u></u><u></u></p>
<p class="MsoNormal"><a href="tel:(703)%20948-4154" value="+17039484154" target="_blank">703-948-4154</a><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<br>______________________________<wbr>_________________<br>
IOT mailing list<br>
<a href="mailto:IOT@icann.org">IOT@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/iot" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/iot</a><br>
<br></blockquote></div><br></div>