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]/
[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 19:40:25 CEST 2019
>> 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. > > less sure here. i can see wanting to differentiate between the two > classes of objects. not sure i care when they were last separated. > unless you expect things to change in time. if you have a better suggestion, go for it. My concern is mainly about having a deterministic way of figuring out which org objects have been subjected to due diligence and which haven't. 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 ]