<div dir="auto"><div>Thanks Farzi and <span class="gmail_chip gmail_plusreply" dir="auto"><a href="mailto:nyamamutondo@gmail.com" style="color:#15c;text-decoration:underline">@nyamamutondo@gmail.com</a></span><span> for your responses. </span></div><div dir="auto"><span><br></span></div><div dir="auto"><span>Farzi, yes we did discuss that but it didn't appear that we had concluded on it. I will pass this position to council mailing list if this is agreeable to us all.</span></div><div><br></div><div data-smartmail="gmail_signature">Remain blessed, <br>Tomslin</div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Fri, 2 May 2025, 00:28 farzaneh badii, <<a href="mailto:farzaneh.badii@gmail.com">farzaneh.badii@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div class="gmail_default" style="font-family:arial,sans-serif">Tomslin,</div><div class="gmail_default" style="font-family:arial,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,sans-serif">Didn't we agree to defer indefinitely? It would be good to review it and try to bring privacy to every domain name registrant regardless of where they are but I don't think that is a battle we can win considering we don't have the resources and can't do that through this group and we can work on implementation of DPS which applies to all registrars and registries. </div><div class="gmail_default" style="font-family:arial,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,sans-serif"><br></div><br clear="all"></div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><font face="verdana, sans-serif">Farzaneh </font></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Apr 29, 2025 at 9:06 PM Tomslin Samme-Nlar <<a href="mailto:mesumbeslin@gmail.com" target="_blank" rel="noreferrer">mesumbeslin@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>FYI team.</div><div><br></div><div>I am keen to hear any thoughts on the questions posed below on the steps for the Whois Accuracy Implementation Advisory Group.</div><div><br></div><div><a class="gmail_plusreply" id="m_-8202236228218495424m_4704724825933058466plusReplyChip-1" href="mailto:stephanie@digitaldiscretion.ca" target="_blank" rel="noreferrer">@Stephanie E Perrin</a> looking to you for some guidance as well being our WHOIS expert then.</div><div><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><br></div><div>Remain blessed,<br></div>Tomslin</div></div></div></div></div></div></div></div></div></div></div></div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br>From: <b class="gmail_sendername" dir="auto">DiBiase, Gregory via council</b> <span dir="auto"><<a href="mailto:council@icann.org" target="_blank" rel="noreferrer">council@icann.org</a>></span><br>Date: Tue, 22 Apr 2025 at 02:28<br>Subject: [council] Next steps for the Whois Accuracy Implementation Advisory Group<br>To: <a href="mailto:Council@icann.org" target="_blank" rel="noreferrer">Council@icann.org</a> <<a href="mailto:council@icann.org" target="_blank" rel="noreferrer">council@icann.org</a>><br></div><br><br><div>
<div lang="EN-US">
<div>
<p class="MsoNormal"><span lang="EN" style="font-family:Calibri,sans-serif">Dear Councilors,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN" style="font-family:Calibri,sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN" style="font-family:Calibri,sans-serif">During our
<a href="https://icann.zoom.us/rec/play/m7OxKCA5oQ9K_waOhDVno3cyrjdqXBktXf0uHaIGJT6I2Eb0FFfQeqFoKB_c4ubaOu_TbhzPckCYh6hD.AbQmFxwkA4Jfe_VV?accessLevel=meeting&canPlayFromShare=true&from=share_recording_detail&startTime=1744318875000&componentName=rec-play&originRequestUrl=https%3A%2F%2Ficann.zoom.us%2Frec%2Fshare%2F1BdJrVMYICLOfeH4W7CEh-q9Udop0TZrUmaQ47ekzkZxRkwQ1GOzSHEEEIEUHhU.YVb3zS-ocr9VoJ41%3FstartTime%3D1744318875000" target="_blank" rel="noreferrer">
<span style="color:rgb(17,85,204)">April meeting</span></a>, we discussed potential next steps for the Whois Accuracy Implementation Advisory Group. Background and potential options are below (the
<a href="https://icann.zoom.us/rec/play/B88W5Be-pDdOMPBXvuhFOa3rbb00kxbNYyjHRGk-meJ7eQHa18dj1Uh26qT8Go6S3hRnLZuyyOYit559.zDpaiZC8Ajs4webS?accessLevel=meeting&canPlayFromShare=true&from=share_recording_detail&startTime=1744318875000&componentName=rec-play&originRequestUrl=https%3A%2F%2Ficann.zoom.us%2Frec%2Fshare%2F1BdJrVMYICLOfeH4W7CEh-q9Udop0TZrUmaQ47ekzkZxRkwQ1GOzSHEEEIEUHhU.YVb3zS-ocr9VoJ41%3FstartTime%3D1744318875000" target="_blank" rel="noreferrer">
<span style="color:rgb(17,85,204)">meeting recording</span></a> includes additional). Please discuss with your SGs and provide feedback by
<b>Friday, 2 May.</b><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN" style="font-family:Calibri,sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span lang="EN" style="font-family:Calibri,sans-serif">What is this procedure?<u></u><u></u></span></b></p>
<p class="MsoNormal"><b><span lang="EN" style="font-family:Calibri,sans-serif"><u></u> <u></u></span></b></p>
<p class="MsoNormal"><span lang="EN" style="font-family:Calibri,sans-serif">ICANN’s
<a href="https://www.icann.org/resources/pages/rdds-conflicts-procedure-2024-02-21-en" target="_blank" rel="noreferrer">
<span style="color:rgb(17,85,204)">Procedure For Handling Registration Data Directory Services Conflicts with Privacy Law</span></a> is a procedure that allows Contracted Parties to demonstrate when they are prevented by local laws from fully complying with the provisions
of ICANN contracts regarding personal data in RDDS. After receiving a recommendation from the 2003 Whois Task Force, the GNSO launched a PDP on this topic in 2005, and ICANN org implemented a procedure in 2006. The procedure was updated in 2017 to include
an alternative trigger.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN" style="font-family:Calibri,sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span lang="EN" style="font-family:Calibri,sans-serif">Why is the Council considering this now?
<u></u><u></u></span></b></p>
<p class="MsoNormal"><b><span lang="EN" style="font-family:Calibri,sans-serif"><u></u> <u></u></span></b></p>
<p class="MsoNormal"><span lang="EN" style="font-family:Calibri,sans-serif">Following the addition of the new alternative trigger to the procedure in 2017, the GNSO Council was set to review the procedure by launching a PDP. However, because the EPDP on the
Temporary Specification was engaged in parallel work, the GNSO Council decided to pause the call for volunteers until the EPDP Team delivered its report. Following the publication of the Final Report, ICANN org and Contracted Parties agreed to prioritize their
work on the Data Processing Specification prior to revisiting the Conflicts Procedure.
<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN" style="font-family:Calibri,sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN" style="font-family:Calibri,sans-serif">ICANN org published the
<a href="https://www.icann.org/resources/pages/data-processing-specification-requests-en#:~:text=The%20DPS%20is%3A,between%20%22independent%20controllers%22)." target="_blank" rel="noreferrer">
<span style="color:rgb(17,85,204)">Data Processing Specification</span></a> (DPS) in January 2025. Now that the DPS is complete, the Council is considering if/how it should proceed on reviewing the Conflicts Procedure.
<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN" style="font-family:Calibri,sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span lang="EN" style="font-family:Calibri,sans-serif">Questions to consider?<u></u><u></u></span></b></p>
<p class="MsoNormal"><b><span lang="EN" style="font-family:Calibri,sans-serif"><u></u> <u></u></span></b></p>
<p class="MsoNormal"><span lang="EN" style="font-family:Calibri,sans-serif">As discussed during the Council meeting and brought up councilors, some of the factors to consider in determining how to proceed include:<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN" style="font-family:Calibri,sans-serif"><u></u> <u></u></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal"><span lang="EN" style="font-family:Calibri,sans-serif">Do Contracted Parties (the parties who would use the procedure) believe this is an urgent need as no Contracted Parties have used the procedure in
years?<u></u><u></u></span></li><li class="MsoNormal"><span lang="EN" style="font-family:Calibri,sans-serif">Does the new Registration Data Policy, which becomes effective in August, obviate the need for a modification to the procedure?<u></u><u></u></span></li><li class="MsoNormal"><span lang="EN" style="font-family:Calibri,sans-serif">Does the Council believe this should be a priority, which would require other work to be de-prioritized?<u></u><u></u></span></li></ul>
<p class="MsoNormal"><span lang="EN" style="font-family:Calibri,sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span lang="EN" style="font-family:Calibri,sans-serif">Potential Options<u></u><u></u></span></b></p>
<p class="MsoNormal" style="margin-left:1in"><span lang="EN" style="font-family:Calibri,sans-serif"><u></u> <u></u></span></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal"><b><span lang="EN" style="font-family:Calibri,sans-serif">Defer/Leave procedure as is</span></b><span lang="EN" style="font-family:Calibri,sans-serif"><u></u><u></u></span>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal"><span lang="EN" style="font-family:Calibri,sans-serif">If Councilors (particularly Contracted Parties) do not believe this procedure needs an urgent modification, further work could be:<u></u><u></u></span>
<ol style="margin-top:0in" start="1" type="i">
<li class="MsoNormal"><b><span lang="EN" style="font-family:Calibri,sans-serif">Deferred indefinitely</span></b><span lang="EN" style="font-family:Calibri,sans-serif"> until the Community communicates a need to review (in
other words, leave the procedure alone until the Community informs Council it needs to be reviewed.)
<u></u><u></u></span></li><li class="MsoNormal"><b><span lang="EN" style="font-family:Calibri,sans-serif">Deferred for a finite amount of time</span></b><span lang="EN" style="font-family:Calibri,sans-serif"> (1 year, 2 years, etc.) to revisit if
updates may be needed<u></u><u></u></span></li></ol>
</li></ul>
</li><li class="MsoNormal"><b><span lang="EN" style="font-family:Calibri,sans-serif">Proceed with original plan - ICANN org to draft modification in consultation with CPs</span></b><span lang="EN" style="font-family:Calibri,sans-serif"><u></u><u></u></span>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal"><span lang="EN" style="font-family:Calibri,sans-serif">If Councilors (particularly Contracted Parties) believe this work is urgent and important, the Council
<b>could request ICANN org to draft a modification</b> to the procedure in consultation with Contracted Parties before sharing with the Council. (As noted above, due to resource constraints, the Council would need to determine what work can be de-prioritized
in order to prioritize this work.)<u></u><u></u></span></li></ul>
</li><li class="MsoNormal"><b><span lang="EN" style="font-family:Calibri,sans-serif">Terminate/Retire procedure</span></b><span lang="EN" style="font-family:Calibri,sans-serif"><u></u><u></u></span>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal"><span lang="EN" style="font-family:Calibri,sans-serif">During the meeting, some councilors noted it may be worth terminating/retiring this procedure due to flaws. It is important to note that the termination/retirement
of the procedure <b>would require further policy work</b> as this procedure is the product of GNSO policy recommendations. If the Council does not want to extend resources on this procedure at this time, it may be worth exploring Option 1.
<u></u><u></u></span></li></ul>
</li></ol>
<p class="MsoNormal"><span lang="EN" style="font-family:Calibri,sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span lang="EN" style="font-family:Calibri,sans-serif">Deadline for Feedback?<u></u><u></u></span></b></p>
<p class="MsoNormal"><b><span lang="EN" style="font-family:Calibri,sans-serif"><u></u> <u></u></span></b></p>
<p class="MsoNormal"><span lang="EN" style="font-family:Calibri,sans-serif">Please socialize with your respective SG/Cs and let the Council know how you think it should proceed by
<b>Friday, 2 May.<u></u><u></u></b></span></p>
<p class="MsoNormal"><b><span lang="EN" style="font-family:Calibri,sans-serif"><u></u> <u></u></span></b></p>
<p class="MsoNormal"><span lang="EN" style="font-family:Calibri,sans-serif">Thanks,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN" style="font-family:Calibri,sans-serif">Greg<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:Calibri,sans-serif"><u></u> <u></u></span></p>
</div>
</div>
_______________________________________________<br>
council mailing list -- <a href="mailto:council@icann.org" target="_blank" rel="noreferrer">council@icann.org</a><br>
To unsubscribe send an email to <a href="mailto:council-leave@icann.org" target="_blank" rel="noreferrer">council-leave@icann.org</a><br>
<br>
_______________________________________________<br>
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" rel="noreferrer noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer noreferrer" target="_blank">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</div></div></div>
_______________________________________________<br>
NCSG-PC mailing list<br>
<a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank" rel="noreferrer">NCSG-PC@lists.ncsg.is</a><br>
<a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" rel="noreferrer noreferrer" target="_blank">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a><br>
</blockquote></div>
</blockquote></div>