Re: [Errata Rejected] RFC7234 (4334)

Mark Nottingham <mnot@mnot.net> Tue, 14 April 2015 00:25 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 892561B2B72 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 13 Apr 2015 17:25:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.912
X-Spam-Level:
X-Spam-Status: No, score=-6.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 Y7ouL7zD9Moi for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 13 Apr 2015 17:25:38 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 15D4B1B2B64 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 13 Apr 2015 17:25:38 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1YhocJ-0002Vy-D0 for ietf-http-wg-dist@listhub.w3.org; Tue, 14 Apr 2015 00:22:15 +0000
Resent-Date: Tue, 14 Apr 2015 00:22:15 +0000
Resent-Message-Id: <E1YhocJ-0002Vy-D0@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.80) (envelope-from <mnot@mnot.net>) id 1YhocF-0002Uz-QA for ietf-http-wg@listhub.w3.org; Tue, 14 Apr 2015 00:22:11 +0000
Received: from mxout-07.mxes.net ([216.86.168.182]) by maggie.w3.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from <mnot@mnot.net>) id 1YhocA-00079W-Jr for ietf-http-wg@w3.org; Tue, 14 Apr 2015 00:22:11 +0000
Received: from [192.168.0.16] (unknown [120.149.147.132]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 5DC0322E262; Mon, 13 Apr 2015 20:21:42 -0400 (EDT)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <552C5CEE.4030405@att.com>
Date: Tue, 14 Apr 2015 10:21:40 +1000
Cc: HTTP <ietf-http-wg@w3.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <0BF1F67D-3685-4C51-94C0-090D2879E1DE@mnot.net>
References: <20150413034357.4AABA180092@rfc-editor.org> <61AEEB7C-6554-47BA-82DC-22E94820F6C5@mnot.net> <552C5CEE.4030405@att.com>
To: Tony Hansen <tony@att.com>
X-Mailer: Apple Mail (2.2098)
Received-SPF: pass client-ip=216.86.168.182; envelope-from=mnot@mnot.net; helo=mxout-07.mxes.net
X-W3C-Hub-Spam-Status: No, score=-7.3
X-W3C-Hub-Spam-Report: AWL=0.404, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: maggie.w3.org 1YhocA-00079W-Jr 5b3cc2a49674e5244c1cb22d8f06f8b7
X-Original-To: ietf-http-wg@w3.org
Subject: Re: [Errata Rejected] RFC7234 (4334)
Archived-At: <http://www.w3.org/mid/0BF1F67D-3685-4C51-94C0-090D2879E1DE@mnot.net>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/29331
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

Aha. Thanks, Tony.

Cheers,


> On 14 Apr 2015, at 10:18 am, Tony Hansen <tony@att.com> wrote:
> 
> I have a feeling that this is not a problem with the document, but instead with the tooling.
> 
> That is, the missing piece of information is which HTML-ized version of the document was Antonio Vera looking at?
> 
> If he was looking at http://tools.ietf.org/html/rfc7234, then yup, it's pointing at the wrong document. The htmlizer tool on tools.ietf.org picked up the "Section ..." text and made that into a link to the section within the current document.
> 
> However, if he was looking at the files in github, he would have seen a link to the proper document.
> 
> 
> So I think there is nothing that needs to be done here by anyone in the http group. But it might be worth poking Henrik to take a look at the rfcmarkup tool to see if an improvement can be made.
> 
> OR, anyone else can take a look at the rfcmarkup code and see if they can come up with a code fix. I'm sure Henrik would love to buy it back.
> 
>    Tony Hansen
> 
> On 4/13/15 7:51 PM, Mark Nottingham wrote:
>> Antonio,
>> 
>> Thanks for noticing that. I suspect that Julian will correct it in our online source at:
>>   https://github.com/httpwg/http11bis
>> .. and it'll filter through to the places where we can get it in time.
>> 
>> If you like, you can raise an issue here:
>>   https://github.com/httpwg/http11bis/issues
>> 
>> Cheers,
>> 
>> 
>> 
>>> On 13 Apr 2015, at 1:43 pm, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
>>> 
>>> The following errata report has been rejected for RFC7234,
>>> "Hypertext Transfer Protocol (HTTP/1.1): Caching".
>>> 
>>> --------------------------------------
>>> You may review the report below and at:
>>> http://www.rfc-editor.org/errata_search.php?rfc=7234&eid=4334
>>> 
>>> --------------------------------------
>>> Status: Rejected
>>> Type: Editorial
>>> 
>>> Reported by: Antonio Vera <antonio.ignacio.vera@gmail.com>
>>> Date Reported: 2015-04-12
>>> Rejected by: Barry Leiba (IESG)
>>> 
>>> Section: 5.3
>>> 
>>> Original Text
>>> -------------
>>> The Expires value is an HTTP-date timestamp, as defined in Section
>>>   7.1.1.1 of [RFC7231].
>>> 
>>> Corrected Text
>>> --------------
>>> The Expires value is an HTTP-date timestamp, as defined in Section
>>>   7.1.1.1 of [RFC7231].
>>> 
>>> Notes
>>> -----
>>> There's no error in the text itself, but the address of the link in 7.1.1.1 is pointing to a hashtag in RFC 7234, not RFC 7231 as it should.
>>> 
>>> Currently, 7.1.1.1 points to: http://tools.ietf.org/html/rfc7234#section-7.1.1.1
>>> It should point to: http://tools.ietf.org/html/rfc7231#section-7.1.1.1
>>> --VERIFIER NOTES--
>>> The RFC Editor has nothing to do with the HTML versions on tools.ietf.org, which are unofficial versions, with the HTML conversion on a best-effort basis.
>>> 
>>> --------------------------------------
>>> RFC7234 (draft-ietf-httpbis-p6-cache-26)
>>> --------------------------------------
>>> Title               : Hypertext Transfer Protocol (HTTP/1.1): Caching
>>> Publication Date    : June 2014
>>> Author(s)           : R. Fielding, Ed., M. Nottingham, Ed., J. Reschke, Ed.
>>> Category            : PROPOSED STANDARD
>>> Source              : Hypertext Transfer Protocol Bis
>>> Area                : Applications
>>> Stream              : IETF
>>> Verifying Party     : IESG
>>> 
>> --
>> Mark Nottingham   https://www.mnot.net/
>> 
>> 
> 

--
Mark Nottingham   https://www.mnot.net/