Content-Disposition Charset Punt

Rens Troost <rens@name.net> Sun, 23 June 1996 04:43 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06377; 23 Jun 96 0:43 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa06371; 23 Jun 96 0:43 EDT
Received: from list.cren.net by CNRI.Reston.VA.US id aa01353; 23 Jun 96 0:43 EDT
Received: from localhost (localhost [127.0.0.1]) by list.cren.net (8.6.12/8.6.12) with SMTP id AAA15303; Sun, 23 Jun 1996 00:33:00 -0400
Received: from name.net (mikado.name.net [204.50.44.10]) by list.cren.net (8.6.12/8.6.12) with ESMTP id AAA15262 for <ietf-822@list.cren.net>; Sun, 23 Jun 1996 00:30:35 -0400
Received: from engine.name.net (engine.name.net [204.50.44.14]) by name.net (8.6.12/8.6.12) with ESMTP id AAA01596 for <ietf-822@list.cren.net>; Sun, 23 Jun 1996 00:30:36 -0400
Received: from localhost.name.net (localhost.name.net [127.0.0.1]) by engine.name.net (8.6.12/8.6.12) with SMTP id AAA19654 for <ietf-822@list.cren.net>; Sun, 23 Jun 1996 00:30:35 -0400
Message-Id: <199606230430.AAA19654@engine.name.net>
Date: Sun, 23 Jun 1996 00:30:35 -0400
X-Orig-Sender: owner-ietf-822@list.cren.net
Precedence: bulk
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Rens Troost <rens@name.net>
To: ietf-822@list.cren.net
Subject: Content-Disposition Charset Punt
In-Reply-To: Your message of "Thu, 20 Jun 1996 12:43:34 +0200." <15735.835267414@domen.uninett.no>
X-Authentication-Warning: engine.name.net: Host localhost.name.net didn't use HELO protocol
X-Listprocessor-Version: 8.0 -- ListProcessor(tm) by CREN

The only bugbear left in the Content-Disposition woods is the desire on
the part of many to have charset support for the filenames. The
current draft punts:

    Current [RFC 1521] grammar restricts parameter values (and
    hence Content-Disposition filenames) to US-ASCII.  We
    recognize the great desirability of allowing arbitrary
    character sets in filenames, but it is beyond the scope of
    this document to define the necessary mechanisms.  We expect
    that the basic [RFC 1521] `value' specification will someday
    be amended to allow use of non-US-ASCII characters, at which
    time the same mechanism should be used in the Content-
    Disposition filename parameter.

In the interests of expediency, I want to stick with this wording and
approach. It was in no small part turmoil over this issue that caused
it to be issued as Experimental in the first place, so I wanted to run
this by the group.

-Rens