Skip to main content

CBOR Web Token (CWT)
RFC 8392

Revision differences

Document history

Date By Action
2019-04-29
(System) Received changes through RFC Editor sync (added Errata tag)
2018-05-10
(System) IANA registries were updated to include RFC8392
2018-05-08
(System)
Received changes through RFC Editor sync (created alias RFC 8392, changed abstract to 'CBOR Web Token (CWT) is a compact means of representing claims …
Received changes through RFC Editor sync (created alias RFC 8392, changed abstract to 'CBOR Web Token (CWT) is a compact means of representing claims to be transferred between two parties.  The claims in a CWT are encoded in the Concise Binary Object Representation (CBOR), and CBOR Object Signing and Encryption (COSE) is used for added application-layer security protection.  A claim is a piece of information asserted about a subject and is represented as a name/value pair consisting of a claim name and a claim value.  CWT is derived from JSON Web Token (JWT) but uses CBOR rather than JSON.', changed pages to 25, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2018-05-08, changed IESG state to RFC Published)
2018-05-08
(System) RFC published