[Cellar] The Long-awaited Agenda for our 2023-02 interim meeting (later today)
Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Tue, 28 February 2023 14:56 UTC
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: cellar@ietfa.amsl.com
Delivered-To: cellar@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26B65C1522C2 for <cellar@ietfa.amsl.com>; Tue, 28 Feb 2023 06:56:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.085
X-Spam-Level:
X-Spam-Status: No, score=-7.085 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 90Ls3z0iUMP7 for <cellar@ietfa.amsl.com>; Tue, 28 Feb 2023 06:56:10 -0800 (PST)
Received: from mail-pj1-x1032.google.com (mail-pj1-x1032.google.com [IPv6:2607:f8b0:4864:20::1032]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C091C1522CB for <cellar@ietf.org>; Tue, 28 Feb 2023 06:56:10 -0800 (PST)
Received: by mail-pj1-x1032.google.com with SMTP id y15-20020a17090aa40f00b00237ad8ee3a0so9883299pjp.2 for <cellar@ietf.org>; Tue, 28 Feb 2023 06:56:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=5VJO93u7skJEvSwnbfKbxiVHV2N/DbRq3Jaou1JguY4=; b=AynZd2/79/IWEQ76jYdeg5YQ+TNliJon8Bhfre7dh2+2MJq2UbSIfmrUxpEscDuMrz iW6RgAsFGzZKhudA1mw6yb7khnPE70cafKBg7d1/YxHXPu1+Tus/d55wpgwEZWPitnHB 3ne8SOoUkYYO2AsvrL3tyXDfHgUN2oE08KEUUiZdaUfFte4dGhEiMp48Sllg6hAmOOcT gAtsLpW3UnR7uinIOiaByU8m6feasQ7I9Nl2kWO/HqClhneD7egkdSrH/1RjqwgSGh8O BV6rVvn+Emw46ndwUsYnPErUaKNqAk2kvIF8JMenUX5tB3LWLeE05JettpUdmiWAUv8d 9avQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=5VJO93u7skJEvSwnbfKbxiVHV2N/DbRq3Jaou1JguY4=; b=rZciYY+hABfmpyvCB3f6ffuS0xYGHAC9XpjewC578026wfsO4kXj9fUO1l23ejHEZg 5RtoLHPWNr/vwLe1oira8cqa21H5l+izIbJ18BWXR5FM0/zMdNi2IGhgEqRH4rjONBCa UFs0k+mBpFHi+imBHo0lYA5gyeINbAUp29HOev1nVz20giXZ6U9fv9kH5yO9n21pm8Ru 48UL6B4pipU3HLe680QsxpJVVxdzn7wOiQW3o/mMJCTKdYI69QWYEfYQ4HRzfrHT/go0 5wRWlxJ2HiR4itxq2CmeDvVOgLCA3qYURnMvMZ6Vq2GRPNn6Kj7j9lVXzqMOXSiBlODO 3x+A==
X-Gm-Message-State: AO0yUKVnCQ/IN4Q83InXWnjMr95CtMhDq5EBhgxdDiOkHl3c9YNyH5Nw Go7cCRRteaJl0fEq6xKXFw81gDDJdqcqfCWmnoRzQTIWHUQ=
X-Google-Smtp-Source: AK7set9ozA37sZcpjLkjuL0Q3rOgf3mDhLtC8zT+Bh8AhvZlo80ms2cCG4ZgFest+XS08uT6P064WKIWdXFEymS+VLg=
X-Received: by 2002:a17:902:ab11:b0:19b:e4c:2039 with SMTP id ik17-20020a170902ab1100b0019b0e4c2039mr1126707plb.4.1677596168708; Tue, 28 Feb 2023 06:56:08 -0800 (PST)
MIME-Version: 1.0
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 28 Feb 2023 08:55:42 -0600
Message-ID: <CAKKJt-fVBMwjEOxmQmpB_692ZeGecaAtov3Z-GUATxmJCkH2CQ@mail.gmail.com>
To: Codec Encoding for LossLess Archiving and Realtime transmission <cellar@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b6688905f5c3cbb6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/MX31iZDbDlNXNQKQKiS78nFEqts>
Subject: [Cellar] The Long-awaited Agenda for our 2023-02 interim meeting (later today)
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Codec Encoding for LossLess Archiving and Realtime transmission <cellar.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cellar>, <mailto:cellar-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cellar/>
List-Post: <mailto:cellar@ietf.org>
List-Help: <mailto:cellar-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cellar>, <mailto:cellar-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Feb 2023 14:56:14 -0000
CELLAR – DRAFT AGENDA for Virtual Interim Meeting DateTimeLocal Times 2023-02-28 14:00 Amsterdam Time Converter <https://savvytime.com/converter/netherlands-amsterdam-to-utc-ny-new-york-city-ca-san-francisco/jun-22-2021/9pm> Note Meeting time is anchored to Amsterdam <https://notes.ietf.org/#Administrivia>Administrivia <https://notes.ietf.org/#INFO>INFO: https://github.com/ietf-wg-cellar/chair-notes/tree/master/interim-2023-02 Note that we’re now pointing to the Github repo for chair notes here <https://notes.ietf.org/#MEETING-INFO-and-WEB-CONFERENCE>MEETING INFO and WEB CONFERENCE: info: https://datatracker.ietf.org/meeting/interim-2023-cellar-02/session/cellar https://meetings.conf.meetecho.com/interim/?short=8a8f2003-11c7-4564-88fe-46b1c0c93049 note that chat is now Zulip: https://zulip.ietf.org/login/#narrow/stream/cellar but is accessible via meetecho interface. <https://notes.ietf.org/#Shared-HedgeDoc-for-notetaking>Shared HedgeDoc for notetaking Now using the Datatracker assigned notepad at:https://notes.ietf.org/notes-ietf-interim-2023-cellar-02-cellar - 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. <https://notes.ietf.org/#2023-virtual-interim-meeting-dates>2023 virtual interim meeting dates - Please note our 2023 dates listed at https://datatracker.ietf.org/wg/cellar/meetings/ <https://notes.ietf.org/#Agenda-Items>Agenda Items <https://notes.ietf.org/#Note-Well>Note Well: https://www.ietf.org/about/note-well/ Please be KIND to each other. <https://notes.ietf.org/#Roll-call>Roll call Attendees - Spencer Dawkins - Regrets * <https://notes.ietf.org/#Accept-draft-minutes-from-2023-01-24>Accept draft minutes from 2023-01-24 - <https://notes.ietf.org/#WG-status-update>WG status update DraftStateDate PostedPlans draft-ietf-cellar-chapter-codecs-01 ID Exists 2022-12-04 draft-ietf-cellar-codec-09 ID Exists 2022-12-04 draft-ietf-cellar-control-01 ID Exists 2022-12-04 draft-ietf-cellar-ffv1-v4-19 ID Exists 2022-12-04 draft-ietf-cellar-flac-07 Waiting for Shepherd write-up 2022-10-23 Shepherd notes sent to mailing list for February meeting draft-ietf-cellar-matroska-15 In Last Call (ends 2023-02-28) 2023-02-11 Last Call ends 2023-02-28 draft-ietf-cellar-tags-09 ID Exists 2022-12-04 <https://notes.ietf.org/#Milestone-review>Milestone review: - IESG Balloting is next step for Matroska - AD Evaluation is next step for FLAC <https://notes.ietf.org/#Matroska-issues---Discussion-of-Last-Call-comments-on-the-call>Matroska issues - Discussion of Last Call comments on the call. - Need to discuss EBML Lacing details are incorrect #726 <https://github.com/ietf-wg-cellar/matroska-specification/issues/726> issue on the call - <https://notes.ietf.org/#FLAC-issues---Discussion-on-the-call>FLAC issues - Discussion on the call - Spencer finally finished the Shepherd Review in two parts, starting here <https://mailarchive.ietf.org/arch/msg/cellar/gYqVZiws52oA38zSrqw5yXEj_TA/> - <https://notes.ietf.org/#FFV1-v4-issues---Discussion-on-the-call>FFV1 v4 issues - Discussion on the call - From Spencer) Any Feedback from FOSDEM FFV1 presentation <https://fosdem.org/2023/schedule/event/om_ffv1/>? - small wish list is in issue tracker: https://github.com/FFmpeg/FFV1/issues - we will go through the issues and prioritize them. - <https://notes.ietf.org/#AOB>AOB? - (from Spencer) Is it useful to discuss how much we want to rely on the RFC Errata process for specifications with source text in GitHub at a future meeting? - (from Spencer) Is it useful to go over the post-WGLC publication process at a future meeting? - Next meeting is 2023-03-28 <https://notes.ietf.org/#Previous-Minutes---CELLAR-%E2%80%93-DRAFT-AGENDA-for-Virtual-Interim-Meeting>Previous Minutes - CELLAR – DRAFT AGENDA for Virtual Interim Meeting <https://notes.ietf.org/#CELLAR-%E2%80%93-DRAFT-AGENDA-for-Virtual-Interim-Meeting1>CELLAR – DRAFT AGENDA for Virtual Interim Meeting DateTimeLocal Times 2023-01-24 14:00 Amsterdam [ ]( https://savvytime.com/converter/netherlands-amsterdam-to-utc-ny-new-york-city-ca-san-francisco/jun-22-2021/9pm ) Note Meeting time is anchored to Amsterdam <https://notes.ietf.org/#Administrivia1>Administrivia <https://notes.ietf.org/#INFO1>INFO: https://github.com/ietf-wg-cellar/chair-notes/tree/master/interim-2023-01 Note that we’re now pointing to the Github repo for chair notes here <https://notes.ietf.org/#MEETING-INFO-and-WEB-CONFERENCE1>MEETING INFO and WEB CONFERENCE: info: https://datatracker.ietf.org/meeting/interim-2023-cellar-01/session/cellar https://meetings.conf.meetecho.com/interim/?short=d340a5fa-8e80-4092-b480-53c684f0b32d note that chat is now Zulip: https://zulip.ietf.org/login/#narrow/stream/cellar but is accessible via meetecho interface. <https://notes.ietf.org/#Shared-HedgeDoc-for-notetaking1>Shared HedgeDoc for notetaking Now using the Datatracker assigned notepad at:https://notes.ietf.org/notes-ietf-interim-2023-cellar-01-cellar - 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. <https://notes.ietf.org/#2023-virtual-interim-meeting-dates1>2023 virtual interim meeting dates - Please note our 2023 dates listed at https://datatracker.ietf.org/wg/cellar/meetings/ <https://notes.ietf.org/#Agenda-Items1>Agenda Items <https://notes.ietf.org/#Note-Well1>Note Well: https://www.ietf.org/about/note-well/ Please be KIND to each other. <https://notes.ietf.org/#Roll-call1>Roll call Attendees - Spencer Dawkins - Martijn van Beurden - Michael Richardsdon - Steve Lhomme - Jerome Martinez - Michael Niedermayer - Dave Rice Regrets * <https://notes.ietf.org/#Accept-draft-minutes-from-December-6-2022>Accept draft minutes from December 6, 2022 - minutes accepted as presented. <https://notes.ietf.org/#WG-status-update1>WG status update DraftStateDate PostedPlans draft-ietf-cellar-chapter-codecs-01 ID Exists 2022-12-04 draft-ietf-cellar-codec-09 ID Exists 2022-12-04 draft-ietf-cellar-control-01 ID Exists 2022-12-04 draft-ietf-cellar-ffv1-v4-19 ID Exists 2022-12-04 draft-ietf-cellar-flac-07 Waiting for Shepherd write-up 2022-10-23 anticipated to arrive before February meeting draft-ietf-cellar-matroska-11 AD Evaluation 2022-10-01 draft-ietf-cellar-tags-09 ID Exists 2022-12-04 FFV1 presentation at FOSDEM in open media dev-room on Saturday, 2023-02-04, 14:00. https://fosdem.org/2023/schedule/event/om_ffv1/ <https://notes.ietf.org/#Milestone-review1>Milestone review: - FLAC waiting for Shepherd write up from Spencer <https://notes.ietf.org/#Matroska-issues---Discussion-of-AD-review-comments-from-Murray-Kucherawy-on-the-call>Matroska issues - Discussion of AD review comments from Murray Kucherawy <https://mailarchive.ietf.org/arch/msg/cellar/waY3cjku6hhTQ16do1wC7XNsXzQ/> on the call. - document has been returned with AD comments - Steve Lhomme has been very responsive in providing PRs and explanations to Murray (Thank you, Steve!) - One PR is still open - we’ll discuss on the call - Our UIDs are not UUIDs - they’re not what the IETF calls UUIDs. - The UUID specification is being revised, but we can recommend calling them UUID v4 and treat them as an opaque 128-bit string. - We have no idea what UUID v8 will be, of course … - Do we forbid reuse of deprecated IDs? That’s maximum compatibility, but reduces the size of the available ID space. - We don’t know of usages (many? most?), but we can’t know that no one has used a deprecated code point. - We can mark the deprecated IDs as “returned” not as “reserved”, and we can instruct IANA to use “returned” IDs last. - This is for one-byte IDs - we can just lose the longer ID codes. We did this with DHCP option codes, so we have prior art here, including collisions because people were reusing “unused” option codes without coordinating with others, and how to recover from that situation. - Spencer noted that this is a working group document, so we should make sure the working group still agrees with the document after changes. <https://notes.ietf.org/#FLAC-issues---Discussion-on-the-call1>FLAC issues - Discussion on the call - OPUS talks a lot about encoding, and the FLAC specification doesn’t. Is that OK? - We tend to focus on decoders, and allow encoders to innovate. We can say what we want to say, but we should make a decision explicitly. - Martijn is still experimenting and making small corrections and clarifications, and that’s fine. - We think June is a reasonable timeframe now. <https://notes.ietf.org/#FFV1-v4-issues---Discussion-on-the-call1>FFV1 v4 issues - Discussion on the call - No discussion on the call. - small wish list is in issue tracker: https://github.com/FFmpeg/FFV1/issues - next meeting, we will go through the issues and prioritize them. <https://notes.ietf.org/#AOB1>AOB? - Next meeting is 2023-02-28 - Implementation report: ffmpeg has ffv1 in MXF patch!
- [Cellar] The Long-awaited Agenda for our 2023-02 … Spencer Dawkins at IETF
- Re: [Cellar] The Long-awaited Agenda for our 2023… Martijn van Beurden