<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="">Hi Steve<div class=""><br class=""></div><div class="">Nameserver change can happen at any time during the registration. It often happens when a registrant transfers the domain but not always.</div><div class=""><br class=""></div><div class="">In the company I work for we have supplied a free dns service in Denmark for the past 20 years. The DNS service keeps running no matter how you wish to transfer your domains from registrar to registrar since the DNS service is not connected to the domain registrar service in any way. In another brand of the company group the domain is often linked to a hosting account and the nameservers would change when the domain is transferred since the domain should be pointed to the new hosting account that the transfer was intended for.</div><div class=""><br class=""></div><div class="">There is many different business model and we should be sure not to lock down ICANN policies down to what most people do, but instead make sure they are open enough so they would work for everyone, everywhere.</div><div class=""><br class=""></div><div class="">The scope of this PDP is and should be limited to the domain registration transfer process.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Kind regards</div><div class="">Kristian Ørmen</div><div class=""><br class=""></div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 18 May 2021, at 03.56, Steve Crocker <<a href="mailto:steve@shinkuro.com" class="">steve@shinkuro.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#0000ff">Min Feng,</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#0000ff"><br class=""></div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#0000ff">Thanks for your email. Yes, the gaining registrar can provide concurrent DNS service in advance of the transfer. For an unsigned zone, this is helpful. However, this will likely not work well for a signed zone. In order to guarantee continuity of service, i.e. both resolution and validation, the name servers and the key(s) of the gaining DNS service have to be added to the losing DNS service.</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#0000ff"><br class=""></div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#0000ff">It's understandable the losing DNS operator might not be interested in cooperating with this transition. However, there is another way to look at the process. Some customers will be interested in having two or more DNS operators serve their zone. Therefore, the first part of the transfer process is the same for both adding a new operator and transferring to a new operator. Once both operators have the zone in operation, the customer may leave both in operation for an extended period of time or they may choose to fold down the old operation.</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#0000ff"><br class=""></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 class=""></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, May 17, 2021 at 9:46 PM <a href="mailto:registrar@22.cn" class="">registrar@22.cn</a> <<a href="mailto:registrar@22.cn" class="">registrar@22.cn</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="">
<div class=""><span class=""></span>Hi Steve,</div><div class=""><br class=""></div><div class=""> My suggestion is that when the registrant moves their registration to another registrars, as the gaining registrar, it should be able to allow the registrant to use the current DNS service during the inter-registrars transfer process or after the inter-registrars transfer is completed, then it can be solved and without a disruption in resolution. In my opinion, this is not a complicated function. Thanks. </div><div class=""><br class=""></div><div class="">Best regards,</div><div class="">Min Feng</div>
<div class=""><br class=""></div><hr style="width:210px;height:1px" size="1" align="left" class="">
<div class=""><span class=""><div style="margin:10px" class=""><div class=""><font face="verdana" class=""><span style="font-size:13.3333px;line-height:20px" class="">International Affairs Team</span></font></div><div class=""><font face="verdana" class=""><span style="font-size:13.3333px;line-height:20px" class="">22Net, Inc</span></font></div><div class=""><font face="verdana" class=""><span style="font-size:13.3333px;line-height:20px" class="">Phone: +86-571-88276021</span></font></div><div class=""><font face="verdana" class=""><span style="font-size:13.3333px;line-height:20px" class="">Fax: +86-571-88276022</span></font></div><div class=""><font face="verdana" class=""><span style="font-size:13.3333px;line-height:20px" class="">Address: 11/F,Bldg No.2, Hangzhou Internet Innovation Pioneer Park, No.176 Zixia Street, Hangzhou, Zhejiang, China</span></font></div><div class=""><font face="verdana" class=""><span style="font-size:13.3333px;line-height:20px" class="">Post code:310030</span></font></div></div></span></div>
<blockquote style="margin-top:0px;margin-bottom:0px;margin-left:0.5em;margin-right:inherit" class=""><div class=""> </div><div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(181,196,223);padding:3pt 0cm 0cm" class=""><div style="padding: 8px; font-size: 12px; font-family: tahoma; background-color: rgb(239, 239, 239);" class=""><div class=""><b class="">From:</b> <a href="mailto:steve@shinkuro.com" target="_blank" class="">Steve Crocker</a></div><div class=""><b class="">Date:</b> 2021-05-18 09:01</div><div class=""><b class="">To:</b> <a href="mailto:owen.smigelski@namecheap.com" target="_blank" class="">Owen Smigelski</a></div><div class=""><b class="">CC:</b> <a href="mailto:gnso-tpr@icann.org" target="_blank" class="">gnso-tpr@icann.org</a></div><div class=""><b class="">Subject:</b> Re: [GNSO-TPR] Concurrent changes; transfer of DNS service</div></div></div><div class=""><div class="gmail-m_-118442647597404309FoxDiv20210518093005241100"><div dir="ltr" class=""><div dir="ltr" class=""><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)">Owen,</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)"><br class=""></div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)">Thanks. The touchstone for me is whether a registrant can successfully transfer his registration from one registrar to another. With respect to the registrant's DNS service, I believe this is most often provided free of charge by the registrar as part of the registrar's service. As a consequence, when the registrant moves their registration to another registrar, they will also have to move their DNS service. As things stand, I believe this often means there will be a disruption in resolution. And for a signed zone, this also means a disruption in validation.</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)"><br class=""></div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)">If I understand your point, you're saying because this was not raised in the issues report, it's not in scope for this PDP. Putting these points together, the goal for this PDP is to reach consensus on how a registrant can transfer their registration from one registrar to another with the understanding they will likely not be able to sustain uninterrupted service.</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)"><br class=""></div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)">Steve</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)"><br class=""></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, May 17, 2021 at 8:49 PM Owen Smigelski via GNSO-TPR <<a href="mailto:gnso-tpr@icann.org" target="_blank" class="">gnso-tpr@icann.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="">Hi Steve,<div class=""><br class=""></div><div class="">Regarding inter-registrar transfers, that is covered by the Temp Spec (specifically Appendix G, Section 1.2). I do not think it needs to be tied to the inter-registrant process due to the post-Temp Spec transfer process due to limited registrant data in the RDDS. </div><div class=""><br class=""></div><div class="">While I think the other issues you raise are worthy of consideration, they are outside of the scope for Phase 1a: gaining/losing FOA, auth-code management, and Wave 1, Recommendation 27. Looking ahead, I do not see them in the other phases as well. While I appreciate a desire for a holistic review, this PDP is bound by its charter which is based upon concerns raised in the issues report (which did not mention those items). We need to be wary of scope creep to ensure that we can timely focus on and resolve the items identified in our charter. </div><div class=""><br class=""></div><div class="">Regards,</div><div class=""><br class=""></div><div class="">Owen</div><div class=""><div class=""><br class=""><blockquote type="cite" style="margin-top:0px" class=""><div class="">On May 16, 2021, at 20:53, Steve Crocker <<a href="mailto:steve@shinkuro.com" target="_blank" class="">steve@shinkuro.com</a>> wrote:</div><br class=""><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)" class="">On the call Friday, I commented that a change of registrar may also require a change in DNS service at the same time. I also asked if the distinction between inter-registrant and inter-registrant mentioned in the charter covered the case where both the registrant and registrar were changing at the same time.</div><div style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)" class=""><br class=""></div><div style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)" class="">Attached is a note digging into these cases. In brief, I recommend consideration of both the one-at-a-time changes AND full understanding of how to make multiple changes.</div><div style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)" class=""><br class=""></div><div style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)" class="">Thanks,</div><div style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)" class=""><br class=""></div><div style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)" class="">Steve</div><div style="font-family:arial,sans-serif;font-size:small;color:rgb(0,0,255)" class=""><br class=""></div></div><div class="gmail_quote"></div></div>
<span id="gmail-m_-118442647597404309gmail-m_-8412056280012638031cid:f_kos2ht5c0" class=""><Consideration of Multiple Changes and the Inclusion of DNS Operations v2.docx></span>_______________________________________________<br class="">GNSO-TPR mailing list<br class=""><a href="mailto:GNSO-TPR@icann.org" target="_blank" class="">GNSO-TPR@icann.org</a><br class=""><a href="https://mm.icann.org/mailman/listinfo/gnso-tpr" target="_blank" class="">https://mm.icann.org/mailman/listinfo/gnso-tpr</a></div></blockquote></div><br class=""></div></div>_______________________________________________<br class="">
GNSO-TPR mailing list<br class="">
<a href="mailto:GNSO-TPR@icann.org" target="_blank" class="">GNSO-TPR@icann.org</a><br class="">
<a href="https://mm.icann.org/mailman/listinfo/gnso-tpr" rel="noreferrer" target="_blank" class="">https://mm.icann.org/mailman/listinfo/gnso-tpr</a></blockquote></div></div>
</div></div></blockquote>
</div></blockquote></div>
_______________________________________________<br class="">GNSO-TPR mailing list<br class=""><a href="mailto:GNSO-TPR@icann.org" class="">GNSO-TPR@icann.org</a><br class="">https://mm.icann.org/mailman/listinfo/gnso-tpr</div></blockquote></div><br class=""></div></body></html>