Re: [Cellar] purpose of FLAC RFC --- vs xiph.org

Michael Niedermayer <michael@niedermayer.cc> Fri, 20 October 2023 13:24 UTC

Return-Path: <michael@niedermayer.cc>
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 14E5DC14CF09 for <cellar@ietfa.amsl.com>; Fri, 20 Oct 2023 06:24:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=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
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 mU-3oXLms4Wk for <cellar@ietfa.amsl.com>; Fri, 20 Oct 2023 06:24:17 -0700 (PDT)
Received: from relay4-d.mail.gandi.net (relay4-d.mail.gandi.net [IPv6:2001:4b98:dc4:8::224]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD3C7C14EB1E for <cellar@ietf.org>; Fri, 20 Oct 2023 06:24:15 -0700 (PDT)
Received: by mail.gandi.net (Postfix) with ESMTPSA id 9FB9CE000A for <cellar@ietf.org>; Fri, 20 Oct 2023 13:24:13 +0000 (UTC)
Date: Fri, 20 Oct 2023 15:24:12 +0200
From: Michael Niedermayer <michael@niedermayer.cc>
To: cellar@ietf.org
Message-ID: <20231020132412.GI5133@pb2>
References: <27285.1697739741@localhost>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="lX1nziVKBsdqARWe"
Content-Disposition: inline
In-Reply-To: <27285.1697739741@localhost>
X-GND-Sasl: michael@niedermayer.cc
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/AZhXuRf25MGyeVkzD8mAQbWWW9s>
Subject: Re: [Cellar] purpose of FLAC RFC --- vs xiph.org
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: Fri, 20 Oct 2023 13:24:21 -0000

On Thu, Oct 19, 2023 at 02:22:21PM -0400, Michael Richardson wrote:
> 
> Roman, in his AD review, asks why we did not take over the xiph.org
> ID registry at: https://xiph.org/flac/id.html
> 
> Well.  I thought it was because while we are detailing FLAC in a Matroska
> container in sufficient detail in an RFC, appropriate for use in archiving,
> we were not intending to take over maintenance of FLAC itself.
> (For instance, you can also put FLAC into an OGG container, or an MP4 container)
> 
> https://xiph.org/flac/format.html actually seems to disagree with me though.
> 
> * community FLAC might continue to evolve
> * the archival/RFC version might be a useful subset of what's possible

Why have 1 standard if we can have 2 or 3 that can diverge ;)

seriously, can we somehow try to make sure that evolution (which is good)
of one doesnt lead to 2 incompatible standards (which is bad) ?



> 
> Maybe I'm wrong, and the FLAC community wants the RFC to be the basis for all
> future work.  In which case, taking over that application ID table would be
> appropriate.  But, there are then other IANA tables that we need:
> * Table 2
> * Table 8
> * Table 13
> 

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

I have often repented speaking, but never of holding my tongue.
-- Xenocrates