<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: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;}
.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:756250541;
mso-list-template-ids:-643262152;}
@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:1528104060;
mso-list-template-ids:1720249476;}
@list l1:level1
{mso-level-start-at:3;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1: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 l1:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2
{mso-list-id:1569729526;
mso-list-type:hybrid;
mso-list-template-ids:1923227410 -837668794 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:"Times New Roman";}
@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:1629629332;
mso-list-template-ids:651876688;}
@list l3: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 l3: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 l3: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:Symbol;}
@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;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@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;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@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;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@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;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@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;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@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;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l4
{mso-list-id:1653682824;
mso-list-template-ids:1991680806;}
@list l4: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 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-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:Symbol;}
@list l4: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:Symbol;}
@list l4: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:Symbol;}
@list l4: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:Symbol;}
@list l4: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:Symbol;}
@list l4: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:Symbol;}
@list l4: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:Symbol;}
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,<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> 05 April 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><u><span style="color:black">Action Items</span>:<o:p></o:p></u></b></p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal"><b>ACTION ITEM: WG members to reply to the WG email distribution list if they are interested in joining a small team to review the NACKing/reasons for denial
<a href="https://docs.google.com/document/d/1L2bZnhJUY3VxyAjVCrkyVqdttOPn2EaqBARRRnEPd0Q/edit?usp=sharing">
working document</a> to finalize draft language for review by the full WG.<o:p></o:p></b></p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal"><b><span style="color:black">Transfer Policy Review Phase 1 - Meeting #</span>40</b><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:6.0pt;line-height:18.0pt"><b><span style="color:black">Tuesday </span>29 March<span style="color:black"> 202</span>2<span style="color:black"> at
</span>1600<span style="color:black"> UTC<o:p></o:p></span></b></p>
<p class="MsoNormal">1. Roll Call & SOI updates (5 minutes)</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">2. Welcome & Chair updates (5 minutes)<o:p></o:p></p>
<ul type="disc">
<li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">We left our denial/reasons for NACKing with open items; we are looking to have a spin-off small team to look at the NACKing working
document to clean up any items we left open. Maybe 5-6 people. Trying to get the draft language solidified to bring to the group. If you are interested let us know. Good to have a representative group if possible.<o:p></o:p></span></li></ul>
<p class="MsoNormal"><b>ACTION ITEM: WG members to reply to the WG email distribution list if they are interested in joining a small team to review the NACKing/reasons for denial
<a href="https://docs.google.com/document/d/1L2bZnhJUY3VxyAjVCrkyVqdttOPn2EaqBARRRnEPd0Q/edit?usp=sharing">
working document</a> to finalize draft language for review by the full WG.<o:p></o:p></b></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">3. Continue discussion on bulk use cases (75 minutes) – See:
<a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/1mqPITDShqiVQ4rH6x-FlvePmL_c05CtyWGgkpj9-77I/edit__;!!PtGJab4!u5fs92SBR8JlLJS9ITcQvLRgMHfmVRVZWgaXIpGpgOQAT04pBPWmLUJ954SbpWKV6cYQJIYAEA$" title="https://urldefense.com/v3/__https://docs.google.com/document/d/1mqPITDShqiVQ4rH6x-FlvePmL_c05CtyWGgkpj9-77I/edit__;!!PtGJab4!u5fs92SBR8JlLJS9ITcQvLRgMHfmVRVZWgaXIpGpgOQAT04pBPWmLUJ954SbpWKV6cYQJIYAEA$">
Working document [docs.google.com]</a><o:p></o:p></p>
<ul type="disc">
<li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Question for discussion: Are there two different paths – one where a year is added on; the other moving from one registrar to another
but not changing the life cycle?<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Question for discussion: Registry back-end operators – how would a transaction identify as a bulk transfer when it was one of many?
In a bulk scenario even if only 10 when they are going to multiple back-end registries? Would this be allowed? Put it differently, how many domain names do you need to make a bulk transfer?
<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Suggested Answer: (Theo Guerts) It is a question of scale. The sweet spot is around 2500 hundred domain names, because then you have
to plan your transfers in batches. Suggest not adding an extra year with a bulk transfer.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Maybe there’s two types of bulk. Some registries do this already and some don’t.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">If you transfer with multiple registries involved: If a registrar is contemplating transferring a bunch of names across registries –
you could have ones that aren’t interrelated.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">When we think about the normal transfer process it includes the extension of the registration term by 1 year in an automated fashion
over EPP, subject to FOA and NACKing. ICANN has a bulk transfer method without term extensions, but that involves certain business considerations. There is a PPA (partial portfolio) not by EPP and not with a term extension, but as a registry service.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">BTAPPA already does that and leaves the expiry date intact. (BTAPPA = Verisign bulk transfer service.)<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Other registries offer BTAPPA as well. But certain qualifications have to be met to use it. Simple bulk transfers not in conjunction
with a merger, sale, etc. are not allowed under BTAPPAs.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Question for Roger or staff: Is this out of scope for this WG?<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">When you do bulk transfers you have to prioritize. You go from TLD to TLD.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">it’s not clear how us adding simple bulk transfer would impact ICANN’s expedited RSEP for BTAPPA.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Resellers often are out of the question and we are stuck.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Bulk transfer is a database switch from registrar to registrar.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">When two different back-end registries are involved there are two different thought processes. Two separate scenarios.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Question: What number is considered bulk and does it apply to the registrar or registry?<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Bulk transfers are a very sharp knife/powerful tool. They are a very focused thing.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Question for Theo: What did you mean by “resellers are stuck”? Answer: The transfer process is focused on the registrant being able
to transfer wherever they like, and they have to help the resellers. Some registrars create barriers for resellers to transfer. A reseller can't easily move its business to a new Registrar. Resellers have the issue that they have no rights under the RAA.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">For bulk transfers you may have three scenarios – a few names, some names, a huge number of names. Are there three buckets or more?<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Holida can correct me if I am wrong, but I don't believe that there is a limit on who can report issues to Compliance. (Compliance agrees
that this is a correct observation.)<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">How can we make a policy binding for a contracted party but also for resellers who are not contracted? Or is there a different way
to handle this? We cannot create contract language for registrars.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">RAA Sec. 3.12: Registrar is responsible for the provision of Registrar Services for all Registered Names that Registrar sponsors being
performed in compliance with this Agreement, regardless of whether the Registrar Services are provided by Registrar or a third party, including a Reseller.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">There are two things: bulk transfers and BTAPPA. Standard transfer policy has a lot of requirements, while the BTAPPA is an industry
tool. BTAPPA wasn’t designed for bulk commercial use.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This bulk discussion is not about BTAPPA; we will talk about that later. Is there a policy that falls somewhere in between?<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Don’t think there is a charter question related to extending a year for a transfer. (Staff confirmed that there is not.)<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">BTAPPA comes at a pretty high cost – would there be fees associated with a bulk transfer between BTAPPA and the current policy?<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Is this a problem that this transfer policy should resolve, or does it fall outside of this policy? Maybe pose the question to the
community and ask for suggestions?<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Here is the charter question for the current phase of work:
<i>b5) Should the ability for registrants to request AuthInfo Codes in bulk be streamlined and codified? If so, should additional security measures be considered?</i><o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Not sure the charter question above relates to the current discussion.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Questions for phase 2:
<o:p></o:p></span>
<ul type="circle">
<li class="MsoListParagraph" style="mso-list:l2 level2 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">In light of these challenges described in section 3.1.7.2 of the Final Issue Report, should the required fee in Section I.B.2 of the
Transfer Policy be revisited or removed in certain circumstances? <o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level2 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Should the scope of voluntary bulk transfers, including partial bulk transfers, be expanded and/or made uniform across all registry
operators? If so, what types of rules and considerations should govern voluntary bulk transfers to partial bulk transfers?<o:p></o:p></span></li></ul>
</li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Some of this discussion may be more appropriate for phase 2.<o:p></o:p></span></li></ul>
<p class="MsoNormal"><b>Charter Question b5) Should the ability for registrants to request AuthInfo Codes in bulk be streamlined and codified? If so, should additional security measures be considered?<o:p></o:p></b></p>
<p class="MsoNormal"><i><span style="color:black">Note: As a starting point, this charter question was added in response to the following feedback to the Transfer Policy Status Report Survey from the RrSG:[It’s] [d]ifficult for Registered Name Holders to retrieve
[AuthInfo Codes] for a long list of domains as there are no requirements to permit bulk [AuthCode] requests. (Note: the discussion of partial bulk transfers and the BTAPPA process will be discussed in Phase 2 under question i2. This discussion is limited to
the consideration of bulk retrieval of AuthInfo Codes.)</span></i><o:p></o:p></p>
<ul type="disc">
<li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Do think there need to be additional security measures, compliance, and registries adding a claw-back option.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This is an interesting question – you get a bunch of names move in volume, but the request is to lower the security, which would make
it more dangerous. Seems that we should be looking at additional security measures.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Notifications are a big part of that security mechanism – do they need to be enhanced?<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Could bring in a lot of legal issues and problems for individual registrants, so having a claw-back mechanism could be helpful.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Re: the TAC and moving large numbers of names from one registrar to another – from a security point of view there should be one TAC
per name, but if you want to simplify the process maybe think about extra security for getting the single TAC for multiple domain names. If you are going to do multiple transfers in parallel then the TACs should have extra security, such as two-factor authentication.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">I’d like to see an additional communication method, requirement for password to be re-entered, capture of IP login etc. Just throwing
some ideas out there.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">In that scenario (using the same TAC on multiple domains) the Registrar could also remove (expire) the TAC after a shorter window.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Just because it’s possible to generate a TAC for each domain name transfer, doesn’t mean that all registrars will do it that way.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Should check to see if the current draft recommendations allow for efficient bulk transfers.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">If we wanted to be most security then the TAC should be unique for each domain name at the registrar. If you are randomly generating
them at each usage then you achieve that. But that is a bit tedious and not customer service friendly for bulk transfer, so you could add additional security feature for bulk transfers per domain name, such as two-factor authentication, or a shorter window
for TAC identity. Maybe as a suggestion rather than a must.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">If a TAC is unique at the registrar level is different from saying the TAC and domain name is unique.
<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">136867 – example authorization code from Google as a two-factor authentication. It expires after a short time, a window during which
it is valid. Needs to be paired with a URL for a certain amount of time.<o:p></o:p></span></li><li class="MsoListParagraph" style="mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The big focus is whether one TAC can be assigned to transfer multiple domain names and, if so, are there additional security measures.<o:p></o:p></span></li></ul>
<p class="MsoNormal">4. AOB (5 minutes) <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:l1 level2 lfo7">Next call: Tuesday 5 April 2022 at 16:00 UTC<o:p></o:p></li></ul>
</ol>
</div>
</body>
</html>