[Pce] NOTE WELL: New Boilerplate Text Required for all new Submissions to IETF

"Adrian Farrel" <adrian@olddog.co.uk> Wed, 12 November 2008 00:08 UTC

Return-Path: <pce-bounces@ietf.org>
X-Original-To: pce-archive@megatron.ietf.org
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CB41128C163; Tue, 11 Nov 2008 16:08:59 -0800 (PST)
X-Original-To: pce@core3.amsl.com
Delivered-To: pce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9AACB28C163 for <pce@core3.amsl.com>; Tue, 11 Nov 2008 16:08:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
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 zAWVr0tuxwbz for <pce@core3.amsl.com>; Tue, 11 Nov 2008 16:08:57 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by core3.amsl.com (Postfix) with ESMTP id 6693D28C150 for <pce@ietf.org>; Tue, 11 Nov 2008 16:08:57 -0800 (PST)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id mAC08oxj032032 for <pce@ietf.org>; Wed, 12 Nov 2008 00:08:50 GMT
Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp2.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id mAC08nDc032019 for <pce@ietf.org>; Wed, 12 Nov 2008 00:08:50 GMT
Message-ID: <22094062BE0D47819B63D64BA3E17776@your029b8cecfe>
From: Adrian Farrel <adrian@olddog.co.uk>
To: pce@ietf.org
Date: Wed, 12 Nov 2008 00:08:46 -0000
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Subject: [Pce] NOTE WELL: New Boilerplate Text Required for all new Submissions to IETF
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/pce>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

Note well. Your I-Ds will not be posted unless they conform to new 
boiler-plate requirements.

Adrian
----- Original Message ----- 
From: "Ed Juskevicius" <edj@nortel.com>
To: "IETF Discussion" <ietf@ietf.org>; <ietf-announce@ietf.org>; 
<ipr-wg@ietf.org>; <iesg@ietf.org>; <iab@iab.org>; "RFC Editor" 
<rfc-editor@rfc-editor.org>; <wgchairs@ietf.org>
Cc: <trustees@ietf.org>
Sent: Tuesday, November 11, 2008 11:03 PM
Subject: Announcement: New Boilerplate Text Required for all new 
Submissionsto IETF


> Greetings.  This message is to draw your attention to the significance
> of the publication of RFC5377 and RFC5378 earlier today.
>
> * RFC5377 is Advice to the Trustees of the IETF Trust on Rights to Be
> Granted in IETF Documents
> * RFC5378 is Rights Contributors Provide to the IETF Trust
>
> Note that RFC5378 is also BCP0078.  RFC5378 is an update to RFC2026, and
> RFC5378 obsoletes both RFC3978 and RFC4748.
>
> Coincident with the above, the IETF Trustees have posted a new policy
> document with guidance to the community on:
> * Legal Provisions Relating to IETF Documents at
> http://trustee.ietf.org/license-info/
>
> Taken as a set, the documents listed above specify changes that are now
> required in all new submissions into the IETF.
>
> Henrik Levkowetz has updated the idnit tool and AMS have updated the
> Internet-Draft submission tool to reflect the new requirements.  An
> update to the xml2rfc has been requested.
>
> Please review the "Legal Provisions Relating to IETF Documents" and
> RFC5378 to discover the new boilerplate text that is now required.
> Please also take action to update the tools you use for creating your
> documents.
>
> New submissions using either the old or the new boilerplate text will be
> accepted starting today, until 01h00 UTC on December 16th, 2008.  After
> this cutoff date, all new submissions will be required to use ONLY the
> new boilerplate text.  All submissions using old boilerplate text after
> the cutoff date will be rejected.
>
> Regards and FYI.
>
>
> Ed Juskevicius
> IETF Trust Chair
> edj@nortel.com
>
>
> p.s. - Don't be surprised if you see periodic reminders about this as we
> approach December 16th.
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 

_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce