<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body><div style="font-family: sans-serif;"><div class="plaintext" style="white-space: normal;"><p dir="auto">Thanks for bringing these points to the discussion group.</p>
<p dir="auto">As we develop our final work product, we need to consider the intended audience(s) and the opportunity to review and perhaps reconsider each next step as an application progresses through the steps we are proposing in our workflow framework.</p>
<p dir="auto">Jim</p>
<br><br><p dir="auto">On 21 Dec 2021, at 8:53, Steve Crocker wrote:</p>
</div><blockquote class="embedded" style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777;"><div id="9F8A534E-01EC-43B1-A468-02032263151E">
<div dir="ltr">
<div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#000000">Jim,<br></div>
<div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#000000"><br></div>
<div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#000000">I think the comment I made during your presentation at the SSAC monthly meeting is related to Anne's question. The multi-step process develops additional information at each step. After each step, it's natural to assess how much is known, and how much more needs to be learned, And, of course, if the situation is clear enough before going through the whole process, there's no reason to continue.</div>
<div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#000000"><br></div>
<div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#000000">The other point I suggested is to provide assessments from multiple points of view -- the applicant, ICANN Org, and one or more groups of others such as other domain name holders and/or general Internet users.</div>
<div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#000000"><br></div>
<div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#000000">Thanks,</div>
<div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#000000"><br></div>
<div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#000000">Steve</div>
<div class="gmail_default" style="font-family:arial,sans-serif;font-size:small;color:#000000"><br></div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Dec 21, 2021 at 5:10 AM James Galvin <<a href="mailto:galvin@elistx.com">galvin@elistx.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>
<div style="font-family:sans-serif">
<div style="white-space:normal">
<p dir="auto">Anne,</p>
<p dir="auto">I’ve been thinking about your question. I will offer my own perspective and would welcome comments from others.</p>
<p dir="auto">On the one hand, the case study that was done for .corp, .home, .mail, lan., .local, and .internal could provide all the information the Board needs to make a decision, in part because the Board might choose to make its decision based on the 2021 overall process.</p>
<p dir="auto">On the other hand, you’re right, the Board could choose to exercise explicitly the workflow framework we’re proposing and use that to make its final decision.</p>
<p dir="auto">So, whether or not we should recommend a pilot is a good question for further discussion. It’d be great if folks would contribute some thoughts here, on the list.</p>
<p dir="auto">Regardless, please do keep the question in mind and make sure we don’t forget to revisit.</p>
<p dir="auto">Jennifer, would you please capture this question for our agenda?</p>
<p dir="auto">Thanks,</p>
<p dir="auto">Jim</p>
<br>
<br>
<p dir="auto">On 15 Dec 2021, at 14:41, Aikman-Scalese, Anne wrote:</p>
</div>
<blockquote style="margin:0px 0px 5px;padding-left:5px;border-left:2px solid rgb(119,119,119);color:rgb(119,119,119)">
<div id="gmail-m_-59304352895095532544D32E350-DEA4-4B9D-887C-F32224E6C151">
<div lang="EN-US">
<div>
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Thanks Jim. I probably should have brought this up on the call but is it possible that the DG should be recommending that ICANN test the system of controlled interruption we are endorsing on strings that were previously applied-for in 2012 and not delegated due to Name Collision issues? I believe that some of those applications have never been withdrawn – e.g. in relation to .corp, .home, and .mail - and if the framework that evolves from the DG is accepted and moves forward, it would seem that those stings might provide good “test cases” of the types of controlled interruption we are recommending, e.g. a type of “pilot” for the Board to consider.</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Anne</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></p>
<div>
<table border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<tbody>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt">
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif;line-height:106%"><b><span style="font-size:11pt;line-height:106%;font-family:"Trebuchet MS",sans-serif;color:rgb(50,50,50)">Anne E. Aikman-Scalese</span></b></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt">
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif;margin-bottom:3pt;line-height:106%"><span style="font-size:11pt;line-height:106%;font-family:"Trebuchet MS",sans-serif;color:rgb(50,50,50)">Of Counsel</span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt">
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif;margin-bottom:3pt;line-height:40%"><span style="font-size:10pt;line-height:40%;font-family:"Trebuchet MS",sans-serif;color:rgb(31,73,125)"><img width="17" height="7" style="width: 0.177in; height: 0.0729in;" id="gmail-m_-5930435289509553254Picture_x0020_2"></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt">
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif;line-height:106%"><span style="font-size:10pt;line-height:106%;font-family:"Trebuchet MS",sans-serif;color:rgb(31,73,125)"><a href="mailto:AAikman@lewisroca.com" title="Email User" target="_blank"><span style="color:rgb(50,50,50)">AAikman@lewisroca.com</span></a></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt">
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif;margin-bottom:0.25in;line-height:106%"><span style="font-size:10pt;line-height:106%;font-family:"Trebuchet MS",sans-serif;color:rgb(50,50,50)">D. 520.629.4428</span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt">
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif;line-height:106%"><span style="font-size:10pt;line-height:106%;font-family:"Trebuchet MS",sans-serif;color:rgb(31,73,125)"><img border="0" width="160" height="22" style="width: 1.6666in; height: 0.2291in;" id="gmail-m_-5930435289509553254Picture_x0020_1"></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt"></td>
</tr>
</tbody>
</table>
</div>
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></p>
<div>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif"><b><span style="font-size:11pt;font-family:Calibri,sans-serif">From:</span></b> <span style="font-size:11pt;font-family:Calibri,sans-serif">James Galvin <<a href="mailto:galvin@elistx.com" target="_blank">galvin@elistx.com</a>><br>
<b>Sent:</b> Wednesday, December 15, 2021 11:11 AM<br>
<b>To:</b> Aikman-Scalese, Anne <<a href="mailto:AAikman@lewisroca.com" target="_blank">AAikman@lewisroca.com</a>><br>
<b>Cc:</b> Jothan Frakes <<a href="mailto:jothan@jothan.com" target="_blank">jothan@jothan.com</a>>; NCAP Discussion Group <<a href="mailto:ncap-discuss@icann.org" target="_blank">ncap-discuss@icann.org</a>><br>
<b>Subject:</b> Re: [NCAP-Discuss] Draft Final Proposed Workflow</span></p>
</div>
</div>
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif"> </p>
<div>
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif"><strong><span style="font-size:9pt;font-family:Helvetica,sans-serif;color:black">[EXTERNAL]</span></strong></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center"></div>
</div>
<div>
<div>
<p style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif">Anne,</p>
<p style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif">Speaking personally, while I agree with the sentiment I have to be honest and point out that I don’t think we’ll be able to fully achieve this, in part because we know we won’t be able to have a full picture of name collisions until after controlled interruption. We know this from the Data Sensitivity Analysis.</p>
<p style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif">The applicant will have a partial view of the risk of applying based on their review of the public information that ICANN will publish (and in fact already are). Currently, an applicant will have to make this determination themselves, i.e., there won’t be any advice from ICANN or the Board on this point.</p>
<p style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif">Speaking as a co-Chair, there may very well be some “business issues” to be discussed that will need to find a home, since these will be out of scope for NCAP.</p>
<p style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif">Jim</p>
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif"> </p>
<p style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif">On 8 Dec 2021, at 16:59, Aikman-Scalese, Anne wrote:</p>
</div>
<blockquote style="margin-top:5pt;margin-bottom:5pt">
<div id="gmail-m_-5930435289509553254B0DEBF7F-ACF1-4C8D-8B30-319032A051DC">
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Thanks Jim and Jonathan,</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">I think this discussion gets to the point that Tom Barrett was trying to make on today’s call – that there should be a technical mechanism for informing a potential applicant of the degree of risk of non-award of the contract at some point before application is made and a large application fee is paid. In other words, if the potential applicant has a way to assess name collision risk as “high”, then the applicant may not waste resources on that particular string. This is consistent with the notion coming out of the Sub Pro Final Report which resulted in a Recommendation to the Board that a DO NOT APPLY list be developed prior to the launch of the next round.</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></p>
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Otherwise, we are saying “go ahead and develop your business plan and pay your application fee and later if name collision risk is too high and the string can’t be delegated, you might get a partial or total refund.” That seems like something that should be avoided.</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></p>
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Anne</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></p>
<div>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif"><b><span style="font-size:11pt;font-family:Calibri,sans-serif">From:</span></b> <span style="font-size:11pt;font-family:Calibri,sans-serif">NCAP-Discuss <<a href="mailto:ncap-discuss-bounces@icann.org" target="_blank">ncap-discuss-bounces@icann.org</a>> <b>On Behalf Of</b> James Galvin<br>
<b>Sent:</b> Wednesday, December 8, 2021 2:33 PM<br>
<b>To:</b> Jothan Frakes <<a href="mailto:jothan@jothan.com" target="_blank">jothan@jothan.com</a>><br>
<b>Cc:</b> NCAP Discussion Group <<a href="mailto:ncap-discuss@icann.org" target="_blank">ncap-discuss@icann.org</a>><br>
<b>Subject:</b> Re: [NCAP-Discuss] Draft Final Proposed Workflow</span></p>
</div>
</div>
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif"> </p>
<div>
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif"><strong><span style="font-size:9pt;font-family:Helvetica,sans-serif;color:black">[EXTERNAL]</span></strong></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center"></div>
</div>
<div>
<div>
<p style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif">An important distinction to make is whether we are using “delegation” in a technical sense or a business sense.</p>
<p style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif">In a technical sense, you are correct. A string must be delegated (be present in the root zone) in order for controlled interruption and enhanced controlled interruption to work. And, if there is an issue created as a result of name collisions then the delegation must be withdrawn.</p>
<p style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif">This is separate and independent from the business decision of deciding to delegate a proposed TLD string to a particular registry operator, which if successful would also require a technical delegation in order for the string “to work”.</p>
<p style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif">The technical delegation is part of the due diligence process. There is no change in predictability to an applicant as compared to the application process as a whole.</p>
<p style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif">Since you mention “applicant” in the context of your question I believe you’re asking about business delegation and that is out of scope for this working group.</p>
<p style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif">Jim</p>
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif;margin-bottom:12pt"> </p>
<p style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif">On 1 Dec 2021, at 14:43, Jothan Frakes wrote:</p>
</div>
<blockquote style="margin-top:5pt;margin-bottom:5pt">
<div id="gmail-m_-59304352895095532547C6CE784-8D1B-4A1A-B27C-B611F55F58AE">
<div>
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif">I am concerned an item on about slides 9&10<br>
<br>
"Does not guarantee approval of permanent delegation"<br>
<br>
Is this contemplating a scenario where a TLD would get revoked _after_ it is delegated due to some NC issue? <br>
<br>
It seems there needs to be a horizon of certainty to an applicant as a reasonable expectation.<br>
<br>
<br clear="all"></p>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif;margin-bottom:12pt"><br>
Jothan Frakes<br>
Tel: +1.206-355-0230</p>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif"> </p>
</div>
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif"> </p>
<div>
<div>
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif">On Wed, Dec 1, 2021 at 10:47 AM Aikman-Scalese, Anne <<a href="mailto:AAikman@lewisroca.com" target="_blank">AAikman@lewisroca.com</a>> wrote:</p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin:5pt 0in 5pt 4.8pt">
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif">Thanks Jim. I may have missed a meeting, but during today's meeting, will you elaborate on the specific differences between "Controlled Interruption" and "Enhanced Controlled Interruption" and why the word, "honeypot", has disappeared from the slides?<br>
Thank you,<br>
Anne<br>
<br>
-----Original Message-----<br>
From: NCAP-Discuss <<a href="mailto:ncap-discuss-bounces@icann.org" target="_blank">ncap-discuss-bounces@icann.org</a>> On Behalf Of James Galvin<br>
Sent: Wednesday, December 1, 2021 9:35 AM<br>
To: NCAP Discussion Group <<a href="mailto:ncap-discuss@icann.org" target="_blank">ncap-discuss@icann.org</a>><br>
Subject: [NCAP-Discuss] Draft Final Proposed Workflow<br>
<br>
[EXTERNAL]<br>
<br>
Attached is a PDF of the slides describing the workflow for those who don’t have ready access to the Shared Drive.<br>
<br>
This is now draft final, which means we will start to progress producing our final work product based on this. We’ll talk more about this today.<br>
<br>
Thanks to all!<br>
<br>
Jim<br>
<br>
________________________________<br>
<br>
This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.<br>
_______________________________________________<br>
NCAP-Discuss mailing list<br>
<a href="mailto:NCAP-Discuss@icann.org" target="_blank">NCAP-Discuss@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/ncap-discuss" target="_blank">https://mm.icann.org/mailman/listinfo/ncap-discuss</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" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" 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.</p>
</blockquote>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif"> </p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center"></div>
<p class="MsoNormal" style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:"Times New Roman",serif"><span style="font-size:7.5pt;font-family:Arial,sans-serif;color:gray"><br>
This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.</span></p>
</div>
</blockquote>
</div>
</div>
<br>
<hr>
<font face="Arial" color="gray" size="1"><br>
This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.<br></font></div>
</div>
</blockquote>
<div style="white-space:normal"></div>
</div>
</div>
_______________________________________________<br>
NCAP-Discuss mailing list<br>
<a href="mailto:NCAP-Discuss@icann.org" target="_blank">NCAP-Discuss@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/ncap-discuss" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/ncap-discuss</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" 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" 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.</blockquote>
</div></div></blockquote>
<div class="plaintext" style="white-space: normal;">
</div>
</div></body>
</html>