[Cellar] Re: Introductions and a new I-D that may be appropriate for CELLAR

Sam Whited <sam@samwhited.com> Mon, 23 February 2026 15:46 UTC

Return-Path: <sam@samwhited.com>
X-Original-To: cellar@mail2.ietf.org
Delivered-To: cellar@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 2498FBC46B6E for <cellar@mail2.ietf.org>; Mon, 23 Feb 2026 07:46:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=samwhited.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lL8dUjL3L5xL for <cellar@mail2.ietf.org>; Mon, 23 Feb 2026 07:46:20 -0800 (PST)
Received: from 004.priority.relay.mayfirst.org (004.priority.relay.mayfirst.org [204.19.241.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id B59E9BC46B69 for <cellar@ietf.org>; Mon, 23 Feb 2026 07:46:20 -0800 (PST)
Received: from 002.route.relay.mayfirst.org (002.route.relay.mayfirst.org [204.19.241.147]) by 004.priority.relay.mayfirst.org (Postfix) with ESMTP id 4fKQF22sjzz4w9T for <cellar@ietf.org>; Mon, 23 Feb 2026 15:46:14 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=samwhited.com; s=mayfirst1; t=1771861574; bh=gZc5uFnlgSZyqeZVjR1LWswlxqcsH2y3JI97FGk0gKY=; h=Date:Subject:To:References:From:In-Reply-To:From; b=IcEc4rW8ZcX3KDfq24yMu2yd7WxlwSy5xx5CAwqR/WV9PvxUPGnshg7ALOoPUEInU Y4LKwY2c3Oy7yJAUCZOdnxocZaEXKp8+0DZeyEJS6meJWDkNVV32hwsNoulmth9JSn UzCQvGLlvPwL6g4rSFQpVmYf4PKe6eZSdP2gzXBm7X9IXQFCR3TM13bf7Fncynf5GW RozQbaj0jUkgYBW/nl6XBI+Ap88UZBmU32qeZy25sfYCAU71zH6K14PZFv9mtrlnjf v4FAqvVGQuaJ9lQauq8zAWXmUJ2pZ1Dqmuh87azkEMmT1u4Xhm8x3mVB0KoRs5WnH+ 5UQAZ/0ZWi7HA==
Received: from filter.mayfirst.org (mailfilter003.mayfirst.org [209.51.172.10]) by 002.route.relay.mayfirst.org (Postfix) with ESMTP id 4fKQF22SJSz20b9 for <cellar@ietf.org>; Mon, 23 Feb 2026 15:46:14 +0000 (UTC)
Received: from filter.mayfirst.org (localhost [127.0.0.1]) by filter.mayfirst.org (Postfix) with ESMTP id 4fKQF21671z2w4K for <cellar@ietf.org>; Mon, 23 Feb 2026 15:46:14 +0000 (UTC)
X-Spam-Language: en
X-Envelope-From: <sam@samwhited.com>
Received: from mail.mayfirst.org (mailcf003.mayfirst.org [209.51.172.14]) by filter.mayfirst.org (Postfix) with ESMTPS id 4fKQF20jlnz2w4F for <cellar@ietf.org>; Mon, 23 Feb 2026 15:46:14 +0000 (UTC)
X-Mayfirst-Relay: priority
Message-ID: <b6785158-5375-491b-bcb7-ee096f7c2116@samwhited.com>
Date: Mon, 23 Feb 2026 10:46:12 -0500
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: cellar@ietf.org
References: <67bf643c-9a4f-4443-998a-01d4d1f5eea6@samwhited.com>
Content-Language: en-US
From: Sam Whited <sam@samwhited.com>
Autocrypt: addr=sam@samwhited.com; keydata= xjMEYQ9TGxYJKwYBBAHaRw8BAQdA1uioUF7QcW5zHL8JZngkgggUHz6IkaiHuD+orF0vBRLN HlNhbSBXaGl0ZWQgPHNhbUBzYW13aGl0ZWQuY29tPsKQBBMWCAA4FiEEgiFNf7VNyaO8DNrh FtUTjlK4SbMFAmEPUxsCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AACgkQFtUTjlK4SbOK UQD/bMy4TOMOojgJZrcdobguB5mXLprol3bW2g70DDQ8DKwBAK7QVx7EqNEsf3dI9/DUV5xV EdS7NVVGzyRXPIp0cxgMzjgEYQ9TGxIKKwYBBAGXVQEFAQEHQMqWNKV2p/GhJnwRucCXB7gk uFt6k71ny/wX7McE+R1LAwEIB8J4BBgWCAAgFiEEgiFNf7VNyaO8DNrhFtUTjlK4SbMFAmEP UxsCGwwACgkQFtUTjlK4SbM3mwD+KFVyE0rJIvc2+a5Y+tVfqaipVBVFz73/mJIndt83Z/EA /RN2WT6/IXF0V0UYgLubjXfKmrodyWHod697aMYJeJMM
In-Reply-To: <67bf643c-9a4f-4443-998a-01d4d1f5eea6@samwhited.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: ClamAV using ClamSMTP
Message-ID-Hash: F3JMG6V24TILYI5NDP2CRCEKIQJYHYRC
X-Message-ID-Hash: F3JMG6V24TILYI5NDP2CRCEKIQJYHYRC
X-MailFrom: sam@samwhited.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-cellar.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Cellar] Re: Introductions and a new I-D that may be appropriate for CELLAR
List-Id: Codec Encoding for LossLess Archiving and Realtime transmission <cellar.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/HWDBxYVtmhpz1lQfAyw0jSPMzpo>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cellar>
List-Help: <mailto:cellar-request@ietf.org?subject=help>
List-Owner: <mailto:cellar-owner@ietf.org>
List-Post: <mailto:cellar@ietf.org>
List-Subscribe: <mailto:cellar-join@ietf.org>
List-Unsubscribe: <mailto:cellar-leave@ietf.org>

Following up: I've also submitted a new draft to be worked on in 
parallel (for now) using Matroska. It's still unclear to me how I would 
store some of this information in Matroska or which format would be 
better for this use case (or even what requirements would lead one 
format to being a better fit than the other), but for now I'll work on 
both and if one ends up seeming like a better option I can always drop 
the other draft.

https://datatracker.ietf.org/doc/draft-swhited-mka-stems/

I'd still be interested in knowing if this is something cellar would be 
interested in (regardless of whether my specific draft is picked up or 
not), or if I should stop spamming the list and stick to the individual 
submission stream :)

—Sam

On 2026-02-19 15:19, Sam Whited wrote:
> Hi all,
>
> I'm a former IETF contributor (RFC9622, various other I-D's with the 
> KITTEN WG) but haven't been around for a long time. I started working 
> on an I-D recently that I had originally considered for independent 
> submission, but someone suggested that CELLAR may be an appropriate 
> place for it.
>
> https://datatracker.ietf.org/doc/draft-swhited-ogg-stems/
>
> The TL;DR is that there is currently no open format for encoding 
> stems, ie. files that contain individual audio tracks for various 
> instruments or clusters of instruments that DJs, producers, etc. use 
> to re-mix tracks on the fly. I would like to define a stem format 
> using OGG wrappers containing FLAC and/or Opus. I read through 
> CELLAR's description and wasn't sure if it would be an appropriate 
> fit, so I joined the list and wanted to know if this is something 
> CELLAR would be interested in adopting or if you'd prefer it remain an 
> independent submission.
>
> Thanks for doing what you do!
>
> —Sam
>
-- 
Sam Whited
sam@samwhited.com