Re: [sig-policy] Address Transfer Policy Proposal
- To: sig-policy SIG <sig-policy at apnic dot net>
- Subject: Re: [sig-policy] Address Transfer Policy Proposal
- From: Geoff Huston <gih at apnic dot net>
- Date: Thu, 23 Jul 2009 16:26:53 +1000
- Cc: Philip Smith <pfs at cisco dot com>
- Delivered-to: sig-policy at mailman dot apnic dot net
- In-reply-to: <4A6694C7.1060702 at lpnz dot org>
- List-archive: <http://mailman.apnic.net/mailing-lists/sig-policy>
- List-help: <mailto:firstname.lastname@example.org?subject=help>
- List-id: APNIC SIG on resource management policy <sig-policy.lists.apnic.net>
- List-post: <mailto:email@example.com>
- List-subscribe: <http://mailman.apnic.net/mailman/listinfo/sig-policy>, <mailto:firstname.lastname@example.org?subject=subscribe>
- List-unsubscribe: <http://mailman.apnic.net/mailman/listinfo/sig-policy>, <mailto:email@example.com?subject=unsubscribe>
- References: <F72ACDCB-D54B-434C-B133-95A94C44C6A9@apnic.net> <AA9D0B9A-A156-4DE8-BDD7-F31690B88175@apnic.net> <4A5EA683.firstname.lastname@example.org><4A5EAF49.email@example.com> <4A5EB00C.firstname.lastname@example.org><ED960528-E62C-4F98-A081-5D4E2DAEA7D6@terrym.net><05C56983-902F-49F4-BC84-6C997FA64407@apnic.net> <99C7ABB5-D340-4E71-B612-FC6456A00E4B@terrym.net> <F3C84020E03AC042A63FEDCAAAC4C662429A41@SBB-MBEX-16V.bb.local> <DC5A93F4-8E5A-48D2-B9E7-9A31E2592836@apnic.net> <4A601611.email@example.com> <2D5456FF-8405-4E74-B798-044CA76E005E@terrym.net> <4A61A57E.firstname.lastname@example.org><92D2A987-17BD-4E96-A0ED-1581922B770D@lpnz.org> <email@example.com> <firstname.lastname@example.org> <4A6694C7.email@example.com>
Hi,Earlier today Philip and I have discussed the conversations that have occurred on this mailing list over the past few weeks and we believe that the following text represents a revision of proposition-50 on address transfers that includes the the general points of agreement we've seen on the mailing list.
(We've used the language of version 3 of proposal-50 as the starting point for these revisions to the proposal, as I had some private feedback some time ago that the abbreviated bullet-point format used in version 4 of this proposal made too many implicit assumptions that allowed some potential for ambiguities and misunderstandings to creep in).
We'll shortly be submitting a complete policy proposal to the policy manager at APNIC, with the following text used as section 4 (Details of the Proposal), as the deadline for submissions is looming.
Many thanks for your contributions, and I hope we've done justice to the various helpful contributions that have been made. We are hopeful that this policy proposal will be positively considered at the forthcoming Policy SIG meeting in Beijing at APNIC 28.
regards, Geoff and PhliipDisclaimer: Both Geoff and Philip are speaking for themselves and not for their respective employers
-------------------------------- APNIC will process and record IPv4 address transfer requests between current APNIC account holders following the adoption of this proposed policy, subject to the following conditions. APNIC will maintain a public log of all transfers made under this policy. Conditions on the IPv4 address block: - The minimum transfer size is a /24 - The address block must be in the range of addresses administered by APNIC. - The address block must be allocated or assigned to a current APNIC account holder. - The address block will be subject to all current APNIC policies from the time of transfer. Conditions on source of the transfer: - The source entity must be a current APNIC account holder. - The source entity must be the currently registered holder of the IPv4 address resources, and not be involved in any dispute as to the status of those resources. - The source entity will be ineligible to receive any further IPv4 address allocations or assignments from APNIC for a period of 12 months after the transfer, or until the exhaustion of APNIC's IPv4 space (i.e. until the commencement of the use of the "final /8" resources), whichever occurs first. - Under exceptional circumstances a member may submit an application for further assignments or allocations earlier than the expiration of this period. The APNIC Secretariat will monitor these exceptional requests carefully and publish comprehensive statistics on a regular basis. Without identifying any member organization, these statistics will record the numbers of requests and the outcome, the economy that the requests come from and clearly identify if any member has made more than one request under this provision. Conditions on recipient of the transfer: - The recipient entity must be a current APNIC account holder. - The recipient entity of the transferred resources will be subject to current APNIC policies. In particular, in any subsequent APNIC IPv4 address allocation request, the recipient will be required to account for the efficient utilization of all IPv4 address space held, including all transferred resources. - Prior to the exhaustion of APNIC's IPv4 space (i.e. prior to the use of the "final /8" allocation measures) recipients of transfers will be required to justify their need for address space. After this time there is no requirement for any form of evaluation of requirements for eligibility. Applicability to NIRs: - NIRs have the choice as to when to adopt this policy for their members (i.e. members of NIRs) Implementation: - This proposal is to take effect as soon as the APNIC Secretariat implement the mechanisms of the policy following the completion of all steps of the Policy Development Process.