…ernationalized Domain Names in Applications (IDNA): Protocol,” August 2010. or [RFC3490] Faltstrom, P., Hoffman, P., and A. Costello, “Internationalizing Domain Names in Applications (IDNA),” March 2003. (see Section 10.1 IDNA dependency and migration of this specification) Conve…

…nycode label" (a label resulting from the "ToASCII" conversion in Section 4 of [RFC3490] ), as appropriate (see Section 6.3 of this specification). Concatenate the resulting labels, separated by a %x2E (".") character. 5.1.3. Domain Matching A string domain-matches a given domain…

…ernationalized Domain Names in Applications (IDNA): Protocol,” August 2010. or [RFC3490] Faltstrom, P., Hoffman, P., and A. Costello, “Internationalizing Domain Names in Applications (IDNA),” March 2003. (see Section 10.1 IDNA dependency and migration of this specification) Conve…

…nycode label" (a label resulting from the "ToASCII" conversion in Section 4 of [RFC3490] ), as appropriate (see Section 6.3 of this specification). Barth & West Expires February 8, 2018 [Page 18] Internet-Draft Cookies: HTTP State Management Mechanism August 2017 3. Concatenate t…

…s and elsewhere as "IDNA2008". The series replaces an earlier version of IDNA [ RFC3490 ] [ RFC3491 ]. For convenience, that version of IDNA is referred to in these documents as "IDNA2003". The newer version continues to use the Punycode algorithm [ RFC3492 ] and ACE (ASCII-compa…

…il addresses. The domain part of email addresses is already internationalized [ RFC3490 ], while the local part is not. Without the extensions specified in this document, the mailbox name is restricted to a subset of 7-bit ASCII [ RFC2821 ]. Though MIME [ RFC2045 ] enables the tr…

…s and elsewhere as "IDNA2008". The series replaces an earlier version of IDNA [ RFC3490 ] [ RFC3491 ]. For convenience, that version of IDNA is referred to in these documents as "IDNA2003". The newer version continues to use the Punycode algorithm [ RFC3492 ] and ACE (ASCII-compa…

…il addresses. The domain part of email addresses is already internationalized [ RFC3490 ], while the local part is not. Without the extensions specified in this document, the mailbox name is restricted to a subset of 7-bit ASCII [ RFC2821 ]. Though MIME RFC2045 ] enables the tran…

…et /host/ be the host component of /uri/. 8. Apply the IDNA ToASCII algorithm [ RFC3490 ] to /host/, with both the AllowUnassigned and UseSTD3ASCIIRules flags set. Let /host/ be the result of the ToASCII algorithm. 9. If ToASCII fails to convert one of the components of the strin…

…ules are aligned with comparison rules established in current RFCs, including [ RFC3490 ], [ RFC3987 ], and [ RFC4518 ]. * Sections 4.1.2.4 and 4.1.2.6 incorporate the conditions for continued use of legacy text encoding schemes that were specified in [ RFC4630 ]. Where in use by…

… Cary Karp. This document draws significantly on the original version of IDNA [ RFC3490 ] both conceptually and for specific text. This second-generation version would not have been possible without the work that went into that first version and especially the contributions of it…

…], and [ RFC2580 ]. This MIB module also references [ RFC1033 ], [ RFC4252 ], [ RFC3490 ], and [ RFC3986 ]. Harrington, et al. Standards Track [Page 21] RFC 5592 Secure Shell Transport Model for SNMP June 2009 This document uses TDomain Textual Conventions for the SNMP-internal M…

…l technology for internationalized domain names (IDNs), here called "IDNA2003" [RFC3490], and Nameprep [RFC3491] was the Stringprep profile for IDNs. At the time, Stringprep was designed as a general framework so that other application protocols could define their own Stringprep …

…erent ASCII representations depending on whether the user agent uses IDNA2003 [ RFC3490 ] or IDNA2008 [ RFC5890 ]. Migrating from one IDNA algorithm to another might redraw a number of security boundaries, potentially erecting new security boundaries or, worse, tearing down secur…

…ferent ASCII representations depending on whether the user agent uses IDNA2003 [RFC3490] or IDNA2008 [RFC5890] . Migrating from one IDNA algorithm to another might redraw a number of security boundaries, potentially erecting new security boundaries or, worse, tearing down securit…