Guidance for COSE and JOSE Protocol Designers and Implementers
draft-tschofenig-jose-cose-guidance-01
| Document | Type |
Expired Internet-Draft
(candidate for jose WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Hannes Tschofenig , Les Hazlewood , Yaron Sheffer | ||
| Last updated | 2025-01-09 (Latest revision 2024-07-08) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Call For Adoption By WG Issued | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE) are two widely used security wrappers, which have been developed in the IETF and have intentionally been kept in sync. This document provides guidance for protocol designers developing extensions for JOSE/COSE and for implementers of JOSE/COSE libraries. Developers of application using JSON and/or JOSE should also read this document but are realistically more focused on the documentation offered by the library they are using.
Authors
Hannes Tschofenig
Les Hazlewood
Yaron Sheffer
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)