Re: [dnssd] [DNSOP] QDCOUNT > 1 (a modest proposal)

Ray Bellis <ray@bellis.me.uk> Mon, 13 February 2023 02:48 UTC

Return-Path: <ray@bellis.me.uk>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7ACCC151524 for <dnssd@ietfa.amsl.com>; Sun, 12 Feb 2023 18:48:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 2dAsvC8lk4il for <dnssd@ietfa.amsl.com>; Sun, 12 Feb 2023 18:48:19 -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 A4A56C14F740 for <dnssd@ietf.org>; Sun, 12 Feb 2023 18:48:19 -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:To:Subject:MIME-Version:Date:Message-ID:Sender:Reply-To:Cc: 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=8WAN36EaI7IVCKiAQj2QVtienJEqvJFtNo9zlc12yqg=; b=LGL/c7RuoOg6E92zQ4IZxB1QgW QyGxWTaBcvmn35loCKTtJ9xQAmHcvtmeBzHVzomOP0ZOk0/b4SVM6tbw16E1ytYhzKkPysBpLfDIe 3triWVJ8QqLSR34KIxGnB5fGE4uebWFwj7Bty1i+iji5qD64sIdm+gE0aihLhmjAfcGI=;
Received: from [50.220.39.108] (port=26132 helo=[192.168.0.159]) by mail.portfast.net ([188.246.200.9]:465) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1pROt6-00071z-Aj (Exim 4.92) for dnssd@ietf.org (return-path <ray@bellis.me.uk>); Mon, 13 Feb 2023 02:48:16 +0000
Message-ID: <30701828-b479-d6d7-630b-c0b8906b42e1@bellis.me.uk>
Date: Sun, 12 Feb 2023 21:48:15 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.7.2
To: dnssd@ietf.org
References: <CAPt1N1nQ2d518E3T0aWoy3POejv=fPpGfJCociMAxstT93LcDw@mail.gmail.com> <a7233917-03d7-12ee-277c-ad9844760a3d@redbarn.org> <CAPt1N1mrwsJ-V4LN0NpvvwnKvhv39wLYDpcjzFgHZ61OssVWjw@mail.gmail.com> <da2126e6-15a3-46ea-6bfa-e11c2fe10ae7@redbarn.org>
From: Ray Bellis <ray@bellis.me.uk>
In-Reply-To: <da2126e6-15a3-46ea-6bfa-e11c2fe10ae7@redbarn.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/-eOf6k6ByU4sHN2_DFCjAaiD-bE>
Subject: Re: [dnssd] [DNSOP] QDCOUNT > 1 (a modest proposal)
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2023 02:48:23 -0000


On 12/02/2023 12:30, Paul Vixie wrote:

> i'll clarify my previous remarks. i am not proposing multiple rcodes, 
> but rather, multiple qtypes. this enforces the all-qnames-the-same 
> constraint implicitly -- because there is only one qname. in your 
> qdcount>1 design, this constraint must be enforced by the responder, 
> which further ambiguates the rcode=formerr signal. also, this is not 
> similar to what i proposed in EDNS1, it's a much simpler thing which 
> better leverages EDNS0.
> 
> in the normal-for-now case in which the responder doesn't grok the new 
> EDNS option, that option will be ignored and you'll get back a single 
> answer to the q-tuple in the qdcount=1 question section. so in a single 
> round trip you get one answer plus an indication of whether the new 
> option for multiple queries is or isn't available from that responder. 
> so there is no new failure scenario and no wasted round trip.

Paul, I wrote a draft on this, to which I recall you had some f2f input 
when I discussed it with you at one of the Prague IETFs:

draft-bellis-dnsext-multi-qtypes-04

Ray