From my own experience with RIPE NCC: If you have an org with 2 or more LIRs and do have an /29 on the first LIR that is not used (not announce in the BGP table): When requesting an IPv6 /29 for the second or LIR, RIPE NCC will ask you if you really need this /29 as you have not announced the previous one. On 22-10-2024 17:57, Jan Zorz - Go6 wrote:
On 21. 10. 24 18:06, Gert Doering wrote:
Aren't we just slaves of our past based in IPv4 world, which in the fact created us?
It's just a philosophical question. "Wouldn't it be nice!" is not a good argument for stockpiling 100+ /29s.
RIPE policies still operate based on need, even if that is applied much more loose on IPv6. Demonstrate need. Hey,
This was sorted out at previous RIPE meeting at the APWG session. Marco asked for guidance and the feedback from the community was clear.
According to the policy - every LIR has an initial allocation of /32 up to /29 without any need of additional documentation. Every additional allocation needs an explanation, and transfers of /29s now fall under that category, as that actually *is* an additional allocation.
Something like: "You already have one /29, can you explain why you require another one? Show me the usage of the initial one and what kind of monster of a network you are building that you require another /29".
Problem with hoarders solved (hopefully).
Cheers, Jan
----- 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/