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

"t.petch" <daedulus@btconnect.com> Mon, 28 March 2011 10:38 UTC

Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 790D43A68F3 for <ietf@core3.amsl.com>; Mon, 28 Mar 2011 03:38:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.839
X-Spam-Level:
X-Spam-Status: No, score=-1.839 tagged_above=-999 required=5 tests=[AWL=0.160, BAYES_00=-2.599, J_CHICKENPOX_54=0.6]
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 wc-qB3sNfS+r for <ietf@core3.amsl.com>; Mon, 28 Mar 2011 03:38:49 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr07.btconnect.com [213.123.20.125]) by core3.amsl.com (Postfix) with ESMTP id 47A523A6838 for <ietf@ietf.org>; Mon, 28 Mar 2011 03:38:48 -0700 (PDT)
Received: from host217-44-145-1.range217-44.btcentralplus.com (HELO pc6) ([217.44.145.1]) by c2bthomr07.btconnect.com with SMTP id CMA07924; Mon, 28 Mar 2011 11:40:06 +0100 (BST)
Message-ID: <007601cbed2c$0edb7b40$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: Henrik Levkowetz <henrik@levkowetz.com>, Mathieu Goessens <mathieu.goessens@irisa.fr>
References: <4D8CCFBC.9030909@irisa.fr> <3B1740F1-6CFB-4D93-BE63-C34CD8DFDA70@vpnc.org> <4D8CFBEB.3010304@irisa.fr> <01db01cbeb2e$1311d5b0$39358110$@olddog.co.uk><4D8E8C41.5090104@irisa.fr> <4D8F12AC.2050000@levkowetz.com>
Subject: Re: Differences between RFC4944 as distributed by tools.ietf anddatatracker.ietf / rfc-editor
Date: Mon, 28 Mar 2011 11:39:34 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Neutral-1, source=Queried, refid=tid=0001.0A0B0302.4D906585.0054, actions=TAG
X-Junkmail-Status: score=10/50, host=c2bthomr07.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0204.4D906589.02C2, ss=1, fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=single engine
X-Junkmail-IWF: false
Cc: adrian@olddog.co.uk, rfc-editor@rfc-editor.org, ietf@ietf.org, 'Paul Hoffman' <paul.hoffman@vpnc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Mar 2011 10:38:52 -0000

----- Original Message -----
From: "Henrik Levkowetz" <henrik@levkowetz.com>
To: "Mathieu Goessens" <mathieu.goessens@irisa.fr>
Cc: <adrian@olddog.co.uk>; <6lowpan@ietf.org>; <ietf@ietf.org>; "'Paul Hoffman'"
<paul.hoffman@vpnc.org>; <rfc-editor@rfc-editor.org>
Sent: Sunday, March 27, 2011 12:34 PM
Subject: Re: Differences between RFC4944 as distributed by tools.ietf
anddatatracker.ietf / rfc-editor


> 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"?
>

Perhaps an XML to RFC issue:-)

Up to -06 (Nov 2006), each packet format was a separate numbered figure.

>From -07, the one line formats at the start of the document were no longer
given the caption 'Figure nn'  but still contributed to the running count of
figure numbers, so the first numbered figure was Figure 7.  This persisted
until -13 after which the RFC Editor put things 'right' in the RFC as published.

Tom Petch




> > 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-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> >>> Mathieu Goessens
> >>> Sent: 25 March 2011 21:33
> >>> To: Paul Hoffman
> >>> Cc: 6lowpan@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