Sander Steffann wrote at 2019-02-04 16:02:
Hello working group,
The first comments I got back on this proposal all seemed to miss the
point of it. Let me explicitly state what this policy is NOT about:
- it is NOT about conserving IPv4 addresses
- it is NOT about postponing the runout date
- it is NOT about extending the lifetime of IPv4
It's purpose is solely about:
- dealing with the returned address space the NCC will get over the
years
Under the current policy:
- the waiting list will grow indefinitely
- the allocations given out will consist of tiny fragments
- it will therefore not be of any practical use
This proposal proposes:
- keeping /22 until we run out of /22s
- give out /24s only after that
- this helps to keep the waiting list manageable [1]
- declare everything smaller (longer prefix) than a /24 unusable
- this helps against people getting unusable dust
[1]: see
https://ripe77.ripe.net/presentations/71-Andrea_Cima_RIPE_77_APWG.pdf
slide 14
Please forget about previous attempts to change allocation sizes.
Those were about changing the current allocation policy. This proposal
only looks forward to what to do after the current policy becomes
unusable. Please focus on that.
Cheers,
Sander
Just another point for discussion: what to do when this /24-only policy
is in effect and RIPE NCC happens to recover a large chunk (e.g. /16 or
more) and is able to hand-out multiple /22's again?
