cbor-wg CBORbis issues - Githubissues

cbor-wg / CBORbis

The draft leading up to RFC8949

https://www.rfc-editor.org/rfc/rfc8949.html

Other

5 stars 12 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Not clear if nested tag needed when bignum used as mantissa in decimal and bigfloat encodings

#227 ecorm closed 2 years ago
1
IEEE quad floats in typed arrays, but not as single values

#226 ecorm opened 3 years ago
2
diff-review

#225 cabo closed 3 years ago
0
Edits from paul

#224 paulehoffman closed 3 years ago
0
Clean up start of 3.2.3 (indefinite-length strings)

#223 cabo closed 4 years ago
0
Nits in -15

#222 cabo closed 4 years ago
1
Attempt CI fix

#221 cabo closed 4 years ago
0
Remove things that would be removed later

#220 paulehoffman closed 4 years ago
0
Close #209

#219 cabo closed 4 years ago
0
Alternative to #205 to close #204.

#218 cabo closed 4 years ago
0
Éric comments

#217 paulehoffman closed 4 years ago
0
Rob comments

#216 cabo closed 4 years ago
0
Changes from Erik Kline's review

#215 paulehoffman closed 4 years ago
0
Addition from Roman's ballot

#214 paulehoffman closed 4 years ago
0
Ben comments

#213 paulehoffman closed 4 years ago
0
Address remaining DISCUSS items from Ben

#212 cabo closed 4 years ago
0
nits: Get rid of remaining typewriter dashes

#211 cabo closed 4 years ago
0
Proposal for handling tag 35 in 7049bis

#210 cabo closed 4 years ago
1
Need to update Appendix G (Changes from RFC 7049)

#209 cabo closed 4 years ago
0
Changes to pseudocode and related statements (via Ben Kaduk)

#208 cabo closed 4 years ago
0
Remove "of" fromm "major type of" an "additional information of" for consistency

#207 paulehoffman closed 4 years ago
0
Editorial improvements noted during IESG Evaluation

#206 kaduk closed 4 years ago
4
Diagnostic notation: 5FFF/7FFF and NaN payloads

#205 ciphergoth closed 4 years ago
8
Diagnostic format should be a surjection onto valid CBOR bytes

#204 ciphergoth closed 4 years ago
7
Address Stuart Cheshire's comments of 2020-07-06

#203 cabo closed 4 years ago
1
Move "changes" appendix to G, turn into narrative form, make it more …

#202 cabo closed 4 years ago
0
Consistent usage of »"break" stop code«

#201 cabo closed 4 years ago
1
Be abundantly clear that tag 24 encodes a single CBOR data item

#200 cabo closed 4 years ago
0
Update needed for Appendix F, Changes from RFC 7049

#199 cabo closed 4 years ago
0
55799 applicability

#198 cabo closed 4 years ago
0
Revert the domain expansion to tags 33 and 34 that happened in #18

#197 cabo closed 4 years ago
0
Section 7.1 and IANA considerations.

#196 cabo closed 4 years ago
0
Some minimal cleanup of section 5.2, close #189

#195 cabo closed 4 years ago
0
content of base64 tag

#194 laurencelundblade closed 4 years ago
0
Reword the sentence about serialization variants.

#193 jyasskin closed 4 years ago
0
"Character"->"code point" when talking about UTF-8 validity.

#192 jyasskin closed 4 years ago
0
Cite the potentially-confusing phrase "well-formed but invalid".

#191 jyasskin closed 4 years ago
1
Nit: Liberate reference to Section 5.6 in 5.3.1.

#190 cabo closed 4 years ago
0
Clean up 5.2 for less redundancy

#189 cabo closed 4 years ago
0
Nit: Fix terminology about "Data Stream", add one more 8742 reference.

#188 cabo closed 4 years ago
0
Under extensibility (7.1), be more direct about how to handle unknown tags

#187 cabo closed 4 years ago
0
Restate that simple values only have a single representation variant

#186 cabo closed 4 years ago
0
Close #184 (idnits)

#185 cabo closed 4 years ago
0
Editorial - idnits

#184 fpalombini closed 4 years ago
1
clarify if tag 55799 is always ignored (cannot cause error), sometimes ignored (can cause error), or either way

#183 x448 closed 4 years ago
4
rfc7049bis recommends unrecognized tags cause an error

#182 mcr closed 4 years ago
2
Close #176: Mention allocation of 16, 32, and 64-bit all-ones "invalid" tags

#181 cabo closed 4 years ago
1
Close #177: Mention the reduced interoperability of 1+8 tag numbers

#180 cabo closed 4 years ago
0
Close #178: mention that there are other mitigations

#179 cabo closed 4 years ago
0
Security considerations: Hash tables

#178 peteroupc closed 4 years ago
0