- From: RFC Errata System <rfc-editor@rfc-editor.org>
- Date: Fri, 10 Nov 2017 20:05:40 -0800 (PST)
- To: tbray@textuality.com, ben@nostrum.com, aamelnikov@fastmail.fm, adam@nostrum.com, mnot@mnot.net, pmcmanus@mozilla.com
- Cc: bortzmeyer+ietf@nic.fr, ietf-http-wg@w3.org, rfc-editor@rfc-editor.org
The following errata report has been submitted for RFC7725, "An HTTP Status Code to Report Legal Obstacles". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata/eid5181 -------------------------------------- Type: Technical Reported by: Stéphane Bortzmeyer <bortzmeyer+ietf@nic.fr> Section: 3 Original Text ------------- Link: <https://spqr.example.org/legislatione>; rel="blocked-by" Corrected Text -------------- Link: <https://search.example.net/legal>; rel="blocked-by" Notes ----- Of course, it is hard to say from just an URL but it seems that the original "blocked-by" mentioned the authority requesting the blocking (spqr = Roman Senate and People) while the text in section 4 says "The intent is that the header be used to identify the entity actually implementing blockage, not any other entity mandating it." Experience with the 451 crawler during the IETF 99 hackathon showed that several implementors got this wrong and used a "blocked-by" indicating the authority. [It could be a good idea to have two links, one for the authority and one for the implementor, but this is outside the scope of this errata.] Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- RFC7725 (draft-ietf-httpbis-legally-restricted-status-04) -------------------------------------- Title : An HTTP Status Code to Report Legal Obstacles Publication Date : February 2016 Author(s) : T. Bray Category : PROPOSED STANDARD Source : Hypertext Transfer Protocol Bis Area : Applications and Real-Time Stream : IETF Verifying Party : IESG
Received on Saturday, 11 November 2017 04:06:22 UTC