Having read Nick's detailed response on why he doesn't approve of this policy amendment I tend to agree with him and therefore confirm that *I don't approve of this amendment* Making the sweeping change of default allocations from /29 to /28 seems like the incorrect approach imo to fixing an issue for a clear and very obvious small minority. On that basis, it very much seems like the current policy as written is appropriate and there should be a approach taken to instead look to address the difficulties faced in getting larger blocks for those that need it! My two cents anyway! - Mick -- Mick O’Donovan Senior Network Engineer HEAnet CLG Ireland's National Education and Research Network 3rd Floor, North Dock 2 | 93/94 North Wall Quay | Dublin D01 V8Y6 | Ireland +353 1 6609040 | mick.odonovan@heanet.ie | www.heanet.ie Registered in Ireland, No. 275301 | CRA No. 20036270 On 04/11/2025 22:34, Nick Hilliard wrote:
CAUTION[External]: This email originated from outside of the organisation. Do not click on links or open the attachments unless you recognise the sender and know the content is safe.
Hi Rich,
Patterson, Richard (Senior IP Architect) wrote on 04/11/2025 20:38:
Nick, I don't think the 11 LIRs or 0.3% statistic is a valid indicator; It's 68 LIRs > /29. 11 refers to those which currently have /28. And I'm sure there are more than 68 networks in the RIPE service region with 500k customers.
Having had to fight tooth and nail with the NCC several times now to get larger IPv6 allocations, I assure you the pain is real; I support a proposal to make it easier to get a larger-than-29 allocation, so indirectly I support this proposal.
I would prefer a proposal to improve policy that streamlines the process and removes the required head-banging-against-brickwall that is currently required to justify a larger allocation, but wording is hard, changing a number from 29 to 28 is (or should be) much easier.
I agree with you that it's too difficult to get larger allocations, but changing the default to /28 is not the solution. All it does is patch a specific case which is not really applicable to most service providers. If there's a problem which causes it to be too difficult to get more than the default size of allocation, then let's fix the problem properly.
Nick
----- 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/