COSE "typ" (type) Header Parameter
draft-jones-cose-typ-header-parameter-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Michael B. Jones , Orie Steele | ||
| Last updated | 2023-08-04 | ||
| Replaced by | draft-ietf-cose-typ-header-parameter | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-cose-typ-header-parameter | |
| 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
This specification adds the equivalent of the JOSE typ (type) header parameter to COSE so that the benefits of explicit typing, as defined in the JSON Web Token Best Current Practices BCP, can be brought to COSE objects. The syntax of the COSE type header parameter value is the same as the existing COSE content type header parameter.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)