Re: [MIB-DOCTORS] FW: IESG Statement on Copyright

There are a number of issues that gathered around 4181 that would
deserve attention if a willing editor is found. 

Dan
 

> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of C. M. Heard
> Sent: Tuesday, September 22, 2009 12:48 AM
> To: MIB Doctors (E-mail)
> Cc: OPS Area (E-mail)
> Subject: Re: [MIB-DOCTORS] FW: IESG Statement on Copyright
> 
> Greetings,
> 
> It seems to me that the new IESG statement on MIB and PIB 
> module copyrights obsoletes Section 3.7 of RFC 4181 
> (Guidelines for Authors and Reviewers of MIB Documents) and 
> all of RFC 4841 (RFC 4181 Update to Recognize the IETF 
> Trust).  If the cycles exist to do it, someone should write a 
> short RFC to update RFC 4181 and to obsolete RFC 4841, or 
> even better, issue an upated version of the mib guidelines 
> that obsoletes both 4181 and 4841.
> 
> Just in case anyone should ask, I'm stil retired from MIB 
> work, and I don't have the cycles to do it myself.
> 
> Best regards,
> 
> Mike Heard
> 
> On Thu, 17 Sep 2009, Romascanu, Dan (Dan) wrote:
> > -----Original Message-----
> > From: [email protected] [mailto:[email protected]] 
> On Behalf 
> > Of IESG Secretary
> > Sent: Wednesday, September 09, 2009 10:45 PM
> > To: [email protected]
> > Cc: [email protected]; [email protected]
> > Subject: IESG Statement on Copyright
> > 
> > This IESG Statement obsoletes all earlier IESG Statements regarding 
> > Copyright statements in MIB and PIB Modules.
> > 
> > The IESG is providing this guidance to align current 
> practice with RFC 
> > 5377, RFC 5378, and the resulting IETF Trust Legal Provisions (TLP) 
> > (http://trustee.ietf.org/license-info).
> > 
> > IETF Contributions and IETF Documents often include code components 
> > that are intended to be directly processed by a computer. 
> Examples of 
> > such code components include ABNF definitions, XML Schemas, 
> XML DTDs, 
> > XML RelaxNG definitions, tables of values, MIBs, PIBs, ASN.1, and 
> > classical programming source code. The IETF Trust maintains 
> a list of 
> > code component types. A link to this list can be found on this web
> > page: http://trustee.ietf.org/license-info.
> > 
> > In addition to the code component types listed, any text 
> found between 
> > the markers <CODE BEGINS> and <CODE ENDS> shall be 
> > considered a code component. Authors may wish to use these 
> markers as 
> > clear delimiters of code components.
> > 
> > Authors are encouraged to collect code into a separate section or 
> > appendix.
> > 
> > The TLP requires copyright notice in IETF Documents, but not 
> > necessarily in each code component within an IETF Document. Authors 
> > may choose to include a copyright notice as a comment when a 
> > significant amount of code is collected together. For 
> example, authors 
> > may include a copyright notice in a comment as part of an 
> ASN.1 module 
> > or a representation of a classical programming language 
> file. If IETF 
> > Document authors choose to include a code component 
> copyright notice 
> > comment, they must follow the guidance in Section 6.d of the TLP.
> > Implementors that extract any code component from the IETF Document 
> > must include the BSD license text as described in Section 
> 4.e of the TLP.
> > 
> _______________________________________________
> MIB-DOCTORS mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/mib-doctors
>