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

Eric Rescorla <ekr@rtfm.com> Wed, 05 February 2020 05:53 UTC

Return-Path: <ekr@rtfm.com>
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 9C7C91201DC for <quic@ietfa.amsl.com>; Tue, 4 Feb 2020 21:53:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
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 SUzlDe6l_A1U for <quic@ietfa.amsl.com>; Tue, 4 Feb 2020 21:53:29 -0800 (PST)
Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45EF8120045 for <quic@ietf.org>; Tue, 4 Feb 2020 21:53:29 -0800 (PST)
Received: by mail-lj1-x22d.google.com with SMTP id h23so1008903ljc.8 for <quic@ietf.org>; Tue, 04 Feb 2020 21:53:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zO8atxyKS8XfBFvJ/ONwWAebctwfn3GJ2Ke5IVlNwAc=; b=NmwUsRjhH6Q9l+7jhs2IeFEgJhvgcqBnTJIUYYhlJsMvFIG68jmUG2Ti/Ll8ZuyD+e AFzhSIZjsLVDGuUBuqJOWmXMair6ZZDf+RIfGQ1QGcfjkntPnEh+o5SsEb8AznN25VNO wT20i4MmEehJD3ChOa8ywZwT60UoIR8vAwHuj9H6XNWBpHcXAo2CC3TkR4dVXJsj6uda sCeqbX+jhmGvq9Qpr4OHieW6702ktCHlV0QgJCElBKZs6XFL3sJaFNnEbAeFjyvhYM16 h1f/tTCE3m6lpd6JOycxdfqapM35ihavLl9VW/wJwe85RhUrIddCwG0WYoH6KrvChQ7i 4YHQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zO8atxyKS8XfBFvJ/ONwWAebctwfn3GJ2Ke5IVlNwAc=; b=H+eV/h+EaXSkGL+oNDJyjezcWsak/OzrmCpxgIRGmaBYbB0yQy3Sg9z66iE7xKj10y n6n4Ru2t/xNObm9OpEne/TYX7lBqj2BnUBl36+ZpvuWhX+OGR7t+ltTfp+QoRC7+8Mxn U2qZwLoHyop69+8wh2TBGO/c1XyE5NI9O154VRp2bWMq/96/dkWK+mc/ZdiTMCUeREd/ N6kt0Wn+MpI102VZKFD+acW7jgeRFxyigi+9nknYCxdJ2M2UwFEooeNIRGhCsajn6pjq cBuP0vOGIPaTl5UfpqBKUOjk600CI8Nm13PhPdoiNONRKpL7b8jYGKVw17JiG1FiBnG0 wXBQ==
X-Gm-Message-State: APjAAAUY6xiRAI35GcULUp5raZIRQaRhePvQYNfwND3NokLktjtqAPfa B4e+BC1hvW9hVlqxIK6kkwJdkFonrsHG7VdFFluI1w==
X-Google-Smtp-Source: APXvYqy3N4x8JEt2NRlunFlQ1av+VFIE9ccRCIR9dbD8ggxr4JqrUMobOY00luoa5P70zkbOj3/bGnO1kV+zS18BRM8=
X-Received: by 2002:a05:651c:448:: with SMTP id g8mr19710982ljg.35.1580882007486; Tue, 04 Feb 2020 21:53:27 -0800 (PST)
MIME-Version: 1.0
References: <A56547B6-2E3B-4ABE-8C9B-BA9ACC489FB2@mnot.net> <CAKC-DJiuhJurq4ojJwPD0Ag3Eoz_4KwFssuuP5Ts1+EH6C9C2A@mail.gmail.com>
In-Reply-To: <CAKC-DJiuhJurq4ojJwPD0Ag3Eoz_4KwFssuuP5Ts1+EH6C9C2A@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 04 Feb 2020 21:52:51 -0800
Message-ID: <CABcZeBMJEDe9gXkfkw4fN+0rFm_8FaS-87uKmdA5nsJQE79Oig@mail.gmail.com>
Subject: Re: QUIC re-chartering: include DNS-over-QUIC?
To: Erik Nygren <erik+ietf@nygren.org>
Cc: Mark Nottingham <mnot@mnot.net>, Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007d03d0059dcdc656"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Vy_lwJE5UANbHbZoMyZCrc5AV58>
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: Wed, 05 Feb 2020 05:53:33 -0000

On Tue, Feb 4, 2020 at 1:05 PM Erik Nygren <erik+ietf@nygren.org> wrote:

> On Wed, Dec 11, 2019 at 4:38 PM Mark Nottingham <mnot@mnot.net> wrote:
>
>> We've just put out Calls for Adoption for extensions to QUICv1, as we
>> believe that the group has some capacity to discuss them as it finishes
>> work on the core protocol.
>>
>
> Is there interest and bandwidth in picking up work on DNS-over-QUIC (eg,
> draft-huitema-quic-dnsoquic-07
> <https://tools.ietf.org/html/draft-huitema-quic-dnsoquic-07>) as well,
> presumably in coordination with the DNS community?
>

I think it would be OK to define DoQ (though I share Tommy's question about
DoH/3, which needs no additional standardization) but I don't think that
should be done in the QUIC WG, any more than we define HTTP in TCPM. We
needed one driving study but now that the QUIC mapping is done, other
mappings should probably be done elsewhere.

>
> Getting a second protocol using QUIC might help make sure we work through
> issues that may arise early, plus DNS-over-QUIC seems quite attractive as a
> technology for resolver-to-authoritative communication if/when we go that
> way.  ie, it seems strictly better than defining a DNS-over-DTLS
>

You might be interested in https://tools.ietf.org/html/rfc8094

-Ekr



> and also seems to have plenty of advantages over DoT.
>
> The current charter also says:
>
> This [HTTP] mapping will accommodate the extension mechanisms defined in
>> the HTTP/2
>> specification. Upon completion of that mapping, additional protocols
>> may be added by updating this charter to include them.
>>
>
> Best,
>      Erik
>
>