[address-policy-wg] 2019-02 New Policy Proposal (Reducing IPv4 Allocations to a /24)
- Previous message (by thread): [address-policy-wg] 2019-02 New Policy Proposal (Reducing IPv4 Allocations to a /24)
- Next message (by thread): [address-policy-wg] 2019-02 New Policy Proposal (Reducing IPv4 Allocations to a /24)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Suchy
danny at danysek.cz
Mon Feb 4 16:19:50 CET 2019
Hello, On 2/4/19 2:14 PM, Francis Brosnan Blázquez wrote: > Sooner or later RIPE IPv4 address space will run out. Moving from /22 > to /24 will not change that, which is the essence of the question, but > doing so will create more fragmentation (BGP, smaller LIRS, cost > unfairness between members...). Fragmentation is here already and it's done even by resource holders having allocations shorter than /22... Some kind of unfairness is also here - some LIRs have only single /22, some LIRs have multiple /16. From this perspective it's nothing bad, when new LIRs will have only /24... As stated in original post "This proposal aims to reduce the IPv4 allocation size to a /24 once the RIPE NCC is unable to allocate contiguous /22 ranges." - that meas, when new allocations will cause fragmentation anyway. - Daniel
- Previous message (by thread): [address-policy-wg] 2019-02 New Policy Proposal (Reducing IPv4 Allocations to a /24)
- Next message (by thread): [address-policy-wg] 2019-02 New Policy Proposal (Reducing IPv4 Allocations to a /24)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]