…omponents of IRIs SHOULD be character normalized by using the Nameprep process [RFC3491]; however, for legibility purposes, they SHOULD NOT be converted into ASCII Compatible Encoding (ACE). Scheme-based normalization may also consider IDN components and their conversions to puny…

…mponents of IRIs SHOULD be character normalized by using the Nameprep process [ RFC3491 ]; however, for legibility purposes, they SHOULD NOT be converted into ASCII Compatible Encoding (ACE). Scheme-based normalization may also consider IDN components and their conversions to pun…

…N components of IRIs SHOULD be character normalized using the Nameprep process [RFC3491] Hoffman, P. and M. Blanchet, Nameprep: A Stringprep Profile for Internationalized Domain Names (IDN), March 2003. ; however, for legibility purposes, they SHOULD NOT be converted into ASCII C…

…mponents of IRIs SHOULD be character normalized by using the Nameprep process [ RFC3491 ]; however, for legibility purposes, they SHOULD NOT be converted into ASCII Compatible Encoding (ACE). Scheme-based normalization may also consider IDN components and their conversions to pun…

…mponents of IRIs SHOULD be character normalized by using the Nameprep process [ RFC3491 ]; however, for legibility purposes, they SHOULD NOT be converted into ASCII Compatible Encoding (ACE). Scheme-based normalization may also consider IDN components and their conversions to pun…

…omponents of IRIs SHOULD be character normalized by using the Nameprep process [RFC3491]; however, for legibility purposes, they SHOULD NOT be converted into ASCII Compatible Encoding (ACE). Scheme-based normalization may also consider IDN components and their conversions to puny…

…mponents of IRIs SHOULD be character normalized by using the Nameprep process [ RFC3491 ]; however, for legibility purposes, they SHOULD NOT be converted into ASCII Compatible Encoding (ACE). Scheme-based normalization may also consider IDN components and their conversions to pun…

…mponents of IRIs SHOULD be character normalized by using the Nameprep process [ RFC3491 ]; however, for legibility purposes, they SHOULD NOT be converted into ASCII Compatible Encoding (ACE). Scheme-based normalization may also consider IDN components and their conversions to pun…

…mponents of IRIs SHOULD be character normalized by using the Nameprep process [ RFC3491 ]; however, for legibility purposes, they SHOULD NOT be converted into ASCII Compatible Encoding (ACE). Scheme-based normalization may also consider IDN components and their conversions to pun…

…mponents of IRIs SHOULD be character normalized by using the Nameprep process [ RFC3491 ]; however, for legibility purposes, they SHOULD NOT be converted into ASCII Compatible Encoding (ACE). Scheme-based normalization may also consider IDN components and their conversions to pun…

…value and construction of the ACE prefix that appears in RFC 3490 or Nameprep [ RFC3491 ]. For consistency and reader convenience, IDNA2008 effectively updates that reference to point to this document. That change does not alter the prefix itself. The prefix, "xn--", is the same …

…tionalized 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 profiles. Indeed, a numb…

…ere 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-compatible encodi…

…nalized 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 profiles. Indeed, a num…

…3 specification is defined by a cluster of IETF RFCs: IDNA [ RFC3490 Nameprep [ RFC3491 Punycode [ RFC3492 Stringprep [ RFC3454 ]. IDNA2008 The IDNA2008 specification is defined by a cluster of IETF RFCs: Internationalized Domain Names for Applications (IDNA): Definitions and Doc…