[Cellar] the why of CELLAR

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 23 January 2024 20:25 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 D9F63C14F749; Tue, 23 Jan 2024 12:25:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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=sandelman.ca
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 n9BgpTiSg6u7; Tue, 23 Jan 2024 12:25:44 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 54E81C14F604; Tue, 23 Jan 2024 12:25:42 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 4AE703898D; Tue, 23 Jan 2024 15:25:41 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id BEw9DlqEX4kk; Tue, 23 Jan 2024 15:25:37 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 9036F3898C; Tue, 23 Jan 2024 15:25:37 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1706041537; bh=0Y/ssGs6WaHbfE36tRk5H8yhOBtXlscXleo8byD7xDI=; h=From:To:cc:Subject:Date:From; b=T/aQr26o6I8aFGXGdN77UPjFiI+fd5yqUSFfkQKrpBuJkT88e7eflXajqFobPNsKw XstvQQz9SEL0G4BpUYzGw2YFeyywg4Y7LE/HcJ4DoeB5n6awd4aBYnW0npnKyUNKeC Zkua3hwGckBSqVZCO/XwaVEjDeE/vBf863CQT+FRZuanfZA52MZiDQLprur8Tw+u9r LeA6ReoUDydv+FGEvR+6meT60BsMT2zjZXXp6kZyTrNE19m3Htv3BzYecGh6RuIcbG EmO/RJJVWqpaulhT2v1lcikSqZCn8EkzEwnE4qeVgUHUE5tm0L7I1vcu2GCcLkOkbC DzT386ZBSWytg==
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 88D12AD; Tue, 23 Jan 2024 15:25:37 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: iesg@ietf.org
cc: cellar@ietf.org, Jay Daley <jay@ietf.org>
X-Attribution: mcr
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 28.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Tue, 23 Jan 2024 15:25:37 -0500
Message-ID: <20154.1706041537@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/egwoxPvsxEk24XwaDhmkV2UHa1k>
Subject: [Cellar] the why of CELLAR
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, 23 Jan 2024 20:25:48 -0000

In case someone wondered about the why of the CELLAR WG.
Might be worth a blog entry.
cellar-matroska is in the RFC-editor Queue.

(the flag document is still in progress)

https://blogs.loc.gov/thesignal/2023/12/embracing-ffv1-matroska-container-preferred/#:~:text=Starting%20in%202020%2C%20FFV1%2FMKV,constraint%20about%20captions%20and%20timecodes

Introduction
  The digital preservation landscape is ever-evolving, and the Library of
  Congress has recently made a significant update to its Recommended Formats
  Statement (RFS). Updated yearly, the RFS serves as guidance for content
  creators in selecting analog and digital formats most suitable for
  long-term preservation. In an off-cycle review of video formats, the
  Library of Congress decided to upgrade FFV1 (version 3) in Matroska (.mkv)
  container from an “Acceptable Format” to one of five “Preferred Formats”
  for the preservation and long-term access of video materials, reflecting
  its ongoing commitment to staying at the forefront of audiovisual
  preservation. Starting in 2020, FFV1/MKV was added as an “Acceptable”
  format only for video content without closed captions and/or timecode
  information. But recent developments have allowed the upgrade from
  “Acceptable” to “Preferred” and removed the constraint about captions and
  timecodes.


--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide