Visual RFC.
ALL RFCs / RFC 8949
Read the RFC ↗
RFC 8949 / MECHANISM GUIDE

Initial byte and arguments

01

The first byte carries a three-bit major type and five-bit additional information.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 3.1 ↗
RFC 8949 · § 3.1EXAMPLE
3 / 3
Initial byte and argumentsThe first byte carries a three-bit major type and five-bit additional information.Initial byte and arguments3901F3major 1 · −1 − 499 = −500Initial byte: 3 type bits + 5 additional-info bits
03
Interpret the type

Type 1 with argument 499 represents −500.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
WHAT CHANGED
RFC 7049RFC 8949 Appendix G

The new specification keeps full format compatibility, corrects errata, and clarifies deterministic encoding. It explicitly does not create a new CBOR format version.

Read the updated RFC section ↗
KEY POINT

Small arguments 0–23 are inline; larger values use following bytes.

  • Small arguments 0–23 are inline; larger values use following bytes.
  • Major types distinguish integers, strings, containers, tags, and simple/float values.
  • Negative integers use value −1 minus the unsigned argument.
DETAILS

Examples are illustrative. Consult the linked RFC and its errata for implementation details.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Initial byte and arguments
  2. Strings and containers
  3. Indefinite lengths
  4. Tags and data models
  5. Deterministic encoding
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗