draft-ietf-spice-sd-cwt-06

This specification describes a data minimization technique for use with CBOR Web Tokens (CWTs). The approach is based on the Selective Disclosure JSON Web Token (SD-JWT), with changes to align with CBOR Object Signing and Encryption (COSE) and CWTs.¶
This note is to be removed before publishing as an RFC.¶
The latest revision of this draft can be found at https://ietf-wg-spice.github.io/draft-ietf-spice-sd-cwt/draft-ietf-spice-sd-cwt.html. Status information for this document may be found at https://datatracker.ietf.org/doc/draft-ietf-spice-sd-cwt/.¶
Discussion of this document takes place on the Secure Patterns for Internet CrEdentials Working Group mailing list (mailto:spice@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/spice/. Subscribe at https://www.ietf.org/mailman/listinfo/spice/.¶
Source for this draft and an issue tracker can be found at https://github.com/ietf-wg-spice/draft-ietf-spice-sd-cwt.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 17 July 2026.¶
Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
1.1. High-Level Flow
3. Overview of Selective Disclosure CWT
3.1. A CWT without Selective Disclosure
3.2. Holder gets an SD-CWT from the Issuer
4. Holder prepares an SD-CWT for a Verifier
5. SD-CWT Definition
5.1. Types of Blinded Claims
6. Differences from the CBOR Web Token Specification
6.1. Definite Length CBOR Required
6.2. Finite values for standard date claims
6.3. Allowed types of CBOR map keys
6.4. Duplicate map key detection
6.5. Level of Nesting of Claims
6.6. Use of Structured Suffixes
7.1. Issuer Generation
7.2. Holder Validation
8. SD-CWT Presentation
8.1. Creating a Key Binding Token
9. SD-KBT and SD-CWT Verifier Validation
11. Tags Used Before SD-CWT Issuance
11.1. To Be Redacted Tag Definition
12. Encrypted Disclosures
12.1. AEAD Encrypted Disclosures Mechanism
13. Credential Types
14.1. Minimal Spanning Example
14.2. Nested Example
15. Privacy Considerations
15.4. Credential Types
16. Security Considerations