[perpass] [rfc-editor@rfc-editor.org: RFC 7816 on DNS Query Name Minimisation to Improve Privacy]

Stephane Bortzmeyer <bortzmeyer@nic.fr> Wed, 23 March 2016 09:18 UTC

Return-Path: <bortzmeyer@nic.fr>
X-Original-To: perpass@ietfa.amsl.com
Delivered-To: perpass@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 8D27312DB87 for <perpass@ietfa.amsl.com>; Wed, 23 Mar 2016 02:18:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id zU9JkCXiJGUv for <perpass@ietfa.amsl.com>; Wed, 23 Mar 2016 02:18:11 -0700 (PDT)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 15A1112DB85 for <perpass@ietf.org>; Wed, 23 Mar 2016 02:18:11 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 430CC3283E; Wed, 23 Mar 2016 10:18:07 +0100 (CET)
Received: by mail.sources.org (Postfix, from userid 1000) id E794B1908D6; Wed, 23 Mar 2016 10:13:34 +0100 (CET)
Date: Wed, 23 Mar 2016 10:13:34 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: perpass@ietf.org
Message-ID: <20160323091334.GA30695@sources.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="PNTmBPCT7hxwcZjr"
Content-Disposition: inline
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux 8.3
X-Charlie: Je suis Charlie
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/perpass/fj3Q0ILhDts_ohI2XyhcKG6KJ14>
Subject: [perpass] [rfc-editor@rfc-editor.org: RFC 7816 on DNS Query Name Minimisation to Improve Privacy]
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "The perpass list is for IETF discussion of pervasive monitoring. " <perpass.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perpass>, <mailto:perpass-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/perpass/>
List-Post: <mailto:perpass@ietf.org>
List-Help: <mailto:perpass-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perpass>, <mailto:perpass-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Mar 2016 09:18:13 -0000

Another RFC which started from perpass.

Only two years for completion :-)

--- Begin Message ---
A new Request for Comments is now available in online RFC libraries.

        RFC 7816

        Title:      DNS Query Name Minimisation to 
                    Improve Privacy 
        Author:     S. Bortzmeyer
        Status:     Experimental
        Stream:     IETF
        Date:       March 2016
        Mailbox:    bortzmeyer+ietf@nic.fr
        Pages:      11
        Characters: 23941
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dnsop-qname-minimisation-09.txt

        URL:        https://www.rfc-editor.org/info/rfc7816

        DOI:        http://dx.doi.org/10.17487/RFC7816

This document describes a technique to improve DNS privacy, a
technique called "QNAME minimisation", where the DNS resolver no
longer sends the full original QNAME to the upstream name server.

This document is a product of the Domain Name System Operations Working Group of the IETF.

EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

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
--- End Message ---