Recommendations for DNS Privacy Service Operators
RFC 8932
also known as BCP 232
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2023-12-12
|
(System) | Imported membership of rfc8932 in bcp232 via sync to the rfc-index |
|
2023-12-12
|
(System) | No history of BCP232 is currently available in the datatracker before this point |
|
2021-07-06
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
|
2020-10-23
|
(System) | Received changes through RFC Editor sync (created alias RFC 8932, changed abstract to 'This document presents operational, policy, and security considerations for DNS recursive … Received changes through RFC Editor sync (created alias RFC 8932, changed abstract to 'This document presents operational, policy, and security considerations for DNS recursive resolver operators who choose to offer DNS privacy services. With these recommendations, the operator can make deliberate decisions regarding which services to provide, as well as understanding how those decisions and the alternatives impact the privacy of users. This document also presents a non-normative framework to assist writers of a Recursive operator Privacy Statement, analogous to DNS Security Extensions (DNSSEC) Policies and DNSSEC Practice Statements described in RFC 6841.', changed pages to 34, changed standardization level to Best Current Practice, changed state to RFC, added RFC published event at 2020-10-23, changed IESG state to RFC Published, created alias BCP 232) |
|
2020-10-23
|
(System) | RFC published |