Re: List moderator action

On Sat, May 2, 2026 at 2:01 PM Brian E Carpenter <
[email protected]> wrote:

> On 03-May-26 07:32, Rob Sayre wrote:
> > Hi,
> >
> > Apologies in advance for being a giant pain.
> >
> > Lars Eggert <[email protected] <mailto:[email protected]>> wrote:
> >  > If you read Section 3.3 of RFC 5378 you will find the “specific
> context” is about documents.
> >
> > It is not. It is about "Contributions" in caps.
> >
> > While I agree with the goal of the IESG statement, and the moderator
> actions here, we have to go fix RFC 5378 for this one.
>
> What needs fixing? It says that the IETF requires the right to make
> derivative works of all contributions, which includes emails.
>
> The final paragraph of section 3.3 allows "no derivative works" legends
> only for two special cases: "information about proprietary technologies"
> and republishing standards from other SDOs. Most emails are neither of
> those cases; therefore "no derivative works" legends are forbidden.
>

This is the worst. The RFC 5378, Section 3.3 says:

"In both of the above cases, in which the production of derivative works is
excluded,
 the Contributor must include a special legend in the Contribution, as
 specified in the Legend Instructions, in order to notify IETF
 participants about this restriction."

Then, one must consult Section 1.a, where we find the definition of
"Contribution".

It sucks. We should fix the RFC.

sorry again,
Rob