[db-wg] ORG record vetting ?

While this is not ideal as it is only available via the web interface
(afaik) it is still somewhat possible to see what the RIPE NCC has looked
at as can be seen here https://i.imgur.com/BUEqB9J.png

I can not edit the RIPE NCC Managed values.

- Cynthia

On Mon, Jul 29, 2019 at 5:32 PM Randy Bush via db-wg <db-wg at ripe.net> wrote:

> > 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.
>
> aha!  ok.  i buy that.
>
> > 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.
>
> randy
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/db-wg/attachments/20190729/dc4dd53d/attachment.html>