BCP 232, RFC 8932 on Recommendations for DNS Privacy Service Operators
rfc-editor@rfc-editor.org Fri, 23 October 2020 21:45 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D2D23A08BB; Fri, 23 Oct 2020 14:45:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RluTmwQcSkh7; Fri, 23 Oct 2020 14:45:54 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10E203A0112; Fri, 23 Oct 2020 14:45:54 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id BFFCFF4071A; Fri, 23 Oct 2020 14:45:46 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 232, RFC 8932 on Recommendations for DNS Privacy Service Operators
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, dns-privacy@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20201023214546.BFFCFF4071A@rfc-editor.org>
Date: Fri, 23 Oct 2020 14:45:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/xt1ozceqtbjqR4hJXtIY4Obc13M>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Oct 2020 21:45:56 -0000
A new Request for Comments is now available in online RFC libraries.
BCP 232
RFC 8932
Title: Recommendations for DNS Privacy Service
Operators
Author: S. Dickinson,
B. Overeinder,
R. van Rijswijk-Deij,
A. Mankin
Status: Best Current Practice
Stream: IETF
Date: October 2020
Mailbox: sara@sinodun.com,
benno@NLnetLabs.nl,
roland@nlnetlabs.nl,
allison.mankin@gmail.com
Pages: 34
See Also: BCP 232
I-D Tag: draft-ietf-dprive-bcp-op-14.txt
URL: https://www.rfc-editor.org/info/rfc8932
DOI: 10.17487/RFC8932
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.
This document is a product of the DNS PRIVate Exchange Working Group of the IETF.
BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC