Re: [Add] questions about the Examples section of svcb-dns-02

Peter van Dijk <peter.van.dijk@powerdns.com> Fri, 09 April 2021 07:36 UTC

Return-Path: <peter.van.dijk@powerdns.com>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C36483A13F2 for <add@ietfa.amsl.com>; Fri, 9 Apr 2021 00:36:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 dpqpMJSKO7mX for <add@ietfa.amsl.com>; Fri, 9 Apr 2021 00:36:54 -0700 (PDT)
Received: from mx4.open-xchange.com (alcatraz.open-xchange.com [87.191.39.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41BDE3A13F1 for <add@ietf.org>; Fri, 9 Apr 2021 00:36:53 -0700 (PDT)
Received: from imap.open-xchange.com (imap.open-xchange.com [84.81.54.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx4.open-xchange.com (Postfix) with ESMTPSA id 2ACCF6A014; Fri, 9 Apr 2021 09:36:51 +0200 (CEST)
Received: from plato ([84.81.54.175]) by imap.open-xchange.com with ESMTPSA id 3saGCRMEcGA7eAAA3c6Kzw (envelope-from <peter.van.dijk@powerdns.com>); Fri, 09 Apr 2021 09:36:51 +0200
Message-ID: <a18e11d6a62b78c8f2b07940dd8e68acede3cac8.camel@powerdns.com>
From: Peter van Dijk <peter.van.dijk@powerdns.com>
To: ADD Mailing list <add@ietf.org>
Date: Fri, 09 Apr 2021 09:36:50 +0200
In-Reply-To: <CAHbrMsAN0PkC-yUdWR6HhkrX-JJ3cCwvgGBJRD2EXLYRjbQVEw@mail.gmail.com>
References: <4613b8d0773d1ae5f806347bbce909fa74439886.camel@powerdns.com> <CAHbrMsCM3pwu7zYVhVzCMKB37_gSMyb6KY3je3NVYQBAwt6kNg@mail.gmail.com> <dc371c7284d3c05d07cf0a550b37f9a624d968c9.camel@powerdns.com> <ba952ca3-b6fe-be9a-8829-a926cb32e148@shaw.ca> <CAHbrMsAN0PkC-yUdWR6HhkrX-JJ3cCwvgGBJRD2EXLYRjbQVEw@mail.gmail.com>
Organization: PowerDNS.COM B.V.
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.30.5-1.1
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/DfD4PiUAQVXhBkiy9-6dQZ-IbvI>
Subject: Re: [Add] questions about the Examples section of svcb-dns-02
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Apr 2021 07:36:59 -0000

Hi Ben,

thank you for adding all those examples, this should unconfuse many
readers.

(I picked this email to reply to, instead of end of thread, because I'm
typing something more inline below).

On Thu, 2021-04-08 at 11:05 -0400, Ben Schwartz wrote:
> OK, I've clarified (and corrected, oops) the explanation of the examples, and added another one to highlight the default-DoT behavior: https://github.com/bemasc/svcb-dns/commit/e59c995fa976a19b5baf1770afb231d3dcb729e1
> 
> We can certainly remove the default ALPN, but personally I like having empty SvcParams correspond to a common default.  The size savings (~8 bytes) are probably not important, although MTU could become relevant in the context of SVCB delegation responses as envisioned by draft-rescorla-dprive-adox.

I think this one hits the core of the problem for me. I'm not confused
about what -empty- SvcParams mean. I am (well, I was) confused by
alpn=h2,h3 meaning alpn=dot,h2,h3.

So I wonder if having a default, but alpn= always *replacing* that
default instead of appending to it, might make more sense. It certainly
feels clearer to me.

In terms of packet size, some records may spend four more bytes on
'dot,' because they do combine it with DoH in one SVCB record. Other
records will spend a few bytes less on not needing no-default-alpn. I
don't know how this balances out in the end.

Kind regards,
-- 
Peter van Dijk
PowerDNS.COM BV - https://www.powerdns.com/