You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: "Bormann, C., \"PoC of the McNally/Allen dCBOR application-level CBOR representation rules\""
70
+
author:
71
+
name: Carsten Bormann
72
+
title: "PoC of the McNally/Allen dCBOR application-level CBOR representation rules"
66
73
target: https://github.com/cabo/cbor-dcbor
67
74
68
75
--- abstract
@@ -110,7 +117,7 @@ CBOR {{-CBOR}} defines maps with duplicate keys as invalid, but leaves how to ha
110
117
111
118
dCBOR encoders:
112
119
113
-
1. MUST NOT emit CBOR maps that contains duplicate keys.
120
+
1. MUST NOT emit CBOR maps that contain duplicate keys.
114
121
115
122
dCBOR decoders:
116
123
@@ -146,7 +153,7 @@ This also means that the three representations of a zero number in CBOR (`0`, `0
146
153
147
154
Note that this reduction means some valid CDE/CBOR maps are not valid dCBOR maps, as numeric reduction can result in duplicate keys, for example, this is an invalid dCBOR map:
148
155
149
-
~~~
156
+
~~~ cbor-diag
150
157
{
151
158
10: "ten",
152
159
10.0: "floating ten"
@@ -182,29 +189,21 @@ The control operators `.dcbor` and `.dcborseq` are exactly like `.cde` and `.cde
182
189
183
190
For example, the normative comment in Section 3 of {{GordianEnvelope}}:
184
191
185
-
~~~
192
+
~~~ cddl
186
193
leaf = #6.24(bytes) ; MUST be dCBOR
187
194
~~~
188
195
189
196
...can now be formalized as:
190
197
191
-
~~~
198
+
~~~ cddl
192
199
leaf = #6.24(bytes .dcbor any)
193
200
~~~
194
201
195
-
# Reference Implementations
196
-
197
-
This section is to be removed before publishing as an RFC.
198
-
199
-
(Boilerplate as per Section 2.1 of {{RFC7942}}:)
200
-
201
-
This section records the status of known implementations of the protocol defined by this specification at the time of posting of this Internet-Draft, and is based on a proposal described in {{RFC7942}}. The description of implementations in this section is intended to assist the IETF in its decision processes in progressing drafts to RFCs. Please note that the listing of any individual implementation here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors. This is not intended as, and must not be construed to be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist.
202
-
203
-
According to {{RFC7942}}, "this will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. It is up to the individual working groups to use this information as they see fit".
204
-
205
-
## Gordian dCBOR Application Profile
202
+
# Implementation Status
203
+
{:removeinrfc}
204
+
{::boilerplate rfc7942info}
206
205
207
-
### Swift
206
+
## Swift
208
207
209
208
- Description: Single-purpose dCBOR reference implementation for Swift.
210
209
- Organization: Blockchain Commons
@@ -215,7 +214,7 @@ According to {{RFC7942}}, "this will allow reviewers and working groups to assig
215
214
- Testing: Unit tests
216
215
- Licensing: BSD-2-Clause-Patent
217
216
218
-
### Rust
217
+
## Rust
219
218
220
219
- Description: Single-purpose dCBOR reference implementation for Rust.
221
220
- Organization: Blockchain Commons
@@ -226,7 +225,7 @@ According to {{RFC7942}}, "this will allow reviewers and working groups to assig
226
225
- Testing: Unit tests
227
226
- Licensing: BSD-2-Clause-Patent
228
227
229
-
### TypeScript
228
+
## TypeScript
230
229
231
230
- Description: Single-purpose dCBOR reference implementation for TypeScript.
232
231
- Organization: Blockchain Commons
@@ -237,7 +236,7 @@ According to {{RFC7942}}, "this will allow reviewers and working groups to assig
237
236
- Testing: Unit tests
238
237
- Licensing: BSD-2-Clause-Patent
239
238
240
-
### Ruby
239
+
## Ruby
241
240
242
241
- Implementation Location: [cbor-dcbor]
243
242
- Primary Maintainer: Carsten Bormann
@@ -262,6 +261,7 @@ This document requests IANA to register the contents of Table 1 into the registr
0 commit comments