On Sep 18, 2017, at 10:20 AM, Ted Hardie <ted.ietf@xxxxxxxxx> wrote: > Does this add a new tool for DNS systems attempting resolution to use when previous efforts are blocked? So any DNS resolution might use it, whether from a browser, an app, or system call, but that those would not *specify* it be used? > > Does this add a method for Web application to directly resolve DNS resource records using a resolver self-identified in the Javascript? So DNS resolutions are instantiated and consumed by Javascript without any intermediation by the local DNS resolver or the browser's DNS rules? > > Does this charter aim for the working group to do both? > > As currently written, I see the charter describing 1. Then that may be a failure of the current charter text. > There has been an argument that it also do 2 or that 2 becomes possible when 1 is specified and is thus automatically part of the scope. If that is the case, I believe the charter needs a re-write to describe it. In the many discussions leading up to the -00 wording for the charter (which became much longer in IESG discussion), #2 was the clear use case. --Paul Hoffman