[GNSO-TPR] TPR WG Action Item: CORD Recommendations Worksheet

Mon Apr 1 20:16:32 UTC 2024

Hi Owen, that is a very helpful answer to my question.  Thank you!

[image: Logo]

Mike Rodenbaugh

address:

548 Market Street, Box 55819

San Francisco, CA 94104

email:

mike at rodenbaugh.com

phone:

+1 (415) 738-8087
*WORLD TRADEMARK REVIEW "WTR 1000" Top Global TM Counsel*
*2012 to present
[Book a Meeting <https://www.cloudhq.net/meeting/mike@rodenbaugh.com>]*

On Fri, Mar 29, 2024 at 3:42 PM Owen Smigelski <owen.smigelski at namecheap.com>
wrote:

> Hi Mike,
>
> When the COR policy was implemented in 2016, it quickly became apparent
> that enabling/disabling privacy/proxy services would trigger the COR
> process. At the time, to transfer a domain name, a registrant would need to
> remove the P/P service prior to transfer to facilitate the gaining
> registrar obtaining the registrant’s email address for the gaining FOA. The
> COR was thus being triggered when the underlying customer information was
> not being changed, and that led to significant problems for registrars.
>
> The GNSO Council wrote to the ICANN Board on 1 December 2016 requesting
> that this obligation be deferred (
> https://www.icann.org/en/system/files/correspondence/bladel-to-crocker-01dec16-en.pdf),
> and on 21 December 2016 ICANN granted the deferral (
> https://www.icann.org/en/system/files/correspondence/crocker-to-bladel-21dec16-en.pdf
> ).
>
> The obligation to do the COR (or now CORD) process for enabling/disabling
> P/P services has not been a requirement for over six years. The proposed
> changes to the CORD to make this exemption part of the policy is just
> reflecting the longstanding environment (which in practice is just
> deferring enforcing the obligations). Nothing new will result.
>
> Please let me know if this answers your question, and whether you need
> additional information.
>
> Regards,
>
> Owen
>
> On Mar 29, 2024, at 09:55, Mike Rodenbaugh <mike at rodenbaugh.com> wrote:
>
> *CAUTION: **This email originated from outside the organization. Do not
> click links unless you can confirm the sender and know the content is safe.*
> To socialize this with our constituencies, it would be very helpful to
> have an Executive Summary of how the recommended policy changes the
> existing policy.  Does Staff have a draft of that please?
>
> I previously raised an issue on the list about privacy/proxy changes,
> challenging the notion that moving from an identifiable registrant to a P/P
> (or vice versa) would be a Material Change, and should trigger a
> Notification.  I do not believe there was ever any response on the list.  I
> foresee this will be an issue for the IPC, so. if anyone could briefly
> explain why such a change is recommended to be outside the scope of this
> new policy, that explanation would be very helpful and appreciated.
>
> Thank you,
> Mike
>
> [image: Logo]
> Mike Rodenbaugh
> address:
> 548 Market Street, Box 55819
> San Francisco, CA 94104
> email:
> mike at rodenbaugh.com
> phone:
> +1 (415) 738-8087
> *WORLD TRADEMARK REVIEW "WTR 1000" Top Global TM Counsel*
> *2012 to present
>   [Book a Meeting <https://www.cloudhq.net/meeting/7FBRTNackKNkI0OKKZgn>]*
>
>
> On Wed, Mar 27, 2024 at 4:41 PM Christian Wheeler <
> christian.wheeler at icann.org> wrote:
>
>> Dear WG Members,
>>
>>
>> We have reached an important point in our work where *we need feedback
>> from all working group members. *
>>
>>
>> We are nearing completion of our Group 1(b) Change of Registrant Data
>> recommendations, and we will be finalizing them over the next few weeks. *In
>> short, if you are unable to participate over the next 2-3 weeks, please
>> ensure your alternate(s) are available to participate* on your behalf so
>> that all representative groups share their perspectives on this important
>> topic.
>>
>>
>> The format under which we will be gathering feedback should be familiar
>> to many of you. Support Staff has compiled the draft preliminary
>> recommendations in this Group 1(b) Recommendations for Initial Report
>> worksheet
>> <https://docs.google.com/document/d/1_lZLOmNQJKqAsAqxHTv8W5TQeRIm58YvS4vCPIwEdbE/edit>.
>> The yellow highlighted text denotes text that Support Staff has edited
>> based on feedback from the last meeting.
>>
>>
>> By *Tuesday, 9 April**,* we ask that all Working Group members:
>>
>>
>>    1. Please *review the **draft preliminary recommendations*
>>    <https://docs.google.com/document/d/1_lZLOmNQJKqAsAqxHTv8W5TQeRIm58YvS4vCPIwEdbE/edit>* in
>>    detail*.
>>    2. Using the tables provided (starting on p.9 of the worksheet
>>    <https://docs.google.com/document/d/1_lZLOmNQJKqAsAqxHTv8W5TQeRIm58YvS4vCPIwEdbE/edit>),
>>    please *identify any recommendations you believe should be changed*.
>>    The tables contemplate levels of support (or lack of support):
>>
>>    1. Cannot live with the recommendation as written - this means that,
>>          unless significantly altered, your group cannot live with the text being
>>          included in the Initial Report
>>          2. Could live with, but would prefer a change
>>          3. Grammatical/typographical edits
>>          4. Support recommendation as written
>>
>>
>>
>>    3. If you do not agree with the current text or believe edits are
>>    necessary, please identify the category (can’t live with, could live with
>>    but prefer edited text, or grammatical change), and *propose
>>    alternate text*.
>>    4. If you can support the recommendation as written, please *also
>>    affirmatively indicate your support *in the green table.
>>    5. Please *provide your feedback by group*, rather than in an
>>    individual capacity.
>>
>>
>> We will be using the next 2-3 weeks to go over proposed updated text (if
>> any). We ask all groups to review the recommendations to ensure*you are
>> comfortable with the proposed text for purposes of inclusion in the Initial
>> Report. *
>>
>>
>> While we do plan to have additional time to review the comprehensive
>> report as a whole (including Group 1(a) and Group 2), *the time to raise
>> fundamental issues with the Group 1(b) text is now. *
>>
>>
>> Thank you for your attention and participation.
>>
>>
>> Best regards,
>>
>> Caitlin, Berry, Julie, Feodora, and Christian
>> _______________________________________________
>> GNSO-TPR mailing list
>> GNSO-TPR at icann.org
>> https://mm.icann.org/mailman/listinfo/gnso-tpr
>>
> ********************
> CAUTION:
> This email originated from outside the organization. Do not click
> links unless you can confirm the sender and know the content is safe.
> ********************
>
> _______________________________________________
> 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/20240401/d1434fa6/attachment-0001.html>