Use TCP service names (Score 1)

One for every "official" service being offered through TCP. http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers

Microsoft.ftp/
Microsoft.ssh/
Microsoft.http/

The last one will confuse you because you're used to identifying the http service with the www name.

NOTE: I would not replace the protocol requested nor the actual port used with this naming. So http://microsoft.ftp:22/ would still be valid. I'm simply suggesting that we pull the list of possible TLDs from the IANA.

Here are the benefits I see:
- prevent overhead to the naming authority from having to identify if you're a non-com, pr0n, within the region of .ly, etc
- still allow the Marketing department to publish a sole destination for all things Microsoft (at .http presumably)
- allow web browsers to assist users by assuming .http (the way they assume www and com currently)
- allow small entities the ability to provide all services while only needing 1 domain (see my note above; if http is your machine, you could still provide SSH over port 22)
- allow international entities to provide region specific resources using subdomians while maintaining the implied authority of the common domain. (Example: UK.Microsoft.http - a user knows its the *real* MS site because they've been trained by Marketing that "http" makes you valid; think .com in today's world)