RFC 7858 on Specification for DNS over Transport Layer Security (TLS)

rfc-editor@rfc-editor.org Tue, 17 May 2016 22:25 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 []) by ietfa.amsl.com (Postfix) with ESMTP id B217512DDEC; Tue, 17 May 2016 15:25:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.328
X-Spam-Status: No, score=-108.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id oOCDzMMtJSsf; Tue, 17 May 2016 15:25:10 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7964212DDEF; Tue, 17 May 2016 15:24:56 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 95121180094; Tue, 17 May 2016 15:24:45 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7858 on Specification for DNS over Transport Layer Security (TLS)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160517222445.95121180094@rfc-editor.org>
Date: Tue, 17 May 2016 15:24:45 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/i0DFmgMnkxwBpBRO5IA-fxkFp70>
Cc: drafts-update-ref@iana.org, dns-privacy@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 17 May 2016 22:25:14 -0000

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

        RFC 7858

        Title:      Specification for DNS over Transport 
                    Layer Security (TLS) 
        Author:     Z. Hu, L. Zhu,
                    J. Heidemann, A. Mankin,
                    D. Wessels, P. Hoffman
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2016
        Mailbox:    zihu@outlook.com, 
        Pages:      19
        Characters: 42138
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dprive-dns-over-tls-09.txt

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

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

This document describes the use of Transport Layer Security (TLS) to
provide privacy for DNS.  Encryption provided by TLS eliminates
opportunities for eavesdropping and on-path tampering with DNS
queries in the network, such as discussed in RFC 7626.  In addition,
this document specifies two usage profiles for DNS over TLS and
provides advice on performance considerations to minimize overhead
from using TCP and TLS with DNS.

This document focuses on securing stub-to-recursive traffic, as per
the charter of the DPRIVE Working Group.  It does not prevent future
applications of the protocol to recursive-to-authoritative traffic.

This document is a product of the DNS PRIVate Exchange Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  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