[GNSO-TPR] Final Reminder - Deadline for feedback 24 June: Draft outreach document requesting early input from SO/AC/SG/Cs

Steve Crocker steve at shinkuro.com
Wed Jun 23 20:02:33 UTC 2021


Volker,

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.

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.

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.

Thanks,

Steve


On Wed, Jun 23, 2021 at 3:43 PM Volker Greimann <vgreimann at key-systems.net>
wrote:

> Hi Steve,
>
> 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.
> The same issues apply when the losing registrar provides hosting or mail
> services after all. If not done well, there will be outages.
>
> Are you suggesting ICANN should regulate hosting and mail services as well?
>





> --
> Volker A. Greimann
> General Counsel and Policy Manager
> *KEY-SYSTEMS GMBH*
>
> T: +49 6894 9396901
> M: +49 6894 9396851
> F: +49 6894 9396851
> W: www.key-systems.net
>
> Key-Systems GmbH is a company registered at the local court of
> Saarbruecken, Germany with the registration no. HR B 18835
> CEO: Oliver Fries and Robert Birkner
>
> Part of the CentralNic Group PLC (LON: CNIC) a company registered in
> England and Wales with company number 8576358.
>
> 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.
>
>
> On Wed, Jun 23, 2021 at 8:54 PM Steve Crocker <steve at shinkuro.com> wrote:
>
>> Volker,
>>
>> 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.
>>
>> Steve
>>
>>
>> On Wed, Jun 23, 2021 at 2:08 PM Volker Greimann <
>> vgreimann at key-systems.net> wrote:
>>
>>> 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?
>>> Volker
>>>
>>> On Wed 23. Jun 2021 at 19:54, Steve Crocker <steve at shinkuro.com> wrote:
>>>
>>>> Emily, et al,
>>>>
>>>> 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.
>>>>
>>>> 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.
>>>>
>>>> Thanks,
>>>>
>>>> Steve
>>>>
>>>>
>>>> On Wed, Jun 23, 2021 at 6:08 AM Emily Barabas <emily.barabas at icann.org>
>>>> wrote:
>>>>
>>>>> Dear Working Group members,
>>>>>
>>>>>
>>>>>
>>>>> *Tomorrow,** Thursday, 24 June is the last day to suggest edits to
>>>>> the outreach letter *to SO/AC/SG/Cs: https://drive.google.com/file/d/1MsaU6sc3TU3azo2-pCWW9A6GWJ0a7XzT/view?usp=sharing
>>>>> [drive.google.com]
>>>>> <https://urldefense.com/v3/__https:/drive.google.com/file/d/1MsaU6sc3TU3azo2-pCWW9A6GWJ0a7XzT/view?usp=sharing__;!!PtGJab4!vkE-FpvoDc1HIrtWnt7zsQUsfbk7Z5W7iLrcWdwh-7tlz3YJCzSsuurm11H3J8ZGLOgbLWgQHA$>
>>>>>
>>>>>
>>>>>
>>>>> 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.
>>>>>
>>>>>
>>>>>
>>>>> Kind regards,
>>>>>
>>>>>
>>>>>
>>>>> Emily, Julie, Caitlin, and Berry
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> *From: *GNSO-TPR <gnso-tpr-bounces at icann.org> on behalf of Emily
>>>>> Barabas <emily.barabas at icann.org>
>>>>> *Date: *Monday, 21 June 2021 at 11:39
>>>>> *To: *"gnso-tpr at icann.org" <gnso-tpr at icann.org>
>>>>> *Subject: *[GNSO-TPR] Reminder - Deadline for feedback 24 June: Draft
>>>>> outreach document requesting early input from SO/AC/SG/Cs
>>>>>
>>>>>
>>>>>
>>>>> Dear Working Group members,
>>>>>
>>>>>
>>>>>
>>>>> As a reminder, if you would like suggest additional questions to
>>>>> include in the request for early input to SO/AC/SG/Cs, *please add
>>>>> these questions to the Google Doc no later than this* *Thursday, 24
>>>>> June*: https://drive.google.com/file/d/1MsaU6sc3TU3azo2-pCWW9A6GWJ0a7XzT/view?usp=sharing
>>>>> [drive.google.com]
>>>>> <https://urldefense.com/v3/__https:/drive.google.com/file/d/1MsaU6sc3TU3azo2-pCWW9A6GWJ0a7XzT/view?usp=sharing__;!!PtGJab4!vkE-FpvoDc1HIrtWnt7zsQUsfbk7Z5W7iLrcWdwh-7tlz3YJCzSsuurm11H3J8ZGLOgbLWgQHA$>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Kind regards,
>>>>>
>>>>>
>>>>>
>>>>> Emily, Julie, Caitlin, and Berry
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> *From: *Emily Barabas <emily.barabas at icann.org>
>>>>> *Date: *Tuesday, 8 June 2021 at 19:28
>>>>> *To: *"gnso-tpr at icann.org" <gnso-tpr at icann.org>
>>>>> *Subject: *Deadline for feedback 24 June: Draft outreach document
>>>>> requesting early input from SO/AC/SG/Cs
>>>>>
>>>>>
>>>>>
>>>>> Dear Working Group members,
>>>>>
>>>>>
>>>>>
>>>>> 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:
>>>>>
>>>>> https://drive.google.com/file/d/1MsaU6sc3TU3azo2-pCWW9A6GWJ0a7XzT/view?usp=sharing
>>>>> [drive.google.com]
>>>>> <https://urldefense.com/v3/__https:/drive.google.com/file/d/1MsaU6sc3TU3azo2-pCWW9A6GWJ0a7XzT/view?usp=sharing__;!!PtGJab4!vkE-FpvoDc1HIrtWnt7zsQUsfbk7Z5W7iLrcWdwh-7tlz3YJCzSsuurm11H3J8ZGLOgbLWgQHA$>
>>>>>
>>>>>
>>>>>
>>>>> 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.
>>>>>
>>>>>
>>>>>
>>>>> *Please provide your input no later than 24 June 2021*. The Working
>>>>> Group call on 29 June will be focused on finalizing this document for
>>>>> submission to the SO/AC/SG/Cs.
>>>>>
>>>>>
>>>>>
>>>>> Kind regards,
>>>>>
>>>>>
>>>>>
>>>>> Emily, Julie, Caitlin, and Berry
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Emily Barabas
>>>>>
>>>>> Policy Manager, GNSO Policy Development Support
>>>>>
>>>>> Internet Corporation for Assigned Names and Numbers (ICANN)
>>>>>
>>>>> Phone: +31 (0)6 84507976
>>>>>
>>>>> www.icann.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>
>>> --
>>> --
>>> Volker A. Greimann
>>> General Counsel and Policy Manager
>>> *KEY-SYSTEMS GMBH*
>>>
>>> T: +49 6894 9396901
>>> M: +49 6894 9396851
>>> F: +49 6894 9396851
>>> W: www.key-systems.net
>>>
>>> Key-Systems GmbH is a company registered at the local court of
>>> Saarbruecken, Germany with the registration no. HR B 18835
>>> CEO: Oliver Fries and Robert Birkner
>>>
>>> Part of the CentralNic Group PLC (LON: CNIC) a company registered in
>>> England and Wales with company number 8576358.
>>>
>>> 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.
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/gnso-tpr/attachments/20210623/c4c4930c/attachment-0001.html>


More information about the GNSO-TPR mailing list