Proposal: make phone number optional in person objects
All, Piotr's set of proposed improvements to the RIPE database has inspired me! Proposal: Make the phone number optional in person objects. Motivation: For ages the "phone" attribute has been mandatory in person objects (since 1995 with document RIPE 49 at least). But I don't see any reason that this should be mandatory. Many people prefer to be contacted via e-mail or some other method. Oddly, "phone" is optional on role objects, which would seem to be the ideal place for help desks and the like. (I am NOT proposing that we change this.) Cheers, -- Shane
On Fri, Apr 17, 2015 at 12:41:52PM +0000, Shane Kerr wrote:
For ages the "phone" attribute has been mandatory in person objects (since 1995 with document RIPE 49 at least).
so, why have _any_ mandatory attributes in the first place? -Peter
Peter, On Fri, 17 Apr 2015 15:07:45 +0200 Peter Koch <pk@DENIC.DE> wrote:
On Fri, Apr 17, 2015 at 12:41:52PM +0000, Shane Kerr wrote:
For ages the "phone" attribute has been mandatory in person objects (since 1995 with document RIPE 49 at least).
so, why have _any_ mandatory attributes in the first place?
Good question! We have the following template: person: [mandatory] [single] [lookup key] address: [mandatory] [multiple] [ ] phone: [mandatory] [multiple] [ ] fax-no: [optional] [multiple] [ ] e-mail: [optional] [multiple] [lookup key] org: [optional] [multiple] [inverse key] nic-hdl: [mandatory] [single] [primary/lookup key] remarks: [optional] [multiple] [ ] notify: [optional] [multiple] [inverse key] abuse-mailbox: [optional] [multiple] [inverse key] mnt-by: [mandatory] [multiple] [inverse key] changed: [mandatory] [multiple] [ ] source: [mandatory] [single] [ ] "person" is the name of the person, so I'd say that needs to exist. "address" probably should be optional. "phone" probably should be optional. "nic-hdl" is the key, so that needs to exist. "mnt-by" is used to protect the object, so that needs to exist. "changed" probably should be optional. "source" is required to distinguish between RPSL sources, so that needs to exist. I'm happy to include "address" and "changed" in the list of optional attributes! Cheers, -- Shane
On Fri, Apr 17, 2015 at 01:43:20PM +0000, Shane Kerr wrote:
"person" is the name of the person, so I'd say that needs to exist. "address" probably should be optional. "phone" probably should be optional. "nic-hdl" is the key, so that needs to exist. "mnt-by" is used to protect the object, so that needs to exist. "changed" probably should be optional. "source" is required to distinguish between RPSL sources, so that needs to exist.
agree with all of this.
I'm happy to include "address" and "changed" in the list of optional attributes!
So, that would mean the business logic should mandate at least one out of those attributes to be present - or we should extend the proposal to make the whole person object optional (what's the point in having a person object just with a name? Well, could hide the IM crediential in remarks ...) -Peter
On 17 Apr 2015, at 14:41, Shane Kerr <shane@time-travellers.org> wrote:
For ages the "phone" attribute has been mandatory in person objects (since 1995 with document RIPE 49 at least).
Hello, Just for the record: https://tools.ietf.org/html/rfc2622#section-3.2 <https://tools.ietf.org/html/rfc2622#section-3.2> All the best, Kaveh.
participants (3)
-
Kaveh Ranjbar -
Peter Koch -
Shane Kerr