IETF Logo Mail Archive

Re: [Doh] Support requirements for Get and Post

Patrick McManus <pmcmanus@mozilla.com> Mon, 19 March 2018 18:01 UTC

Return-Path: <pmcmanus@mozilla.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 B36AA12DA6F for <doh@ietfa.amsl.com>; Mon, 19 Mar 2018 11:01:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.233
X-Spam-Level:
X-Spam-Status: No, score=-1.233 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 pJTiiZxerpBG for <doh@ietfa.amsl.com>; Mon, 19 Mar 2018 11:01:28 -0700 (PDT)
Received: from linode64.ducksong.com (www.ducksong.com [192.155.95.102]) by ietfa.amsl.com (Postfix) with ESMTP id D725A12DA49 for <doh@ietf.org>; Mon, 19 Mar 2018 11:01:27 -0700 (PDT)
Received: from mail-oi0-f54.google.com (mail-oi0-f54.google.com [209.85.218.54]) by linode64.ducksong.com (Postfix) with ESMTPSA id 3D7A13A04F for <doh@ietf.org>; Mon, 19 Mar 2018 14:01:27 -0400 (EDT)
Received: by mail-oi0-f54.google.com with SMTP id u141so3183996oif.1 for <doh@ietf.org>; Mon, 19 Mar 2018 11:01:27 -0700 (PDT)
X-Gm-Message-State: AElRT7HiV/wCPJKMVs7wob/eUsW8Kpawq/3RrLZQ8X6y+1C8/xFkL0Gx WNXl12+VPTM3gcqKiHxJ3u/UEz2MLhS6H27jkXg=
X-Google-Smtp-Source: AG47ELtJ+jEQqJ/ylO8D6ToWFRQMLNHiY9S70gtoN3+H0guKTfzP+0pVCFrQHUkfhdCsEqCzNMkzmPtDQuRb4gOEhBU=
X-Received: by 10.202.3.65 with SMTP id 62mr7873055oid.38.1521482486935; Mon, 19 Mar 2018 11:01:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.74.66.212 with HTTP; Mon, 19 Mar 2018 11:01:25 -0700 (PDT)
In-Reply-To: <23215.63984.364570.759118@gro.dd.org>
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> <23215.63984.364570.759118@gro.dd.org>
From: Patrick McManus <pmcmanus@mozilla.com>
Date: Mon, 19 Mar 2018 18:01:25 +0000
X-Gmail-Original-Message-ID: <CAOdDvNqVE3mDJ31fKs0zLY8Lu-Pt2oeZ2UtbOorz3=TeiaBxRg@mail.gmail.com>
Message-ID: <CAOdDvNqVE3mDJ31fKs0zLY8Lu-Pt2oeZ2UtbOorz3=TeiaBxRg@mail.gmail.com>
To: Dave Lawrence <tale@dd.org>
Cc: DoH WG <doh@ietf.org>
Content-Type: multipart/alternative; boundary="001a113ba0802a84760567c7bfb7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/yTaybF2cWiJ1T7A4RmiRslL4whs>
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 18:01:33 -0000

this is an open issue I was planning to address with f2f time of the wg as
part of the slot related to this document (of course in addition to any
mailing list comments).

On Mon, Mar 19, 2018 at 5:57 PM, Dave Lawrence <tale@dd.org> wrote:

> 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.
>
> _______________________________________________
> Doh mailing list
> Doh@ietf.org
> https://www.ietf.org/mailman/listinfo/doh
>

v2.23.0 | Report a Bug | By Email