[Fwd: Last call for comments on draft-reschke-rfc2231-in-http-07]
Julian Reschke <julian.reschke@gmx.de> Mon, 28 December 2009 14:51 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 E1E2D3A691D for <apps-discuss@core3.amsl.com>; Mon, 28 Dec 2009 06:51:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.625
X-Spam-Level:
X-Spam-Status: No, score=-4.625 tagged_above=-999 required=5 tests=[AWL=-2.026, 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 vVEGC+Xf1UqD for <apps-discuss@core3.amsl.com>; Mon, 28 Dec 2009 06:51:33 -0800 (PST)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 718543A6811 for <discuss@apps.ietf.org>; Mon, 28 Dec 2009 06:51:32 -0800 (PST)
Received: (qmail invoked by alias); 28 Dec 2009 14:51:12 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.117]) [217.91.35.233] by mail.gmx.net (mp067) with SMTP; 28 Dec 2009 15:51:12 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/YtWNrP4/YJQf2V5YfdF/RY9qfltQw6Rm5ah9f77 zczJtDpTEdjExE
Message-ID: <4B38C5DE.50204@gmx.de>
Date: Mon, 28 Dec 2009 15:51:10 +0100
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: Apps Discuss <discuss@apps.ietf.org>
Subject: [Fwd: Last call for comments on draft-reschke-rfc2231-in-http-07]
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.51
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, 28 Dec 2009 14:51:35 -0000
FYI -------- Original Message -------- To: HTTP Working Group <ietf-http-wg@w3.org> Subject: Last call for comments on draft-reschke-rfc2231-in-http-07 References: <20091227183001.A776A3A68E0@core3.amsl.com> In-Reply-To: <20091227183001.A776A3A68E0@core3.amsl.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, I just updated draft-reschke-rfc2231-in-http with a short section explaining document history: Appendix A. Document History and Future Plans (to be removed by RFC Editor before publication) Problems with the internationalization of the HTTP Content- Disposition header field have been known for many years (see test cases at <http://greenbytes.de/tech/tc2231/>). During IETF 72 (<http://tools.ietf.org/wg/httpbis/minutes?item=minutes72.html>), the HTTPbis Working Group shortly discussed how to deal with the underspecification of (1) Content-Disposition, and its (2) internationalization aspects. Back then, there was rough consensus in the room to move the definition into a separate draft. This specification addresses problem (2), by defining a simple subset of the encoding format defined in RFC 2231. A separate specification, draft-reschke-rfc2183-in-http, is planned to address problem (1). Note that this approach was chosen because Content- Disposition is just an example for an HTTP header field using this kind of encoding. Another example is the currently proposed Link header field (draft-nottingham-http-link-header). This document is planned to be published on the IETF Standards Track, so that other standards-track level documents can depend on it, such as the new specification of Content-Disposition, or potentially future revisions of the HTTP Link Header specification. Also note that this document specifies a proper subset of the extensions defined in RFC 2231, but does not normatively refer to it. Thus, RFC 2231 can be revised separately, should the email community decide to. - <http://tools.ietf.org/html/draft-reschke-rfc2231-in-http-07#appendix-A> I think this document is ready for an IETF Last Call, but before I request publication (*), I'd appreciate more review from HTTPbis WG members. Best regards, Julian (*) Planned in three weeks from now, on Jan 18, 2010. Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts directories. > > Title : Application of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Header Fields > Author(s) : J. Reschke > Filename : draft-reschke-rfc2231-in-http-07.txt > Pages : 13 > Date : 2009-12-27 > > By default, message header field parameters in Hypertext Transfer > Protocol (HTTP) messages can not carry characters outside the ISO- > 8859-1 character set. RFC 2231 defines an escaping mechanism for use > in Multipurpose Internet Mail Extensions (MIME) headers. This > document specifies a profile of that encoding suitable for use in > HTTP. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-reschke-rfc2231-in-http-07.txt > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > > > ------------------------------------------------------------------------ > > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@ietf.org > https://www.ietf.org/mailman/listinfo/i-d-announce > Internet-Draft directories: http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
- [Fwd: Last call for comments on draft-reschke-rfc… Julian Reschke