Lines Matching +full:existing +full:- +full:parts
37 repertoire (Unicode), but IDNA allows the non-ASCII characters to be
38 represented using only the ASCII characters already allowed in so-
39 called host names today. This backward-compatible representation is
40 required in existing protocols like DNS, so that IDNs can be
41 introduced with no changes to the existing infrastructure. IDNA is
63 3.2.2. Non-domain-name data types stored in domain names... 9
87 (beginning with a special prefix) to represent non-ASCII name labels.
88 Lower-layer protocols need not be aware of this; therefore IDNA does
91 elements, because the ASCII name service provided by the existing DNS
96 maintaining interoperability with existing infrastructure. If an
97 application wants to use non-ASCII characters in domain names, IDNA
98 is the only currently-defined option. Adding IDNA support to an
99 existing application entails changes to the application only, and
127 to see an exact-match lookup service. Either there is a single
128 exactly-matching name or there is no match. This model has served
129 the existing applications well, but it requires, with or without
139 upgrades to existing infrastructure (such as DNS servers and mail
141 in applications by using the ASCII representation of the non-ASCII
142 name labels. While such names are very user-unfriendly to read and
146 allow user-friendly input and output of the IDNs, the applications
157 inputting names in different scripts. Many important language-based
158 and script-based mappings are not covered in IDNA and need to be
194 protocols and interfaces that support IDNs directly using non-ASCII
200 not a client-server or peer-to-peer protocol: everything is done
208 - The ToASCII operation is used before sending an IDN to something
212 - The ToUnicode operation is used when displaying names to users,
249 ASCII means US-ASCII [USASCII], a coded character set containing 128
255 code points associated with ASCII letters, digits, and the hyphen-
270 "com". (The zero-length root label described in [STD13], which can
292 generalization, embracing both old ASCII labels and new non-ASCII
300 name to be an IDN without it containing any non-ASCII characters).
310 zone-specific restrictions or conventions.
316 match using a case-insensitive ASCII comparison. ASCII labels
323 To allow internationalized labels to be handled by existing
332 convert any label to an equivalent non-ACE label. In fact, an ACE
334 operation would alter (whereas non-ACE labels are left unaltered by
356 following the at-sign (@) in the From: field of an email message
363 An "IDN-aware domain name slot" is defined in this document to be a
370 An "IDN-unaware domain name slot" is defined in this document to be
371 any domain name slot that is not an IDN-aware domain name slot.
386 2) Whenever a domain name is put into an IDN-unaware domain name slot
404 users when it is known that the environment can handle the non-ACE
406 is not known whether or not the environment can handle the non-ACE
407 form, the application MAY use the non-ACE form (which might fail,
417 (obtained by applying ToASCII) match using a case-insensitive
436 to every non-IN class, present and future, except where future
444 matters by imposing type-specific rules.
455 3.2.2. Non-domain-name data types stored in domain names
457 Although IDNA enables the representation of non-ASCII characters in
459 representation of non-ASCII characters in other data types that are
463 record). IDNA does not update the existing email standards, which
464 allow only ASCII characters in local parts. Therefore, unless the
466 parts, a domain label that holds the local part of an email address
473 An application converts a domain name put into an IDN-unaware slot or
480 a character set other than Unicode or US-ASCII, it will first need to
513 operation if you are about to put the name into an IDN-unaware
542 with this failure is application-specific.
572 (a) Verify the absence of non-LDH ASCII code points; that is, the
575 (b) Verify the absence of leading and trailing hyphen-minus; that
640 3, using a case-insensitive ASCII comparison.
647 alphanumeric ASCII characters followed by two hyphen-minuses. It
649 which includes the following: "bl--", "bq--", "dq--", "lq--", "mq--",
650 "ra--", "wq--" and "zq--". The ToASCII and ToUnicode operations MUST
651 recognize the ACE prefix in a case-insensitive manner.
653 The ACE prefix for IDNA is "xn--" or any capitalization thereof.
655 This means that an ACE label might be "xn--de-jg4avhby1noc0d", where
656 "de-jg4avhby1noc0d" is the part of the ACE label that is generated by
660 beginning with the ACE prefix are necessarily ACE labels. Non-ACE
689 +------+
691 +------+
695 +-------------------|-------------------------------+
697 | +-----------------------------+ |
702 | +-----------------------------+ |
705 | Call to resolver: | | Application-specific |
708 | +----------+ | protocol is updated |
710 | +----------+ | encodings |
712 +-----------------|----------|----------------------+
716 +-------------+ +---------------------+
718 +-------------+ +---------------------+
742 An IDNA-aware application can accept and display internationalized
759 pages. They are transported in many parts of many protocols, such as
760 both the control commands and the RFC 2822 body parts of SMTP, and
807 more charsets that are used in applications (UTF-8 and UTF-16 are
808 likely candidates for almost any operating system, and script-
811 IDNA-aware applications MUST be able to work with both non-
847 ACE to something else, such as UTF-8. The question whether or not
914 Existing DNS servers do not know the IDNA rules for handling non-
916 All existing channels through which names can enter a DNS server
918 [RFC2136]) are IDN-unaware because they predate IDNA, and therefore
978 [STD3] Braden, R., "Requirements for Internet Hosts --
980 "Requirements for Internet Hosts -- Application and
983 [STD13] Mockapetris, P., "Domain names - concepts and
984 facilities", STD 13, RFC 1034 and "Domain names -
1001 (Reading, MA, Addison-Wesley, 2000. ISBN 0-201-61633-5),
1086 set of privileged or anti-privileged domains. In such situations it
1089 form, the proper comparison reduces to the same case-insensitive
1092 The introduction of IDNA means that any existing labels that start
1095 non-ASCII labels, whether or not that was the intent of the zone
1132 S-117 43 Stockholm Sweden