Re: [Doh] New query formats

Ben Schwartz <bemasc@google.com> Tue, 03 April 2018 18:53 UTC

Return-Path: <bemasc@google.com>
X-Original-To: doh@ietfa.amsl.com
Delivered-To: doh@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 139191242EA for <doh@ietfa.amsl.com>; Tue, 3 Apr 2018 11:53:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.709
X-Spam-Level:
X-Spam-Status: No, score=-2.709 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 0lrMnsh9RfPE for <doh@ietfa.amsl.com>; Tue, 3 Apr 2018 11:53:47 -0700 (PDT)
Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::22a]) (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 94661120721 for <doh@ietf.org>; Tue, 3 Apr 2018 11:53:47 -0700 (PDT)
Received: by mail-it0-x22a.google.com with SMTP id e98-v6so24149693itd.4 for <doh@ietf.org>; Tue, 03 Apr 2018 11:53:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=JtKgaxEvI8UGqqb/1Uj4Hyd0AgC+4K0bsKXu5DfgcXs=; b=GVb1V7VySqU9GIW9wkaFo7UkKt2XmrfU3JuYrzT07fKLnxUyrvgmxyXU6hT+RAfnuy qjvuKuC/zjou7ATjt8/XH/uxcr/7eKHYFqg2KIWm1p9k+BnsFjLadV+Qn+UHRbWQA6+n cuz56L81miyTM2GdRXhsVgBl4OccYEHT+bXAeCO7yQVXkGrsICS5mLYdJeZ8vMk26QNq ci08yT4h9dEzQpsiAm3G9zOtIjuiynNJVgzzuUwsp/G9gzJjoFdwggTznJET7zxHndZd 8yHzMElwwuW3WIu4A9nYQJs/j8CD4LzJNsQyJCs9vtOfwafqqoZBQsNU5BzCMckGn/17 Z90Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=JtKgaxEvI8UGqqb/1Uj4Hyd0AgC+4K0bsKXu5DfgcXs=; b=TRJKEse24xAYMWJvvVHS6savFXmMTEQZQz/1DTYEZZF0NYaS/hI1LbPS95Zkw+DynA XcfiUQqSmvmJpp0UCdDKiBHzslVy/g9MtKgmXUqBog3vfGtlk3TI9GL9/WCvby1JLbO0 qEgrr8xDqmPQQqBKoya0ht3tEo88sxASbEAad5J7sRi27cC98aRhmrwKEK6Lv2QxKD/0 c/LBoaazTLrc6ITH9al2+JQmhJKwAoS/rhHM4nh13hT7FvCl1kIgVX0QzBo3mmzQgDpQ gmTT/N9TnqyeEVBVmWpHQsus/+INrpmLG2I7SkMTR5M8FZue8H/Of2JCXB6s10iRM9pb 7B8Q==
X-Gm-Message-State: ALQs6tAyKD4uvCLB84ZzycvPUMzKIZQgvrc6XppuGzkSnkPav0YsS1ia kF9h7qPLawohpAW+KHghL7aP2Q3B17kmnmE8UlOwDFvwNNA=
X-Google-Smtp-Source: AIpwx49zW1yFkia5+lczn3gO7l15dgwv1WPi1Fj3sc4oiSfQO2SJd2JKT1+oUwNAQChK9NuE2AaZaSUFNabpy5yzhgs=
X-Received: by 2002:a24:27d7:: with SMTP id g206-v6mr6093812ita.21.1522781625787; Tue, 03 Apr 2018 11:53:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.168.210 with HTTP; Tue, 3 Apr 2018 11:53:45 -0700 (PDT)
In-Reply-To: <20180326083031.2bco57z33vyty766@nic.fr>
References: <CABkgnnVf_bEsxkTuFeCLO+PxUu6cYb1K-5j1C4LzOsrt0-V6HQ@mail.gmail.com> <20180326083031.2bco57z33vyty766@nic.fr>
From: Ben Schwartz <bemasc@google.com>
Date: Tue, 03 Apr 2018 14:53:45 -0400
Message-ID: <CAHbrMsB3ecOipRV6zg-pPqhuwxPPMi8mTiPjCVVBDnfgYdpzjw@mail.gmail.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Cc: Martin Thomson <martin.thomson@gmail.com>, DoH WG <doh@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="000000000000f41c3d0568f639e3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/tEki_AsrF3CfapqfRrDQYljnTtA>
Subject: Re: [Doh] New query formats
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DNS Over HTTPS <doh.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/doh>, <mailto:doh-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/doh/>
List-Post: <mailto:doh@ietf.org>
List-Help: <mailto:doh-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/doh>, <mailto:doh-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Apr 2018 18:53:50 -0000

This suggestion has now been implemented in draft-05.  Do you feel the new
text achieves your goal?

In particular, I will note the following sentences:

The DNS API server defines the URI used by the
> request through the use of a URI Template [RFC6570].  Configuration
> and discovery of the URI Template is done out of band from this
> protocol.


and

These examples use a DNS API service with a URI Template of
>    "https://dnsserver.example.net/dns-query{?dns}"


Based on this text, it seems to me that if a client is configured out of
band with a template of this kind, and the server is later upgraded to
support additional query forms, the client cannot exercise those forms
until after a new out-of-band configuration update, because it does not
have any instructions about how to map the new values into a URI.

This is in contrast to draft-04's URL-based configuration, which would
allow a client to attempt new query forms without requiring a configuration
update.

On Mon, Mar 26, 2018 at 4:30 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr>
wrote:

> On Thu, Mar 22, 2018 at 02:32:40PM +0000,
>  Martin Thomson <martin.thomson@gmail.com> wrote
>  a message of 45 lines which said:
>
> > 3. Specify that other parameters can be used to carry information
> > about queries.  Servers that find unknown query parameters MUST ignore
> > them.
> >
> > 4. Define a new registry for header field parameters.  (The URI
> > template would have covered this neatly, so you could avoid that.)
>
> Yes, RFC 6570 is the right way to specify these parameters.
>
> You can get some inspiration from my (old) DNS looking glass:
>
> http://www.bortzmeyer.org/dns-lg-usage.html
>
> _______________________________________________
> Doh mailing list
> Doh@ietf.org
> https://www.ietf.org/mailman/listinfo/doh
>