[Technical Errata Reported] RFC6266 (5383)

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 07 June 2018 13:12 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54C93130E9D for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 7 Jun 2018 06:12:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.651
X-Spam-Level:
X-Spam-Status: No, score=-7.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 S1PF8k5ojbuJ for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 7 Jun 2018 06:12:08 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (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 E4DDB130E60 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 7 Jun 2018 06:12:07 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1fQuaM-0005m2-M1 for ietf-http-wg-dist@listhub.w3.org; Thu, 07 Jun 2018 13:04:14 +0000
Resent-Date: Thu, 07 Jun 2018 13:04:14 +0000
Resent-Message-Id: <E1fQuaM-0005m2-M1@frink.w3.org>
Received: from titan.w3.org ([128.30.52.76]) by frink.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <wwwrun@rfc-editor.org>) id 1fQuaC-0005lF-RU for ietf-http-wg@listhub.w3.org; Thu, 07 Jun 2018 13:04:04 +0000
Received: from rfc-editor.org ([4.31.198.49]) by titan.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <wwwrun@rfc-editor.org>) id 1fQua9-0004dO-IC for ietf-http-wg@w3.org; Thu, 07 Jun 2018 13:04:04 +0000
Received: by rfc-editor.org (Postfix, from userid 30) id 8B911B828C3; Thu, 7 Jun 2018 06:03:07 -0700 (PDT)
To: julian.reschke@greenbytes.de, ben@nostrum.com, aamelnikov@fastmail.fm, adam@nostrum.com, mnot@mnot.net, pmcmanus@mozilla.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: magnar@myrtveit.com, ietf-http-wg@w3.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20180607130307.8B911B828C3@rfc-editor.org>
Date: Thu, 07 Jun 2018 06:03:07 -0700
X-W3C-Hub-Spam-Status: No, score=-6.2
X-W3C-Hub-Spam-Report: AWL=0.952, BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1fQua9-0004dO-IC 4f7eb24af8ce7afc9db560e0345aeaad
X-Original-To: ietf-http-wg@w3.org
Subject: [Technical Errata Reported] RFC6266 (5383)
Archived-At: <https://www.w3.org/mid/20180607130307.8B911B828C3@rfc-editor.org>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/35506
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: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

The following errata report has been submitted for RFC6266,
"Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata/eid5383

--------------------------------------
Type: Technical
Reported by: Parameter names must not allow * <magnar@myrtveit.com>

Section: 4.1

Original Text
-------------
     disp-ext-parm       = token "=" value
                         | ext-token "=" ext-value
     ext-token           = <the characters in token, followed by "*">

   Defined in [RFC2616]:

     token         = <token, defined in [RFC2616], Section 2.2>
     quoted-string = <quoted-string, defined in [RFC2616], Section 2.2>
     value         = <value, defined in [RFC2616], Section 3.6>
                   ; token | quoted-string

   Defined in [RFC5987]:

     ext-value   = <ext-value, defined in [RFC5987], Section 3.2>

Corrected Text
--------------
     disp-ext-parm       = parmname "=" value
                         | ext-parmname "=" ext-value
     ext-parmname        = <the characters in parmname, followed by "*">

   Defined in [RFC2616]:

     quoted-string = <quoted-string, defined in [RFC2616], Section 2.2>
     value         = <value, defined in [RFC2616], Section 3.6>
                   ; token | quoted-string

   Defined in [RFC5987]:

     parmname    = <parmname, defined in [RFC5987], Section 3.2>
     ext-value   = <ext-value, defined in [RFC5987], Section 3.2>

Notes
-----
RFC5987 section 3.2.1 modifies the grammar from RFC2616. These modifications should be used in RFC6266. If not, it is impossible to determine whether a parameter should be a value or an ext-value based on the parameter name, since "*" is a valid character in token.

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. 

--------------------------------------
RFC6266 (draft-ietf-httpbis-content-disp-09)
--------------------------------------
Title               : Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)
Publication Date    : June 2011
Author(s)           : J. Reschke
Category            : PROPOSED STANDARD
Source              : Hypertext Transfer Protocol Bis APP
Area                : Applications
Stream              : IETF
Verifying Party     : IESG