…tal variant of Internet mail that permits the use of Unicode encoded in UTF-8 [ RFC3629 ], rather than ASCII, as the base form for Internet email header fields. This form is permitted in transmission, if authorized by the SMTP extension specified in [ RFC5336 ] or by other transp…

…onger than 123 bytes, then throw a SYNTAX_ERR exception and abort these steps. [RFC3629] Run the first matching steps from the following list: If the readyState attribute is in the CLOSING (2) or CLOSED (3) state Do nothing. The connection is already closing or is already closed.…

…tal variant of Internet mail that permits the use of Unicode encoded in UTF-8 [ RFC3629 ], rather than ASCII, as the base form for Internet email header fields. This form is permitted in transmission, if authorized by the SMTP extension specified in [ RFC5336 ] or by other transp…

…alized email addresses in envelopes, and UNICODE characters (encoded in UTF-8) [RFC3629] in headers. 1.1. Role of This Specification The framework document specifies the requirements for, and describes components of, full internationalization of electronic mail. A thorough unders…

… defined in Appendix B of [RFC5234] and the UTF-8 syntax rules in Section 4 of [RFC3629] . UTF-8 Address Type "An Extensible Message Format for Delivery Status Notifications" RFC3464 ] defines the concept of an address type. The address format introduced in "Internationalized Ema…

… defined in Appendix B of [RFC5234] and the UTF-8 syntax rules in Section 4 of [RFC3629] . UTF-8 Address Type "An Extensible Message Format for Delivery Status Notifications" RFC3464 ] defines the concept of an address type. The address format introduced in "Internationalized Ema…

…lized email addresses in envelopes, and UNICODE characters (encoded in UTF-8) [ RFC3629 ] in headers. 1.1 . Role of This Specification The framework document specifies the requirements for, and describes components of, full internationalization of electronic mail. A thorough unde…

…C1939] using the POP3 extension mechanism [RFC2449] to permit un-encoded UTF-8 [RFC3629] in headers, as described in "Internationalized Email Headers" [RFC5335]. It also adds a mechanism to support login names and passwords outside the ASCII character set, and a mechanism to supp…

…9 ] using the POP3 extension mechanism [ RFC2449 ] to permit un-encoded UTF-8 [ RFC3629 ] in headers, as described in "Internationalized Email Headers" [ RFC5335 ]. It also adds a mechanism to support login names and passwords outside the ASCII character set, and a mechanism to s…

…her a locale-specific encoding such as ISO-8859-1 ([ ISO-8859-1 ]), or UTF-8 ([ RFC3629 ]). For backwards compatibility reasons, this specification continues to leave the default encoding undefined, as long as it is compatible with US-ASCII (mapping any US-ASCII character to a si…

…ch lines MUST NOT begin with "SSH-", and SHOULD be encoded in ISO-10646 UTF-8 [ RFC3629 ] (language is not specified). Clients MUST be able to process such lines. Such lines MAY be silently ignored, or MAY be displayed to the client user. If they are displayed, control character …

… "stringprep" algorithm [ RFC3454 ] as the normalization algorithm to a UTF-8 [ RFC3629 ] encoded "str". The resulting string is also in UTF-8. When applying SASLprep, "str" is treated as a "stored strings", which means that unassigned Unicode codepoints are prohibited (see Secti…

…rt binary source text MUST support binary source text encoded using the UTF-8 [ RFC3629 ] character encoding scheme. Other character encoding schemes MAY be supported. Use of UTF-8 to encode binary source text is encouraged but not required. 4.1 . Charset Parameter The charset pa…

…3536 ] for internationalization terminology) for vCard is UTF-8 as defined in [ RFC3629 ]. There is no way to override this. It is invalid to specify a value other than "UTF-8" in the "charset" MIME parameter (see Section 10.1 ). 3.2 . Line Delimiting and Folding Individual lines…

…ch lines MUST NOT begin with "SSH-", and SHOULD be encoded in ISO-10646 UTF-8 [ RFC3629 ] (language is not specified). Clients MUST be able to process such lines. Such lines MAY be silently ignored, or MAY be displayed to the client user. If they are displayed, control character …