<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:439380639;
mso-list-type:hybrid;
mso-list-template-ids:-2146798198 -537501306 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:5;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-font-family:Calibri;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:1364746858;
mso-list-type:hybrid;
mso-list-template-ids:-1272147904 -537501306 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-start-at:5;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-font-family:Calibri;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style>
</head>
<body lang="en-BE" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Dear Working Group members,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Following yesterday’s call, staff had an action item to review the deliberations about the proposed notification of TAC provision and specifically how this notification should fit alongside
the provision of the TAC itself. In going back to the recordings, I can confirm that Sarah’s recollection is correct – members expressed support for the idea that if the TAC is being provided by email and the notification of TAC provision is being provided
by email, these can be combined. I</span><span style="mso-fareast-language:EN-US">f the TAC is provided by
</span><span lang="EN-US" style="mso-fareast-language:EN-US">another method</span><span style="mso-fareast-language:EN-US"> and it's not certain that it was directly
</span><span lang="EN-US" style="mso-fareast-language:EN-US">sent </span><span style="mso-fareast-language:EN-US">to the RNH, then the RNH must be notified separately</span><span lang="EN-US" style="mso-fareast-language:EN-US">. Please see pages 29-33 of the
transcript from 14 September here: <a href="https://gnso.icann.org/sites/default/files/policy/2021/transcript/transcript-gnso-tpr-14sep21.en_.pdf">
https://gnso.icann.org/sites/default/files/policy/2021/transcript/transcript-gnso-tpr-14sep21.en_.pdf</a>.
</span><span style="mso-fareast-language:EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Thanks for catching the error in the text, Sarah. We will go ahead and update the draft recommendations.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Kind regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Emily<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:12.0pt;color:black">From:
</span></b><span lang="EN-US" style="font-size:12.0pt;color:black">GNSO-TPR <gnso-tpr-bounces@icann.org> on behalf of Julie Hedlund <julie.hedlund@icann.org><br>
<b>Date: </b>Tuesday, 16 November 2021 at 18:30<br>
<b>To: </b>"gnso-tpr@icann.org" <gnso-tpr@icann.org><br>
<b>Subject: </b>[GNSO-TPR] Notes and action items - TPR WG Meeting #23 - 16 Nov 2021<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US" style="color:black">Dear TPR WG Members,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">Please find below the notes and action items from today’s call.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">The next TPR WG meeting will be</span><span lang="EN-US"> on<span style="color:black">
<b>Tuesday, </b></span><b>23 November <span style="color:black">at </span>16:00<span style="color:black"> UTC</span></b><span style="color:black">.<o:p></o:p></span></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"><br>
Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">Emily, Julie, Berry, and Caitlin </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><b><u><span lang="EN-US" style="color:black"><o:p><span style="text-decoration:none"> </span></o:p></span></u></b></p>
<p class="MsoNormal"><b><u><span lang="EN-US" style="color:black">Action Items<o:p></o:p></span></u></b></p>
<p class="MsoNormal"><b><u><span lang="EN-US" style="color:black"><o:p><span style="text-decoration:none"> </span></o:p></span></u></b></p>
<p class="MsoNormal"><span lang="EN-US">1. Losing FOA Candidate Recommendations – see:
<u><a href="https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?url=https*3A*2F*2Furldefense.com*2Fv3*2F__https*3A*2Fdocs.google.com*2Fdocument*2Fd*2F1wCUMe9ii6g05kUZ558IuUvJaS6K2t0GZJYvlfOy-raY*2Fedit__*3B!!PtGJab4!tVlReslxdp4FVqbtvaBGc0balBYYf8nmPv8Fd4I7wkegiaNANR3DTiMqhsdOVSNozdJdnVI*24&data=04*7C01*7Crcarney*40godaddy.com*7Cd65072730ccf413e9c3f08d9a5224acf*7Cd5f1622b14a345a6b069003f8dc4851f*7C0*7C0*7C637722389110981711*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C1000&sdata=MFXWvsgjs2Vq*2BUPOVfyCajb4AISeQ7LpF5F46rlr0Oo*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl!!PtGJab4!oCSoSUMrN-UqvVVo5WG7t__ox54piuqwF197CBe5ASw-VLom5Y2NRR3715R6CFnpujK--Evvvw$" title="https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?url=https*3A*2F*2Furldefense.com*2Fv3*2F__https*3A*2Fdocs.google.com*2Fdocument*2Fd*2F1wCUMe9ii6g05kUZ558IuUvJaS6K2t0GZJYvlfOy-raY*2Fedit__*3B!!PtGJab4!tVlReslxdp4FVqbtvaBGc0balBYY">Losing
FOA Working Document </a></u>(beginning on p. 14)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Candidate Recommendation #12: <b>Staff will add a reference/footnote.<o:p></o:p></b></span></p>
<p class="MsoNormal"><span lang="EN-US">Candidate Recommendation #13: <o:p></o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US">1) Staff to review the discussions to clarify the rationale for this recommendation to have two communications.<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span lang="EN-US">2) WG members to suggest wording for the method of sending and period of time (text in brackets).<o:p></o:p></span></b></p>
<p class="MsoNormal"><span lang="EN-US">Candidate Recommendation #14: <b>WG members to suggest wording re: the method of sending and period of time (text in brackets).<o:p></o:p></b></span></p>
<p class="MsoNormal"><span lang="EN-US">Candidate Recommendation #15:<o:p></o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US">1) WG members to suggest wording re: the method of sending and period of time (text in brackets).
<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span lang="EN-US">2) Staff to update the context to add text on when this makes sense to be used.</span></b><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Candidate Recommendation #16: <b>WG members to suggest wording re: the method of sending and period of time (text in brackets).<o:p></o:p></b></span></p>
<p class="MsoNormal"><b><span lang="EN-US"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><span lang="EN-US">2.<b> </b>Rationale for Elimination of the Gaining FOA:
<b>WG members to review the document at <a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/1QOCzbLh7w4hdijpAsg6_lybddr0nlsFDcWjdz5e21Qo/edit__;!!PtGJab4!rt55ElTqTkAucJCRpFIX0odqy6RjmPpQzMKy-i97LHfqG_fE9HMyd4ugCjLhX55WyeD3qtJM8A$" title="https://urldefense.com/v3/__https://docs.google.com/document/d/1QOCzbLh7w4hdijpAsg6_lybddr0nlsFDcWjdz5e21Qo/edit__;!!PtGJab4!rt55ElTqTkAucJCRpFIX0odqy6RjmPpQzMKy-i97LHfqG_fE9HMyd4ugCjLhX55WyeD3qtJM8A$">
Gaining FOA Working Document [docs.google.com]</a> (beginning on p. 16) and provide suggestions and comments if any.</b><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="color:black">Transfer Policy Review Phase 1 - Meeting #2</span></b><b><span lang="EN-US">3</span></b><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:6.0pt;line-height:18.0pt"><b><span lang="EN-US" style="color:black">Tuesday </span></b><b><span lang="EN-US">16 November<span style="color:black"> 2021 at
</span>16:00<span style="color:black"> UTC<o:p></o:p></span></span></b></p>
<p class="MsoNormal"><span lang="EN-US">1. Roll Call & SOI Updates<o:p></o:p></span></p>
<ul type="disc">
<li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">No updates provided.<o:p></o:p></span></li></ul>
<p class="MsoNormal"><span lang="EN-US">2. Welcome & Chair updates<o:p></o:p></span></p>
<ul type="disc">
<li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Will return to the lock discussion in a few weeks.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Note that since we are being so efficient, we are looking to do a Project Change Request to pull forward the NACKing discussion
scheduled for Phase 2 so we can get a complete view of the transfer policy during Phase 1a. That includes copying what we are doing now to review charter questions, develop recommendations, and incorporate into the Phase 1 report. We will inform the Council
that those discussions may include the TEAC – how it may change or be enhanced with respect to the NACKing of transfers, but any recommendations for changes will not be part of Phase 1, but will stay in Phase 2.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Schedule NACKing after we get through with our discussions on bulk, etc.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">The RrSG is holding a poll on locking.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">At-Large CPWG also will hold a poll on locking.<o:p></o:p></span></li></ul>
<p class="MsoNormal"><span lang="EN-US">3. Losing FOA Candidate Recommendations – see:
<u><a href="https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?url=https*3A*2F*2Furldefense.com*2Fv3*2F__https*3A*2Fdocs.google.com*2Fdocument*2Fd*2F1wCUMe9ii6g05kUZ558IuUvJaS6K2t0GZJYvlfOy-raY*2Fedit__*3B!!PtGJab4!tVlReslxdp4FVqbtvaBGc0balBYYf8nmPv8Fd4I7wkegiaNANR3DTiMqhsdOVSNozdJdnVI*24&data=04*7C01*7Crcarney*40godaddy.com*7Cd65072730ccf413e9c3f08d9a5224acf*7Cd5f1622b14a345a6b069003f8dc4851f*7C0*7C0*7C637722389110981711*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C1000&sdata=MFXWvsgjs2Vq*2BUPOVfyCajb4AISeQ7LpF5F46rlr0Oo*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl!!PtGJab4!oCSoSUMrN-UqvVVo5WG7t__ox54piuqwF197CBe5ASw-VLom5Y2NRR3715R6CFnpujK--Evvvw$" title="https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?url=https*3A*2F*2Furldefense.com*2Fv3*2F__https*3A*2Fdocs.google.com*2Fdocument*2Fd*2F1wCUMe9ii6g05kUZ558IuUvJaS6K2t0GZJYvlfOy-raY*2Fedit__*3B!!PtGJab4!tVlReslxdp4FVqbtvaBGc0balBYY">Losing
FOA Working Document </a></u>(beginning on p. 14)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><u><span lang="EN-US">Candidate Recommendation #12</span></u><span lang="EN-US">: The Working Group recommends eliminating from the Transfer Policy the requirement that the Registrar of Record send a Losing Form of Authorization. This requirement
is detailed in sections [xxxx] of the Transfer Policy.<o:p></o:p></span></p>
<ul type="disc">
<li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Wonder if there should be a footnote that there will still be a notification.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">It would really help to include the explanation/context so that people not familiar will know that there will still be
a notification.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Context: How this is structured – the candidate recommendations are preceded by a response to the charter questions, which
does provide the context, including the rationale. These recommendations won’t be presented in isolation.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">ACTION ITEM: Staff will add a reference/footnote.<o:p></o:p></span></b></li></ul>
<p class="MsoNormal"><u><span lang="EN-US">Candidate Recommendation #13</span></u><span lang="EN-US">:
<o:p></o:p></span></p>
<ul type="disc">
<li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">What do we mean by “distinct” as in “If the Registrar of Record provides the TAC by email, the email containing the TAC
and the message notifying the RNH of the TAC request must be two distinct communications.” Could be “two separate communications”.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Don’t see the value of sending two separate emails. Would rather see a combination of this in one email.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">The important part is the notification to the registered name holder (RNH). There is also the concept of the 5-day window
at the beginning.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Definitely agree we must ensure the RNH is notified; not sure it needs to be two separate messages. But we must have had
some reason for it?<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Would like to include the name of the person who requested it.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">If we look at rows 4 and 5 in the charter, that is what we are doing here. The question we haven’t answered is do we have
to specify who the TAC is provided to? If provided to the RNH then we don’t need separate methods. If to someone other than the RNH we’ll need two messages. The security element (secondary notification to RNH) is only needed if the TAC is provided in some
method OTHER than by email to the RNH<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">It can only go to the RNH. It only makes sense to go there.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">When we are talking about how we supply the TAC, there could be other means. We could send a notice that a TAC has been
created and to look in your account,.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">If we look at the early deliberations, some support was expressed for making this two distinct communications for security
reasons.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Maybe we split this recommendation up: 1) notification to RNH that a TAC has been requested. 2) If the RNH is receiving
the TAC via a communication then they know that the request happened (so no need for a separate communication).<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Our goal is to ensure that the RNH is aware of the request.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">We want to say if the TAC is being communicated to the RNH then we don’t need two communications, but if provided by a
different mechanism then the RNH should receive a notification that the request has happened.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">It might be helpful to zoom out to look at the table at:
<a href="https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/17ADMRTYxN5sA-e3WoEI96KxlH5YRALBsxgwOmpsCC0g/edit?usp=sharing__;!!PtGJab4!p_ek0O_uwiZMzjqMmoTZBPMMKNEjSXb2UCQ9YXFc1yx-zWeM_9lgeBnPbuuqhminBsaAp1ftHw$">
https://docs.google.com/spreadsheets/d/17ADMRTYxN5sA-e3WoEI96KxlH5YRALBsxgwOmpsCC0g/edit?usp=sharing [docs.google.com]</a>.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Also note that the recommendations are in order of mandatory ones first then optional, rather than in order of the process
steps.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Registrar doesn’t know how the reseller is going to deliver the TAC.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Maybe it will be clearer if we break this recommendation into two parts.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Try to make the type of communication/notification as generic as possible. Suggest wording.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">List doesn’t say specifically that the TAC has to be provided or how.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Don’t we have recommendations relating to the TAC? We have a set of recommendations that are specific to the TAC. Notifications
of the provision of the TAC are related to the Losing FOA, so that is why the reference is here. We are likely to reorganized these when they are agreed to so all of the TAC recommendations are together.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Envision a scenario where someone logs into a portal and updates the RNH email address and requests a TAC – could be fraud
in the account. So, if a RNH email is changed in a certain amount of time then a notification is sent to the previous RNH.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Think the above scenario will come up as part of the change of registrant process. Not sure that is a problem we need
to solve for.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">We cannot stop this type of fraud with an ICANN policy.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Concerned that we are relying on laws to provide security via some cumbersome and lengthy process, rather than looking
at mechanisms that can enhance the security of the transfer.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">This relates to Change of Registrant (COR) so we’ll delay that part of the discussion.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">ACTION ITEMS: 1) Staff to review the discussions to clarify the rationale for this recommendation to have two communications.
2) WG members to suggest wording for method of sending and period of time (text in brackets).<o:p></o:p></span></b></li></ul>
<p class="MsoNormal"><u><span lang="EN-US">Candidate Recommendation #14:<o:p></o:p></span></u></p>
<ul type="disc">
<li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">On number 1 and the IANA ID – losing registrar always gets the IANA ID but not the name of the gaining registrar – if we
want that then the registry will have to provide it.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Does it matter that the IANA ID is provided with the name of the gaining registrar?<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Think adding IANA ID will overly complicate a communication intended for non-technical people.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Agree that regular users will find IANA ID confusing and unhelpful, but also agree that we can't currently automagically
get the actual registrar name.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">“Regular users” have a problem when there are resellers have initiated the transfers and the RNH sees the Registrar name
(with/without IANA ID).<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">We do not have info about resellers at the gaining registrar.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Not sure that we need to set a requirement on that.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Language seems flexible enough to allow for minimal notification.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">In most cases we see reporters do not know about registrars and file reports with compliance as changing reseller/service
provider, but in fact it ends up with changing registrar.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">ACTION ITEM: WG members to suggest
</span></b><b><span lang="EN-US" style="font-family:"Calibri",sans-serif">wording</span></b><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> re: the method of sending and period of time (text in brackets).</span></b><u><span lang="EN-US" style="font-family:"Calibri",sans-serif"><o:p></o:p></span></u></li></ul>
<p class="MsoNormal"><u><span lang="EN-US">Candidate Recommendation #15:<o:p></o:p></span></u></p>
<ul type="disc">
<li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">This is one of the optional notifications.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Add a number 4, the reason for the delay, if there is one? If it is due to a delayed TAC response this would be a good
idea.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Do we need to add the rationale for why this is needed? Maybe clarifying when this makes sense to be used in the context.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">ACTION ITEM: 1) WG members to suggest
</span></b><b><span lang="EN-US" style="font-family:"Calibri",sans-serif">wording</span></b><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> re: the method of sending and period of time (text in brackets). 2) Staff to update
the context to add text on when this makes sense to be used.</span></b><u><span lang="EN-US" style="font-family:"Calibri",sans-serif"><o:p></o:p></span></u></li></ul>
<p class="MsoNormal"><u><span lang="EN-US">Candidate Recommendation #16:<o:p></o:p></span></u></p>
<ul type="disc">
<li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-family:"Calibri",sans-serif">This is the second optional notification – the pending notification.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><span lang="EN-US" style="font-family:"Calibri",sans-serif">If this is optional, do we have to specify the period of time?<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l0 level1 lfo1"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">ACTION ITEM: WG members to suggest
</span></b><b><span lang="EN-US" style="font-family:"Calibri",sans-serif">wording</span></b><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> re: the method of sending and period of time (text in brackets).</span></b><span lang="EN-US" style="font-family:"Calibri",sans-serif"><o:p></o:p></span></li></ul>
<p class="MsoNormal"><span lang="EN-US">4. Rationale for Elimination of the Gaining FOA – see:
<a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/1QOCzbLh7w4hdijpAsg6_lybddr0nlsFDcWjdz5e21Qo/edit__;!!PtGJab4!rt55ElTqTkAucJCRpFIX0odqy6RjmPpQzMKy-i97LHfqG_fE9HMyd4ugCjLhX55WyeD3qtJM8A$" title="https://urldefense.com/v3/__https://docs.google.com/document/d/1QOCzbLh7w4hdijpAsg6_lybddr0nlsFDcWjdz5e21Qo/edit__;!!PtGJab4!rt55ElTqTkAucJCRpFIX0odqy6RjmPpQzMKy-i97LHfqG_fE9HMyd4ugCjLhX55WyeD3qtJM8A$">
Gaining FOA Working Document [docs.google.com]</a> (beginning on p. 16)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US">ACTION ITEM: WG members to review the Rationale for Elimination of the Gaining FOA – see:
<a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/1QOCzbLh7w4hdijpAsg6_lybddr0nlsFDcWjdz5e21Qo/edit__;!!PtGJab4!rt55ElTqTkAucJCRpFIX0odqy6RjmPpQzMKy-i97LHfqG_fE9HMyd4ugCjLhX55WyeD3qtJM8A$" title="https://urldefense.com/v3/__https://docs.google.com/document/d/1QOCzbLh7w4hdijpAsg6_lybddr0nlsFDcWjdz5e21Qo/edit__;!!PtGJab4!rt55ElTqTkAucJCRpFIX0odqy6RjmPpQzMKy-i97LHfqG_fE9HMyd4ugCjLhX55WyeD3qtJM8A$">
Gaining FOA Working Document [docs.google.com]</a> (beginning on p. 16) and provide suggestions and comments if any.<o:p></o:p></span></b></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">5. AOB<o:p></o:p></span></p>
<ul type="disc">
<li class="MsoListParagraph" style="mso-list:l1 level1 lfo2"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Next call: Tuesday 23 November 2021 at 16:00 UTC</span><span lang="EN-US"><o:p></o:p></span></li></ul>
</div>
</body>
</html>