[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 Karrenberg
dfk at ripe.net
Wed Feb 6 14:35:22 CET 2019
On 06/02/2019 11:23, Martin Huněk wrote: >> ... >> c) It is not tenable for the RIPE NCC to require the first LIR on the >> waiting list to wait for more address space than a minimal usfeful block >> to accumulate. > > 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. That is exactly what I wrote. > 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). That is where the implementation would become very complicated since it needs to be perceived as 'fair'. I see no good reason for this complication. > ... Keep /22 possibility so the > complete runout of IPv4 won't be postponed. See above. I do not see the point about 'complete runout'. We *have* run out already. This is about the very very tail end. Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: <https://lists.ripe.net/ripe/mail/archives/address-policy-wg/attachments/20190206/fb083f80/attachment.sig>
- 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 ]