IETF Logo Mail Archive

Re: [dns-privacy] DNS and QUIC,HTTP/3 Long term vision...

James <james.ietf@gmail.com> Tue, 06 October 2020 21:03 UTC

Return-Path: <james.ietf@gmail.com>
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 35BF63A14E2 for <dns-privacy@ietfa.amsl.com>; Tue, 6 Oct 2020 14:03:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 x4EYzd5PKU_u for <dns-privacy@ietfa.amsl.com>; Tue, 6 Oct 2020 14:03:36 -0700 (PDT)
Received: from mail-il1-x131.google.com (mail-il1-x131.google.com [IPv6:2607:f8b0:4864:20::131]) (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 0C0353A14DD for <dns-privacy@ietf.org>; Tue, 6 Oct 2020 14:03:36 -0700 (PDT)
Received: by mail-il1-x131.google.com with SMTP id c5so151879ilk.11 for <dns-privacy@ietf.org>; Tue, 06 Oct 2020 14:03:36 -0700 (PDT)
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=R6V0GCSuNGHoRx64/JcOk2TlNqvnfBGPFRN2U2Prano=; b=FAEEYNojJkMNhpW5+QjNyU9Oopz9C1+eJpyQ5vpXgrWB4h75SBVe7XpNWIWc/xYcw2 dEiQMM1NKqua/rQVXG85/NiEXM4xQwl/Zxt4/dYrUEqcL88HJbHwphR2VSrM15BP4NJ+ VEpLck+V81jRjLW7qJOrMeR2zOyFXWqQGKf+KE7yCAbeuC1mVuyhjHhjAY9l/p23IKsX LsYx08wvzec578aVecSGeXiKL9HJV0smJsexMfZKcF5ZAhE7PJLZL4dSpsAcInmSfkJG TqAdXFTvJ89tP4F/PLBjsKxAA6q3EnZ0jNRO8Sm9OW4W4dbyaF3Ysh6OEmdIF93khBbT nVyQ==
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=R6V0GCSuNGHoRx64/JcOk2TlNqvnfBGPFRN2U2Prano=; b=jDhl2ARjfkq1rG+hHWPaXpj9muG1VR5Jo/jz/EI0bBMaqBkLxyfK7J+wOt3ecYq2aV Y43ICAtVBktRI5+EcwN9kL2cstkaOT4yu/cIAGjWxVRNAc2GVxamRh7DA+rbBW5nTEK9 70k4UtYDHwlZC6cwepZugPEl6fwQG+enPCw53rbwdqzj7R1BTmKEBjscw99GB4dDIKuD igJDcB0FM2tSJmOWoP0+M7QIwTUCLhqrWNRiL3T7OoprwDBjuZ371XAr7QAM4NhDSzVH 9GwRY0iTlvHQLsathcGc2bG62Es6FYIe7vrMzJeqBOkgY4fmqdHxqIDOnDeI4xhYj1Tr nClA==
X-Gm-Message-State: AOAM53334lWcYnhLZn7DzF1yBkWr2YVAJZif0YkpH1iJ5NaWNshgOqjW 3JFdBlEhVp8Ods1M8T9R1uFaC1UOxYY48endTNY=
X-Google-Smtp-Source: ABdhPJxvWqM9Hs6FO148BqSfr7solPO8GxyyYz5JZLICli0KIkxBmpOFBX54LkbMlHqWLtXGRCaKrqLv/cX82Dz4h3U=
X-Received: by 2002:a92:588b:: with SMTP id z11mr70772ilf.308.1602018215170; Tue, 06 Oct 2020 14:03:35 -0700 (PDT)
MIME-Version: 1.0
References: <MN2PR11MB47604813E0DC2DDA0E297A36D80C0@MN2PR11MB4760.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB47604813E0DC2DDA0E297A36D80C0@MN2PR11MB4760.namprd11.prod.outlook.com>
From: James <james.ietf@gmail.com>
Date: Tue, 06 Oct 2020 23:03:24 +0200
Message-ID: <CAO+dDxn1J2bOz1b8iPKbUnYLTFhSLJRhx9Od5hAHpP3TSkp7yQ@mail.gmail.com>
To: "Vinny Parla (vparla)" <vparla=40cisco.com@dmarc.ietf.org>
Cc: dns-privacy@ietf.org
Content-Type: multipart/alternative; boundary="000000000000a399f105b106eed3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/BJDVxPgG64BHc19b7znHOI_WgJM>
Subject: Re: [dns-privacy] DNS and QUIC,HTTP/3 Long term vision...
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.29
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, 06 Oct 2020 21:03:38 -0000

My most recent observations of discussions around DNS over QUIC and HTTP/3
was that some folks had attempted DNS over HTTP/3, however the overheads
(~14KiB for a query at worst-case) made it impractical and infeasible. With
regards to DNS over QUIC, the current dprive working group adopted draft
[1] is focusing on stub to recursive, but not necessarily as a multiplex
with an existing QUIC connection.

- J

1: https://tools.ietf.org/html/draft-ietf-dprive-dnsoquic-00

On Mon, 5 Oct 2020 at 17:31, Vinny Parla (vparla) <vparla=
40cisco.com@dmarc.ietf.org> wrote:

> Hi,
>
>
>
> It was suggested that I ask this question on the 3 lists:
>
>
>
> Now that QUIC & HTTP/3 is imminent…
>
>
>
> I would like to know what the opinion is of the community on the long term
> view of DNS.
>
> Would DNS remain an independent channel or would it be subsumed in a
> multiplexed stream via HTTP/3 in some future version?
>
>
>
> For example, would a browser perform DNS queries over a QUIC multiplexed
> session?
>
>  (e.g. similar to how today an http proxy can perform DNS queries on
> behalf of the client using that proxy)
>
>
>
> Would love to hear from implementors what their long term view is of this
> in particular.
>
>
>
> Thanks,
>
>
>
> -Vinny
>
>
> _______________________________________________
> dns-privacy mailing list
> dns-privacy@ietf.org
> https://www.ietf.org/mailman/listinfo/dns-privacy
>

v2.23.0 | Report a Bug | By Email