IETF Logo Mail Archive

Re: comment for draft-moore-mime-cdisp-00

Valdis.Kletnieks@vt.edu Wed, 06 August 1997 08:47 UTC

Received: from cnri by ietf.org id aa24659; 6 Aug 97 4:47 EDT
Received: from mail.proper.com (mail.proper.com [206.86.127.224]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid EAA15421; Wed, 6 Aug 1997 04:45:55 -0400 (EDT)
Received: (from majordomo@localhost) by mail.proper.com (8.8.5/8.7.3) id BAA17406 for ietf-822-bks; Wed, 6 Aug 1997 01:19:49 -0700 (PDT)
Received: from black-ice.cc.vt.edu (black-ice.cc.vt.edu [128.173.14.71]) by mail.proper.com (8.8.5/8.7.3) with ESMTP id BAA17402 for <ietf-822@imc.org>; Wed, 6 Aug 1997 01:19:44 -0700 (PDT)
Received: from black-ice.cc.vt.edu (LOCALHOST [127.0.0.1]) by black-ice.cc.vt.edu (8.8.7/8.8.7) with ESMTP id EAA23536; Wed, 6 Aug 1997 04:24:03 -0400
Message-Id: <199708060824.EAA23536@black-ice.cc.vt.edu>
To: "Kenzaburou Tamaru (Exchange)" <kenzat@exchange.microsoft.com>
Cc: ietf-822@imc.org, Mark Crispin <MRC@cac.washington.edu>
Subject: Re: comment for draft-moore-mime-cdisp-00
In-Reply-To: Your message of "Tue, 05 Aug 1997 21:06:19 PDT." <2FBF98FC7852CF11912A00000000000105ED95ED@DINO>
From: Valdis.Kletnieks@vt.edu
X-Url: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#; 3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t( ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-) %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <2FBF98FC7852CF11912A00000000000105ED95ED@DINO>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_919545674P"; micalg="pgp-md5"; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Wed, 06 Aug 1997 04:24:02 -0400
Sender: owner-ietf-822@imc.org
Precedence: bulk

On Tue, 05 Aug 1997 21:06:19 PDT, "Kenzaburou Tamaru (Exchange)" said:
> field. MIME-2(Message Header Extensions for Non-ASCII) is defined as
> extension for header field., I don't think this can be applied to this
> "value".
> It is time to say like
> ---------------------------------------------
> disposition-param := filename-param
> 	/..............
> filename-param := "filename" "=" dstring
> dstring := 1*utf8
> utf8 := <any sequence of octets formed from the UTF-8 transformation of
> a character from ISO 10646>
> ---------------------------------------------

No.

The more correct answer here is to allow RFC2047 header-encoding to be used
in the 'dstring' field.  This way, other encoding systems besides UTF8 
can be used if desired.

Unfortunately, it's past 4AM local time and I can't remember why we didn't
allow the 2047-style encoding in the first place.  Somebody else here
remember why we did that?


-- 
				Valdis Kletnieks
				Computer Systems Senior Engineer
				Virginia Tech

v2.23.0 | Report a Bug | By Email