On Thu, 31 Oct 2024 at 17:04, Gert Doering <gert@space.net> wrote: [...]
Where are these rules?
The policy proposal that introduced AGGREGATED-BY-LIR was very clear on the circumstances where it can be used. I'm fairly sure you know whether these have made it to policy text, so asking me to go chasing the details would be wasting my time.
It's worth including the policy text in this discussion: "6.2 Network Infrastructure and End User Networks When an LIR holding an IPv4 address allocation makes IPv4 address assignments, it must register these assignments in the RIPE Database. These registrations can either be made as individual assignments or by inserting an object with a status value of 'AGGREGATED-BY-LIR'. In case of an audit, the LIR must be able to present statistics showing the number of individual assignments made in all objects with a status of 'AGGREGATED-BY-LIR'." https://www.ripe.net/publications/docs/ripe-826/
But you missed the two major points in my e-mail: please accept that you have been considered to be in the rough on 2023-04 and stop complaining. If you want to actually *change* the situation (like, having more detailed documentation, rules, requirements), your approach is not the way to achieve anyhting.
Yes. Policy is mutable. If 'AGGREGATED-BY-LIR' does not work then the community can get rid of it. But we have less than a year of experience with it so far. We can ask the RIPE NCC to report on its use. Kind regards, Leo Vegoda, for the co-chairs