Re: [tlp-interest] [IAB] Boilerplate changes Required for TLP 4.0

Julian Reschke <julian.reschke@gmx.de> Thu, 14 January 2010 08:58 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: tlp-interest@core3.amsl.com
Delivered-To: tlp-interest@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 850AA3A6938 for <tlp-interest@core3.amsl.com>; Thu, 14 Jan 2010 00:58:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.25
X-Spam-Level:
X-Spam-Status: No, score=-3.25 tagged_above=-999 required=5 tests=[AWL=-0.651, 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 zpogTj810dtK for <tlp-interest@core3.amsl.com>; Thu, 14 Jan 2010 00:58:44 -0800 (PST)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id DDE4D3A6936 for <tlp-interest@ietf.org>; Thu, 14 Jan 2010 00:58:43 -0800 (PST)
Received: (qmail invoked by alias); 14 Jan 2010 08:52:00 -0000
Received: from p508FFD25.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.253.37] by mail.gmx.net (mp046) with SMTP; 14 Jan 2010 09:52:00 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18suc1nz2As1Q3csc7ld4tU0uJ7IB97Jwif/AHtu/ me6j2Fl/rmaFBU
Message-ID: <4B4EDB2A.3070004@gmx.de>
Date: Thu, 14 Jan 2010 09:51:54 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
References: <964DF240-EEC4-45BA-94ED-295E9C9FEF9E@americafree.tv> <4B4E2A3A.3050505@gmail.com> <4B4E3E2F.3070400@vigilsec.com>
In-Reply-To: <4B4E3E2F.3070400@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.67
Cc: Trustees <trustees@ietf.org>, Working Group Chairs <wgchairs@ietf.org>, tlp-interest@ietf.org, Internet Research Steering Group <irsg@isi.edu>, RFC Interest <rfc-interest@rfc-editor.org>, IAB <iab@iab.org>, IESG <iesg@ietf.org>
Subject: Re: [tlp-interest] [IAB] Boilerplate changes Required for TLP 4.0
X-BeenThere: tlp-interest@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of proposed revisions to the Trust Legal Provisions <tlp-interest.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tlp-interest>, <mailto:tlp-interest-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tlp-interest>
List-Post: <mailto:tlp-interest@ietf.org>
List-Help: <mailto:tlp-interest-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tlp-interest>, <mailto:tlp-interest-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jan 2010 08:58:44 -0000

Russ Housley wrote:
> Brian:
> 
> The most recent approved changes do not prevent the posting of I-Ds. For 
> this reason, I do not understand your comments.
> 
> The most recent changes allow non-IETF stream RFCs to include different 
> license for code; they rejected the Simplified BSD license that the 
> tools team recommended to the Trust for the IETF stream.  I-Ds for these 
> streams can be posted using the earlier boilerplate, as they have been 
> for the last several months.  When the tools are updated, I-Ds for these 
> alternate streams will have alternate boilerplate if they wish to use 
> it, but they will not be required to use it to get their I-D posted.
> ...

Exactly *which* previous boilerplate?

The boilerplate as of 2009-02 can't be produced by xml2rfc.tcl for new 
IDs, as it decides on the boilerplate based on the publication date.

The boilerplate as of 2008-11 never could be produced by xml2rfc.tcl.

I may be missing something; maybe you should post a sample source for 
xml2rfc.tcl that produces the boilerplate that is needed?

Best regards, Julian