Hi Paul, On 2 Nov 2020, at 12:19, Paul Wouters <[email protected]> wrote:
> On Mon, 2 Nov 2020, Roy Arends wrote: > >> As for version -01, the authors propose to separate the document into two: >> >> (1) A document that discusses the motivation for private space top level >> domains, provides recommendations for people setting them up, etc. > > The IETF / DNSOP should not recommend setting up private space TLDs by > instructing people how to do this. We anticipated that there would be differences of opinion around this set of topics that might be difficult to resolve. This is the motivation of splitting the issues into different documents, really. >> (2) A document to note that ISO policy supports using ISO3166 User Assigned >> code elements to anchor private namespaces, recognise that use and, finally, >> recommend against use of these code elements for any other purposes that >> cause operational or security problems (e.g. due to collisions with >> delegations in the root zone). > > I still don't see the value in this, but there is also no harm done > describing this. So I am ambivalent on this. It seemed to us that the needle of consensus might be more consistently in that kind of green arc for this topic, too. > In general, I'm mostly afraid that this/these document(s) will eat up a > lot of DNSOP resources/time, seeing more Special Domain discussions and > all, while naming things is really outside of IETF/DNSOPS area. I am confident that our chairs are listening and are aware of the lack of jurisdictional clarity on this point. Joe _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
