RE: Browser TLD Searching
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Browser TLD Searching



On Tuesday, February 03, 1998 5:40 PM, Leonid Yegoshin[SMTP:egoshin at genesyslab.com] wrote:
@>From: Jim Fleming <JimFleming at doorstep.unety.net>
@>
@>On Tuesday, February 03, 1998 2:20 PM, Leonid Yegoshin[SMTP:egoshin at genesyslab.com] wrote:
@><snip>
@>@
@>@   IETF can develope and adopt some technical shift in name search
@>@which can be more fitable with trademark principles. For exam, why
@>@the reason that any commercial seeking .COM ? - there is the very
@>@fast way to find company by typing its trademark in browser, but
@>@current browsers don't search something like "trade-mark.fr" domain.
@>@
@>
@>If you look in the registry of an MS-based system
@>you will see how easy it is to change or add to the
@>browser searching.
@>
@>[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\UrlTemplate]
@>"1"="www.%s.com"
@>"2"="www.%s.edu"
@>"3"="www.%s.org"
@>"4"="%s.com"
@>"5"="%s.edu"
@>"6"="%s.org"
@>"7"="www.%s.mall"
@
@   Jim, It should be configured on server side, not on search side.
@Your example looks like an advice to commercial producers relay on
@correct customer configuration in search of buyers ! Ask any CEO/sales
@person about it and propose him don't guard its trade-marks too strict...
@(And enjoy reaction :-)
@

Thanks for the marketing advice.

>From an "engineering" point of view, the above is
not a pretty site. The browsers now generate DNS
traffic that was not engineered into the system.

Also, back to marketing, what will people do
if Microsoft decides to ship the above product
with "1"="www.%s.msn" ???

Will companies have to re-register their .COM
domain in another TLD to make sure it is hit first
during the browser search ?


Jim Fleming
Unir Corporation
IBC, Tortola, BVI



Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.