2.3 MIME Conformance User agents MUST meet the definition of MIME-conformance in [RFC2049] and MUST also support [RFC2231]. This level of MIME Conformance provides support for internationalization and multimedia in message bodies ([RFC2045], [RFC2046], [RFC2231]), and support for internationalization of headers ([RFC2047], [RFC2231]). Note that [Errata] currently exist for [RFC2046] and [RFC2231]. For the purposes of Section 5 of [RFC2047], all headers defined in Section 3 of this standard are to be considered as "extension message header fields" (insofar as they are not already considered under the existing Email standards), permitting the use of [RFC2047] encodings within any <unstructured> header, or within any <comment> or <phrase> permittted within any structured header. User agents MAY accept and generate other MIME extension headers, and in particular SHOULD accept Content-Disposition [RFC2183] and Content-Language [RFC3282].[< Prev] [TOC] [ Next >]
Newer | Older |
---|---|
usefor-usefor May 2005 | usefor-usefor November 2004 usefor-usefor September 2004 |
--- ../usefor-usefor-02/MIME_Conformance.out November 2004 +++ ../usefor-usefor-03/MIME_Conformance.out April 2005