| Username: |
_Jeff |
| Date/Time: |
Mon, July 3, 2000 at 9:19 PM GMT |
| Browser: |
Netscape Communicator V4.5 using Windows 98 |
| Score: |
5 |
| Subject: |
Purposed domains: ftp, gopher, https |
Message: |
|
|
I purpose we have a top-level domain for each and every Internet protocol scheme.
We have .web -- it's not entered into the root servers, but we have it -- why can't
we have .ftp for FTP sites and .gopher for Gopher? Such top level domains would
allow the novice Internet user to easily determine which protocol is being used.
No longer would ".com" thought to indicate a web site is on the Internet -- we could
have ".web" instead. Think about it. Instead of having http://microsoft.com/
and ftp://microsoft.com/, Microsoft would have microsoft.web and microsoft.ftp.
Secure encrypted HTTP sessions to Microsoft would be microsoft.https. Mail
would be addressed to microsoft.smtp. Besides being shorter and containing
less frivolous symbols, my method would distribute DNS queries all requesting what's
the address of microsoft.com to multiple DNS servers. What does everyone have to
say about this idea? I welcome your comments. Thanks,
_Jeff
|
|
|