[Cellar] Re: Introductions and a new I-D that may be appropriate for CELLAR
Robert Sparks <rjsparks@nostrum.com> Wed, 25 March 2026 14:33 UTC
Return-Path: <rjsparks@nostrum.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 CBF50D13F661 for <cellar@mail2.ietf.org>; Wed, 25 Mar 2026 07:33:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.08
X-Spam-Level:
X-Spam-Status: No, score=-2.08 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, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.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 gj9TFLa9PvaI for <cellar@mail2.ietf.org>; Wed, 25 Mar 2026 07:33:16 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 41D90D13F651 for <cellar@ietf.org>; Wed, 25 Mar 2026 07:33:16 -0700 (PDT)
Received: from [192.168.1.148] (47-186-32-211.fdr02.plan.tx.ip.frontiernet.net [47.186.32.211]) (authenticated bits=0) by nostrum.com (8.18.2/8.18.1) with ESMTPSA id 62PEX6kC007747 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 25 Mar 2026 09:33:07 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1774449187; bh=lkJqosea8eLt0vQ/cdDmwyh49Rkjvi79wRdxDF06DgY=; h=Date:Subject:To:References:From:In-Reply-To; b=F69DD6DCjV1hEvHOvyerOPiWS1T7v/ctcIhGaUQowItTyw1m6fbmD7XbUwEyAbvtb UgWdVPwmZzQaHJJOr5OcYwWhFJmzzqbEg2uLJZ/FlVGYjqUs9Ooj6tA2F11EWAeFZD Sdvm9w59M0X9v7eno7L4ccvAPu4/Dbp5Gw6wXvPE=
X-Authentication-Warning: raven.nostrum.com: Host 47-186-32-211.fdr02.plan.tx.ip.frontiernet.net [47.186.32.211] claimed to be [192.168.1.148]
Message-ID: <76ed559e-b6fe-47a2-aebe-1ad6a7be0366@nostrum.com>
Date: Wed, 25 Mar 2026 09:33:01 -0500
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Sam Whited <sam@samwhited.com>, cellar@ietf.org
References: <67bf643c-9a4f-4443-998a-01d4d1f5eea6@samwhited.com> <0f9d1d78-a822-4907-a57e-705ae1ac9c2d@samwhited.com>
Content-Language: en-US
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <0f9d1d78-a822-4907-a57e-705ae1ac9c2d@samwhited.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: NSXJHUSCDPOB76LYPEIPX5WABIZ6OHJZ
X-Message-ID-Hash: NSXJHUSCDPOB76LYPEIPX5WABIZ6OHJZ
X-MailFrom: rjsparks@nostrum.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/nUs67aZjC1-kSS19_CTSMFOURmo>
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>
On 3/25/26 6:28 AM, Sam Whited wrote: > Hi all, > > I'm considering asking the secretary That's not who you would ask. > to consider this draft [1] for publication. Do you mean as an RFC? > It's new and likely isn't actually ready yet, Which tells you that it is not time to ask _any_ stream to publish this as an RFC. > but I've had a hard time finding folks who want to review it so in the > interest of not letting it sit until it expires I'm thinking about > pushing it forward to get some AD reviews (it does appear to be > relatively complete, so hopefully it's not wasting their time). > > If anyone in this working group would like to do further reviews > before hand, however, you're the experts and I'd love to get your > advice, but I know there's a lot to do and that's a big ask. > Similarly, I've only ever submitted through working groups before, so > if anyone who's more heavily involved has opinions on the individual > submission stream Did you mean Independent Submission stream? If so, you'll have to convince the Independent Stream Editor that there's a reason to publish the document now and that it's not something that the IETF stream should publish instead. It would only get an IESG review that covers "Does this conflict with IETF work". If you really meant progressing this as an Individual Submission in the IETF stream, you will have to convince an AD to sponsor it. I think you'll find that they ask that you gather interest from the community first. If you didn't participate in realtime, you might find listening to the recording of the dispatch session from the most recent IETF informative. The best use of your time is to continue to try to find interested parties to work on further refining the document. > and wants to share them, I'm certainly willing to listen! > > Thank you, > Sam > > > [1]: https://datatracker.ietf.org/doc/draft-swhited-mka-stems/ > > > > 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 >>
- [Cellar] Introductions and a new I-D that may be … Sam Whited
- [Cellar] Re: Introductions and a new I-D that may… Martijn van Beurden
- [Cellar] Re: Introductions and a new I-D that may… Sam Whited
- [Cellar] Re: Introductions and a new I-D that may… Sam Whited
- [Cellar] Re: Introductions and a new I-D that may… Steve Lhomme
- [Cellar] Re: Introductions and a new I-D that may… Sam Whited
- [Cellar] Re: Introductions and a new I-D that may… Sam Whited
- [Cellar] Re: Introductions and a new I-D that may… Spencer Dawkins at IETF
- [Cellar] Re: Introductions and a new I-D that may… Sam Whited
- [Cellar] Re: Introductions and a new I-D that may… Steve Lhomme
- [Cellar] Re: Introductions and a new I-D that may… Sam Whited
- [Cellar] Re: Introductions and a new I-D that may… Robert Sparks
- [Cellar] Re: Introductions and a new I-D that may… Sam Whited