<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
<style>
div.plaintext { white-space: normal; }
body { font-family: sans-serif; }
div.plaintext h1 { font-size: 1.4em; }
div.plaintext h2 { font-size: 1.2em; }
div.plaintext h3 { font-size: 1.1em; }
blockquote.embedded,div.plaintext blockquote { margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777; }
blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote { border-left-color: #999999; color: #999999; }
blockquote.embedded blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote blockquote { border-left-color: #BBBBBB; color: #BBBBBB; }
blockquote.embedded,div.plaintext blockquote a { color: #777777; }
blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote a { color: #999999; }
blockquote.embedded blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote blockquote a { color: #BBBBBB; }
@media (prefers-color-scheme: dark) { blockquote { border-left-color: #BBBBBB; color: #BBBBBB; }
blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote { border-left-color: #999999; color: #999999; }
blockquote.embedded blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote blockquote { border-left-color: #777777; color: #777777; }
blockquote.embedded,div.plaintext blockquote a { color: #BBBBBB; }
blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote a { color: #999999; }
blockquote.embedded blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote blockquote a { color: #777777; }
}
div.plaintext math[display="inline"] > mrow { padding:5px; }
div.plaintext div.footnotes li p { margin: 0.2em 0; }
</style>
</head>
<body>
<div class="plaintext"><p dir="auto">I’m forwarding this on behalf of Steve Crocker for consideration by the discussion group.</p>
<br><br><p dir="auto">Forwarded message:</p>
<blockquote><p dir="auto">From: Steve Crocker <steve@shinkuro.com><br>
Date: Tue, 23 Apr 2019 19:11:00 -0400</p>
</blockquote><br></div>
<blockquote class="embedded"><div dir="ltr">Jim,<div><br></div><div>Thanks for the agenda and thanks to you and Jay for chairing this group.</div><div><br></div><div>I've spent time on this topic over the years, so I'll offer some thoughts right away.</div><div><br></div><div>It should be possible to define name collisions and explain them clearly for those who are not familiar with the phenomenon fairly quickly. I recommend this be done right away, prior to the three goals listed. This will be a qualitative, not quantitative, description and hence would not include any statement or measure of how much damage is caused by collisions. Instead it would provide a straightforward framework to build on. This should not take six months and should not take a lot of money.</div><div><br></div><div>Let me go a bit further and attempt a very short description.</div><div><br></div><div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div>Over the years, several strings have appeared as if they were top level names and have shown up in queries to the root even though these strings have never been delegated. The most common examples are corp, home, mail, local, localhost, example, belkin <<edit this list as needed.>> Queries to the root that end with one of these names are responded with the DNS protocol NXDOMAIN, i.e. this domain does not exist.</div><div><br></div></blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div>The reasons these names occur so frequently are somewhat varied and are mentioned below, but the reason these require attention is because they have been requested as official top level domains. That is, there are business interests that wish to have some of these strings delegated to them so they can run a registry.</div><div><br></div></blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div>As mentioned queries ending with these strings are already occurring. If these strings were to be delegated, such queries would be directed to the registry, thus changing behavior seen by the systems that generate those queries. It would also provide a channel for the delegated registry to respond to the systems generating the queries, with potentially negative effects. Finally, but probably less important, it would impose a load on the registry.</div><div><br></div></blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px">As mentioned, the reasons for such queries are a bit varied, but what's common in all cases is the queries are the result of some form of configuration error in the querying systems. In the case of belkin, some of their products were sold with .belkin configured into their software in a way that caused erroneous queries to leak onto the public Internet. In the case of .corp, the configuration manuals for the products from major companies instructed system administrators to use .corp as an enterprise level internal top level domain, and these systems also leaked queries onto the public Internet.<br><br>An added complication is many systems have scripts that try a sequence of queries. When the NXDOMAIN is received in response to an erroneous query sent over the public Internet, the querying system moves along to the next query in its script.<br><br>Delegation of strings that are appearing in numerous erroneous queries has the potential of causing harm to the system that are generating these queries. There are roughly four courses of action:<br></blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><ol><li>Refuse to delegate the string and leave things as they are.<br><br></li><li>Reduce or eliminate the erroneous queries by changing the configurations of the systems that generate these queries.<br><br></li><li>Make a determination that although delegation would change the status quo, the resulting harm would be acceptable.<br><br></li><li>Determine if there is a way to configure the registry to process erroneous requests so as to avoid harming the offending systems.</li></ol></blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px">Combinations of 2, 3 and 4 might be possible, and the course of action might be different for each string. Significant study and possible experimentation is required, although there have been previous studies of some of these.<br><br>In addition to the technical issues involved, this work requires exploring a policy question that has never been dealt with directly. In prior delegation of new top level domains, there was an implicit understanding that these names were fresh, i.e. had not been in use. With requests pending for names that have not been delegated but are nonetheless in use, ICANN is faced will have to develop a policy. This group may be able to assemble the facts related to the causes of erroneous queries for each string and the potential methods of mitigation, i.e. actions 2 or 4, but unless there is a way to reduce the level and causes of erroneous queries for these strings to the same level as for delegated TLD strings, ICANN Org and the community will have to developed a policy that balances competing interests.<br><br></blockquote>Cheers,</div><div><br></div><div>Steve</div><div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Apr 23, 2019 at 6:10 PM James Galvin <<a href="mailto:jgalvin@afilias.info" target="_blank">jgalvin@afilias.info</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">Hello and welcome from one of your co-chairs. Jay Daley is the other. <br>
We’ll introduce ourselves tomorrow during our first meeting.<br>
<br>
Here is the agenda:<br>
<br>
1. Introduction from the co-chairs and staff<br>
- who we are<br>
- how this discussion group will be managed<br>
- SOIs<br>
<br>
2. Introduction from discussion group members<br>
<br>
3. Introduction to NCAP<br>
- three studies<br>
- roles of OCTO / SSAC / Discussion Group<br>
- defining a name collision<br>
<br>
4. Current work<br>
- RFP being drafted<br>
- required output of study 1<br>
<br>
Attached to this document is the text we need to review and will be <br>
discussion in item 4 above. I’ve also attached it as a PDF to make <br>
sure everyone can read it.<br>
<br>
See you all on Wednesday, 24 April, 2000 UTC.<br>
<br>
Jim<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" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/ncap-discuss</a><br>
</blockquote></div></div></blockquote>
<div class="plaintext"><blockquote>
</blockquote></div>
</body>
</html>