Re: [xml2rfc] Some ID references require version, some don't
Robert Moskowitz <rgm@htt-consult.com> Thu, 28 January 2016 18:48 UTC
Return-Path: <rgm@htt-consult.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B25BA1B2F8F for <xml2rfc@ietfa.amsl.com>; Thu, 28 Jan 2016 10:48:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TKwtw55lCBl2 for <xml2rfc@ietfa.amsl.com>; Thu, 28 Jan 2016 10:48:12 -0800 (PST)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [50.253.254.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0B031B2F94 for <xml2rfc@ietf.org>; Thu, 28 Jan 2016 10:48:10 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 05BAD615E4; Thu, 28 Jan 2016 13:48:09 -0500 (EST)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 3ukQvC1R9+uH; Thu, 28 Jan 2016 13:48:03 -0500 (EST)
Received: from lx120e.htt-consult.com (unknown [192.168.160.20]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id C8D2B62188; Thu, 28 Jan 2016 13:48:02 -0500 (EST)
To: "HANSEN, TONY L" <tony@att.com>, William Atwood <william.atwood@concordia.ca>, "xml2rfc@ietf.org" <xml2rfc@ietf.org>
References: <56AA464A.3080004@htt-consult.com> <56AA5374.20107@concordia.ca> <581DCCD0-3A83-4C5E-B90B-EEE0E5EA289F@att.com> <56AA576B.9020003@concordia.ca> <56AA5B7E.80808@htt-consult.com> <376DDDC2-BBBF-41C3-A069-D8DAC30FA811@att.com>
From: Robert Moskowitz <rgm@htt-consult.com>
Message-ID: <56AA6261.90405@htt-consult.com>
Date: Thu, 28 Jan 2016 13:48:01 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <376DDDC2-BBBF-41C3-A069-D8DAC30FA811@att.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/xml2rfc/r_gPQFbnmOFUSEBS0oOs8h1Q7UE>
Subject: Re: [xml2rfc] Some ID references require version, some don't
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2016 18:48:15 -0000
On 01/28/2016 01:28 PM, HANSEN, TONY L wrote: > Change <?rfc include="reference.I-D.draft-moskowitz-sse.xml”?> to <?rfc include=“reference.I-D.moskowitz-sse.xml”?> > > (The series names do not start with “draft-”. Got it! I read your earlier response backwards. I will blame my dyslexia. :) One more thing learned and cleaned up. > > > > On 1/28/16, 1:18 PM, "Robert Moskowitz" <rgm@htt-consult.com> wrote: > >> Does not seem to work. >> >> I changed: >> >> <?rfc include="reference.I-D.draft-moskowitz-sse-01.xml"?> >> >> >> <?rfc include="reference.I-D.draft-moskowitz-sse.xml"?> >> >> and got: >> >> Unable to Validate File >> >> ERROR: Unable to parse the XML document: INPUT >> INPUT: Line 331: Unable to resolve external request: >> "reference.I-D.draft-moskowitz-sse.xml" >> >> Using >> XML_LIBRARY=/home/www/tools.ietf.org/tools/xml2rfc/web/public/rfc/bibxml:/home/www/tools.ietf.org/tools/xml2rfc/web/public/rfc/bibxml2:/home/www/tools.ietf.org/tools/xml2rfc/web/public/rfc/bibxml3:/home/www/tools.ietf.org/tools/xml2rfc/web/public/rfc/bibxml4:/home/www/tools.ietf.org/tools/xml2rfc/web/public/rfc/bibxml5:/home/www/tools.ietf.org/tools/xml2rfc/web/public/rfc/bibxml6 >> Parsing file INPUT >> Resolving entity... >> /usr/local/lib/python2.7/dist-packages/xml2rfc-2.5.1.dev0-py2.7.egg/xml2rfc/templates/rfc2629.dtd >> Resolving entity... >> /usr/local/lib/python2.7/dist-packages/xml2rfc-2.5.1.dev0-py2.7.egg/xml2rfc/templates/rfc2629-xhtml.ent >> Resolving entity... >> /usr/local/lib/python2.7/dist-packages/xml2rfc-2.5.1.dev0-py2.7.egg/xml2rfc/templates/rfc2629-other.ent >> Resolving entity... >> /usr/local/lib/python2.7/dist-packages/xml2rfc-2.5.1.dev0-py2.7.egg/xml2rfc/templates/rfc2629.dtd >> Resolving entity... >> /usr/local/lib/python2.7/dist-packages/xml2rfc-2.5.1.dev0-py2.7.egg/xml2rfc/templates/rfc2629-xhtml.ent >> Resolving entity... >> /usr/local/lib/python2.7/dist-packages/xml2rfc-2.5.1.dev0-py2.7.egg/xml2rfc/templates/rfc2629-other.ent >> Resolving include... >> /home/www/tools.ietf.org/tools/xml2rfc/web/public/rfc/bibxml/reference.RFC.2119.xml >> Resolving include... >> /home/www/tools.ietf.org/tools/xml2rfc/web/public/rfc/bibxml/reference.RFC.1421.xml >> Resolving include... >> /home/www/tools.ietf.org/tools/xml2rfc/web/public/rfc/bibxml/reference.RFC.2784.xml >> Resolving include... >> /home/www/tools.ietf.org/tools/xml2rfc/web/public/rfc/bibxml/reference.RFC.3095.xml >> Resolving include... >> /home/www/tools.ietf.org/tools/xml2rfc/web/public/rfc/bibxml/reference.RFC.4303.xml >> Resolving include... >> /home/www/tools.ietf.org/tools/xml2rfc/web/public/rfc/bibxml/reference.RFC.5996.xml >> Resolving include... >> /home/www/tools.ietf.org/tools/xml2rfc/web/public/rfc/bibxml/reference.RFC.7401.xml >> Resolving include... >> /home/www/tools.ietf.org/tools/xml2rfc/web/public/rfc/bibxml3/reference.I-D.draft-ietf-dots-requirements-00.xml >> Resolving include... >> http://xml2rfc.ietf.org/public/rfc/bibxml/reference.I-D.draft-moskowitz-sse.xml >> URL retrieval failed with status code 404 for >> 'http://xml2rfc.ietf.org/public/rfc/bibxml/reference.I-D.draft-moskowitz-sse.xml' >> Resolving include... >> http://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.I-D.draft-moskowitz-sse.xml >> URL retrieval failed with status code 404 for >> 'http://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.I-D.draft-moskowitz-sse.xml' >> Resolving include... >> http://xml.resource.org/public/rfc/bibxml/reference.I-D.draft-moskowitz-sse.xml >> URL retrieval failed with status code 404 for >> 'http://xml2rfc.ietf.org/public/rfc/bibxml/reference.I-D.draft-moskowitz-sse.xml' >> Resolving include... >> http://xml2rfc.ietf.org/public/rfc/bibxml2/reference.I-D.draft-moskowitz-sse.xml >> URL retrieval failed with status code 404 for >> 'http://xml2rfc.ietf.org/public/rfc/bibxml2/reference.I-D.draft-moskowitz-sse.xml' >> Resolving include... >> http://xml2rfc.tools.ietf.org/public/rfc/bibxml2/reference.I-D.draft-moskowitz-sse.xml >> URL retrieval failed with status code 404 for >> 'http://xml2rfc.tools.ietf.org/public/rfc/bibxml2/reference.I-D.draft-moskowitz-sse.xml' >> Resolving include... >> http://xml.resource.org/public/rfc/bibxml2/reference.I-D.draft-moskowitz-sse.xml >> URL retrieval failed with status code 404 for >> 'http://xml2rfc.ietf.org/public/rfc/bibxml2/reference.I-D.draft-moskowitz-sse.xml' >> Resolving include... >> http://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-moskowitz-sse.xml >> URL retrieval failed with status code 404 for >> 'http://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-moskowitz-sse.xml' >> Resolving include... >> http://xml2rfc.tools.ietf.org/public/rfc/bibxml3/reference.I-D.draft-moskowitz-sse.xml >> URL retrieval failed with status code 404 for >> 'http://xml2rfc.tools.ietf.org/public/rfc/bibxml3/reference.I-D.draft-moskowitz-sse.xml' >> Resolving include... >> http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-moskowitz-sse.xml >> URL retrieval failed with status code 404 for >> 'http://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-moskowitz-sse.xml' >> Resolving include... >> http://xml2rfc.ietf.org/public/rfc/bibxml4/reference.I-D.draft-moskowitz-sse.xml >> URL retrieval failed with status code 404 for >> 'http://xml2rfc.ietf.org/public/rfc/bibxml4/reference.I-D.draft-moskowitz-sse.xml' >> Resolving include... >> http://xml2rfc.tools.ietf.org/public/rfc/bibxml4/reference.I-D.draft-moskowitz-sse.xml >> URL retrieval failed with status code 404 for >> 'http://xml2rfc.tools.ietf.org/public/rfc/bibxml4/reference.I-D.draft-moskowitz-sse.xml' >> Resolving include... >> http://xml.resource.org/public/rfc/bibxml4/reference.I-D.draft-moskowitz-sse.xml >> URL retrieval failed with status code 404 for >> 'http://xml2rfc.ietf.org/public/rfc/bibxml4/reference.I-D.draft-moskowitz-sse.xml' >> Resolving include... >> http://xml2rfc.ietf.org/public/rfc/bibxml5/reference.I-D.draft-moskowitz-sse.xml >> URL retrieval failed with status code 404 for >> 'http://xml2rfc.ietf.org/public/rfc/bibxml5/reference.I-D.draft-moskowitz-sse.xml' >> Resolving include... >> http://xml2rfc.tools.ietf.org/public/rfc/bibxml5/reference.I-D.draft-moskowitz-sse.xml >> URL retrieval failed with status code 404 for >> 'http://xml2rfc.tools.ietf.org/public/rfc/bibxml5/reference.I-D.draft-moskowitz-sse.xml' >> Resolving include... >> http://xml.resource.org/public/rfc/bibxml5/reference.I-D.draft-moskowitz-sse.xml >> URL retrieval failed with status code 404 for >> 'http://xml2rfc.ietf.org/public/rfc/bibxml5/reference.I-D.draft-moskowitz-sse.xml' >> >> >> On 01/28/2016 01:01 PM, William Atwood wrote: >>> Aha, >>> >>> I missed the need for "draft-" when looking for a specific version. >>> >>> Thank you for the confirmation. >>> >>> Bill >>> >>> On 28/01/2016 12:50 PM, HANSEN, TONY L wrote: >>>> Bill, you are correct. References to individual versions are available using “reference.I-D.draft-....” names, and references to the “latest and greatest” are available using “reference.I-D....” names. >>>> >>>> Tony >>>> >>>> >>>> >>>> On 1/28/16, 12:44 PM, "xml2rfc on behalf of William Atwood" <xml2rfc-bounces@ietf.org on behalf of william.atwood@concordia.ca> wrote: >>>> >>>>> Robert, >>>>> >>>>> I believe that it is the choice of the writer of the document. If you >>>>> put the include without the version number, you will get the latest one, >>>>> i.e., it will "automatically" update to the most recent one, each time >>>>> that you compile. >>>>> >>>>> If you put the specific version, it will always bring up exactly that. >>>>> The only time that this is useful is when you have to refer to a >>>>> specific version of the draft. (For example, when taking about >>>>> something that has been deleted from some later version.) >>>>> >>>>> Bill >>>>> >>>>> On 28/01/2016 11:48 AM, Robert Moskowitz wrote: >>>>>> I have just noticed that some ID references do not need the version >>>>>> number. For example: >>>>>> >>>>>> <?rfc include="reference.I-D.ietf-hip-rfc4423-bis.xml"?> >>>>>> >>>>>> where as others need the version: >>>>>> >>>>>> <?rfc include="reference.I-D.draft-ietf-dots-requirements-00.xml"?> >>>>>> <?rfc include="reference.I-D.draft-kivinen-ipsecme-oob-pubkey-14.xml"?> >>>>>> >>>>>> Why is that? What has to be done so that version number is not needed? >>>>>> >>>>>> thanks
- [xml2rfc] Some ID references require version, som… Robert Moskowitz
- Re: [xml2rfc] Some ID references require version,… William Atwood
- Re: [xml2rfc] Some ID references require version,… HANSEN, TONY L
- Re: [xml2rfc] Some ID references require version,… William Atwood
- Re: [xml2rfc] Some ID references require version,… Robert Moskowitz
- Re: [xml2rfc] Some ID references require version,… HANSEN, TONY L
- Re: [xml2rfc] Some ID references require version,… Robert Moskowitz
- Re: [xml2rfc] Some ID references require version,… Brian E Carpenter