…olicy specification RFC2277 ] and the domain name internationalization standard RFC5890 1.2 . Format of the Definitions in This Document In the body of this document, the source for the definition is shown in angle brackets, such as "<ISOIEC10646>". Many definitions are shown as …

…escribed in [ RFC1035 ] or an "internationalized domain name" as described in [ RFC5890 ]. Clients and servers MUST treat the IdP-Identifier as a domain name slot [ RFC5890 ]. They also SHOULD support internationalized domain names (IDNs) in the IdP-Identifier field; if they do s…

…ve already converted any non-ASCII labels to their corresponding A-labels (see [RFC5890] ). For this reason, origin-based security policies are sensitive to the IDNA algorithm employed by the user agent. See Section 8.4 for further discussion. If there is no port component of the…

…e already converted any non-ASCII labels to their corresponding A-labels (see [ RFC5890 ]). For this reason, origin-based security policies are sensitive to the IDNA algorithm employed by the user agent. See Section 8.4 for further discussion. 6. If there is no port component of …

…lized domain names MUST be encoded as A-labels, as described in Section 2.3 of [RFC5890] . Crocker, et al. Standards Track [Page 20] RFC 6376 DKIM Signatures September 2011 ABNF: sig-d-tag = %x64 [FWS] "=" [FWS] domain-name domain-name = sub-domain 1*("." sub-domain) ; from [ RFC…

…ser" consists of any character, and domain is aninternationalized domain name [ RFC5890 ] encoded as a sequence of U-labels. The PeerConnection API MUST check this string as follows: 1. If the "domain" portion of the string is equal to the domain name of the IdP proxy, then the a…

…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). 3. C…

…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). 3. Co…

…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). 3. C…

…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). 3. C…

…e already converted any non-ASCII labels to their corresponding A-labels (see [ RFC5890 ]). For this reason, origin-based security policies are sensitive to the IDNA algorithm employed by the user agent. See Section 8.4 for further discussion. 6. If there is no port component of …

…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). 3. C…

…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). 3. Co…

…: 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). Conc…