On 14.12.22 12:25, Paul Wouters wrote: > On Dec 14, 2022, at 11:29, Eliot Lear <l...@lear.ch> wrote: > > > > > > We're off in the woods again. Let's keep these two principles in mind: > > > > The DNS resolution mechanisms are not expected to resolve, let alone secure > > names ending in .ALT. > > How other resolution mechanisms secure names is their affair. > I don’t think people disagree on this. > > > >> On 14.12.22 17:13, Paul Wouters wrote: > >> "bob.foo.alt" still squarely falls into "my" namespace > >> It is indeed not “yours”. > > ... from the perspective of DNS. Whether it is "yours" or "mine" from the > > perspective of GNS is a matter for GNS to resolve (for example). > > > I was not talking from the perspective of IETF or DNS. The .alt is the Wild > West. Even GNS cannot claim exclusivity of a chunk of it. It is competing > with all the other unregulated namespaces. >
Then the draft should just say that. And not insinuate that as a dev I can or should do something about that. > Martin said he cannot help other alternative namespaces using the same > alternative namespace as he is using. I merely confirmed that and recommend > that if he is looking for exclusivity, he has to leave the Wild West behind > and go to a regulated space and play within the rules set out there to get > his exclusive namespace. > If there is an obvious way to do it, the draft could give an example. Whatever you mean by "go to a regulated space" should be given with clear example. But as you well know, your wording is simply not without problems (IANA SU-TLD registry is technically also/still a "regulated space" that would fall within your wording). My best interpretation of the sentence is that it low-key defines a fcfs-style self-governance of .alt. Which would also be fine, but I have an issue with the unclear wording (i.e. I should not have interpret what the meaning of "wholly responsible for dealing with collisions" is). BR Martin > Paul > > > > > Eliot > > _______________________________________________ > > DNSOP mailing list > > DNSOP@ietf.org > > https://www.ietf.org/mailman/listinfo/dnsop > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
