> This is an issue for network people and developers. So, the problems mentioned in the post essentially were... * ambiguity specifying ports * softw

> This is an issue for network people and developers. So, the problems mentioned in the post essentially were... * ambiguity specifying ports * software not recognizing addresses * length to type (3-32+7 characters) Looking past DNS, the first is only really an issue in web browsers, which I would doubt most people will actually use. The second is arguably a software issue, not a format issue. The third genuinely seems marginally debatable. Still, it seems like the amount of code needed to translate from one format to another would be trivial. In the amount of time it took to write the post, someone could probably have just written the code instead. There are tons of plugin mechanisms for stuff (shell, editor, browser, etc...).. > Given that machines, networks, routes, etc. are all becoming increasingly ephemeral MPTCP addresses some of these issues.