[Disman] Fw: Boilerplate changes Required for TLP 4.0

"Randy Presuhn" <randy_presuhn@mindspring.com> Wed, 13 January 2010 18:49 UTC

Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: disman@core3.amsl.com
Delivered-To: disman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C5F2628C134; Wed, 13 Jan 2010 10:49:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 mqlTnqGeU9bQ; Wed, 13 Jan 2010 10:49:42 -0800 (PST)
Received: from elasmtp-curtail.atl.sa.earthlink.net (elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) by core3.amsl.com (Postfix) with ESMTP id 7ED2828C111; Wed, 13 Jan 2010 10:49:42 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=Yb1dk3rBnp02JbhKopAIkvCbBAvqakOxzxIEcLZ/belASbuZjTmkUc+L4PJP6P4F; 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 [76.254.49.211] (helo=oemcomputer) by elasmtp-curtail.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1NV8Hj-0001uX-IZ; Wed, 13 Jan 2010 13:49:39 -0500
Message-ID: <008801ca9481$9a2ccdc0$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, 13 Jan 2010 10:52:47 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888494b88d665f13b40f6800d4dac5defdd281aeb94907e9363350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 76.254.49.211
Subject: [Disman] Fw: Boilerplate changes Required for TLP 4.0
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/disman>, <mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/disman>, <mailto:disman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2010 18:49:43 -0000

Hi -

Forwarded for your information.

Randy

----- Original Message ----- 
> From: "Marshall Eubanks" <tme@americafree.tv>
> To: <tlp-interest@ietf.org>
> Cc: "Trustees" <trustees@ietf.org>rg>; "Working Group Chairs" <wgchairs@ietf.org>rg>; "Internet Research Steering Group" <irsg@isi.edu>du>;
"RFC Interest" <rfc-interest@rfc-editor.org>
> Sent: Wednesday, January 13, 2010 3:47 AM
> Subject: Boilerplate changes Required for TLP 4.0
>
> Colleagues,
>
> Some concerns have been raised about tooling issues and boilerplate
> changes. At present, for example, xml2rfc is not supported, and
> because of this it is not clear when it will be possible to update it
> to support the new boilerplate.  However, Alternate Stream documents
> have been blocked for some time waiting for the new Trust Legal
> Provisions (TLP), and it was decided to unblock these documents with
> TLP 4.0 even in the absence of xml2rfc support. (There is an open call
> for volunteers to support xml2rfc, and I would encourage interested
> parties to contact Russ Housley.)
>
>      The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
>      NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and
>      "OPTIONAL" in this document are to be interpreted as described in
>      RFC 2119.
>
> If for any reason the tool of your choice has not been upgraded by the
> end of the grace period on February 1 then the following two minor
> changes need to be made to Internet-Draft boilerplates before
> submission. Note that the changes are different for IETF Stream and
> for Alternate Stream Documents. The changes for the IETF stream are
> editorial (as noted by a SHOULD in the text below) and drafts produced
> by the current tools for that stream are therefore compliant with TLP
> 4.0.  The changes for the other streams are required (as noted by a
> MUST in the text below).
>
> -----
>
> For IETF Stream Documents the following changes SHOULD be made :
>
> Change 1 :
> OLD:
> This Internet-Draft is submitted to IETF in full conformance with the
> provisions of BCP 78 and
> BCP 79.
>
> NEW:
> This Internet-Draft is submitted in full conformance with the
> provisions of BCP 78 and BCP 79.
>
> EXPLANATION:
> Dropped the words "to IETF" as there is some ambiguity with respect to
> Internet drafts that are not submitted to be published as IETF Stream
> RFCs.
>
> Change 2 :
>
> Second : Different Treatment for IETF and non-IETF stream documents
> regarding potential BSD licenses for code components.
>
> OLD:
> Code Components extracted from this document must include Simplified
> BSD License text as described in Section 4.e of the Trust Legal
> Provisions and are provided without warranty as described in the BSD
> License.
>
> NEW:
> Code Components extracted from this document must include Simplified
> BSD License text as described in Section 4.e of the Trust Legal
> Provisions and are provided without warranty as described in the
> Simplified BSD License.
>
> EXPLANATION: Introduction of the word "Simplified" at the second use
> of "BSD License" for clarity.
>
> -----
>
> For Alternate Stream Documents the following changes MUST be made
>
> Change 1 :
> OLD:
> This Internet-Draft is submitted to IETF in full conformance with the
> provisions of BCP 78 and
> BCP 79.
>
> NEW:
> This Internet-Draft is submitted in full conformance with the
> provisions of BCP 78 and BCP 79.
>
> EXPLANATION:
> Dropped the words "to IETF" as there is some ambiguity with respect to
> Internet drafts that are not submitted to be published as IETF Stream
> RFCs.
>
> Change 2 :
>
> OLD:
> Code Components extracted from this document must include Simplified
> BSD License text as described in Section 4.e of the Trust Legal
> Provisions and are provided without warranty as described in the BSD
> License.
>
> NEW: This sentence must not be included (note that this text MUST NOT
> be inserted in the document).
>
> EXPLANATION: The BSD license is not available for code components from
> Alternate Stream documents.
>
> Regards
> Marshall Eubanks
>