Hello DNSOP, On Wed, 2021-05-19 at 16:58 +0000, Paul Hoffman wrote: > Greetings again. Peter and I have revised > draft-ietf-dprive-unauth-to-authoritative and draft-pp-dprive-common-features > based on recent mailing list traffic. One major change is that we realized > that we could move even more sections from unauth-to-authoritative to > common-features because they would apply to the fully-authenticated use case. > Please review them to see if you agree. > > If people like the idea of us splitting out common features, it would be good > if it too became a WG document, particularly to help focus the discussions on > the unauthenticated and fully-authenticated use cases. > > --Paul Hoffman and Peter van Dijk > > https://www.ietf.org/archive/id/draft-pp-dprive-common-features-01.txt > https://www.ietf.org/archive/id/draft-ietf-dprive-unauth-to-authoritative-01.txt
A friendly ping - we moved a bunch of text from our adopted draft to the 'common' draft, so that 'discovery' and 'security properties' can be discussed separately. We think this even makes sense if the adox draft does not get adopted today, because it (or some other draft with stronger security properties than our unauth draft) might get adopted in the future. So, chairs, can you please think about adopting draft-pp-dprive-common-features even before the adox draft is adopted? Kind regards, -- Peter van Dijk PowerDNS.COM BV - https://www.powerdns.com/ _______________________________________________ dns-privacy mailing list [email protected] https://www.ietf.org/mailman/listinfo/dns-privacy
