On Tue, 25 Nov 2003, James M Woods wrote: > 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.
Then how about spending a day's salary to notify resellers of which domains might be affected instead of asking thousands of RSPs to go through their profiles, find their .info domains and turn off locking? Seems like you guys passed the buck here :-( and the resulting cost is going to be higher... both in reseller time spent, and possibly clients hurt because resellers ignored or misunderstood the warning. Never mind the "Note: The Lock Status result is not authoritative. To get authoritative result, individual domain must be queried." message on the search domains page... > 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? perfect sense... but please consider that resellers pay your salaries, and making them spend $$ internally maintaining their opensrs profiles isn't going to win any popularity contents. IMHO the name of the game is "help"... business is about building win-win relationships, you guys help us, and we help you.... -Tom
