This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[address-policy-wg] 2023-04 New Policy Proposal (Add AGGREGATED-BY-LIR status for IPv4 PA assignments)
- Previous message (by thread): [address-policy-wg] 2023-04 New Policy Proposal (Add AGGREGATED-BY-LIR status for IPv4 PA assignments)
- Next message (by thread): [address-policy-wg] 2023-04 New Policy Proposal (Add AGGREGATED-BY-LIR status for IPv4 PA assignments)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at foobar.org
Wed Sep 27 22:57:36 CEST 2023
denis walker wrote on 24/09/2023 17:12: > So are you saying > that in 2023 we can't manage a distributed database without > overwhelming repetitive tasks? yes, correct. People are stuck using the tools that they have. Most off-the-shelf tools don't implement server-client or 2way database synchronisation between the local ipam system and the ripe db, and there's ~zero financial inventive to build this sort of functionality in-house. The outcome is that the ripedb ends up with manual updates, or else with low quality / 1-way synchronisation with little or no cleanup. The result of this is that the ASSIGNED-PA objects in the ripedb are generally of low average accuracy. Nick
- Previous message (by thread): [address-policy-wg] 2023-04 New Policy Proposal (Add AGGREGATED-BY-LIR status for IPv4 PA assignments)
- Next message (by thread): [address-policy-wg] 2023-04 New Policy Proposal (Add AGGREGATED-BY-LIR status for IPv4 PA assignments)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]