IETF Logo Mail Archive

Re: [Doh] Support requirements for Get and Post

Stephane Bortzmeyer <bortzmeyer@nic.fr> Thu, 22 March 2018 08:41 UTC

Return-Path: <bortzmeyer@nic.fr>
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 E17851201FA for <doh@ietfa.amsl.com>; Thu, 22 Mar 2018 01:41:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 AVIufYA4Cxlz for <doh@ietfa.amsl.com>; Thu, 22 Mar 2018 01:41:52 -0700 (PDT)
Received: from ayla.bortzmeyer.org (ayla.bortzmeyer.org [IPv6:2001:4b98:dc0:41:216:3eff:fe27:3d3f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13DE9126C2F for <doh@ietf.org>; Thu, 22 Mar 2018 01:41:50 -0700 (PDT)
Received: by ayla.bortzmeyer.org (Postfix, from userid 10) id 205A2A05BB; Thu, 22 Mar 2018 09:41:48 +0100 (CET)
Received: by godin (Postfix, from userid 1000) id AFFC1EC0B88; Thu, 22 Mar 2018 09:40:56 +0100 (CET)
Date: Thu, 22 Mar 2018 08:40:56 +0000
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Petr Špaček <petr.spacek@nic.cz>
Cc: doh@ietf.org
Message-ID: <20180322084056.GA30108@laperouse.bortzmeyer.org>
References: <alpine.DEB.2.20.1803171337530.1331@tvnag.unkk.fr> <CAN6NTqykeU1gT0TaDKahBPeF-a8gwYG7gsAEK_aSE0fNP-AsfQ@mail.gmail.com> <CAOdDvNq7e5YGtUap6tHu34zX5q1PvmQjAh+fc0m=xcRDUrmKhA@mail.gmail.com> <CAOdDvNqGvPRH3SzP_tkHVZHr-geacqDBa+QfoqXGVxFWW2qr2A@mail.gmail.com> <CAHbrMsAkU+KKwCFpyLD40aPZLEVtRj=aEZsaC+=Y2yYwKCiEyA@mail.gmail.com> <CAOdDvNpFqavszS_OzOdOOd+e0E+ufDcqkyQzCrnAtWPZnKEZFQ@mail.gmail.com> <CAHbrMsBYcO_1v-dPKP8vvubqfjLyRJhZPsmHHE_ReVRiczbuYA@mail.gmail.com> <23215.63984.364570.759118@gro.dd.org> <CAOdDvNqVE3mDJ31fKs0zLY8Lu-Pt2oeZ2UtbOorz3=TeiaBxRg@mail.gmail.com> <958176d9-00cd-e8ba-8c74-c6c736ab99e8@nic.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <958176d9-00cd-e8ba-8c74-c6c736ab99e8@nic.cz>
X-Transport: UUCP rules
X-Operating-System: Ubuntu 16.04 (xenial)
X-Charlie: Je suis Charlie
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/2kTos9LJVs670SanyP2ij-ABQvM>
Subject: Re: [Doh] Support requirements for Get and Post
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: Thu, 22 Mar 2018 08:41:54 -0000

On Mon, Mar 19, 2018 at 10:59:31PM +0100,
 Petr Špaček <petr.spacek@nic.cz> wrote 
 a message of 25 lines which said:

> A subversive question:
> Do we *actually* need GET and POST? Could we get away with just one of
> these?

No, we don't NEED. But today, as Ben Schwartz and Dave Lawrence
noticed, we have a much worse situation: clients and servers can choose
and, as a result, they may be unable to interoperate. So, mandating
GET *or* POST *or* both is necessary, to solve this interoperability
problem.

Now, regarding your question: experience from the hackathon seems to
indicate that supporting both GET and POST is very little work.

v2.23.0 | Report a Bug | By Email