Re: Differences between RFC4944 as distributed by tools.ietf and datatracker.ietf / rfc-editor

2011-03-28 Thread RFC Editor
Greetings,

Just to clarify, please note that the version available
in the RFC Editor repository
(http://www.rfc-editor.org/rfc/rfc4944.txt) is dated 24 Sept 2007, and
the RFC was announced on 25 Sept 2007.  The document has not been
altered or updated since it was published.

Please let us know if you have any questions.

Thank you.

RFC Editor


On Sun, Mar 27, 2011 at 12:34:20PM +0200, Henrik Levkowetz wrote:
> Hi,
>
> (I only now became aware of this thread.  Bob Hinden forwarded the original
> message to me, but I didn't note at the time that it was a list message.)
>
> Anyway, here's the story:
>
> The tools site never overwrites existing RFCs, so if it would happen that
> a RFC by mistake had been placed in the RFC Editor's repository with the
> wrong text, any correction put in place after the tools site had done the
> initial download would not be overwritten.  I assumed that's what happened
> here, and moved the first tools out of the way so that a new copy was
> downloaded from the RFC Editor's repository.
>
> I was in a rush at that time, however, preparing for the Saturday code sprint,
> so I didn't take care to make the .pdf and .html copies be regenerated, which
> is of course needed.  Done now, which takes care of the first part of the
> comment below:
>
> On 2011-03-27 03:00 Mathieu Goessens said the following:
>> Thanks to the one who corrected it.
>>
>> The html are pdf version are also wrong:
>> http://tools.ietf.org/html/rfc4944
>> http://tools.ietf.org/pdf/rfc4944
>
> Fixed.
>
>> The drafts are also wrong, both in txt, html and pdf:
>> http://tools.ietf.org/html/draft-ietf-6lowpan-format-13
>> http://tools.ietf.org/id/draft-ietf-6lowpan-format-13.txt
>> http://tools.ietf.org/pdf/draft-ietf-6lowpan-format-13.txt
>> (I did not check the older versions)
>
> However, this I don't understand.  Drafts are never edited after being
> submitted, so the explanation for how there could be 2 different copies
> of the RFC doesn't apply here.  Furthermore, for the drafts above, I
> don't see links to two conflicting copies -- in which way do you mean
> that the drafts "are also wrong"?
>
>> Any information about the problem ? It is limited to this RFC or can it
>> appears in some others ?
>
> I've come across I think two previous instances of the tools site grabbing
> an early copy of an RFC, which was corrected before being announced, and I
> handled that in the same way as this case.  The RFC editor's copy is always
> the correct one, the way I see it.  I'm about to do a run across all of the
> RFCs now on tools.ietf.org to see if there are any other cases of this.
>
>
> Regards,
>
>   Henrik
>   perpetrator of (almost) all things tools.ietf.org   
>
>
>> On 25/03/2011 21:48, Adrian Farrel wrote:
>>> [Copying the RFC Editor to let them also check their records]
>>>
>>> Note that the IANA registry is consistent with
>>> http://www.rfc-editor.org/rfc/rfc4944.txt
>>>
>>> Adrian
>>>
>>>
>>>> -Original Message-
>>>> From: ietf-boun...@ietf.org [mailto:ietf-boun...@ietf.org] On Behalf Of
>>>> Mathieu Goessens
>>>> Sent: 25 March 2011 21:33
>>>> To: Paul Hoffman
>>>> Cc: 6low...@ietf.org; ietf@ietf.org
>>>> Subject: Re: Differences between RFC4944 as distributed by tools.ietf and
>>>> datatracker.ietf / rfc-editor
>>>>
>>>> On 25/03/2011 20:12, Paul Hoffman wrote:
>>>>
>>>>> On Mar 25, 2011, at 6:24 PM, Mathieu Goessens wrote:
>>>>>
>>>>>
>>>>>
>>>>>> Hi folks,
>>>>>>
>>>>>> The RFC4944 looks to be different in the version distributed by
>>>>>>
>>> tools.ietf.org
>>>
>>>> and datatracker.ietf.org / rfc-editor.org.
>>>>
>>>>>> The figure 2 looks truncated on the tools.ietf.org version:
>>>>>>
>>>>>> http://tools.ietf.org/rfc/rfc4944.txt
>>>>>> http://www.rfc-editor.org/rfc/rfc4944.txt
>>>>>>
>>>>>> Do you know what is the problem ? Document generation problem ? Where it
>>>>>>
>>>> should be reported ?
>>>>
>>>>>>
>>>>> These two documents were clearly derived from very different sources: the
>>>>>
>>>> page breaks are also quite different.
>>>>
>>>>> How on earth did that happen
>>>>>
>>>> I am not that sure: the page break is different precisely starting from
>>>> this figure.
>>>>
>>>> I was more thinking about a different version of configuration of the
>>>> xml2rfc software.
>>>>
>>>> Regards,
>>>>
>>>> --
>>>> Mathieu Goessens
>>>> IRISA, Campus de Beaulieu, 35042 Rennes cedex, France
>>>> Tel: +33 (0) 2 99 84 71 00, Fax: +33 (0) 2 99 84 71 71
>>>>
>>>> ___
>>>> Ietf mailing list
>>>> Ietf@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/ietf
>>>>
>>>
>>
___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf


Re: [rfc-i] Important: do not publish "draft-iab-streams-headers-boilerplates-08" as is!

2009-11-24 Thread RFC Editor
Hi Julian,

I went through version -08 of the headers-boilerplates document and
attempted to put together all of the possible combinations of text for
the "Status of This Memo."   I believe the attached file is a complete
list of these possibilities, based on the text in Section 3.   

Please note that I have updated the URLs to match that of the existing
metadata pages that were created in response to this document
(http://www.rfc-editor.org/info/rfc).  

The RFC Editor hopes that the IAB will agree to update the URLs
(throughout) and the text in Appendix A to reflect the appropriate
text from the corresponding Stream/Status/Consensus in the attached
file during the editing process.  

Please feel free to check the attached files, as manual error is
possible.

Hope this is of some help! Thanks!

Sandy


On Tue, Nov 24, 2009 at 02:01:56PM +0100, Julian Reschke wrote:
> Hi,
> 
> I just created five test cases representing the appendices A.1 to A.5. 
> Turns out that the text in the examples is not in sync with the 
> definitions in Section 3 (see, for instance, 
> <http://greenbytes.de/tech/webdav/rfc2629xslt/samples/sample.ipr.rfc.hab.a2.test.xhtml>).
> 
> Best regards, Julian
> 
> Julian Reschke wrote:
> > Julian Reschke wrote:
> >>
> >> <http://tools.ietf.org/html/draft-iab-streams-headers-boilerplates-08#section-3.2.3>
> >>  
> >> says:
> >>
> >>"Information about the current status of this document, any errata,
> >>and how to provide feedback on it may be obtained at
> >>http://www.rfc-editor.org//rfc.html"
> >>
> >> Can we please recommend *not* to put a file extension into the URL?
> >>
> >> BR, Julian
> >> ...
> > 
> > Hi,
> > 
> > in the meantime I have finished a prototype implementation of the new 
> > boilerplate in rfc2629.xslt (*not* xml2rfc!). The implementation is 
> > available from <http://greenbytes.de/tech/webdav/rfc2629xslt.zip>, and 
> > requires the use of two new extension Processing Instructions to enable 
> > the new boilerplate:
> > 
> >   
> >   
> > 
> > (where the first enables the new format, while the second provides the 
> > information about whether there was consensus, something the current 
> > xml2rfc format doesn't provide).
> > 
> > I haven't found any problems in addition to what was reported before, 
> > except for a trailing dot in one of the boilerplate statements, and 
> > cases of repeating sentence beginnings -- maybe all of this can be fixed 
> > during AUTH48 (although I'd prefer to see this in a new draft for 
> > community review).
> > 
> > For the record, here's a complete summary:
> > 
> > -- snip --
> > 3.1.  The title page header
> > 
> >  This describes the area where the work originates.
> >   Historically, all RFCs were labeled Network Working Group.
> >   "Network Working Group" refers to the original version of today's
> >   IETF when people from the original set of ARPANET sites and
> >   whomever else was interested -- the meetings were open -- got
> >   together to discuss, design and document proposed protocols
> >   [RFC0003].  Here, we obsolete the term "Network Working Group" in
> >   order to indicate the originating stream.
> > 
> >   The  is the name of the RFC stream, as defined in
> >   [RFC4844] and its successors.  At the time of this publication,
> >   the streams, and therefore the possible entries are:
> > 
> >   *  Internet Engineering Task Force
> > 
> >   *  Internet Architecture Board
> > 
> >   *  Internet Research Task Force
> > 
> >   *  Independent
> > 
> > JRE: as discussed earlier: should this be "Independent Submission"
> > instead of "Independent"?
> > 
> >[:]  Some relations between RFCs in the
> >   series are explicitly noted in the RFC header.  For example, a new
> >   RFC may update one or more earlier RFCs.  Currently two
> >   relationships are defined: "Updates", and "Obsoletes" [RFC2223].
> >   Variants like "Obsoleted by" are also used (e.g in [RFC5143]).
> >   Other types of relationships may be defined by the RFC Editor and
> >   may appear in future RFCs.
> > 
> > JRE: "Obsoleted By" is not a variant of "Obsoletes" or "Updates".
> > 
> > 3.2.2.  Paragraph 2
> > 
> >The second paragraph of the "Status of T