At 8:24 AM 5/7/95, Rick Busdiecker wrote:
BTW, do any of the current proposals deal with 822-compliant messages
which are not MIME compliant? Is 822 dead? Are there plans to strip
out the non-MIME-compliant parts? If someone could point me to an
The best way to think of RFC822 and MIME is separately.
RFC822 specifies a technique for creating message headers and for
the use of a few of those headers, most especially those pertaining to
naming and addressing of originators and recipients. The document says
almost nothing about the actual contents of the message. The little is
does say is trivial.
MIME is a way of creating structured, mult-media objects. It is
designed to fit nicely into the RFC822 context but does not require it.
Hence it can be used for other environments such as the Web.
(There are some critical technical nuances that I'm glossing over,
but for the current discussion, I'll let the above two paragraphs stand.)
d/
--------------------
Dave Crocker
Brandenburg Consulting +1 408 246 8253
675 Spruce Dr. fax: +1 408 249 6205
Sunnyvale, CA 94086
dcrocker(_at_)networking(_dot_)stanford(_dot_)edu