<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Jeff,<br class=""><div><br class=""></div><div>On Jun 15, 2020, at 8:02 AM, Jeff Neuman <<a href="mailto:jeff.neuman@comlaude.com" class="">jeff.neuman@comlaude.com</a>> wrote:<br class=""><blockquote type="cite" class=""><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 11px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">ICANN, as far as I can tell, does not have a consensus policy that states that once ISO-3166 codes are created anyone can use it for any purpose. <span style="font-size: 11pt;" class="">If there is such a policy, I would love to see it. </span></div></div></div></blockquote><div><br class=""></div><div>Traditionally (as long as I’ve been doing DNS stuff, i.e., 1984-ish), 2-letter ISO-3166 codes have been the domain (pun intended) of ISO-3166/MA and the entities to which ISO-3166/MA assigns control. I am unaware that such control is a subject of ICANN consensus policy, and in the lack of such a policy, my understanding has been that previous usage applied. I gather your view is different?</div><div><br class=""></div><blockquote type="cite" class=""><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 11px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class="">ISO assigns to character codes, yes. But ISO does not assign 2 character domains? </span></div></div></div></blockquote><div><br class=""></div>No, but as you know, since around 1984, a 2-letter code cannot be delegated unless it is assigned by ISO-3166/MA. ISO-3166/MA has assigned a set of codes to be “user defined” codes, which means they can’t be delegated by ICANN as there is (by definition) no single entity that has been assigned control, thus it would seem to make sense (IMHO) to use them for private namespaces if you want to avoid potential collision. </div><div><br class=""><blockquote type="cite" class=""><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 11px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class="">That is within ICANN’s purview. </span><span style="font-size: 11pt;" class="">Yes, we through the ICANN processes have acknowledged the right of ccTLDs to use their assigned codes as ccTLDs, </span></div></div></div></blockquote><div><br class=""></div>An interesting perspective. To be honest, I’m not sure that is a right ICANN has the ability to give or take away, but that’s a probably a different discussion.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 11px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class="">but to my knowledge, ICANN has never discussed the ability to use other ISO code lists for other purposes.</span></div></div></div></blockquote><br class=""></div><div>OK, but (a) we’re talking about private namespaces which, by definition, ICANN has no control over and (b) Roy/Ed are not speaking for ICANN in any way.</div><div><br class=""><blockquote type="cite" class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 11px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Why should anyone be averse to having this discussion within the ICANN community and why did Roy and Ed decide that the right venue to discuss this issue was the IETF. To me this is policy issue and not a technical issue?</div></div></blockquote><div><br class=""></div>Not to speak for Roy/Ed (I haven’t spoken to them about this), my guess is that they used the technical forum they were most familiar with. It might also be that they view publishing via the IETF as being more likely to result in the document being read by the folks who would be considering squatting on an “unused” string. I wouldn’t imagine they’d be against publishing the document elsewhere, after all, the intent of Internet Drafts is to facilitate discussion, regardless of venue. However, where/how would you propose they publish?</div><div><br class=""></div><div>Regards,</div><div>-drc</div><div><br class=""></div><style class="">ul[class*='mb-extra__public-links'], ul[class*='mb-note__public-links'], ul[class*='mb-task__public-links'] { display: none !important; }</style></body></html>