Agreed completely...and 'reading the docs' better is not a good enough answer when you have neophyte (usually) users in the mix.
-----Original Message----- From: Kris Benson [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 29, 2002 1:21 PM To: Mark Jeftovic Cc: James Simmons; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: CIRA Mark Jeftovic wrote: > > I've been offline for a few days, so sorry if this thread is old. But > whenever I hear people crying the blues about CIRA and saying they > can't do anything right I always have to pipe up and say one thing > which usually hits home: > > Registrar transfers from beginning to end in under 10 minutes. > > Tell me that doesn't rock and that Verisign can even come close. That's great, Mark. But that's assuming that the registrant has the CIRA account & password that was sent with a very machine-readable look to it, causing it to be deleted by many. Now, you're going to argue that I can easily have it resent. Well, not necessarily. If the client has changed e-mail addresses without informing us/CIRA, then the change wasn't made. Now, we're in a Catch-22. No e-mail so we can't get the password and no password so we can't change the e-mail. What's left? Well, a fax to OpenSRS which hopefully causes something to happen in the next not-too-long period of time. How is Verisign better? They let me, as Technical contact, modify the domain. They let me change the admin contact. This means that when a client says "yes I'll transfer" I change the admin contact to *me* then I can approve it all from this end without having to worry about Verisign's stupid and misleading messages. This is also how CDN*Net did a better job of managing the .CA namespace -- as tech contact I could change the admin contact. Sometimes the "technical" contact is responsible for technical information such as street address and e-mail address for the contacts. Possible solutions to CIRA's issues: 1. allow tech contact to modify domains 2. alleviate the burden by using domain/password instead of account/password 3. alleviate the burden by allowing user-assignable account/username and user-assignable password. 4. give registrars the contractual ability to modify a domain based on *their* authentication (read: I make a change in manage.opensrs.net and it doesn't need to be approved at cira.ca) The junk we're facing right now WRT changing RANT type, but needing to have *that* authenticated at CIRA is pushing me to suggest a price increase on our .CA sales from CA$65/yr to significantly more, if only to discourage registrations and/or recover our losses. Can we expect to see a change in this realm in the nearer future? -kb -- Kris Benson ABC Communications +1 (250)612-5270 x204 +1 (888)235-1174 x204
