[db-wg] ORG record vetting ?
Piotr Strzyzewski Piotr.Strzyzewski at polsl.pl
Mon Jul 29 08:43:52 CEST 2019
On Mon, Jul 29, 2019 at 07:39:05AM +0200, Gert Doering via db-wg wrote: > > In the context of your response, would one or more ASNs count as "resources" > > which would trigger manditory vetting of the associated ORG? > > > > Or is it only the association of some IP address block that causes NCC to > > vet the ORG? > > I'd assume that an AS would be handled the same as a PI block - you > (the LIR who acts as contact between end user and NCC) need to present > a contract with the end user, and company registration papers for said > end user. The org object would then need to match the paperwork (name, > address). > > At least this has always been my experience when we had to clean up > end user resources (company name changes, change of sponsoring LIR, > etc.) In the context of RIPE DB one should not forget about aut-num's with either OTHER or LEGACY status or with the RIPE-NONAUTH source. Only around 10% of the latter do have organisation object linked. Those ones were most likely never vetted. Piotr -- Piotr Strzyżewski Silesian University of Technology, Computer Centre Gliwice, Poland
[ db-wg Archives ]