Chapter 3 of the current policy explains the main goals, with Chapter 3.5 focusing on conservation, meaning every allocation should be reasonable. However, Chapter 3.4 talks about aggregation and comes before conservation, which suggests that keeping address space together (aggregated) is more important. I think having address space in large, continuous blocks is more important. This is why the change from /29 to /28 was made, so LIRs have enough space from the start. It also reduces the need for LIRs to gather multiple separate /29 blocks and transfer them, which will help reduce the workload for the RIPE NCC. Your point seems to support always giving a /28 and removing the option to ask for a /32 (90% already goes for the /29 option in the current policy). Having just one default allocation would make things simpler and stop LIRs from needing to request more space later, making the process easier for everyone. Rinse On 21-10-2024 09:02, Michiel Klaver via address-policy-wg wrote:
-----Original message-----
Is there a shortage of IPv6 that nobody told me about?? Technically: no. Administratively: yes.
Every request has to be verified by humans, RIPE NCC only has a limited amount of manpower to handle all requests. Hoarders put a disproportionate load onto that process.
----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/address-policy-wg.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/