Examples of using ASCII label in English and their translations into Spanish
{-}
-
Colloquial
-
Official
Therefore an ASCII label must not be.
The ASCII label may only include hyphens in the third and fourth position if it represents a valid internationalized domain.
There must be no possibility for confusing an ASCII label for an IP address or other numerical identifier by application software.
The ASCII label may only include hyphens in the third and fourth position if it represents a valid internationalized domain name in its A-label form ASCII encoding as described in Part II.
There must be no possibility for confusing an ASCII label with an IP address or other numerical identifier.
All two-character ASCII labels shall be withheld from registration or allocated to Registry Operator at the second level within the TLD.
There must be no possibility for confusing an ASCII label with an IP address or other numerical identifier.
The following ASCII label must be allocated to Registry Operator upon delegation into the root zone at All Levels for use in connection with the operation of the registry for the TLD: NIC.
For the avoidance of doubt,Registry Operator is required to activate the ASCII label NIC pursuant to Section 3.1 of this Specification 3.
The following ASCII labels must be withheld from registration or allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: WWW, RDDS and WHOIS.
Registry Operator may activate WWW, RDDS and WHOIS in the DNS, butmust activate NIC in the DNS, as necessary for the operation of the TLD in accordance with the provisions of Exhibit A, the ASCII label NIC must be provisioned in the DNS as a zone cut using NS resource records.
There must be no possibility for confusing an ASCII label for an IP address or other numerical identifier by application software.
The ASCII label must be a valid host name, as specified in the technical standards DOD Internet Host Table Specification(RFC 952), Requirements for Internet Hosts- Application and Support(RFC 1123), and Application Techniques for Checking and Transformation of Names RFC 3696.
The following ASCII label must be allocated to Registry Operator upon delegation into the root zone at All Levels for use in connection with the operation of the registry for the TLD: NIC.
The ASCII label must be a valid host name, as specified in technical standards DOD Internet Host Table Specification(RFC 952); Requirements for Internet Hosts- Application and Support(RFC 1123); and Application Techniques for Checking and Transformation of Names RFC 3696.
The ASCII label“EXAMPLE” shall be withheld from registration or allocated to Registry Operator at the second level and at all other levels within the TLD at which Registry Operator offers registrations such second level and all other levels are collectively referred to herein as,“All Levels”.
The ASCII label must be a valid host name, as specified in the technical standards DOD Internet Host Table Specification(RFC 952), Requirements for Internet Hosts- Application and Support(RFC 1123), and Application Techniques for Checking and Transformation of Names(RFC 3696), Internationalized Domain Names in Applications 4 The string requirements have been revised according to revisions of RFC 1123 in progress in the IETF.
The presentation format of the domain(i.e., either the label for ASCII domains, or the U-label for Applicant Guidebook- Proposed Final Version 2-13 internationalized domain names) must not begin or end with a digit.5.
Generation of reports,letters, labels and ASCII files.