Scott Allan wrote: > > This is a sore spot for us because we had hoped to have this out by now. > Suffice it to say we have gotten other things done... this is on the map > for specification in September. This means we will get it to dev late in > the month, and it could take anywhere from 4-8 weeks to develop, test, and > extend this functionality. We will be seeking reseller input in designing > this functionality - stay tuned to discuss list for a draft spec. If possible, it would be good for there to be two possible locks on a domain, both of which lock it in the registry: one available to the registrant, one available to the reseller. This means that if the customer is being belligerant and hasn't paid bills, the domain can be 'locked' to prevent them from taking off with their services. > Note that worrying about you names being stolen is like worrying about > getting hit by a car when you cross the street, it rarely happens. If and > when it happens, the most damage (which we recognize as bad) is a small > period where service for this name do not work. The name is always restored That seems like a very appropriate analogy. > to it's rightful owner (in our experiences with this), especially if it is > an operational name with services attached to it. Our enhanced transfer > notification now alerts registrants when a name is requested to be moved to > another registrar, so, if your contact info is good, you can really > mitigate your risks. We are still going to extend "locking" functionality > as we do see it as having value, and revenue potential. Do you mean OpenSRS will be charging for domain-lock actions, or that resellers can charge for them without an added cost? -kb -- Kris Benson ABC Communications +1 (250)612-5270 x14 +1 (888)235-1174 x14
