On Aug 11, 2020, at 11:32 AM, James Bottomley [off-list ref] wrote:

On Tue, 2020-08-11 at 10:48 -0400, Chuck Lever wrote:

quoted

quoted

On Aug 11, 2020, at 1:43 AM, James Bottomley
[off-list ref] wrote:
On Mon, 2020-08-10 at 19:36 -0400, Chuck Lever wrote:

[...]

quoted

quoted

quoted

Thanks for the help! I just want to emphasize that documentation
(eg, a specification) will be critical for remote filesystems.

If any of this is to be supported by a remote filesystem, then we
need an unencumbered description of the new metadata format
rather than code. GPL-encumbered formats cannot be contributed to
the NFS standard, and are probably difficult for other
filesystems that are not Linux-native, like SMB, as well.

I don't understand what you mean by GPL encumbered formats.  The
GPL is a code licence not a data or document licence.

IETF contributions occur under a BSD-style license incompatible
with the GPL.

https://trustee.ietf.org/trust-legal-provisions.html

Non-Linux implementers (of OEM storage devices) rely on such
standards processes to indemnify them against licensing claims.

Well, that simply means we won't be contributing the Linux
implementation, right?

At the present time, there is nothing but the Linux implementation.
There's no English description, there's no specification of the
formats, the format is described only by source code.

The only way to contribute current IMA metadata formats to an open
standards body like the IETF is to look at encumbered code first.
We would effectively be contributing an implementation in this case.

(I'm not saying the current formats should or should not be
contributed; merely that there is a legal stumbling block to doing
so that can be avoided for newly defined formats).

Well, let me put the counterpoint: I can write a book about how linux
device drivers work (which includes describing the data formats)

Our position is that someone who reads that book and implements those
formats under a non-GPL-compatible license would be in breach of the
GPL.

The point of the standards process is to indemnify implementing
and distributing under _any_ license what has been published by the
standards body. That legally enables everyone to use the published
protocol/format in their own code no matter how it happens to be
licensed.

Fine, good grief, people who take a sensible view of this can write the
data format down and publish it under any licence you like then you can
pick it up again safely.

That's what I proposed. Write it down under the IETF Trust legal
provisions license. And I volunteered to do that.

All I'm saying is that description needs to come before code.


--
Chuck Lever
chucklever@gmail.com