Greetings again. It is good to see much more discussion here about how we might to recursive-to-authoritative encryption. Based on this, I have updated <https://datatracker.ietf.org/doc/draft-pp-recursive-authoritative-opportunistic/>.
- There may be interest in using authenticated results in order for caches to promote parent-side NS records to a higher standing than they currently have in the caches, or something like that. If so, that should be part of the opportunistic draft because opportunistic means "try to authenticate if there is any value at all". - It now seems more likely that someone will write a "always authenticate" draft; if so, the discussion of the transport cache would be useful to both, so it could be split out as a separate document. See y'all later for the WG meeting! --Paul Hoffman
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ dns-privacy mailing list [email protected] https://www.ietf.org/mailman/listinfo/dns-privacy
