Re: QUIC re-chartering: include DNS-over-QUIC?

Paul Vixie <paul@redbarn.org> Thu, 06 February 2020 21:16 UTC

Return-Path: <paul@redbarn.org>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96268120147 for <quic@ietfa.amsl.com>; Thu, 6 Feb 2020 13:16:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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 InlQ_IIR6Ezi for <quic@ietfa.amsl.com>; Thu, 6 Feb 2020 13:16:48 -0800 (PST)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 552441200E5 for <quic@ietf.org>; Thu, 6 Feb 2020 13:16:48 -0800 (PST)
Received: from [10.0.10.241] (unknown [80.146.187.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 00610B0591; Thu, 6 Feb 2020 21:16:45 +0000 (UTC)
Subject: Re: QUIC re-chartering: include DNS-over-QUIC?
To: Vidhi Goel <vidhi_goel=40apple.com@dmarc.ietf.org>
Cc: Ian Swett <ianswett=40google.com@dmarc.ietf.org>, IETF QUIC WG <quic@ietf.org>, Christopher Wood <caw@heapingbits.net>
References: <CAKcm_gNf43tXizw9D2jdtTieh+=zS7PKVDiNNV-UEbP8Gw+mHg@mail.gmail.com> <69F63EAA-B7AB-4874-9AD5-7C8F98A92C77@apple.com>
From: Paul Vixie <paul@redbarn.org>
Message-ID: <de87e833-de54-ae5a-cd85-2f93565192f7@redbarn.org>
Date: Thu, 06 Feb 2020 22:16:42 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 PostboxApp/7.0.11
MIME-Version: 1.0
In-Reply-To: <69F63EAA-B7AB-4874-9AD5-7C8F98A92C77@apple.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/iuZrLKfIy9N3_-EwjttNb2N4Whs>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Feb 2020 21:16:49 -0000


Vidhi Goel wrote on 2020-02-06 18:26:
> I support DoQ for the use cases that are based on non HTTP application 
> protocol. DoQ implicitly provides benefits of QUIC which DoT doesn’t have.

i fear this may be off-topic for this mailing list; in which case, just 
tell me. i've been watching this thread carefully, and i think the 
concern about too many dns transports with no possible guidance to 
developers as to which one to try in what order. as a server operator i 
expect to have to support everything, which means arguments about threat 
surface in one transport vs. another are effectively null.

i can definitely see why the QUIC team might want more than one proof, 
it would help assure us all that there aren't HTTP assumptions designed 
in. and all of the reasons i never pushed for DNS over DTLS or DNS over 
SCTP are certainly addressed by DNS over QUIC.

however, my reasons for not pushing DNS over DTLS or DNS over SCTP are 
also addressed by DoT. i'd be grateful if you could explain what 
problems you think DoT has, which would beg us to invent another DNS 
transport profile such as DNS over QUIC.

i see DoQ as nec'y for QUIC's success but not relevant to DNS beyond the 
fact that DNS is a convenient second example of how QUIC can be used. if 
there are use cases or failure modes not handled well by DoT, i'd like 
to learn more about those.

-- 
P Vixie