Thank you, Jim, Rick, and Beth. This item will be added to the input tracking document here [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1d7KwQH6poIxra...>. Kind regards, Emily From: James Galvin <jgalvin@identity.digital> Date: Thursday, 1 December 2022 at 03:07 To: Emily Barabas <emily.barabas@icann.org> Cc: "gnso-tpr@icann.org" <gnso-tpr@icann.org> Subject: [Ext] Re: [GNSO-TPR] Input Due 30 November: Draft Revisions to Recommendations 2-9 The following comment is from the Registry Stakeholder Group review of the redline of Recommendations 1-9 The redlined text currently has the following proposed recommendation: Preliminary Recommendation xx: The Registry Operator MUST provide the Gaining Registrar’s IANA ID to the Losing Registrar, which will enable the Losing Registrar to provide this information in the [Losing FOA and] Notification of Transfer Completion. Registries note that the discussion text included guidance on how and when this should be done and we believe it is important to include this guidance in the recommendation. We propose the following revised text for consideration. Preliminary Recommendation xx: The Registry Operator MUST provide the Gaining Registrar’s IANA ID in the notification of a pending transfer request to the Losing Registrar, which will enable the Losing Registrar to provide this information in the [Losing FOA and] Notification of Transfer Completion. Note the insertion of the phrase “in the notification of a pending transfer request”. The RySG representatives are prepared to discuss this and answer any questions as needed. Thanks, Jim, Rick, and Beth On 16 Nov 2022, at 12:18, Emily Barabas wrote: Dear working group members, As discussed on yesterday’s call, staff had an action item to provide a redline revision of the Initial Report reflecting agreed updates to Recommendations 3-9 (see pages 18-24), as well as a strawman draft of the new Recommendation 2 and response to Charter Question A7. The redline is attached. The Recommendation 2 strawman is available here [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1e8iG6FmRD0M5V...>. Please carefully review these documents in coordination with the groups you represent. If you feel that there are items that need to be revised, please enter them here [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1d7KwQH6poIxra...>. For each item, please include: * Report version (the date listed in the header of the document) and applicable line numbers ( these are listed along the left margin of the document). * Name and group you represent: If multiple WG members represent a group, input should be in coordination with these other members. * Rationale: please provide a clear explanation for why you are proposing the revision. * Specific proposed revision: Provide the language you would like to see added/removed/edited. The deadline for submitting input is 30 November 2022. After the deadline, the working group will discuss the items submitted in the input document. Following review of those items, the text will be considered stable. Please do not hesitate to reach out with any questions about the review process. Kind regards, Caitlin, Julie, Berry, and Emily Emily Barabas Policy Development Support Senior Manager Internet Corporation for Assigned Names and Numbers (ICANN) Phone: +31 (0)6 84507976 www.icann.org<http://www.icann.org/> _______________________________________________ GNSO-TPR mailing list GNSO-TPR@icann.org https://mm.icann.org/mailman/listinfo/gnso-tpr