Re: [Doh] [Ext] Consensus confirmation

Shane Kerr <shane@time-travellers.org> Mon, 26 March 2018 06:54 UTC

Return-Path: <shane@time-travellers.org>
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 2308A126BF6 for <doh@ietfa.amsl.com>; Sun, 25 Mar 2018 23:54:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 zHTs5Fjp0XXS for <doh@ietfa.amsl.com>; Sun, 25 Mar 2018 23:54:56 -0700 (PDT)
Received: from time-travellers.nl.eu.org (c.time-travellers.nl.eu.org [IPv6:2a02:2770::21a:4aff:fea3:eeaa]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2CA8126B72 for <doh@ietf.org>; Sun, 25 Mar 2018 23:54:56 -0700 (PDT)
Received: from [79.124.59.194] (helo=[127.0.0.1]) by time-travellers.nl.eu.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <shane@time-travellers.org>) id 1f0M2f-0002ve-NU for doh@ietf.org; Mon, 26 Mar 2018 06:55:41 +0000
To: doh@ietf.org
References: <CAHbrMsAs8G-eW7DTUtbdGukLszHohmk4NHhFPWw01+h3-v9Uog@mail.gmail.com> <E40FD111-0316-426F-AC43-38F75FE46893@icann.org>
From: Shane Kerr <shane@time-travellers.org>
Message-ID: <a7dde3b7-f407-c928-3f18-fa08150a34b2@time-travellers.org>
Date: Mon, 26 Mar 2018 06:54:00 +0000
MIME-Version: 1.0
In-Reply-To: <E40FD111-0316-426F-AC43-38F75FE46893@icann.org>
Content-Type: text/plain; charset="windows-1252"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/QmumovNH6957UvJW4W1e7ggG2KU>
Subject: Re: [Doh] [Ext] Consensus confirmation
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: Mon, 26 Mar 2018 06:54:58 -0000

All,

Paul Hoffman:
>> 1. Should we have a content-type that is Mandatory to Implement?
>>
>> Several participants spoke in favor of making the default format (currently called "application/dns-udpwireformat") mandatory, at least for servers.
> 
> application/dns-udpwireformat needs to be mandatory to implement for us to have maximum interoperability out of the box.
> 
>> 2. Among the GET and POST modes of operation, which, if any, should be mandatory to implement?
>>
>> Among the participants, there was consensus in favor of making both GET and POST mandatory to implement for servers.
> 
> Both GET and POST need to be mandatory to implement for servers so that we have maximum interoperability out of the box.

I agree on both counts. Otherwise we are dooming every client ever
written from now until the end of time to either:

* Have a little dance trying to figure out server capabilities, or
* Rely on the lowest-common denominator.

Cheers,

--
Shane