Operational Contacts

>The following is my recollection of the Paris discussion about this:
>
>Andreas Schachtner had proposed to add an attribute to all non-person
>objects specifying the mailbox of the operational contact points.  
>This had been mailed around on ripe-op before the Paris meeting. 
>
>The proposal was discussed and a separate NOC object was proposed in
>order to prevent duplication of the same data all over the database
>and have a better mapping with reality.  This was considered a too
>heavyweight soloution for the time being. 
>

We should soon introduce this new NOC object. If for example a service provider
wants to give support to all his customer networks, all three attributes have
to be added to a lot of networks. And then the phone number changes ...
Don't waste time.

>Consensus was to add separate optional attributes to all objects except
>persons for e-mail, phone and fax of the operational contacts.  If this
>gets widely used then introduction of a NOC object and replacement of
>these attributes by a pointer to it can be considered at a later stage. 
>
>I propose the following naming:
>
>	ATTR    op      op-phone
>	ATTR    of      op-fax
>	ATTR    om      op-mail
>
>All optional and multiple. 
>
>Semantics:
>
>	Generic contact information for operational purposes like a
>	common mailbox for the NOC or operations group and/or a
>	NOC hotline etc.
>
>	Not intended for duplication of information that can be found
>	via the tc, ac, and zc persons!
>
>Comments?
>
>Daniel

Arnold