| CARVIEW |
Select Language
HTTP/2 200
date: Tue, 15 Jul 2025 00:57:55 GMT
content-type: text/html; charset=utf-8
cf-ray: 95f54ef69eb03e92-BLR
cf-cache-status: DYNAMIC
last-modified: Tue, 30 Jul 2024 05:47:05 GMT
vary: Accept-Encoding
x-content-type-options: nosniff
strict-transport-security: max-age=15552000; preload
server: cloudflare
content-encoding: gzip
[sig-policy] End of Comment Period: prop-107-v001: AS number transfer po
[sig-policy] End of Comment Period: prop-107-v001: AS number transfer po
- To: SIG policy <sig-policy at apnic dot net>
- Subject: [sig-policy] End of Comment Period: prop-107-v001: AS number transfer policy proposal
- From: Masato Yamanishi <myamanis at japan-telecom dot com>
- Date: Wed, 06 Nov 2013 17:21:45 -0800
- Delivered-to: sig-policy at mailman dot apnic dot net
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apnic.net; s=c3po; h=received:received:x-google-dkim-signature:x-gm-message-state:x-received: return-path:received:user-agent:date:subject:from:to:cc:message-id: thread-topic:mime-version:content-type; bh=ibWUGi4STeSfCCuMDRtyNXP926YEhW8l2Wt6whptqAQ=; b=LxiDs7bTBunZQTmhzQZKq06GHPhtS8yHZOO7fPtmqdFp1UQHQdMrEmlZCMJ5M0h7NIVrlReAwYHg2 KC4B1M6yxdi/op/paUQL0eWDP+DK60kW3YvHRjzBH0UYuSb+EmbSm0ftqPuzdr9qZsIy8XHlaN0aq4 4s+T36/ll0Xpzn04=
- List-archive: <https://mailman.apnic.net/mailing-lists/sig-policy/>
- List-help: <mailto:sig-policy-request@lists.apnic.net?subject=help>
- List-id: APNIC SIG on resource management policy <sig-policy.lists.apnic.net>
- List-post: <mailto:sig-policy@lists.apnic.net>
- List-subscribe: <https://mailman.apnic.net/mailman/listinfo/sig-policy>, <mailto:sig-policy-request@lists.apnic.net?subject=subscribe>
- List-unsubscribe: <https://mailman.apnic.net/mailman/options/sig-policy>, <mailto:sig-policy-request@lists.apnic.net?subject=unsubscribe>
- Thread-topic: End of Comment Period: prop-107-v001: AS number transfer policy proposal
- User-agent: Microsoft-MacOutlook/14.3.8.130913
- Prev by Date: [sig-policy] End of Comment Period: prop-105-v002: Distribution of returned IPv4 address blocks
- Next by Date: [sig-policy] End of Comment Period: prop-108-v002: Suggested changes to the APNIC Policy Development Process
- Previous by thread: [sig-policy] End of Comment Period: prop-105-v002: Distribution of returned IPv4 address blocks
- Next by thread: [sig-policy] End of Comment Period: prop-108-v002: Suggested changes to the APNIC Policy Development Process
- Index(es):
Dear Colleagues, On behalf of Andy Linton, Policy SIG chair, I would like to inform you that the final comment period of prop-107-v001 has ended as follows. ____________________________________________________________________ prop-107-v001: AS number transfer policy proposal _____________________________________________________________________ Dear colleagues The eight-week final comment period for the proposal 'AS number transfer policy proposal' has ended. During the comment period there were no objections raised to the proposal. The Chairs therefore deem that consensus has been maintained on the proposal. We formally request that the APNIC Executive Council endorse this proposal. For a detailed history of this proposal see: Regards APNIC Policy SIG Chairs Andy, Masato ---------------------------------------------------------------------- prop-107-v001: AS number transfer policy proposal ---------------------------------------------------------------------- Author: Tomohiro Fujisaki <fujisaki at syce dot 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: ARIN: There is a AS number transfer policy in the ARIN region. No other RIRs implement AS number transfer policy. Inter-RIR transfer policy: ARIN: 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. 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 numbers. Inter-regional AS number transfers may take place only via RIRs who agree to the transfer and share reciprocal, compatible, needs-based policies. 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: |