Re: TLD suggestions

[Jeff Williams <jwkckid1@ix.netcom.com>]

Warren,

  Please read belowy your comments.

Warren F. Seltzer wrote:
> 
> TLDs for COMPANIES:
> Trade names make excellent SLDs, but "com" cannot contain them all.  For
> global access to commercial organizations, I suggest the TLDs "inc",
> "corp", and "ltd".  The companies would probably like to include their full
> name into their internet address.  The (English) words Inc, Corp, and Ltd
> have the semantically identical function to the TLD "com".   Com itself has
> become sort of a substitute for Inc, Corp, and Ltd.   Customers and
> suppliers already know of and like "McDonalds Corp", "IBM Corp", et cetera.

  The idea of ysing .INC, .WORK or .WRK(Work), and .CORP for TLD's is 
a real good one.  I don't know the you can extend it too far.  But these
are real goo suggestions.
> 
> TLDs for PEOPLE:
> Often one wants to reach a particular person at home or at work, where ever
> that happens to be now.  It could be useful for those individuals who wish,
> to obtain lifetime addresses, to be later mapped to specific sites as
> needed.   These email addresses explain it all:   "John-Smith.1234@home"
> and "John-Smith.1234@work".    The registrars will need to allocate and
> resolve the numerous collisions of names, of course, in as user-friendly
> (memorable) a way as possible.  This is not the only solution to the
> problem, but could be much more efficient than using search engines every
> time, and could make use of search engines more efficient as well.  I think
> people would like to put their permanent Internet (email) name on a
> business card, High School yearbook, Birthday cards, Wedding announcements,
>  Birth announcements, and so on.

  Same here, for .Home and maybe someting like .SCH(School) or .SCHL
possibly.  
> 
> There are a number of additional scenarios, (some of which follow) but the
> point is that 2 special TLDs seem to be needed to let any of this happen,
> as the whole idea is to transcend ephemeral employers and home addresses.

  Yes, I agree. This would be a real good idea.  It has simplicity of
and yet flexibility for the perposes of sharing.  These TLD's could
be shared.  Not all though.  
> 
> Perhaps the authority issuing the birth certificate would want to issue the
> full, unique, email address.  After all, it's nearly the same thing as a
> birth certificate serial number, but more useful.   One could phone up or
> send email to "Jill-Q-Smith.CA1234@home".   John and Jill will want the
> right to be able to block all such generic contact, of course.

  I think this get's into long of a name.
> 
> The phone system is working on a similar dialing scheme for calling people
> wherever they are.   The advent of Internet voice systems makes this
> especially relevant.    For generic, life-long voice contact, I don't know
> whether a special protocol might be best -  voice://Jill-Q-Smith@home.
> Or a special TLD - mailto://Jill-Q-Smith@voice.    The former calls her
> house, the latter her internet phone, no matter where she is logged in, or
> even if she isn't.   A  way to block unwanted communication and retain
> privacy will be necessary.

  This could easly be built into a protocol.  For instance we have
something similar to what you are suggesting here.  Integrating 
voice, E-Mail, fax and celluar.  IBM has part of what you are suggesting
now as well, but not as fully developed.  In addition you would also
need a method of securing all communications, which would suggest to
me a special SLD for that perpose.
> 
> A Bit Off Topic:
> Certain TLDs should have the following standardized features:
> 
> Industry will be well-served if there are standardized addresses for
> commercial web pages and email addresses, such as
>    Complaints, PayBill, Promotions, Catalog-Sales, President, PurchaseOrders:
>         mailto://complaints@ibm.com
>         mailto://complaints@LloydsOfLondon.Ltd
>         mailto://President@Odwalla.Inc
> 
> Standard site names for forms are likewise useful,   For example, standard
> forms would be at:
>         http://Complaints.ibm.com
>         http://PayBill.ATT.com
>         http://PayBill.SearsRoebuck.Corp
> 
> The public should be able to guess the right spot from the company name.

  I am all for this.  Easy to remember naming standards should be 
greatly encouraged.  I have been preaching this for years.
> 
>         Warren Seltzer
>         warrens@warrens.seanet.com

Regards,

-- 
Jeffrey A. Williams
DIR. Internet Network Eng/SR. Java Development Eng.
Information Eng. Group. 
Phone :972-447-1878
E-Mail jwkckid1@ix.netcom.com