…ll range of Unicode characters, an SMTP extension to permit UTF-8 [ RFC3629 ] [ RFC5198 ] mail addressing and delivery of those extended header fields, support for internationalization of delivery and service notifications [ RFC3461 ] [ RFC3464 ], and (finally) a requirement for …

…ll range of Unicode characters, an SMTP extension to permit UTF-8 [ RFC3629 ] [ RFC5198 ] mail addressing and delivery of those extended header fields, support for internationalization of delivery and service notifications [ RFC3461 RFC3464 ], and (finally) a requirement for supp…

… data to be converted to Unicode Normalization Form C ("NFC"; see Section 3 of [RFC5198] ) and to be encoded into octets using the UTF-8 character encoding scheme ([ RFC3629 ]). For the user-id, recipients MUST support all characters defined in the "UsernameCasePreserved" profile…

…net requires support of the much larger set of characters provided by Unicode [ RFC5198 ] in both mail addresses and most header field values. Additionally, complex encoding schemes like encoded-words introduce inefficiencies as well as significant opportunities for processing er…

… data to be converted to Unicode Normalization Form C ("NFC"; see Section 3 of [RFC5198] ) and to be encoded into octets using the UTF-8 character encoding scheme ([ RFC3629 ]). For the user-id, recipients MUST support all characters defined in the "UsernameCasePreserved" profile…

…ng: A Unicode string that is encoded using UTF-8 [RFC3629] in Net-Unicode form [RFC5198]. Note that here, and in all other places where UTF-8 encoding is used in the CoAP protocol, the intention is that the encoded strings can be directly used and compared as opaque byte strings …

…net requires support of the much larger set of characters provided by Unicode [ RFC5198 ] in both mail addresses and most header field values. Additionally, complex encoding schemes like encoded-words introduce inefficiencies as well as significant opportunities for processing er…

… data to be converted to Unicode Normalization Form C ("NFC"; see Section 3 of [RFC5198] ) and to be encoded into octets using the UTF-8 character encoding scheme ([ RFC3629 ]). For the user-id, recipients MUST support all characters defined in the "UsernameCasePreserved" profile…

…efined in [RFC3629], but kept in this document for reasons of convenience. See [RFC5198] for a discussion of normalization; the use of normalization form NFC is RECOMMENDED. Abel Experimental [Page 5] RFC 5335 I18N Email Headers September 2008 4.2. Changes on MIME Headers This sp…

…ode Standard Annex #15 [UAX15] for background information). In accordance with [RFC5198], normalization form C (NFC) is RECOMMENDED. 5.2.5. Directionality Rule The directionality rule of a profile specifies how to treat strings containing what are often called "right-to-left" (RT…

…efined in [RFC3629], but kept in this document for reasons of convenience. See [RFC5198] for a discussion of normalization; the use of normalization form NFC is RECOMMENDED. 4.2. Changes on MIME Headers This specification updates Section 6.4 of [RFC2045]. [RFC2045] prohibits appl…

…formational UTF-8 text, conforming to the restrictions defined in Section 2 of [RFC5198] , and ending with a line break, 2. a URI section that is comprised of one or more ordered lines, each containing a TA URI, and ending with a line break, 3. a line break, and 4. a subjectPubli…

…ned in [ RFC3629 ], but kept in this document for reasons of convenience. See [ RFC5198 ] for a discussion of normalization; the use of normalization form NFC is RECOMMENDED. Abel Experimental [Page 5] RFC 5335 I18N Email Headers September 2008 4.2 . Changes on MIME Headers This …

… Standard Annex #15 [ UAX15 ] for background information). In accordance with [ RFC5198 ], normalization form C (NFC) is RECOMMENDED. 5.2.5 . Directionality Rule The directionality rule of a profile specifies how to treat strings containing what are often called "right-to-left" (…

…ned in [ RFC3629 ], but kept in this document for reasons of convenience. See [ RFC5198 ] for a discussion of normalization; the use of normalization form NFC is RECOMMENDED. Abel Experimental [Page 5] RFC 5335 I18N Email Headers September 2008 4.2 . Changes on MIME Headers This …