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] 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 ]
Petr Umelov
petr at fast-telecom.net
Sat Apr 25 18:13:09 CEST 2015
Hi everybody. Let me tell some words about current proposal. Many providers (among them is our company) need to get (e.g.) /20 subnet (not 4 x /22). If we ask the RIPE NCC to allocate 4 x /22, we can get next variants: 1. /20 2. 2 x /21 from different subnets 3. /22, /21, /22 There is only one chance to get /20 100% - make request for 7 x /22 (if the tickets will be processed together). But in this case we will have unwanted 3 x /22 which we can transfer to other LIRs to minimize our expenses. And also we can get different separate 4 x /22 (the worst case) and we have to transfer such blocks and make new request. If this proposal will be agreed, many providers (new and old) will have material losses. So I can't support this proposal. -- Kind regards, Techincal Director FastTelecom Petr Umelov
- 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 ]