Skip to main content


Meeting Agenda Codec Encoding for LossLess Archiving and Realtime transmission (cellar) WG
Date and time 2024-01-23 20:00
Title (None)
State Active
Other versions markdown
Last updated 2024-01-23


CELLAR -- DRAFT AGENDA for Virtual Interim Meeting

Date Time Local Times
2024-01-23 21:00 Amsterdam Time Converter
Note Meeting time is anchored to Amsterdam


**Note that we're now pointing to the Github repo for chair notes here**


note that chat is now Zulip:
but is accessible via meetecho interface.

Shared HedgeDoc for notetaking

Now using the Datatracker assigned notepad at:
  • Note that if you log in to the IETF datatracker, you'll be able to edit/clarify/correct these notes, add your name to attendee lists, etc.

  • Please ask Michael or Spencer if you have questions.

2024 virtual interim meeting dates

Agenda Items

Note Well:
Please be KIND to each other.

Roll call


Accept draft minutes from previous meeting


WG status update

Draft State Date Posted Plans
draft-ietf-cellar-chapter-codecs-03 Expired 2023-07-02
draft-ietf-cellar-codec-11 Expired 2023-07-02
draft-ietf-cellar-control-03 Expired 2023-07-02
draft-ietf-cellar-ffv1-v4-21 ID Exists 2024-01-17
draft-ietf-cellar-flac-14 IESG Evaluation::AD Followup 2024-01-14
draft-ietf-cellar-matroska-21 RFC Ed Queue 2023-10-22
draft-ietf-cellar-tags-12 ID-Exists 2023-10-22

Milestone review:

Next steps for additional Matroska specifications (three of which are expired)

  • We're still going to do these, right?

FLAC IESG ballot

  • Moving the picture types defined in [ID3v2] to an IANA registry gave us a new normative downref for [RFC2083].
  • Thre requrement is that normative references from a higher-maturity specification (in our case, Propose Standard) to a lower-maturity specification (in our case, Informational) must be identified in the Last Call announcement.
  • After a downref has been evaluated as part of a Last Call for any document, the reference can be added to the downref registry, but [RFC2083] isn't in that registry (yet)
  • Murray is checking with the IESG to see how he should proceed
  • No action needed at this time from the working group or from Martijn
  • For the group - This wasn't actually anyone's fault - Spencer thought we weren't allocating any new code points, because we were copying the picture types into a new IANA registry with no changes, but we actually WERE allocating new code points to the IANA registry

New revision for FFV1v4

  • Email thread is here

Update on patch for FFv1 versions 1-3?

  • Jérôme said at our last meeting that we have a patch for FFv1 versions 1-3 (odd width or height, and chroma subsampling) that he needs to review again, and it may require an errata.


Next meeting is 2024-02-27.