<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Comic Sans MS";
panose-1:3 15 7 2 3 3 2 2 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
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.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";}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks Holly! Sort of like talking about travel plans to the high school reunion, but not actually being at the reunion yet. Makes sense to me.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Paul<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<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"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Holly Raiche [mailto:h.raiche@internode.on.net]
<br>
<b>Sent:</b> Thursday, January 28, 2016 4:20 PM<br>
<b>To:</b> McGrady, Paul D.<br>
<b>Cc:</b> Carlton Samuels; gnso-ppsai-pdp-wg@icann.org<br>
<b>Subject:</b> Re: [Gnso-ppsai-pdp-wg] PP transfer issue<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks Paul<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I was starting to worry about the continuing emails myself. What I believe we are doing is only getting heads around any next steps - at least clarifying not only what we agreed, but any outstanding issues that we didn’t settle. And I believe
what Mary was doing was reminding those of us who weren’t at the GNSO Council meeting of recommendations agreed upon that highlight further work - clearly done through the normal ICANN processes. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Certainly, from my point of view, and I’m sure others, the emails are informal discussion - maybe leading up to more work, but certainly not part of a GNSO PDP. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Holly<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">On 29 Jan 2016, at 9:05 am, McGrady, Paul D. <<a href="mailto:PMcGrady@winston.com">PMcGrady@winston.com</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I have a strictly procedural question: what is the role of the Issues Team after the PDP has been approved but before it gets underway? I’m a little concerned
that we are either modifying the issues (with no community opportunity to comment on any outcomes) or are starting the formal PDP proceedings without the rest of the team signed up and before it is actually commenced. </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">However, if this is just unofficial warm up to the formal PDP proceedings (or we are writing as hobbyists only), no worries. </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I hope you all are well.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Best,</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Paul</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span class="apple-converted-space"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> </span></span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><a href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org"><span style="color:purple">gnso-ppsai-pdp-wg-bounces@icann.org</span></a><span class="apple-converted-space"> </span>[<a href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org"><span style="color:purple">mailto:gnso-ppsai-pdp-wg-bounces@icann.org</span></a>]<span class="apple-converted-space"> </span><b>On
Behalf Of<span class="apple-converted-space"> </span></b>Holly Raiche<br>
<b>Sent:</b><span class="apple-converted-space"> </span>Thursday, January 28, 2016 3:52 PM<br>
<b>To:</b><span class="apple-converted-space"> </span>Carlton Samuels<br>
<b>Cc:</b><span class="apple-converted-space"> </span><a href="mailto:gnso-ppsai-pdp-wg@icann.org"><span style="color:purple">gnso-ppsai-pdp-wg@icann.org</span></a><br>
<b>Subject:</b><span class="apple-converted-space"> </span>Re: [Gnso-ppsai-pdp-wg] PP transfer issue</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">Hi Carlton<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">I think we can use the reasoning we used when discussing lawyers holding a domain name for their clients - but are not accredited. In that situation, the lawyer is the client - the registrant - a very different situation than when both
the originating and receiving registrars are accredited and P/P providers and covered by the same rules. We just need to work through what rules should be in place so that a beneficial registrant can transfer from one accredited P/P provider to another accredited
P/P provider (provided by a different registrar) because in both cases, there are requirements on registrars relating to collecting and checking on the accuracy of the Whois data. We started down that road, with useful discussion which, as Kathy points out
- needs more work.<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">Holly<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal">On 29 Jan 2016, at 4:18 am, Carlton Samuels <<a href="mailto:carlton.samuels@gmail.com"><span style="color:purple">carlton.samuels@gmail.com</span></a>> wrote:<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><br>
<br>
<br>
<o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Comic Sans MS"">Coming on the new dispensation, would it make a difference if both the originating and receiving Registrars are ICANN-accredited P/P providers? </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Comic Sans MS""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Comic Sans MS"">-Carlton</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><br>
==============================<br>
Carlton A Samuels<br>
Mobile: 876-818-1799<br>
<i><span style="color:#33CC00">Strategy, Planning, Governance, Assessment & Turnaround</span></i><br>
=============================<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">On Thu, Jan 28, 2016 at 12:37 AM, Holly Raiche <<a href="mailto:h.raiche@internode.on.net" target="_blank"><span style="color:purple">h.raiche@internode.on.net</span></a>> wrote:<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">Kathy/Mary<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">In a F2F (LA, I think) James talked through the problem. Under the RAA, registrars are responsible for the accuracy of the Whois (RDS) data. As yet, there isn’t a mechanism by which a registrar, taking on a P/P customer from another from
another registrar, can be assured that the Whois data relating to that new customer is accurate. So the short answer is that the new registrar cannot now take at face value the custom of a P/P customer without checking the accuracy of their Whois data. The
trouble with the recommendation below is that it fudges the issue. What we should be asking is the extent to which a P/P provider must verify new P/P data - and the extent to which that data can remain confidential in the transfer process. (not the best
wording, but we need to accommodate two apparently conflicting requirements: the confidentiality of the data of the P/P customer, and the requirement on registrars for the accuracy of the Whois data for all their customers.)<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="color:#888888"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="color:#888888">Holly</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="color:#888888"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">On 27 Jan 2016, at 3:45 am, Mary Wong <<a href="mailto:mary.wong@icann.org" target="_blank"><span style="color:purple">mary.wong@icann.org</span></a>> wrote:<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Hello Kathy and all,</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Thanks for your note; it reminded that I should have also included the further recommendation below in my previous email that noted two specific WG recommendations containing
references to the IRTP. This additional recommendation that I’m now pasting came about as a result of the WG’s email and live discussions, following the November email exchanges which you and others are referring to today:</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<blockquote style="margin-left:30.0pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><i><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">“The next review of the IRTP should include an analysis of the impact on P/P service customers, to ensure that adequate safeguards are in place as regards P/P service
protection when domain names are transferred pursuant to an IRTP process. Where a P/P service customer initiates a transfer of a domain name, the WG recognizes that a registrar should have the same flexibility that it has currently to reject incoming transfers
from any individual or entity, including those initiated by accredited P/P services. Nevertheless, the WG recommends that, in implementing those elements of the P/P service accreditation program that pertain to or that affect domain name transfers and in addition
to its specific recommendations contained in this Final Report, ICANN should perform a general “compatibility check” of each proposed implementation mechanism with the then-current IRTP.”</span></i><o:p></o:p></p>
</div>
</blockquote>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">I believe the context for this – and the other two IRTP-related recommendations approved in the Final Report that I’d pasted in my earlier email – is the WG’s recognition
that the effect of the IRTP changes on P/P services and their customers may need to be more directly addressed in the next review of the IRTP. This WG's final recommendations therefore addressed particular situations for which specific exceptions may be warranted
due, e.g., to the need to ensure continuing customer protection during the deaccreditation of a P/P service provider.</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Thanks and cheers</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Mary</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Mary Wong</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Senior Policy Director</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Internet Corporation for Assigned Names and Numbers (ICANN)</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Email: <a href="mailto:mary.wong@icann.org" target="_blank"><span style="color:#954F72">mary.wong@icann.org</span></a></span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Telephone:<span class="apple-converted-space"> </span><a href="tel:%2B1-603-5744889" target="_blank"><span style="color:purple">+1-603-5744889</span></a></span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<div>
<p class="MsoNormal"><b><span style="font-family:"Calibri","sans-serif"">From: </span></b><span style="font-family:"Calibri","sans-serif""><<a href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org" target="_blank"><span style="color:#954F72">gnso-ppsai-pdp-wg-bounces@icann.org</span></a>>
on behalf of Kathy Kleiman <<a href="mailto:kathy@kathykleiman.com" target="_blank"><span style="color:#954F72">kathy@kathykleiman.com</span></a>><br>
<b>Date: </b>Tuesday, January 26, 2016 at 23:08<br>
<b>To: </b>"<a href="mailto:gnso-ppsai-pdp-wg@icann.org" target="_blank"><span style="color:#954F72">gnso-ppsai-pdp-wg@icann.org</span></a>" <<a href="mailto:gnso-ppsai-pdp-wg@icann.org" target="_blank"><span style="color:#954F72">gnso-ppsai-pdp-wg@icann.org</span></a>><br>
<b>Subject: </b>Re: [Gnso-ppsai-pdp-wg] PP transfer issue</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Tx Mary, but I am still missing the impact of the discussion below on our PPSAI recommendations. If I want to transfer my domain name(s) from
Registrar A to Registrar B, both with Privacy and Proxy services, and to keep the data private as the transfer takes place (something we all agreed should happen) -- is there a problem, a limitation, a barrier? If so, how can we overcome it?<br>
<br>
Best, <br>
Kathy</span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">On 11/25/2015 2:04 PM, Mary Wong wrote:</span><o:p></o:p></p>
</div>
</div>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Hello everyone,</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Just a quick note for those WG members who may not be familiar with the IRTP, the changes to IRTP-C, or the implementation discussions – it may help to note the following
definition for the IRTP. I believe that James is referring to the registrar’s discretion in determining whether the purported change is or is not typographical in nature (see in particular the words I’ve highlighted in bold and italics). This is illustrated
by the examples given:</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">“Material Change” <b><i>means a non-typographical correction</i></b>. The following will be considered material changes:</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">(i) A change to the Registered Name Holder’s name or organization that does not appear to be a merely a typographical correction;</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">(ii) Any change to the Registered Name Holder’s name or organization that is accompanied by a change of address or phone number;</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">(iii) Any change to the Registered Name Holder’s email address.</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">The point about having discretion on this matter can be significant because, under the Policy, a Material Change to a registrant’s name, organizational address or email address <u>will</u> be
considered a Change of Registrant and thus trigger the 60-day lock. Hence, disabling/removal of a proxy service would trigger a lock – although the current Policy contemplates another possible instance of registrar discretion in such instances, i.e. a registrar
has the discretion (“may”) to permit the Registered Name Holder to opt out of the lock <u>prior</u> to the Change of Registrant request.</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">I’m far from an expert on the IRTP, but hopefully the above helps to explain the current proposed recommendation in the Final Report where, in referring to IRTP-C, the WG
is recommending that - in relation to de-accreditation - <i>"where a Change of Registrant (as defined under the IRTP) takes place during the process of de-accreditation of a proxy service provider, a registrar should lift the mandatory 60-day lock at the express
request of the beneficial user, provided the registrar has also been notified of the de–accreditation of the proxy service provider”</i>.</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Thanks and cheers</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Mary</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Mary Wong</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Senior Policy Director</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Internet Corporation for Assigned Names & Numbers (ICANN)</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Telephone:<span class="apple-converted-space"> </span><a href="tel:%2B1%20603%20574%204889" target="_blank"><span style="color:purple">+1 603 574 4889</span></a></span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Email: <a href="mailto:mary.wong@icann.org" target="_blank"><span style="color:#954F72">mary.wong@icann.org</span></a></span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<div>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From: </span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><<a href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org" target="_blank"><span style="color:#954F72">gnso-ppsai-pdp-wg-bounces@icann.org</span></a>>
on behalf of "James M. Bladel" <<a href="mailto:jbladel@godaddy.com" target="_blank"><span style="color:#954F72">jbladel@godaddy.com</span></a>><br>
<b>Date: </b>Wednesday, November 25, 2015 at 11:24<br>
<b>To: </b>Mike Zupke <<a href="mailto:Mike.Zupke@icann.org" target="_blank"><span style="color:#954F72">Mike.Zupke@icann.org</span></a>>, "Metalitz, Steven" <<a href="mailto:met@msk.com" target="_blank"><span style="color:#954F72">met@msk.com</span></a>>,
Volker Greimann <<a href="mailto:vgreimann@key-systems.net" target="_blank"><span style="color:#954F72">vgreimann@key-systems.net</span></a>>, "<a href="mailto:gnso-ppsai-pdp-wg@icann.org" target="_blank"><span style="color:#954F72">gnso-ppsai-pdp-wg@icann.org</span></a>"
<<a href="mailto:gnso-ppsai-pdp-wg@icann.org" target="_blank"><span style="color:#954F72">gnso-ppsai-pdp-wg@icann.org</span></a>>, Amy Bivins <<a href="mailto:amy.bivins@icann.org" target="_blank"><span style="color:#954F72">amy.bivins@icann.org</span></a>><br>
<b>Subject: </b>Re: [Gnso-ppsai-pdp-wg] PP transfer issue</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Hi folks. Just responding to Mike’s post from last Wednesday:</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">The question of P/P services triggering the “Change of Registrant” policy was not, IMO, sufficiently addressed by the IRTP WG. It was, however, the subject of extensive
discussion by the Implementation team, which ultimately determined that Registrar’s should have the discretion to determine whether or not this qualified as a Change of Registrant. For example, a Registrar may determine that adding/removing an affiliated P/P
service does NOT trigger the change of registrant policy, but that an unaffiliated P/P service contains too many unknowns, so explicit consent and a 60-day transfer lock may be warranted.</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">There are a number of practical scenarios where this flexibility is needed, including dealing with transfers as part of an aftermarket sale, implementation of a UDRP decision,
billing or payment failures for the P/P service, or termination due to a violation of the P/P services terms. I would also caution against recommendations of any particular WG (PPSAI) explicitly reverse recommendations or Implementation decisions of prior
WGs (IRTP-C) even before they have been adopted.</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">I don’t think this should materially affect the overall recommendations of PPSAI, nor do I see any incompatibilities with this and our recommendations. But happy to discuss
this point on our next call.</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Thanks—</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">J.</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<div>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From: </span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Mike Zupke <<a href="mailto:Mike.Zupke@icann.org" target="_blank"><span style="color:#954F72">Mike.Zupke@icann.org</span></a>><br>
<b>Date: </b>Wednesday, November 18, 2015 at 7:10 <br>
<b>To: </b>"Metalitz, Steven" <<a href="mailto:met@msk.com" target="_blank"><span style="color:#954F72">met@msk.com</span></a>>, Volker Greimann <<a href="mailto:vgreimann@key-systems.net" target="_blank"><span style="color:#954F72">vgreimann@key-systems.net</span></a>>,
James Bladel <<a href="mailto:jbladel@godaddy.com" target="_blank"><span style="color:#954F72">jbladel@godaddy.com</span></a>>, PPSAI WG <<a href="mailto:gnso-ppsai-pdp-wg@icann.org" target="_blank"><span style="color:#954F72">gnso-ppsai-pdp-wg@icann.org</span></a>>,
Amy Bivins <<a href="mailto:amy.bivins@icann.org" target="_blank"><span style="color:#954F72">amy.bivins@icann.org</span></a>><br>
<b>Subject: </b>RE: [Gnso-ppsai-pdp-wg] PP transfer issue</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Sorry for the delayed reply. We needed to consult with a few others.</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">In answer to Steve’s question (“Could you clarify whether the 60-day lock provision is part of the IRTP as a consensus policy, or part of the implementation
of that policy?”), the lock was included in the policy recommendations of IRTP WG C, which were adopted by the Council and Board. There was no mention of privacy or proxy services in that part of the recommendation. So our implementation of the IRTP C recommendations
was done “to the letter” of the recommendation, so to speak. I.e., no exception was made for privacy and proxy services. </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">We don’t believe the PPSAI working group is necessarily precluded from addressing questions about how the to-be-created type of PP registrations interact with
the Transfer Policy just because the Transfer Policy is an existing policy. PPSAI charter question B-3 (here: <a href="https://community.icann.org/x/ihLRAg" target="_blank"><span style="color:#954F72">https://community.icann.org/x/ihLRAg</span></a>) spoke
to having the WG “[c]larify how transfers, renewals, and PEDNR policies should apply.”</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">With regard to the point James made, during implementation of the IRTP C recommendations, we talked a good bit about how a proxy (or the beneficial customer)
could disable a proxy or privacy service in a world where consent of the other party would now be required in order to make the change in Whois. The solution to that question was to allow use of “designated agents” (see <a href="https://www.icann.org/resources/pages/transfer-policy-2015-09-24-en#II" target="_blank"><span style="color:#954F72">https://www.icann.org/resources/pages/transfer-policy-2015-09-24-en#II</span></a> at
1.1.2) to approve Changes of Registrant. I don’t believe the matter of exempting PP registrations from the 60 day lock was raised by the IRT or in public comment, although I do recall occasionally that people would reference the work of this WG as potentially
being necessary to addressing interaction with accredited PP service registrations and the Transfer Policy. </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hope that helps. </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Mike Zupke</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Director, Registrar Services</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Internet Corporation for Assigned Names and Numbers</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<div>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> <a href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org" target="_blank"><span style="color:#954F72">gnso-ppsai-pdp-wg-bounces@icann.org</span></a> [<a href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org" target="_blank"><span style="color:#954F72">mailto:gnso-ppsai-pdp-wg-bounces@icann.org</span></a>] <b>On
Behalf Of </b>James M. Bladel<br>
<b>Sent:</b> Wednesday, November 18, 2015 6:12 AM<br>
<b>To:</b> Volker Greimann <<a href="mailto:vgreimann@key-systems.net" target="_blank"><span style="color:#954F72">vgreimann@key-systems.net</span></a>>; <a href="mailto:gnso-ppsai-pdp-wg@icann.org" target="_blank"><span style="color:#954F72">gnso-ppsai-pdp-wg@icann.org</span></a><br>
<b>Subject:</b> Re: [Gnso-ppsai-pdp-wg] PP transfer issue</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Agree, and I thought this was also the final determination of the IRTP-C Implementation Review Team. It came up several times…</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Thanks-</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">J.</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<div>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From: </span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><<a href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org" target="_blank"><span style="color:#954F72">gnso-ppsai-pdp-wg-bounces@icann.org</span></a>>
on behalf of Volker Greimann <<a href="mailto:vgreimann@key-systems.net" target="_blank"><span style="color:#954F72">vgreimann@key-systems.net</span></a>><br>
<b>Date: </b>Wednesday, November 18, 2015 at 4:22 <br>
<b>To: </b>PPSAI WG <<a href="mailto:gnso-ppsai-pdp-wg@icann.org" target="_blank"><span style="color:#954F72">gnso-ppsai-pdp-wg@icann.org</span></a>><br>
<b>Subject: </b>Re: [Gnso-ppsai-pdp-wg] PP transfer issue</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">In all honesty, a removal of an accredited privacy service should not trigger the transfer lock as it does not imply an owner change. I am therefore
in favor of option 2)<br>
<br>
Best,<br>
<br>
Volker</span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Am 17.11.2015 um 19:01 schrieb Amy Bivins:</span><o:p></o:p></p>
</div>
</div>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Dear PPSAI WG Members:</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Here is the issue you asked staff to address by email today. This came to our attention after reflecting on the work done Friday by the “implementation issues” sub-team.</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">In short, disabling a proxy or privacy service will trigger the 60-day inter-registrar transfer lock required by IRTP C (which takes effect on 1 August 2016, <a href="https://www.icann.org/resources/pages/transfer-policy-2015-09-24-en" target="_blank"><span style="color:#954F72">https://www.icann.org/resources/pages/transfer-policy-2015-09-24-en</span></a> ).
Although applicable generally, this issue is of particular concern following de-accreditation of a privacy or proxy service (if transfer to another registrar is required to maintain privacy).</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Here are 3 things the WG could consider doing to address this:</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">1. Maintain the status quo and leave the 60-day IRTP C lock in place.<br>
2. Create an exception for Privacy and Proxy Service customers, so the 60 day IRTP C (inter-registrar transfer) lock doesn't apply when/if the customer changes or removes the PP service.<br>
3. Create an exception for PP users only if a PP service is de-accredited, so the IRTP C (inter-registrar transfer) lock can be lifted by the beneficial user if the registrar has been notified of de-accreditation.</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#333333;background:white"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#333333;background:white">Please let us know if you’d like to us to provide any further background. </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#333333;background:white"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#333333;background:white">Thank you!</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">Amy E. Bivins</span></b><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">Registrar Policy Services Manager</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">I</span></b><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">nternet <b>C</b>orporation for <b>A</b>ssigned <b>N</b>ames and <b>N</b>umbers (ICANN)</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri","sans-serif""><a href="mailto:amy.bivins@icann.org" target="_blank"><span style="color:#954F72">amy.bivins@icann.org</span></a></span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><b><i><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D">One World. One Internet.</span></i></b><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">Direct:<span class="apple-converted-space"> </span><a href="tel:%2B1%20%28202%29%20249-7551" target="_blank"><span style="color:purple">+1 (202) 249-7551</span></a></span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">Fax: <span class="apple-converted-space"> </span><a href="tel:%2B1%20%28202%29%20789-0104" target="_blank"><span style="color:purple">+1 (202) 789-0104</span></a></span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">801 17<sup>th</sup> Street NW, Suite 400</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">Washington, DC 20006</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><br>
<br>
<br>
</span><o:p></o:p></p>
</div>
<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" target="_blank"><span style="color:#954F72">Gnso-ppsai-pdp-wg@icann.org</span></a><a href="https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg" target="_blank"><span style="color:#954F72">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</span></a><o:p></o:p></pre>
</div>
</blockquote>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
<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.: <a href="tel:%2B49%20%280%29%206894%20-%209396%20901" target="_blank"><span style="color:purple">+49 (0) 6894 - 9396 901</span></a><o:p></o:p></pre>
<pre>Fax.: <a href="tel:%2B49%20%280%29%206894%20-%209396%20851" target="_blank"><span style="color:purple">+49 (0) 6894 - 9396 851</span></a><o:p></o:p></pre>
<pre>Email: <a href="mailto:vgreimann@key-systems.net" target="_blank"><span style="color:#954F72">vgreimann@key-systems.net</span></a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Web: <a href="http://www.key-systems.net/" target="_blank"><span style="color:#954F72">www.key-systems.net</span></a> / <a href="http://www.rrpproxy.net/" target="_blank"><span style="color:#954F72">www.RRPproxy.net</span></a><a href="http://www.domaindiscount24.com/" target="_blank"><span style="color:#954F72">www.domaindiscount24.com</span></a> / <a href="http://www.brandshelter.com/" target="_blank"><span style="color:#954F72">www.BrandShelter.com</span></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" target="_blank"><span style="color:#954F72">www.facebook.com/KeySystems</span></a><a href="http://www.twitter.com/key_systems" target="_blank"><span style="color:#954F72">www.twitter.com/key_systems</span></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/" target="_blank"><span style="color:#954F72">www.keydrive.lu</span></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.: <a href="tel:%2B49%20%280%29%206894%20-%209396%20901" target="_blank"><span style="color:purple">+49 (0) 6894 - 9396 901</span></a><o:p></o:p></pre>
<pre>Fax.: <a href="tel:%2B49%20%280%29%206894%20-%209396%20851" target="_blank"><span style="color:purple">+49 (0) 6894 - 9396 851</span></a><o:p></o:p></pre>
<pre>Email: <a href="mailto:vgreimann@key-systems.net" target="_blank"><span style="color:#954F72">vgreimann@key-systems.net</span></a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Web: <a href="http://www.key-systems.net/" target="_blank"><span style="color:#954F72">www.key-systems.net</span></a> / <a href="http://www.rrpproxy.net/" target="_blank"><span style="color:#954F72">www.RRPproxy.net</span></a><a href="http://www.domaindiscount24.com/" target="_blank"><span style="color:#954F72">www.domaindiscount24.com</span></a> / <a href="http://www.brandshelter.com/" target="_blank"><span style="color:#954F72">www.BrandShelter.com</span></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" target="_blank"><span style="color:#954F72">www.facebook.com/KeySystems</span></a><a href="http://www.twitter.com/key_systems" target="_blank"><span style="color:#954F72">www.twitter.com/key_systems</span></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/" target="_blank"><span style="color:#954F72">www.keydrive.lu</span></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>
</div>
</div>
</blockquote>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><br>
<br>
<br>
</span><o:p></o:p></p>
</div>
<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" target="_blank"><span style="color:#954F72">Gnso-ppsai-pdp-wg@icann.org</span></a><a href="https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg" target="_blank"><span style="color:#954F72">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</span></a><o:p></o:p></pre>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">_______________________________________________<br>
Gnso-ppsai-pdp-wg mailing list<br>
<a href="mailto:Gnso-ppsai-pdp-wg@icann.org" target="_blank"><span style="color:#954F72">Gnso-ppsai-pdp-wg@icann.org</span></a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg" target="_blank"><span style="color:#954F72">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</span></a></span><o:p></o:p></p>
</div>
</blockquote>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><br>
_______________________________________________<br>
Gnso-ppsai-pdp-wg mailing list<br>
<a href="mailto:Gnso-ppsai-pdp-wg@icann.org"><span style="color:purple">Gnso-ppsai-pdp-wg@icann.org</span></a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg" target="_blank"><span style="color:purple">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</span></a><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Verdana","sans-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.<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<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.</body>
</html>