ietf-822
[Top] [All Lists]

Re: We japanese need ISO-2022-JP!!!

1994-12-01 06:52:09
Wataru-san,

At 1:19 AM 12/1/94, wataru(_at_)ntttsd(_dot_)ntt(_dot_)jp wrote:
This can be taken that other iso-2022 encoding than US-ASCII
should be encoded into a form of MIME.

That is correct.

This makes us difficult to communicate with the *simple* format
defined in rfc822.  I believe that the policy of rfc822 is
to exchange messages in a simple format.

RFC822 provides no mechanism for exchanging messages in any character set
other than ASCII.  Only Mime provides such a capability.  In fact, RFC822
says almost nothing about the format of message text, other than to specify
uninterpreted lines of ASCII text.  Mime was developed to fix this
limitation.

As to the 'policy' of RFC822, it is the same as for all Internet standards:
to develop conventions for open and global use of the Internet.  This
requirement means that achieving global interoperability must be pursued
through the use of common conventions, rather than conventions subject to
local modification.

When the requirement is for character sets other than ASCII, use of RFC822
without Mime is not possible to achieve in a standard way.  That is one of
the reasons that Mime was developed.

Dave

--------------------
Dave Crocker
Brandenburg Consulting                          Phone:  +1 408 246 8253
675 Spruce Dr.                                  Fax:    +1 408 249 6205
Sunnyvale, CA  94086               Email:  
dcrocker(_at_)mordor(_dot_)stanford(_dot_)edu



<Prev in Thread] Current Thread [Next in Thread>