Re: [Dance] Encoding of the certificate
Michael Richardson <mcr+ietf@sandelman.ca> Wed, 08 February 2023 13:18 UTC
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: dance@ietfa.amsl.com
Delivered-To: dance@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63651C1516F3 for <dance@ietfa.amsl.com>; Wed, 8 Feb 2023 05:18:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 Ap-mLjcBqOWe for <dance@ietfa.amsl.com>; Wed, 8 Feb 2023 05:18:08 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (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 57A52C15154D for <dance@ietf.org>; Wed, 8 Feb 2023 05:18:08 -0800 (PST)
Received: from dyas.sandelman.ca (unknown [77.241.232.4]) by relay.sandelman.ca (Postfix) with ESMTPS id 75B881F47B; Wed, 8 Feb 2023 13:18:06 +0000 (UTC)
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id BFD0EA010F; Wed, 8 Feb 2023 08:18:05 -0500 (EST)
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id BD8F4A010E; Wed, 8 Feb 2023 14:18:05 +0100 (CET)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Stange, Wolf" <wolf-joergen.stange=40accenture.com@dmarc.ietf.org>, "dance@ietf.org" <dance@ietf.org>
In-reply-to: <SJ0P114MB1246C45019BA1E7318A4BAE2ACD89@SJ0P114MB1246.NAMP114.PROD.OUTLOOK.COM>
References: <SJ0P114MB1246C45019BA1E7318A4BAE2ACD89@SJ0P114MB1246.NAMP114.PROD.OUTLOOK.COM>
Comments: In-reply-to "Stange, Wolf" <wolf-joergen.stange=40accenture.com@dmarc.ietf.org> message dated "Wed, 08 Feb 2023 08:25:40 +0000."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Wed, 08 Feb 2023 14:18:05 +0100
Message-ID: <2499960.1675862285@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dance/U9aom6aIOdren4MPqTZCVEdmNco>
Subject: Re: [Dance] Encoding of the certificate
X-BeenThere: dance@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DANE Authentication for Network Clients Everywhere <dance.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dance>, <mailto:dance-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dance/>
List-Post: <mailto:dance@ietf.org>
List-Help: <mailto:dance-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dance>, <mailto:dance-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2023 13:18:09 -0000
Stange, Wolf <wolf-joergen.stange=40accenture.com@dmarc.ietf.org> wrote: > DANE is using Base16 (hex) for storing the certificate/subpubkey data > in the TLSA record - Have there been any thoughts about using base64 as > the encoding for the data, or even more compact encodings? No, that's not correct. RFC6698, section 2.1 _Wire Format_ defines that the content is binary. You are confusing that with 2.2, Presentation Format, which says to *present* the binary format as hext digits. That's only used in ascii zone files. Bind9, powerDNS, and others have proprietary formats for storing zones files in binary on disk. -- Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works -= IPv6 IoT consulting =-
- [Dance] Encoding of the certificate Stange, Wolf
- Re: [Dance] Encoding of the certificate Shreyas Zare
- Re: [Dance] Encoding of the certificate Michael Richardson
- Re: [Dance] Encoding of the certificate Rick van Rein