Lines Matching refs:ASCII
33 characters outside the ASCII repertoire. This document defines
37 repertoire (Unicode), but IDNA allows the non-ASCII characters to be
38 represented using only the ASCII characters already allowed in so-
86 IDNA works by allowing applications to use certain ASCII name labels
87 (beginning with a special prefix) to represent non-ASCII name labels.
91 elements, because the ASCII name service provided by the existing DNS
97 application wants to use non-ASCII characters in domain names, IDNA
141 in applications by using the ASCII representation of the non-ASCII
179 radio) would correctly enter the IDN. Similar issues exist for ASCII
192 anywhere that ASCII domain names are already supported, including DNS
194 protocols and interfaces that support IDNs directly using non-ASCII
209 that expects ASCII names (such as a resolver) or writing an IDN
210 into a place that expects ASCII names (such as a DNS master file).
249 ASCII means US-ASCII [USASCII], a coded character set containing 128
251 is an extension of ASCII: it includes all the ASCII characters and
255 code points associated with ASCII letters, digits, and the hyphen-
289 UseSTD3ASCIIRules flag unset). This implies that every ASCII label
292 generalization, embracing both old ASCII labels and new non-ASCII
299 ASCII domain name is an IDN (which implies that it is possible for a
300 name to be an IDN without it containing any non-ASCII characters).
302 name". Just as has been the case with ASCII names, some DNS zone
313 operation, which constructs an ASCII form for a given label, whether
314 or not the label was already an ASCII label. Labels are defined to
315 be equivalent if and only if their ASCII forms produced by ToASCII
316 match using a case-insensitive ASCII comparison. ASCII labels
324 applications, IDNA uses an "ACE label" (ACE stands for ASCII
326 that can be rendered in ASCII and is equivalent to an
327 internationalized label that cannot be rendered in ASCII. Given any
328 internationalized label that cannot be rendered in ASCII, the ToASCII
330 ASCII label will be left unaltered by ToASCII). ACE labels are
347 The "ACE prefix" is defined in this document to be a string of ASCII
387 (see section 2), it MUST contain only ASCII characters. Given an
416 if and only if they are equivalent, that is, their ASCII forms
418 ASCII comparison. Whenever two names are compared, they MUST be
430 MUST be in ASCII form (see section 3.1, requirement 2).
457 Although IDNA enables the representation of non-ASCII characters in
459 representation of non-ASCII characters in other data types that are
464 allow only ASCII characters in local parts. Therefore, unless the
478 sequence of Unicode code points (remember that all ASCII code points
480 a character set other than Unicode or US-ASCII, it will first need to
495 on ASCII characters in host names [STD3]. (Applications already
535 the ASCII range (0..7F). If ToASCII succeeds, the original sequence
546 ToASCII is either a sequence of ASCII code points or a failure
550 ASCII range to begin with (although it could fail). Applying the
556 1. If the sequence contains any code points outside the ASCII range
572 (a) Verify the absence of non-LDH ASCII code points; that is, the
579 4. If the sequence contains any code points outside the ASCII range
611 1. If all code points in the sequence are in the ASCII range (0..7F)
640 3, using a case-insensitive ASCII comparison.
647 alphanumeric ASCII characters followed by two hyphen-minuses. It
752 encoded ASCII characters or the proper decoded characters, the
778 for handling domain names in the ASCII charset. Thus, ACE labels
799 ASCII, applications MUST prepare labels that are passed to the
801 the resolver library contain only ASCII characters; internationalized
802 labels that cannot be represented directly in ASCII use the ACE form.
817 ASCII, and application developers might one day pass not only domain
832 ASCII, DNS servers MUST use the ACE form produced by the ToASCII
833 operation. All IDNs served by DNS servers MUST contain only ASCII
888 servers that cannot be represented directly in ASCII must use the ACE
892 DNSSEC authenticates the ASCII domain name, not the Unicode form or
903 the mapping between the Unicode form and the ASCII form. In the
915 ASCII forms of IDNs, and therefore need to be shielded from them.
922 converted to their equivalent ASCII forms.
924 It is imperative that there be only one ASCII encoding for a
926 ToUnicode operations, there are no ACE labels that decode to ASCII
927 labels, and therefore name servers cannot contain multiple ASCII
931 the ASCII range (0..7F), and this document does not change that.
934 to applications, unpredictable behavior could result. The ASCII form
1015 [USASCII] Cerf, V., "ASCII format for Network Interchange", RFC
1037 When systems use local character sets other than ASCII and Unicode,
1088 specified in section 3.1 requirement 4. For labels already in ASCII
1090 ASCII comparison that has always been used for ASCII labels.
1095 non-ASCII labels, whether or not that was the intent of the zone