[Cbor] Use and development of draft-faltstrom-base45 (was: Re: CBOR in QRcodes)

'Christian Amsüss' <christian@amsuess.com> Fri, 25 June 2021 09:10 UTC

Return-Path: <christian@amsuess.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 3E9FB3A0C2A for <cbor@ietfa.amsl.com>; Fri, 25 Jun 2021 02:10:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 453XuK6-78h3 for <cbor@ietfa.amsl.com>; Fri, 25 Jun 2021 02:10:16 -0700 (PDT)
Received: from prometheus.amsuess.com (prometheus.amsuess.com []) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4BEC3A0C29 for <cbor@ietf.org>; Fri, 25 Jun 2021 02:10:15 -0700 (PDT)
Received: from poseidon-mailhub.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bd]) by prometheus.amsuess.com (Postfix) with ESMTPS id 527B94001D; Fri, 25 Jun 2021 11:10:12 +0200 (CEST)
Received: from poseidon-mailbox.amsuess.com (hermes.amsuess.com []) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id 4839FD7; Fri, 25 Jun 2021 11:10:11 +0200 (CEST)
Received: from hephaistos.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:ceed:4926:c757:3c85]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id EAF8123; Fri, 25 Jun 2021 11:10:10 +0200 (CEST)
Received: (nullmailer pid 1354675 invoked by uid 1000); Fri, 25 Jun 2021 09:10:10 -0000
Date: Fri, 25 Jun 2021 11:10:10 +0200
From: 'Christian =?iso-8859-1?Q?Ams=FCss'?= <christian@amsuess.com>
To: Doug Ewell <doug@ewellic.org>
Cc: 'Michael Richardson' <mcr+ietf@sandelman.ca>, cbor@ietf.org
Message-ID: <YNWdchJRQRzm3I9j@hephaistos.amsuess.com>
References: <9704.1624378576@localhost> <YNN05Efh4/8Xyt63@hephaistos.amsuess.com> <000201d76914$53aa4890$fafed9b0$@ewellic.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="LcTnrqFkh3hCUUxG"
Content-Disposition: inline
In-Reply-To: <000201d76914$53aa4890$fafed9b0$@ewellic.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/uKGQ7WZDx6SPpcb7-kjOfNLs3ik>
Subject: [Cbor] Use and development of draft-faltstrom-base45 (was: Re: CBOR in QRcodes)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
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, 25 Jun 2021 09:10:20 -0000

Hello Doug,
(CC'ing the bse45 authors as the thread is moving there)

On Thu, Jun 24, 2021 at 10:16:43AM -0600, Doug Ewell wrote:
> > base45 (or some enhanced version thereof) does appear useful.
> I'm not sure what the bit in parentheses means. I'm thinking of the
> various "enhanced versions" of base32, base64, and base85, all of
> which are intended to solve some localized problem, and all of which
> add confusion and incompatibility to what should be a straightforward
> conversion. I hope this isn't a suggestion to do something similar to
> base45.

As I understand the base45 mechanism is very recent and not widespread
yet -- it has seen significant use in the digital health certificates
application (thread at [1]), but that was rolled out so fast that little
discussion was had given the time pressure the project is under what
they use is baked[2].

Outside the context of this, the draft has received no pertinent
discussion I could find[3], so I think it's more in the "there is a
draft and the mechanisms can be discussed" stage than in the "There is
an RFC that has become The Word" stage (in which any alterations might
become confusing).

Even if it were,

* given it is aimed at QR code readers but *still* gets trapped in some
  of the URI-but-not-really pitfalls,

* given that the proposed enhancements[4] would make it a base41, base42 or
  base43 and the use in combination with scheme-like dispatch there is
  little chance of confusion,

I think it'd be premature to call for a moratorium (as I'd understand
your comment).


(with my chair hat off, in case that needs clarification in this context)

[1]: https://mailarchive.ietf.org/arch/msg/cbor/M07MvOOyQlw-0P9i2GYYFd8hSbM/
[2]: https://github.com/ehn-dcc-development/hcert-spec/issues/64#issuecomment-861226115
[3]: https://mailarchive.ietf.org/arch/search/?q=faltstrom-base45
[4]: https://github.com/ehn-dcc-development/hcert-spec/issues/64#issuecomment-860974626

To use raw power is to make yourself infinitely vulnerable to greater powers.
  -- Bene Gesserit axiom