At 12:26 PM 10/22/2003, Owen DeLong wrote:
The "RIGHT" way, absent a clear and compelling need to do it is DON'T.
I will now clarify...
In order to make such a change, the following criteria should be required prior to consideration:
1. There must be a clear and compelling reason for the change. Verisign's financial gain isn't a clear and compelling reason for the entire internet. Providing better directory assistance an innovative features might be, but...
Yes, but one point to consider on this: What happens to the wildcard in the event that the Registry is given to another party to manage when/if the current Verisign contract is terminated? Will the wildcard be left in place pointing to sitefinder? Will the new registry create another version of sitefinder? Will the users who have become used to seeing sitefinder now have to revert to seeing "Host Not Found" messages again?
2. There must be no alternative method for implementing the "clear and compelling" capability or service which could be implemented without such radical or abrupt change.
As was asked during the meeting, if the intent is to serve misdirected HTTP clients, why not simply create a browswer plug-in? This would perpetuate beyond a registry transfer, and work in all TLDs, not just the ones that Verisign happens to operate the registry for. -Chris -- \\\|||/// \ StarNet Inc. \ Chris Parker \ ~ ~ / \ WX *is* Wireless! \ Director, Engineering | @ @ | \ http://www.starnetwx.net \ (847) 963-0116 oOo---(_)---oOo--\------------------------------------------------------ \ Wholesale Internet Services - http://www.megapop.net