Hi, 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. Also, this is fully irrelevant. If a LIR refuses to publish relevant information (even if they are obliged to do so by policy), having more or less technical mechanisms in the DB is not going to make any difference. *Also*, please do accept that you were in the rough at consensus building, and stop using every single opportunity you have to complain about 2023-04. Ship has sailed. You are not adding signal to any noise. If you want to contribute in a positive way, join ranks in the planned "have a very close look at Status: values and their use" project (as discussed in the APWG slot, Remco's presentation). thanks, 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