![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Contreras, Jorge wrote:
Hmm... seems to me that there is a release required for the derivative work here right?Just as a simple "for example": what is the set of names that needs to be posted just to cover all of the boilerplate text we're required to put in ourdocuments?The boilerplate text is owned by the IETF Trust. No author permissions are needed.
Todd Glassey
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. _______________________________________________ Ietf mailing list Ietf at ietf.org https://www.ietf.org/mailman/listinfo/ietf ------------------------------------------------------------------------ Internal Virus Database is out of date.Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.9.18/1850 - Release Date: 12/15/2008 5:04 PM
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.