Clarification below.
At 06:16 AM 6/18/2007, Dave Cridland wrote:
On Mon Jun 18 08:30:00 2007, Simon Josefsson wrote:
> If you do believe the ABNF needs special licensing in
> this case, I am sorry to say that your remedy is not sufficient.
This
> document imports ABNF from other documents (from RFC 3986,
> to take one important example). Those documents do not have
> anything like what you suggest.
I disagree, I think they do have what Simon's suggesting. But then,
I think RFC2192bis does, as well.
Given existing wording, it is somewhere between an extremely good
idea and necessary to indicate that the ABNF and the code (and yes, I
agree with Simon that it needs to apply to both) can be extracted and
modified as necessary by anyone. And while we are trying to solve
this for the future, that unfortunately can not help current documents.
My only caveat is that the wording suggested by Simon does much more,
and it is not necessary to go that far to meet the requirements. An
indication that says that those specific parts can be extracted,
modified, and used for any and all derivative works would
suffice. (I am not a lawyer and I am not going to try to write license terms.)
Yours,
Joel
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf