Re: [Doh] [Ext] Proposal to close off these threads

Patrick McManus <pmcmanus@mozilla.com> Tue, 12 June 2018 00:36 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 C8633130E99 for <doh@ietfa.amsl.com>; Mon, 11 Jun 2018 17:36:53 -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 gucEOxzatNBs for <doh@ietfa.amsl.com>; Mon, 11 Jun 2018 17:36:52 -0700 (PDT)
Received: from linode64.ducksong.com (linode6only.ducksong.com [IPv6:2600:3c02::f03c:91ff:fe6e:e8da]) by ietfa.amsl.com (Postfix) with ESMTP id EBD5A130E7D for <doh@ietf.org>; Mon, 11 Jun 2018 17:36:51 -0700 (PDT)
Received: from mail-oi0-f48.google.com (mail-oi0-f48.google.com [209.85.218.48]) by linode64.ducksong.com (Postfix) with ESMTPSA id 72A723A03D for <doh@ietf.org>; Mon, 11 Jun 2018 20:36:50 -0400 (EDT)
Received: by mail-oi0-f48.google.com with SMTP id h79-v6so19533350oig.13 for <doh@ietf.org>; Mon, 11 Jun 2018 17:36:50 -0700 (PDT)
X-Gm-Message-State: APt69E26WbVekRwUYCIUZqaV1iqTVRMK9/EZr8m6wZHUU3iFfA1PGKxK zlktNQAmuVWdsXLuv8+NtCn6gKDwTvmj+WPTdb0=
X-Google-Smtp-Source: ADUXVKLULOFq327OYASkTs8PK0JunFjNQ4UA3+XGhIQzKvLlIzofveu8K3zlqJWfEbKzrlSOzsgdYfDFsFaJ4DrJm0E=
X-Received: by 2002:aca:5c46:: with SMTP id q67-v6mr714306oib.17.1528763810132; Mon, 11 Jun 2018 17:36:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4a:8a32:0:0:0:0:0 with HTTP; Mon, 11 Jun 2018 17:36:48 -0700 (PDT)
In-Reply-To: <alpine.DEB.2.11.1806111648580.10764@grey.csi.cam.ac.uk>
References: <1D917C05-2B74-4607-9EE2-55D367FF48B5@icann.org> <20180610220841.GB16671@server.ds9a.nl> <CAOdDvNrXpyGTFmMHcF6Vnegku0Zmiw_LFb1VKm1O2mFgB3aHEw@mail.gmail.com> <FB8DBC78-4584-4133-AF1F-E0483C28224D@icann.org> <CAOdDvNoYYVEGC0Zsyd1m8sayuzZoW186gb4gmMojZzvYy6=6rw@mail.gmail.com> <alpine.DEB.2.11.1806111648580.10764@grey.csi.cam.ac.uk>
From: Patrick McManus <pmcmanus@mozilla.com>
Date: Mon, 11 Jun 2018 17:36:48 -0700
X-Gmail-Original-Message-ID: <CAOdDvNoQW0p1XpYPQ0kpxyPJ5hrtcQEBMw0qZFsP7_Kc3do4cQ@mail.gmail.com>
Message-ID: <CAOdDvNoQW0p1XpYPQ0kpxyPJ5hrtcQEBMw0qZFsP7_Kc3do4cQ@mail.gmail.com>
To: Tony Finch <dot@dotat.at>
Cc: Patrick McManus <pmcmanus@mozilla.com>, Paul Hoffman <paul.hoffman@icann.org>, DoH WG <doh@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d93a84056e670f46"
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/1keQ9izgn5h4XNwFVonQibwKfLY>
Subject: Re: [Doh] [Ext] Proposal to close off these threads
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.26
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: Tue, 12 Jun 2018 00:36:54 -0000

On Mon, Jun 11, 2018 at 8:54 AM, Tony Finch <dot@dotat.at> wrote:

> Patrick McManus <pmcmanus@mozilla.com> wrote:
> >
> > There has a been a convincing case that a > 64KB axfr responses uses 2
> > wireformat records in TCP today and therefore won't fit in the DoH MTI
> > wireformat media type. AIUI that's not because its AXFR, but because it
> is
> > >64KB, right? At the same time tale convincingly argues he has plenty of
> > <64KB zones that only use one message and match our MTI fine.
>
> It's more complicated than that :-)
>
> Small zones can be transferred using multiple messages too.
>
>
it doesn't need to be more complicated. The mti wireformat is defined as
one message (or if its not - it should be clarified) that might be limited
to 64KB. I thought one message was already clear and we were debating the
64KB point.

so if you can't meet those constraints, you can't use that media format.
but its not inherently about the query type.


> "HTTP defines status code 406 for cases where the server cannot generate a
> > representation suitable for the client". We can probably just say that.
>
> My DoH server sends a 200 OK HTTP response containing a NOTIMP DNS
> response.
>
>
Personally, I think you're better off with the HTTP error in this case as
the problem is with finding a matching HTTP transport.