<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 10:33 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=""><span style="caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; 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; float: none; display: inline !important;" class="">But what about in the future if someone in the IETF want to create a special use domain for IOT or what about a string that corresponds with a brand?</span><br style="caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; 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;" class=""></div></blockquote><div><br class=""></div>Hence the proposal to use a set of strings that, because they are specified by the recognized authority (ISO-3166/MA) as assigned for user defined use, are not delegatable in the DNS according to existing policy. This is in contrast to pretty much any other string as there is (AFAIK) no policy that says those (non-ISO-3166) strings can’t be used in some future new gTLD round. </div><div><br class=""><blockquote type="cite" class=""><div class=""><span style="caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; 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; float: none; display: inline !important;" class="">The only thing I am objecting to, to the extent I am even objecting, is that there seems to be some resistance to multi-organizational collaboration. </span></div></blockquote><div><br class=""></div><div>There is no resistance that I’m aware of (at least on the part of Roy, Ed, or myself). I’m unclear why you would interpret a document being published as an Internet Draft in the IETF as an attempt to “circumvent” the multistakeholder process. I’ve asked in a previous message: <span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">where/how would you propose Roy and Ed publish their idea?</span></div><br class=""><blockquote type="cite" class=""><div class=""><span style="caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; 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; float: none; display: inline !important;" class="">Anyway, I think the main point is to encourage cross organizational discussions.</span><br style="caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; 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;" class=""></div></blockquote></div><br class=""><style class="">ul[class*='mb-extra__public-links'], ul[class*='mb-note__public-links'], ul[class*='mb-task__public-links'] { display: none !important; }</style><div class="">Looks like there is indeed a lively discussion: <a href="https://www.ietf.org/mailman/listinfo/dnsop" class="">https://www.ietf.org/mailman/listinfo/dnsop</a>, archives at <a href="https://mailarchive.ietf.org/arch/browse/dnsop/" class="">https://mailarchive.ietf.org/arch/browse/dnsop/</a> (which I’d probably recommend reviewing before jumping into the fray).</div><div class=""><br class=""></div><div class="">Regards,</div><div class="">-drc</div><div class=""><br class=""></div></body></html>