denis walker via db-wg wrote on 13/09/2022 14:16:
I was struggling to know exactly what is meant by the phrase "using the RIPE Database as an IPAM solution".
the dbtf interpreted this as something along the lines of: "using the RIPE Database as the canonical reference for the holder's internal address assignments". The difficulty here is that the ripe db wasn't really designed to be granular enough, or private, or extensible enough, to suit the requirements of LIRs and other DB consumers for generic IPAM functionality. Separate to this, because it's a public database, there is no way of not exposing potentially confidential data. On the other hand, IPAM software suites are built for these purposes. Ultimately, people need to use tools that are fit for purpose. You can knock in a nail with a pliers, but that doesn't make it the best tool for hammering. Nor does it make it pliers any less useful as a type of tool. We're in the same territory here with the RIPE DB and purpose-built IPAM systems. Nick