<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#0000ff">Volker,</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#0000ff"><br></div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#0000ff">I'm certainly not suggesting ICANN *regulate* hosting and mail services. Hosting and mail services are almost always sold as separate services. DNS is usually provided for free. Further, DNS is a supporting service, not a user service.</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#0000ff"><br></div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#0000ff">But the implied sense of your question is that we're talking about ICANN *regulating* DNS service. I think that's too narrow of an interpretation. ICANN's interest, and, indeed what everyone's interest should be, is for users to receive reliable and safe service. DNS service falls into a bit of a gray area because it's often supplied by the registrar at no additional cost and hence intimately entangled in the registration service. This is helpful to the registrants, so that's good. But it also means it comes into play during a transfer.</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#0000ff"><br></div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#0000ff">The basic proposition, which I think everyone here is working towards, is that registrars should work cooperatively to provide a smooth transition during transfers. In those cases where the registrar is providing DNS service, this means working cooperatively to provide smooth transition of the DNS service during transfers.</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#0000ff"><br></div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#0000ff">Thanks,</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#0000ff"><br></div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#0000ff">Steve</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#0000ff"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jun 23, 2021 at 3:43 PM Volker Greimann <<a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi Steve,</div><div><br></div><div>with regard to registrar services, DNS services are ancillary services at best and mostly fall outside of the ICANN mandate. Many registrants do not use the free DNS services provided by many registrars but third party services. Yes, it is true that many registrants do use the services of their registrar, and that sloppy planning of a migration can lead to outages, but that is not a service that ICANN regulates, or should regulate. <br></div><div>The same issues apply when the losing registrar provides hosting or mail services after all. If not done well, there will be outages.</div><div><br></div><div>Are you suggesting ICANN should regulate hosting and mail services as well?<br></div></div></blockquote><div><br></div><div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)"></div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div></div><div><div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><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/" style="color:rgb(17,85,204)" target="_blank"><span lang="EN-US">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-family:Roboto,sans-serif;font-size:14px;white-space:pre-wrap;background-color:rgb(248,249,250)">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></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jun 23, 2021 at 8:54 PM Steve Crocker <<a href="mailto:steve@shinkuro.com" target="_blank">steve@shinkuro.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)">Volker,</div><div style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)"><br></div><div style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)">If the registrar is also supplying the DNS service and the registrant initiates a change of registrar, the existing registrar will stop providing the DNS service. Therefore, the registrant is forced to change DNS service as part of changing registrars. If the registrant also wishes for the DNS service to continue to work during the transition, some careful coordination between the two DNS operations is required.</div><div style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)"><br></div><div style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)">Steve</div><div style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jun 23, 2021 at 2:08 PM Volker Greimann <<a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">I keep wondering what DNS settings and operations have to do with transfers in the first place. Surely the correct DNS settings are the responsibility of the registrant?</div><div dir="auto">Volker</div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed 23. Jun 2021 at 19:54, Steve Crocker <<a href="mailto:steve@shinkuro.com" target="_blank">steve@shinkuro.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)">Emily, et al,</div><div style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)"><br></div><div style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)">I have added some words related to coordination of DNS operations during a change of registrar. I was not able to edit the document directly via Google docs, so I downloaded the document and inserted changes. Tracking is turned on. I inserted my suggested changes between "c" and "d" so I used the letter x.</div><div style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)"><br></div><div style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)">I believe this belongs in this phase, 1a, because phase 1b looks like it's focused specifically on a change of registrant. The question of coordination of DNS operation could be relevant during a change of registrant but will be much more likely to be relevant during a change of registrar without a change of registrant.</div><div style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)"><br></div><div style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)">Thanks,</div><div style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)"><br></div><div style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)">Steve</div><div style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jun 23, 2021 at 6:08 AM Emily Barabas <<a href="mailto:emily.barabas@icann.org" target="_blank">emily.barabas@icann.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="en-BE">
<div>
<p class="MsoNormal"><span lang="EN-US">Dear Working Group members,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span lang="EN-US">Tomorrow,</span></b><b><span lang="EN-US"> Thursday, 24 June is the last day to suggest edits to the outreach letter
</span></b><span lang="EN-US">to SO/AC/SG/Cs: </span><a href="https://urldefense.com/v3/__https:/drive.google.com/file/d/1MsaU6sc3TU3azo2-pCWW9A6GWJ0a7XzT/view?usp=sharing__;!!PtGJab4!vkE-FpvoDc1HIrtWnt7zsQUsfbk7Z5W7iLrcWdwh-7tlz3YJCzSsuurm11H3J8ZGLOgbLWgQHA$" target="_blank">https://drive.google.com/file/d/1MsaU6sc3TU3azo2-pCWW9A6GWJ0a7XzT/view?usp=sharing
[drive.google.com]</a><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><span lang="EN-US">As a point of clarification, the current task is to make sure that the text of the letter is acceptable and determine if any additional questions need to be asked of SO/AC/SG/Cs as part of this request for input beyond
the listed charter questions. Once the WG has finalized the letter, it will be sent to SO/AC/SG/Cs who will have approximately five weeks to respond. Please feel free to reach out with any questions.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Kind regards,</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US">Emily, Julie, Caitlin, and Berry</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div style="border-color:rgb(181,196,223) currentcolor currentcolor;border-style:solid none none;border-width:1pt medium medium;padding:3pt 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:12pt;color:black">From: </span></b><span style="font-size:12pt;color:black">GNSO-TPR <<a href="mailto:gnso-tpr-bounces@icann.org" target="_blank">gnso-tpr-bounces@icann.org</a>> on behalf of Emily Barabas <<a href="mailto:emily.barabas@icann.org" target="_blank">emily.barabas@icann.org</a>><br>
<b>Date: </b>Monday, 21 June 2021 at 11:39<br>
<b>To: </b>"<a href="mailto:gnso-tpr@icann.org" target="_blank">gnso-tpr@icann.org</a>" <<a href="mailto:gnso-tpr@icann.org" target="_blank">gnso-tpr@icann.org</a>><br>
<b>Subject: </b>[GNSO-TPR] Reminder - Deadline for feedback 24 June: Draft outreach document requesting early input from SO/AC/SG/Cs</span><span style="font-size:12pt;color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal"><span lang="EN-US">Dear Working Group members,</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US">As a reminder, if you would like suggest additional questions to include in the request for early input to SO/AC/SG/Cs,
<b>please add these questions to the Google Doc no later than this</b> <b>Thursday, 24 June</b>:
</span><a href="https://urldefense.com/v3/__https:/drive.google.com/file/d/1MsaU6sc3TU3azo2-pCWW9A6GWJ0a7XzT/view?usp=sharing__;!!PtGJab4!vkE-FpvoDc1HIrtWnt7zsQUsfbk7Z5W7iLrcWdwh-7tlz3YJCzSsuurm11H3J8ZGLOgbLWgQHA$" target="_blank">https://drive.google.com/file/d/1MsaU6sc3TU3azo2-pCWW9A6GWJ0a7XzT/view?usp=sharing
[drive.google.com]</a> <u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US">Kind regards,</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US">Emily, Julie, Caitlin, and Berry</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US"> </span><u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<div style="border-color:rgb(181,196,223) currentcolor currentcolor;border-style:solid none none;border-width:1pt medium medium;padding:3pt 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:12pt;color:black">From: </span></b><span style="font-size:12pt;color:black">Emily Barabas <<a href="mailto:emily.barabas@icann.org" target="_blank">emily.barabas@icann.org</a>><br>
<b>Date: </b>Tuesday, 8 June 2021 at 19:28<br>
<b>To: </b>"<a href="mailto:gnso-tpr@icann.org" target="_blank">gnso-tpr@icann.org</a>" <<a href="mailto:gnso-tpr@icann.org" target="_blank">gnso-tpr@icann.org</a>><br>
<b>Subject: </b>Deadline for feedback 24 June: Draft outreach document requesting early input from SO/AC/SG/Cs</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<p class="MsoNormal"><span lang="EN-US">Dear Working Group members,</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US">As discussed on today’s call, the leadership team has prepared a draft outreach document to send to SO/AC/SG/Cs requesting early input on the topics within the TRP PDP’s charter. You can find the draft here:</span><u></u><u></u></p>
<p class="MsoNormal"><a href="https://urldefense.com/v3/__https:/drive.google.com/file/d/1MsaU6sc3TU3azo2-pCWW9A6GWJ0a7XzT/view?usp=sharing__;!!PtGJab4!vkE-FpvoDc1HIrtWnt7zsQUsfbk7Z5W7iLrcWdwh-7tlz3YJCzSsuurm11H3J8ZGLOgbLWgQHA$" target="_blank">https://drive.google.com/file/d/1MsaU6sc3TU3azo2-pCWW9A6GWJ0a7XzT/view?usp=sharing
[drive.google.com]</a> <u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US">If you would like to propose edits to the text or would like to suggest additional questions for early input to include in the document, please add comments directly into the Google Document. If anyone is unable to use
Google Drive, Word and PDF versions are attached for reference. You can also use Google Doc comments to provide feedback on questions or edits that have been proposed by other members.</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US"> </span><u></u><u></u></p>
<p class="MsoNormal"><b><span style="color:black" lang="EN-US">Please provide your input no later than 24 June 2021</span></b><span lang="EN-US">. The Working Group call on 29 June will be focused on finalizing this document for submission to the SO/AC/SG/Cs.
</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US">Kind regards,</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US">Emily, Julie, Caitlin, and Berry</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US"> </span><u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif;color:black" lang="EN-US">Emily Barabas</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif;color:black" lang="EN-US">Policy Manager, GNSO Policy Development Support</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif;color:black" lang="EN-US">Internet Corporation for Assigned Names and Numbers (ICANN)</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif;color:black" lang="EN-US">Phone: +31 (0)6 84507976</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif;color:black" lang="EN-US"><a href="http://www.icann.org/" title="http://www.icann.org/" target="_blank">www.icann.org</a></span><u></u><u></u></p>
<p class="MsoNormal"><span style="color:black"> </span><u></u><u></u></p>
</div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
_______________________________________________<br>
GNSO-TPR mailing list<br>
<a href="mailto:GNSO-TPR@icann.org" target="_blank">GNSO-TPR@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-tpr" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-tpr</a></blockquote></div>
_______________________________________________<br>
GNSO-TPR mailing list<br>
<a href="mailto:GNSO-TPR@icann.org" target="_blank">GNSO-TPR@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-tpr" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-tpr</a></blockquote></div></div>-- <br><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><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/" style="color:rgb(17,85,204)" target="_blank"><span lang="EN-US">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-family:Roboto,sans-serif;font-size:14px;white-space:pre-wrap;background-color:rgb(248,249,250)">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></div></div></div></div>
</blockquote></div>
</blockquote></div>
</blockquote></div></div>