IETF Logo Mail Archive

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

Ted Lemon <mellon@fugue.com> Thu, 16 February 2023 21:36 UTC

Return-Path: <mellon@fugue.com>
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 6539AC15C528 for <dnssd@ietfa.amsl.com>; Thu, 16 Feb 2023 13:36:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20210112.gappssmtp.com
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 U1XC7eP53p-t for <dnssd@ietfa.amsl.com>; Thu, 16 Feb 2023 13:36:49 -0800 (PST)
Received: from mail-qv1-xf35.google.com (mail-qv1-xf35.google.com [IPv6:2607:f8b0:4864:20::f35]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EECA0C14CF05 for <dnssd@ietf.org>; Thu, 16 Feb 2023 13:36:49 -0800 (PST)
Received: by mail-qv1-xf35.google.com with SMTP id l4so2402563qvh.11 for <dnssd@ietf.org>; Thu, 16 Feb 2023 13:36:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20210112.gappssmtp.com; s=20210112; t=1676583409; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=KPQqF4vpgytPVjLV2+tD53UCV1DHOqaYzeSdVSSULas=; b=N1c8jopYdSW7BhILHPNBOanrz6R0qs2XGIDBsfgjT8YXR/LHvPfRnbtONAmcw/LHhO lBNc0B5MQ1a7KbfPj1VEgRRaN+PFMSqUozZ+q1DOKQe4mVFoC2kLy7VBB6QX+e+LNNew ShURBNKUT16BOPlh64V+BxLnikVCO4WpcgzFJ4Su2G/ISv1FUsEhiFRNMApx7lKGlNIC Bq0H8chYysgFSLgeb+UJHmbH1dw2VljzNy0eRrbpkG/ZjagnJ2G6zqEq2xWVpGQp6qJE jCYA9l8fWNoXgQHtfwZeLsXONrTs08DDVN18fgqAK6lHcSPdAnJ7iP95SZHEiLA/S9kn EDVQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1676583409; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=KPQqF4vpgytPVjLV2+tD53UCV1DHOqaYzeSdVSSULas=; b=uUueyROxkVfK4PGLLT6HVA9RfmWPLZUHVTDhuULrRKr/kyy3JCwMZrDlOXIcnXUpBs 2+pXw4L70Vz7pImhD5OlJgThrAF0ey3wLSKExTCk6VDkBNhDu7AcGERJKlNGnzvwqhMZ TheaD7wQRQQ/OkpY6UZ7cjPqSgVMATstbFQvCF1YLGxhzfwmXR9gkP5BzYh/45AoPPNS lIp3SAZamLBigwzLUDNi6qSOnGxDeORvnsatYwTEO8LT5Mr0j4L69fXWFW+9jVV1ttVP kD7oWUtk70v7aMYQ/ootTD1Co91KteM8rCNCCgEAHWDuH1flTWIcahn42r2ku6NxPfFt hySQ==
X-Gm-Message-State: AO0yUKXmIQ7FOB6yM30CmoJbv7a1fEZCWJ2deFQAFNR656G+O07FHaul DMFSsMsrjfY11EJw9sQSJ4U6JjpFGIJ/8yTM4dSsuA==
X-Google-Smtp-Source: AK7set9YBES9qh+qPjah27n4fpXZEE78oYBlbsjf2PxHAFSvMZiD/dtCFgrTWVpnd6qgIyxyEQe+AH9GJGS2KFiTObs=
X-Received: by 2002:a0c:f2c4:0:b0:56e:adf1:171e with SMTP id c4-20020a0cf2c4000000b0056eadf1171emr590598qvm.44.1676583408741; Thu, 16 Feb 2023 13:36:48 -0800 (PST)
MIME-Version: 1.0
References: <e3a02b74-4eb7-6187-2c2c-061c6f4c0e41@bellis.me.uk> <C4751071-6795-4B53-82FB-601F74DFAF8D@gmail.com> <f4b19b59-11a1-5965-cd70-eb01ba4efc31@bellis.me.uk> <CACce4dRQBBZYz9a8thMYrCyqJTJb=h83neJS_1K6dfwz9sv9Zw@mail.gmail.com>
In-Reply-To: <CACce4dRQBBZYz9a8thMYrCyqJTJb=h83neJS_1K6dfwz9sv9Zw@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Thu, 16 Feb 2023 16:36:37 -0500
Message-ID: <CAPt1N1=XK8yrzXsJEseRd_5cX_Fpf7XuObdc1hJF8nsF7DoW0w@mail.gmail.com>
To: Abtin Keshavarzian <abtink=40google.com@dmarc.ietf.org>
Cc: Ray Bellis <ray@bellis.me.uk>, dnssd@ietf.org, tjw ietf <tjw.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="00000000000083c77605f4d7fe8f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/tQj-vbPVU6PxB8beAaezYecnE00>
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: Thu, 16 Feb 2023 21:36:54 -0000

Ray’s proposal to add an EDNS0 option for additional rrtypes would also
support this. However, the overhead would be slightly more.

Of course, we could really win big by defining a dns compression format for
6lowpan…. :)

On Thu, 16 Feb 2023 at 16:22, Abtin Keshavarzian <abtink=
40google.com@dmarc.ietf.org> wrote:

> Hi,
>
> I think the proposal is to fully prohibit "QDCOUNT > 1" and require
> resolvers to always reject such queries.
> Is my understanding correct?
>
> When there is ambiguity, it may be better to lean towards a more
> accommodating clarification.
>
> Ted mentioned the main use-case:
> - With Thread (and Matter) more small IoT embedded devices can act as
> client performing DNS-SD service resolution.
> - These can be battery powered and resource-constrained sensors (limited
> memory and computational power, low bandwidth and sleepy).
> - For service resolution, they need to get SRV and TXT records for a
> service instance name (most likely a local service).
>
> It would be good to allow resolvers to respond to queries containing
> questions for SRV and TXT for the same name.
> This can be optional (not required but also not disallowed) and/or limited
> to local names.
>
> Without this, we require multiple message exchanges (adding
> inefficiencies) on a less capable client device to accommodate a far more
> capable resolver.
> Is there any concern with this (that I may be missing)?
>
> Thanks,
> Abtin.
>
> On Thu, Feb 16, 2023 at 9:00 AM Ray Bellis <ray@bellis.me.uk> wrote:
>
>>
>>
>> On 16/02/2023 11:49, tjw ietf wrote:
>>
>> > This is a great idea Ray and the chairs look forward to your draft
>> submission
>>
>> Joe Abley and I are going to write the "QDCOUNT is 1, dammit!" draft.
>>
>> I've also just revivied draft-bellis-dnsext-multi-qtypes, but since
>> DNSEXT doesn't exist any more (boo!) I'm open to suggestions as to
>> whether the draft should go to DNSOP or DNSSD.
>>
>> Ray
>>
>> _______________________________________________
>> dnssd mailing list
>> dnssd@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnssd
>>
> _______________________________________________
> dnssd mailing list
> dnssd@ietf.org
> https://www.ietf.org/mailman/listinfo/dnssd
>

v2.23.0 | Report a Bug | By Email