<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=iso-8859-1">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:HelveticaNeue;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.ms-outlook-ios-reference-expand, li.ms-outlook-ios-reference-expand, div.ms-outlook-ios-reference-expand
{mso-style-name:ms-outlook-ios-reference-expand;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#999999;}
p.ms-outlook-ios-availability-container, li.ms-outlook-ios-availability-container, div.ms-outlook-ios-availability-container
{mso-style-name:ms-outlook-ios-availability-container;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
border:none;
padding:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.ms-outlook-ios-mention, li.ms-outlook-ios-mention, div.ms-outlook-ios-mention
{mso-style-name:ms-outlook-ios-mention;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
background:#F1F1F1;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#333333;}
p.ms-outlook-ios-mention-external, li.ms-outlook-ios-mention-external, div.ms-outlook-ios-mention-external
{mso-style-name:ms-outlook-ios-mention-external;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
background:#FDF7E7;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#BA8F0D;}
p.ms-outlook-ios-mention-external-clear-design, li.ms-outlook-ios-mention-external-clear-design, div.ms-outlook-ios-mention-external-clear-design
{mso-style-name:ms-outlook-ios-mention-external-clear-design;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
background:#F1F1F1;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#BA8F0D;}
p.ms-outlook-ios-dark-mode, li.ms-outlook-ios-dark-mode, div.ms-outlook-ios-dark-mode
{mso-style-name:ms-outlook-ios-dark-mode;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#E1E1E1;}
p.ms-outlook-ios-availability-timeslot-container, li.ms-outlook-ios-availability-timeslot-container, div.ms-outlook-ios-availability-timeslot-container
{mso-style-name:ms-outlook-ios-availability-timeslot-container;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.ms-outlook-ios-availability-border, li.ms-outlook-ios-availability-border, div.ms-outlook-ios-availability-border
{mso-style-name:ms-outlook-ios-availability-border;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.ms-outlook-ios-reference-expand1, li.ms-outlook-ios-reference-expand1, div.ms-outlook-ios-reference-expand1
{mso-style-name:ms-outlook-ios-reference-expand1;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#777777;}
p.ms-outlook-ios-availability-container1, li.ms-outlook-ios-availability-container1, div.ms-outlook-ios-availability-container1
{mso-style-name:ms-outlook-ios-availability-container1;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
border:none;
padding:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.ms-outlook-ios-availability-timeslot-container1, li.ms-outlook-ios-availability-timeslot-container1, div.ms-outlook-ios-availability-timeslot-container1
{mso-style-name:ms-outlook-ios-availability-timeslot-container1;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
background:#0086F0;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
p.ms-outlook-ios-availability-border1, li.ms-outlook-ios-availability-border1, div.ms-outlook-ios-availability-border1
{mso-style-name:ms-outlook-ios-availability-border1;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
border:none;
padding:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.ms-outlook-ios-mention1, li.ms-outlook-ios-mention1, div.ms-outlook-ios-mention1
{mso-style-name:ms-outlook-ios-mention1;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
background:#292929;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#ACACAC;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle34
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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">Jeff et al – a few clarifying questions if you don’t mind the usage of that term….<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">On this paragraph - <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:150%">“<span style="font-family:"HelveticaNeue",serif;color:#333333">The one exception is on the issue of closed generics, where the board specifically stated that it was creating a temporary solution
and that it wanted policy development on this matter. Therefore, in the event that we cannot find consensus on that subject, we will document the positions taken and at the end of the day it will be up to the board to determine what the baseline is.”<o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:"HelveticaNeue",serif;color:#333333"><o:p> </o:p></span></p>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:"HelveticaNeue",serif;color:#333333">At what point does the “temporary solution” become permanent? Is it when this group determines a policy that sets proactive rules going forward? Is
it when the Board, based upon the deliberations, but not a consensus determination, comes up with a new resolution trumping the existing one? And how long does the GAC advice on this stand? Does he have a shelf life or expiration date?<o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:"HelveticaNeue",serif;color:#333333">Thanks<o:p></o:p></span></p>
<p class="MsoNormal">For handy reference, the Board resolution and rationale on this can be found here.
<a href="https://www.icann.org/resources/board-material/resolutions-new-gtld-2015-06-21-en#2.a">
https://www.icann.org/resources/board-material/resolutions-new-gtld-2015-06-21-en#2.a</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org>
<b>On Behalf Of </b>Jeff Neuman<br>
<b>Sent:</b> Friday, September 27, 2019 2:10 PM<br>
<b>To:</b> Alan Greenberg <alan.greenberg@mcgill.ca>; Kathy Kleiman <kathy@kathykleiman.com>; gnso-newgtld-wg@icann.org<br>
<b>Subject:</b> Re: [Gnso-newgtld-wg] Resolving Objection Proceedings with Mandatory PICs<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:"HelveticaNeue",serif;color:#333333">As Alan states below, the baseline that we use is how the program was actually implemented as opposed to what was in the 2007/2008 GNSO Policy and/or
what was in the Applicant Guidebook. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:"HelveticaNeue",serif;color:#333333"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:"HelveticaNeue",serif;color:#333333">The one exception is on the issue of closed generics, where the board specifically stated that it was creating a temporary solution and that it wanted
policy development on this matter. Therefore, in the event that we cannot find consensus on that subject, we will document the positions taken and at the end of the day it will be up to the board to determine what the baseline is.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:"HelveticaNeue",serif;color:#333333"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:"HelveticaNeue",serif;color:#333333">With respect to what constitutes high-level agreement, this is a determination that leadership of the working group will have to make. We take this responsibility
very seriously and assure you that we are doing everything in our power to be fair and neutral. That said its determination (and ultimately the determination of consensus) is not formulaic, but rather is dependent on a number of factors. We also want to note
that the fact that there is only one group, or one individual, or one constituency or stakeholder group that opposes a concept, does not automatically mean that there cannot be high level agreement on the concepts, or elements thereof. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:"HelveticaNeue",serif;color:#333333"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:"HelveticaNeue",serif;color:#333333">As you will see in a number of comments, many groups oppose an entire concept. However, when you read the comments as a whole you can see that their
opposition to the entire concept may be based on one element of many that constitute the subject area. Where that is the case, If we can address that one element, we may still find high-level agreement on the concept as a whole.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:"HelveticaNeue",serif;color:#333333"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:"HelveticaNeue",serif;color:#333333">Therefore, what is most helpful to us is not a reply that states there is no high-level agreement on a subject. Rather, what is most helpful to us is
a reply that states in specificity what elements of the overall concept you believe the group as a whole may not have addressed in a satisfactory manner. Some of the recent comments have done that, but others have not. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:"HelveticaNeue",serif;color:#333333"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:"HelveticaNeue",serif;color:#333333">Best regards,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:"HelveticaNeue",serif;color:#333333"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:"HelveticaNeue",serif;color:#333333">Jeffrey J Neuman<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:"HelveticaNeue",serif;color:#333333">(202) 549-5079<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:"HelveticaNeue",serif;color:#333333"><a href="mailto:Jeff.Neuman@comlaude.com">Jeff.Neuman@comlaude.com</a><o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<div class="MsoNormal" align="center" style="text-align:center;line-height:150%">
<span style="font-family:"HelveticaNeue",serif;color:#333333">
<hr size="2" width="98%" align="center">
</span></div>
<div id="divRplyFwdMsg">
<p class="MsoNormal" style="line-height:150%"><b><span style="color:#333333">From:</span></b><span style="color:#333333"> Gnso-newgtld-wg <<a href="mailto:gnso-newgtld-wg-bounces@icann.org">gnso-newgtld-wg-bounces@icann.org</a>> on behalf of Alan Greenberg
<<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a>><br>
<b>Sent:</b> Friday, September 27, 2019 5:36 AM<br>
<b>To:</b> Kathy Kleiman; <a href="mailto:gnso-newgtld-wg@icann.org">gnso-newgtld-wg@icann.org</a><br>
<b>Subject:</b> Re: [Gnso-newgtld-wg] Resolving Objection Proceedings with Mandatory PICs
<o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="color:#333333"> <o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:"HelveticaNeue",serif;color:#333333">My understanding is that the Baseline that we are working to is not the Applicant Guidebook but the final effective implementation including Board actions,
so Voluntary PICS, (which predated Mandatory PICS) are there unless we have agreement to change them.<br>
<br>
JEFF/CHERYL: Can you confirm exactly what our baseline is?<br>
<br>
Alan<br>
<br>
At 26/09/2019 06:39 PM, Kathy Kleiman wrote:<br>
<br>
<br>
<o:p></o:p></span></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="line-height:150%"><span style="font-family:"HelveticaNeue",serif;color:#333333">All,<br>
<br>
Mandatory PICS are unchanging. You can't resolve an Objection with a Mandatory PIC. It would require a Voluntary PIC -- which has become a misnomer, and a complete garbage can of everything applicants wanted to throw into the kitchen sink. There are longstanding
objections to "voluntary PICs" from the Noncommercial Stakeholder Group, Electronic Frontier Foundation and the Public Interest Community (as we discussed many times). There is no high-level agreement on including them -- and they were not part of the Round
1 rules. <br>
<br>
We agreed in last week's call that you could *amend the application* to settle an Objection. That puts the private Objection settlement out for fuller and fairer review -- which is fair. Changes to public portion of applications would be subject to public
comment -- and hopefully notification to all who have filed comments and therefore are likely interested in following changes to that application. Publication and public notice on significant changes to applications (with public comment) to settle an Objection<b>was
</b>done in Round 1. <br>
<br>
But there was no question that there is a <u>high level Disagreement to settling disputes with changes to PICs -- because mandatory PICs are fixed and unchanging. </u>This high level Disagreement was raised in every Objections call until last night.<i>Surely
we are not saying that if you miss one discussion in the dead of night, you have waived all previous objections? </i><br>
<br>
I'm assuming GAC objections were the topic at issue here -- and can settled with changes to the application itself.Many, many changes to public portions of applications were made in response to the GAC in Round 1. <i><br>
</i><br>
Best, Kathy<br>
<br>
Kathryn Kleiman, American University Washington College of Law<br>
<br>
<br>
On 9/26/2019 6:13 PM, Aikman-Scalese, Anne wrote:<br>
<br>
<o:p></o:p></span></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="margin-bottom:12.0pt;line-height:150%"><span style="font-family:"HelveticaNeue",serif;color:#333333"><img border="0" width="31" height="31" style="width:.3263in;height:.3263in" id="Picture_x0020_2" src="cid:image001.jpg@01D57546.2BC7C2D0" alt="[]"></span><a name="_GoBack"></a><span style="font-family:"HelveticaNeue",serif;color:#333333"> <br>
Regarding the last call and the possible high level agreement on resolving Objection proceedings with mandatory PICs, it’s important to note that there is no private right of action to enforce a PIC. The current PIC Dispute Resolution procedure – PICDRP (see
attached) provides for various steps to be taken in resolving the PIC complaint and if unresolved, ICANN at its SOLE discrestion, can invoke a a Staning Panel or undertake a compliance investigation.<br>
<br>
So the points I am raising here are:<br>
<br>
(1) Proceeding on the report of a PIC violation rests in the sole discretion of ICANN<br>
(2) The expense of the Compliance investigation and/or Standing Panel is an expense of ICANN.<br>
<br>
Accordingly, it may be appropriate to consider adopting a private right of action (rather than forcing the expense on ICANN) in connection with the enforcement of mandatory PICs adopted for purposes of resolving an Objection proceeding.<br>
<br>
In fact, the PICDRP originally contained a provision allowing the enforcement issue to be taken to a third party provider. However, that draft did not survive.<br>
<br>
Anne<br>
<br>
<br>
<b>Anne E. Aikman-Scalese<br>
</b>Of Counsel<br>
520.629.4428 office<br>
520.879.4725 fax<br>
<a href="mailto:AAikman@lrrc.com">AAikman@lrrc.com</a><br>
_____________________________<br>
</span><span style="font-family:"HelveticaNeue",serif;color:#333333"><img border="0" width="115" height="46" style="width:1.1944in;height:.4791in" id="_x0000_i1032" src="cid:7.1.0.9.2.20190927001342.09916580@mcgill.ca.4" alt="[]"></span><span style="font-family:"HelveticaNeue",serif;color:#333333"><br>
Lewis Roca Rothgerber Christie LLP<br>
One South Church Avenue, Suite 2000<br>
Tucson, Arizona 85701-1611<br>
<a href="http://lrrc.com/">lrrc.com</a><br>
</span><span style="font-family:"HelveticaNeue",serif;color:#333333"><img border="0" width="120" height="39" style="width:1.25in;height:.4027in" id="_x0000_i1031" src="cid:7.1.0.9.2.20190927001342.09916580@mcgill.ca.5" alt="[]"></span><span style="font-family:"HelveticaNeue",serif;color:#333333"><br>
Because what matters<br>
to you, matters to us.™<br>
<br>
<o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center;line-height:150%">
<span style="font-family:"HelveticaNeue",serif;color:#333333">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal" style="margin-bottom:12.0pt;line-height:150%"><span style="font-size:7.5pt;line-height:150%;font-family:"Arial",sans-serif;color:gray"><br>
This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message
or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying
to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.<br>
<br>
</span><span style="font-family:"HelveticaNeue",serif;color:#333333"><o:p></o:p></span></p>
<pre style="line-height:150%"><span style="color:#333333">_______________________________________________Gnso-newgtld-wg mailing list<a href="mailto:Gnso-newgtld-wg@icann.org">Gnso-newgtld-wg@icann.org</a><a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg</a>_______________________________________________By submitting your personal data, you consent to the processing of yourpersonal data for purposes of subscribing to this mailing list accordancewith the ICANN Privacy Policy(<a href="https://www.icann.org/privacy/policy">https://www.icann.org/privacy/policy</a>) and the website Terms ofService(<a href="https://www.icann.org/privacy/tos">https://www.icann.org/privacy/tos</a>). You can visit the Mailman linkabove to change your membership status or configuration, includingunsubscribing, setting digest-style delivery or disabling deliveryaltogether (e.g., for a vacation), and so on.<o:p></o:p></span></pre>
</blockquote>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:"HelveticaNeue",serif;color:#333333"><br>
<br>
_______________________________________________<br>
Gnso-newgtld-wg mailing list<br>
<a href="mailto:Gnso-newgtld-wg@icann.org">Gnso-newgtld-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg</a><br>
_______________________________________________<br>
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy"> https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a href="https://www.icann.org/privacy/tos"> https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.<o:p></o:p></span></p>
</blockquote>
</div>
<div class="MsoNormal" align="center" style="text-align:center;line-height:150%">
<span style="font-family:"HelveticaNeue",serif;color:#333333">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:"HelveticaNeue",serif;color:#333333">The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by
anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that the Com Laude Group
does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of
the group or one of its member entities. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Valideus
Limited, a company registered in England and Wales with company number 06181291 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176, having its registered
office at 33 Melville Street, Edinburgh, Lothian, EH3 7JF Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, headquartered at 1751 Pinnacle Drive, Suite 600, McLean, VA 22102, USA; Com Laude (Japan) Corporation, a company registered in Japan having
its registered office at Suite 319,1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan. For further information see
<a href="https://comlaude.com" target="_blank">www.comlaude.com</a> <o:p></o:p></span></p>
</div>
</body>
</html>