<!DOCTYPE html><html><head><title></title><style type="text/css">#qt p.qt-MsoNormal,#qt li.qt-MsoNormal{margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;font-size:11pt;font-family:"Calibri", sans-serif;}
#qt a:link{color:blue;text-decoration-line:underline;text-decoration-style:solid;text-decoration-color:currentcolor;text-decoration-thickness:auto;}
#qt pre{margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;font-size:10pt;font-family:"Courier New";}
#qt li.qt-MsoListParagraph{margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:36pt;font-size:11pt;font-family:"Calibri", sans-serif;}
#qt li.qt-xmsolistparagraph,#qt p.qt-xmsonormal{margin-right:0cm;margin-left:0cm;font-size:11pt;font-family:"Calibri", sans-serif;}
#qt ul,#qt ol{margin-bottom:0cm;}
p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>Sarah, <br></div><div><br></div><div>This looks like a good process and leaves enough room when it comes to TAC delivery without disrupting business models. <br></div><div><br></div><div>If the registrant nacks the tac and other things happen, those should be optional as an account password reset are not possible on an operational level for some business models and I can imagine there are some retail registrars that rather not lock accounts after a nack, at least I suspect that is what the password reset is for. <br></div><div><br></div><div>Thanks, <br></div><div>Theo <br></div><div><br></div><div><br></div><div><br></div><div>On Tue, Nov 22, 2022, at 6:48 PM, Sarah Wyld wrote:<br></div><blockquote type="cite" id="qt" style="overflow-wrap:break-word;"><div class="qt-WordSection1"><div><p style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;"><span style="color:black;"><span class="font" style="font-family:"Arial", sans-serif;">Hello team,</span></span><br></p><p class="qt-MsoNormal"> <br></p><p style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;"><span style="color:black;"><span class="font" style="font-family:"Arial", sans-serif;">I’ve reviewed our draft updated recommendations and the </span></span><a href="https://docs.google.com/document/d/1e8iG6FmRD0M5VlMUrmIedPw3burqfxLXQrkubxDJ3oQ/edit"><span style="color:rgb(17, 85, 204);"><span class="font" style="font-family:"Arial", sans-serif;">strawman for Rec 2</span></span></a><span style="color:black;"><span class="font" style="font-family:"Arial", sans-serif;">. Left some minor changes in the </span></span><a href="https://docs.google.com/document/d/1d7KwQH6poIxrafFYc5_1e1jQiiCA4WHqdNuRrx2IfWY/edit"><span style="color:rgb(17, 85, 204);"><span class="font" style="font-family:"Arial", sans-serif;">redline doc</span></span></a><span style="color:black;"><span class="font" style="font-family:"Arial", sans-serif;">. </span></span><br></p><p class="qt-MsoNormal"> <br></p><p class="qt-MsoNormal"><span style="color:black;"><span class="font" style="font-family:"Arial", sans-serif;">I want to provide more context specifically around the suggestion for an alternative to the Losing FOA, we can call it the “TAC ACK” process. Prior to our public comment review, the WG seemed aligned on the decision to drop the Losing FOA; we must certainly address all the concerns raised in the public comments, and I think we can do that while also maintaining our goal of streamlining the transfer process by further exploring the TAC ACK option. </span></span><br></p><p class="qt-MsoNormal"> <br></p><p style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;"><b><span style="color:black;"><span class="font" style="font-family:"Arial", sans-serif;">What the process would look like: </span></span></b><br></p><ol style="margin-top:0cm;" type="1" start="1"><li class="qt-MsoListParagraph" style="color:black;margin-left:0cm;vertical-align:baseline;"><span style=""><span class="font" style="font-family:"Arial", sans-serif;">RNH unlocks domain and requests TAC from the Registrar of Record (Losing Rr) </span></span><br></li><li class="qt-MsoListParagraph" style="color:black;margin-left:0cm;vertical-align:baseline;"><span style=""><span class="font" style="font-family:"Arial", sans-serif;">Losing Rr sends a TAC ACK email to the RNH saying “Someone requested a TAC; if this wasn’t you, click <NACKlink>. If it was you, you can either do nothing and we’ll provide you the TAC in 5 days or you can click <ACKlink> and we’ll give you the TAC right now”</span></span><br></li></ol><ol style="margin-top:0cm;" type="1" start="2"><ol style="margin-top:0cm;" type="a" start="1"><li style="color:black;margin-top:0cm;margin-bottom:0cm;vertical-align:baseline;"><span style=""><span class="font" style="font-family:"Arial", sans-serif;">If RNH clicks <NACKlink>, the TAC is never set at the Ry, and other things might happen (e.g. account password reset, etc) </span></span><br></li><li style="color:black;margin-top:0cm;margin-bottom:0cm;vertical-align:baseline;"><span style=""><span class="font" style="font-family:"Arial", sans-serif;">If RNH clicks <ACKlink>, the Losing Rr provisions the TAC at the Ry and issues it to the RNH (Rec 3 Notification of TAC Issuance)</span></span><br></li><li style="color:black;margin-top:0cm;margin-bottom:0cm;vertical-align:baseline;"><span style=""><span class="font" style="font-family:"Arial", sans-serif;">If no response, Losing Rr waits 5 days and then provisions the TAC at the Ry and issues it to the RNH (Rec 3 Notification of TAC Issuance)</span></span><br></li></ol></ol><ol style="margin-top:0cm;" type="1" start="3"><li class="qt-MsoListParagraph" style="color:black;margin-left:0cm;vertical-align:baseline;"><span style=""><span class="font" style="font-family:"Arial", sans-serif;">When the RNH receives the TAC, they provide it to the gaining Rr and the transfer is completed (Rec 4 “Notification of Transfer Completion” etc)</span></span><br></li></ol><p class="qt-MsoNormal"> <br></p><p style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;"><b><span style="color:black;"><span class="font" style="font-family:"Arial", sans-serif;">Why this is beneficial: </span></span></b><br></p><ul style="margin-top:0cm;" type="disc"><li class="qt-MsoNormal" style="color:black;vertical-align:baseline;"><b><span style=""><span class="font" style="font-family:"Arial", sans-serif;">Registrant agency</span></span></b><span style=""><span class="font" style="font-family:"Arial", sans-serif;">: the Registrant has the option to cancel the transfer right away, following the same process as with the current Losing FOA (which has the option to NACK, and which auto-ACKs after a 5 day pending period) <b></b></span></span><br></li><li class="qt-MsoNormal" style="color:black;vertical-align:baseline;"><b><span style=""><span class="font" style="font-family:"Arial", sans-serif;">Just-in-time notifications</span></span></b><span style=""><span class="font" style="font-family:"Arial", sans-serif;">: The TAC ACK process occurs right when the RNH is preparing for the transfer, rather than at some point later on after they’ve initiated it with the gaining Rr and moved on/stopped thinking about it </span></span><br></li><li class="qt-MsoNormal" style="color:black;vertical-align:baseline;"><b><span style=""><span class="font" style="font-family:"Arial", sans-serif;">Simplicity</span></span></b><span style=""><span class="font" style="font-family:"Arial", sans-serif;">: Registrants consistently request fewer emails overall and fewer steps specifically in the transfer process, and have requested an ‘instant transfer’ process for years</span></span><br></li></ul><p class="qt-MsoNormal"> <br></p><p style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;"><b><span style="color:black;"><span class="font" style="font-family:"Arial", sans-serif;">Risks & mitigations: </span></span></b><br></p><ul style="margin-top:0cm;" type="disc"><li class="qt-MsoNormal" style="color:black;vertical-align:baseline;"><span style=""><span class="font" style="font-family:"Arial", sans-serif;">Risk: There would be no notification/’stop the transfer’ moment after the transfer is initiated with the gaining registrar; Mitigation: (a) there is a notification/stop moment at the time of TAC request, and (b) the fast-undo process we are committed to creating in the next phase of this WG would specifically address these issues and could certainly include reverting DNS if it was changed </span></span><br></li><li class="qt-MsoNormal" style="color:black;vertical-align:baseline;"><span style=""><span class="font" style="font-family:"Arial", sans-serif;">Risk: Level of development effort does not balance benefit; Mitigation: The level of effort will differ for different providers, and we shouldn‘t reject ideas just because they take work, especially since we’re already making changes to the transfer process as a whole. Now is exactly the time to do this! </span></span><br></li></ul><p class="qt-MsoNormal"> <br></p><p style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;"><span style="color:black;"><span class="font" style="font-family:"Arial", sans-serif;">The working group hasn’t reached consensus on eliminating the Losing FOA, but we also haven’t reached consensus on keeping it. I still believe that this “TAC ACK” proposal would address the entirely valid concerns about security and registrant agency, while also providing noticeable improvement for registrants who have repeatedly and for quite some time requested a faster transfer process. I hope we can discuss this proposal alongside the Losing FOA strawman.</span></span><br></p><p style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;"><span style="color:black;"><span class="font" style="font-family:"Arial", sans-serif;"> </span></span><br></p></div><p style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;"><span style="color:black;"><span class="font" style="font-family:"Arial", sans-serif;">Thank you,</span></span><br></p><pre> <br></pre><pre><span style=""><span class="font" style="font-family:"Verdana", sans-serif;">-- </span></span><br></pre><pre><b><span style=""><span class="font" style="font-family:"Verdana", sans-serif;">Sarah Wyld</span></span></b><span style=""><span class="font" style="font-family:"Verdana", sans-serif;">, CIPP/E</span></span><br></pre><pre><span style=""><span class="font" style="font-family:"Verdana", sans-serif;"> </span></span><br></pre><pre><span style=""><span class="font" style="font-family:"Verdana", sans-serif;">Policy & Privacy Manager</span></span><br></pre><pre><span style=""><span class="font" style="font-family:"Verdana", sans-serif;">Pronouns: she/they</span></span><br></pre><pre><span style=""><span class="font" style="font-family:"Verdana", sans-serif;"> </span></span><br></pre><pre><a href="mailto:swyld@tucows.com"><span style=""><span class="font" style="font-family:"Verdana", sans-serif;">swyld@tucows.com</span></span></a><span style=""><span class="font" style="font-family:"Verdana", sans-serif;"> </span></span><br></pre><p class="qt-MsoNormal"><span style=""><span class="font" style="font-family:"Courier New";"><span class="size" style="font-size:10pt;"> </span></span></span><br></p><div style="border-right-color:currentcolor;border-right-style:none;border-right-width:medium;border-bottom-color:currentcolor;border-bottom-style:none;border-bottom-width:medium;border-left-color:currentcolor;border-left-style:none;border-left-width:medium;border-image-outset:0;border-image-repeat:stretch;border-image-slice:100%;border-image-source:none;border-image-width:1;border-top-color:rgb(225, 225, 225);border-top-style:solid;border-top-width:1pt;padding-top:3pt;padding-right:0cm;padding-bottom:0cm;padding-left:0cm;"><p class="qt-MsoNormal" style="border-top-color:currentcolor;border-top-style:none;border-top-width:medium;border-right-color:currentcolor;border-right-style:none;border-right-width:medium;border-bottom-color:currentcolor;border-bottom-style:none;border-bottom-width:medium;border-left-color:currentcolor;border-left-style:none;border-left-width:medium;border-image-outset:0;border-image-repeat:stretch;border-image-slice:100%;border-image-source:none;border-image-width:1;padding-top:0cm;padding-right:0cm;padding-bottom:0cm;padding-left:0cm;"></p><div><b>From: </b><a href="mailto:emily.barabas@icann.org">Emily Barabas</a><br></div><div><b>Sent: </b>November 16, 2022 12:18 PM<br></div><div><b>To: </b><a href="mailto:gnso-tpr@icann.org">gnso-tpr@icann.org</a><br></div><div><b>Subject: </b>[GNSO-TPR] Input Due 30 November: Draft Revisions toRecommendations 2-9<br></div><p></p></div><p class="qt-MsoNormal"> <br></p><p class="qt-xmsonormal" style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;"><span style="color:black;" lang="EN-US">Dear working group members,</span><span style="color:black;"></span><br></p><p class="qt-xmsonormal" style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;"><span style="color:black;" lang="EN-US"> </span><span style="color:black;"></span><br></p><p class="qt-xmsonormal" style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;"><span style="color:black;" lang="EN-US">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 <a href="https://docs.google.com/document/d/1e8iG6FmRD0M5VlMUrmIedPw3burqfxLXQrkubxDJ3oQ/edit">here</a>.</span><span style="color:black;"></span><br></p><p class="qt-xmsonormal" style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;"><span style="color:black;" lang="EN-US"> </span><span style="color:black;"></span><br></p><p class="qt-xmsonormal" style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;"><span style="color:black;" lang="EN-US">Please carefully review these documents in coordination with the groups you represent. If you feel that there are items that need to be revised, <b>please enter them <a href="https://docs.google.com/document/d/1d7KwQH6poIxrafFYc5_1e1jQiiCA4WHqdNuRrx2IfWY/edit">here</a></b>. For each item, please include:</span><span style="color:black;"></span><br></p><p class="qt-xmsonormal" style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;"><span style="color:black;" lang="EN-US"> </span><span style="color:black;"></span><br></p><ul style="margin-top:0cm;" type="disc"><li class="qt-xmsolistparagraph" style="color:black;margin-top:0cm;margin-bottom:0cm;"><span lang="EN-US">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).</span><br></li><li class="qt-xmsolistparagraph" style="color:black;margin-top:0cm;margin-bottom:0cm;"><span lang="EN-US">Name and group you represent: If multiple WG members represent a group, input should be in coordination with these other members.</span><br></li><li class="qt-xmsolistparagraph" style="color:black;margin-top:0cm;margin-bottom:0cm;"><span lang="EN-US">Rationale: please provide a clear explanation for why you are proposing the revision.</span><br></li><li class="qt-xmsolistparagraph" style="color:black;margin-top:0cm;margin-bottom:0cm;"><span lang="EN-US">Specific proposed revision: Provide the language you would like to see added/removed/edited.</span><br></li></ul><p class="qt-xmsonormal" style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;"><span style="color:black;" lang="EN-US"> </span><span style="color:black;"></span><br></p><p class="qt-xmsonormal" style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;"><b><span style="color:black;" lang="EN-US">The deadline for submitting input is 30 November 2022.</span></b><span class="qt-apple-converted-space"><span style="color:black;" lang="EN-US"> </span></span><span style="color:black;" lang="EN-US">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. </span><span style="color:black;"></span><br></p><p class="qt-xmsonormal" style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;"><span style="color:black;" lang="EN-US"> </span><span style="color:black;"></span><br></p><p class="qt-xmsonormal" style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;"><span style="color:black;" lang="EN-US">Please do not hesitate to reach out with any questions about the review process.</span><span style="color:black;"></span><br></p><p class="qt-xmsonormal" style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;"><span style="color:black;" lang="EN-US"> </span><span style="color:black;"></span><br></p><p class="qt-xmsonormal" style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;"><span style="color:black;" lang="EN-US">Kind regards,</span><span style="color:black;"></span><br></p><p class="qt-xmsonormal" style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;"><span style="color:black;" lang="EN-US"> </span><span style="color:black;"></span><br></p><p class="qt-xmsonormal" style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;"><span style="color:black;" lang="EN-US"> Caitlin, Julie, Berry, and Emily</span><span style="color:black;"></span><br></p><p class="qt-xmsonormal" style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;"><span style="color:black;" lang="EN-US"> </span><span style="color:black;"></span><br></p><p class="qt-xmsonormal" style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;"><span style="color:black;" lang="EN-US"> </span><span style="color:black;"></span><br></p><p class="qt-MsoNormal"><span style=""> </span><br></p><p class="qt-MsoNormal"><span style=""> </span><br></p><div><p class="qt-MsoNormal"><span style="color:black;" lang="EN-US"><span class="font" style="font-family:"Arial", sans-serif;"><span class="size" style="font-size:10pt;">Emily Barabas</span></span></span><span style="color:black;"></span><br></p><p class="qt-MsoNormal"><span style="color:black;" lang="EN-US"><span class="font" style="font-family:"Arial", sans-serif;"><span class="size" style="font-size:10pt;">Policy Development Support Senior Manager</span></span></span><span style="color:black;"></span><br></p><p class="qt-MsoNormal"><span style="color:black;" lang="EN-US"><span class="font" style="font-family:"Arial", sans-serif;"><span class="size" style="font-size:10pt;">Internet Corporation for Assigned Names and Numbers (ICANN)</span></span></span><span style="color:black;"></span><br></p><p class="qt-MsoNormal"><span style="color:black;" lang="EN-US"><span class="font" style="font-family:"Arial", sans-serif;"><span class="size" style="font-size:10pt;">Phone: +31 (0)6 84507976</span></span></span><span style="color:black;"></span><br></p><p class="qt-MsoNormal"><span style="color:black;" lang="EN-US"><span class="font" style="font-family:"Arial", sans-serif;"><span class="size" style="font-size:10pt;"><a href="http://www.icann.org/" title="http://www.icann.org/"><span style="color:rgb(5, 99, 193);">www.icann.org</span></a></span></span></span><span style="color:black;"></span><br></p><p class="qt-MsoNormal"><span style="color:black;"> </span><br></p></div><p class="qt-MsoNormal"><span style=""> </span><br></p><p class="qt-MsoNormal"><span style=""> </span><br></p></div><div>_______________________________________________<br></div><div>GNSO-TPR mailing list<br></div><div><a href="mailto:GNSO-TPR@icann.org">GNSO-TPR@icann.org</a><br></div><div><a href="https://mm.icann.org/mailman/listinfo/gnso-tpr">https://mm.icann.org/mailman/listinfo/gnso-tpr</a><br></div></blockquote><div><br></div></body></html>