Session Date/Time: 26 Jan 2022 15:00

CBOR

Summary

The CBOR working group discussed the intended status of the "File Magic" document, agreeing to move it from BCP to Standards Track. Editorial comments and naming conventions within the document were also addressed. Additionally, the working group decided to withdraw its request for a session at IETF 113 due to a lack of a substantial agenda, opting instead for potential interim meetings or pursuing a broader IAB-led discussion on data modeling for CDDL2.0.

Key Discussion Points

Intended Status of the "File Magic" Document:
- Initial discussion centered on whether the document, currently marked as a Best Current Practice (BCP), should be BCP or Standards Track.
- The document's author initially saw it as a BCP providing guidance, noting that IANA actions it references are primarily First Come First Serve (FCFS).
- Concern was raised that if the document is expected to be a normative reference in other specifications, BCP status would be inappropriate and would require a downref procedure.
- A strong sense of those present indicated that the document should indeed be Standards Track given its potential for normative references.
Editorial Comments on "File Magic" Introduction:
- Comments were raised regarding the accuracy and clarity of historical context provided in the introduction, specifically sentences relating to "record-oriented files" and the impact of Unix.
- The author agreed to remove or rephrase sentences that might be historically inaccurate or cause confusion when read out of context.
"CBOR vs. CBOX" Naming in "File Magic" Document:
- A discussion took place on the naming convention within the document, specifically whether to use "CBOR" or "CBOX" when referring to CBOR-formatted files.
- An argument was made for "CBOR" based on principles of protocol design, emphasizing normalization of information and avoiding ambiguity that could lead to different interpretations or implementations.
- The author and other participants agreed that keeping "CBOR" was the preferred approach for consistency, despite acknowledging "CBOX" was a good suggestion.
IETF 113 Session and Agenda Planning:
- The working group considered whether to request a session at IETF 113.
- Concerns were raised about a lack of sufficient agenda items to warrant a full meeting slot, beyond routine status updates.
- Discussion included the possibility of discussing CDDL2.0, coordinating with the DATE WG on the Time Tag document, and work on CBOR-Packed.
- It was suggested that a wider presentation on CDDL2.0 might be more impactful as an IAB Tech Talk or in a dedicated interim meeting rather than a WG session during IETF.
- The idea of a broader IAB-led plenary discussion on data modeling (including YANG, CDDL, and SDF) was proposed.

Decisions and Action Items

Decision: The "File Magic" document's intended status will be Standards Track.
Decision: The "File Magic" document will consistently use "CBOR" in its naming convention.
Decision: The CBOR working group will withdraw its request for a session at IETF 113.
Action Item: Michael (document author) to update the "File Magic" draft in the coming week to reflect the agreed-upon changes, including the status, naming, and editorial adjustments.
Action Item: Christian (Chair) to send a follow-up email to the CBOR mailing list explaining the reason for withdrawing the IETF 113 meeting request.
Action Item: Carsten (participant) to approach the IAB with a proposal for a broader "data modeling" plenary topic, potentially including YANG, CDDL, and SDF.

Next Steps

The "File Magic" document will be revised and resubmitted reflecting the Standards Track status, "CBOR" naming, and editorial changes.
The IETF 113 meeting slot request will be officially withdrawn, and the mailing list will be informed.
Carsten will initiate contact with the IAB regarding a future, broader presentation on data modeling technologies at an IETF plenary or similar event.
Ongoing work on CBOR-Packed and the Time Tag document (with DATE WG) will continue, likely through interim meetings or offline collaboration as needed.