draft-reschke-rfc2231-in-http: section 4.2, Error Handling

Thomas Roessler <roessler@gmail.com> Wed, 24 February 2010 19:34 UTC

Return-Path: <roessler@gmail.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E4FA128C150 for <apps-discuss@core3.amsl.com>; Wed, 24 Feb 2010 11:34:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 zBDw58gk8Tvg for <apps-discuss@core3.amsl.com>; Wed, 24 Feb 2010 11:34:16 -0800 (PST)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id 04D493A857A for <apps-discuss@ietf.org>; Wed, 24 Feb 2010 11:34:15 -0800 (PST)
Received: by gwb10 with SMTP id 10so1868696gwb.31 for <apps-discuss@ietf.org>; Wed, 24 Feb 2010 11:36:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=DcW2RLOEYmVM3qMO0pJBPGpzVa0cnlg7rmqoxvb91Qs=; b=SSgbYCoQk3Z76l6lTyCToosmv3VJmTDRDsKqgKktFu+LockXaoQOkY3LrBbzXS1W3R ASQEJKD7Qo/jBdTb7GCfLwkdAUiSo4DwlsCno19kQ5qnQo/s6Hlw3wd7yjn+Wy7raj61 hkZcuLUNelYCj72f5d7p0mxEA5ISI5akUSKDg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=oc+QsOQa6v9Qn+QR8wjs/+B2XQiHTS+S69I4foAbAw7KvdH9YK97V8+zbC7pyxP4tN 90ft5pfJtrakk0ZcTn5q+tbOno+hv9OBU+fdlGDh0wRYQ9yQUZFBwQiI3ob6yUDkjVxx uROZYC4gmO6uTGF6GpXmUqicNSsEd8nhxPpt4=
MIME-Version: 1.0
Received: by 10.100.24.40 with SMTP id 40mr531845anx.56.1267040180743; Wed, 24 Feb 2010 11:36:20 -0800 (PST)
Date: Wed, 24 Feb 2010 20:36:20 +0100
Message-ID: <4c80fa21002241136y629dda22l1d7617eb25250af8@mail.gmail.com>
Subject: draft-reschke-rfc2231-in-http: section 4.2, Error Handling
From: Thomas Roessler <roessler@gmail.com>
To: apps-discuss@ietf.org, Julian Reschke <julian.reschke@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Thu, 25 Feb 2010 08:41:27 -0800
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 24 Feb 2010 19:35:34 -0000

Reviewing http://www.ietf.org/id/draft-reschke-rfc2231-in-http-10.txt,
section 4.2 says:

   Header specifications that include parameters should also specify
   whether same-named parameters can occur multiple times.  If
   repetitions are not allowed (and this is believed to be the common
   case), the specification should state whether regular or the extended
   syntax takes precedence.  In the latter case, this could be used by
   producers to use both formats without breaking recipients that do not
   understand the syntax.

Leaving the choice of precedence to the header specification implies
that parsers need to special-case. It would seem reasonable to make a
choice in this specification that for properties which can only occur
once, the traditional syntax takes precedence.