Yes, please. Lets add the new definition. On Monday, October 18, 2021, Sarah Wyld <swyld@tucows.com> wrote:
Thanks, all! I’m happy to use the new definition, assuming the note at the bottom of the slide will be updated to indicate the origin of it. No need to hide that we’ve already accomplished something 😊
--
*Sarah Wyld*, CIPP/E
Policy & Privacy Manager
Pronouns: she/they
swyld@tucows.com
+1.416 535 0123 Ext. 1392
*From: *Emily Barabas <emily.barabas@icann.org> *Sent: *October 18, 2021 3:15 AM *To: *James Galvin <jgalvin@donuts.email>; Sarah Wyld <swyld@tucows.com> *Cc: *gnso-tpr@icann.org *Subject: *Re: [Ext] Re: [GNSO-TPR] Proposed agenda for meeting #22 on Tuesday19 October2021 at 16:00 UTC
Hi Jim and everyone,
Thanks for the follow up. If the group prefers, we could use Jim’s new proposed definition from the working document in slide 8 of the ICANN72 deck. Here is the text Jim proposes: “A Transfer Authorization Code (TAC) is a token created by the registrar of record and provided upon request to the registrant or designated representative. The TAC is required to transfer a domain name from one Registrar to another registrar and when presented authorizes the transfer.”
If there are any objections, please share them on list.
Kind regards,
Emily
*From: *James Galvin <jgalvin@donuts.email> *Date: *Sunday, 17 October 2021 at 23:08 *To: *Sarah Wyld <swyld@tucows.com> *Cc: *Emily Barabas <emily.barabas@icann.org>, "gnso-tpr@icann.org" < gnso-tpr@icann.org> *Subject: *[Ext] Re: [GNSO-TPR] Proposed agenda for meeting #22 on Tuesday 19 October2021 at 16:00 UTC
Thanks for calling this out Sarah.
I wrote some new words for this definition expressly to deal with the issue of the use of identify. It might have been in a comment.
Emily, is that text still available?
Thanks,
Jim
On 15 Oct 2021, at 9:24, Sarah Wyld wrote:
Hi team
Reviewed the ICANN72 pdf, have a comment.
The page 8 definition of the AuthInfo code (“Unique code created by a registrar on a per-domain basis to identify the registrant of the domain name”) is not the definition we came up with, I think it’s pieces pulled together from the current Transfer Policy. Can this be marked on this slide as unofficial and not the long-term definition, with the source included, and a note that updating this definition is part of our group’s work? I just wouldn’t want this slide to lead anyone to think that this is our current working definition, should be used in the long-term, etc.
Thanks!
--
*Sarah Wyld*, CIPP/E
Policy & Privacy Manager
Pronouns: she/they
swyld@tucows.com
+1.416 535 0123 Ext. 1392
*From: *Emily Barabas <emily.barabas@icann.org> *Sent: *October 15, 2021 3:27 AM *To: *gnso-tpr@icann.org *Subject: *[GNSO-TPR] Proposed agenda for meeting #22 on Tuesday 19 October2021 at 16:00 UTC
Dear Working Group members,
Please find below the proposed agenda for the meeting scheduled to take place on Tuesday 19 October 2021 at 16:00 UTC.
Kind regards,
Julie, Caitlin, Berry, and Emily
*Transfer Policy Review Phase 1 - Meeting #**22*
*Proposed Agenda*
Tuesday 19 October 2021 at 16:00 UTC
1. Roll Call & SOI Updates (5 minutes) 2. Welcome & Chair updates (5 minutes) 3. Deliberations on Additional Security Measures (60 minutes)
- Additional Security Measures working document [docs.google.com] <https://urldefense.com/v3/__https:/docs.google.com/document/d/1q7xaJuxi50Q6T...>
· Review: Summary of “Potential Recommendations Under Consideration” to be presented to the community during ICANN72 session (15 minutes)
- See slide 12 of the attached deck
5. AOB (5 minutes)
· ICANN72 session: Tuesday, 26 October 2021 at 17:30 UTC
_______________________________________________ GNSO-TPR mailing list GNSO-TPR@icann.org https://mm.icann.org/mailman/listinfo/gnso-tpr
-- Farzaneh
