**Session Date/Time:** 24 Sep 2024 19:00

# [CELLAR](../wg/cellar.html)

## Summary

The CELLAR Working Group held a meeting to discuss the status of the ongoing Working Group Last Call (WGLC) for a document, the progress of the FLAC document in the RFC Editor queue, and an update on a Google Summer of Code (GSoC) project. The WGLC received no significant objections, and the working group plans to move the document forward. Discussion also covered formatting within the document's registry section and a general update on working group closure.

## Key Discussion Points

*   **Working Group Last Call (WGLC) Status**: The WGLC for a document (implicitly the one containing the registry discussed below) was nearing its close, with the deadline set for the end of the day. The chair, Michael, reported that no significant comments or objections had been received, beyond some minor affirmations from authors.
*   **Previous Meeting Minutes**: The minutes from the previous meeting were reviewed and accepted without objection.
*   **Document Registry Section Syntax**: An Area Director (AD) raised a question regarding the use of backslashes in the `idtype/default` and `path` components within the registry section of the document (e.g., `segment/tracks/TrackEntry/Audio`). Steve (the editor) clarified that this formatting was adopted to maintain conciseness and avoid excessive width after an earlier table format proved unwieldy. The AD confirmed understanding and found it acceptable.
*   **FLAC Document in RFC Editor Queue**: The FLAC document has been in the RFC Editor queue for 14 weeks. Discussion revolved around potential reasons for the delay, including being "head-of-queue blocked" by another large document (MATOSA) or potential RFC Editor personnel availability issues, possibly due to post-meeting illnesses. It was confirmed that the RFC number for FLAC will remain the same.
*   **Google Summer of Code (GSoC) Update**: Steve provided an update on the GSoC project. The student has largely completed the coding work, with some remaining issues being addressed. The associated specifications are also nearly finalized. Steve noted that further input on security considerations, particularly concerning JavaScript embedded in a file, would be sought from the IESG.
*   **FLAC Document Fixes**: It was noted that any suggestions for fixes to the FLAC document should be held until feedback is received from the RFC Editor's AUTH48 process.

## Decisions and Action Items

*   **Decision**: The minutes from the previous meeting were accepted.
*   **Decision**: The Working Group Last Call (WGLC) for the current document will proceed towards closure, given the lack of significant objections.
*   **Action Item**: Michael (chair) will declare the WGLC closed and summarize any gathered comments for the mailing list.
*   **Action Item**: Following Michael's summary, the Area Director will initiate the process to advance the document in the IETF data tracker.

## Next Steps

*   The document that was subject to the WGLC will be processed for advancement to the IESG.
*   The status of the FLAC document in the RFC Editor queue will continue to be monitored.
*   Remaining issues in the GSoC code will be resolved, and IESG input will be sought regarding security considerations for the specifications.
*   Suggestions for FLAC document fixes should be deferred until the AUTH48 process.