…e are other documents, specifically the MIME document series [RFC2045, RFC2046, RFC2047, RFC2048, RFC2049], that extend this standard to allow for values outside of that range. Discussion of those mechanisms is not within the scope of this standard. Messages are divided into line…

… so according to the following procedure: (a) MIME encoding (for example, see [ RFC2047 ] for headers and RFC2045 ] for body parts) MUST be removed in the texts being collated. If MIME encoding removal fails for a message (e.g., a body part of the message has an unsupported Conte…

…re are other documents, specifically the MIME document series [RFC2045, RFC2046 RFC2047 RFC2048 RFC2049 ], that extend this standard to allow for values outside of that range. Discussion of those mechanisms is not within the scope of this standard. Messages are divided into lines…

…her documents, specifically the MIME document series ([ RFC2045 ], RFC2046 ], [ RFC2047 ], [ RFC2049 ], [ RFC4288 ], [ RFC4289 ]), that extend this specification to allow for values outside of that range. Discussion of those mechanisms is not within the scope of this specificatio…

…her documents, specifically the MIME document series ([ RFC2045 ], RFC2046 ], [ RFC2047 ], [ RFC2049 ], [ RFC4288 ], [ RFC4289 ]), that extend this specification to allow for values outside of that range. Discussion of those mechanisms is not within the scope of this specificatio…

… can be encoded in <hfvalue> as follows: 1. MIME encoded words (as defined in [ RFC2047 ]) are permitted in header field values, but not in an <hfvalue> of a "body" <hfname>. Sequences of characters that look like MIME encoded words can appear in an <hfvalue> of a "body" <hfname>…

…es not provide a mechanism for internationalized email addresses. In RFC 2047 [ RFC2047 ], MIME defines an encoding mechanism for some specific message header fields to accommodate non-ASCII data. However, it does not permit the use of email addresses that include non-ASCII chara…

…s originally limited to [ ASCII ] in 7-bit form. MIME [ RFC2045 ] [ RFC2046 ] [ RFC2047 ] provides the ability to use additional character sets, but this support is limited to body part data and to special encoded-word constructs that were only allowed in a limited number of plac…

… Message Format [ RFC5322 ] with message header extensions for non-ASCII text [ RFC2047 ] and other 7-bit encodings. Down-conversion is specified by "Downgrading Mechanism for Email Address Internationalization" [ RFC5504 ]. 1.1 . Conventions Used in This Document The key words "…

…et Message Format RFC5322 ] with message header extensions for non-ASCII text [ RFC2047 and other 7-bit encodings. Down-conversion is specified by "Downgrading Mechanism for Email Address Internationalization" RFC5504 ]. 1.1 . Conventions Used in This Document The key words "MUST…

… ] suggested that non-ASCII field names be encoded according to the method in [ RFC2047 ], this practice doesn't seem to have been followed widely. This specification makes three sets of recommendations for three different states of workflow. 5.1.1 . Avoid Non-ASCII Field Names F…

… can be encoded in <hfvalue> as follows: 1. MIME encoded words (as defined in [ RFC2047 ]) are permitted in header field values, but not in an <hfvalue> of a "body" <hfname>. Sequences of characters that look like MIME encoded words can appear in an <hfvalue> of a "body" <hfname>…

…was originally limited to [ ASCII ] in 7-bit form. MIME RFC2045 ] [ RFC2046 ] [ RFC2047 ] provides the ability to use additional character sets, but this support is limited to body part data and to special encoded-word constructs that were only allowed in a limited number of plac…

…does not provide a mechanism for internationalized email addresses. In RFC 2047 RFC2047 ], MIME defines an encoding mechanism for some specific message header fields to accommodate non-ASCII data. However, it does not permit the use of email addresses that include non-ASCII chara…

This is a purely informative rendering of an RFC that includes verified errata. This rendering may not be used as a reference. The following 'Verified' errata have been incorporated in this document: EID 504 , EID 506 Network Working Group K. Moore Request for Comments: 2047 Univ…