Re: Case sensitivity of Transfer-Codings

Bjoern Hoehrmann <derhoermi@gmx.net> Tue, 31 January 2012 05:04 UTC

Return-Path: <ietf-http-wg-request@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 F39E411E8111 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 30 Jan 2012 21:04:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.568
X-Spam-Level:
X-Spam-Status: No, score=-7.568 tagged_above=-999 required=5 tests=[AWL=3.031, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qVGNXtqG6zuv for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 30 Jan 2012 21:04:35 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 9AA5611E80EC for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 30 Jan 2012 21:04:35 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.69) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1Rs5rr-0003K9-PY for ietf-http-wg-dist@listhub.w3.org; Tue, 31 Jan 2012 05:02:55 +0000
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.69) (envelope-from <derhoermi@gmx.net>) id 1Rs5rd-0003J5-Ol for ietf-http-wg@listhub.w3.org; Tue, 31 Jan 2012 05:02:41 +0000
Received: from mailout-de.gmx.net ([213.165.64.23]) by maggie.w3.org with smtp (Exim 4.72) (envelope-from <derhoermi@gmx.net>) id 1Rs5rb-00021J-Vy for ietf-http-wg@w3.org; Tue, 31 Jan 2012 05:02:41 +0000
Received: (qmail invoked by alias); 31 Jan 2012 05:02:12 -0000
Received: from dslb-094-223-178-249.pools.arcor-ip.net (EHLO HIVE) [94.223.178.249] by mail.gmx.net (mp033) with SMTP; 31 Jan 2012 06:02:12 +0100
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1/2ULB6wyb2IDcbDN7CLkVsMIFdvXNAGtY3k+x5+v 9ssuBnpPVorQwB
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Dave Bordoley <bordoley@gmail.com>
Cc: ietf-http-wg@w3.org
Date: Tue, 31 Jan 2012 06:02:34 +0100
Message-ID: <9atei71svotg4cqkm3h59i83cgeg0m6vc5@hive.bjoern.hoehrmann.de>
References: <CAL4Fp5pT3WvYP3a-RJ7oxM00U-JZ2dypVUwC7JdpDD1kBSj9_w@mail.gmail.com>
In-Reply-To: <CAL4Fp5pT3WvYP3a-RJ7oxM00U-JZ2dypVUwC7JdpDD1kBSj9_w@mail.gmail.com>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Received-SPF: pass client-ip=213.165.64.23; envelope-from=derhoermi@gmx.net; helo=mailout-de.gmx.net
X-W3C-Hub-Spam-Status: No, score=-1.9
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01
X-W3C-Scan-Sig: maggie.w3.org 1Rs5rb-00021J-Vy 52eb1f34ba2c257ddacbf6a28c6b4451
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Case sensitivity of Transfer-Codings
Archived-At: <http://www.w3.org/mid/9atei71svotg4cqkm3h59i83cgeg0m6vc5@hive.bjoern.hoehrmann.de>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/12265
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>
Resent-Message-Id: <E1Rs5rr-0003K9-PY@frink.w3.org>
Resent-Date: Tue, 31 Jan 2012 05:02:55 +0000

* Dave Bordoley wrote:
>In version 18 of the draft spec it states that "All transfer-coding
>values are case-insensitive." Its a little unclear whether this also
>applies to the attribute/value pairs that make up a
>transfer-parameter. In similar key/value pairs, attribute values tend
>to be case insensitive while values are not. For instance, the spec
>for media types states: "The type, subtype, and parameter attribute
>names are case-insensitive.  Parameter values might or might not be
>case-sensitive." It would be nice for the spec to state this
>explicitly as well transfer-codings.

(FWIW, I thought this would be already very clear and looked up the
section Dave Bordoley was missing, but upon further inspection, I do
agree that there should be some text to this effect, or this should
be organized differently, like having a generic definition that says
parameter names are case-insensitive, for values see the individual
parameter definition.)
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/