Re: [Cbor] Multiple questions with CBOR for DNS

Carsten Bormann <cabo@tzi.org> Fri, 10 November 2023 10:21 UTC

Return-Path: <cabo@tzi.org>
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 6FB43C17DC0B; Fri, 10 Nov 2023 02:21:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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] autolearn=ham autolearn_force=no
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 cNLLqiTF7fg8; Fri, 10 Nov 2023 02:21:24 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 5CEA5C17C526; Fri, 10 Nov 2023 02:20:48 -0800 (PST)
Received: from smtpclient.apple (eduroam-pool10-352.wlan.uni-bremen.de [134.102.91.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4SRZbK3bdtzDCdc; Fri, 10 Nov 2023 11:20:45 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.200.91.1.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <14fd34aa-b9f1-4449-9331-2082052aaba4@tu-dresden.de>
Date: Fri, 10 Nov 2023 11:20:33 +0100
Cc: Joe Hildebrand <hildjj@cursive.net>, 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: <AF01E59B-1487-4F3D-A3AE-E660101D4748@tzi.org>
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> <e48d9ae3b8634c3096d7430d57a7f7e1@msx-l317.msx.ad.zih.tu-dresden.de> <14fd34aa-b9f1-4449-9331-2082052aaba4@tu-dresden.de>
To: Martine Sophie Lenders <martine.lenders@tu-dresden.de>
X-Mailer: Apple Mail (2.3774.200.91.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/a5NEgD8Y2mB4R6mwXV0GqNrtOFY>
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: Fri, 10 Nov 2023 10:21:27 -0000

Well, if 65 % of all queries (number picked out of thin air) are single-question and AAAA, we are adding at least 0.65 bytes to the average question.
Exercise to the reader: How many tons of CO2 is that per year?

(I’m not saying we need to spring for every opportunity to save 0.65 bytes, but this one seems too easy to leave it.)

Grüße, Carsten


> On Nov 10, 2023, at 09:43, Martine Sophie Lenders <martine.lenders@tu-dresden.de> wrote:
> 
> If we make the type mandatory, it is not necessary to define it as `undefined` or `null`. Currently, it defaults to 28 (AAAA records), so if we make the type necessary it should be the according record type number. But that exactly should make clear, that we are not just adding a single byte but up to three, as the number space of record types is 1 to 65535.
> 
> That said, maybe it makes sense to make the type necessary. The AAAA record type was picked as a default based on what we see on the current Internet, where address resolution types (i.e. A and AAAA records) are the most prevalent, but that might change. Will look into that.