Re: feedback on draft-reschke-basicauth-enc-04, "3. The 'encoding' auth-param"

Bjoern Hoehrmann <derhoermi@gmx.net> Mon, 30 January 2012 13:18 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 AEB0421F86BB for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 30 Jan 2012 05:18:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.19
X-Spam-Level:
X-Spam-Status: No, score=-7.19 tagged_above=-999 required=5 tests=[AWL=3.109, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 1pkdqcH8ECqm for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 30 Jan 2012 05:18:07 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id EBAE221F869E for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 30 Jan 2012 05:18:06 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.69) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1Rrr6x-0004kG-BK for ietf-http-wg-dist@listhub.w3.org; Mon, 30 Jan 2012 13:17:31 +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 1Rrr6i-0004jP-Ue for ietf-http-wg@listhub.w3.org; Mon, 30 Jan 2012 13:17:16 +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 1Rrr6g-0002Tb-F1 for ietf-http-wg@w3.org; Mon, 30 Jan 2012 13:17:16 +0000
Received: (qmail invoked by alias); 30 Jan 2012 13:16:47 -0000
Received: from dslb-094-223-178-249.pools.arcor-ip.net (EHLO HIVE) [94.223.178.249] by mail.gmx.net (mp001) with SMTP; 30 Jan 2012 14:16:47 +0100
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1/fk8BYahDfy1ogetb+2I3CotZEhB1p2BDVHFPc+T sYrBSpvyEXK297
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Alexei Khlebnikov <alexei.khlebnikov@opera.com>
Cc: ietf-http-wg@w3.org
Date: Mon, 30 Jan 2012 14:17:08 +0100
Message-ID: <ff4di7h44pike7nb859avqr4lc5cbr38ml@hive.bjoern.hoehrmann.de>
References: <op.v8wcktoyockn2m@alexeik-desktop.oslo.osa>
In-Reply-To: <op.v8wcktoyockn2m@alexeik-desktop.oslo.osa>
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 1Rrr6g-0002Tb-F1 8eff0fb00b96d2071595ff85cb16f696
X-Original-To: ietf-http-wg@w3.org
Subject: Re: feedback on draft-reschke-basicauth-enc-04, "3. The 'encoding' auth-param"
Archived-At: <http://www.w3.org/mid/ff4di7h44pike7nb859avqr4lc5cbr38ml@hive.bjoern.hoehrmann.de>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/12260
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: <E1Rrr6x-0004kG-BK@frink.w3.org>
Resent-Date: Mon, 30 Jan 2012 13:17:31 +0000

* Alexei Khlebnikov wrote:
>My feedback on  
><http://greenbytes.de/tech/webdav/draft-reschke-basicauth-enc-04.html#encoding>:
>
>Was it considered to name the new parameter "charset" instead of  
>"encoding"?

Well, "we" are trying to http://www.w3.org/TR/charmod/#C020 move away
from using the "charset" term and there are not many alternative words
to choose from if you want to use an established term.

>I can see the following advantages of "charset":
>
>1) "Charset" is unambigous. "Encoding" is ambigous, it can refer to many  
>things: base64, quoted-printable, chunked-coding, gzip-compression, etc.

That is probably largely thanks to language hygiene efforts like above,
it used to be rather unclear what people meant when they said "charset"
or "character set". Maybe we can declare success and use it, at least
where it's consistent with existing usage, but expect complaints.
-- 
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/