[Ltru] Fw: IESG Statement on Copyright

"Randy Presuhn" <randy_presuhn@mindspring.com> Wed, 09 September 2009 20:05 UTC

Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: ltru@core3.amsl.com
Delivered-To: ltru@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 6AEC128B797; Wed, 9 Sep 2009 13:05:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.14
X-Spam-Status: No, score=-1.14 tagged_above=-999 required=5 tests=[AWL=1.459, BAYES_00=-2.599]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id mRK7NQ9dd1Pu; Wed, 9 Sep 2009 13:05:20 -0700 (PDT)
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net []) by core3.amsl.com (Postfix) with ESMTP id 781B23A6963; Wed, 9 Sep 2009 13:05:20 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=g9SqiXLyLcfllbQMJ+YTVUmCzstxDC5q7gFpxz8U+c4YSPzZc42AaUfj35wkzl5W; h=Received:Message-ID:From:To:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [] (helo=oemcomputer) by elasmtp-kukur.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1MlTQN-0002fb-Ck; Wed, 09 Sep 2009 16:05:51 -0400
Message-ID: <000401ca3188$f3f4cb20$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <agentx@ietf.org>, "Disman" <disman@ietf.org>, "LTRU Working Group" <ltru@ietf.org>
Date: Wed, 9 Sep 2009 13:05:59 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8881afdcb5313ff34f95335002d8bdbe8996a78cebe1d3c87a8350badd9bab72f9c350badd9bab72f9c
Subject: [Ltru] Fw: IESG Statement on Copyright
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ltru>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Sep 2009 20:05:21 -0000

Hi -

Fwd FYI.


----- Original Message ----- 
> From: "IESG Secretary" <iesg-secretary@ietf.org>
> To: <ietf-announce@ietf.org>
> Cc: <wgchairs@ietf.org>rg>; <ietf@ietf.org>
> Sent: Wednesday, September 09, 2009 12:45 PM
> 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 &lt;CODE BEGINS&gt; and &lt;CODE ENDS&gt; 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.