Re: [Ietf-message-headers] Provisional registration of 5 X-Device-* HTTP Header fields for use in content transformation guidelines

Francois Daoust <fd@w3.org> Tue, 04 August 2009 16:31 UTC

Return-Path: <fd@w3.org>
X-Original-To: ietf-message-headers@core3.amsl.com
Delivered-To: ietf-message-headers@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C2E023A7007 for <ietf-message-headers@core3.amsl.com>; Tue, 4 Aug 2009 09:31:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8hX9UHGL9ZHp for <ietf-message-headers@core3.amsl.com>; Tue, 4 Aug 2009 09:31:15 -0700 (PDT)
Received: from lewis.sophia.w3.org (gw.sophia.w3.org [193.51.208.72]) by core3.amsl.com (Postfix) with ESMTP id E56723A67F4 for <ietf-message-headers@ietf.org>; Tue, 4 Aug 2009 09:31:14 -0700 (PDT)
Received: from doust-w3claptop.sophia.w3.org ([10.1.2.97]) by lewis.sophia.w3.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from <fd@w3.org>) id 1MYMuj-0008I9-2z; Tue, 04 Aug 2009 16:31:01 +0000
Message-ID: <4A786244.2000508@w3.org>
Date: Tue, 04 Aug 2009 18:31:00 +0200
From: Francois Daoust <fd@w3.org>
User-Agent: Thunderbird 2.0.0.22 (X11/20090608)
MIME-Version: 1.0
To: SM <sm@resistor.net>
References: <4A55C127.8030609@w3.org> <4A572B0A.5020104@ninebynine.org> <4A575F8C.7070907@w3.org> <6.2.5.6.2.20090710090140.02a0f0c8@resistor.net>
In-Reply-To: <6.2.5.6.2.20090710090140.02a0f0c8@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Graham Klyne <GK@ninebynine.org>, ietf-message-headers@ietf.org
Subject: Re: [Ietf-message-headers] Provisional registration of 5 X-Device-* HTTP Header fields for use in content transformation guidelines
X-BeenThere: ietf-message-headers@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Discussion list for header fields used in Internet messaging applications." <ietf-message-headers.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-message-headers>, <mailto:ietf-message-headers-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-message-headers>
List-Post: <mailto:ietf-message-headers@ietf.org>
List-Help: <mailto:ietf-message-headers-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-message-headers>, <mailto:ietf-message-headers-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Aug 2009 16:31:15 -0000

Apologies for the late reply, I somehow managed not to see it up until now.

SM wrote:
> Hi Francois,
> At 08:34 10-07-2009, Francois Daoust wrote:
>> The situation the Mobile Web Best Practices working group is trying to 
>> address is one where different vendors used different HTTP header 
>> field conventions (all starting with 'X-') for the same use in their 
>> proxies, requiring content providers to support the different names 
>> when they wanted to do things properly. What the working group would 
>> like to do is to shrink the list of existing conventions to one and 
>> only one convention, but would prefer not to introduce any new 
>> convention (be it the last one) for that to happen. The 'X-Device-foo' 
>> format is the most commonly used format in the list based on the 
>> group's experience, and thus the chosen one.
> 
> I'll encourage you to adopt Graham's suggestion of moving to 
> "Device-foo" or any other valid name that does not start with "X-".  
> These "X-" headers are generally for private use where the 
> interpretation is by private agreement.  There are people outside the 
> group that might use that header field for other purposes and they are 
> unlikely to look it up in the registry.  If your working group already 
> agrees on having one convention, it is better to do away with the "X-".
> 

Thanks. I understand the suggestion and the implications of not 
following the suggestion.

At this point, the working group agrees on having one convention among 
the existing ones, which unfortunately all start with "X-". But the 
working group does not agree to do away with the "X-" not to introduce 
any kind of new notation. If you're fine with it, the group would thus 
like to proceed only with the registration of the "X-" versions of the 
HTTP header fields.

Francois.

[...]