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/db-wg@ripe.net/
[db-wg] ORG record vetting ?
- Previous message (by thread): [db-wg] ORG record vetting ?
- Next message (by thread): [db-wg] ORG record vetting ?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at foobar.org
Mon Jul 29 17:28:47 CEST 2019
Randy Bush via db-wg wrote on 29/07/2019 14:40: > i am not speaking for or against, as i do not understand what the threat > model is. the idea is that some org objects are created by users and inserted into the ripe database while others are subject to due diligence by the ripe ncc. I.e. there's a qualitative difference in data quality between the two, but there is no way of distinguishing between them. There are ways of flagging whether this process was carried out. One option would be to use a binary flag. Another would be to implement a datestamp for the last due diligence process carried out if it's not been set by the NCC. Lack of data could be flagged by either the absence of the parameter or else use 0000-00-00T00:00:00Z. Nick
- Previous message (by thread): [db-wg] ORG record vetting ?
- Next message (by thread): [db-wg] ORG record vetting ?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]