Application-Oriented Literals in CBOR Extended Diagnostic Notation
draft-bormann-cbor-edn-literals-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Author | Carsten Bormann | ||
| Last updated | 2022-04-09 (Latest revision 2021-10-06) | ||
| Replaced by | draft-ietf-cbor-edn-literals, draft-ietf-cbor-edn-literals, draft-ietf-cbor-edn-literals | ||
| RFC stream | (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 8949) defines a "diagnostic notation" in order to be able to converse about CBOR data items without having to resort to binary data. This document specifies how to add application-oriented extensions to the diagnostic notation. It then defines two such extensions for the use of CBOR diagnostic notation with CoRAL and Constrained Resource Identifiers (draft-ietf-core-coral, draft-ietf-core-href).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)