…: Convert the host name to a sequence of NR-LDH labels (see Section 2.3.2.2 of [RFC5890] Klensin, J., “Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework,” August 2010. ) and/or A-labels according to the appropriate IDNA specification [RFC5…

…s not a Non-Reserved LDH (NR-LDH) label, to an A-label (see Section 2.3.2.1 of [RFC5890] for the former and latter), or to a "punycode label" (a label resulting from the "ToASCII" conversion in Section 4 of [RFC3490] ), as appropriate (see Section 6.3 of this specification). Bart…

…minology used to describe IDNA concepts is defined in the Definitions document [RFC5890]. The terminology used for the Bidi properties of Unicode characters is taken from the Unicode Standard [Unicode52]. The Unicode Standard specifies a Bidi property for each character. That pro…

…odels such as those of Internationalizing Domain Names in Applications (IDNA) [ RFC5890 ], Preparation, Enforcement, and Comparison of Internationalized Strings (PRECIS) [ RFC7613 ], or the Unicode Identifier and Pattern Syntax specification [ UAX31 ]. Saint-Andre & Klensin Stand…

…odels such as those of Internationalizing Domain Names in Applications (IDNA) [ RFC5890 ], Preparation, Enforcement, and Comparison of Internationalized Strings (PRECIS) [ RFC7613 ], or the Unicode Identifier and Pattern Syntax specification [ UAX31 ]. Saint-Andre & Klensin Stand…

…r (e.g., in a Host: header); per current standards, the A-label as defined in [ RFC5890 ] will be used. Lowercase ASCII characters SHOULD be used. The canonical format for strings is quoted-string (as it may contain equals signs ("="), plus signs ("+"), and slashes ("/")), unless…

…odels such as those of Internationalizing Domain Names in Applications (IDNA) [ RFC5890 ], Preparation, Enforcement, and Comparison of Internationalized Strings (PRECIS) [ RFC7613 ], or the Unicode Identifier and Pattern Syntax specification [ UAX31 ]. Saint-Andre & Klensin Stand…

…port of internationalized domain names through the use of A-labels defined in [ RFC5890 ]. DNS hostnames are case-insensitive. The algorithm to compare hostnames is described in [ RFC5890 ], Section 2.3.2.4 Literal IPv4 and IPv6 addresses are not permitted in "HostName". It is RE…

… an internationalized domain name, it MUST use the A-label form as defined in [ RFC5890 ]. For example, to request a TLSA resource record for an HTTP server running TLS on port 443 at "www.example.com", "_443._tcp.www.example.com" is used in the request. To request a TLSA resourc…

…lized domain names MUST be encoded as A-labels, as described in Section 2.3 of [RFC5890] . If the <sender> has no local-part, substitute the string "postmaster" for the local-part. 4.4 . Record Lookup In accordance with how the records are published (see Section 3 above), a DNS q…

…of code specified by the attacker). The security considerations of [ STD66 ], [ RFC5890 ], [ RFC5891 ], and [ RFC3987 ] also apply. Implementers and users are advised to check them carefully. Duerst, et al. Standards Track [Page 13] RFC 6068 The 'mailto' URI Scheme October 2010 8…

…ty. 2 . Terminology Many important terms used in this document are defined in [ RFC5890 ], [ RFC6365 ], [ RFC7564 ], and [ Unicode ]. The term "non-ASCII space" refers to any Unicode code point having a Unicode general category of "Zs", with the exception of U+0020 (here called "…

…standard at the time of this writing, normally called "IDNA2008", is defined in RFC5890 RFC5891 RFC5892 RFC5893 , and RFC5894 . These documents define many IDN-specific terms such as "LDH label", "A-label", and "U-label". RFC6365 defines more terms that relate to internationaliza…

…ues that begin with the ASCII- Compatible Encoding prefix "xn--" as defined in [RFC5890] are properly encoded. Wildcard domain names (with "*" as the first label) MUST NOT be included in authorization objects. If an authorization object conveys authorization for the base domain o…

… to be a dot-separated sequence of LDH labels, as defined in Section 2.3.1 of [ RFC5890 , where: the sequence does not begin or end with an ASCII dot, and all labels are at most 63 octets. Clients additionally SHOULD ignore the structure if the final LDH label either consists of …