Live data from Hacker News

Internet Draft: Let 'localhost' be localhost

tools.ietf.org

31–40 of 179 posts

Re: Internet Draft: Let 'localhost' be localhost

#32
post #7

To be clear, this is not an RFC yet. It's not even adopted by a working group, although I hope it will be. Mods: can RFC be removed from the title? [Edit: thanks for updating the title!]

So, an RFRFC?

It's called an I-D, for "Internet Draft."

Very roughly, a Standards Track document in the IETF goes through four stages:

1. Someone submits an I-D as an individual. Literally anyone can do this and such a document carries no weight.

2. A working group (WG) "adopts" the I-D and proceeds to work on the document as a group. The document still carries no weight at this stage.

3. The I-D is published as an RFC. When this happens, the document finally has real weight. The document can no longer be changed, although it can be updated or obsoleted by another RFC.

4. When the RFC matures, it can be promoted to an Internet Standard.

Let localhost be localhost is still in the first stage.

Re: Internet Draft: Let 'localhost' be localhost

#33
post #2

If this doesn't happen or takes too long, there's always lacolhost.com and *.lacolhost.com. I own this domain, have registered it out until 2026 and vow that the domain and all subdomains will always redirect to localhost. It's easy to type and easy to remember and should always do a good job of expressing intent of usage.

[deleted]

Re: Internet Draft: Let 'localhost' be localhost

#34

The domain "localhost.", and any names falling within ".localhost.", are known as "localhost names". Localhost names are special in the following ways […] Is this not implemented on macOS or am I just misunderstanding? ~ ping test.localhost ping: cannot resolve test.localhost: Unknown host ~ ping localhost.test ping: cannot resolve localhost.test: Unknown host

It would be rather surprising if a brand new draft RFC from a google employee were already implemented in macOS...

Re: Internet Draft: Let 'localhost' be localhost

#35

The domain "localhost.", and any names falling within ".localhost.", are known as "localhost names". Localhost names are special in the following ways […] Is this not implemented on macOS or am I just misunderstanding? ~ ping test.localhost ping: cannot resolve test.localhost: Unknown host ~ ping localhost.test ping: cannot resolve localhost.test: Unknown host

As I understood it, that simply states that if any of those domains were implemented, they should loopback, as opposed to all domains containing "localhost" ARE implemented.

Re: Internet Draft: Let 'localhost' be localhost

#37

This sucks. I have registered and am actively using a 'localhost' domain name under one of the new generic TLDs for for emails and account signups for quite some time now.

This wouldn't affect that: it applies to the bare TLD localhost and its subdomains -- not localhost.

Re: Internet Draft: Let 'localhost' be localhost

#38
post #5

Earlier quoted context omitted.

I don't think (?) I've ever made this typo. How many hits do you get? (I feel like "ocalhost", "locahost", or "localhos" would be more common typos.)

localhost would be a good name for a bar in SF.

I keep trying to go to this hip new bar called localhost, but somehow directions just lead me to drinking at home.

Re: Internet Draft: Let 'localhost' be localhost

#40
post #2

If this doesn't happen or takes too long, there's always lacolhost.com and *.lacolhost.com. I own this domain, have registered it out until 2026 and vow that the domain and all subdomains will always redirect to localhost. It's easy to type and easy to remember and should always do a good job of expressing intent of usage.

The problem with things like this is that they won't resolve without an internet connection.
Post reply on HN