Re: [Cbor] Reviews and shepherd for draft-ietf-cbor-cddl-more-control

Carsten Bormann <cabo@tzi.org> Sat, 13 April 2024 13:36 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 68763C14F61A; Sat, 13 Apr 2024 06:36:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.886
X-Spam-Level:
X-Spam-Status: No, score=-6.886 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, T_SPF_TEMPERROR=0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 SVg4TPOpDWnF; Sat, 13 Apr 2024 06:36:40 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::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 CA85EC14F60E; Sat, 13 Apr 2024 06:36:37 -0700 (PDT)
Received: from eduroam-pool10-144.wlan.uni-bremen.de (eduroam-pool10-144.wlan.uni-bremen.de [134.102.90.143]) (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 4VGvbl1cJHzDCdQ; Sat, 13 Apr 2024 15:36:35 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <824851A4-BB83-400A-BBBE-2BFA5E6A4D60@tzi.org>
Date: Sat, 13 Apr 2024 15:36:34 +0200
Cc: Christian Amsüss <christian@amsuess.com>, "cbor@ietf.org" <cbor@ietf.org>, "draft-ietf-cbor-cddl-more-control@ietf.org" <draft-ietf-cbor-cddl-more-control@ietf.org>
X-Mao-Original-Outgoing-Id: 734708194.421315-551276f970334738372f2003b6a9e49d
Content-Transfer-Encoding: quoted-printable
Message-Id: <3F4D3A40-B55D-4625-8684-09915B13B036@tzi.org>
References: <ZeMG7tpfKLyf3aSz@hephaistos.amsuess.com> <ZhPIC9DyzcpyhjPI@hephaistos.amsuess.com> <3FECD79D-C19A-4F04-BF04-A39AC4962C2D@island-resort.com> <31FEFB97-87CD-4B6D-86A7-06CBE12D51E8@tzi.org> <EF87DF03-8483-45DD-AA80-8E885BB78F75@island-resort.com> <824851A4-BB83-400A-BBBE-2BFA5E6A4D60@tzi.org>
To: "lgl island-resort.com" <lgl@island-resort.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/WJoyDFhIPPfQhLbMovQoya6Honw>
Subject: Re: [Cbor] Reviews and shepherd for draft-ietf-cbor-cddl-more-control
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: Sat, 13 Apr 2024 13:36:46 -0000

On 2024-04-11, at 15:27, Carsten Bormann <cabo@tzi.org> wrote:
> 
> JWT-JWS = text .join ([
>             b64u<jwt-headers>, ".",
>             b64u<jwt-payload>, ".",
>             b64u<jwt-signature>])
> b64u<B> = text .b64u B
> jwt-headers = text .json jwt-headermap
> jwt-headermap = { * text => any } ; simplified
> jwt-payload = bytes
> jwt-signature = bytes

This proposal didn’t address the fact that .json describes a text string, but b64u<B> requires bytes.  Better:

JWT-JWS = text .join ([
             b64u<jwt-headers>, ".",
             b64u<jwt-payload>, ".",
             b64u<jwt-signature>])
b64u<B> = text .b64u B

jwt-headers = '' .cat jwt-headers1
jwt-headers1 = text .json jwt-headermap
jwt-headermap = { * text => any } ; simplified

jwt-payload = bytes
jwt-signature = bytes

(This uses .cat as a conversion method between bytes and text, please see [1].)

This could be beautified some more, but does show the principle.

Grüße, Carsten

[1]: https://www.rfc-editor.org/rfc/rfc9165.html#section-2.2-2