[dns-privacy] [Fwd: New Version Notification for draft-vandijk-dprive-ds-dot-signal-and-pin-00.txt]

Peter van Dijk <peter.van.dijk@powerdns.com> Tue, 19 May 2020 09:24 UTC

Return-Path: <peter.van.dijk@powerdns.com>
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 6CF853A1311 for <dns-privacy@ietfa.amsl.com>; Tue, 19 May 2020 02:24:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.004
X-Spam-Level:
X-Spam-Status: No, score=0.004 tagged_above=-999 required=5 tests=[AC_FROM_MANY_DOTS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 jIMris1c2X0M for <dns-privacy@ietfa.amsl.com>; Tue, 19 May 2020 02:24:33 -0700 (PDT)
Received: from mx3.open-xchange.com (alcatraz.open-xchange.com [87.191.39.187]) (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 491E23A1313 for <dns-privacy@ietf.org>; Tue, 19 May 2020 02:24:33 -0700 (PDT)
Received: from open-xchange.com (imap.open-xchange.com [10.20.30.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx3.open-xchange.com (Postfix) with ESMTPS id D95456A303; Tue, 19 May 2020 11:24:30 +0200 (CEST)
Received: from plato (ip545136af.direct-adsl.nl [84.81.54.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by open-xchange.com (Postfix) with ESMTPSA id BB83D3C0310; Tue, 19 May 2020 11:24:30 +0200 (CEST)
Message-ID: <a15e2d1df86820f2483516662d3712d8a60161cd.camel@powerdns.com>
From: Peter van Dijk <peter.van.dijk@powerdns.com>
To: dns-privacy@ietf.org
Date: Tue, 19 May 2020 11:24:30 +0200
References: <158987990316.29446.4343920282978207647@ietfa.amsl.com>
Organization: PowerDNS.COM B.V.
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.30.5-1.1
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/0dfhu3lyK9g8Ujaybp1ZjvNLVb0>
Subject: [dns-privacy] [Fwd: New Version Notification for draft-vandijk-dprive-ds-dot-signal-and-pin-00.txt]
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 19 May 2020 09:24:37 -0000

Hello DNS privacy people,

please find below all details about our proposal for enabling DoT from
resolver to authoritative.

This work is based on Manu Bretelle's presentation in Prague over a
year ago, after which we spent a lot of time figuring out how to
squeeze the DoT signal and key pin into the constraints of DNSKEY/DS
records.

We have some running code (linked in the draft) to show feasibility of
the approach.

The draft is managed on GitHub in .md format at 
https://github.com/PowerDNS/parent-signals-dot/tree/master/draft-vandijk-dprive-ds-dot-signal-and-pin

Looking forward to your comments,
Peter, Manu & Robin

-------- Forwarded Message --------
From: internet-drafts@ietf.org
To: Peter van Dijk <peter.van.dijk@powerdns.com>, Emmanuel Bretelle <
chantra@fb.com>, Robin Geuze <robing@transip.nl>
Subject: [EXT] New Version Notification for draft-vandijk-dprive-ds-
dot-signal-and-pin-00.txt
Date: Tue, 19 May 2020 02:18:23 -0700

A new version of I-D, draft-vandijk-dprive-ds-dot-signal-and-pin-00.txt
has been successfully submitted by Peter van Dijk and posted to the
IETF repository.

Name:		draft-vandijk-dprive-ds-dot-signal-and-pin
Revision:	00
Title:		Signalling Authoritative DoT support in DS records, with key pinning
Document date:	2020-05-19
Group:		Individual Submission
Pages:		10
URL:            https://www.ietf.org/internet-drafts/draft-vandijk-dprive-ds-dot-signal-and-pin-00.txt
Status:         https://datatracker.ietf.org/doc/draft-vandijk-dprive-ds-dot-signal-and-pin/
Htmlized:       https://tools.ietf.org/html/draft-vandijk-dprive-ds-dot-signal-and-pin-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-vandijk-dprive-ds-dot-signal-and-pin


Abstract:
   This document specifies a way to signal the usage of DoT, and the
   pinned keys for that DoT usage, in authoritative servers.  This
   signal lives on the parent side of delegations, in DS records.  To
   ensure easy deployment, the signal is defined in terms of (C)DNSKEY.

                                                                                  


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat