Details will be coming, however, we decided that the lock will be easy to add and remove for simplicity. The reseller will have the ability to lock/unlock, and if you run your own manage there will be a flag to enable the lock/unlock in the manage.cgi interface (this will not be offered in the public manage interface at https://manage.opensrs.net)
Charles Daminato TUCOWS Product Manager [EMAIL PROTECTED] On Sat, 2 Mar 2002, Dave Warren wrote: > > It will not show up in the whois; however, an API status is available to > > ALL resellers (to prevent erroneous RSP->RSP transfers of domains > > on lock). > > > > Note that the registry prevents nameserver changes while a domain is on > > lock; but removing the lock is real-time, so someone can "unlock, change, > > lock" if they require a nameserver change (and you've allowed them access > > to the lock/unlock) > > What is involved with locking and unlocking? Just a flag in manage, or will > it confirm via email? Would it be worthwhile to have an "even more secure" > option that would require email confirmation to unlock? > > > -- > The nice thing about standards, there is enough for everyone to have their own. > > >
