Date: Fri, 27 Mar 1992 07:58:36 -0500 (EST)
From: Nathaniel Borenstein <nsb(_at_)thumper(_dot_)bellcore(_dot_)com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: Keith Moore <moore(_at_)cs(_dot_)utk(_dot_)edu>
Subject: Re: Text "attachments" to messages
Cc: ietf-822(_at_)dimacs(_dot_)rutgers(_dot_)edu,
moore(_at_)cs(_dot_)utk(_dot_)edu
References: <9203262329(_dot_)AA13599(_at_)wilma(_dot_)cs(_dot_)utk(_dot_)edu>
Hmmm, I hadn't really thought about the character set issue. Maybe
another subtype is appropriate. Rather than"application/text", perhaps
it should be "text/file", so that MIME implementations that didn't
understand it could at least show the user the text? Also, putting it
under text immediately solves the problem of character sets, since
charset is already defined for text.... -- Nathaniel
I think text/file is probably about right, for the reasons you mention.
Keith