IETF Logo Mail Archive

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

Ray Bellis <ray@bellis.me.uk> Fri, 17 November 2023 11:04 UTC

Return-Path: <ray@bellis.me.uk>
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 9FE31C15155A for <dnsop@ietfa.amsl.com>; Fri, 17 Nov 2023 03:04:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=portfast.net
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 LCJ0zuyJN1mg for <dnsop@ietfa.amsl.com>; Fri, 17 Nov 2023 03:04:04 -0800 (PST)
Received: from mail.portfast.net (mail.portfast.net [IPv6:2a03:9800:20:1::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BFD9C15153E for <dnsop@ietf.org>; Fri, 17 Nov 2023 03:04:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=portfast.net; s=dkim; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: From:References:Cc:To:Subject:MIME-Version:Date:Message-ID:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=t7j9irg5EJsbtSoW487bwR20TM41batGmDHa/hGkTSM=; b=FoIMmbbI8narCtXedekGxrff8p 4YiDMv6e0VEn0h4NqgENvhZl48CyboEtuE2vZSJN+5tCYuYexgYzhv2DMwnu4RfA+g0FIlTMP9xAw 975Wd29mWxYJ8VJCe5lSZNMu1KhGLiS7EkhSSP/+Dj6DvnqOcaQI83M8oZ0tZoHmOmes=;
Received: from [213.18.158.12] (port=56831 helo=[10.1.2.72]) by mail.portfast.net ([188.246.200.9]:465) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_128_GCM:128) id 1r3wdk-002z3t-1p (Exim 4.96) (return-path <ray@bellis.me.uk>); Fri, 17 Nov 2023 11:04:00 +0000
Message-ID: <be9ecbb4-2e19-46ee-ae42-5eb19cc29936@bellis.me.uk>
Date: Fri, 17 Nov 2023 11:03:59 +0000
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-GB
To: Paul Wouters <paul@nohats.ca>
Cc: dnsop@ietf.org
References: <169996260219.33611.6405129886775920165@ietfa.amsl.com> <5c529b73-07a8-3e81-c478-a3aaed8b9a23@nohats.ca> <6c35913b-e938-4b0f-88da-0c07151d2735@bellis.me.uk> <3c36d4ae-2a78-f033-4b4b-207e2ca91364@nohats.ca>
From: Ray Bellis <ray@bellis.me.uk>
In-Reply-To: <3c36d4ae-2a78-f033-4b4b-207e2ca91364@nohats.ca>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/XQbqibntNOSiEk4O_qjSZvd1swU>
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:04:08 -0000


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.

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'd also say that this is an extension - it does not change any existing 
core DNS features.   It's 100% backwards compatible.

Ray

v2.23.0 | Report a Bug | By Email