…uments in the set as "Rationale". It is not normative. o A document, RFC 5891 [ RFC5891 ], that describes the core IDNA2008 protocol and its operations. In combination with the Bidi document, described immediately below, it explicitly updates and replaces RFC 3490 . It is referre…

…ocuments in the set as "Rationale". It is not normative. o A document, RFC 5891 RFC5891 ], that describes the core IDNA2008 protocol and its operations. In combination with the Bidi document, described immediately below, it explicitly updates and replaces RFC 3490 . It is referre…

…4 ], [ RFC1035 ], and [ RFC1123 ], and the modern IDNA standards [ RFC5890 ], [ RFC5891 ], and [ RFC5892 ]. [[NB: The syntax below assumes that Perl Compatible Regular Expressions 2 [ PCRE2 ] is being used, such that \xnn and \x{...} refer to valid Unicode scalar values, i.e., we…

… that are written from right to left. It is part of the revised IDNA protocol [ RFC5891 ]. When labels satisfy the rule, and when certain other conditions are satisfied, there is only a minimal chance of these labels being displayed in a confusing way by the Unicode bidirectional…

…formed to the Internationalizing Domain Names in Applications (IDNA) encoding [ RFC5891 ] where appropriate. URI producers SHOULD provide these domain names in the IDNA encoding, rather than percent-encoded, if they wish to maximize interoperability with legacy 'mailto' URI inter…

…s that are written from right to left. It is part of the revised IDNA protocol [RFC5891]. When labels satisfy the rule, and when certain other conditions are satisfied, there is only a minimal chance of these labels being displayed in a confusing way by the Unicode bidirectional …

…nsformed to the Internationalizing Domain Names in Applications (IDNA) encoding RFC5891 ] where appropriate. URI producers SHOULD provide these domain names in the IDNA encoding, rather than percent-encoded, if they wish to maximize interoperability with legacy 'mailto' URI inter…

…ual label strings, using the procedures defined in Sections 5.3 through 5.5 of [RFC5891]. Otherwise, when implementing IDNA2003, convert each label using the "ToASCII" conversion in Section 4 of [RFC3490] (see also the definition of "equivalence of labels" in Section 2 of [RFC349…

…al label strings, using the procedures defined in Sections 5.3 through 5.5 of [ RFC5891 ]. Otherwise, when implementing IDNA2003, convert each label using the "ToASCII" conversion in Section 4 of [RFC3490] (see also the definition of "equivalence of labels" in Section 2 of [RFC34…

…al label strings, using the procedures defined in Sections 5.3 through 5.5 of [ RFC5891 ]. Otherwise, when implementing IDNA2003, convert each label using the "ToASCII" conversion in Section 4 of [RFC3490] (see also the definition of "equivalence of labels" in Section 2 of [RFC34…

…al label strings, using the procedures defined in Sections 5.3 through 5.5 of [ RFC5891 ]. Otherwise, when implementing IDNA2003, convert each label using the "ToASCII" conversion in Section 4 of [RFC3490] (see also the definition of "equivalence of labels" in Section 2 of [RFC34…

…al label strings, using the procedures defined in Sections 5.3 through 5.5 of [ RFC5891 ]. Otherwise, when implementing IDNA2003, convert each label using the "ToASCII" conversion in Section 4 of [RFC3490] (see also the definition of "equivalence of labels" in Section 2 of [RFC34…

…. Therefore, the newer IDNA specifications, here called "IDNA2008" ([RFC5890], [RFC5891], [RFC5892], [RFC5893], [RFC5894]), no longer use Stringprep and Nameprep. This migration away from Stringprep for IDNs prompted other "customers" of Stringprep to consider new approaches to t…

… a general familiarity with the terminology and functions of IDNA [ RFC5890 ] [ RFC5891 ] [ RFC5892 ] [ RFC5893 ] [ RFC5894 ] are also assumed. 3 . Problem Statement Internationalizing Domain Names in Applications (IDNA) [ RFC5890 ] permits internationalized domain names, but dep…

…ent is an A-label, use the corresponding U-label instead (see [ RFC5890 ] and [ RFC5891 ]). 2. Otherwise, use the component verbatim. 5. If the port part of the origin triple is different from the default port for the protocol given by the scheme part of the origin triple: 1. App…