Skip to main content

Minutes IETF126: cbor
minutes-126-cbor-00

Meeting Minutes Concise Binary Object Representation Maintenance and Extensions (cbor) WG
Date and time 2026-07-23 09:30
Title Minutes IETF126: cbor
State Active
Other versions plain text
Last updated 2026-08-14

minutes-126-cbor-00
Minutes for the CBOR WG
IETF 126, 2026-07-23

These minutes are based on input from <https://ietfminutes.org/>, with edits by
Paul Hoffman. See <https://datatracker.ietf.org/meeting/126/session/cbor> for
the full meeting materials.

The CBOR Working Group met at IETF 120 to discuss the status and next steps for
two primary documents: `draft-ietf-cbor-serialization` (CBOR Serialization and
Determinism) and `draft-ietf-cbor-edn-literals` (Concise Diagnostic Notation).

`draft-ietf-cbor-serialization` is close to ready for Working Group Last Call.
For `draft-ietf-cbor-edn-literals`, the working group agreed to adopt a
structured feature-winnowing process on the mailing list to establish a stable
technical baseline, postponing non-technical debates (such as document naming)
to the end of the cycle. Both documents will continue to progress in parallel.

Laurence Lundblade presented a status update using the slides "[CBOR
Serialization Status
Update](https://datatracker.ietf.org/meeting/126/materials/slides-126-cbor-cbor-serialization-status-update-00)".
The discussion that followed covered a few topics:
    *   There are inconsistencies in how the bundle protocol, c509, COSE, and
    other signing designs handle byte strings. *   There was the usual
    discussion of nontrivial NaNs that needs to be resolved on the mailing
    list. *   There might later be a separate document on language-specific
    mappings. *   THe recent thread on the list about bignums needs to be
    resolved.

Christian Amsüss introduced the status of `draft-ietf-cbor-edn-literals`,
noting that version -27 (submitted after the deadline) incorporates significant
editorial restructuring requested by reviewers. The chairs proposed using a
structured triage workflow on the mailing list (based on suggestions from Joe
Hildebrand) to determine which features to keep, modify, or remove. The goal is
to start from a baseline matching RFC 8949 and RFC 8610 and selectively remove
features lacking consensus. Non-technical debates, such as what to name the
final notation, will be explicitly deferred to after the decisions on what to
remove.