[db-wg] ORG record vetting ?

Prior to an ASN or PI space being assigned by the NCC, the NCC goes through
and checks the organization info.
The only time an ORG ID can have resources registered to it without being
vetted is in the case of PA IP space being sub allocated or assigned by a
LIR, where the LIR is responsible for ensuring accurate information is
provided.

Jacob Slater

On Sun, Jul 28, 2019 at 4:28 PM Ronald F. Guilmette via db-wg <
db-wg at ripe.net> wrote:

> In message <20190728211022.GK60824 at Space.Net>,
> Gert Doering <gert at space.net> wrote:
>
> >On Sat, Jul 27, 2019 at 10:53:28PM -0700, Ronald F. Guilmette via db-wg
> wro=te:
> >> Just a point of curiosity...
> >>
> >> For each newly created ORG record that is put into the data base, if
> >> the ORG record represents something other than a natural person, does
> >> NCC staff make any effort to check to make sure that the alleged
> >> non-person entity actually exists, I mean, you know, as a legal entity,
> >> somewhere on planet earth?
> >>...
> >
> >I think this depends on the context that you want to *use* said org
> >object.  If you put it in as a standalone and unreferenced database
> >object, I think no vetting takes place.
> >
> >If you want to tie resources to it that are maintained by the NCC
> >(allocations [PA] or end user assignments [PI]) this needs to go through
> >a NCC ticket, and they want to see paperwork.
>
> 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?
>
>
> Regards,
> rfg
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/db-wg/attachments/20190728/4755d7a7/attachment.html>