Re: [apps-discuss] "X-" revisited

Dave CROCKER <dhc@dcrocker.net> Wed, 06 July 2011 20:54 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CA4E21F8C08 for <apps-discuss@ietfa.amsl.com>; Wed, 6 Jul 2011 13:54:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.932
X-Spam-Level:
X-Spam-Status: No, score=-6.932 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cPL-mU4jKEJl for <apps-discuss@ietfa.amsl.com>; Wed, 6 Jul 2011 13:54:05 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id B162D21F8C07 for <apps-discuss@ietf.org>; Wed, 6 Jul 2011 13:54:05 -0700 (PDT)
Received: from [192.168.1.156] (adsl-67-124-149-98.dsl.pltn13.pacbell.net [67.124.149.98]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p66KrxFZ011846 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Wed, 6 Jul 2011 13:54:04 -0700
Message-ID: <4E14CB64.2090403@dcrocker.net>
Date: Wed, 06 Jul 2011 13:53:56 -0700
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
References: <4E08CDCB.70902@stpeter.im> <4E13DC15.2080302@stpeter.im> <4E14A334.60500@dcrocker.net> <4E14BFFC.5070504@stpeter.im>
In-Reply-To: <4E14BFFC.5070504@stpeter.im>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 06 Jul 2011 13:54:05 -0700 (PDT)
Cc: dcrocker@bbiw.net, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] "X-" revisited
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jul 2011 20:54:10 -0000

On 7/6/2011 1:05 PM, Peter Saint-Andre wrote:
>>>   3.  When parameter names need to be very short
>>
>> I've no idea how this requirement can justify an x- name.  (A minor
>> point, but note that x- adds two bytes to the length of the name...)
>
> Well, "x-foo" is shorter than "VND.BrandenburgInternetWorking.foo".

Mumble.  This issue seems like one that is going to take vastly more effort than 
it ought, but that's probably true for the entire topic.  (Entire topic:  X- was 
a good idea to avoid collisions with standards, but turns out to be a much worse 
idea for uses that become standards.  So, don't use X-".)

Anyhow...

"X-foo" is longer than "foo".

And I believe the real comparision to VND should be 
"X-BrandenburgInternetWorking.foo"...


>>> Implementers are easily confused.
>>
>> I don't understand how using or not using x- creates or alleviates
>> confusion in implementers.
>
> I don't either, but that was one of the objections.

OK, but whoever was/is objecting needs to explain their concerns, of course.


>>     2.  Authors of application protocol specifications SHOULD NOT
>>         mandate that all parameters without the "X-" prefix need
>>         to be registered with the IANA.
>>
>> (#2 seems odd.  I don't really understand why it is needed or what it
>> does that's significant, given the recommendation of not using x-
>> parameters ever. Is there a way of stating what is desired affirmatively?)
>
> The point is directed at the kind of thing we find in RFC 5451, which
> says that x- params MUST NOT be registered and non-x- params MUST be
> registered. That seems wrongheaded to me.

OK.  I think this reduces to a new phrasing along the lines of:

   Authors of application protocol specifications SHOULD provide extensible 
registries for all parameters and SHOULD mandate use of the registries, for all 
values of the parameters, independent of the form of the parameter names.

(The absence of any reference to X- is intentional.)

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net