IETF Logo Mail Archive

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

Martin Duke <martin.h.duke@gmail.com> Mon, 10 February 2020 18:58 UTC

Return-Path: <martin.h.duke@gmail.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 4CE4E120019 for <quic@ietfa.amsl.com>; Mon, 10 Feb 2020 10:58:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 JDz4RmhKOVwD for <quic@ietfa.amsl.com>; Mon, 10 Feb 2020 10:58:11 -0800 (PST)
Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) (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 3C48B12081A for <quic@ietf.org>; Mon, 10 Feb 2020 10:58:11 -0800 (PST)
Received: by mail-wr1-x42a.google.com with SMTP id r11so5908913wrq.10 for <quic@ietf.org>; Mon, 10 Feb 2020 10:58:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=XeN7kAMiBm54cs4T3Qtr2HUvDKmkEU7anA35aS6Y5c0=; b=BKxhBDCQDWYJyD5OTyX/WRyR0cWJ0awn8ot9Tkmn4nyvTnuid65NMsZXQWiSvzvAu0 Vvk3iEXljEFenltomFxPuU+HpREQor8LVnqDQJkEOHIFAb45yAHypQx1OUQFQPLPy13H tuIiKPQs801Z4uPOzhV2CI1VsqQAFzkGgvvy5FcVUYhmtizsdtKdpgxbkbXleXWs85aT inpK4gBNMyWNTZm58rq3r7Wa7/pdNPeR1dYhViXKGAmnrM2PTiBm5NJMlwpR+sDyjCLW gycCZD4clCrA/xvy6Z15+eUCua3+n2yXRx2UUAFGpmveG2tw5vJyeiWQcVUxRUyZN11x aEXA==
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=XeN7kAMiBm54cs4T3Qtr2HUvDKmkEU7anA35aS6Y5c0=; b=e2/Ap696TA4M1HUBfzW2AZEVw6VDkHo2Fj2GEyu2fL98i3czipOZQp8X79np9H4rMY Eig8XYmgLeJmMN8o6DW63DK3YhnfLLxuJm1M6hNW8ujvDuQyKOB1cESubwJf8iQrDn2j mle/S+PSIs+oBe1axqSTDIacH40NNh9d1yzHhkaN7KyEr1MGzj7iDl7VnIcP6ajNXRuf mM6kIsodpNzqjIEu//HZ+7+EoYgHOq/Cm8G67AdhXy3jJPUF9ppja/q94KXkhySdiIy3 4uNqcUwF1yrpfyjHGT2YHQIcZpystnWRYVzM4Zj6nhT+vLP/HlHi8GbC4eZkWphiNnLi q48w==
X-Gm-Message-State: APjAAAU/OSME7vvMcuWIbc8adJwGc1W/t//uFzo4zvG55usednu7m4DB itMbgsCf6/Au95B96eyiSm8O7MACSXz4lwvxetM=
X-Google-Smtp-Source: APXvYqy3HkLpZdbCy7hRRzCUctnMddaHnttwUL7hfjfutuaDBMYj7aBzkJOaMce0m/DVnPZwC925aPnB6YvbUzTxAQU=
X-Received: by 2002:adf:fe83:: with SMTP id l3mr3551201wrr.41.1581361089756; Mon, 10 Feb 2020 10:58:09 -0800 (PST)
MIME-Version: 1.0
References: <CAKcm_gNf43tXizw9D2jdtTieh+=zS7PKVDiNNV-UEbP8Gw+mHg@mail.gmail.com> <69F63EAA-B7AB-4874-9AD5-7C8F98A92C77@apple.com> <de87e833-de54-ae5a-cd85-2f93565192f7@redbarn.org> <CAMGpriUY_DhRY28Boa2JA3=4XZm1Z23epy8SPfu5OyO1aupu2g@mail.gmail.com>
In-Reply-To: <CAMGpriUY_DhRY28Boa2JA3=4XZm1Z23epy8SPfu5OyO1aupu2g@mail.gmail.com>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Mon, 10 Feb 2020 19:57:58 +0100
Message-ID: <CAM4esxRQ2V=XoGFjHOhH-n4BLx=3oXTq5kmxgSe6sWfd+9Qpww@mail.gmail.com>
Subject: Re: QUIC re-chartering: include DNS-over-QUIC?
To: Erik Kline <ek.ietf@gmail.com>
Cc: Paul Vixie <paul@redbarn.org>, Vidhi Goel <vidhi_goel=40apple.com@dmarc.ietf.org>, IETF QUIC WG <quic@ietf.org>, Christopher Wood <caw@heapingbits.net>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000443b5059e3d5224"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/xpQwF6BzZqcHaVF5-eqH5RkKX74>
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: Mon, 10 Feb 2020 18:58:13 -0000

As others have said, this is great work that should be done elsewhere. If
we've done a good job, the QUIC transport should be able to handle this use
case without a bunch of transport-re-engineering.

However, if it turns out you need a protocol tweak, please come back to us.

On Thu, Feb 6, 2020 at 11:12 PM Erik Kline <ek.ietf@gmail.com> wrote:

>
>
> On Thu, Feb 6, 2020 at 1:17 PM Paul Vixie <paul@redbarn.org> wrote:
>
>>
>>
>> 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.
>>
>
> I think the add charter might be aiming to address the advice to clients
> concern (https://datatracker.ietf.org/doc/charter-ietf-add/).
>

v2.23.0 | Report a Bug | By Email