Very helpful! Some very minor feedback for any potential next version:

- Add reference to draft-bretelle-dprive-dot-for-insecure-delegations-00
- Section 3, 1st para is about auth with secure delegation in conflict with the 
section title. Perhaps s/Authenticating an insecure delegation/Authentication 
and describe auth w/secure delegation briefly in a new 3.1. Alternatively, the 
auth w/secure delegation bit is a tiny section of it's own and what is now S3 
becomes S4 with the current section title.

In preparation for IETF-106, we are tracking open Qs for WG discussion at 
https://github.com/alex-nicat/ietf-dprive-phase2-requirements/issues/20. Feel 
free to add to that.

Jason

On 11/4/19, 2:56 PM, "dns-privacy on behalf of John R Levine" 
<[email protected] on behalf of [email protected]> wrote:

    On Sun, 3 Nov 2019, John Levine wrote:
    > I thought it might be useful to make a list of possible ways to signal
    > that a server offers ADoT:
    >
    > https://datatracker.ietf.org/doc/draft-levine-dprive-signal/

    Did another version with more possibilities.

    Regards,
    John Levine, [email protected], Taughannock Networks, Trumansburg NY
    Please consider the environment before reading this e-mail. https://jl.ly

    _______________________________________________
    dns-privacy mailing list
    [email protected]
    https://www.ietf.org/mailman/listinfo/dns-privacy


_______________________________________________
dns-privacy mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dns-privacy

Reply via email to