--On Thursday, 18 December, 2008 17:37 -0500 "Contreras, Jorge"
<Jorge.Contreras@xxxxxxxxxxxxxx> wrote:
>> As a slightly harder example: what is the set of names
>> required to cover
>> all the boilerplate text that goes into an RFC containing a
>> MIB module?
>
> See above. In addition, MIB modules were licensed broadly
> under RFC 3978, so they are less problematic than non-code
> text.
Maybe I still don't fully understand what 5398 does, but, while
that broad licensing of MIB modules presumably permits the IETF
(and others) to work with them, it doesn't imply the transfers
to the Trust, and ability of the Trust to relicense, required by
5398, does it? And, if not, the broad licensing of MIB modules
doesn't help a new author of a document that incorporates a MIB
module make the assertions that 5398 requires, does it?
If the answer is "no", then such an author would still have to
go back to the original Contributor(s) of the MIB module and
persuade them to generate the new license, just as he or she
would with any other older contributed text. Right?
john
_______________________________________________
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf