…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 …

…l UTF-8 text RFC3629 , conforming to the restrictions defined in Section 2 of [ RFC5198 . The leading "#" character that is used to denote a comment in RFC8630 is omitted here. certificateURIs: This field is semantically equivalent to the URI section defined in Section 2.2 of [ R…

… %d32 to %d126 inclusive) using the "Network Virtual Terminal" (NVT) encoding [ RFC5198 ]. The message header usually contains characters only from the ASCII repertoire, in the NVT encoding. This has been observed even in cases where a different encoding (e.g., UTF-8) has been us…

…sword 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 ]. Shekh-Yusef, et al. Standards Track [Page 20] RFC 7616 HTTP Digest Access Authentication September 2015 …

…sword 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 ]. Shekh-Yusef, et al. Standards Track [Page 20] RFC 7616 HTTP Digest Access Authentication September 2015 …

…nd is sometimes described as the "Network Virtual Terminal" or "NVT" encoding [ RFC5198 ]. Less formally, "ASCII" and "NVT" are often used interchangeably. However, "non-ASCII" refers only to characters outside the ASCII repertoire and is not linked to a specific encoding. See Se…