<p dir="ltr">Thanks Ken and Kathy,<br>
My take from this brief discuss is our role to outreach in the area of 2FA and Whitelisting our Registrars. </p>
<p dir="ltr">It would reduce the bad experience and minimize damage should a malicious transfer occur.</p>
<p dir="ltr">While some of us would go ahead with such an insight, it brings me to the last statement in your response to Kathy; can we be specific on email and make an attempt to include an SMS, considering that the informations are available to the registrar? </p>
<p dir="ltr">Thank you.<br>
</p>
<br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Sep 27, 2024, 6:33 PM Ken Herman <<a href="mailto:ken@kherman.com">ken@kherman.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div>
<p dir="LTR"><span lang="en-us"><font face="Calibri">Hi Kathy. Thanks for yo</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">ur message.</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">I'm not sure how best to approach this</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri"> and present a practical suggestion that</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">, frankly, makes sense to the implementing</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">partners, i.e., the registrars</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">.</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">What I have heard most from the discussions is that</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">protection of the</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">RNH's</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">registrar account is p</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">aramount, since those are the keys to the kingdom,</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">along with RNH's protecting their e-mail accounts.</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">And, I might add, the registrar's need to protect the integrity of their own systems.</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri"></font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> </span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">The point is, if I make a change to my registered name, either</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">to</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">initiate a transfer or</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">to</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">change the registration data, especially the e-mail address I use, then either of these will result</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">in a notification, which i should expect. It's</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">the situation</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">where I</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><b> <font face="Calibri">did not</font></b></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri"> make the change that I need to be</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">worried about and I may, indeed, miss the notification. </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">I'm pretty sure the contracted parties will contend that</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri"></font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">it is not just a matter of missing one message</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">.</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">What I expect to hear is that t</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">o initiate a cha</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">nge in my registration would require a</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">n attacker</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">to gain access to my account and</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri"> in that case</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri"> is</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri"> likely</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">to</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">simply change the registration data, which would result in a message to the old and new contacts</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">, as per</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">"</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">Recommendation #27: Change of Registrant Data Notification</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">".</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri"></font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">If it's a malicious action and I see the message, then I can take action right away. If I miss the message, well, then it's a problem. So, what now?</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">I believe</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">the answer lies in</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">the Change of Registrant Data (CORD) recommendations.</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">We have already suggested in the comments on recommendation 26</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri"></font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">that we would like</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">to</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">impose</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">a transfer restrictio</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">n (which an RNH may opt out of)</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri"> after any material change</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">. We can further strengthen this by recommending that the registrar</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">require a confirmation of a material change to registration data from the old and new contact e-mail</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">before completing a material change of registration data.</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri"> This was the case in the original policy.</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">Would that satisfy?</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">I think there would be resistance to a requirement for multiple messages</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">to the same e-mail address</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">(none exists now) and</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">I</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">would struggle to find a good answer, whereas a greater protection of the account itself, throug</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">h a change confirmation process, might be a more practical option.</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">I have updated the comment document accordingly and here's the link for easy r</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">eference</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">:</font></span></p>
<p dir="LTR"><span lang="en-us"></span><a href="https://docs.google.com/document/d/1uM38-A98TYK-bED30l4Ue1cFJdNuHaZl/edit?usp=sharing&ouid=105988793481216121706&rtpof=true&sd=true" target="_blank" rel="noreferrer"><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><u><font color="#467886" face="Calibri">https://docs.google.com/document/d/1uM38-A98TYK-bED30l4Ue1cFJdNuHaZl/edit?usp=sharing&ouid=105988793481216121706&rtpof=true&sd=true</font></u></span><span lang="en-us"></span></a><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">A couple of other points…I believe there are no more admin contacts; it’s just the RNH</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri"> contact</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">.</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">Not sure about technical. Registrars might have more, but the data system only has the one.</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">Rec</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">ommendation 27 does</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">not limit</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri"> the registrar</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">to</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">one</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">secure methods (</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">e-mail or</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">SMS,</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">for example)</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">, but there is no requirement to</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font face="Calibri">use more than o</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">ne</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">.</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> </span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">Let me know what you think.</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">Ken</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"></span></p>
<p dir="LTR"><span lang="en-us"></span><a name="m_7385210669387516445_" rel="noreferrer"><span lang="en-us"></span></a></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">-----Original Message-----<br>
From: kathy@dnrc.tech <kathy@dnrc.tech><br>
Sent: Friday, September 27, 2024 12:09 PM<br>
To: Ken Herman <<a href="mailto:ken@kherman.com" target="_blank" rel="noreferrer">ken@kherman.com</a>><br>
Cc: <a href="mailto:NCSG-DISCUSS@listserv.syr.edu" target="_blank" rel="noreferrer">NCSG-DISCUSS@listserv.syr.edu</a><br>
Subject: Re: FW: Draft Comments - FW: Transfer Policy Review Preliminary Report - NCSG Public Comment Discussion</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">Hi Ken,</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">Tx for all your work on this issue. Years of work and effort!</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">I share Adebunmi's concerns below. How can we can request more than one notification -- at all major points along the way? One notice can go into a spam folder, as you mention below, or be lost completely when the power goes down (as in so many areas of US right now - since a large hurricane hit overnight). It seems a fair and reasonable principle that never should a notice on something important involving our domain names be an isolated one.</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">Precedent: In the Uniform Dispute Resolution Policy (UDRP) rules, we worked very hard for an "actual notice" standard - making sure that the Domain Name Registrant actually knows that the UDRP proceeding is taking place -- by requiring the complaint to be distributed via:</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">- Email to all the listed contacts (registrant, admin, tech), and</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">- "Written Notice to all postal-mail and facsimile addresses for the domain-name holder, administrative and technical contact (as applicable) shown in the domain name's Registration Data in Registrar's Registration Data Directory Service... [and] supplied by Registrar to the Provider for the registration's billing contact." (UDRP Rules)</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">****</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">Can we quickly expand our comments to ensure wide and fair notice - and certainly no single point of failure in the notice system?</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">Best and tx,</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">Kathy</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">On 2024-09-27 06:41, Ken Herman wrote:</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> Hello Adebunmi.</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> Thanks for your question. The proposed recommendations include many </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> areas where notifications of registration changes are sent to </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> registered name holders throughout the process. One key notification </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> can be found in recommendation 11, “Notification of TAC issuance”</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> which states:</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> “The working group recommends that the Registrar of Record MUST send a </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> “Notification of TAC</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> Issuance” to the RNH without undue delay but no later than 10 minutes </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> after the Registrar of</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> Record issues the TAC. For the purposes of sending the notification, </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> the Registrar of Record</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> MUST use contact information as it was in the registration data at the </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> time of the TAC request.”</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> Also, Recommendation #19: Notification of Transfer Completion contains </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> a requirement to notify when the transfer has been completed.</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> There are other places where notifications to registered name holders </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> have been added to the policy.</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> When it comes to quantity of notices, it is only going to be one per </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> instance. And, as far as whether or not a message goes to a RNH’s spam </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> folder, well, that isn’t under the control of the sender, in this case </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> the registrar involved.</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> As the non-commercial community, we may want to do more outreach to </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> constituents to ensure the adoption of good practices, like taking </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> advantage of multi-factor authentication when it is available and </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> whitelisting messages from important senders, like the registrars we </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> use. Also, as a constituency, we can advocate for registrars who have </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> not already done so to put in place security measures such as MFA.</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> I am sorry to hear of your bad experience with a notification, and </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> keep in mind that the policy mandates a 30-day transfer restriction </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> after a transfer, so if a domain is taken maliciously, there is time </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> to address the problem.</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> I hope this helps and once again, thank you for the question.</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> Ken</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> From: Adebunmi Akinbo <</font></span><span lang="en-us"></span><a href="mailto:adebunmi.akinbo@gmail.com" target="_blank" rel="noreferrer"><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">adebunmi.akinbo@gmail.com</font></span><span lang="en-us"></span></a><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">></font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> Sent: Wednesday, September 25, 2024 7:51 PM</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> To: Ken Herman <</font></span><span lang="en-us"></span><a href="mailto:ken@kherman.com" target="_blank" rel="noreferrer"><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">ken@kherman.com</font></span><span lang="en-us"></span></a><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">></font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> Cc:</font></span><span lang="en-us"> </span><a href="mailto:NCSG-DISCUSS@listserv.syr.edu" target="_blank" rel="noreferrer"><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">NCSG-DISCUSS@listserv.syr.edu</font></span><span lang="en-us"></span></a><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> Subject: Re: FW: Draft Comments - FW: Transfer Policy Review </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> Preliminary Report - NCSG Public Comment Discussion</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> Apologies for missing the meeting.</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> I will do my best to read the reworked comments, but I want to respond </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> briefly to your comment on the 30 days.</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> We should factor out the following questions and processes:</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> Question: What is the communication strategy to ensure the </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> non-commercial registered name user respond to any supposed malicious </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> transfer? Would it be once? When does it start counting? How sure are </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> we that such mails do not go to junk or spam mail?</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> From experience, I failed to respond to an ownership and my domain </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> name was restricted from use. My website stopped loading and my mails </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> failed. Apparently, the initial mail sent went to junk.</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> If the policy reflects a mandatory communication strategy, it may help </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> the seemingly non-commercial registered name holder an opportunity to </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> respond on time to a malicious domain name transfer.</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> My 2kobo!</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> On Thu, Sep 26, 2024, 12:31 AM Ken Herman <</font></span><span lang="en-us"></span><a href="mailto:ken@kherman.com" target="_blank" rel="noreferrer"><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">ken@kherman.com</font></span><span lang="en-us"></span></a><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">> wrote:</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Dear NCSG Members</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> I would like to thank everyone who attended today’s session on the </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Transfer Policy Review. I hope you all found the presentation useful </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> and for those unable to make it, Andrea has circulated a link to the </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> recording.</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> As a result of this review, and after examining the process for </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> submitting comments, I have reworked and edited the responses, and </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> you can find it at this link:</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">></font></span><span lang="en-us"> </span><a href="https://docs.google.com/document/d/1uM38-A98TYK-bED30l4Ue1cFJdNuHaZl/e" target="_blank" rel="noreferrer"><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">https://docs.google.com/document/d/1uM38-A98TYK-bED30l4Ue1cFJdNuHaZl/e</font></span><span lang="en-us"></span></a><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> dit?usp=sharing&ouid=105988793481216121706&rtpof=true&sd=true</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> As you will see, we won’t be uploading this document per se, but the </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> comments remain basically the same.</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Please have a look and provide any comments in the document or to me </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> by 23:00 UTC on Sunday, September 29, 2024. This will give me time to </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> incorporate into the responses prior to the submission deadline on </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Monday, September 30.</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Thanks again and I look forward to any input you may have.</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Best regards</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Ken</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> From: NCSG-Discuss <</font></span><span lang="en-us"></span><a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU" target="_blank" rel="noreferrer"><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">NCSG-DISCUSS@LISTSERV.SYR.EDU</font></span><span lang="en-us"></span></a><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">> On Behalf Of Ken </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Herman</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Sent: Monday, September 23, 2024 7:44 PM</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> To:</font></span><span lang="en-us"> </span><a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU" target="_blank" rel="noreferrer"><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">NCSG-DISCUSS@LISTSERV.SYR.EDU</font></span><span lang="en-us"></span></a><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Subject: Draft Comments - FW: Transfer Policy Review Preliminary </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Report - NCSG Public Comment Discussion</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Hello again fellow NCSG members</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> In preparation for our discussion on Wednesday, or as a way for </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> members unable to attend to contribute, you can find in the link </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> below some suggested text for our public comment.</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> ·Link Removed</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> The public comment is due next Monday, September 30, 2024, so I </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> welcome any additional points that you feel are important to raise </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> for this policy.</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> One aspect of the policy that I have been wondering about is the </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> transfer restrictions imposed after registration or a transfer. The </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> recommendation regarding this aspect of the policy imposes a 30-day </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> restriction (with some exceptions, which you can see I addressed in </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> the draft comments). I have no issue with the restriction itself, but </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> my question is whether or not 30-days (720 hours) is enough time. </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Keeping in mind that the transfer restrictions are in place for </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> security reasons, my experience is that the average non-commercial </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> registered name holder does not have substantial knowledge of domain </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> name management activities and may take some time to understand what </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> might be happening in the case of a malicious transfer. Therefore, </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> would 30 days be enough time to understand the issues and respond? If </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> not, what timeframe would be better and why? Or, is my assumption </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> incorrect and 30 days is generally sufficient.</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Your thoughts on this, or any of the other policy recommendations, </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> are most welcome and I look forward to our discussion on Wednesday.</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Best regards.</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Ken</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> From: NCSG-Discuss <</font></span><span lang="en-us"></span><a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU" target="_blank" rel="noreferrer"><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">NCSG-DISCUSS@LISTSERV.SYR.EDU</font></span><span lang="en-us"></span></a><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">> On Behalf Of Ken </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Herman</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Sent: Thursday, September 19, 2024 11:47 PM</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> To:</font></span><span lang="en-us"> </span><a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU" target="_blank" rel="noreferrer"><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">NCSG-DISCUSS@LISTSERV.SYR.EDU</font></span><span lang="en-us"></span></a><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Subject: Transfer Policy Review Preliminary Report - NCSG Public </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Comment Discussion</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Dear fellow NCSG members:</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> As I reported previously, the Transfer Policy review Working Group </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> (TPR WG) has completed its consideration of the issues outlined in </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> its charter and have produced its preliminary report. We are now in </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> the public comment period for this report, which closes at the end of </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> September. Recently, the TPR WG support team have run two webinars </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> describing the recommendations, along with an opportunity to ask </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> questions. The links to the recordings of these webinars are below.</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> As the deadline for comments approaches, your TPR WG NCSG </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> representatives (Juan and I) welcome all NCSG members to a working </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> session to consider any issues we may wish to include in our public </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> comment contribution.</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> We have arranged the call for Wednesday, September 25, 2024 @ 13:30 </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> UTC with the connection details below. I have also requested Andrea </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> to send these details as calendar invitations.</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> For your reference I have placed below links to the relevant </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> materials, including the NCSG public comment to the interim report </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> published in 2022.</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> I look forward to your participation in this discussion, but if you </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> cannot attend we welcome any written comments anyone may have.</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> As always, please feel free to contact me if you have any questions.</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Best regards</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Ken</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Join Zoom Meeting:</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">></font></span><span lang="en-us"> </span><a href="https://icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT" target="_blank" rel="noreferrer"><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">https://icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT</font></span><span lang="en-us"></span></a><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> 09</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Meeting ID: 988 7818 9584</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Passcode: i!y7.qx+11</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> One tap mobile</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> +16699006833,,98878189584#,,,,,,0#,,7740925615# US (San Jose)</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> +12532158782,,98878189584#,,,,,,0#,,7740925615# US (Tacoma)</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> PHONE ONLY DETAILS:</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Find your local number:</font></span><span lang="en-us"> </span><a href="https://icann.zoom.us/u/ayKmeftWg" target="_blank" rel="noreferrer"><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">https://icann.zoom.us/u/ayKmeftWg</font></span><span lang="en-us"></span></a><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Meeting ID: 988 7818 9584</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Phone only Passcode: 7740925615</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Transfer Policy Review PDP Page:</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">></font></span><span lang="en-us"> </span><a href="https://community.icann.org/display/TPRPDP/Transfer+Policy+Review+PDP" target="_blank" rel="noreferrer"><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">https://community.icann.org/display/TPRPDP/Transfer+Policy+Review+PDP</font></span><span lang="en-us"></span></a><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> TPR Public Comment page:</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">></font></span><span lang="en-us"> </span><a href="https://www.icann.org/en/public-comment/proceeding/initial-report-on-t" target="_blank" rel="noreferrer"><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">https://www.icann.org/en/public-comment/proceeding/initial-report-on-t</font></span><span lang="en-us"></span></a><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> he-transfer-policy-review-01-08-2024</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Transfer Policy Review Webinar 1:</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>></font></span><span lang="en-us"> </span><a href="https://community.icann.org/x/OgKkFQ" target="_blank" rel="noreferrer"><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">https://community.icann.org/x/OgKkFQ</font></span><span lang="en-us"></span></a><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> Transfer Policy Review Webinar 2:</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>></font></span><span lang="en-us"> </span><a href="https://community.icann.org/x/PAKkFQ" target="_blank" rel="noreferrer"><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">https://community.icann.org/x/PAKkFQ</font></span><span lang="en-us"></span></a><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> NCSG Response to preliminary report in 2022:</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">>> </font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">></font></span><span lang="en-us"> </span><a href="https://itp.cdn.icann.org/public-comment/proceeding/Initial%20Report%2" target="_blank" rel="noreferrer"><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"><font face="Calibri">https://itp.cdn.icann.org/public-comment/proceeding/Initial%20Report%2</font></span><span lang="en-us"></span></a><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> 0on%20the%20Transfer%20Policy%20Review%20-%20Phase%201(a)-21-06-2022/s</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> ubmissions/NCSG/NCSG%20Response%20-%20Transfer%20Policy%20Review-15-08</font></span></p>
<p dir="LTR"><span lang="en-us"><font face="Calibri">> -2022.pdf</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"></span></p>
</div>
</blockquote></div>