Hello all,

GoDaddy supports the strawman for Recommendation 2 as currently written at the following link (https://docs.google.com/document/d/1e8iG6FmRD0M5VlMUrmIedPw3burqfxLXQrkubxDJ3oQ/edit).

After several internal meetings, GoDaddy is uncomfortable with the fact that once a TAC is produced for the registrant it can fall into the wrong hands through various scenarios. The losing FOA provides a final chance for the Registrant to stop the transfer if the TAC has been compromised. Keeping the losing FOA also requires no system changes and does not require registrant re-education. The registrant will be provided the Registrar IANA ID which can be used to determine the legitimacy of the transfer. The registrant will be able to keep the final transfer decision with the proposed strawman.

Thanks,

Jody Kolker

From: GNSO-TPR <gnso-tpr-bounces@icann.org> On Behalf Of Emily Barabas
Sent: Wednesday, November 16, 2022 11:18 AM
To: gnso-tpr@icann.org
Subject: [GNSO-TPR] Input Due 30 November: Draft Revisions to Recommendations 2-9

Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@.

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.

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. 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