The IESG has prepared a draft statement as a companion
document. Since the two are related, the IESG would like the
community to comment on the two documents at the same time.
On behalf of the IESG,
--- Draft IESG Statement ---
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)
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
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
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.
At 01:32 AM 6/23/2009, Marshall Eubanks wrote:
The IETF Trustees invite your comments on the proposed revisions to
the "Legal Provisions Relating to IETF Documents" (TLP) policy. The
proposed revisions are in rtf, pdf and doc formats and located at:
http://trustee.ietf.org/policyandprocedures.html under Draft
Policies and Procedures for IETF Documents.
This is a summary of the proposed revisions:
2.e -- the review period for TLP changes has been changed from 30 to
14 days, which is consistent with the last-call period for other IETF
2.f -- this new language describes the conditions under which the IETF
Trust will assume licensing and copyright responsibility for IAB, IRTF
and Independent Stream submissions, should the managers of those
streams request that it do so.
4.a -- the URL for the list of Code Components has been updated
4.c -- clarifies that the BSD License may not be applied to Code
Components that come from IETF Documents as to which the Contributor
has prohibited the making of derivative works.
4.e -- this new section clarifies the legend requirements for Code
Components that are used in software under the BSD License. In short,
the user must include the full BSD License text or a shorter pointer
to it (which is set forth in Section 6.d)
6 -- the language regarding placement of legends on IETF Documents has
been clarified. Placement on the "first page" is no longer required,
and authority for placement of the legends is with the RFC Editor and
6.a - the words "to IETF" have been removed, to enable submission to
IAB, IRFT and other streams.
6.b -- a new sentence has been added to the legend that must be placed
on all IETF Documents, pointing out the BSD License requirements
described in 4.e above and emphasizing that code in IETF Documents
comes without any warranty, as described in the BSD License.
6.c -- some minor clean-up edits
6.d -- the BSD legend/pointer described in 4.e above
7.a -- correction of capitalization
Please accept this message as a formal request by the IETF Trustees
for your review and feedback on the proposed revision to the TLP
document. The comment period will end on July 20, 2009.
I expect the Trustees will decide on whether to adopt this revision
shortly after July 20, 2009.
Regards, and thanks in advance,
IETF Trust Chair
Ietf mailing list