Hi Robert,

We have reviewed what would be involved in providing this ability, in a
nutshell, we'd have to queue the change request and cron it after the
transfer went through. So far we only have the ability to queue new
registrations but not changes/modification for gTLD's. We are looking on
possibly building that ability but implementation is not yet scheduled. We
will advise further as news develops.

Regarding the info bug. This is one that I personally feel should be
addressed sooner than later by the registry but we have yet to receive any
guidance from them as to when it would be fixed. We ran a query to see how
many domains were in that state between now and early next year and the
number is extremely low. So based on this fact committing dev resources
seemed unwarranted.

When things of this nature surface we always assess the impact to resellers.
We then weigh that impact vs. level of effort to ascertain whether
committing dev resources (ie. Hard Dollars) is required.

Make sense?

Cheers,

James

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Robert L Mathews
Sent: Tuesday, November 25, 2003 1:23 PM
To: [EMAIL PROTECTED]
Subject: Re: OpenSRS Live Reseller Updates[domains]-25/11/2003

>From the latest LRU:

>2.  .org Contact Information Changes Cannot Be Made During a Transfer
>---------------
>It is the policy of all Registries operating on the EPP system to not 
>allow contact information changes during the transfer process.  Since 
>the .org Registry is migrating to the EPP system, .org registrations 
>will now operate in a similar manner to .info, .biz and .us.  The 
>contact information provided on the transfer order will not be applied 
>to the domain information once the transfer completes.
>Domain contact information changes must be made either prior to 
>initiating the transfer request using the current Registrar's tools and 
>procedures, or after the transfer completes using Tucows'
>management interfaces.

Wouldn't this be something that's easy for Tucows to do? When you get
notification that the transfer completes, just push the contact info. 
That way, all TLDs would appear to work the same way.

I'm relying on Tucows to handle registry inconsistencies as much as
possible; if it is possible, I would hope that you guys would try to hide
this kind of thing.


>3.  .info Expired Registrations Cannot Be Taken Off Lock Status
>---------------
>Due to a bug in the registry operator's system, locked .INFO domains 
>that have expired cannot be taken off 'lock' status once they are 
>renewed.  This means the renewed domain cannot be managed.  .INFO 
>domains that are 'locked' AND set to 'auto-renew' WILL NOT renew as 
>expected and due to 'auto-renew' being set, will not receive renewal 
>notifications.  If a .info domain is not renewed within the specified 
>time, the only recourse will be to use the redemption program that the 
>registry began in September 2003.
>https://rrc.tucows.com/releasenotes/info/redemption
>
>In order to prevent this, resellers' should remove the 'lock' status on 
>all .info domains that are due to expire.

See above. This sounds like something Tucows should be doing; a cron job to
remove locks from expiring .info domains sounds like just the thing. 
Why should thousands of resellers have to each work around a registry bug,
when one of your programmers could do it fairly quickly?

This is especially true since this is a horrific bug with awful
consequences. It means that domains become either unusable or unrenewable;
these are more than an inconvenience.

Actually, I can't believe Afilias is suggesting that they'd charge the
redemption fee to someone who would otherwise potentially lose their domain
name due to their bug. There is no way in hell I would pay such a fee; the
very idea is insulting. Afilias should be paying people who experience this
problem, not charging them. Tucows needs to explain to them that this is not
an appropriate policy.

I already stopped selling .tv, .cc and .ca domains due to registry
stupidity. Maybe .info should be next.

-- 
Robert L Mathews, Tiger Technologies      http://www.tigertech.net/

"I am not able rightly to apprehend the kind of confusion of  ideas that
could provoke such a question."  -- Charles Babbage


Reply via email to