IETF Logo Mail Archive

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

Erik Kline <ek.ietf@gmail.com> Thu, 06 February 2020 22:12 UTC

Return-Path: <ek.ietf@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 9C187120819 for <quic@ietfa.amsl.com>; Thu, 6 Feb 2020 14:12:23 -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=unavailable 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 nNquS9d63oFW for <quic@ietfa.amsl.com>; Thu, 6 Feb 2020 14:12:21 -0800 (PST)
Received: from mail-oi1-x229.google.com (mail-oi1-x229.google.com [IPv6:2607:f8b0:4864:20::229]) (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 D9DBB120111 for <quic@ietf.org>; Thu, 6 Feb 2020 14:12:20 -0800 (PST)
Received: by mail-oi1-x229.google.com with SMTP id a142so10191oii.7 for <quic@ietf.org>; Thu, 06 Feb 2020 14:12:20 -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=xFwtAtNDbz4k9yzGl5o4YLnNW9OqLy+qXAU3eyxQSjg=; b=irIr53j+BAmbYvy/ZMNVXj92s/248+ig/c+Rwp7ZIU6IVXPsiM+fxS5CKXx+KUu6gM 7huiBSHdKJIhtsNbpozBj+A0kz19lJ4KdcnPGmmNWf8C3+aNci3402omK7fWGFPdOo2D OEszf6K19N7jp6X2CXL2s576xEoB+wB8Dz2BuV7xJkLPcc/zsmjBggVPYEkPSjb6vHF1 34+keuSy0Kgw0ietsrkBCcVMW9LwrE3Jlj4rMVcb8883cSQL3he9pRzqvUhSnCsFZ5qj T2EfctWojJ4G8Ym/8BI4zSv9eHDetguRk2Zd8MGrFPUT/1vz1EFzZkLO3M0y3nhKo3ME RQ4g==
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=xFwtAtNDbz4k9yzGl5o4YLnNW9OqLy+qXAU3eyxQSjg=; b=HuANhd0+BALGXk9+vTwooHHc+Joy0c0jR8TieFensBvujF8yov7PmrOaSqv/AO52EW RRwuPqKvj4ULGA2EDsLKIsQ9U7kEUnC2gtH/bEIb7am6X0z/shZQxMZrV65R1YKVrHIN WBusdBRhuVYhFVmjB36v5vWGJNGpAGyCoLwoz0qvO52pnz6+h/FFxd0rLtgCvmRCA+cH w0BlLShTxMI++Zr/lxgmEXVSW6hvtUmbMbrLzz2AdP1bKJIGlaajTlUzwJD93sM3RCeO 5+sETjCve0XQrfbTMqcv9N9NJ1dykMaauNIK1ckHQ4zKOc0jBcypjWh+04v/DeLYxSCO 0dQw==
X-Gm-Message-State: APjAAAXKxUUxtbEdLx5z+Kcz2tUZiVoxoWkosUgV654dw/OO82gtltA1 QBKOYKMdtpw2KNqa4xCQ0oOWFFKkaeg2GWdHui8=
X-Google-Smtp-Source: APXvYqwgcqUnRt9JfZ3pd2SmhVaJfv98BrUfLUd8K2amDMGm43gSZ6NJJzPc21Y6c7wGRcQhoHoxYzP1K+99ZKog5P4=
X-Received: by 2002:aca:b187:: with SMTP id a129mr95260oif.175.1581027140167; Thu, 06 Feb 2020 14:12:20 -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>
In-Reply-To: <de87e833-de54-ae5a-cd85-2f93565192f7@redbarn.org>
From: Erik Kline <ek.ietf@gmail.com>
Date: Thu, 06 Feb 2020 14:12:09 -0800
Message-ID: <CAMGpriUY_DhRY28Boa2JA3=4XZm1Z23epy8SPfu5OyO1aupu2g@mail.gmail.com>
Subject: Re: QUIC re-chartering: include DNS-over-QUIC?
To: Paul Vixie <paul@redbarn.org>
Cc: 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="00000000000011ebcf059def911a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/PjHF4xaPH7AhOQK1sVLNim_ZVjw>
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 22:12:24 -0000

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