<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font size="+1"><font face="Lucida Grande">I think you just need
to up your numbers a bit Michael...I might get more in small
claims Court these days! (Don't got there, it is just a
comparator).</font></font></p>
<p><font size="+1"><font face="Lucida Grande">cheers Stephanie</font></font></p>
<p><font size="+1"><font face="Lucida Grande">PS still pondering the
whole issue of giving up rights...Doubt I would ever buy it.
What happens if data subject finds out subsequently that their
data has been sold to criminal gangs? (think equifax,
choicepoint cases here). Remember that I am not just talking
about WHOIS data in a tiered access case....I am assuming that
queries will also lead to direct contact with registrars to
get financial data. We should not build two systems here...</font></font></p>
<p><font size="+1"><font face="Lucida Grande"></font></font><br>
</p>
<div class="moz-cite-prefix">On 2018-06-20 12:03, Michael Palage
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:056001d408b0$42797770$c76c6650$@palage.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<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:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Lucida Grande";
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:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
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";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Arial",sans-serif;
color:windowtext;
font-weight:normal;
font-style:normal;}
span.EmailStyle24
{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]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">Brian,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">Thanks
for the constructive feedback, and I welcome your additional
feedback in connection with my response below.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">As
I have noted previously, the final ADR component of the
Philly Special has not yet been finalized, although I am
working at it diligently. In fact I have a call with a
former JAMS employee today to discuss some of her thoughts
on my framework. My goal is to have a framework document
(not specific policy and rules) out for discussion by the
beginning of Panama.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">As
you accurately note, Privacy Shield DOES NOT provide for
“damages.” However, Section 82, Paragraph 1 of the GDPR
does provide that “Any person who has suffered material or
non-material damage as a result of an infringement of this
Regulation shall have the right to receive compensation from
the controller or processor for the damage suffered.”
Moreover Section 80 provides for a qualified third party to
represent a Data Subject(s) and the right “to receive
compensation referred to in Article 82 on his or her behalf
where provided for by Member State law.”<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">So
what I am trying to do with the Philly Special ADR component
is thread the needle with a ADR framework that provides
“some” compensation to the Data Subject. I believe that the
majority of the IPC/BC participants will likely support the
proposition that the Data Subject get nothing per the
Privacy Shield provision. However, the GDPR does provide for
a private right of action and compensation and that cannot
be ignored. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">My
current best thinking involves a hybrid approach where a
Data Subject waives their rights under Section 80 and 82, if
they elect for the ADR that has some type of renumeration
for their harm. TO BE CLEAR, THE DATA SUBJECT WOULD NOT BE
REQUIRED TO WAIVE THEIR RIGHT TO REPORT OR FILE A COMPLAINT
WITH A DPA. OBVIOUSLY THAT WOULD BE A NON-STARTER FOR THE
EDPB.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">In
a recent discussion with a privacy lawyer, the thought
process involved giving businesses some predictability as to
the damages/fines they might face through an adverse ADR
decision, while empowering a Data Subject to have a quicker
process to have their claim resolved.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">Now
those last couple of paragraphs will probably result in my
receiving universal objection from both the hardcore IPC/BC
advocates on this list as well as from Stephanie and Kathy.
However, I am wearing my standard issued ICANN Kevlar Body
armor and flame resistant undergarments – so fire away. This
is a unenviable middle ground I have often found myself in
over the past 20 years. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">Stephine
has made clear she thinks a Data Subject should be able to
receive substantially much more than my proposed fine range.
My response to Stephanie is if a Data Subject has been
substantially harmed avoid my lightweight ADR and resort to
the courts under Section 80 or 82. However, if the harm to
the Data Subject is not truly onerous and the Data Subject
does not have the financial resources to initiate a legal
proceeding in a court of competent jurisdiction, the ADR and
the nominal fine may be better than nothing.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">To
my BC/IPC colleagues, Section 80 and 82 of the GDPR are
real, and they provide for a private cause of action with
real damages. Should the ultimate winner in ICANN’s
Universal Access Model (UAM) steel cage match NOT account
for a mechanism that provides Data Subjects an
administrative right to remedy the alledged violation, it is
not a matter “if” but “when” the Data Controllers and Data
Processors associated with this UAM find themselves in
court. That does not seem like the business predictability
that most businesses strive to achieve. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">Finally
in response to John’s most recent email about the
unworkability of the Philly Special model when someone
refuses to pay the fine, thus resulting in future denied
access. The Philly Special specifically provides for a
financial instrument to be put in place to prevent this type
of bad actor walking away from their wrong/debt. This
provision was not only provided for in the Philly Special
2.0 policy document but it was also provided for in the
proposed legal template that Users would have to sign prior
to gaining access to the system.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">Brian
thanks again for the constructive engagement, and hopefully
this email provides additional insight into how I am
proposing to navigate the complex ADR minefield.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">Best
regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">Michael<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<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;color:windowtext">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">
Accred-Model <a class="moz-txt-link-rfc2396E" href="mailto:accred-model-bounces@icann.org"><accred-model-bounces@icann.org></a> <b>On
Behalf Of </b>BECKHAM, Brian<br>
<b>Sent:</b> Wednesday, June 20, 2018 7:55 AM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:accred-model@icann.org">accred-model@icann.org</a><br>
<b>Subject:</b> Re: [Accred-Model] Version 1.6 of the
Accreditation and Access Model<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:windowtext">With
respect to Michael’s request for feedback, and merely for
information, the binding arbitration provided for under the
Privacy Shield framework that Kathy has helpfully pointed
out proposes the following:<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:windowtext"><a
href="https://www.privacyshield.gov/article?id=B-Available-Remedies"
moz-do-not-send="true">https://www.privacyshield.gov/article?id=B-Available-Remedies</a>
<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:windowtext">B.
Available Remedies<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:windowtext">Under
this arbitration option, the Privacy Shield Panel
(consisting of one or three arbitrators, as agreed by the
parties) has the authority to impose individual-specific,
non-monetary equitable relief (such as access, correction,
deletion, or return of the individual’s data in question)
necessary to remedy the violation of the Principles only
with respect to the individual. These are the only powers
of the arbitration panel with respect to remedies. In
considering remedies, the arbitration panel is required to
consider other remedies that already have been imposed by
other mechanisms under the Privacy Shield. No damages,
costs, fees, or other remedies are available. Each party
bears its own attorney’s fees. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:windowtext">Perhaps
the types of equitable relief foreseen here are meant to
speak to the difficulty in being “made whole”?<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:windowtext">Kind
regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:windowtext">Brian
<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:windowtext"><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:10.0pt;font-family:"Tahoma",sans-serif;color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:windowtext">
Accred-Model [<a
href="mailto:accred-model-bounces@icann.org"
moz-do-not-send="true">mailto:accred-model-bounces@icann.org</a>]
<b>On Behalf Of </b>Stephanie Perrin<br>
<b>Sent:</b> Wednesday, June 20, 2018 1:13 AM<br>
<b>To:</b> <a href="mailto:accred-model@icann.org"
moz-do-not-send="true">accred-model@icann.org</a><br>
<b>Subject:</b> Re: [Accred-Model] Version 1.6 of the
Accreditation and Access Model<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p><span style="font-size:13.5pt;font-family:"Lucida
Grande",serif">I think Mike has come up with a
reasonable solution, although the numbers are low. If I
have to replace my phone number because it is out there now,
$250 does not cover my trouble. This is the fundamental
problem with privacy loss, it is often impossible to be made
whole. </span><o:p></o:p></p>
<p><span style="font-size:13.5pt;font-family:"Lucida
Grande",serif">Stephanie Perrin</span><o:p></o:p></p>
<div>
<p class="MsoNormal">On 2018-06-19 14:23, Michael Palage
wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>John,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>So I think it is fair to say that no matter what Kathy or I say you will not be happy with any meaningful Data Subject centric safeguard, so this will be my last response on the list.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>So the "complex" problem we are seeking to solve is respecting the Fundamental Human Right to Privacy that Europeans have. Much like I respect my fellow Americans and their love of the Second Amendment, I have learned to respect European's passion for their Right to Privacy.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Now the problem with ICANN and the IPC/BC solution is that there is no mechanism to make a Data Subject whole after their Personal Data has been improperly processed. All of the proposed safeguards are focused on limiting a third party to harm additional Data Subjects in the future. I just find that problematic.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>When Kathy I worked on the UDRP and Working Group B almost 20 years ago, we were on the opposite side of the issue. However, we recognized that any solution that ICANN proposed had to be modeled after well established international law, and respect the rights of both Complainant (Trademark Owner) and Respondent (Domain Registrant). <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>What I tried to do in my proposal was model that seed of compromise that was so successful almost 20 years ago in connection with the UDRP. As Kathy noted there are ADR components in the Privacy Shield that provide for the resolution of disputes. You are also correct that there are requirements that businesses pay for these services and there are no fees to Data Subjects, which creates the potential for abuse. That is why I have been looking to modify the JAMS ADR rules to perhaps find a middle ground that balances the respect rights of the Data Subject and Controller/Processor.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>In speaking with a number of privacy attorneys, Data Subject rarely get compensated for violations of their rights, although DPA can impose substantial fines against the Controller/Processor. The sweet spot I was looking at in connection with the ADR mechanism was something URS "like". I think this group and ICANN has done a really good job delineating under what set of circumstances a request can be legally made. In fact I think it would be constructive if a User enumerated at the time of the search what basis they were acting upon. The URS "like" ADR process would make use of templates for the complaint and response forms and NO formal written opinion by the panel just a summary decision.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>I am still surveying privacy professionals but I think a fine in the range of $250 to $500 for a violation of the terms of services would not be unreasonable. However, this is still at the spaghetti throwing stage. The other important mechanism is the need to have a disincentive for people to abuse the system by filing abusive requests. There may be the need for some type of speed bump mechanism to mitigate against abusive filings. Still noodling on this safeguard but would appreciate any group feedback.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>One of the hard lessons I have learned in ICANN is that it is easy to criticize but it is really hard to find a solution to both complex and simple problems.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Safe travels and I look forward to hopefully seeing you in Panama next week.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Best regards,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Michael <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre> <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>-----Original Message-----<o:p></o:p></pre>
<pre>From: Accred-Model <a href="mailto:accred-model-bounces@icann.org" moz-do-not-send="true"><accred-model-bounces@icann.org></a> On Behalf Of John R. Levine<o:p></o:p></pre>
<pre>Sent: Tuesday, June 19, 2018 1:32 PM<o:p></o:p></pre>
<pre>To: Kathy Kleiman <a href="mailto:kathy@kathykleiman.com" moz-do-not-send="true"><kathy@kathykleiman.com></a><o:p></o:p></pre>
<pre>Cc: <a href="mailto:accred-model@icann.org" moz-do-not-send="true">accred-model@icann.org</a><o:p></o:p></pre>
<pre>Subject: Re: [Accred-Model] Version 1.6 of the Accreditation and Access Model<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>It's great when there is actually an easy solution. At least for the <o:p></o:p></pre>
<pre>many US companies, law firms, cybersecurity firms, and others (and <o:p></o:p></pre>
<pre>this a huge part of the group seeking access), they should <o:p></o:p></pre>
<pre>"self-certify" to the EU-US Privacy Shield, via procedures set up by <o:p></o:p></pre>
<pre>the US Department of Commerce and Federal Trade Commission.<o:p></o:p></pre>
</blockquote>
<pre><o:p> </o:p></pre>
<pre>Well, at least until the EU courts kill privacy shield like they did Safe Harbor.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Banks and non-profits such as CAUCE are not eligible for Privacy Shield (they're not regulated by the FTC or DOT.) For small organizations the PS rules are extremely conplex and there's a mandatory annual payment to cover potential arbitration costs.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Can we back up and explain what problem this overcomplex "solution" is supposed to be solving here?<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Regards,<o:p></o:p></pre>
<pre>John Levine, <a href="mailto:johnl@iecc.com" moz-do-not-send="true">johnl@iecc.com</a>, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. <a href="https://jl.ly" moz-do-not-send="true">https://jl.ly</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Accred-Model mailing list<o:p></o:p></pre>
<pre><a href="mailto:Accred-Model@icann.org" moz-do-not-send="true">Accred-Model@icann.org</a><o:p></o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/accred-model" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/accred-model</a><o:p></o:p></pre>
</blockquote>
<table class="MsoNormalTable" style="width:213.75pt" width="285"
cellspacing="0" cellpadding="0" border="0">
<tbody>
<tr>
<td style="width:6.0pt;padding:0in 0in 0in 0in" width="8"
valign="top">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"> <o:p></o:p></span></p>
</td>
<td style="width:77.25pt;padding:0in 0in 0in
0in;vertical-align:center" width="103">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><a
href="http://www.wipo.int/gii/?utm_source=wipomail&utm_medium=signature&utm_campaign=gii2018"
moz-do-not-send="true"><span
style="text-decoration:none"><img
style="width:1.0763in;height:.618in"
id="_x0000_i1034"
src="http://www.wipo.int/export/sites/www/shared/pics/gii_2018_icon_sm.png"
alt="The image of the 2018 GII cover shows
crashing waves captured within the outline of
a battery cell, representing the raw power of
innovation." moz-do-not-send="true"
width="103" height="59" border="0"></span></a><o:p></o:p></span></p>
</td>
<td style="width:7.5pt;padding:0in 0in 0in 0in" width="10"
valign="top">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"> <o:p></o:p></span></p>
</td>
<td style="width:117.75pt;padding:0in 0in 0in 0in"
width="157" valign="top">
<p class="MsoNormal"><strong><span
style="font-size:15.0pt;font-family:"Helvetica",sans-serif;color:#054356">GLOBAL</span></strong><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><br>
</span><strong><span
style="font-size:15.0pt;font-family:"Arial",sans-serif;color:#054356">INNOVATION</span></strong><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><br>
</span><strong><span
style="font-size:15.0pt;font-family:"Arial",sans-serif;color:#054356">INDEX</span></strong><strong><span
style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#054356">
</span></strong><strong><span
style="font-size:15.0pt;font-family:"Arial",sans-serif;color:#2D9EC0">2018</span></strong><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p></o:p></span></p>
</td>
<td style="width:7.5pt;padding:0in 0in 0in 0in" width="10"
valign="top">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"> <o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;display:none"><o:p> </o:p></span></p>
<table class="MsoNormalTable" style="width:213.75pt" width="285"
cellspacing="0" cellpadding="0" border="0">
<tbody>
<tr>
<td style="width:6.0pt;padding:0in 0in 0in 0in" width="8"
valign="top">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"> <o:p></o:p></span></p>
</td>
<td style="padding:0in 0in 0in 0in">
<p class="MsoNormal"><span
style="font-family:"Arial",sans-serif;color:#054356">Energizing
the World with Innovation</span><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p></o:p></span></p>
</td>
<td style="width:7.5pt;padding:0in 0in 0in 0in" width="10"
valign="top">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"> <o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext;display:none"><o:p> </o:p></span></p>
<table class="MsoNormalTable" style="width:213.75pt" width="285"
cellspacing="0" cellpadding="0" border="0">
<tbody>
<tr>
<td style="width:6.0pt;padding:0in 0in 0in 0in" width="8"
valign="top">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"> <o:p></o:p></span></p>
</td>
<td style="width:84.75pt;padding:0in 0in 0in 0in"
width="113" valign="top">
<p class="MsoNormal"><span
style="font-size:8.5pt;font-family:"Arial",sans-serif;color:#2D9EC0">Launch
July 10</span><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p></o:p></span></p>
</td>
<td style="width:65.25pt;padding:0in 0in 0in 0in"
width="87" valign="top">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><a
href="http://www.wipo.int/gii/?utm_source=wipomail&utm_medium=signature&utm_campaign=gii2018"
moz-do-not-send="true"><span
style="font-size:8.5pt;font-family:"Arial",sans-serif;color:#2D9EC0;text-decoration:none">www.wipo.int/gii</span></a><o:p></o:p></span></p>
</td>
<td style="width:44.25pt;padding:0in 0in 0in 0in"
width="59" valign="top">
<p class="MsoNormal" style="text-align:right"
align="right"><span
style="font-size:8.5pt;font-family:"Arial",sans-serif;color:#2D9EC0">#GII2018</span><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p></o:p></span></p>
</td>
<td style="width:13.5pt;padding:0in 0in 0in 0in"
width="18" valign="top">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"> <o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<p> <o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif">World
Intellectual Property Organization Disclaimer: This
electronic message may contain privileged, confidential and
copyright protected information. If you have received this
e-mail by mistake, please immediately notify the sender and
delete this e-mail and all its attachments. Please ensure
all e-mail attachments are scanned for viruses prior to
opening or using. <o:p></o:p></span></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Accred-Model mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Accred-Model@icann.org">Accred-Model@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/accred-model">https://mm.icann.org/mailman/listinfo/accred-model</a>
</pre>
</blockquote>
</body>
</html>