Hi Paul, the draft lgtm. But, the passage regarding collisions because of the missing registry now contains a regression IMO:
"Developers are wholly responsible for dealing with any collisions" I think this is an impossible task and as a developer that is addressed here I have to say that we cannot do that unilaterally for our implementation/design because collisions occur when _others_ do something. Maybe you are talking about "groups" (as used in this paragraph) or the "alternative name system community" here, which would make more sense? This paragraph also uses both "groups" and "developers", and the difference (to me) is not clear. Maybe simply strike this sentence again? Instead or in addition maybe a full acknowledment of this issue in the security considerations, along the lines of " This draft does not define a registry or governance model for the .alt namespace and as such developers/groups as well as users and applications cannot expect unambiguous mappings from names with a ".alt"-TLD to a specific alternative name space / name resolution mechanism. This issue can be mitigated, for example, through the creation and use of a registry by the alternative name system developer community. " Best Martin On 13.12.22 20:20, Paul Hoffman wrote: > Greetings again. As you can see, Warren and I just updated the draft to > reflect the WG discussion at IETF 115 and on the list after that. At IETF > 115, the WG chairs said that they might move this to a second WG Last Call > soon. > > In the discussion, there was lots of active disagreement about reducing > traffic to the root servers, particularly around what it would mean for > recursive resolvers filtering for .alt. One such proposal that came up was > scrapping this draft and moving to AS112, but there was little interest and > some strong pushback. > > Thus, we did not include any proposed way to do this in the new draft, > although we did make a strong push towards methods resolvers could use that > would reduce root queries for names ending not only in .alt, but all other > non-existent TLDs. > > --Paul Hoffman > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop
signature.asc
Description: PGP signature
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
