<html 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:Helvetica;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@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:0in;
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:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle19
{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:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:64380186;
mso-list-template-ids:392870256;}
@list l0:level1
{mso-level-start-at:3;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:112526165;
mso-list-template-ids:315534676;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2
{mso-list-id:351684827;
mso-list-type:hybrid;
mso-list-template-ids:-423563928 329661064 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l2:level1
{mso-level-start-at:2;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Calibri",sans-serif;
mso-fareast-font-family:Calibri;}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l2:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l2:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l2:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l2:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l2:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l2:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l2:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l3
{mso-list-id:992443498;
mso-list-type:hybrid;
mso-list-template-ids:2093659250 -334827476 2037306258 629833414 -182030338 -564472432 -1966173506 284719688 -1653807646 -1849932306;}
@list l3:level1
{mso-level-number-format:bullet;
mso-level-text:•;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l3:level2
{mso-level-number-format:bullet;
mso-level-text:•;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l3:level3
{mso-level-number-format:bullet;
mso-level-text:•;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l3:level4
{mso-level-number-format:bullet;
mso-level-text:•;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l3:level5
{mso-level-number-format:bullet;
mso-level-text:•;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l3:level6
{mso-level-number-format:bullet;
mso-level-text:•;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l3:level7
{mso-level-number-format:bullet;
mso-level-text:•;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l3:level8
{mso-level-number-format:bullet;
mso-level-text:•;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l3:level9
{mso-level-number-format:bullet;
mso-level-text:•;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l4
{mso-list-id:1248927798;
mso-list-template-ids:-116984032;}
@list l4:level1
{mso-level-start-at:3;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l4:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5
{mso-list-id:2088533082;
mso-list-type:hybrid;
mso-list-template-ids:-610338454 -365814960 1412827852 -1964718464 -973034754 1300893402 1154109920 -1880845022 -462636104 178552388;}
@list l5:level1
{mso-level-number-format:bullet;
mso-level-text:•;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l5:level2
{mso-level-number-format:bullet;
mso-level-text:•;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l5:level3
{mso-level-number-format:bullet;
mso-level-text:•;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l5:level4
{mso-level-number-format:bullet;
mso-level-text:•;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l5:level5
{mso-level-number-format:bullet;
mso-level-text:•;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l5:level6
{mso-level-number-format:bullet;
mso-level-text:•;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l5:level7
{mso-level-number-format:bullet;
mso-level-text:•;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l5:level8
{mso-level-number-format:bullet;
mso-level-text:•;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
@list l5:level9
{mso-level-number-format:bullet;
mso-level-text:•;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Arial",sans-serif;
mso-bidi-font-family:"Times New Roman";}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:black">Dear TPR WG Members,</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">Please find below the notes and action items from today’s
</span>meeting<span style="color:black">.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">The next TPR WG meeting will be</span> on<span style="color:black">
<b>Tuesday,</b></span><b> 10 May 2022 <span style="color:black">at </span>16:00 UTC<i><span style="color:black">.</span></i></b><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><br>
Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<div style="border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in">
<p class="MsoNormal"><span style="color:black">Emily, Julie, Berry, and Caitlin <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="color:black">Action Items</span>:<o:p></o:p></b></p>
<p class="MsoNormal"><b><u><o:p><span style="text-decoration:none"> </span></o:p></u></b></p>
<p class="MsoNormal">Draft recommendations on NACK Charter Question h1 produced by the small group<b> </b>(see working document pages 16-23 <a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/1L2bZnhJUY3VxyAjVCrkyVqdttOPn2EaqBARRRnEPd0Q/edit__;!!PtGJab4!t_o2O1GHzkJDjFq1Wmy7lE2ChWlmMrJ30pO8zf5rLHhKq3yVtdZZJDcTSI37gyzc98d9UDYNTg$" title="https://urldefense.com/v3/__https://docs.google.com/document/d/1L2bZnhJUY3VxyAjVCrkyVqdttOPn2EaqBARRRnEPd0Q/edit__;!!PtGJab4!t_o2O1GHzkJDjFq1Wmy7lE2ChWlmMrJ30pO8zf5rLHhKq3yVtdZZJDcTSI37gyzc98d9UDYNTg$">here
[docs.google.com]</a>)<o:p></o:p></p>
<p class="MsoNormal"><b><u><o:p><span style="text-decoration:none"> </span></o:p></u></b></p>
<p class="MsoNormal"><b>For I.A.3.7.3 --</b> <b>Change “No payment” to “Non-payment”.<o:p></o:p></b></p>
<p class="MsoNormal"><b>For I.A.3.9.1 -- </b><b>WG members who have suggestions for text to address this situation should send them to the list.<o:p></o:p></b></p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal">Composition of the TAC (see attached document):<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Recommendation 7: <o:p></o:p></p>
<p class="MsoNormal"><b>1. Staff to consult with ICANN org Compliance as to whether there are issues with enforcement to reference an RFC without context.<o:p></o:p></b></p>
<p class="MsoNormal"><b>2. WG members to review the suggested text from Sarah and Jim and provide comments on the list.<o:p></o:p></b></p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal">Recommendation 11:<o:p></o:p></p>
<p class="MsoNormal"><b>Jim Galvin and WG members to consider suggested change to the language as follows:
</b><b>“The working group recommends that the TAC as created by the Registrar of Record according to Preliminary Recommendation 7, must be “one-time use. In other words, it MUST be used no more than once per domain name. The Registry Operator MUST clear the
TAC as part of completing the successful transfer request.”<o:p></o:p></b></p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal"><b>Notes:<o:p></o:p></b></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>Transfer Policy Review Phase 1 - Meeting #45<o:p></o:p></b></p>
<p class="MsoNormal"><b>Tuesday, 03 May 2022 at 16:00 UTC</b><o:p></o:p></p>
<p class="MsoNormal"><b>Proposed Agenda</b><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">1. Roll Call & SOI updates<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">2. Welcome & Chair updates<o:p></o:p></p>
<ul type="disc">
<li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Homework: Review Initial Report and identify those items that need extra work in coordination with your groups as much as possible.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Only other reminder is that we have 6 sessions now to work diligently, avoiding bringing up settled discussions.<o:p></o:p></span></li></ul>
<p class="MsoNormal">3. Draft recommendations on NACK Charter Question h1 produced by the small group<b> </b>(see working document pages 16-23 <a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/1L2bZnhJUY3VxyAjVCrkyVqdttOPn2EaqBARRRnEPd0Q/edit__;!!PtGJab4!t_o2O1GHzkJDjFq1Wmy7lE2ChWlmMrJ30pO8zf5rLHhKq3yVtdZZJDcTSI37gyzc98d9UDYNTg$" title="https://urldefense.com/v3/__https://docs.google.com/document/d/1L2bZnhJUY3VxyAjVCrkyVqdttOPn2EaqBARRRnEPd0Q/edit__;!!PtGJab4!t_o2O1GHzkJDjFq1Wmy7lE2ChWlmMrJ30pO8zf5rLHhKq3yVtdZZJDcTSI37gyzc98d9UDYNTg$">here
[docs.google.com]</a>)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Overview:<o:p></o:p></p>
<ul type="disc">
<li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Reminder: the goal is to take the small group outputs as they are unless something is really broken or wrong in what they produced.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Thank the members of the small team and the staff support, particularly the summary table.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Focus was the finalize the input from the full WG.<o:p></o:p></span></li></ul>
<p class="MsoNormal"><b>Recommendation 19</b>: The working group recommends revising the following reasons that the Registrar of Record MAY deny a transfer request as follows:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I.A.3.7.1: Evidence of fraud <b>or violation of the Registration Agreement.</b>
<u>Implementation Guidance</u>: The intent of “violation of the Registration Agreement” is not to allow the blocking of transfers due to minor violations, but to allow action in case of substantive contravention of the Registration Agreement.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I.A.3.7.2: Reasonable <s>dispute over the identity of</s> <b>
concern that the transfer was not requested by</b> the Registered Name Holder <s>
or Administrative Contact</s>.<o:p></o:p></p>
<ul type="disc">
<li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Identity is not the goal.<o:p></o:p></span></li></ul>
<p class="MsoNormal">I.A.3.7.3: No payment for previous registration period (including
<b>payment disputes or </b>credit card charge-backs) if the domain name is past its expiration date
<b>at the current Registrar of Record </b>or for previous or current registration periods if the domain name has not yet expired.
<s>In all such cases, however, the domain name must be put into "Registrar Hold" status by the Registrar of Record prior to the denial of transfer.<o:p></o:p></s></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Comment from Jothan re: “for previous or current registration periods if the domain name has not yet expired…” I was asked if this addresses explicit renewals in addition to those within add-grace<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>Recommendation 20</b>: The working group recommends changing the following reasons that the Registrar of Record currently MAY deny a transfer into reasons that the Registrar of Record MUST deny a transfer and revising the text as follows:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I.A.3.7.4: Express objection to the transfer by the authorized Transfer Contact<b> Registered Name Holder</b>. Objection could take the form of specific request (either by paper or electronic means) by the
<s>authorized Transfer Contact</s> <b>Registered Name Holder </b>to deny a particular transfer request, or a general objection to all transfer requests received by the Registrar, either temporarily or indefinitely. In all cases, the objection must be provided
with the express and informed consent of the <s>authorized Transfer Contact</s> <b>
Registered Name Holder </b>on an opt-in basis and upon request by the <s>authorized Transfer Contact</s>
<b>Registered Name Holder</b>, the Registrar must remove the lock or provide a reasonably accessible method for the
<s>authorized Transfer Contact</s> <b>Registered Name Holder </b>to remove the lock within five (5) calendar days.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I.A.3.7.5: The transfer was requested within <s>60</s> <b>30</b> days of the creation date as shown in the registry
<s>Whois</s> <b>RDDS</b> record for the domain name.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I.A.3.7.6: A domain name is within 60 <b>30</b> days (or a lesser period to be determined) after being transferred (apart from being transferred back to the original Registrar in cases where both Registrars so agree and/or where a decision
in the dispute resolution process so directs). "Transferred" shall only mean that an inter-registrar transfer has occurred in accordance with the procedures of this policy.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Discussion:<o:p></o:p></p>
<ul type="disc">
<li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><u><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Re: 1.A.3.7.3</span></u><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">: Question: If someone has entered into a
payment plan and the registrant determines to renew the domain name, you would not want the domain name to transfer away during that time. Do the sections address this? Answer: For I.A.3.7.3 – instead of “No payment” we could say “Non-payment”, but maybe it
covers without that.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Seems like the registrar has extended credit to the registrant, but the domain has been paid for. Seems like a more complicated relationship,
that doesn’t involve a grace-period payment. Don’t think the policy has to accommodate this.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Think it is premium names that are not addressed in the current policy.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Seems like if there was a payment plan there would be contracts to cover that?<o:p></o:p></span></li></ul>
<p class="MsoNormal"><b>ACTION ITEM: For I.A.3.7.3 --</b> <b>Change “No payment” to “Non-payment”.<o:p></o:p></b></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>Recommendation 21: </b>The working group recommends revising the reasons that the Registrar of Record MUST deny a transfer request as follows:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I.A.3.8.1: <s>A p</s> <b>P</b>ending UDRP proceeding that the Registrar has been i<s>nformed</s>
<b>notified</b> of <b>by the Provider in accordance with the UDRP Rules</b>.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I.A.3.8.3: Pending dispute <s>related to a previous transfer, pursuant to</s>
<b>under</b> the Transfer Dispute Resolution Policy.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I.A.3.8.4: <b>Pending </b>URS proceeding or URS suspension that the Registrar has been
<s>informed</s> <b>notified</b> of <b>by the Provider in accordance with the URS Procedure</b>.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>Recommendation 22</b>: The working group recommends changing the following reasons that the Registrar of Record currently MAY NOT deny a transfer into reasons that the Registrar of Record MUST NOT deny a transfer and revising the text
as follows:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I.A.3.9.1: <u>Implementation Guidance</u>: Registrars are prohibited from denying domain name transfer requests based on non-payment of fees for pending or future registration periods during the Auto-Renew Grace Period, provided that any
auto-renewal costs borne by the Registrar are reversible for future period.<o:p></o:p></p>
<ul type="disc">
<li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Comment from Jothan: Explicit renewals do not have automatic refunds like auto-renewals. These have a unit cost that extends the renewal
term for 1 year so is related to a future registration period. Is the losing registrar protected in this instance by this verbiage where a registrant extends and has funds still due?<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This one might suggest that a registrant might have their transfer denied while under a payment plan. If that is covered by contract,
then that’s okay. Wording could leave room for the registrant to migrate the domain away.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The question is whether we want to allow registrars to hold a transfer hostage for payment? But this could be covered by a contract.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Registrars should take this into account with the contracts with registrants.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Think we are confusing this with a title, versus a payment plan that is like an unsecured loan. This is not an apt analogy. In Jothan’s
situation the entity loaning the money has made an unsecured loan. Or mechanism facilitates the situation where the registrar could be the registered name holder and leases the name, rather than the registrant holding the title so to speak.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">You could structure the deal in a way that the registrar is listed as RNH until the domain is paid in full.<o:p></o:p></span></li></ul>
<p class="MsoNormal"><b>ACTION ITEM: For I.A.3.9.1 -- </b><b>WG members who have suggestions for text to address this situation should send them to the list.<o:p></o:p></b></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I.A.3.9.2: No response from the Registered Name Holder. <s>or Administrative Contact</s><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I.A.3.9.3: <b>A registrar-applied inter-registrar transfer lock is in place on the</b>
<s>D</s><b>d</b>omain name <s>in Registrar Lock Status</s>, for reasons other than those specified in I.A.3.7 and I.A.3.8
<s>unless</s> <b>and</b> the Registered Name Holder is <b>not</b> provided with the reasonable opportunity and ability to unlock the domain name<b>
</b>prior to the Transfer Request<b> pursuant to the requirements in sections I.A.5.1 - I.A.5.4</b>.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I.A.3.9.4: Domain name registration period time constraints, other than
<b>as defined in I.A.3.7.5 and I.A.3.7.6<sup>[1]</sup> </b><s>during the first 60 days of initial registration,</s>
<s>during the first 60 days after a registrar transfer</s> , or during the 60-day lock following a Change of Registrant pursuant to Section II.C.2.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I.A.3.9.5: General payment defaults between Registrar and <b>
Reseller, as defined in the RAA, </b><s>business partners / affiliates</s> in cases where the Registered Name Holder for the domain in question has paid for the registration.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">4. Composition of the TAC – Recommendations 7, 9, and 11<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Recommendation 7:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Current text:<o:p></o:p></p>
<p class="MsoNormal">[The working group recommends that ICANN org establish minimum requirements for the composition of the TAC (for example, minimum length, syntax, or entropy value) based on current applicable technical security standards. ICANN org MAY change
these requirements in response to new or updated standards, but any changes to the requirements MUST go in effect with sufficient notification and time for contracted parties to implement the necessary updates.] OR [The Working Group recommends that Registrars
and Registry Operators follow best practices for the composition of the TAC (for example, minimum length, syntax, or entropy value) based on current applicable technical security standards such as RFC9154 or subsequent or similar RFCs. These best practices
may be updated in response to new or<o:p></o:p></p>
<p class="MsoNormal">updated standards as appropriate.]<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">From Sarah Wyld: <o:p></o:p></p>
<p class="MsoNormal">The Working Group recommends that Registrars and Registry Operators follow best practices for the composition of the TAC (for example, minimum length, syntax, or entropy value) based on current applicable technical security standards such
as RFC9154 or subsequent or similar RFCs. These best practices may be updated in response to new or updated standards as appropriate.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">From Jim Galvin: <o:p></o:p></p>
<p class="MsoNormal">The working group recommends that the minimum requirements for the composition of a TAC MUST be as specified in RFC 9154 (and its update and replacement RFCs). In addition, where random values are required by RFC 9154, such values MUST
be created according to BCP 106. [Footnote: BCP 106 is a Best Current Practice and is an idempotent reference to the most recent version of the specification entitled “Randomness Requirements for Security”, currently RFC 4086, which is how it is referenced
in RFC 9154.] The salient specification point from RFC 9154 is as follows.<o:p></o:p></p>
<p class="MsoNormal">● Using the set of all printable ASCII printable characters except space and a required entropy of 128 bits, the length of the TAC MUST be at least 20 characters. Gould, J. and R. Wilhelm, "Extensible Provisioning Protocol (EPP) Secure
Authorization Information for Transfer", RFC 9154, DOI 10.17487/RFC9154, December 2021,<o:p></o:p></p>
<p class="MsoNormal"><https://www.rfc-editor.org/info/rfc9154>.<o:p></o:p></p>
<p class="MsoNormal">Eastlake 3rd, D., Schiller, J., and S. Crocker, "Randomness Requirements for Security", BCP 106, RFC 4086, June 2005, <https://www.rfc-editor.org/info/bcp106>.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Discussion:<o:p></o:p></p>
<ul type="disc">
<li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Seems rather technical for a policy recommendation.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Seems reasonable though.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Not sure how to balance technical with general. Not sure what to change.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Maybe we can find a way to bring in Sarah’s language.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">RFC 4086 and BCP 106 are the same document.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">If the PDP wants to say higher level and just refer to the IETF standards, it could refer to RFC 4086 and BCP 106 and stop there.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This seems like a good suggestion.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Are we future proofing this enough, or locking it in one place? To the extent that the technology evolves the RFCs would be updated
accordingly. They would be adaptable.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">In RFC 9154, it has a “SHOULD” around the 20 characters – it doesn’t make it a “MUST”. The bullet point in the suggested text makes
it a “MUST”.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Seems that this text might be too technical for a recommendation, but great to have for reference?
<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">IETF didn’t put “MUST” in because that would have been policy; this WG would have to make it a “MUST” to make it policy.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The objective is to make sure we are providing registrants a reasonable amount of security for the TAC. The specificity of the text
has to be balanced with evolving technology.<o:p></o:p></span></li></ul>
<p class="MsoNormal"><b>ACTION ITEMS: <o:p></o:p></b></p>
<p class="MsoNormal"><b>1. Staff to consult with ICANN org Compliance as to whether there are issues with enforcement to reference an RFC without context.<o:p></o:p></b></p>
<p class="MsoNormal"><b>2. WG members to review the suggested text from Sarah and Jim and provide comments on the list.<o:p></o:p></b></p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal">Recommendation 9:<o:p></o:p></p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal">Current text:<o:p></o:p></p>
<p class="MsoNormal">The working group recommends that:<o:p></o:p></p>
<p class="MsoNormal">9.1 The TAC MUST be only generated by the Registrar of Record upon request by the RNH or their designated representative.<o:p></o:p></p>
<p class="MsoNormal">9.2: When the Registrar of Record sets the TAC at the Registry, the Registry MUST securely store the TAC using a one-way hash that protects the TAC from disclosure.<o:p></o:p></p>
<p class="MsoNormal">9.3: When the Registrar of Record provides the TAC to the RNH or their designated representative, the Registrar of Record MUST also provide information about when the TAC will<o:p></o:p></p>
<p class="MsoNormal">expire.<o:p></o:p></p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal">From Jim Galvin:<o:p></o:p></p>
<p class="MsoNormal">9.2 When the Registrar of Record sets the TAC at the Registry, the Registry MUST store the TAC securely, at least according to the minimum requirement set forth in RFC 9154: using a strong one-way cryptographic hash with at least a 256-bit
hash function, such as SHA-256 [FIPS-180-4], and with a per-authorization information random salt with at least 128 bits. [FIPS-180-4]<o:p></o:p></p>
<p class="MsoNormal">National Institute of Standards and Technology, U.S. Department of Commerce, "Secure Hash Standard, NIST Federal Information Processing Standards (FIPS) Publication 180-4", DOI 10.6028/NIST.FIPS.180-4, August 2015, <https://csrc.nist.gov/publications/detail/fips/180/4/final>.<o:p></o:p></p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal">Discussion:<o:p></o:p></p>
<ul type="disc">
<li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This prevents the registry from storing TACs with encryption that is reversable. The registry can never recover the TAC. If it is
encrypted it could be recovered using the key. This means that the TAC is short lived and disposable.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Registry can compare them, not recreate them.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This is not current practice – this is a big improvement in security. How to make this clear.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">If the TAC is transformed into something only used for the transfer it would affect registrars who use the TAC for other confirmations/authorizations.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">If they are using it for something else don’t we should address that here. The TAC is supposed to be only for transfer.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Current TAC is not as private as people think it is.<o:p></o:p></span></li></ul>
<p class="MsoNormal">Recommendation 11: <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Current text: <o:p></o:p></p>
<p class="MsoNormal">The working group recommends that the TAC MUST be “one-time use.” In other words, it MUST be used no more than once per domain name. The Registry Operator MUST clear the TAC as part of completing the successful transfer request.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">From Jim Galvin: <o:p></o:p></p>
<p class="MsoNormal">The working group recommends that the TAC MUST be “one-time use.” In other words, it MUST be used no more than once per domain name. The Registrar of Record MUST meet this requirement by randomly creating a new TAC each time one is needed
as specified in Preliminary Recommendation 7. The Registry Operator MUST clear the TAC as part of completing the successful transfer request.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Discussion:<o:p></o:p></p>
<ul type="disc">
<li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Concern that this would force people to work with other people’s patented processes.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">For bulk transfers, still planning to use a TAC on a single domain – hadn’t yet recommended one TAC for multiple domains. Will be revisiting
this. In this case, “bulk” means that if you have 100 names you have 100 TACs.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">All Jim added was a sentence tying this to recommendation 7.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Seems like Recommendation 11 is valid without the additional text.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The current wording does not specify that the registrar of record is creating the TAC and links that to recommendation 7. Could amend
to take out the word “randomly” – you don’t need it if you are referencing recommendation 7.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Do think it’s useful to tie together the related recommendation.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Don’t understand the “MUST meet”.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Suggestion from Rick Wilhelm: “The working group recommends that the TAC as created by the Registrar of Record according to Preliminary
Recommendation 7, must be “one-time use.” In other words…”<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Proprietary, non-standard use of Auth-Info shall be broken by this.<o:p></o:p></span></li></ul>
<p class="MsoNormal"><b>ACTION ITEM: Jim Galvin and WG members to consider suggested change to the language as follows:
</b><b>“The working group recommends that the TAC as created by the Registrar of Record according to Preliminary Recommendation 7, must be “one-time use. In other words, it MUST be used no more than once per domain name. The Registry Operator MUST clear the
TAC as part of completing the successful transfer request.”<o:p></o:p></b></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">5. AOB<o:p></o:p></p>
<ol style="margin-top:0in" start="3" type="1">
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="mso-list:l0 level2 lfo6">Next call: Tuesday 10 May 2022 at 16:00 UTC<o:p></o:p></li></ul>
</ol>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>