…-ASCII = UTF8-2 / UTF8-3 / UTF8-4 ; UTF8-2, UTF8-3, and UTF8-4 are defined in [ RFC3629 ] CONTROL = %x00-08 / %x0A-1F / %x7F ; All the controls except HTAB The property value component of a content line has a format that is property specific. Refer to the section describing each …

… Unicode characters where that makes sense, an SMTP Extension to permit UTF-8 [ RFC3629 ] mail addressing and delivery of those extended headers, and (finally) a requirement for support of the 8BITMIME SMTP extension [ RFC1652 ] so that all of these can be transported through the…

…valid JID is a string of Unicode code points [ Unicode ], encoded using UTF-8 [ RFC3629 ], and structured as an ordered sequence of localpart, domainpart, and resourcepart, where the first two parts are demarcated by the '@' character used as a separator and the last two parts ar…

…ode characters, which may or may not be members of the ASCII subset, in UTF-8 [ RFC3629 ], a standard Unicode Encoding Form. All other specialized terms used in this specification are defined in the framework document or in the base Internet email specifications. In particular, t…

… A valid JID is a string of Unicode code points [Unicode], encoded using UTF-8 [RFC3629], and structured as an ordered sequence of localpart, domainpart, and resourcepart, where the first two parts are demarcated by the '@' character used as a separator and the last two parts are…

…code characters, which may or may not be members of the ASCII subset, in UTF-8 [RFC3629], a standard Unicode Encoding Form. All other specialized terms used in this specification are defined in the framework document or in the base Internet email specifications. In particular, th…

…ters) The name of the data channel as a UTF-8-encoded string, as specified in [ RFC3629 ] . This may be an empty string. ¶ Protocol: Variable Length (sequence of characters) If this is an empty string, the protocol is unspecified. If it is a non-empty string, it specifies a proto…

…valid JID is a string of Unicode code points [ Unicode ], encoded using UTF-8 [ RFC3629 ], and structured as an ordered sequence of localpart, domainpart, and resourcepart, where the first two parts are demarcated by the '@' character used as a separator and the last two parts ar…

…SHOULD all first be encoded as octets according to the UTF-8 character encoding RFC3629 ], in accordance with Section 2.5 of [RFC3986] ; then, only those octets that do not correspond to characters in the unreserved set or to permitted characters from the reserved set SHOULD be p…

…options in the templates. string: 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 co…

…ode characters, which may or may not be members of the ASCII subset, in UTF-8 [ RFC3629 ], a standard Unicode Encoding Form. All other specialized terms used in this specification are defined in the framework document or in the base Internet email specifications. In particular, t…

…nt. 2.1. Convert the character to a sequence of one or more octets using UTF-8 [RFC3629]. 2.2. Convert each octet to %HH, where HH is the hexadecimal notation of the octet value. Note that this is identical to the percent-encoding mechanism in section 2.1 of [RFC3986]. To reduce …

…ilize the full 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 requirem…

…cement steps according to the OpaqueString profile (see [ RFC7613 ]) to a UTF-8 RFC3629 ] encoded "str". The resulting string is also in UTF-8. Note that implementations MUST either implement OpaqueString profile operations from [ RFC7613 ] or disallow the use of non US-ASCII Uni…

…valid JID is a string of Unicode code points [ Unicode ], encoded using UTF-8 [ RFC3629 ], and structured as an ordered sequence of localpart, domainpart, and resourcepart, where the first two parts are demarcated by the '@' character used as a separator and the last two parts ar…