Thankyou for your explanation. I see the same old problem with this process as with the usages reports when requesting more space. That problem is the NCC are trying to do too much and not handing enough responsability to us the LIR usrers/managers. Looking at it objectivly we the mangers of the LIR's should be the ones who know who is a VPC (valid point of contact) within the LIR so it seems pointless that the NCC have to manage the list of VPC for your LIR. What i see as the best solution is to create an automated system which we can manage so you have a valid list of our VPC's, instead of adding yet another ticketed system which you the NCC have to spend time and money (our money) on upkeeping. Besides which it would be much faster. Moving it to another mail ticketing is not removing the problem just giving a record of the problems but putting the responsability back in our hands removes the problem for you and improves the service all round.
Some time ago the RIPE NCC introduced a system through which LIRs could
the RIPE NCC of changes to their LIR contacts by updating their role object.
Adding the attribute [notify: hm-dbm-msgs@ripe.net] within their role object meant that whenever this role object was updated the RIPE NCC would get a RIPE database notification message and update the internal record for your Local Internet Registry contacts based on the tech-c or admin-c changes made within the role object.
This system was introduced because at that time the only way LIRs were able to inform the RIPE NCC of changes to their Local Internet Registry contacts was through the <hostmaster@ripe.net> mailbox.
Nowadays LIRs can notify the RIPE NCC of changes through the <lir-help@ripe.net> mailbox which is ticketised and thus all emails are archived.
Using the 'notify' system within a role object for LIR contact changes
to be very time consuming, impractical and above all not very reliable for several reasons:
- The same role object was sometimes updated 3 times a week: adding a contact one day, removing it the next day and adding it again 12 hours later. The intention of changing LIR contacts so frequently is questionable.
- Role objects were referring to other role objects with or without the notify attribute pointing to the RIPE NCC. Verification of the requested changes was difficult.
- Some LIRs did not realise that if they removed a contact from their role object, this contact would no longer be able to submit request forms to
RIPE NCC. Implications of changes to the role object were often not realised by the LIRs and produced misunderstandings.
Information about this purely operational change to the procedure of changing LIR contacts was only sent to those LIRs who had a notify attribute
to <hm-dbm-msgs@ripe.net> in their role object(s). Apologies for the lack of explanation in that message.
Using the <lir-help@ripe.net> mailbox proved to be a much more consistent, reliable and efficient way of changing confidential contact information.
Regards,
Sabrina Wilmot
--
o------------------------------------------o | Sabrina Wilmot sabrina@ripe.net | | Registration Services Operations Manager | | | | RIPE NCC tel +31 20 535 4444 | | www.ripe.net fax +31 20 535 4445 | o------------------------------------------o
"Stephen Burley" <stephenb@uk.uu.net> writes: * Hi * I am a little concerned with the email we recieved today (copied below * in part). This was sent to the community and enforced without any reason why * or justification or even a dicussion as the the change in working
* As the NCC work for the benefit of the RIPE community i would have
* this sort of change in working practice would have to be agreed with
inform proved the pointing practice. thought the
* community before the announcment went out. I may have missed the discussion * on the list and if so i am sorry but i still would think it manners to * explain why. I for one found this functionality very useful. * * Regards, * Stephen Burley * UUNET EMEA Hostmaster * SB855-ripe * * * [PLEASE FORWARD THIS TO YOUR LOCAL INTERNET REGISTRY CONTACT] * * Dear Colleague, * * This email is to inform you that the RIPE NCC no longer updates * its internal record for your Local Internet Registry contacts * based on the tech-c or admin-c changes you make within your role * object. Therefore we ask you to remove the line * 'notify: hm-dbm-msgs@ripe.net' from your role object: * * *