[COSE] Re: Differences between COSE-HPKE and JOSE-HPKE
Brian Campbell <bcampbell@pingidentity.com> Mon, 22 September 2025 20:31 UTC
Return-Path: <bcampbell@pingidentity.com>
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 2E90E6704021 for <cose@mail2.ietf.org>; Mon, 22 Sep 2025 13:31:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=pingidentity.com
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 7sB7kug8hM_d for <cose@mail2.ietf.org>; Mon, 22 Sep 2025 13:30:59 -0700 (PDT)
Received: from mail-ua1-x933.google.com (mail-ua1-x933.google.com [IPv6:2607:f8b0:4864:20::933]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 336596704013 for <cose@ietf.org>; Mon, 22 Sep 2025 13:30:59 -0700 (PDT)
Received: by mail-ua1-x933.google.com with SMTP id a1e0cc1a2514c-9000129f2bcso893640241.2 for <cose@ietf.org>; Mon, 22 Sep 2025 13:30:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pingidentity.com; s=google; t=1758573058; x=1759177858; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=an0XWq/qOqDnqcUhJb6rXO6EP/dHyZMvpOfha+U8MzY=; b=CYb73UmBsL3RCi9D5Cq3/reCJGKvUkRmIz4ddTCaKd+QANUN2UTXE5LAMhDa1rSk+d kez4dPcHv8Lanhjbyfvmv5C2XEVPEabxKydLLN8tq7Dk411djmA6C5KQvDY3/ELSxRGD +wR6LT9boAJqPbEzPtxfuNM+DbC4gs2h5Zelg+LMC6Z9aE8jbMWuzfNjXRrT6B8jpqg4 u+y3Ez0mPgAHXREKxUEArlWQ7a+lQqYFrt3Y6pEUBCpU9GmVCv6b6uJB4RZ6nSEJZTAw HLPxt40EPXXa6ClcRT8773PH69OKNJWOKiRoaJn6nHq52N5+u9flC642sXyxN16TfqPg SxpQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1758573058; x=1759177858; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=an0XWq/qOqDnqcUhJb6rXO6EP/dHyZMvpOfha+U8MzY=; b=vdcA2W5TrvJ1HLIV8mvU81dcIYoX2pSCRcFXfSLUOylI1zWWJrR/a/7H8DIztyTYqf lQxyZbuxDtDOefkKmUHqQUluzoU3mhuKWa00pRVMtgHH8tD8cCHbkfxqZmT1FPEhIRVz YDy2mMjtG8ZQJ3HVsb1Al0TFIQ5Lby9MeOGhQgwb9rCWLfdBc4I2WhkRLxX3uZiq2PJS gNiPItZVv6OFnkL0R/jU1XNE8WNp10Y8eZF680wtAmapnhXyho1v3lPhzvyQkBPaDPmQ EedHY82Jnu/qyZzJ93q11And+LZgHdmJNNEfF2CBjYsNmt1xIjo11s+HFGRpZbKRpnhe D7UA==
X-Gm-Message-State: AOJu0Yyen59Jmv24OVY3fIXFPoC+qSh2M2qpnTiA2B/Kad3kVSrj2EKS xIxSS19nIJ5e7JGqA7aqGbU5gVuHX5w6d8KMLUoMhXAypIMUQSlTwtw+BCP+/v1sG6FiY74qPTn SOV/BYkeWVx0hAvjj8yPFcc8kgM5jmHwacXnrbHHehVOryXptk54Z0V47Hk+ooZLyBWCc3O7uPb 8yoa3JtiAeL0mRCrlQSh33DOLuS4lK
X-Gm-Gg: ASbGncszAbHSJaz6gRAyS4oCIauhug+taa5YkLC7KElFu94IrlpXEnSTTtM2ARpCeNS WNBwvf+Rxy66nT47G/7whl0JnpNg/sYT6A1wLhI9VtEk7JA9RZa3VVG8hA58MVzbTqJdv9pU+Aw egyqn9sPLalzZ+n8W1lP7Gvkkw6OYtnMjitSsh1ctArQe6PCWMzhQHoWCyHpE+FVHzPdBeJ1zji CIa02YZ
X-Google-Smtp-Source: AGHT+IEBx+ML1z17frulew6JmcTF9Olq6S8bOru7P4JiR469KBZyg1YZqMNcKMNo5OuI3eVcIuL++qp9AVm6JzlzdJI=
X-Received: by 2002:a05:6122:82a8:b0:542:d782:2522 with SMTP id 71dfb90a1353d-54bcb19409emr134882e0c.14.1758573058070; Mon, 22 Sep 2025 13:30:58 -0700 (PDT)
MIME-Version: 1.0
References: <trinity-17891aea-f80f-421a-84c2-ab8c164fc215-1750752463937@trinity-msg-rest-gmx-gmx-live-847b5f5c86-fxr46> <CA+k3eCS6BpBN_=AO0FKnKQU5nqSFf=GnELiwPKZz9L9FARQ2Rg@mail.gmail.com>
In-Reply-To: <CA+k3eCS6BpBN_=AO0FKnKQU5nqSFf=GnELiwPKZz9L9FARQ2Rg@mail.gmail.com>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Mon, 22 Sep 2025 14:30:32 -0600
X-Gm-Features: AS18NWAbr5CPDKhfpArQIOuV9oX6WY0M19YoOMb0AcHTd1boVGOsiQsyRYE7b2w
Message-ID: <CA+k3eCR4mFsAhgCQXN-YSb2Ln9pFr-iA7dRKC+YgOSia6+rj+w@mail.gmail.com>
To: Hannes Tschofenig <Hannes.Tschofenig=40gmx.net@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007047e0063f69b299"
Message-ID-Hash: JVSGO3FHD6B37KMNJS52BVXTQETVYMDA
X-Message-ID-Hash: JVSGO3FHD6B37KMNJS52BVXTQETVYMDA
X-MailFrom: bcampbell@pingidentity.com
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: cose@ietf.org, JOSE WG <jose@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [COSE] Re: Differences between COSE-HPKE and JOSE-HPKE
List-Id: CBOR Object Signing and Encryption <cose.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cose/zYgzF7kT4lxD2kaH8vaPiXJ_ULg>
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>
[adding the JOSE list as it seems relevant] On Wed, Jun 25, 2025 at 2:40 PM Brian Campbell <bcampbell@pingidentity.com> wrote: > > > On Tue, Jun 24, 2025 at 2:07 AM Hannes Tschofenig <Hannes.Tschofenig= > 40gmx.net@dmarc.ietf.org> wrote: > >> Hi all, >> >> the JOSE and COSE chairs have issued a working group last call on the two >> HPKE drafts. Most of the content has been aligned, as far as the structural >> differences between COSE and JOSE allow. >> >> However, there are some noteworthy differences between the two drafts: >> >> - The COSE-HPKE draft introduces a new CBOR structure called >> Recipient_structure, which is passed into the Additional Authenticated Data >> (AAD) field of the HPKE invocation. This structure contains the protected >> headers from the COSE_recipient (if present) as well as fixed fields, such >> as the algorithm used in the next layer. >> >> - The JOSE-HPKE draft does not define an equivalent structure. It >> basically leaves it up to a profile of the draft (or to the developer) to >> define the inforrmation it wants to incorporate. >> >> Both drafts support the inclusion of mutually known private information >> via the info field in HPKE. Additionally, each draft offers different >> extension points for passing additional data into the AAD and info fields. >> > > As mentioned in the PR on the JOSE-HPKE > <https://github.com/ietf-wg-jose/draft-ietf-jose-hpke-encrypt/pull/41> > draft, I don't think the way "mutually known private information" is used > is accurate or helpful to consumers of the document. I suspect that > similarly applies for the COSE-HPKE draft. > It looks like it did also apply to the COSE-HPKE draft and the problematic text has been removed in the recently published -16 revision https://author-tools.ietf.org/iddiff?url2=draft-ietf-cose-hpke-16 while it is still in JOSE-HPKE. I would suggest that this is an area (not having inaccurate/unhelpful content) where alignment would be beneficial. >> I believe further alignment between the two documents would be beneficial. >> > > Does sending this only to the COSE list imply that you think alignment > should come in the form of COSE moving towards JOSE? Or am I reading too > much into that? > Perhaps that read too much like a rhetorical question and it was foolish of me to expect a response. Rather than a question, this time I'll make the statement that alignment just for the sake of alignment shouldn't be a goal. For better or worse, JOSE and COSE diverged long ago. These drafts are not the place to try to fix that nor could they. -- _CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you have received this communication in error, please notify the sender immediately by e-mail and delete the message and any file attachments from your computer. Thank you._
- [COSE] Differences between COSE-HPKE and JOSE-HPKE Hannes Tschofenig
- [COSE] Re: Differences between COSE-HPKE and JOSE… Laurence Lundblade
- [COSE] Re: Differences between COSE-HPKE and JOSE… Brian Campbell
- [COSE] Re: Differences between COSE-HPKE and JOSE… Brian Campbell