Skip to main content

Request for Proposals (RFP) for IANA Stewardship Transition Proposal Issued by the IANA Stewardship Transition Coordination Group

The IANA Stewardship Coordination Group (ICG) today issued a Request for Proposals (RFP) seeking complete formal responses from the "operational communities" of IANA (i.e. those with direct operational or service relationships with the IANA functions operator, in connection with names, numbers, or protocol parameters). The target deadline for all complete formal responses to this RFP is 31 December 2014.*

Proposals are expected to enjoy a broad consensus of support from all interested parties. During the development of their proposals, the operational communities are requested to consult and work with other affected parties. Likewise, in order to help the ICG maintain its light coordination role, all other affected parties are strongly encouraged to participate in community processes.

Information about ongoing community processes and how to participate in them can be found here.

Communities are asked to adhere to open and inclusive processes in developing their responses, so that all community members may fully participate in and observe those processes. Communities are also asked to actively seek out and encourage wider participation by any other parties with interest in their response.

Additionally, while the ICG is requesting complete formal proposals from the operational communities only, and that all interested parties get involved as early as possible in the relevant community processes, some parties may choose to provide comments directly to the ICG about specific aspects of particular proposals, about the community processes, or about the ICG's own processes. Comments may be directly submitted to the ICG any time via email to Comments will be publicly archived at:

The full RFP can be found here [PDF, 95 KB].

RFP Activities Schedule:

RFP Published 3 September 2014
Closing Date for Submission of Proposals 31 December 2014*

* The RFP was updated subsequent to this announcement and the target deadline was changed. Please see

More Announcements
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."