Re: [dnssd] Draft: A DNS Query including A Main Question with Accompanying Questions

Tim Wicinski <tjw.ietf@gmail.com> Sun, 19 November 2023 21:42 UTC

Return-Path: <tjw.ietf@gmail.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 A921EC14F74A for <dnssd@ietfa.amsl.com>; Sun, 19 Nov 2023 13:42:59 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 (2048-bit key) header.d=gmail.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 8mJrc3yc_Wzx for <dnssd@ietfa.amsl.com>; Sun, 19 Nov 2023 13:42:59 -0800 (PST)
Received: from mail-ej1-x62e.google.com (mail-ej1-x62e.google.com [IPv6:2a00:1450:4864:20::62e]) (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 12369C14F749 for <dnssd@ietf.org>; Sun, 19 Nov 2023 13:42:54 -0800 (PST)
Received: by mail-ej1-x62e.google.com with SMTP id a640c23a62f3a-9e4675c7a5fso502588466b.0 for <dnssd@ietf.org>; Sun, 19 Nov 2023 13:42:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700430172; x=1701034972; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=q+AKQI7nEgi18Njkfybxj3CD9tH9a8KoFN1x2VIhq8g=; b=RTjQCo8CKPNSnRCfKTLscxo0Q8jxe0UANDnPprZD+iOf4lLAGhw2yJ0YSs/xt+5RM6 XJeDmCy4SY+urPj08UsmtToTfBOb9AnpiOiymmheJ8BQ9tiZbC14Q4BNaiNrWCxNIhh7 DHRwxMigWe3URROVQCn9KWl1nHAHqi/aWO28uNYCvYVZAobxjziiFW0YDepglQEQtY9X +EV9O7t+buux076bR/l28OYi817VKsVQjVyC/CW3Hmkhx8PC5Jg7OYUCLTIyko11oUnX EERqjTW4hzAMa/yrh4M9VACygZX4iCkLSp1bdhJAGCOQMfaQwYl42ROngAnCmsSVYKcc 4v1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700430172; x=1701034972; 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=q+AKQI7nEgi18Njkfybxj3CD9tH9a8KoFN1x2VIhq8g=; b=ScigH+BUkAARdwUZKT0KWyDHbWlLgh55TGqsYvVBA3wOYt509J+6jXMMKM9Ywhihcn j3YbVN9UbfVPzkLyUBhqsaxzDwyQHc98sKOCE1nu/mPOaK6Bm0CO9unqa22CjNvo5YsS 26Am0MHrS4ToV5OfYX8nn4IJswIq3IKqhmUs5X6XG1bCn3f3qF2TWprp9UMCK5treacE pwwUx/17yVJ9+UYj/2/iwYDjRN/fp8bEO2vngAuytKfYaDcE4kLPnkkvHWoaPBa3AGpW ugswx+zWQoagcHTGlePqZp1byrnEBhs7+pEotI01QC4AAiyCYPeYIh14f6K1dVqvrbFh z5Ig==
X-Gm-Message-State: AOJu0Yx5fWm5UyekcJqZ2cAm62AhAPsFwGK7uIEl47D1h1iwZZWe5+w1 gwdjFtPPIUZOtQvbWHF549BXBDkZN3efVBv9hy4=
X-Google-Smtp-Source: AGHT+IEtRM1RyK2pFoFcT59Pt32XBcm8VP4Zjgy4LKjh+bu833eRL0J7Wa+rsYnVYvI+86rRAY+BQRUEcTNbj2ofUqg=
X-Received: by 2002:a17:907:9486:b0:9c4:6893:ccc5 with SMTP id dm6-20020a170907948600b009c46893ccc5mr4899043ejc.57.1700430171657; Sun, 19 Nov 2023 13:42:51 -0800 (PST)
MIME-Version: 1.0
References: <64F542A2-B228-4AC5-84D1-F8F1DAFEAD4E@cnnic.cn> <CAPt1N1mRAYtvJE4f5grReTaJugdfzuJy0oMfYL5La2smO7_x1g@mail.gmail.com> <4764F1C3-AB8B-4367-B865-6331B626789B@cnnic.cn> <CAPt1N1=LYMUeQUnG=jLAg0Zfis4uYxchS-LVmXKPgV2KH3SxWw@mail.gmail.com>
In-Reply-To: <CAPt1N1=LYMUeQUnG=jLAg0Zfis4uYxchS-LVmXKPgV2KH3SxWw@mail.gmail.com>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Sun, 19 Nov 2023 16:42:40 -0500
Message-ID: <CADyWQ+F+dWhfmUaRAMrrhLGvBY+b3kNc7_B-1gFONE06+LuCZw@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
Cc: Jiankang Yao <yaojk@cnnic.cn>, dnssd@ietf.org
Content-Type: multipart/alternative; boundary="00000000000058da7e060a8840a6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/W_nV1vcZi-32UxCHfxXt301IJB0>
Subject: Re: [dnssd] Draft: A DNS Query including A Main Question with Accompanying Questions
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: Sun, 19 Nov 2023 21:42:59 -0000

I remember this was presented back at IETF96/IETF97 in DNSOP (had to
refresh my memory).

The feedback at the time was it was hard to implement and to use; lacked
any security considerations; and involved changing resolver behavior.
The last one is the most important - it's one thing to add to RR Types that
require no extra processing; EDNS options are a bit work, but changing
resolver behavior has a very long tail in the DNS world.

(We keep the DNSOP materials back to IETF96 in github
https://github.com/ietf-wg-dnsop/wg-materials for those interested.)

I'd like to see implementations or attempted implementations myself.

tim


On Sun, Nov 19, 2023 at 10:20 AM Ted Lemon <mellon@fugue.com> wrote:

> Is anyone thinking of implementing something like your tlsa example?
> What’s the use case?
>
> Op zo 19 nov 2023 om 10:15 schreef Jiankang Yao <yaojk@cnnic.cn>
>
>> I think that this design can cover more use cases.
>>
>> For example:
>>
>> Case 1) Muti-types for the same name:
>>   – Query example.com for A and AAAA
>> When asking about a QTYPE=A RRset, a QTYPE=AAAA RRset may also
>> be of use [RFC 5321];
>>
>> Case 2)Muti-types for the same name and its sub-name:
>> – Query www.example.com for A and AAAA, and _443._tcp.www.example.com
>> for TLSA
>> When asking for some RRset of www.example.com about A and AAAA, records
>> of a sub-domain name such as _443._tcp.www.example.com
>> for TLSA may be of interest[RFC 6698].
>>
>>
>> Best Regards
>> Jiankang Yao
>>
>>
>> 2023年11月19日 下午10:09,Ted Lemon <mellon@fugue.com> 写道:
>>
>> This seems quite a bit more complicated than the document that’s been
>> proposed for adoption in dnssd. Is there some benefit to this added
>> complexity?
>>
>> Op za 18 nov 2023 om 23:21 schreef Jiankang Yao <yaojk@cnnic.cn>
>>
>>> Hi all,
>>>
>>>
>>> I have a draft submitted several years ago.
>>>
>>> “
>>>
>>>    This document enables DNS initiators to send a main question
>>>    accompanying with several related questions in a single DNS query,
>>>    and enables DNS responders to put the answers into a single DNS
>>>    response.
>>>
>>> "
>>>
>>>
>>> https://www.ietf.org/archive/id/draft-yao-dnsop-accompanying-questions-04.txt
>>>
>>>
>>> If the WG  has some interests in this document, I would like to continue
>>> to improve it.
>>>
>>>
>>> Best Regards
>>> Jiankang Yao
>>> _______________________________________________
>>> 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
>>
>>
>> _______________________________________________
> dnssd mailing list
> dnssd@ietf.org
> https://www.ietf.org/mailman/listinfo/dnssd
>