HI Job

I am not aware of any document explaining the reasons for this limitation. There is no technical reason why it could not be extended, although the way it is currently implemented would need to be modified.

But think about it from a higher level. If this functionality was to be allowed to all address space documented in the RIPE Database, what would that mean? You are asking the RIPE NCC to give permissions to Party A to override perfectly valid authorisation on objects maintained by Party B. The RIPE NCC may have no contractual relationship with either party, no knowledge of any business relationship between these two parties, no knowledge of any historical deals that may have taken place in the past and has no certain knowledge of who is the authoritative holder of all or any part of this address space.

I don't think you can resolve this issue right now with a technical solution at the database level.

cheers
denis
independent netizen