[jose] I-D Action: draft-ietf-jose-json-proof-token-14.txt

internet-drafts@ietf.org Mon, 20 July 2026 21:03 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: jose@ietf.org
Delivered-To: jose@mail2.ietf.org
Received: from [10.244.22.187] (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 1F9E411AC8E76; Mon, 20 Jul 2026 14:03:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1784581406; bh=qrRW4ew8geyXshZ7OEuGyqirb1+cNmQxwtAQgad/VmI=; h=From:To:Cc:Subject:Reply-To:Date; b=bCDkLKfMkfOQm7lXf++u/Qpj6/S0v3GOz7ZJHiecNbMrdFrGKFRnKXqsD1seZkYYs DPAqKD5cOL8VS/xIWp+BFQE3kEj29BrY8J0iN88O3Q/QFQZbQig8J4qsdGpMtWh13h hyWDcWhu7r0i+0NAg1e36i0dUPF5kmSsEc6gfjYY=
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.69.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <178458140591.192235.18072155520951849497@dt-datatracker-d4d6ff9d9-ql5mb>
Date: Mon, 20 Jul 2026 14:03:25 -0700
Message-ID-Hash: RCQA4FJGFV56KDRPG5XXCAOYBBXPICFY
X-Message-ID-Hash: RCQA4FJGFV56KDRPG5XXCAOYBBXPICFY
X-MailFrom: internet-drafts@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-jose.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: jose@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: jose@ietf.org
Subject: [jose] I-D Action: draft-ietf-jose-json-proof-token-14.txt
List-Id: Javascript Object Signing and Encryption <jose.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/jose/5xovL9_28TOJRT-u7A7xmfb0DP0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jose>
List-Help: <mailto:jose-request@ietf.org?subject=help>
List-Owner: <mailto:jose-owner@ietf.org>
List-Post: <mailto:jose@ietf.org>
List-Subscribe: <mailto:jose-join@ietf.org>
List-Unsubscribe: <mailto:jose-leave@ietf.org>

Internet-Draft draft-ietf-jose-json-proof-token-14.txt is now available. It is
a work item of the Javascript Object Signing and Encryption (JOSE) WG of the
IETF.

   Title:   JSON Proof Token and CBOR Proof Token
   Authors: Michael B. Jones
            David Waite
            Jeremie Miller
   Name:    draft-ietf-jose-json-proof-token-14.txt
   Pages:   15
   Dates:   2026-07-20

Abstract:

   JSON Proof Token (JPT) is a compact, URL-safe, privacy-preserving
   representation of claims to be transferred between three parties.
   The claims in a JPT are encoded as base64url-encoded JSON objects
   that are used as the payloads of a JSON Web Proof (JWP) structure,
   enabling them to be digitally signed and selectively disclosed.  JPTs
   also support reusability and unlinkability when using Zero-Knowledge
   Proofs (ZKPs).

   A CBOR-based representation of JPTs is also defined, called a CBOR
   Proof Token (CPT).  It has the same properties as JPTs, but uses the
   JSON Web Proof (JWP) CBOR Serialization, rather than the JSON-based
   JWP Compact Serialization.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-jose-json-proof-token/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-jose-json-proof-token-14.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-jose-json-proof-token-14

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts