[db-wg] phone number required for person objects
- Previous message (by thread): [db-wg] phone number required for person objects
- Next message (by thread): [db-wg] 2022-01 Resource holders identity
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
denis walker
ripedenis at gmail.com
Wed May 25 18:22:23 CEST 2022
Hi On Wed, 25 May 2022 at 17:07, Gert Doering <gert at space.net> wrote: > > *That* said - if people do not want to be contacted about issues with > their network, then we should ask ourselves if putting these contacts > into the RIPE-DB is the correct thing to do - phone numbers or not - > to me this is the prime reason we store contact data there, to reach > responsible persons/teams when there is something with their network > that needs attention. > It may be that a network operator simply doesn't have the capability to operate a tech support desk 24/7. That doesn't mean they don't want to be contacted or that they don't want to know there is a problem. If you detect an issue at 8pm, they are not available to fix it this evening so no point listing a phone number. If you send them an email they can look into the issue tomorrow. So there is still value in listing their (email) contact details in the database. > > On this particular discussion: I agree that it makes no sense to have > the phone number optional on a role: (*this* is usually a NOC that has > a phone...) and mandatory on a person: - make it optional on both. For now yes I agree to make it optional in both. In the long term we need to get rid of the PERSON object then we won't have discrepancies cheers denis proposal author.
- Previous message (by thread): [db-wg] phone number required for person objects
- Next message (by thread): [db-wg] 2022-01 Resource holders identity
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]