Re: [Dance] Encoding of the certificate
Rick van Rein <rick@openfortress.nl> Wed, 08 February 2023 16:14 UTC
Return-Path: <vanrein@vanrein.org>
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 7C644C1575A0 for <dance@ietfa.amsl.com>; Wed, 8 Feb 2023 08:14:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.666
X-Spam-Level:
X-Spam-Status: No, score=-0.666 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, PDS_RDNS_DYNAMIC_FP=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_DYNAMIC=0.982, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 XSEMR09Chhk4 for <dance@ietfa.amsl.com>; Wed, 8 Feb 2023 08:14:48 -0800 (PST)
Received: from fame.vanrein.org (2a02-58-157-9b00--7.ip6.tweak.nl [IPv6:2a02:58:157:9b00::7]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99658C151549 for <dance@ietf.org>; Wed, 8 Feb 2023 08:14:45 -0800 (PST)
Received: by fame.vanrein.org (Postfix, from userid 1000) id C7D9F2CB8E; Wed, 8 Feb 2023 16:14:40 +0000 (UTC)
Date: Wed, 08 Feb 2023 16:14:40 +0000
From: Rick van Rein <rick@openfortress.nl>
To: "Stange, Wolf" <wolf-joergen.stange=40accenture.com@dmarc.ietf.org>
Cc: "dance@ietf.org" <dance@ietf.org>
Message-ID: <20230208161440.GA2200@openfortress.nl>
Mail-Followup-To: "Stange, Wolf" <wolf-joergen.stange=40accenture.com@dmarc.ietf.org>, "dance@ietf.org" <dance@ietf.org>
References: <SJ0P114MB1246C45019BA1E7318A4BAE2ACD89@SJ0P114MB1246.NAMP114.PROD.OUTLOOK.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <SJ0P114MB1246C45019BA1E7318A4BAE2ACD89@SJ0P114MB1246.NAMP114.PROD.OUTLOOK.COM>
User-Agent: Mutt/1.5.20 (2009-06-14)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dance/uJH6ZbVytzpeOky-mZ-1chiKiGw>
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 16:14:52 -0000
Hi Wolf, > 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? On top of what the others said, there is a big advantage in hexdumps of certificates -- they are readable to the trained eye, unlike base64 which moves the bits in too various ways. (This may surprise you, but I can actually read DER dumps in hex.) So as long as it is a representation I'd say to leave it as hex! -Rick
- [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