Lawrence Rosen wrote:
...
The notion is not right, albeit that it is reflected in the current IETF IPR
policy, that a process can be in any way restricted from being improved
because someone planted a copyright notice on its essential description. An
description of a process, method of operation, etc., cannot be locked away
and prevented from amendment and improvement because of copyright. Allowing
that would subject our functional process specifications in IETF to 100-year
copyright monopolies even though there aren't even 20-year patent monopolies
that apply to that specification. Nobody owns those ideas or the essential
descriptions of those ideas; they are public domain.
So my answer to Sam's question is: I dare anyone to try and stop you or me
from taking an IETF RFC and revising it as necessary to express any new
idea, procedure, process, system, method of operation, concept, principle,
or discovery. And I dare anyone to try and stop IETF or any other standards
organization from adopting such an improvement as a revised RFC because of a
copyright notice.
...
So, in the process of doing this, can I use the original RFC text?
Best regards, Julian
PS: would I need sign off from all previous contributors for the IDs I
posted in November, <draft-ietf-httpbis-p*>? How do I find out who these
contributors are in case they are not listed as authors?
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf