This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[address-policy-wg] Principles for the use of the last IPv4 /8 address space in the RIPE NCC Region
- Next message (by thread): [address-policy-wg] Principles for the use of the last IPv4 /8 address space in the RIPE NCC Region
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Kelaidi Christina
kelaidi at ote.gr
Mon May 4 08:27:29 CEST 2009
Dear colleagues ETNO has prepared an Expert Contribution on the Principles for the use of the last IPv4 /8 address space in the RIPE NCC region, based on a previous contribution with regard to IPv4 address exhaustion presented in the RIPE address-policy-wg mailing list in May 2008. According to ETNO any policy proposal relevant to the use of the last IPv4 /8 address space should satisfy the principles contained in this contribution in order to permit both a fair and equitable use of the last IPv4 /8 address space and a flexible approach with regard to its management. Introduction ETNO recognises that with the theoretical date of exhaustion of IPv4 public addresses fast approaching, principles ensuring fair and equitable use of the last /8 address space in the RIPE NCC region are required. This contribution presents a number of such principles in order to initiate such discussions that are intended to lead to a RIPE NCC policy. ETNO in a previous contribution with regard to IPv4 address exhaustion identified a number of principles associated with the management of IPv4 public addresses as exhaust approached. These principles form the basis of the principles below as applied to the last /8 address space. In the development of this Expert Contribution, regarding the use of the last IPv4/8, ETNO wants to guarantee that any policy developed is based upon the fair and equitable allocation of address space to all LIR's, irrespective of whether they are new or existing. Principles Demonstrated Need Allocation Allocation of IPv4 addresses from the last IPv4 /8 should be treated the same way for all Registries (LIR), and should be in response to their demonstrated need. Pre-determined Use Assignment from the last IPv4 /8 should only be used to facilitate the deployment of IPv6 Public address resource by the LIR. Size of Address Allocation The size of any allocation from the last IPv4 /8 should be based upon flexibility, recognising that it is an allocation from the last /8, and meeting the needs of the applicant. As a consequence the size of address allocated may require adaptation of the current and existing allocation rules. Predictability of Allocation Relevant policies associated with the allocation from the last IPv4 /8 should be announced well in advance in order to give sufficient time for operators and ISPs through their LIRs to be prepared. Conclusion ETNO supports the development of a RIPE policy detailing how the last IPv4 /8 will be deployed in order to ensure clarity for all stakeholders. ETNO believes that the above principles should be the basis of any RIPE policy related to the last IPv4 /8 and supported by the implementation of appropriate measures and actions. Christina Kelaidi ETNO Naming Addressing and Numbering Issues (NANI) WG Chairperson ETNO (European Telecommunications Network Operators' Association) is representing 40 major companies from 34 European countries, providing electronic communications networks over fixed, mobile or personal communications systems. ETNO's primary purpose is to establish a constructive dialogue between its member companies and actors involved in the development of the European Information Society to the benefit of users. More information on ETNO can be found at: www.etno.be.
- Next message (by thread): [address-policy-wg] Principles for the use of the last IPv4 /8 address space in the RIPE NCC Region
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]