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] 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 ]
Denis Fondras
ripe at liopen.fr
Wed Feb 6 12:32:41 CET 2019
On Wed, Feb 06, 2019 at 11:23:53AM +0100, Martin Huněk wrote: > Here it starts. I would say get such a LIR what you have got (to /22 of > course). Even by means of multiple /24s. But not blocks smaller than /24, as > it would be useless. Maybe let them decide if they would like to wait for > whole /22 where there would be less then 4x /24 (in that one case). > [...] > If you keep there /22 and /24 as an option, than there would be no problem. No please, don't let LIR choose. This will only complicate management of resources. In a FIFO, a LIR asking for /22 would delay a LIR who only needs 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 ]