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

Paul Hoffman <paul.hoffman@vpnc.org> Wed, 06 July 2011 21:25 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 6808821F8ACC for <apps-discuss@ietfa.amsl.com>; Wed, 6 Jul 2011 14:25:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.766
X-Spam-Level:
X-Spam-Status: No, score=-102.766 tagged_above=-999 required=5 tests=[AWL=-0.167, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 yclSNrsmqGIA for <apps-discuss@ietfa.amsl.com>; Wed, 6 Jul 2011 14:25:54 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 88A2321F8AC2 for <apps-discuss@ietf.org>; Wed, 6 Jul 2011 14:25:51 -0700 (PDT)
Received: from [10.20.30.101] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4] (may be forged)) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p66LPWwL045567 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 6 Jul 2011 14:25:33 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <4E14CD42.2010800@stpeter.im>
Date: Wed, 06 Jul 2011 14:25:41 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <7B0B0248-DD76-4CF9-9108-9BB5F74F1900@vpnc.org>
References: <4E08CDCB.70902@stpeter.im> <4E13DC15.2080302@stpeter.im> <4E14A334.60500@dcrocker.net> <4E14BFFC.5070504@stpeter.im> <4E14CB64.2090403@dcrocker.net> <4E14CD42.2010800@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1084)
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
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 21:25:54 -0000

On Jul 6, 2011, at 2:01 PM, Peter Saint-Andre wrote:

> On 7/6/11 2:53 PM, Dave CROCKER wrote:
>>  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 second SHOULD strikes me as somewhat controversial. :)

Not much more controversial than the whole topic. I can quickly name many protocols for which "some values are reserved for experimental use" have had horrible problems in practice, either where an experimental value ended up being baked into shipping products or two vendors used the same experimental use value for different things.

Maybe the Apps Area is not as familiar with "values 250 through 255 are reserved for experimental use" than the rest of the IETF, but the topic is quite germane to this draft. Dave's proposed wording is hard to swallow, but probably best for the real-world long-lived Internet.

> The first SHOULD is fine by me, although I'm not sure what an extensible
> registry is -- did you mean "both permanent and provisional registries"?


And extensible registry is one where there is a registration procedure so that today's registry might be larger tomorrow.

--Paul Hoffman