Skip to main content

.post Agreement Amendment

Comment/Reply Periods (*) Important Information Links
Comment Open: 9 April 2012
Comment Close: 9 May 2012
Close Time (UTC): 23:59 UTC Public Comment Announcement
Reply Open: 10 May 2012 To Submit Your Comments (Forum Closed)
Reply Close: 30 May 2012 View Comments Submitted
Close Time (UTC): 23:59 UTC Report of Public Comments
Brief Overview
Originating Organization: ICANN
Categories/Tags: Contracted Party Agreements
Purpose (Brief): ICANN is posting today for public comment the Universal Postal Union (UPU) request to amend its 2009 Sponsorship TLD agreement to remove the requirement to reserve the "previously-reserved IANA domain strings" at the second level. The UPU is the registry responsible for the management of .post generic top-level domain. This amendment, if approved, means that .post would be allowed to register second-level domains, like, for example,,, etc. Comments may be submitted through 9 May, 2012 and can be accessed here.
Current Status: UPU is seeking amendment to its 2009 sponsorship agreement.
Next Steps: Once the public comments are reviewed, the ICANN will consider the amendment.
Staff Contact: Kurt Pritz Email:
Detailed Information
Section I: Description, Explanation, and Purpose

ICANN is posting today for public comment the Universal Postal Union (UPU) request to amend its 2009 Sponsorship TLD agreement to remove the requirement to reserve the "previously-reserved IANA domain strings" at the second level. This amendment means that .post would be allowed to register, for example,,, etc. Comments may be submitted through 9 May 2012.

It is worth mentioning that these "previously-reserved IANA domain strings" at the second-level are in many cases already registered in existing gTLDs. These names are also not going to be required to be reserved in new gTLDs pursuant to advice from the Generic Names Supporting Organization (GNSO).

The UPU submitted the request to ICANN in accordance with the Registry Services Evaluation Policy (RSEP) and process set forth at The UPU .post RSEP request can be found here [PDF, 25 KB].

ICANN has conducted a preliminary review and did not identify any significant competition, security or stability issues. The implementation of this request requires a modification to the .post TLD Sponsorship Agreement signed 11 December 2009. This public comment seeks community feedback on the proposed amendment. Below is the redlined version of the proposed amendment:

Section II: Background
The Universal Postal Union (UPU) signed a sponsor agreement with ICANN in 2009. UPU is a specialized agency of the United Nations, represented by the Director General of its International Bureau, whose purpose is to secure the organization and improvement of the postal services, to promote in this sphere the development of international collaboration and to take part, as far as possible, in postal technical assistance sought by its member countries.
Section III: Document and Resource Links
Section IV: Additional Information

(*) Comments submitted after the posted Close Date/Time are not guaranteed to be considered in any final summary, analysis, reporting, or decision-making that takes place once this period lapses.

Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as"""" is not an IDN."