IETF Logo Mail Archive

[Doh] URI Template

Daniel Stenberg <daniel@haxx.se> Fri, 31 August 2018 06:28 UTC

Return-Path: <daniel@haxx.se>
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 E06BA130E12 for <doh@ietfa.amsl.com>; Thu, 30 Aug 2018 23:28:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 zbGNcHfuGEvH for <doh@ietfa.amsl.com>; Thu, 30 Aug 2018 23:28:26 -0700 (PDT)
Received: from giant.haxx.se (www.haxx.se [IPv6:2a00:1a28:1200:9::2]) by ietfa.amsl.com (Postfix) with ESMTP id 9865412872C for <doh@ietf.org>; Thu, 30 Aug 2018 23:28:26 -0700 (PDT)
Received: from giant.haxx.se (mail [127.0.0.1]) by giant.haxx.se (8.15.2/8.15.2/Debian-4) with ESMTPS id w7V6SMq2026685 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <doh@ietf.org>; Fri, 31 Aug 2018 08:28:22 +0200
Received: from localhost (dast@localhost) by giant.haxx.se (8.15.2/8.15.2/Submit) with ESMTP id w7V6SM7h026680 for <doh@ietf.org>; Fri, 31 Aug 2018 08:28:22 +0200
X-Authentication-Warning: giant.haxx.se: dast owned process doing -bs
Date: Fri, 31 Aug 2018 08:28:22 +0200
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: doh@ietf.org
Message-ID: <alpine.DEB.2.20.1808310821230.28896@tvnag.unkk.fr>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
X-fromdanielhimself: yes
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/Lv6XzwT-27F3TiOLXs5jwzuNer4>
Subject: [Doh] URI Template
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.27
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: Fri, 31 Aug 2018 06:28:29 -0000

Hey,

I've written three separate client-side DoH implementations by now and I'm 
mentoring a 4th. I don't get the use of URI Template in the spec.

A template is meant to be used to describe how the URI can be made up and the 
DoH spec mandates the name 'dns' to be used for the DNS packet parameter when 
GET is used. There's no other URL parameters.

Can a service then offer any other template than with a trailing '{?dns}' ? 
Like 'https://example.org/path{?dns}'.

If it can provide other parts in the {} section, what is a generic client 
supposed to do with those?

I'm probably just stupid.

-- 

  / daniel.haxx.se

v2.23.0 | Report a Bug | By Email