Re: FYI: IETF LC for draft-reschke-rfc2231-in-http
Julian Reschke <julian.reschke@gmx.de> Mon, 29 March 2010 12:57 UTC
Return-Path: <julian.reschke@gmx.de>
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 68D5D3A6A43 for <apps-discuss@core3.amsl.com>; Mon, 29 Mar 2010 05:57:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.131
X-Spam-Level: *
X-Spam-Status: No, score=1.131 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13]
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 m6Cjh78xmxIH for <apps-discuss@core3.amsl.com>; Mon, 29 Mar 2010 05:57:09 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 44F523A6A1A for <apps-discuss@ietf.org>; Mon, 29 Mar 2010 05:57:08 -0700 (PDT)
Received: (qmail invoked by alias); 29 Mar 2010 12:57:35 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.119]) [217.91.35.233] by mail.gmx.net (mp006) with SMTP; 29 Mar 2010 14:57:35 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19ru0oN6jFrVwolTnddUHrl6j8OWa964F31G5jTYr 3h+fpFj1pTEuOO
Message-ID: <4BB0A3BF.1030608@gmx.de>
Date: Mon, 29 Mar 2010 14:57:35 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: IETF Apps Discuss <apps-discuss@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Subject: Re: FYI: IETF LC for draft-reschke-rfc2231-in-http
References: <20100222140422.2EFC728C125@core3.amsl.com> <4B829C3C.3070901@gmx.de>
In-Reply-To: <4B829C3C.3070901@gmx.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.54000000000000004
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: Mon, 29 Mar 2010 12:57:10 -0000
On 22.02.2010 16:01, Julian Reschke wrote: > ... > Hi there, > > this spec is now in Last Call, ending March, 22. > > A few issues are open, and those are summarized in Appendix D. I'm > particularly looking for feedback on: > > - parameter-abnf > > In Section 3.2: > > Type: change > > julian.reschke@greenbytes.de (2010-02-20): The ABNF for reg-parameter > and ext-parameter is ambiguous, as "*" is a valid token character; > furthermore, RFC 2616's "attribute" production allows "*" while RFC > 2231's does not. (reported by Alexey Melnikov). > > julian.reschke@greenbytes.de (2010-02-21): Proposal: restrict the > allowable character set in parameter names to exclude "*" (and maybe > even more non-name characters?). Also, consider extending the set of > value characters (for the right hand side) to allow more characters > that can be unambiguously parsed outside quoted strings, such as "/". > > and This will be fixed as proposed in the next draft. > - iso8859 > > In Section 3.2: > > Type: change > > julian.reschke@greenbytes.de (2010-02-20): The protocol could be > further simplified by mandating UTF-8 only (reported by Alexey > Melnikov). On the other hand and not surprisingly, testing shows > that ISO-8859-1 support is widely implemented. The author is looking > for community feedback on this choice. > > Feedback on these specific issues would be appreciated, > ... There was no feedback at all on this one; as the existing implementations *do* support ISO-8859-1 I'm leaning towards leaving things as they are. Best regards, Julian
- FYI: IETF LC for draft-reschke-rfc2231-in-http Julian Reschke
- Re: FYI: IETF LC for draft-reschke-rfc2231-in-http Julian Reschke