<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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"Times New Roman \,serif";
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;
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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma",sans-serif;
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma",sans-serif;
color:black;}
p.733a5379-4364-4e27-92bf-1e0d585669eb, li.733a5379-4364-4e27-92bf-1e0d585669eb, div.733a5379-4364-4e27-92bf-1e0d585669eb
{mso-style-name:733a5379-4364-4e27-92bf-1e0d585669eb;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Times New Roman",serif;
color:black;
font-weight:normal;
font-style:normal;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle27
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle28
{mso-style-type:personal-compose;
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 bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Thank you Volker. Yes, of course, I agree with all of that. And if we want to say that dotting the “i”s and crossing the “t”s in this context means including Val’s attestation language – such that a contracted
party can ignore a complaint that doesn’t do that – I’m fine with that.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">But I don’t think that’s what we’re talking about. We’re talking about
</span><span style="color:#1F497D">what form the document that delegates authority from the trademark/copyright owner to third-party agents should take, and who must sign it. But if the contracted party isn’t going to have to check, verify, or confirm that
form (and I don’t think there is any way they can, for the reasons that you and Michele mentioned yesterday), and in fact may never see it, that’s where I get confused. </span><span style="color:#1F497D"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><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="color:windowtext">From:</span></b><span style="color:windowtext"> gnso-ppsai-pdp-wg-bounces@icann.org [mailto:gnso-ppsai-pdp-wg-bounces@icann.org]
<b>On Behalf Of </b>Volker Greimann<br>
<b>Sent:</b> Wednesday, April 08, 2015 9:53 AM<br>
<b>To:</b> gnso-ppsai-pdp-wg@icann.org<br>
<b>Subject:</b> Re: [Gnso-ppsai-pdp-wg] PPSAI - Proposed language on attestation<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hi Todd,<br>
<br>
it fits the remit only if that becomes a trigger for a reveal process, i.e. ifconditions a, b, and c are met and d, e, and f are not present, g follows.<br>
<br>
ICANN cannot tell third parties what to do. But it can tell a contracted party what they must accept and what they can ignore. And if a request does not meet the requirements, no obligation of the provider to act in a certain way is triggered.
<br>
<br>
In other words, if the complainant dots the "i"s and crosses the "t"s, inaction by the provider could result in compliance action. If the complainant does not care to follow prescribed procedure, nothing the provider does results in compliance action.<br>
<br>
Volker<br>
<br>
<span style="font-size:12.0pt"><o:p></o:p></span></p>
<div>
<p class="MsoNormal">Am 08.04.2015 um 15:29 schrieb Williams, Todd:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="color:#1F497D">I’m sorry, I’m getting quite confused on this part.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Ultimately what we’re discussing is an accreditation policy for P/P Providers, correct? And one of the questions (the big question) that we’ve been discussing is when can/should/must accredited P/P Providers
disclose? We’ve developed a fairly detailed framework to answer that question (at least in the trademark and copyright context), and one component of that framework is that a request for disclosure must include the requisite attestation (and, for the record,
I like Val’s language as to what that attestation should look like). So far that all makes sense to me.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">But now we’re debating what form the document that delegates authority from the trademark/copyright owner to third-party agents should take (and who must sign it)? As Paul mentioned: how does that fit into our
remit? It doesn’t have anything to do with the P/P providers whom ICANN will be accrediting – right? As Kathy mentioned below, the forms will not “be delivered to the Provider and certainly not checked, verified or confirmed by the Provider.” But if that’s
the case – meaning that the P/P Provider is completely out of the loop – then how can ICANN regulate the content of that form (and who must sign it) by accrediting (or de-accrediting) a P/P Provider who has nothing to do with the form, isn’t checking, verifying,
or confirming it, and in fact may never see it? I guess I don’t see the contractual “hook” any more.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">To put it another way: the trademark/copyright owners have no contractual relationship with ICANN, right? So how can ICANN tell them what form to use when they choose to delegate authority (and who must sign
it)? And when we say that the forms should be “available for audit” – audit by whom? By ICANN? </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Bottom line: I would think that the most that we can do is perfect Val’s attestation language (and I like it the way that it is), and then leave it at that. Does that mean that there is a risk that the attestation
will be false in some cases? Yes. But can ICANN police false attestations through its contracting/accreditation of P/P Providers? I don’t see how. </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><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><span style="color:windowtext">From:</span></b><span style="color:windowtext">
<a href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org">gnso-ppsai-pdp-wg-bounces@icann.org</a> [<a href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org">mailto:gnso-ppsai-pdp-wg-bounces@icann.org</a>]
<b>On Behalf Of </b>Kathy Kleiman<br>
<b>Sent:</b> Tuesday, April 07, 2015 3:24 PM<br>
<b>To:</b> McGrady, Paul D.; <a href="mailto:gnso-ppsai-pdp-wg@icann.org">gnso-ppsai-pdp-wg@icann.org</a><br>
<b>Subject:</b> Re: [Gnso-ppsai-pdp-wg] PPSAI - Proposed language on attestation</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<p class="MsoNormal">Hi Paul, Hi Jim,<br>
No, the proposal would not apply to attorneys. The proposal is designed to apply to consultants and other outside entities not bound by the attorney-client relationship. We'll be certain to clarify in the next version. But tracing back to our discussions over
the last few weeks -- we have been concerned about parties *other than attorneys and officers of the company* making legal allegations and taking possession of private data. By the rules we live by, attorneys for the company (inside and outside counsel) and
officers of the corporation are bound by a number of ethical and fiduciary rules (depending on their position) that help ensure that they will operate a) within the scope of their expertise in making legal allegations of infringement and b) within the scope
of their authority to legally bind their companies to the limitations that the policy will require for the use of the revealed data.
<br>
<br>
What we are looking for is some documentation from the Trademark Owner/Copyright Owner that consultants and others similarly have a) the expertise to make the legal allegations of infringement, and b) have the legal authority to bind Procter & Gamble and others
to limitations on the use of the revealed data once received. <br>
<br>
The half page authorization and delegation to the consultant on letterhead from the Trademark Owner/Copyright Owner that I think Chris Pelling spoke of today would probably complement Val's self-attestation terms nicely. It does not have to be delivered to
the Provider and certainly not checked, verified or confirmed by the Provider, but it should be available for audit. And again, applies to those not bound by the other rules we have discussed...<br>
<br>
Best,<br>
Kathy<br>
<br>
<br>
:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="font-size:12.0pt">Kathy, would you proposal below apply to law firms as well? I will let the other service providers speak for themselves, but I really, really don’t think ICANN has any business attempting to interfere in
attorney/client relationships – that is clearly outside of our scope and ICANN’s remit.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Best,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Paul</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellpadding="0" width="100%" style="width:100.0%">
<tbody>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><b><span style="font-family:"Arial",sans-serif">Paul D. McGrady Jr.</span></b><o:p></o:p></p>
</td>
</tr>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#333333">Partner
</span></b><o:p></o:p></p>
</td>
</tr>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#333333">Chair, Trademark, Domain Names and Brand Enforcement Practice
</span></b><o:p></o:p></p>
</td>
</tr>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#333333">Winston & Strawn LLP<br>
35 W. Wacker Drive<br>
Chicago, IL 60601-9703</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#333333">D: +1 (312) 558-5963</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#333333">F: +1 (312) 558-5700</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#D8291C"><a href="http://www.winston.com/en/who-we-are/attorneys/mcgrady-paul-d.html"><span style="color:#D8291C;text-decoration:none">Bio</span></a> | <a href="http://www.winston.com/vcards/996.vcf"><span style="color:#D8291C;text-decoration:none">VCard</span></a> | <a href="mailto:pmcgrady@winston.com"><span style="color:#D8291C;text-decoration:none">Email</span></a> | <a href="http://www.winston.com"><span style="color:#D8291C;text-decoration:none">winston.com</span></a></span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span style="font-size:12.0pt"><img border="0" width="97" height="54" id="_x0000_i1025" src="cid:image001.jpg@01D071E3.89B4B260" alt="Winston & Strawn LLP"></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><o:p></o:p></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">
<a href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org">gnso-ppsai-pdp-wg-bounces@icann.org</a> [<a href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org">mailto:gnso-ppsai-pdp-wg-bounces@icann.org</a>]
<b>On Behalf Of </b>Kathy Kleiman<br>
<b>Sent:</b> Tuesday, April 07, 2015 8:19 AM<br>
<b>To:</b> <a href="mailto:gnso-ppsai-pdp-wg@icann.org">gnso-ppsai-pdp-wg@icann.org</a><br>
<b>Subject:</b> Re: [Gnso-ppsai-pdp-wg] PPSAI - Proposed language on attestation</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<p class="MsoNormal">Tx Val, <br>
Many of us think adding the statement you have drafted below would be very useful. Tx you! But still it does not get its hand around our full concer. What we seek is not the self-declaration of the Consultant, but the clear delegation of the Trademark/Copyright
Owner (e.g., Procter and Gamble). Where is the authorization? <br>
<br>
James Gannon, our newest member, has been working on some language that is perhaps a little long, and I am sure we can consolidate, but creates a "Letter of Delegation of Authority for Reveal Requests" that shows clearly that the Trademark/Copyright Owner at
the senior levels intended to delegate the authority for the legal judgments of infringements being made, and the limitations on the use of the revealed data being committed to. Provided to the Provider and, if necessary, the Customer.<br>
<br>
Here's the language. Best, Kathy<br>
--------------------------------------------------------------------------------------------------------------------<br>
<br>
<span style="font-size:13.5pt">In order to find a compromise between both sides of the aisle here I suggest the following possible solution:<br>
<br>
Policy Principle: Entities who issue requests pursuant to the Policy must ensure they have the delegated authority to do so. Where an entity requests a reveal of records and does not have the written authority to do so, the entity is deemed to be in non-compliance
with the policy. </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Detailed Policy Language for Principle:<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">The sitting corporate officers or general counsel of the requester organization issues a<span class="apple-converted-space"> </span>Letter of Delegation of<span class="apple-converted-space"> </span><span style="font-size:7.5pt">A</span>uthority<span class="apple-converted-space">
for Reveal Requests </span>to be held directly by anyone to whom the Reveal Request authority is delegated. <span class="apple-converted-space">
</span>This letter is separate to the general delegation of agency to work on the holders behalf. This letter would be specifically delegating the authority to issue Reveal Requests to P/P Service Providers.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">The letter<span class="apple-converted-space"> </span>would<span class="apple-converted-space"> </span>include the following provisions:<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">- Confirming and warranting the authorization of the delegator to appoint a delegate as an sitting Officer or General Counsel of the company or entity in question.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">- Specifying the nature of the delegation and the subject to whom the delegation is being given.
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">- For each individual that the delegation of authority applies, a letter so delegating that authority to the individual, by name, will be prepared. This letter will specify that
the delegation is specific to the process for requesting reveals of personal and potentially private and sensitive information of individuals, organizations and companies.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">- Affirming the authority and expertise of the delegated party to render legal judgements on trademark and copyright infringements.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">- Clearly and directly affirming the commitment of the delegating organization or company to be bound by the limits of the use of the Revealed Data as set out in the ICANN policy
now and as it might be modified in the future, and consistent with the laws of the jurisdiction in which the Proxy/Privacy Service Provider is incorporated.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">- Delegating Organization or Company expressly agrees to be answerable for any challenges that arise by virtue of the Delegatee's actions in preparing and responding to Reveal Requests,
and the Delegatee's handling of the Revealed Data, and agrees to be bound to challenge, review and/or lawsuit in any jurisdiction in which the Delegatee has agreed to be bound. <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">- Delegating Organization or Company consents Provide a copy of this Letter of Delegated Authority for Reveal Requests as a part of the Reveal Request process and as requested by
the Proxy/Privacy Service Provider.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">---<br>
<br>
<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Dear all:<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Following up on our productive discussion earlier this week, we’d like to offer a suggestion to modify the “attestation” provisions (II.A.6.c; II.B.7.d; and II.C.6.c) to require a statement by the requestor specifying his/her authority
for making the request, or basis for agency if he or she is not the rights holder. For example: “Where the signatory is not the rights holder, he/she must attest that he/she is an authorized representative of the rights holder, capable and qualified to evaluate
and address the matters involved in this request, and having the authority to make the representations and claims on behalf of the rights holder in the request.”<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">We could even spell out the statement for the signatory to make in conjunction with each request : “I attest that I am the rights holder / authorized representative of the rights holder, capable and qualified to evaluate and address the
matters involved in this request, and have the authority to make the representations and claims in this request.”<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">These statements of authority and agency are to be made in good faith, under the penalty of perjury – just like representations forming the basis for the request and the requestor’s promise to use the data disclosed only for limited enumerated
purposes – and the falsity of these statements would be redressable by the method(s) we agree on.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">We believe this approach fairly balances the considerations expressed by various WG members and look forward to your thoughts.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Best,<o:p></o:p></p>
<p class="MsoNormal">Val<o:p></o:p></p>
<p class="733a5379-4364-4e27-92bf-1e0d585669eb"> <o:p></o:p></p>
<p class="733a5379-4364-4e27-92bf-1e0d585669eb"><b><span style="font-size:10.0pt;font-variant:small-caps;color:#1F497D"><a href="http://www.sgrlaw.com/attorneys/profiles/sherman-valeriya/" title=""><span style="color:#1F497D;text-decoration:none">Valeriya Sherman</span></a> |</span></b><b><span style="font-size:9.0pt;font-family:"Arial",sans-serif">
Attorney at Law</span></b><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
<p class="733a5379-4364-4e27-92bf-1e0d585669eb"><span style="font-size:8.5pt;font-family:"Arial",sans-serif">202-973-2611
<em><span style="font-family:"Arial",sans-serif">phone</span></em><br>
202-263-4326 <em><span style="font-family:"Arial",sans-serif">fax</span></em><br>
<em><span style="font-family:"Arial",sans-serif"><a href="http://www.sgrlaw.com" title=""><span style="color:black;text-decoration:none">www.sgrlaw.com</span></a></span></em><i><br>
<em><span style="font-family:"Arial",sans-serif"><a href="mailto:vsherman@sgrlaw.com" title=""><span style="color:black;text-decoration:none">vsherman@sgrlaw.com</span></a></span></em></i></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
<p class="733a5379-4364-4e27-92bf-1e0d585669eb"><span style="font-size:8.5pt;font-family:"Arial",sans-serif">1055 Thomas Jefferson Street, N.W.<br>
Suite 400<br>
Washington, D.C. 20007</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
<p class="733a5379-4364-4e27-92bf-1e0d585669eb"><em><span style="font-size:8.5pt;font-family:"Arial",sans-serif">Ms. Sherman's practice is limited to matters before federal courts and before the United States Patent and Trademark Office.</span></em><i><span style="font-size:8.5pt;font-family:"Arial",sans-serif"><br>
<em><span style="font-family:"Arial",sans-serif">She is not admitted in the District of Columbia.</span></em></span></i><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
<br>
<br>
<br>
</span><o:p></o:p></p>
<p class="733a5379-4364-4e27-92bf-1e0d585669eb"><b><span style="font-size:10.0pt;font-variant:small-caps;color:#1F497D"><a href="http://www.sgrlaw.com"><span style="text-decoration:none"><img border="0" width="80" height="27" id="IMG1" src="cid:image002.jpg@01D071E3.89B4B260"></span></a> Smith,
Gambrell & Russell, LLP </span></b><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Arial",sans-serif">Confidentiality Notice<br>
This message is being sent by or on behalf of a lawyer. It is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged or confidential or otherwise legally exempt
from disclosure. If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately by e-mail and delete all
copies of the message.<br>
</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
<br>
<br>
<br>
<br>
</span><o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Gnso-ppsai-pdp-wg mailing list<o:p></o:p></pre>
<pre><a href="mailto:Gnso-ppsai-pdp-wg@icann.org">Gnso-ppsai-pdp-wg@icann.org</a><o:p></o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman ,serif",serif"><br>
The contents of this message may be privileged and confidential. Therefore, if this message has been received in error, please delete it without reading it. Your receipt of this message is not intended to waive any applicable privilege. Please do not disseminate
this message without the permission of the author. </span><o:p></o:p></p>
</blockquote>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman ,serif",serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
<br>
<br>
<o:p></o:p></span></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Gnso-ppsai-pdp-wg mailing list<o:p></o:p></pre>
<pre><a href="mailto:Gnso-ppsai-pdp-wg@icann.org">Gnso-ppsai-pdp-wg@icann.org</a><o:p></o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
<br>
<o:p></o:p></span></p>
<pre>-- <o:p></o:p></pre>
<pre>Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Mit freundlichen Grüßen,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Volker A. Greimann<o:p></o:p></pre>
<pre>- Rechtsabteilung -<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Key-Systems GmbH<o:p></o:p></pre>
<pre>Im Oberen Werk 1<o:p></o:p></pre>
<pre>66386 St. Ingbert<o:p></o:p></pre>
<pre>Tel.: +49 (0) 6894 - 9396 901<o:p></o:p></pre>
<pre>Fax.: +49 (0) 6894 - 9396 851<o:p></o:p></pre>
<pre>Email: <a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Web: <a href="http://www.key-systems.net">www.key-systems.net</a> / <a href="http://www.RRPproxy.net">www.RRPproxy.net</a><o:p></o:p></pre>
<pre><a href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a href="http://www.BrandShelter.com">www.BrandShelter.com</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:<o:p></o:p></pre>
<pre><a href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a><o:p></o:p></pre>
<pre><a href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Geschäftsführer: Alexander Siffrin<o:p></o:p></pre>
<pre>Handelsregister Nr.: HR B 18835 - Saarbruecken <o:p></o:p></pre>
<pre>Umsatzsteuer ID.: DE211006534<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Member of the KEYDRIVE GROUP<o:p></o:p></pre>
<pre><a href="http://www.keydrive.lu">www.keydrive.lu</a> <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>--------------------------------------------<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Should you have any further questions, please do not hesitate to contact us.<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>Volker A. Greimann<o:p></o:p></pre>
<pre>- legal department -<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Key-Systems GmbH<o:p></o:p></pre>
<pre>Im Oberen Werk 1<o:p></o:p></pre>
<pre>66386 St. Ingbert<o:p></o:p></pre>
<pre>Tel.: +49 (0) 6894 - 9396 901<o:p></o:p></pre>
<pre>Fax.: +49 (0) 6894 - 9396 851<o:p></o:p></pre>
<pre>Email: <a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Web: <a href="http://www.key-systems.net">www.key-systems.net</a> / <a href="http://www.RRPproxy.net">www.RRPproxy.net</a><o:p></o:p></pre>
<pre><a href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a href="http://www.BrandShelter.com">www.BrandShelter.com</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Follow us on Twitter or join our fan community on Facebook and stay updated:<o:p></o:p></pre>
<pre><a href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a><o:p></o:p></pre>
<pre><a href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>CEO: Alexander Siffrin<o:p></o:p></pre>
<pre>Registration No.: HR B 18835 - Saarbruecken <o:p></o:p></pre>
<pre>V.A.T. ID.: DE211006534<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Member of the KEYDRIVE GROUP<o:p></o:p></pre>
<pre><a href="http://www.keydrive.lu">www.keydrive.lu</a> <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
</div>
</body>
</html>