<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=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"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:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-CA link="#0563C1" vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span lang=EN-US>Hello all,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>This goes back to the question of what exactly is in scope for this phase 2a, and what problem we’re trying to solve.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>We already have Recommendation #13 from Phase 1 stating that (among other things) “the Registrar MUST provide an email address or a web form to facilitate email communication with the relevant contact,” so the requirement to provide a contact method, which may be an email address, has already been decided. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Specifics related to the web form around things like character limits and CAPTCHA are not in scope for 2a as they are unrelated to our instructions, as James pointed out. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Our duty here is not to determine if a relay email is required, or under what circumstances. Instead, we’re here to review the legal guidance and any specific proposals which offer methods to implement that email while addressing the issues raised in that guidance and of course adhering to relevant data protection obligations. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><br>Is it feasible for unique contacts to have a uniform anonymized email address? If so, should that be required when implementing an email address contact relay? That’s what we’re doing here, and we shouldn’t mix that up with questions around if a relay email is itself required or not, which are already determined. <o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><pre><span style='font-family:"Verdana",sans-serif'>-- <o:p></o:p></span></pre><pre><b><span style='font-family:"Verdana",sans-serif'>Sarah Wyld</span></b><span style='font-family:"Verdana",sans-serif'>, CIPP/E<o:p></o:p></span></pre><pre><span style='font-family:"Verdana",sans-serif'><o:p> </o:p></span></pre><pre><span style='font-family:"Verdana",sans-serif'>Policy & Privacy Manager<o:p></o:p></span></pre><pre><span style='font-family:"Verdana",sans-serif'>Tucows<o:p></o:p></span></pre><pre><span style='font-family:"Verdana",sans-serif'><a href="mailto:swyld@tucows.com">swyld@tucows.com</a> <o:p></o:p></span></pre><pre><span style='font-family:"Verdana",sans-serif'>+1.416 535 0123 Ext. 1392<o:p></o:p></span></pre><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></p><p class=MsoNormal><img border=0 width=100 height=21 style='width:1.0416in;height:.2187in' id="Picture_x0020_3" src="cid:image001.png@01D698B1.25CB4480"><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='border:none;padding:0cm'><b>From: </b><a href="mailto:vgreimann@key-systems.net">Volker Greimann</a><br><b>Sent: </b>January 18, 2021 8:21 AM<br><b>To: </b><a href="mailto:Brian.King@markmonitor.com">King, Brian</a><br><b>Cc: </b><a href="mailto:gnso-epdp-team@icann.org">gnso-epdp-team@icann.org</a><br><b>Subject: </b>Re: [Gnso-epdp-team] Contact Relays</p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>I think the main issue is not whether it is desirable, but whether it is feasible at all, in a way that _fully safeguards_ all affected parties.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><div><div><div><div><p class=MsoNormal><span lang=EN-US>-- <br>Volker A. Greimann<br>General Counsel and Policy Manager<br><b>KEY-SYSTEMS GMBH</b><br><br>T: +49 6894 9396901<br>M: +49 6894 9396851<br>F: +49 6894 9396851<br>W: </span><a href="http://www.key-systems.net/" target="_blank"><span lang=EN-US style='color:#1155CC'>www.key-systems.net</span></a><span lang=EN-US><br><br>Key-Systems GmbH is a company registered at the local court of Saarbruecken, Germany with the registration no. HR B 18835<br>CEO: Oliver Fries and Robert Birkner<br><br>Part of the CentralNic Group PLC (LON: CNIC) a company registered in England and Wales with company number 8576358.<br><br></span><span style='font-size:10.5pt;font-family:"Arial",sans-serif;color:black;background:#F8F9FA'>This email and any files transmitted are confidential and intended only for the person(s) directly addressed. If you are not the intended recipient, any use, copying, transmission, distribution, or other forms of dissemination is strictly prohibited. If you have received this email in error, please notify the sender immediately and permanently delete this email with any files that may be attached.</span></p></div></div></div></div></div><p class=MsoNormal><o:p> </o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Sun, Jan 17, 2021 at 11:28 PM King, Brian via Gnso-epdp-team <<a href="mailto:gnso-epdp-team@icann.org">gnso-epdp-team@icann.org</a>> wrote:</p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US>Hi James,<o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US>I’d like to understand your request a bit better. <o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US>For many IP purposes, having a reliable email address is necessary to facilitate communication with the RNH, especially since web forms have proven insufficient for many of us. To the IP folks, contactability is an important reason for our work on “the feasibility of requiring unique contacts to have a uniform anonymized <b>email address</b>” (Temp Spec, emphasis added). I was concerned (or hopefully confused) to hear the RrSG assert that email contact was not necessary for IP purposes – I’d think we could either take the IPC’s word on that, or attempt to understand each other better. <o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US>If we agree that some form of email address is needed, or that we need to understand each other better, let’s proceed accordingly. If not, I’d ask candidly whether we should expect the RrSG to join consensus on a (lawful) requirement to provide an email contact, if the RrSG position is that email is not necessary and the RrSG is unwilling to discuss it further. <o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US> <o:p></o:p></span></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;vertical-align:baseline'><b><span lang=EN-US style='font-size:10.0pt;color:black'>Brian J. King</span></b><span lang=EN-US style='font-size:10.0pt'><br><i><span style='color:black'>He/Him/His</span></i></span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;vertical-align:baseline'><span lang=EN-US style='font-size:10.0pt;color:black'>Head of Policy and Advocacy, Intellectual Property Group</span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;vertical-align:baseline'><span lang=EN-US style='font-size:10.0pt'><br><span style='color:black'>T +1 443 761 3726</span></span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;vertical-align:baseline'><u><span lang=EN-US style='font-size:10.0pt;color:#0563C1'><a href="http://clarivate.com" target="_blank">clarivate.com</a></span></u><span lang=EN-US style='font-size:10.0pt'></span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;vertical-align:baseline'><span lang=EN-US style='font-size:10.0pt'>Accelerating innovation</span><span lang=EN-US><o:p></o:p></span></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US> <o:p></o:p></span></p><div><div style='border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0cm 0cm 0cm;border-color:currentcolor currentcolor'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span lang=EN-US>From:</span></b><span lang=EN-US> Gnso-epdp-team <<a href="mailto:gnso-epdp-team-bounces@icann.org" target="_blank">gnso-epdp-team-bounces@icann.org</a>> <b>On Behalf Of </b>James M. Bladel<br><b>Sent:</b> Sunday, January 17, 2021 3:32 PM<br><b>To:</b> <a href="mailto:gnso-epdp-team@icann.org" target="_blank">gnso-epdp-team@icann.org</a><br><b>Subject:</b> [Gnso-epdp-team] Contact Relays<o:p></o:p></span></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US>Hi folks –<o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US>On last Thursday’s call, we spent a chunk of time discussing the merits/efficacy of various Registrar implementations of the Contact Relay requirement. <o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US>In my view, this is one of htose topics that our group can’t resist debating, and yet it is not within scope for our work in Phase 2A. Our calendar is extremely tight, and I would ask everyone (myself included) to try and avoid these “catnip” topics that burn a lot of call time, but ultimately don’t end up anywhere.<o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US><br>Thanks—<o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US><br>J.<o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US> <o:p></o:p></span></p></div><div><p style='line-height:8.0pt'><span lang=EN-US style='font-size:8.0pt;color:dimgray'>Confidentiality note: This e-mail may contain confidential information from Clarivate. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this e-mail is strictly prohibited. If you have received this e-mail in error, please delete this e-mail and notify the sender immediately. <o:p></o:p></span></p></div></div></blockquote></div><p class=MsoNormal style='margin-left:4.8pt'>_______________________________________________<br>Gnso-epdp-team mailing list<br><a href="mailto:Gnso-epdp-team@icann.org" target="_blank">Gnso-epdp-team@icann.org</a><br><a href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</a><br>_______________________________________________<br>By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" target="_blank">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>