[COSE] Re: extending application/cose-x509
Carsten Bormann <cabo@tzi.org> Tue, 07 October 2025 05:21 UTC
Return-Path: <cabo@tzi.org>
X-Original-To: cose@mail2.ietf.org
Delivered-To: cose@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 74CE56E67C01 for <cose@mail2.ietf.org>; Mon, 6 Oct 2025 22:21:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -3.989
X-Spam-Level:
X-Spam-Status: No, score=-3.989 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=tzi.org
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8w-YU9nIX5vh for <cose@mail2.ietf.org>; Mon, 6 Oct 2025 22:21:43 -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 ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 90A466E67BF5 for <cose@ietf.org>; Mon, 6 Oct 2025 22:21:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=tzi.org; s=2019; t=1759814495; bh=FAU5TxjqI+FFZLa52Q4OOm9avTi+o3xyCH4DIlax2xo=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=TJS6QL+/tf89PHDafcW+xpjxhv8H5uA3kEGYGxVX0BOpdKhpL9t766PpqW1dMENzf BXx5lRMMb7zs1Un+UEqNyzlDXqrLwiwELcpXTNjGfjnL15cnuEIL51obs1Ux3CMprs NnjyTRZaA2kLvD+7D/73EDRasppFDkUGtGyj8Ui+Fz8iLgzJwmje7Kn/xcDtNLwWN/ aKk5qfD2lKmw+0f13xyk9R29w39I0kxgh8xvIa6TmsdKdNdaBCudvyQm6aYKCksrUi 4pIuoavFFIOkIwCEScpBxDk0OQHmopau3Vcqr21bBiEQ3dzBGdHAxO8QoRvKTyJuwv PRIcqZ3j9A+sg==
Received: from smtpclient.apple (p5dc5df6f.dip0.t-ipconnect.de [93.197.223.111]) (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 4cgkyR1z81zDCbn; Tue, 7 Oct 2025 07:21:35 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CA+1=6yfDfWefi6JWNmPXrYMC5=CCnPcvZLHx_aMPt2qvf9CEgg@mail.gmail.com>
Date: Tue, 07 Oct 2025 07:21:14 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <0E5CAEF4-D82C-43EA-BBAC-C5F687BB3E86@tzi.org>
References: <CA+1=6ydHCGoDoUXS2ayHJ-TV2TXZex-Sw+e-Hb=oZ=4FgJWCvg@mail.gmail.com> <16285.1759508921@obiwan.sandelman.ca> <CA+1=6yc_eYwBizMpNP3WBCDYFN=SNMuEn8bErhrSsNOLXWtVjg@mail.gmail.com> <CA+1=6yfDfWefi6JWNmPXrYMC5=CCnPcvZLHx_aMPt2qvf9CEgg@mail.gmail.com>
To: "thomas.fossati@linaro.org" <thomas.fossati@linaro.org>
X-Mailer: Apple Mail (2.3826.700.81)
X-FromAuthMilter: ok
Message-ID-Hash: TVMAMZXXJX6QXNZXSP3VZ6IU7VDWXD54
X-Message-ID-Hash: TVMAMZXXJX6QXNZXSP3VZ6IU7VDWXD54
X-MailFrom: cabo@tzi.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-cose.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Michael Richardson <mcr+ietf@sandelman.ca>, cose <cose@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [COSE] Re: extending application/cose-x509
List-Id: CBOR Object Signing and Encryption <cose.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cose/j-HvjcHaz2LR35kWVCX0Lu1tbHc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cose>
List-Help: <mailto:cose-request@ietf.org?subject=help>
List-Owner: <mailto:cose-owner@ietf.org>
List-Post: <mailto:cose@ietf.org>
List-Subscribe: <mailto:cose-join@ietf.org>
List-Unsubscribe: <mailto:cose-leave@ietf.org>
On Oct 6, 2025, at 15:35, Thomas Fossati <thomas.fossati@linaro.org> wrote:
>
> So, given the ambiguity surrounding the encoding of COSE_X509
Can you explain the “ambiguity”?
So far, nothing restricts the encoding, so any well-formed CBOR can be used.
Is there a reason to want this to be different?
If you are talking about Section 9 of RFC 9052, please read again:
9. CBOR Encoding Restrictions
This document limits the restrictions it imposes on how the CBOR
Encoder needs to work. The new encoding restrictions are aligned
with the Core Deterministic Encoding Requirements specified in
Section 4.2.1 of RFC 8949 [STD94]. It has been narrowed down to the
following restrictions:
* The restriction applies to the encoding of the Sig_structure, the
Enc_structure, and the MAC_structure.
* (...The actual restrictions...)
The three structures are used for creating signing inputs, not for any data that goes over the wire.
Grüße, Carsten
- [COSE] extending application/cose-x509 Thomas Fossati
- [COSE] Re: extending application/cose-x509 Michael Richardson
- [COSE] Re: extending application/cose-x509 Thomas Fossati
- [COSE] Re: extending application/cose-x509 Thomas Fossati
- [COSE] Re: extending application/cose-x509 Michael Richardson
- [COSE] Re: extending application/cose-x509 Thomas Fossati
- [COSE] Re: extending application/cose-x509 Michael Richardson
- [COSE] Re: extending application/cose-x509 Thomas Fossati
- [COSE] Re: [Rats] extending application/cose-x509 Carsten Bormann
- [COSE] Re: [Rats] extending application/cose-x509 Thomas Fossati
- [COSE] Re: [Rats] extending application/cose-x509 Carsten Bormann
- [COSE] Re: [Rats] extending application/cose-x509 Thomas Fossati
- [COSE] Re: extending application/cose-x509 Carsten Bormann
- [COSE] Re: extending application/cose-x509 Thomas Fossati
- [COSE] Re: extending application/cose-x509 Carsten Bormann
- [COSE] Re: extending application/cose-x509 Thomas Fossati
- [COSE] Re: extending application/cose-x509 Carsten Bormann
- [COSE] Re: extending application/cose-x509 Thomas Fossati
- [COSE] Re: extending application/cose-x509 Michael Richardson
- [COSE] Re: extending application/cose-x509 Carsten Bormann
- [COSE] Re: extending application/cose-x509 Thomas Fossati
- [COSE] Re: extending application/cose-x509 John Mattsson
- [COSE] Re: extending application/cose-x509 Michael Richardson
- [COSE] Re: extending application/cose-x509 Carsten Bormann