[apps-discuss] Review of draft-ietf-appsawg-xdash-04
ht@inf.ed.ac.uk (Henry S. Thompson) Fri, 30 March 2012 10:20 UTC
Return-Path: <ht@inf.ed.ac.uk>
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 5CC3021F896D; Fri, 30 Mar 2012 03:20:34 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CsZCpMaJClHA; Fri, 30 Mar 2012 03:20:33 -0700 (PDT)
Received: from treacle.ucs.ed.ac.uk (treacle.ucs.ed.ac.uk [129.215.16.102]) by ietfa.amsl.com (Postfix) with ESMTP id 4E38321F8951; Fri, 30 Mar 2012 03:20:31 -0700 (PDT)
Received: from nutty.inf.ed.ac.uk (nutty.inf.ed.ac.uk [129.215.33.33]) by treacle.ucs.ed.ac.uk (8.13.8/8.13.4) with ESMTP id q2UAKARL002994; Fri, 30 Mar 2012 11:20:15 +0100 (BST)
Received: from calexico.inf.ed.ac.uk (calexico.inf.ed.ac.uk [129.215.24.15]) by nutty.inf.ed.ac.uk (8.13.8/8.13.8) with ESMTP id q2UAK45e019158; Fri, 30 Mar 2012 11:20:10 +0100
Received: from calexico.inf.ed.ac.uk (localhost [127.0.0.1]) by calexico.inf.ed.ac.uk (8.14.4/8.14.4) with ESMTP id q2UAK34L021374; Fri, 30 Mar 2012 11:20:03 +0100
Received: (from ht@localhost) by calexico.inf.ed.ac.uk (8.14.4/8.14.4/Submit) id q2UAK0Me021367; Fri, 30 Mar 2012 11:20:00 +0100
X-Authentication-Warning: calexico.inf.ed.ac.uk: ht set sender to ht@inf.ed.ac.uk using -f
To: apps-discuss@ietf.org, draft-ietf-appsawg-xdash.all@tools.ietf.org
From: ht@inf.ed.ac.uk
Date: Fri, 30 Mar 2012 11:20:00 +0100
Message-ID: <f5b7gy2v19r.fsf@calexico.inf.ed.ac.uk>
User-Agent: Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.4.21 (linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Edinburgh-Scanned: at treacle.ucs.ed.ac.uk with MIMEDefang 2.60, Sophie, Sophos Anti-Virus, Clam AntiVirus
X-Scanned-By: MIMEDefang 2.60 on 129.215.16.102
Cc: iesg@ietf.org
Subject: [apps-discuss] Review of draft-ietf-appsawg-xdash-04
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, 30 Mar 2012 10:20:34 -0000
I have been selected as the Applications Area Directorate reviewer for this draft (for background on appsdir, please see http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate). Please resolve these comments along with any other Last Call comments you may receive. Please wait for direction from your document shepherd or AD before posting a new version of the draft. Document: draft-ietf-appsawg-xdash Title: Deprecating the X- Prefix and Similar Constructs in Application Protocols Reviewer: Henry S. Thompson Review Date: 2012-03-30 IETF Last Call Date: 2012-03-15 Summary: This draft is almost ready for publication as an Proposed Standard but has a few issues that should be fixed before publication Major Issues: Abstract and Introduction [This started out as a nit about the use of scare-quotes in the Abstract, but now that I see how much depends on it throughout the document, I have promoted it] I have an allergy to scare-quotes, I guess, but putting quotes around "standard" here seems . . . odd. If what you mean is more along the lines of "distinguished between the names of parameters defined in the relevant standards and those without such definitions", then words along those lines might serve better. . . If you make such a change, then "newly-defined parameters" could become something such as "parameters getting their names outside the standards process". More importantly, the distinction between "parameters named in, or by means licensed by, the relevant standard" and "parameters named elsewhere" deserves more careful definition than that implied just by contrasting, in quotes, "standard" and "non-standard", given the weight the distinction has to bear later on. Section 2. Maybe not major? Depends on the answer. What does "discriminate between 'standard' and 'non-standard' parameters" actually _mean_? Either a parameter is defined in the relevant standard, or via a standards-licensed route, or it isn't. This section seems to imply there is some kind of generic processing reserved to parameters named in or licensed by the relevant standard (or, perhaps, to parameters _not_ so named), but this reader at least is not clear what such generic processing might be. It seems that the authors of this RFC know, or suspect, that some application implementers are lazy, and deploy such processing without actually using a list derived from the relevant specs and registries---if so, give an example? If not, what is this section for, exactly? Minor Issues: 3 Maybe, if you think there are relevant cases, add something along the lines of "MUST follow any naming guidelines set out in the relevant standard(s)". ht -- Henry S. Thompson, School of Informatics, University of Edinburgh 10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440 Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk URL: http://www.ltg.ed.ac.uk/~ht/ [mail from me _always_ has a .sig like this -- mail without it is forged spam]
- [apps-discuss] Review of draft-ietf-appsawg-xdash… Henry S. Thompson
- Re: [apps-discuss] Review of draft-ietf-appsawg-x… Peter Saint-Andre