Re: Proposed Revisions to the IETF Trust Legal Provisions (TLP)
Russ Housley <housley@vigilsec.com> Tue, 23 June 2009 13:37 UTC
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5F7CD28C342; Tue, 23 Jun 2009 06:37:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.616
X-Spam-Level:
X-Spam-Status: No, score=-102.616 tagged_above=-999 required=5 tests=[AWL=-0.017, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GZkE2lTtHtph; Tue, 23 Jun 2009 06:37:28 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id 59E2128C32C; Tue, 23 Jun 2009 06:37:28 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id ACA53F2400A; Tue, 23 Jun 2009 09:37:57 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id 4psSBDfITH7C; Tue, 23 Jun 2009 09:37:43 -0400 (EDT)
Received: from THINKPADR52.vigilsec.com (pool-96-241-154-102.washdc.fios.verizon.net [96.241.154.102]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id D9335F24005; Tue, 23 Jun 2009 09:37:55 -0400 (EDT)
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 23 Jun 2009 09:37:40 -0400
To: ietf@ietf.org
From: Russ Housley <housley@vigilsec.com>
Subject: Re: Proposed Revisions to the IETF Trust Legal Provisions (TLP)
In-Reply-To: <B7008260-2BA6-4529-B4F6-1D0D3D9E7AEA@americafree.tv>
References: <B7008260-2BA6-4529-B4F6-1D0D3D9E7AEA@americafree.tv>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Message-Id: <20090623133755.D9335F24005@odin.smetech.net>
Cc: trustees@ietf.org, iab@iab.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jun 2009 13:37:30 -0000
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, Russ --- 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) (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. 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 >documents > >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 >IESG. > >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, > >Marshall Eubanks >IETF Trust Chair
- Proposed Revisions to the IETF Trust Legal Provis… Marshall Eubanks
- Re: [IAB] Proposed Revisions to the IETF Trust Le… John C Klensin
- Re: Proposed Revisions to the IETF Trust Legal Pr… Simon Josefsson
- Re: Proposed Revisions to the IETF Trust Legal Pr… Russ Housley
- Re: Proposed Revisions to the IETF Trust Legal Pr… John C Klensin
- RE: [Trustees] Proposed Revisions to the IETF Tru… Contreras, Jorge
- Re: Proposed Revisions to the IETF Trust Legal Pr… Simon Josefsson
- Re: [Trustees] Proposed Revisions to the IETF Tru… Andrew Sullivan
- RE: Proposed Revisions to the IETF Trust Legal Pr… Yaakov Stein
- Re: Proposed Revisions to the IETF Trust Legal Pr… Joel M. Halpern
- Re: Proposed Revisions to the IETF Trust Legal Pr… Simon Josefsson
- RE: Proposed Revisions to the IETF Trust Legal Pr… Yaakov Stein
- Re: Proposed Revisions to the IETF Trust Legal Pr… Sam Hartman
- RE: [Trustees] [IAB] Proposed Revisions to the IE… Contreras, Jorge
- Re: Proposed Revisions to the IETF Trust Legal Pr… Robert Elz
- Re: Proposed Revisions to the IETF Trust Legal Pr… Tom.Petch
- Re: Proposed Revisions to the IETF Trust Legal Pr… Tom.Petch
- Re: Proposed Revisions to the IETF Trust Legal Pr… Simon Josefsson
- RE: [Trustees] [IAB] Proposed Revisions to the IE… John C Klensin
- Re: Proposed Revisions to the IETF Trust Legal Pr… John C Klensin
- Re: [Trustees] Proposed Revisions to the IETF Tru… Scott O. Bradner
- Re: [Trustees] Proposed Revisions to the IETF Tru… Scott O. Bradner
- Re: [Trustees] Proposed Revisions to the IETF Tru… Marshall Eubanks
- Re: [Trustees] Proposed Revisions to the IETF Tru… Marshall Eubanks
- Appeal/Request for Review (was: Re: Proposed Revi… John C Klensin
- Re: [Trustees] Proposed Revisions to the IETF Tru… Brian E Carpenter
- Re: [Trustees] Proposed Revisions to the IETF Tru… Marshall Eubanks
- Re: [IAB] [Trustees] Proposed Revisions to the IE… Russ Housley
- Re: [IAB] [Trustees] Proposed Revisions to the IE… Doug Ewell
- Re: [IAB] [Trustees] Proposed Revisions to the IE… Russ Housley
- Re: [Trustees] Proposed Revisions to the IETF Tru… Scott O. Bradner
- Re: [Trustees] Proposed Revisions to the IETF Tru… Henk Uijterwaal
- Re: [Trustees] Proposed Revisions to the IETF Tru… Scott O. Bradner
- Re: [Trustees] Proposed Revisions to the IETF Tru… Doug Ewell
- Re: [Trustees] Proposed Revisions to the IETF Tru… Ray Pelletier
- Re: [Trustees] Proposed Revisions to the IETF Tru… John C Klensin
- Re: [Trustees] Proposed Revisions to the IETF Tru… Henk Uijterwaal
- Re: [Trustees] Proposed Revisions to the IETF Tru… Henk Uijterwaal
- Re: [Trustees] Proposed Revisions to the IETF Tru… Scott O. Bradner
- Re: [Trustees] Proposed Revisions to the IETF Tru… John C Klensin
- Re: [Trustees] Proposed Revisions to the IETF Tru… Scott O. Bradner
- Re: [Trustees] Proposed Revisions to the IETF Tru… Eliot Lear
- Re: [Trustees] Proposed Revisions to the IETF Tru… Fred Baker
- Re: [Trustees] Proposed Revisions to the IETF Tru… Pete Resnick
- Re: [Trustees] Proposed Revisions to the IETF Tru… Henk Uijterwaal
- Re: Appeal/Request for Review (was: Re: Proposed … Margaret Wasserman
- Re: Appeal/Request for Review (was: Re: Proposed … Russ Housley
- Re: Appeal/Request for Review (was: Re: Proposed … Marshall Eubanks