Hi all, This revision https://tools.ietf.org/html/draft-reddy-dprive-dprive-privacy-policy-02 addresses comments from the WG at IETF-106. This updated document defines a mechanism for a DNS server to communicate its privacy statement URL and filtering policy to a DNS client. This communication is cryptographically signed to attest to its authenticity. By evaluating the DNS privacy statement, filtering policy and the signatory, the user can choose a DNS server that best supports the desired privacy and filtering policy.
Comments and suggestions are more than welcome. Cheers, -Tiru ---------- Forwarded message --------- From: <[email protected]<mailto:[email protected]>> Date: Fri, 17 Jan 2020 at 19:18 Subject: New Version Notification for draft-reddy-dprive-dprive-privacy-policy-02.txt To: Dan Wing <[email protected]<mailto:[email protected]>>, Tirumaleswar Reddy.K <[email protected]<mailto:[email protected]>>, Michael C. Richardson <[email protected]<mailto:mcr%[email protected]>> A new version of I-D, draft-reddy-dprive-dprive-privacy-policy-02.txt has been successfully submitted by Tirumaleswar Reddy and posted to the IETF repository. Name: draft-reddy-dprive-dprive-privacy-policy Revision: 02 Title: DNS Server Privacy Statement and Filtering Policy with Assertion Token Document date: 2020-01-17 Group: Individual Submission Pages: 21 URL: https://www.ietf.org/internet-drafts/draft-reddy-dprive-dprive-privacy-policy-02.txt Status: https://datatracker.ietf.org/doc/draft-reddy-dprive-dprive-privacy-policy/ Htmlized: https://tools.ietf.org/html/draft-reddy-dprive-dprive-privacy-policy-02 Htmlized: https://datatracker.ietf.org/doc/html/draft-reddy-dprive-dprive-privacy-policy Diff: https://www.ietf.org/rfcdiff?url2=draft-reddy-dprive-dprive-privacy-policy-02 Abstract: Users want to control how their DNS queries are handled by DNS servers so they can configure their system to use DNS servers that comply with their privacy and DNS filtering expectations. This document defines a mechanism for a DNS server to communicate its privacy statement URL and filtering policy to a DNS client. This communication is cryptographically signed to attest to its authenticity. By evaluating the DNS privacy statement, filtering policy and the signatory, the user can choose a DNS server that best supports their desired privacy and filtering policy. This token is particularly useful for DNS-over-TLS and DNS-over-HTTPS servers that are either public resolvers or are discovered on the local network. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org<http://tools.ietf.org>. The IETF Secretariat
_______________________________________________ dns-privacy mailing list [email protected] https://www.ietf.org/mailman/listinfo/dns-privacy
