This message was not delivered due to problems at our site. It is being resent.
The following is a copy of the message:
Received: from rutgers.edu (-:RUTGERS.EDU:-) by yonge.csri.toronto.edu via TCP
with SMTP id AA28054; Thu, 11 Jul 91 20:18:08 EDT
Received: from dimacs.rutgers.edu by rutgers.edu (5.59/SMI4.0/RU1.4/3.08)
id AA23903; Thu, 11 Jul 91 20:16:46 EDT
Received: by dimacs.rutgers.edu (5.59/SMI4.0/RU1.4/3.08)
id AA15776; Thu, 11 Jul 91 19:17:45 EDT
Received: from [192.5.214.2] by dimacs.rutgers.edu (5.59/SMI4.0/RU1.4/3.08)
id AA15755; Thu, 11 Jul 91 19:17:32 EDT
Received: from jrdmax.jrd.dec.com by decuac.DEC.COM (5.61/Ultrix-fma)
id AA13668; Thu, 11 Jul 91 19:16:48 -0400 XXX
Received: from usagi.jrd.dec.com by jrdmax.jrd.dec.com (5.65/J-ULTRIX4.0)
id AA00760; Fri, 12 Jul 91 08:16:29 +0900
Received: from localhost by usagi.jrd.dec.com (5.65/J-ULTRIX4.0)
id AA04234; Fri, 12 Jul 91 08:16:08 +0900
Message-Id: <9107112316(_dot_)AA04234(_at_)usagi(_dot_)jrd(_dot_)dec(_dot_)com>
To: erik(_at_)sra(_dot_)co(_dot_)jp
Cc: ietf-822(_at_)dimacs(_dot_)rutgers(_dot_)edu
Subject: Re: charset philosophy
In-Reply-To: Your message of Thu, 11 Jul 91 21:23:00 +0900.
<9107111223(_dot_)AA23556(_at_)sran8(_dot_)sra(_dot_)co(_dot_)jp>
X-Phone-Reply-To: 045-336-5358 (work)/045-320-0492 (home) [in Japan]
Content-Type: TEXT/US-ASCII
Content-Transfer-Encoding: 7BIT
X-Content-Encoding-By: post, v1.5, usagi.jrd.dec.com
Date: Fri, 12 Jul 91 08:16:06 JST
From: doi(_at_)jrd(_dot_)dec(_dot_)com
# If we send a plain ASCII text message and we wish to label it with a
# content type header and a character encoding identifier, we include
# the following:
#
# Content-Type: text/us-ascii
#
# Today, when ASCII messages cross a border into an EBCDIC world, they
# are converted to EBCDIC. Assuming that such a gateway is fully
# upgraded to conform to the new RFC-XXXX, what should be done about the
# content type header? Should it be changed to the following?
#
# Content-Type: text/us-ebcdic
#
# Or something like that?
I thought that it should be something like..
Content-Type: text/us-ascii
Content-Transfter-Encoding: ascii2ebcdic
(or x-ascii2ebcdic)
But if it already had some encoding, such as quoted-printable,
then the gateway will have to un-do the encoding (if it knows how)
and do the encoding from ascii to ebcdic.
Isn't the content-type: field supposed to identify the content of
the original message?
[Note new work phone number]
Hitoshi Doi, International Systems Engineering
doi(_at_)jrd(_dot_)dec(_dot_)com
Japan Research and Development Center decwrl!jrd.dec.com!doi
Digital Equipment Corporation Japan
doi(_at_)decvax(_dot_)dec(_dot_)com