Skip to main content

Global Policy Proposal for Autonomous System Numbers - Background Report | (Proposal to change the date for full transition from 16-bit to 32-bit ASNs)

Updated 3 June 2010
4 December 2009


Global Internet Number Resource Policies are defined by the ASO MOU - between ICANN and the NRO - as "Internet number resource policies that have the agreement of all RIRs according to their policy development processes and ICANN, and require specific actions or outcomes on the part of IANA or any other external ICANN-related body in order to be implemented". Attachment A of this MOU describes the Development Process of Global Internet Number Resource Policies, including the adoption by every RIR of a global policy to be forwarded to the ICANN Board by the ASO, as well as its ratification by the ICANN Board. In this context, the ICANN Board adopted its own Procedures for the Review of Internet Number Resource Policies Forwarded by the ASO for Ratification.

Among other features, these Procedures state that the Board will decide, as and when appropriate, that ICANN staff should follow the development of a particular global policy, undertaking an “early awareness” tracking of proposals in the addressing community. To this end, staff should issue background reports periodically, forwarded to the Board, to all ICANN Supporting Organizations and Advisory Committees and posted at the ICANN Web site.

At its meeting on 27 August 2009, the Board resolved to request tracking of the development of a Global Policy Proposal for "IANA Policy for Allocation of ASN Blocks to Regional Internet Registries", under discussion in the addressing community. The status overview presented below is compiled in response to this request and will be further updated as developments proceed, for information to ICANN entities and the wider community. This is the third issue of the tracking of this policy.

Status Overview

The current Global Policy for Autonomous System Numbers, ASNs, removes the policy distinction between 16-bit and 32-bit ASNs on 1 January 2010. The new Global Policy Proposal moves that date to 1 January 2011.

The proposal was first introduced in RIPE on 27 May 2009, in ARIN on 29 May 2009, in LACNIC on 1 June 2009, in APNIC on 13 July 2009 and in AfriNIC on 28 August 2009. It has now been adopted in all RIRs; RIPE, ARIN, APNIC, LACNIC and AfriNIC.

On 6 August 2009, the ASO AC recognized the proposal as fulfilling the formal requirements as a candidate for a Global Policy.

Once adopted by all the RIRs, i.e. ARIN, AfriNIC, LACNIC, RIPE and APNIC, the proposal will be handled by the NRO EC and the ASO AC according to their procedures before being submitted to the ICANN Board for ratification.

The table below outlines the steps taken within each RIR for the current proposal. Hyperlinks are included for easy access.







Proposal Introduced

28 Aug 2009
list message

13 July 2009
list message/

29 May 2009
list message/
prop 89

31 Aug 2009
prop 2009-6

1 Jun 2009
list message

27 May 2009
prop 2009-7

Discussion list

Resource Policy Discussion List


Public Policy Mailing List

Politicas – Policy Mailing List

Address Policy WG

Public Forum

AfriNIC 11
21-27 Nov 2009 (consensus)

APNIC 28 24 -28 Aug 2009 (consensus)

21 - 23 Oct 2009

Expedite process, not requiring a meeting


Final Call for Comments

2- 17 Dec 2009

31 Aug - 26 Oct 2009

28 Oct - 13 Nov 2009

31 July - 29 Sept 2009 Consensus call 7-21 Oct

19 Aug - 16 Sept 2 009

Next Public Forum

AfriNIC 12 23 May - 4 June 2010





RIR Board Endorsement

Adopted by the AfriNIC Board on 24 May 2010

Endorsed by APNIC EC 18 Nov 2009

Adopted by ARIN Board of Trustees 18 Dec 2009

Ratified by the LACNIC Board 22 Feb 2010

Accepted by the RIPE Community 28 Sept 2009

Link to document

Policy (Amendment ) AFPUB-2009-ASN-001


Proposal 2009-6

LAC-2009-08 (EN)

LAC-2009-08 (ES)

LAC-2009-08 (PT)

Policy RIPE-480



Link to Policy Development Process

Policy Development Process

Policy Development Process

Policy Development Process

Policy Development Process

Policy Development Process







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