Re: [DNSOP] I-D Action: draft-bellis-dnsext-multi-qtypes-08.txt

Paul Wouters <paul@nohats.ca> Fri, 17 November 2023 11:25 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 085F4C15171B for <dnsop@ietfa.amsl.com>; Fri, 17 Nov 2023 03:25:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xYrvAPJlrU-h for <dnsop@ietfa.amsl.com>; Fri, 17 Nov 2023 03:25:01 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.85]) (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 44AC9C15108A for <dnsop@ietf.org>; Fri, 17 Nov 2023 03:25:00 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4SWvhB48KQzCKc; Fri, 17 Nov 2023 12:24:58 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1700220298; bh=C1J1J5DbvKvSBvC0YpHvxkTtlXxGHF8Mj81uEE2XG0M=; h=From:Subject:Date:References:Cc:In-Reply-To:To; b=NTAKo4w4WjO/3LSZYvdIepX7XVbY7Yo7o/rS9cA6npgbdqA3t7Dvw0BJEVwbK/cHu /7qMbVo0QZjYAoJ6YePPOEsIdkamMwmyX4SwlLsxaf6wQp16omBmAlhRTQdLrWA4kV uu5UUDDvpb6pZtNDa144XvXzrJ3c30v9s6RX/vAg=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id exglu2lTH75V; Fri, 17 Nov 2023 12:24:57 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [193.110.157.194]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Fri, 17 Nov 2023 12:24:57 +0100 (CET)
Received: from smtpclient.apple (77-173-61-107.fixed.kpn.net [77.173.61.107]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by bofh.nohats.ca (Postfix) with ESMTPSA id 6A00710BFDC1; Fri, 17 Nov 2023 06:24:56 -0500 (EST)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Paul Wouters <paul@nohats.ca>
Mime-Version: 1.0 (1.0)
Date: Fri, 17 Nov 2023 12:24:42 +0100
Message-Id: <FC8BADB9-CF1E-4AC2-87CA-FE0FCDD96981@nohats.ca>
References: <be9ecbb4-2e19-46ee-ae42-5eb19cc29936@bellis.me.uk>
Cc: dnsop@ietf.org
In-Reply-To: <be9ecbb4-2e19-46ee-ae42-5eb19cc29936@bellis.me.uk>
To: Ray Bellis <ray@bellis.me.uk>
X-Mailer: iPhone Mail (21A360)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/YDtAyFnj1WT3olBAuoMBDdf8Xxw>
Subject: Re: [DNSOP] I-D Action: draft-bellis-dnsext-multi-qtypes-08.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Nov 2023 11:25:06 -0000

On Nov 17, 2023, at 12:04, Ray Bellis <ray@bellis.me.uk> wrote:
> 
> 
> 
>> On 17/11/2023 10:41, Paul Wouters wrote:
>> 
>> I think it would be unwise to make assumptions on how people will use
>> this feature. They might want to ask for many more records along with
>> A/AAAA records. If we change a core DNS feature, it should not designed
>> for a specific DNSSD use case of HTTPS.
> 
> The extension is already limited to a maximum of 7 additional QTYPES, and some might argue that that's too many.  A consideration here is the opportunity for amplification.

I think the artificial limit should not be there.
Amplification is handled by source validation, eg allow for TCP or after sending DNS COOKIES. 

> The main DNSSD use case is TXT+SRV.  A+AAAA+HTTPS was an example of a future use case that might be popular outside of DNSSD, and where NSEC bitmaps are not efficient.

I find the efficiently argument not very relevant if we are asking potential blobs of public keys etc, eg for ECH.

> I'd also say that this is an extension - it does not change any existing core DNS features.   It's 100% backwards compatible.

To me it’s generic, it’s not a very specific focused use case that is only valid in the context of dnssd.

Paul