it is type 'OTHER' it was not created by the RIPE NCC and will not have been subjected to any due diligence checks by the RIPE NCC.

'OTHER' objects which receive direct assignments from the NCC (PI IP space or ASNs) are still subjected to due diligence checks (though only at the time of assignment).

I'd still argue the flag exists - search for 'ASSIGNED PI' (on IP space) or 'ASSIGNED (on ASNs) with the associated ORG object to see if any exist. Not exactly (currently) straight forward but it is still definitely doable.

Jacob Slater

On Wed, Jul 31, 2019 at 6:31 PM ripedenis--- via db-wg <db-wg@ripe.net> wrote:

HI Nick

The ORGANISATION object has an "org-type:" attribute. Most ORGANISATION objects have a value of either 'LIR' or 'OTHER'. If it is 'LIR' that ORGANISATION object was created by the RIPE NCC for a resource holder and has been through the due diligence process. If it is type 'OTHER' it was not created by the RIPE NCC and will not have been subjected to any due diligence checks by the RIPE NCC. So I think the 'binary flag' you suggested already exists.

cheers
denis

co-chair DB-WG

On Monday, 29 July 2019, 19:40:47 CEST, Nick Hilliard via db-wg <db-wg@ripe.net> wrote:

>> 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