--On Tuesday, January 27, 2015 10:37 -0500 Sam Hartman
<hartmans-ietf@xxxxxxx> wrote:
>>>>>> "John" == John C Klensin <john-ietf@xxxxxxx> writes:
>
> John> Tobias,
>
> John> IANAL (other disclaimers incorporated by
> hand-waving), but a John> plain-English reading of this
> indicated that the text gives John> permission to modify
> the text of the template itself. That John> raises all of
> the issues that caused us to try to make John> enforceable
> copyright claims on the RFC series in the first John>
> place-- someone could use such derived text (maliciously or
> John> not) to mislead others about IETF statements, intent, and
> John> requirements.
>
> I'd like to specifically disagree with John and say that I'd
> like to see the trust be very liberal in grating license
> exceptions when the IETF purposes are served.
> There are significant costs to asking the trust to be more
> liberal when we discover that our needs are not met by our
> licensing. I have always disagreed that there is significant
> harm that will happen if people modify IETF documents
> especially if those modifications are labeled.
>...
Just to close the loop, my hope was that the trust would
consider the advantages and disadvantages of a policy broad
enough to allow people to reproduce _and_ modify the templates
in non-IETF / non-IANA contexts. Sam has explained (thoroughly
and well, IMO) the advantages.
However, when I combine his position with several of the other
comments that have been made, I wonder whether the right policy
would be to take us back to just about where were were long
before we started making strong copyright claims about RFCs and
certainly before several IPR WG efforts and the IETF Trust came
into being and started making very specific policies. That
ancient policy was, in essence, "do what you like with RFCs but
please acknowledge and, if you making excerpts and/or changes,
be very clear about what you have done and how it relates to the
original in your acknowledgments".
I have _very_ mixed feelings whether that policy or the current
"need to ask permission except for a list of exception cases
that keeps getting longer and more complicated" policy (noting
the comments about why the "template" policy needs to be
different from the "code" policy) is the better one, but I hope
that the IETF Trust is asking that question again each time a
requirement for a new, and time consuming, policy tweak comes
up. Part of that question, which I'm sure the Trust has
considered but on which it has not briefed the community, is how
egregious or harmful a violation would have to be before
presumably-limited resources were spent trying to mount an
enforcement action.
john