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

Marshall Eubanks <tme@multicasttech.com> Mon, 23 February 2009 23:09 UTC

Return-Path: <tme@multicasttech.com>
X-Original-To: mboned@core3.amsl.com
Delivered-To: mboned@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D4DEF28C229 for <mboned@core3.amsl.com>; Mon, 23 Feb 2009 15:09:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.574
X-Spam-Level:
X-Spam-Status: No, score=-103.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 ISihk-JH3gEo for <mboned@core3.amsl.com>; Mon, 23 Feb 2009 15:09:21 -0800 (PST)
Received: from multicasttech.com (lennon.multicasttech.com [63.105.122.7]) by core3.amsl.com (Postfix) with ESMTP id 91CB03A6837 for <mboned@ietf.org>; Mon, 23 Feb 2009 15:09:18 -0800 (PST)
Received: from [63.105.122.7] (account marshall_eubanks HELO [IPv6:::1]) by multicasttech.com (CommuniGate Pro SMTP 3.4.8) with ESMTP-TLS id 14757328 for mboned@ietf.org; Mon, 23 Feb 2009 18:07:36 -0500
Message-Id: <326026A8-0180-4059-8C22-EBCAAB263D60@multicasttech.com>
From: Marshall Eubanks <tme@multicasttech.com>
To: mboned@ietf.org
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 23 Feb 2009 18:09:36 -0500
References: <BAC42C76-BC6E-4FBE-85CB-98353B697CBE@cisco.com>
X-Mailer: Apple Mail (2.930.3)
Subject: [MBONED] Fwd: Several ways you can publish I-Ds with pre 5378 content - TODAY
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Feb 2009 23:09:22 -0000

The ID tools are supposed to be updated soon, but in case you don't  
want to wait...

Note that this applies to text with inclusions dated prior to November  
10, 2008. Entirely new drafts do not
need to worry about any of this.

Regards
Marshall

Begin forwarded message:

> From: Cullen Jennings <fluffy@cisco.com>
> Date: February 23, 2009 5:19:13 PM EST
> To: Working Group Chairs <wgchairs@ietf.org>, IETF discussion list <ietf@ietf.org 
> >
> 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
> http://tools.ietf.org/html/draft-jennings-http-srv-01
>
> And copy the Copyright Notice section into your draft
>
>
>
> Method 3: XML2RFC approach recommended for folks that run xml2rfc  
> locally
>
> Get the very hacked version at
> http://svn.resiprocate.org/rep/ietf-drafts/xml2rfc/1.34pre2-fluffy/xml2rfc.tcl
>
> 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>
> To
> <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
> http://svn.resiprocate.org/rep/ietf-drafts/fluffy/example.xml
>
> That should work - good luck
>
>
>
>
>
>
>
>
>
>
>
>