[ripe-db-requirements-tf] Requirements for the RIPE Database... or Databases?

> On 17 Oct 2019, at 14:07, Shane Kerr <shane at time-travellers.org> wrote:
> 
> Fellow TF members,
> 
> tl;dr Do we want to explicitly say that we are making requirements for separate databases? (Probably with separate requirements.)
> 
> More words follow...
> 
> I was thinking about starting off a discussion about stakeholders in the RIPE Database, and I quickly remembered that the RIPE Database is at least two and maybe more databases in one.
> 
> We have the number registry:
> 
> * IP address assignments (hierarchical)
> * ASN assignments (semi-hierarchical)
> 
> We have the routing registry:
> 
> * Routes
> * Routers
> * Other routing policy information in various objects & attributes
> 
> We have some DNS information, which is used to configure DNS delegation in DNS servers that the RIPE NCC maintains:
> 
> * Reverse DNS domains
> 
> We have abuse/security information:
> 
> * "Incident Response Team" (a.k.a. CERT)
> * Various attributes (abuse-c, remarks, ...)
> 
> We have the last remains of attempts at lighthearted fun:
> 
> * Poems
> 
> We have contact information used by everything (secondary data, cleaned up automatically if not referenced by something else):
> 
> * Organisations
> * Persons
> * Roles
> 
> We have the authentication/authorization that protects stuff (also secondary data, although I don't think cleaned up automatically):
> 
> * Maintainers
> * PGP & X.509 certificates
> 
> 
> Finally, I'd like to note that there is a highly-coupled database, which is the RIPE NCC member database. The RIPE NCC keeps all kinds of non-public information, some of which is pushed to the RIPE Database (like organization contact information), some of which the RIPE Database has specific access to (like SSO authentication), and some of which is never entered into the RIPE Database (like billing status).
> 
> So... do we want to explicitly say that we are making requirements for separate databases? 😄

I believe we should cover all databases that come under the RIPE Database umbrella today and as part of our role we should review their role and need. It would be good to hear what others think, should our work cover ALL databases within the RIPE database? Is there agreement here? 

Thanks,

Bijal 
> 
> Cheers,
> 
> --
> Shane
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/ripe-db-requirements-tf/attachments/20191105/13328558/attachment.html>