Re: [Cellar] IETF work on FLAC (fwd) Josh Coalson: Re: IETF work on FLAC
Michael Richardson <mcr+ietf@sandelman.ca> Tue, 23 November 2021 11:00 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 4D9523A0120 for <cellar@ietfa.amsl.com>; Tue, 23 Nov 2021 03:00:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k8wlIFmX47KM for <cellar@ietfa.amsl.com>; Tue, 23 Nov 2021 03:00:40 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61C283A02BB for <cellar@ietf.org>; Tue, 23 Nov 2021 03:00:28 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id BAD4D180A6 for <cellar@ietf.org>; Tue, 23 Nov 2021 06:03:14 -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 i6ONtykdUrBL for <cellar@ietf.org>; Tue, 23 Nov 2021 06:03:10 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 0031C18012 for <cellar@ietf.org>; Tue, 23 Nov 2021 06:03:10 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sandelman.ca; s=mail; t=1637665390; bh=Vo+21xASExCSpa0PBLg70aRKaz+oLc2L1CkzIfb6VeM=; h=From:To:Subject:Date:From; b=S2Ea/5rIsYyM+u70aOyEQ0lwODASCsbQGefkP4fxiD97OCEvp8btkMV8mSPimgS5w lvzj2npE3rC3AajjY+fqNvljKbsMww9F1pOLyati7R6wlhEO7QxP9i9He0CmlD+FSI ob8EB4wBoSWuZTAxYKKU7Aof6nhX32U+Y3hcc9GCNRvXT6AJA5wqbZpIyDsEKVS/jR Ct7rPevp013QMzHvKdFM11jGhusqMa8uYEcM7ekdr62N5HG2p6f+n1p0C7ekq26zTI MFJKUZRmj5XqyoY4JdAwR7FJLmye1PLT2BJwi3dO1O7BSeYVXfoPkQDuZyZmm23sVN 8NMLHvnCiOSPQ==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 8F8E3128B for <cellar@ietf.org>; Tue, 23 Nov 2021 06:00:22 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: cellar@ietf.org
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
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 Nov 2021 06:00:22 -0500
Message-ID: <32445.1637665222@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/yRr6u7Km6NSH16zEt4HfMp0-P8c>
Subject: Re: [Cellar] IETF work on FLAC (fwd) Josh Coalson: Re: IETF work on FLAC
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.29
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 Nov 2021 11:00:45 -0000
From: Josh Coalson v0idstar at icloud dot com Subject: Re: IETF work on FLAC Date: Fri, 19 Nov 2021 08:43:19 -0800 I see. I’m fine with the same Xiph license (new BSD) that is used for the libraries. Xiph is managing the publishing of the docs on their website though; if an attestation from me is not enough, is there something to coordinate with them? Also, I don’t mind helping with the standard if you have any format-specific questions along the way. -Josh > On Nov 13, 2021, at 11:53 AM, Michael Richardson <mcr+ietf@sandelman.ca> wrote: > > > Thank you for the reply! > > Josh Coalson <v0idstar at icloud dot com> wrote: >> Hi Michael, I’m glad you were able to reach me. It should be no >> problem. I’m not aware of compatible licenses; can you refer me to >> license requirements or some example licenses used by similar projects? > > Alas, due to lack of universal/Bern-convention Trademark protections, the > IETF has a non-free copyright on RFCs. Basically, this keeps people from > copying and modifying RFCs and claiming that the result is the original. > It's stupid. In countries with trademark protection, we'd simply trademark > the names "RFCxxxx", but that doesn't work in a lot of non-G7 countries. > The result is that RFCs are not-DFSG compatible, but I'm unable to change this. > > We need you to agree to dual-license the documentation text for flac under a > BSD or MIT or Apache license. Currently, it's under a GPL Documentation > license. Whomever brought the work (first uploaded it), didn't realize that > there was a conflict. > > https://github.com/ietf-wg-cellar/flac-specification <https://github.com/ietf-wg-cellar/flac-specification> > > As a significant part of the original text is yours, we'd like to credit you > as an author. But, that doesn't have to involving doing much, as long as you > are available during the final stages to confirm you haven't got any > undeclared patents on the techniques. > > (If you don't want to agree to dual-license, then we have to start over and > write text from scratch...) > >>> Hi, my name is Michael Richardson. >>> I'm co-chair of the IETF CELLAR WG. >>> https://datatracker.ietf.org/wg/cellar >>> >>> I'm trying to reach Josh Coalson about the copyright on the documentation to >>> the FLAC encoder. >>> A number of people of have tried to reach via xiph.org and failed. >>> >>> We specifically want to ask if you'll relicense the original document in a >>> form that can be turned in an RFC. >>> Also, if you'd like to be listed as a co-author. >>> >>> -- Michael Richardson <mcr+IETF@sandelman.ca> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide
- Re: [Cellar] IETF work on FLAC (fwd) Josh Coalson… Michael Richardson