IETF Logo Mail Archive

Re: [Cbor] Multiple questions with CBOR for DNS

Joe Hildebrand <hildjj@cursive.net> Thu, 09 November 2023 18:38 UTC

Return-Path: <hildjj@cursive.net>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18E30C1CAFF3 for <cbor@ietfa.amsl.com>; Thu, 9 Nov 2023 10:38:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 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_DNSWL_HI=-5, 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=cursive.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 rPb86GbQugC7 for <cbor@ietfa.amsl.com>; Thu, 9 Nov 2023 10:38:53 -0800 (PST)
Received: from mail-qt1-x82d.google.com (mail-qt1-x82d.google.com [IPv6:2607:f8b0:4864:20::82d]) (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 70CA7C1CAFF2 for <cbor@ietf.org>; Thu, 9 Nov 2023 10:38:53 -0800 (PST)
Received: by mail-qt1-x82d.google.com with SMTP id d75a77b69052e-41f155c862bso6720001cf.2 for <cbor@ietf.org>; Thu, 09 Nov 2023 10:38:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cursive.net; s=google; t=1699555132; x=1700159932; darn=ietf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=ZiQLeNYH4Qod7dJt98aVgEKtTYqZ9RRH4wR/Zb/iaGs=; b=OTqRR0KUdKXcUHqbliY2fK501vaqLgtvmzb4S22IP18RXsVvnBk8DJYfiLUMNXeQfw 3xifM/aPB+iIYuYoIje3tJfGVLYIw4RA83h1LyMDl9Bt0GUps/WM8wXHe7oH3WPRsf7g eMhZLHZw3NvO7JlHfP2yeDc/qfyDc/3oIC9Hw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699555132; x=1700159932; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=ZiQLeNYH4Qod7dJt98aVgEKtTYqZ9RRH4wR/Zb/iaGs=; b=w/RjJyFzVjV0pUayRd8uy5sp6tHjQsJDGynj7e0Uq7m5wSfMoxUqCV4+EuPP/uAZpv nhRJmk/zFxlGo7wSmj6BsRk7c2JUwAiRw7g1QNDZZN/4xwAhZUIOjUqvLo5Hua4pm425 USJwZdbZm4WR12trivgaxVJV6fqMZ6QoGTSgXzhTzFjiDKtQmx8Huhbm2LPO4GkRtf4z zLby43X3xNaMR6ACMfnw5GvsKiTbgsKfZBvRqdQ56bJweFzAm7DzwWRJirlb7pS0xJo3 YlWhKc1GQx3fta8tvyO1x7CHd+tcTYiCXDrS/ot89wZdk2pejqLPY6CooUn77MX9WUyK mYLQ==
X-Gm-Message-State: AOJu0Yw61LHyzdWWJ4RINGXsLuJL9EmmQzwy3pyqTTHwctwNOHUOERUe CEkXnmNkmxXW3P4QGO7+u4MLuA==
X-Google-Smtp-Source: AGHT+IEFuSxJ9BZLJZ1+rxdfBD3rObPrYxNSKjuWBG9MQPHskPsBkQXJ1P6e5CxaBYR4ifMOMlMLYA==
X-Received: by 2002:ac8:7d06:0:b0:41b:806e:81c7 with SMTP id g6-20020ac87d06000000b0041b806e81c7mr6627962qtb.32.1699555132129; Thu, 09 Nov 2023 10:38:52 -0800 (PST)
Received: from smtpclient.apple ([2601:282:2101:423e:8ca0:789b:670a:f856]) by smtp.gmail.com with ESMTPSA id g10-20020ac842ca000000b0041e9f3c3be8sm2147427qtm.23.2023.11.09.10.38.50 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Nov 2023 10:38:51 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.200.91.1.1\))
From: Joe Hildebrand <hildjj@cursive.net>
In-Reply-To: <4C5086F6-1B56-4428-B0B0-63DA4DFBA2BA@tzi.org>
Date: Thu, 09 Nov 2023 11:38:39 -0700
Cc: Martine Sophie Lenders <martine.lenders@tu-dresden.de>, Esko Dijk <esko.dijk@iotconsultancy.nl>, "cbor@ietf.org" <cbor@ietf.org>, "draft-lenders-dns-cbor.authors@ietf.org" <draft-lenders-dns-cbor.authors@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <8F998A0F-A9B9-4E6F-96E8-216B76A52E11@cursive.net>
References: <90f306d4-d887-43f6-8990-3c39a7ffcb46@tu-dresden.de> <DU0P190MB19784314798812652C9398CFFDAFA@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM> <c36a1e19d66c40009e0abe51f9c2bcf5@msx-l317.msx.ad.zih.tu-dresden.de> <66bc2b17-888b-440e-9eae-4ea2633f157d@tu-dresden.de> <d1191e0d356248ef83c413469e025d81@msx-l317.msx.ad.zih.tu-dresden.de> <83a63ff9-e36f-4e82-918b-4294570a6598@tu-dresden.de> <4C5086F6-1B56-4428-B0B0-63DA4DFBA2BA@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.3774.200.91.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/716TRUnimayK0RFeAMHBhzFQ3ZA>
Subject: Re: [Cbor] Multiple questions with CBOR for DNS
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Nov 2023 18:38:57 -0000

Wouldn't it be easier to make type-spec mandatory for all questions, and allow `undefined` or `null` (pick one) as the type-spec?  You're only adding a single byte.

— 
Joe Hildebrand

> On Nov 9, 2023, at 8:25 AM, Carsten Bormann <cabo@tzi.org> wrote:
> 
> How about:
> 
> question-section = [
>  * full-question, 
>  ? last-question
> ]
> 
>    full-question = (
>      name: domain-name,
>      type-spec,
>    )
> 
>    last-question = (
>      name: domain-name,
>      ? type-spec,
>    )
> 
> It is a bit hard in this form to maintain the requirement for at least one question, because if the last question is also a full question, it will be gobbled up by the `* question` part.
> (An intersection would work, but requires two parsing threads.)
> 
>> In the current draft, it is not, but if we go for the name component route, it will become hard to distinguish between the name for a second question or another component of the name for the first. Just necessitating at least a type in-between the names would help with that
> 
> Grüße, Carsten
> 
> _______________________________________________
> CBOR mailing list
> CBOR@ietf.org
> https://www.ietf.org/mailman/listinfo/cbor

v2.46.0 | Report a Bug | By Email | System Status