Generic Top-Level Domain (gTLD) Registry Agreements

gTLD Registry Agreements establish the rights, duties, liabilities, and obligations ICANN requires of registry operators to run gTLDs.

Proposed Unsponsored TLD Agreement: Appendix C, Part 13 (.name)

ICANN | Proposed Unsponsored TLD Agreement: Appendix C, Part 13 (.name)
  ICANN Logo

Proposed Unsponsored TLD Agreement: Appendix C,
Part 13 (.name)

(3 July 2001)


Functional Specifications

Part 13 - Character Sets

This section defines the different character sets being used by the Registry Operator.

UTF-8

Usage

This character set is for use in places where arbitrary strings are to be entered. Examples of places to use this character set is names of persons, addresses, descriptive texts and communication protocols in need of transferring international content.

Also, refer to RFC 2277 (IETF Policy On Character Sets and Languages) for recommendations on when and where to implement UTF-8.

Definition

The UTF-8 character set will be interpreted according to the definition found in RFC 2279.

ISO 8859-1

Usage

This character set will mostly be used for logfile contents, error messages and console text.

Definition

The interpretation of the ISO 8859-1 is done according to the ISO documentation for the ISO 8859 character set standard.

Reduced character set

Usage

This is a character set mostly for use in places where control characters are undesirable.

Definition

The reduced character set will be interpreted as a subset of the standard specification of the 7-bit US-ASCII character set found in the following document:
7-bit American Standard Code for Information Interchange (ASCII), ANSI X3.4-1986.

The reduced character set consists of the following characters, specified in the Backus-Naur Form (BNF) meta-language.

References made to decimal character values are taken to mean corresponding US-ASCII values:

Reduced charset definition:
----------------------------

text = 1*CHAR ; max length depends on context

CHAR = (Decimal 32.-126.)

Password character set

Usage

This character set defines the characters available for specifying passwords.

Definition

The password character set will be interpreted as a subset of the standard specification of the 7-bit US-ASCII character set found in the following document:
7-bit American Standard Code for Information Interchange (ASCII), ANSI X3.4-1986.

The password character set consists of the following characters, specified in the Backus-Naur Form (BNF) meta-language.

References made to decimal character values are taken to mean corresponding US-ASCII values:

Password charset definition:
----------------------------

password = 1*CHAR ; max length depends on context

CHAR = (Decimal 33.-126.)

Domain name character set

Usage

This character set will be used in places where a domain name is to be specified. It does not govern the specification of internationalised domain names, which are not authorized by the current specification.

Definition

The rules for the format and character set of domain names are defined by the following:

dot = %x2E ; "."
alpha = %x41-5A | %x61-7A ; A-Z | a-z
digit = %x30-39 ; 0-9
dash = %x2D ; "-"
dns-char = alpha | digit | dash
id-prefix = alpha | digit
label = id-prefix [*61dns-char id-prefix]
sldn = label dot label ; not to exceed 254 characters
hostname = 1*(label dot) sldn; not to exceed 254 characters









Email address character set

Usage

This character set is for use in places where an email address is to be specified.

Definition

The rules for the format and character set of email addresses are defined by RFC 2822. Except where otherwise specified, or where restricted by other standards, Registry Operators system will allow any address that is a legal email address per the definitions given in RFC 2822 where an email address is to be used. An SLD E-mail address registered under the SLD E-mail service must, however, comply with the format rules for a third-level domain name, except that the first "." Is replaced with a "@".


Comments concerning the layout, construction and functionality of this site
should be sent to webmaster@icann.org.

Page Updated 03-Jul-2001

(c) 2001  The Internet Corporation for Assigned Names and Numbers. All rights reserved.