<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" 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=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@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;
mso-ligatures:standardcontextual;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Team:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Rolling-up and sharing a number of conversations recently:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The Public Suffix List (PSL) (<a href="https://publicsuffix.org/">https://publicsuffix.org/</a>) is a volunteer-maintained list of TLDs and “TLD-like” domains like .com.cc, .co.uk, etc. PSL is lovingly maintained by Jothan and a small group
of folks for quite a while now. The uses of PSL vary widely. There are several other similar projects that effectively maintain lists of TLD-like things for one reason or another.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I believe it is a Finding for NCAP that such projects exist and have lose and widely varying relationships with the collisions phenomenon.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">PSL typically populates itself in one of two ways: (1) Observing IANA actions; and (2) Voluntary submissions. In the case of new gtlds, absent advance notification from ICANN/TRT, PSL would find out about the TLD at the time of an IANA
action (the first trial delegation by the TRT). I think there is only one NCAP consideration beyond the Finding – should ICANN/TRT “pre-advise” PSL (causing PSL publication prior to IANA action), or simply remain silent and allow PSL to pick it up in normal
course?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Like everything Collisions, there is no clear choice and arguments could be made either way. Issues related to end software updates against PSL snapshots and the associated time lags are both unknowable and fortunately out of our remit.<o:p></o:p></p>
<p class="MsoNormal"><o:p></o:p></p>
<p class="MsoNormal">Going back to first principals, we want to:<o:p></o:p></p>
<p class="MsoNormal">(1) Not hurt anything (beyond the intentionally designed notification interruptions)<o:p></o:p></p>
<p class="MsoNormal">(2) Notify those potentially impacted<o:p></o:p></p>
<p class="MsoNormal">(3) Collect data<o:p></o:p></p>
<p class="MsoNormal"><o:p></o:p></p>
<p class="MsoNormal">While I don’t know precisely all the ways folks use PSL, I can imagine the scenario we’re most interested in is software that analyzes a domain name looking thing to determine if it should use DNS to resolve it or do “something else” with
it (perhaps like sending it to search or another resolution mechanism). Given that, since all our assumptions and processes are predicated on the potentially colliding strings being queried in the DNS, I think we should pre-advise the PSL as soon as practical
and leave it at that. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thx,<o:p></o:p></p>
<p class="MsoNormal">Jeff<o:p></o:p></p>
</div>
</body>
</html>