Re: [Doh] meta qtypes

Dave Lawrence <tale@dd.org> Tue, 20 March 2018 09:38 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 33314120721 for <doh@ietfa.amsl.com>; Tue, 20 Mar 2018 02:38:05 -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 2DNpBDnMk5ut for <doh@ietfa.amsl.com>; Tue, 20 Mar 2018 02:38:04 -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 473231200F1 for <doh@ietf.org>; Tue, 20 Mar 2018 02:38:04 -0700 (PDT)
Received: by gro.dd.org (Postfix, from userid 102) id 0114A38C1D; Tue, 20 Mar 2018 05:38:02 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: quoted-printable
Message-ID: <23216.54906.978869.638719@gro.dd.org>
Date: Tue, 20 Mar 2018 05:38:02 -0400
From: Dave Lawrence <tale@dd.org>
To: doh@ietf.org
In-Reply-To: <3a58b678-e514-b34f-f477-a3f36dbbea15@nic.cz>
References: <20180318143811.bn5kwr7oqo2ux6qm@miek.nl> <CAOdDvNoNN98zOuPAepS0=0Nt06+UAGV1ZCrxs0J2TzQaVnJz8w@mail.gmail.com> <CAN6NTqwA+Ub22Ajr_RGGh2+32aMMUMcKnPdUrUpkk8zF6TBn1Q@mail.gmail.com> <20180319131134.46hjo2eo757jqe7d@miek.nl> <16CD849A-55B3-487C-A370-CA96FF619BC3@bangj.com> <alpine.DEB.2.11.1803191408010.20806@grey.csi.cam.ac.uk> <23215.52292.616186.468475@gro.dd.org> <3a58b678-e514-b34f-f477-a3f36dbbea15@nic.cz>
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/cRidbXFTQvkM234QL2Bfba1ZKyI>
Subject: Re: [Doh] meta qtypes
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: Tue, 20 Mar 2018 09:38:05 -0000

Petr Špaček writes:
> Oh, but in that case the theoretical "proxy" would have re-assemble
> answers from TCP connection to a DNS server into jumbo-message. Bleh,
> please do not do this. DNS is complex as hell now and additional layer
> of complexity in translation is going to be major pain.

If your HTTP server didn't want to do an AXFR because of the extra
coding involved, it's got HTTP error codes to signal that.  Should the
doc recommend a specific one for whatever DNS features the HTTPS
server chooses not to support?

My main point is that on a practical level nothing precludes being
able to do a DNS response greater than 64k over HTTPS, and if an
implementer wants to support AXFR for whatever reason I don't see why
they need to be blocked from that.