CBOR working group conference call, 2023-03-06

Meetecho:
https://meetings.conf.meetecho.com/interim/?group=cc6fec51-aa51-46d7-9d9b-ac5bec286bf2

IETF 119 (Brisbane) agenda

Note we have 90 minutes instead of the usual 60.

See also discussion last time at
https://datatracker.ietf.org/doc/minutes-interim-2024-cbor-04-202402211500/

CB presenting the landscape overview.

CB (p2): -time-tag in the RFC Editor's Queue; 3 ongoing WGLC until
Brisbane (EDN, CDDL grammar, CDDL more control). EDN is stable, in spite
of a few last-minute changes due to received feedback.
CB (p2): Here, I don't think we don't need to discuss things.

CB (p3): CDDL has "modules" project, which is nearing completion. Few
changes, but can't ship yet b/c sockets and similar constructs are not
supported yet (can not extend alternatives). Objective: Ready for
hackathon to prove that they are usable.

CB (p4): Four more drafts related to CDDL: -cddl-freezer, -cddl-2-draft,
-rfc-cddl-models, -cddl-csv. Not much to do there right now.

CB (p5): On EDN, extension points now defined in the new -e-ref. Then
-draft-numbers on both EDN and CDDL, for working on examples in Internet
Drafts while some values are not registered with IANA yet.

CB (p5): Everything up to here was "languages".
CB (p6): Now on to extensions, which use extension points.

CB (p6): There is also -packed-reference from CA, I think we should
discuss it in Brisbane.

CB (p7): applications of it for DNS and YANG. Also CBOR-related but not
in the CBOR WG: -intarea-rfc7042-bis and -core-href.

CA: What is the goal on -modules at IETF 119? Do you look for input or
confirm the status before WGLC?
CB: We should have a mini tutorial about the modules.
CA: Ok.
IMD (on chat): +1 to Mini-tutorial at IETF 119

CA: Do you plan to talk about e-ref (in the context of -yang-standin)?
There should be time for it.
CB: Not many changes since December interim where this was presented.
(Summarizing what e and ref do).
CB: The part of -draft-numbers about CDDL is already being considered
for draft-ietf-ace-oscore-gm-admin.
CA: So you don't plan to go through this in Brisbane.
CB: We do give overviews for people to help using CBOR, also thinking of
the -oscore-gm-admin document.

CA: With a 90 minute slot, I wonder if we split the meeting to have a
block dedicated for a tutorial, for example at the end of the session.
CB: It's Friday. But .au is far so people may not leave immediately.
When inviting, prefer to have externals at start.

CA: So we can start the session with a block overviewing things that are
possible in the CBOR ecosystem. The content on the modules might take
more time and transition into the second part of the session. Will
double-check with Barry, then we should be able to go for this.

CB: Oh, I missed the CDE cluster, but stable at this point in time (CDE,
dCBOR, backgrounder).
CB: On Gordian, don't expect that at the Brisbane meeting, it could be
for an interim meeting.

CA: I'll reshape the early-thought agenda based on the above and prepare
an official preliminary agenda. Any more topic to consider?
(none heard)

AOB

First check on dates for the interim calls between IETFs 119 and 120

The proposed dates, keeping the same, even-week cadence on Wednesdays at
16:00 Berlin time (14:00-15:00 UTC) are: 3? and 17 April; (1 skipped
being May 1st), 15, and 29 May; 12 and 26 June; 10 July. We just need to
decide whether 3 April makes sense or whether it's too soon after IETF
119 and we should just start with 17 April.

Starting at April 17th.

CB: We have 3 ongoing WG Last Calls. Please send your comments.
CA: Focus on cddl-more-control.

Note taking: Marco Tiloca