On Mon Jun 18 11:42:05 2007, Simon Josefsson wrote:
Several people consider this license insufficient to make it
possible to
include extracted material from RFCs into some implementations.
Given your reading, and given that the same thing must apply to MIBs
(which are explicitly used as an example), then it seems to me that
virtually every SNMP implementation would be in violation of the
copyright license, since MIBs are very commonly extracted from RFCs,
often with errata patched in, and used as input to implementations,
either directly or indirectly (by being used in MIB compilers and
suchlike to create compilable code).
Now, BCP78 doesn't cover third party rights - its title is pretty
clear on that - but it still includes section 7.5, at least, and more
importantly it requires that the rights you're seeking are allowed to
be granted by the IETF Trust, and the IETF Trust itself certainly
appears to be granting them, such as in the answer to Question 6 and
7 at http://trustee.ietf.org/24.html
Modulo a clarifying statement to the contrary from the IETF Trust,
I'd say I've been explicitly granted rights to snarf the ABNF from
anywhere I choose and slap it straight into my implementation,
including the ABNF from RFC2192bis, and supporting documents.
This isn't to say it's a waste of time to get all this a little
clearer, but I don't see how bogging down every document containing
ABNF in legal tangles is going to help.
Dave.
--
Dave Cridland - mailto:dave(_at_)cridland(_dot_)net -
xmpp:dwd(_at_)jabber(_dot_)org
- acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
- http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf