Hi, On Thu, Oct 31, 2024 at 04:59:34PM +0100, denis walker wrote:
On Thu, 31 Oct 2024 at 15:23, Gert Doering <gert@space.net> wrote:
On Thu, Oct 31, 2024 at 01:24:45PM +0100, denis walker wrote:
An LIR with an allocation can now simply split that allocation in half and create two objects with status 'aggregated-by-lir'. The boundary between the two aggregations does not even need to match the boundaries of any more specific ranges. There are NO rules about using this status. Absolutely nothing else more specific to these aggregations needs to be documented in the RIPE Database, in any public domain or notified to the RIPE NCC. The LIR may make a sub-allocation of, say, a /24 below one of these aggregations. Or maybe below both of them, crossing the boundary.
Denis, you are talking nonsense. There are very clear rules what can be under AGGREGATED-BY-LIR (namely, ASSIGNED, with the same contact data). Not SUB-ALLOCATED.
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. 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. Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Ingo Lalla, Karin Schuler, Sebastian Cler Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279