[BEHAVE] FW: Several ways you can publish I-Ds with pre 5378 content - TODAY

"Dan Wing" <dwing@cisco.com> Tue, 24 February 2009 05:59 UTC

Return-Path: <dwing@cisco.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 316C028C0ED for <behave@core3.amsl.com>; Mon, 23 Feb 2009 21:59:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.505
X-Spam-Status: No, score=-6.505 tagged_above=-999 required=5 tests=[AWL=0.094, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id unvLQN2DxDFX for <behave@core3.amsl.com>; Mon, 23 Feb 2009 21:59:48 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com []) by core3.amsl.com (Postfix) with ESMTP id A0A933A692A for <behave@ietf.org>; Mon, 23 Feb 2009 21:59:48 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.38,257,1233532800"; d="scan'208";a="134604186"
Received: from sj-dkim-4.cisco.com ([]) by sj-iport-2.cisco.com with ESMTP; 24 Feb 2009 06:00:07 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com []) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n1O607TW011958 for <behave@ietf.org>; Mon, 23 Feb 2009 22:00:07 -0800
Received: from dwingwxp01 ([]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n1O607i4019804 for <behave@ietf.org>; Tue, 24 Feb 2009 06:00:07 GMT
From: Dan Wing <dwing@cisco.com>
To: behave@ietf.org
Date: Mon, 23 Feb 2009 22:00:05 -0800
Message-ID: <112f01c99645$23da03d0$c2f0200a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: AcmWBOTVmUru7T5rQYiIKxx0DQC2YwAP+a7w
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3103; t=1235455207; x=1236319207; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dwing@cisco.com; z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com> |Subject:=20FW=3A=20Several=20ways=20you=20can=20publish=20 I-Ds=20with=20pre=205378=20content=20-=20TODAY |Sender:=20; bh=Hvv70jW4tFNjmmCYHuVjW1NS3BuQgIRYwvuHZOaAWc8=; b=lFMS+iHKbaL7pwk9VfqI3VCJUwcjuRXMBw7L7mmtofbusIRhhrzeHCvcPd PLObNRETr+g5RSbCbHzboE2KyKBqQv7pAEjA3TrLAZbPSU8WJUjY5jKS6XMx 3/UOmuRD8a;
Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
Subject: [BEHAVE] FW: Several ways you can publish I-Ds with pre 5378 content - TODAY
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Feb 2009 05:59:53 -0000

In the event anyone has been holding publication due to the RFC5378 issue the
summary (below) explains several mechanisms to publish a draft with the
RFC5378 workaround text.

(Forwarding to BEHAVE because I expect many don't follow the main IETF list.)


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Cullen
Sent: Monday, February 23, 2009 2:19 PM
To: Working Group Chairs; IETF discussion list
Subject: Several ways you can publish I-Ds with pre 5378 content - TODAY

Method 1: (Not recommended)

Go read the BCP and Trust statement and edit your .txt to have the  
right text.

Method 2: (Recommended for people using word template)

Go look at a draft that did work, such as

And copy the Copyright Notice section into your draft

Method 3: XML2RFC approach recommended for folks that run xml2rfc  

Get the very hacked version at

This will soon be obsoleted when the real xml2rfc tool gets updated.  
Don't worry, Julian, Bill, and Marshal are working on that. They will  
produce something much better than my hack of xml2rfc

Set the ipr attribute in the <rfc> element to ipr="pre5378Trust200902"  
and it will produce a txt file that id submission tool will accept.

Method 4: XML2RFC approach for folks that run xml2rfc on the web

Use the experimental version from http://xml.resource.org/experimental.html 
. You can download the zip or tgz file on this page or use the online  
version at this page.

Make sure you have

<?rfc strict="no" ?>
somewhere above the <rfc> element.
In the <rfc> element, set the ipr attribute to ipr="trust200811"
Change your abstract to use a note. Do this by changing
<abstract> <t> This draft is about ... </t> </abstract>
<note title="Abstract"><t> This draft is about ...</t> </note>
And before this not insert a note like
<note title=""> <t> This document may contain material from IETF  
Documents or IETF Contributions published or made publicly available  
before November 10, 2008. The person(s) controlling the copyright in  
some of this material may not have granted the IETF Trust the right to  
allow modifications of such material outside the IETF Standards  
Process. Without obtaining an adequate license from the person(s)  
controlling the copyright in such materials, this document may not be  
modified outside the IETF Standards Process, and derivative works of  
it may not be created outside the IETF Standards Process, except to  
format it for publication as an RFC or to translate it into languages  
other than English. </t> </note>

You can seen the XML for an example I-D that does this at

That should work - good luck

Ietf mailing list