At 03:01 28-03-2008, Simon Josefsson wrote:
Regarding -outbound section 4.3:
As such, the rough consensus is that the IETF Trust is to grant
rights such that code components of IETF contributions can be
extracted, modified, and used by anyone in any way desired. To
enable the broadest possible extraction, modification and usage, the
IETF Trust should avoid adding software license obligations beyond
those already present in a contribution. The granted rights to
extract, modify and use code should allow creation of derived works
outside the IETF that may carry additional license obligations.
I believe the intention here is good, but it leaves the IETF Trust with
no guidelines on how to write the license declaration that is likely to
work well in practice with actual products. There are no reference to
what "open source" means in this context, and references to "free
software" is missing.
The above are guidelines. You'll get a different definition of what
"open source" or "free software" is depending on whom you ask. The
words "enable the broadest possible extraction, modification and
usage" provides more scope.
To give the Trust something concrete to work with I propose to add the
To make sure the granted rights are usable in practice, they need to
at least meet the requirements of the Open Source Definition [OSD],
the Free Software Definition [FSD], and the Debian Free Software
These are not guidelines; they are requirements.
IETF mailing list