<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Em 21 de set de 2018, à(s) 05:11:000, McGrady, Paul D. <<a href="mailto:PMcGrady@winston.com" class="">PMcGrady@winston.com</a>> escreveu:</div><br class="Apple-interchange-newline"><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-family: Calibri, sans-serif;" class="">Thanks Rafik. Thanks Darcy.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-family: Calibri, sans-serif;" class="">Darcy, to respond to your request, I’m not sure that I can provide much more background on this than the letter itself, which is pretty self-explanatory. We all know the history:<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: "Times New Roman", serif; text-indent: -0.25in;" class=""><span style="font-family: Symbol;" class=""><span class="">·<span style="font-style: normal; font-variant-caps: normal; font-weight: normal; font-stretch: normal; font-size: 7pt; line-height: normal; font-family: "Times New Roman";" class=""> <span class="Apple-converted-space"> </span></span></span></span><span style="font-family: Calibri, sans-serif;" class="">GNSO Community working on various policy development efforts to address WHOIS, including protecting privacy and allowing disclosure for legitimate purposes. .<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: "Times New Roman", serif; text-indent: -0.25in;" class=""><span style="font-family: Symbol;" class=""><span class="">·<span style="font-style: normal; font-variant-caps: normal; font-weight: normal; font-stretch: normal; font-size: 7pt; line-height: normal; font-family: "Times New Roman";" class=""> <span class="Apple-converted-space"> </span></span></span></span><span style="font-family: Calibri, sans-serif;" class="">GDPR comes into effect with deadline for fines.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: "Times New Roman", serif; text-indent: -0.25in;" class=""><span style="font-family: Symbol;" class=""><span class="">·<span style="font-style: normal; font-variant-caps: normal; font-weight: normal; font-stretch: normal; font-size: 7pt; line-height: normal; font-family: "Times New Roman";" class=""> <span class="Apple-converted-space"> </span></span></span></span><span style="font-family: Calibri, sans-serif;" class="">Certain Contracted Parties become concerned about fines and work with Staff to develop the Temp Spec. IPC and other folks who need disclosure for legitimate purposes practically beg Staff to include the<span class="Apple-converted-space"> </span><b class=""><u class="">details</u></b><span class="Apple-converted-space"> </span>of a framework for such disclosures.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: "Times New Roman", serif; text-indent: -0.25in;" class=""><span style="font-family: Symbol;" class=""><span class="">·<span style="font-style: normal; font-variant-caps: normal; font-weight: normal; font-stretch: normal; font-size: 7pt; line-height: normal; font-family: "Times New Roman";" class=""> <span class="Apple-converted-space"> </span></span></span></span><span style="font-family: Calibri, sans-serif;" class="">Staff produces a Temp Spec for the Board to implement which contains the<span class="Apple-converted-space"> </span><b class=""><u class="">requirement</u></b><span class="Apple-converted-space"> </span>for disclosures but little detail.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: "Times New Roman", serif; text-indent: -0.25in;" class=""><span style="font-family: Symbol;" class=""><span class="">·<span style="font-style: normal; font-variant-caps: normal; font-weight: normal; font-stretch: normal; font-size: 7pt; line-height: normal; font-family: "Times New Roman";" class=""> <span class="Apple-converted-space"> </span></span></span></span><span style="font-family: Calibri, sans-serif;" class="">Almost immediately, it is much more difficult to obtain needed disclosures for legitimate purposes, creating a safe haven for all sorts of Internet maladies. We understand that some do not believe in the existence of this problem, but like most real things, the existence of the problem isn’t dependent on a need for 100% of people to believe in them.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: "Times New Roman", serif; text-indent: -0.25in;" class=""><span style="font-family: Symbol;" class=""><span class="">·<span style="font-style: normal; font-variant-caps: normal; font-weight: normal; font-stretch: normal; font-size: 7pt; line-height: normal; font-family: "Times New Roman";" class=""> <span class="Apple-converted-space"> </span></span></span></span><span style="font-family: Calibri, sans-serif;" class="">Like Contracted Parties who saw an immediate problem and went to Staff seeking a Temp Spec while GNSO Community policy work was ongoing, IPC and others are working with Staff to (hopefully) get a Temp Spec in place addressing the details for a uniform/unified disclosure process while the Community work continues. Hopefully, the EPDP produces Policy that finally, after decades of work, solves all of the above.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-family: Calibri, sans-serif;" class="">To the extent that the policy development process is being undermined by the letter it seems to me that it has already been undermined by the request by certain Contracted Parties for the Temp Spec. That ship has sailed and, respectfully, certain of the Contracted Parties were at the helm. I know this may be unpopular email, but I think it is best not to dance around the issues or try to get cute in explaining why the letter was sent. I think as far as the EPDP is concerned, it seems like a non-issue, since as Rafik noted, the letter had no effect on the work of the EPDP. <o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><br class=""></div></div></div></blockquote><div><br class=""></div></div><br class=""><div class="">Paul, </div><div class=""><br class=""></div><div class="">Besides what has already been addressed by Michele that Contracted Parties long before Temp Spec asked (publicly as public forum records show) for guidance to be provided in due time (with no particular flavor of guidance being mentioned, like policy, contract amendment, temp spec etc.), what I need to communicate is that the use of a Temp Spec for the purposes it has already been used was already seen as an overstretch of something that was created for real emergencies (like the Conficker outbreak some years ago). A 2nd Temp Spec would likely face a barrage of responses including RfRs, IRPs and arbitration requests that make any such Temp Spec moot for longer than any PDP would take to complete. </div><div class=""><br class=""></div><div class="">That said, not doing a 2nd Temp Spec does not preclude a non-PDP solution. For instance, I still believe on a voluntary UAM developed by the larger registrars, LEAs and IP interests to have a greater chance of success than any policy effort could ever have. That model would also become a low-hanging fruit for a PDP because if there is something already in place encompassing 90% of domains, its adoption would turn out to be much easier. </div><div class=""><br class=""></div><div class="">This is not possible at this point due to the ongoing PDP discussions on Access, which are foundational in nature; but as soon as it concludes, I strongly recommend IPC and BC to reach out to the "Big Daddies / Large Cows" of the industry to build something that makes access requests scale. The unwilling uncooperative registrars, those that are 99.9% likely to not be RrSG members, are a different beast that ICANN's hammer is not big enough to pound; you can leave them to the men and women with badges and guns... </div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Rubens</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>