[sig-policy] prop-066: Ensuring efficient use of historicalIPv4 resource

  • To: "'APNIC Policy SIG List'" <sig-policy at apnic dot net>
  • Subject: [sig-policy] prop-066: Ensuring efficient use of historicalIPv4 resources
  • From: "zhangjian" <zhangjian at cnnic dot cn>
  • Date: Tue, 22 Jul 2008 16:10:07 +0800
  • Delivered-to: sig-policy at mailman dot apnic dot net
  • List-archive: <http://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: <http://mailman.apnic.net/mailman/listinfo/sig-policy>, <mailto:sig-policy-request@lists.apnic.net?subject=subscribe>
  • List-unsubscribe: <http://mailman.apnic.net/mailman/listinfo/sig-policy>, <mailto:sig-policy-request@lists.apnic.net?subject=unsubscribe>
  • Thread-index: Acjr0lrSvq1XCGdQT925kXJBofJmTw==
    • Dear SIG members


      The proposal 'Ensuring efficient use of historical IPv4 resources' has been sent to the Policy SIG for review. It will be presented at the Policy SIG at APNIC 26 in Christchurch, New Zealand, 25-29 August 2008.


      The proposal's history can be found at:




      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



      Randy and Jian




      prop-066-v001: Ensuring efficient use of historical IPv4 resources ________________________________________________________________________



      Authors:   Brenda D. Tarimel

                      btarimel at palaunet dot com


                  Philip Smith

                  pfs at cisco dot com


                  James Spenceley

                  james at vocus dot com dot au


      Version:   1


      Date:      22 July 2008



      1.  Introduction



      This is a proposal to include all historical address allocations when assessing a network's eligibility for more IPv4 addresses.



      2.  Summary of current problem



      The unallocated pool of IPv4 addresses is predicted to run out within the next few years.  As the unallocated pool dwindles, it is important to ensure that the remaining IPv4 addresses are allocated responsibly and fairly.


      Currently, when LIRs apply for new IPv4 allocations from APNIC, they only have to include the past allocations they have received from APNIC as part of the documentation and justification process. They do not have to declare any historical addresses [1] they may have received prior to receiving address space from APNIC.


      As a result of this, there is a large amount of historical IPv4 address space where little or nothing is known about its use.


      At the moment LIRs can receive more scarce IPv4 address space from APNIC while at the same time hoarding unused historical address space.  This uses up the remaining IPv4 pool more rapidly than is really necessary.



      3.  Situation in other RIRs



      The other RIRs do not currently include historical allocations when assessing requests for allocations from the RIR pools.


      This proposal has not been submitted to any other region.



      4.  Details of the proposal



      This is a proposal to modify the criteria for receiving IPv4 address space so that both historical addresses and previous allocations are included.


           - This proposal applies to all historical IPv4 resources

             registered in the APNIC Whois Database.


           - Historical IPv4 resources that are not managed under the

             existing historical maintenance or transfer policies will remain

             free of fees.



      5.  Advantages and disadvantages of the proposal



      5.1 Advantages


           - Ensures that organisations are using scarce IPv4 address space

             resources to the fullest extent possible.


           - The utilisation of historical IPv4 addresses will be brought

             into line with current best practices for address management.


           - The remaining IPv4 free pool will be delegated to LIRs that have

             a genuine need for IP addresses.



      5.2 Disadvantages


           - Organisations can no longer hoard unused address space while at

             the same time receive more scarce address space from APNIC's



           - LIRs with historical IPv4 addresses may find it time consuming

             to change network architecture that uses historical IPv4

             addresses in an inefficient manner.


             However, the difficulties felt by these networks is outweighed

             by the greater benefits of ensuring that the remaining IPv4

             address space is delegated to networks with a genuine need for

             IPv4 allocations.



      6.  Effect on APNIC members



      APNIC members who have applied best practices for address space management for all their address ranges will not be affected.


      APNIC members who have not applied best practices for all their address ranges may need to modify their management of historical addresses before they can qualify for IPv4 addresses from APNIC.


      There will be no impact on fees paid by members.



      7.  Effect on NIRs



      The proposal has no direct impact on NIRS, but impacts members of NIRs in the same way it impacts APNIC members.



      8.  References



      [1]  Historical resources definition





      Sig-policy-chair mailing list

      Sig-policy-chair at apnic dot net