IETF Logo Mail Archive

Re: [Doh] Support requirements for Get and Post

Dave Lawrence <tale@dd.org> Mon, 19 March 2018 17:57 UTC

Return-Path: <tale@dd.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 BCFB012D873 for <doh@ietfa.amsl.com>; Mon, 19 Mar 2018 10:57:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 HwcfP1PKX0vH for <doh@ietfa.amsl.com>; Mon, 19 Mar 2018 10:57:05 -0700 (PDT)
Received: from gro.dd.org (gro.dd.org [207.136.192.136]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B86612D88A for <doh@ietf.org>; Mon, 19 Mar 2018 10:57:05 -0700 (PDT)
Received: by gro.dd.org (Postfix, from userid 102) id 5D0C73843A; Mon, 19 Mar 2018 13:57:04 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <23215.63984.364570.759118@gro.dd.org>
Date: Mon, 19 Mar 2018 13:57:04 -0400
From: Dave Lawrence <tale@dd.org>
To: doh@ietf.org
In-Reply-To: <CAHbrMsBYcO_1v-dPKP8vvubqfjLyRJhZPsmHHE_ReVRiczbuYA@mail.gmail.com>
References: <CAN6NTqzkUeF79y=heQ7PK7T3mQVDDk5WRtqB-npi6PuQ2s5bNQ@mail.gmail.com> <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>
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/mpUOJIvLyKPrfh4ufRZWnOfOinU>
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: Mon, 19 Mar 2018 17:57:08 -0000

Ben Schwartz writes:
> So does that mean that a DOH server and client that both comply with all
> SHOULD-strength requirements still may not be able to exchange any DNS data? 
> That seems like a weaker guarantee of compatibility than is typical at the
> IETF.

Has an answer to this question come through yet?

> If following all the SHOULD-level recommendations is not sufficient
> to ensure compatibility, then as an implementor I would appreciate
> some clear additional guidance on what I have to do to make my
> client compatible with any compliant DOH server (and vice versa as a
> server implementor).

Very much agree.

v2.2.0 | Report a Bug | By Email