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/address-policy-wg@ripe.net/
[address-policy-wg] Transfer Requirements for IPv4 Allocations
- Previous message (by thread): [address-policy-wg] Transfer Requirements for IPv4 Allocations
- Next message (by thread): [address-policy-wg] Transfer Requirements for IPv4 Allocations
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mikael Abrahamsson
swmike at swm.pp.se
Thu Apr 23 14:50:46 CEST 2015
On Thu, 23 Apr 2015, Vladimir Andreev wrote: >> On application for IPv4 resources LIRs will receive IPv4 addresses according to the following: >> >> The size of the allocation made will be exactly one /22. >> >> The sum of all allocations made to a single LIR by the RIPE NCC after the 14th of September 2012 is limited to a maximum of 1024 IPv4 addresses (a single /22 or the equivalent thereof). >> >> The LIR must confirm it will make assignment(s) from the allocation. > > Please point me where in quoted text you see any prohibition to open and merge LIRs with /22's? We can't do that, so what we're trying to do is make it less profitable to do so. But the INTENTION behind the current policy was to allow a new ISP (or other type of entity) a /22 to allow them to participate in IPv4 world 5-10 years down the line. It was NOT to allow people to use administrative tricks to cheaply acquire IPv4 space for use in a single business.
- Previous message (by thread): [address-policy-wg] Transfer Requirements for IPv4 Allocations
- Next message (by thread): [address-policy-wg] Transfer Requirements for IPv4 Allocations
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]