At 9:58 AM +0200 9/9/08, Simon Josefsson wrote: >I suggest to remove the newly added text, making section 4.c read: > > c. License. Code Components are hereby licensed to each person > who wishes to receive such a license on the terms of the "BSD > License", as follows: > >Without this change, I believe it is not sufficiently clear that code >components are _only_ licensed under the BSD license. Fully agree. >Thus, I suggest to change the above sentence to: > > b. Identification. Text in IETF Contributions and IETF > Documents of the types identified in Section 4.a above shall > constitute "Code Components". In addition, any text found > between the markers <CODE BEGINS> and <CODE ENDS> shall be > considered a "Code Component". Alternatively, text in the > document that refer to this rule can be added to denote which > portions are intended to be regarded as Code Components. > >You could also revert to the earlier text used in the 08-05-08 and >08-13-08 version: > > b. Identification. For ease of reference, Code Components in > IETF RFCs MUST be clearly identified as code, and one technique > for clearly identifying it is <CODE BEGINS> <CODE ENDS>. Either sounds good, and the latter is more in line with IETF history. >One final comment: > >#3: > >For good style, attribute the origin of the BSD license text used. If >the IETF requests of others to attribute origins of work, setting a good >example helps. According to Jorge in ><http://permalink.gmane.org/gmane.ietf.ipr/5379> the source is: >http://www.opensource.org/licenses/bsd-license.php Eating our own dogfood: good. --Paul Hoffman, Director --VPN Consortium _______________________________________________ Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf