[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 ]
Carlos Friaças
cfriacas at fccn.pt
Mon Jul 29 13:02:45 CEST 2019
Hi (please see inline) On Mon, 29 Jul 2019, Nick Hilliard via db-wg wrote: > Jacob Slater via db-wg wrote on 29/07/2019 06:25: (...) >> Do you have a suggestion for how the process could be improved? Perhaps excluding jurisdictions *outside* the RIPE NCC service region, where company related data *can't* be verified by the RIPE NCC. > Would it be feasible for the RIPE NCC to add a read-only record to org: > objects which provided the date of the last due diligence check? E.g. > something like > > organisation: ORG-FNL99-RIPE > org-name: Foo Networks Limited > org-type: LIR > [...] > mnt-ref: RIPE-NCC-HM-MNT > mnt-by: RIPE-NCC-HM-MNT > abuse-c: FOO2000-RIPE > created: 2019-01-01T01:01:01Z > last-modified: 2019-01-01T01:01:01Z > due-diligence: 2019-07-01T12:00:00Z > source: RIPE > > Otherwise it doesn't look like it's easy to heuristically work out whether > due diligence has been carried out on a particular object or not. If this is feasible, it really sounds like a good idea to me! Cheers, Carlos > 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 ]