Re: [dns-privacy] Fwd: Fwd: New Version Notification for draft-huitema-quic-dnsoquic-00.txt

Alexander Mayrhofer <alexander.mayrhofer@nic.at> Tue, 11 April 2017 06:43 UTC

Return-Path: <alexander.mayrhofer@nic.at>
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 BFE341287A3; Mon, 10 Apr 2017 23:43:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.889
X-Spam-Level:
X-Spam-Status: No, score=-6.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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 Umrf5BCdN7ij; Mon, 10 Apr 2017 23:43:29 -0700 (PDT)
Received: from mail.sbg.nic.at (mail.sbg.nic.at [83.136.33.227]) (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 EBCE0128B8D; Mon, 10 Apr 2017 23:43:27 -0700 (PDT)
Received: from nics-exch2.sbg.nic.at ([10.17.175.6]) by mail.sbg.nic.at with XWall v3.52f ; Tue, 11 Apr 2017 08:43:21 +0200
Received: from NICS-EXCH2.sbg.nic.at ([fe80::a5b2:6e42:e54d:9d57]) by NICS-EXCH2.sbg.nic.at ([fe80::a5b2:6e42:e54d:9d57%12]) with mapi id 14.03.0319.002; Tue, 11 Apr 2017 08:43:20 +0200
From: Alexander Mayrhofer <alexander.mayrhofer@nic.at>
To: Christian Huitema <huitema@huitema.net>, "quic@ietf.org" <quic@ietf.org>, "dns-privacy@ietf.org" <dns-privacy@ietf.org>
Thread-Index: AQHSsh8cNI/htzqFBkW5pWYvd2Daa6G/thFg
Date: Tue, 11 Apr 2017 06:43:19 +0000
Message-ID: <19F54F2956911544A32543B8A9BDE07598F48DC7@NICS-EXCH2.sbg.nic.at>
References: <0b31dc15-3e13-ac36-5c09-056ea8f1b2e8@huitema.net> <cbdb51e1-7f5a-9ddf-a30e-6ca9c2b9c67d@huitema.net>
In-Reply-To: <cbdb51e1-7f5a-9ddf-a30e-6ca9c2b9c67d@huitema.net>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.3.13]
Content-Type: multipart/alternative; boundary="_000_19F54F2956911544A32543B8A9BDE07598F48DC7NICSEXCH2sbgnic_"
MIME-Version: 1.0
X-XWALL-BCKS: auto
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/sryy2d-rxRSfcPtE1d7EfHzm1N0>
Subject: Re: [dns-privacy] Fwd: Fwd: New Version Notification for draft-huitema-quic-dnsoquic-00.txt
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.22
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, 11 Apr 2017 06:43:33 -0000

Hello Christian,

great to see this – i remember when i mentioned QUIC as an option during the DNS-over-HTTP Bar BoF in Seoul i got quite a few weird looks :). I like this. It looks like a logical choice somewhere „between“ TLS and DTLS.

I have some background on Section 6.5 (Padding) – back when we specified DNS over TLS, we had a similar discussion whether to pad on the DNS or the transport (TLS, in that case) layer. We decided in that case that padding on the DNS layer is preferred, since it allows for greater control by the application. This was actually the reason RFC 7830 was created in the first place.

The situation might be different for QUIC as there’s a tighter coupling between transport and application, though padding on the DNS layer would allow re-using the ongoing research and specification work in DPRIVE. (Disclaimer: I know little about the current state of such research for QUIC).

best,
Alex

Von: dns-privacy [mailto:dns-privacy-bounces@ietf.org] Im Auftrag von Christian Huitema
Gesendet: Montag, 10. April 2017 19:23
An: quic@ietf.org; dns-privacy@ietf.org
Betreff: [dns-privacy] Fwd: Fwd: New Version Notification for draft-huitema-quic-dnsoquic-00.txt [x_phishing]


FYI: Just published this draft describing transport of DNS over a dedicated QUIC connection.
-- Christian Huitema

-------- Forwarded Message --------
Subject:

New Version Notification for draft-huitema-quic-dnsoquic-00.txt

Date:

Mon, 10 Apr 2017 09:45:37 -0700

From:

internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>

To:

Melinda Shore <mshore@fastly.com><mailto:mshore@fastly.com>, Sara Dickinson <sara@sinodun.com><mailto:sara@sinodun.com>, Christian Huitema <huitema@huitema.net><mailto:huitema@huitema.net>, Allison Mankin <amankin@salesforce.com><mailto:amankin@salesforce.com>, Janardhan Iyengar <jri@google.com><mailto:jri@google.com>, Jana Iyengar <jri@google.com><mailto:jri@google.com>



A new version of I-D, draft-huitema-quic-dnsoquic-00.txt

has been successfully submitted by Christian Huitema and posted to the

IETF repository.



Name:         draft-huitema-quic-dnsoquic

Revision:     00

Title:        Specification of DNS over QUIC

Document date: 2017-04-10

Group:        Individual Submission

Pages:        18

URL:            https://www.ietf.org/internet-drafts/draft-huitema-quic-dnsoquic-00.txt

Status:         https://datatracker.ietf.org/doc/draft-huitema-quic-dnsoquic/

Htmlized:       https://tools.ietf.org/html/draft-huitema-quic-dnsoquic-00

Htmlized:       https://datatracker.ietf.org/doc/html/draft-huitema-quic-dnsoquic-00





Abstract:

   This document describes the use of QUIC to provide transport privacy

   for DNS.  The encryption provided by QUIC has similar properties to

   that provided by TLS, while QUIC transport eliminates the head-of-

   line blocking issues inherent with TCP and provides more efficient

   error corrections than UDP.  DNS over QUIC has privacy properties

   similar to DNS over TLS specified in RFC7858, and performance similar

   to classic DNS over UDP.









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