Re: [apps-discuss] WGLC on draft-ietf-appsawg-xdash-02.txt

Paul Hoffman <paul.hoffman@vpnc.org> Fri, 27 January 2012 18:13 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 9B24A21F863F for <apps-discuss@ietfa.amsl.com>; Fri, 27 Jan 2012 10:13:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.552
X-Spam-Level:
X-Spam-Status: No, score=-102.552 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 pNd67ZEPP-kJ for <apps-discuss@ietfa.amsl.com>; Fri, 27 Jan 2012 10:13:35 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 17AE021F864E for <apps-discuss@ietf.org>; Fri, 27 Jan 2012 10:13:35 -0800 (PST)
Received: from [10.20.30.103] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.3) with ESMTP id q0RIDW1u053822 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 27 Jan 2012 11:13:33 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <4F1F1A72.1090302@isode.com>
Date: Fri, 27 Jan 2012 10:13:32 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <6068EE9E-D120-4CE9-8096-C296C169C7DE@vpnc.org>
References: <4EE2430E.4080501@isode.com> <4F1F1A72.1090302@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] WGLC on draft-ietf-appsawg-xdash-02.txt
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: Fri, 27 Jan 2012 18:13:35 -0000

After discussing this a bit more with Pete Resnick off-line, we found a place where I missed a major assumption: this draft is only about parameter names, not numbers. Pete believes that this changes things hugely, but I am less sure. Regardless, we agreed it needs to be clarified.

Proposed text to be added after the second paragraph of Section 1:

Note that this document only discusses parameters with text names; it does not discuss parameters that are expressed with numbers. The difference between these two is that text names of parameters (for example, "hash-type" and "x-hash-type") tend to appear in administrative and user interfaces much more often than numbers that identify parameters (for example, 7 or 0xa007). The misuse of parameters with text names and with numbers are similar; developers will try to get experimental parameters standardized without changing the parameter value, developers mis-use unassigned values without going through the defined registration procedure, and so on. However, the more likely exposure to administrators and users limits the focus of this document only to named parameters.

--Paul Hoffman