…for resolution via the DNS, the name must be transformed to the IDNA encoding [ RFC3490 ] prior to name lookup. URI producers should provide these registered names in the IDNA encoding, rather than a percent-encoding, if they wish to maximize interoperability with legacy URI reso…

… for resolution via the DNS, the name must be transformed to the IDNA encoding [RFC3490] prior to name lookup. URI producers should provide these registered names in the IDNA encoding, rather than a percent-encoding, if they wish to maximize interoperability with legacy URI resol…

…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…

…itional terms entered the IETF's vocabulary as part of the earlier IDN effort [ RFC3490 ] (IDNA2003): Stringprep Stringprep [ RFC3454 ] provides a model and character tables for preparing and handling internationalized strings. It was used in the original IDN specification (IDNA2…

…for resolution via the DNS, the name must be transformed to the IDNA encoding [ RFC3490 ] prior to name lookup. URI producers should provide these registered names in the IDNA encoding, rather than a percent-encoding, if they wish to maximize interoperability with legacy URI reso…

…ngs ("stringprep")", RFC 3454, December 2002. http://ietf.org/rfc/rfc3454.txt [ RFC3490 ] Faltstrom, P., Hoffman, P. and A. Costello, "Internationalizing Domain Names in Applications (IDNA)", RFC 3490, March 2003. http://ietf.org/rfc/rfc3490.txt [ RFC3491 ] Hoffman, P. and M. Bla…

…me (with both the AllowUnassigned and UseSTD3ASCIIRules flags set both times). [RFC3490] If ToASCII fails to convert one of the components of the string, e.g. because it is too long or because it contains invalid characters, or if the origin of the script has no domain part, then…

…d a few references to documents that have seen new revisions (RFC4281, RFC2313, RFC3490, MPEG-DASH) and provided a more stable link to BECSS. Added a note about and made some modifications to the URL reference. A number of small styling tweaks were made and typos were fixed. This…

…name part, if present, using the ToASCII operation specified in Section 4.1 of [RFC3490] with the flags UseSTD3ASCIIRules and AllowUnassigned set to TRUE. Escape all additional characters as follows: Each additional character is converted to UTF-8 [RFC3629] as one or more bytes. …

…me (with both the AllowUnassigned and UseSTD3ASCIIRules flags set both times). [RFC3490] If ToASCII fails to convert one of the components of the string, e.g. because it is too long or because it contains invalid characters, or if the origin of the script has no domain part, then…

…ringprep")", RFC 3454, December 2002. https://www.rfc-editor.org/info/rfc3454 [ RFC3490 ] Faltstrom, P., Hoffman, P. and A. Costello, "Internationalizing Domain Names in Applications (IDNA)", RFC 3490, March 2003. https://www.rfc-editor.org/info/rfc3490 [ RFC3491 ] Hoffman, P. an…

…rs other than Latin A(a)-Z(z), digits 0-9 and the hyphen (-) in domain names in RFC3490 , RFC3491 and RFC3492 in 2002 (published in 2003 and often referenced collectively as "IDNA2003"). These documents depend on RFC 3454 and were tied to Unicode version 3.2. An update to the cur…

…alizing Domain Names in Applications (IDNA) specification. [RFC3986] [RFC3987] [RFC3490] The following terms are defined in the Cookie specification: [COOKIES] cookie-string receives a set-cookie-string CORS The following terms are defined in the CORS specification: [CORS] cross-…

…e same email with inclusion . See 1.3.2 DOM URIs in 7 May 2003 DOM 3 Core draft RFC3490: Internationalizing Domain Names in Applications (IDNA) See TB's proposed step forward on IRI 27. RFC 3987 is a Proposed Standard Action history CL accepted on 7 Apr 2003 Revise position state…

…use it contains invalid characters, then return an error and abort these steps [RFC3490] If parsing resulted in a <path> component, then replace the matching substring of with the string that results from applying the following steps to each character other than U+0025 PERCENT SI…