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] proposal: new attribute 'geofeed:

Previous message (by thread): [db-wg] Fwd: proposal: new attribute 'geofeed:
Next message (by thread): [db-wg] Cleanup of trailing dot in "nserver:" attributes in domain objects in the RIPE database

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Edward Shryane eshryane at ripe.net
Mon Jan 11 15:46:30 CET 2021

Hi Michael,

> On 8 Jan 2021, at 15:16, Michael Kafka via db-wg <db-wg at ripe.net> wrote:
> 
> Dear members,
> 
...
> Much more critical are the 100k or maybe even millions of RIPE-db
> entries, containing name and street address of natural persons which
> are under the sole control of RIPE.
> 
> Best regards,
> 
> MiKa
> 

If you are referring to PERSON objects, then out of 2 million PERSON objects in the RIPE database, only 14,841 are maintained by the RIPE NCC.

13,277 of these are (previously unmaintained) locked person objects, which we are in the process of cleaning up.

The vast majority of PERSON objects are referenced from inet(6)num allocations and assignments (i.e. maintained by LIRs and End Users).

Regards
Ed Shryane
RIPE NCC

Previous message (by thread): [db-wg] Fwd: proposal: new attribute 'geofeed:
Next message (by thread): [db-wg] Cleanup of trailing dot in "nserver:" attributes in domain objects in the RIPE database

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]