Info & FAQ |  Resource services |  Training |  Meetings |  Membership |  Documents |  Whois & Search |  Internet community

You're here:  Home  Mailing Lists sig-policy 

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[sig-policy] prop-107-v001: AS number transfer policy proposal

Dear SIG members

The proposal "prop-107-v001: AS number transfer policy proposal"
has been sent to the Policy SIG for review. It  will be presented at the
Policy SIG at APNIC 36 in Xi'an, China, on Thursday, 29 August 2013.
We invite you to review and comment on the proposal on the mailing list
before the meeting.

The comment period on the mailing list before an APNIC meeting is an
important part of the policy development process. We encourage you to
express your views on the proposal:

     - Do you support or oppose this proposal?
     - Does this proposal solve a problem you are experiencing? If so,
       tell the community about your situation.
     - Do you see any disadvantages in this proposal?
     - Is there anything in the proposal that is not clear?
     - What changes could be made to this proposal to make it more

Information about this and other policy proposals is available from:


Andy, Masato


prop-107-v001: AS number transfer policy proposal


Author: Tomohiro Fujisaki <fujisaki@syce.net>

1. Problem statement

In the APNIC region, IPv4 transfer policy has been implemented since
February 2010.

On the other hand, there is no transfer policy for AS numbers, while
some demands for transfers of AS numbers between AS number holders are
have been observed through individual feedback to the proposal author.

- There are a few requests to transfer the AS number with IPv4 address
  at the same time. However, currently, AS numbers are not able
  transfer under the transfer policy and only under M&A.

- Currently, there is no policy for transfers of AS numbers between
  RIRs. M&A policy allows transfers of AS number only within the same
  RIR region. However, there are expected to be some cases where
  organizations wish to transfer both IPv4 address and AS number at the
  same time to an LIR in other RIR region.

- AS number is also limited resource, and it is meaningful to promote
  efficient use with transfer policy.

2. Objective of policy change
The objective of this proposal is to allow transfer of AS numbers
between organizations in the APNIC region, as well as with members of
other RIRs, if a counterpart RIR has adopted an equivalent transfer
policy for AS numbers.

3. Situation in other regions

Intra-region transfer policy:

There is a AS number transfer policy in the ARIN region.

No other RIRs implement AS number transfer policy.

Inter-RIR transfer policy:

There was a Recommended Draft Policy ARIN-2013-1 which allows Inter-RIR
ASN transfers, but it was abandoned by ARIN AC in June 2013.
(see https://www.arin.net/policy/proposals/2013_1.html)

ARIN AC said the reason as follows in their statements; (see
"Based on the feedback received at the ARIN 31 Public Policy Meeting,
and at the Public Policy Consultation at NANOG 58, the ARIN AC voted
to abandon ARIN-2013-1 "Section 8.4 Inter-RIR Transfers of ASNs".  The
feedback from the community indicated that many people felt the policy
was unnecessary as it would have no effect until/unless another RIR
expresses interest in allowing Inter-RIR ASN transfers as well.

4. Proposed policy solution
AS numbers may be transferred if recipient of the transfer will meets
the criteria under the current APNIC policy for an assignment of AS

Inter-regional AS number transfers may take place only via RIRs who
agree to the transfer and share reciprocal, compatible, needs-based

5. Explain the advantages of the proposal
Just like IPv4 addresses, AS numbers are finite resource. This proposal
promotes efficient use of AS numbers by allowing transfers of AS
numbers, which is no longer needed by the existing holders.

6. Explain the disadvantages of the proposal
No disadvantages.

7. Impact on resource holders
NIRs are able to choose whether or not to implement this policy.

8. References (if required)

ARIN's AS number transfer policy: