Concise Binary Object Representation (CBOR) Tag for Error Indications
draft-richter-cbor-error-tag-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Joerg Richter , Carsten Bormann | ||
| Last updated | 2019-08-03 (Latest revision 2019-01-30) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
The Concise Binary Object Representation (CBOR, RFC 7049) is a data format whose design goals include the possibility of extremely small code size, fairly small message size, and extensibility without the need for version negotiation. In CBOR, one point of extensibility is the definition of CBOR tags. While CBOR defines representations for null values and for an undefined value, there is no convention for expressing errors or exceptions in data structures, where the actual value desired could not be calculated due to an error. The present specification defines a tag for such error indications, enabling the addition of varying levels of detail.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)