[db-wg] ORG record vetting ?

Hi,

On Sun, Jul 28, 2019 at 04:27:04PM -0700, Ronald F. Guilmette via db-wg wrote:
> >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?

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

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: </ripe/mail/archives/db-wg/attachments/20190729/e1b08573/attachment.sig>