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

Dave Lawrence <tale@dd.org> Mon, 11 June 2018 05:15 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 8420D130EDF for <doh@ietfa.amsl.com>; Sun, 10 Jun 2018 22:15:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] 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 uIdXvh85IjUL for <doh@ietfa.amsl.com>; Sun, 10 Jun 2018 22:15:37 -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 9AE3E12F1AC for <doh@ietf.org>; Sun, 10 Jun 2018 22:15:37 -0700 (PDT)
Received: by gro.dd.org (Postfix, from userid 102) id E3D342AFE5; Mon, 11 Jun 2018 01:15:36 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <23326.1400.909022.763497@gro.dd.org>
Date: Mon, 11 Jun 2018 01:15:36 -0400
From: Dave Lawrence <tale@dd.org>
To: DoH WG <doh@ietf.org>
In-Reply-To: <CAOdDvNoYYVEGC0Zsyd1m8sayuzZoW186gb4gmMojZzvYy6=6rw@mail.gmail.com>
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>
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/kPYQtVqp1pzkv_tXBf7AywhlDFs>
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: Mon, 11 Jun 2018 05:15:39 -0000

Patrick McManus writes:
> Therefore, match the restriction to what the problem is.. in other words the
> problem is that the MTI wireformat can only carry 64KB.

Spit-balling here, but what about two mandatory-to-implement wire
format types, with the only difference being that one, dns-message-64k
puts a hard cap at 64k, while the other, dns-message(-unlimited)?, has
basically a soft cap at 64k for people who are fronting legacy
handlers, until such time as that code is, if ever, updated.

Yeah I don't expect that to make the people who want the limit very
happy either, but there it is.  I'm not in love with it, but that
seems like the closest thing to a compromise on the issue that I can
envision at the moment if a limit really has to be hung on a media
type.