[GNSO-TPR] Concurrent changes; transfer of DNS service

Tue May 18 01:46:03 UTC 2021

Hi Steve,

    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. 

Best regards,
Min Feng

International Affairs Team
22Net, Inc
Phone: +86-571-88276021
Fax: +86-571-88276022
Address: 11/F,Bldg No.2, Hangzhou Internet Innovation Pioneer Park, No.176 Zixia Street, Hangzhou, Zhejiang, China
Post code:310030

From: Steve Crocker
Date: 2021-05-18 09:01
To: Owen Smigelski
CC: gnso-tpr at icann.org
Subject: Re: [GNSO-TPR] Concurrent changes; transfer of DNS service
Owen,

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.

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.

Steve

On Mon, May 17, 2021 at 8:49 PM Owen Smigelski via GNSO-TPR <gnso-tpr at icann.org> wrote:
Hi Steve,

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. 

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. 

Regards,

Owen

On May 16, 2021, at 20:53, Steve Crocker <steve at shinkuro.com> wrote:

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.

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.

Thanks,

Steve

<Consideration of Multiple Changes and the Inclusion of DNS Operations v2.docx>_______________________________________________
GNSO-TPR mailing list
GNSO-TPR at icann.org
https://mm.icann.org/mailman/listinfo/gnso-tpr

_______________________________________________
GNSO-TPR mailing list
GNSO-TPR at icann.org
https://mm.icann.org/mailman/listinfo/gnso-tpr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/gnso-tpr/attachments/20210518/6e9de2b3/attachment-0001.html>