[dns-privacy] RFC 8094 on DNS over Datagram Transport Layer Security (DTLS)
rfc-editor@rfc-editor.org Wed, 01 March 2017 01:17 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2E7112984B; Tue, 28 Feb 2017 17:17:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 5pJFvpzh8REn; Tue, 28 Feb 2017 17:17:44 -0800 (PST)
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 07794129851; Tue, 28 Feb 2017 17:17:28 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id E7E34B820E6; Tue, 28 Feb 2017 17:17:27 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170301011727.E7E34B820E6@rfc-editor.org>
Date: Tue, 28 Feb 2017 17:17:27 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/S3RircPrAgGRHMdYidgPQqAfXEg>
Cc: drafts-update-ref@iana.org, dns-privacy@ietf.org, rfc-editor@rfc-editor.org
Subject: [dns-privacy] RFC 8094 on DNS over Datagram Transport Layer Security (DTLS)
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Mar 2017 01:17:51 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8094
Title: DNS over Datagram Transport Layer
Security (DTLS)
Author: T. Reddy, D. Wing,
P. Patil
Status: Experimental
Stream: IETF
Date: February 2017
Mailbox: tireddy@cisco.com,
dwing-ietf@fuggles.com,
praspati@cisco.com
Pages: 13
Characters: 31130
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-dprive-dnsodtls-15.txt
URL: https://www.rfc-editor.org/info/rfc8094
DOI: 10.17487/RFC8094
DNS queries and responses are visible to network elements on the path
between the DNS client and its server. These queries and responses
can contain privacy-sensitive information, which is valuable to
protect.
This document proposes the use of Datagram Transport Layer Security
(DTLS) for DNS, to protect against passive listeners and certain
active attacks. As latency is critical for DNS, this proposal also
discusses mechanisms to reduce DTLS round trips and reduce the DTLS
handshake size. The proposed mechanism runs over port 853.
This document is a product of the DNS PRIVate Exchange 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
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