Could this situation be improved/eliminated when we move from TCP/IP to NDN (Named Data Network)?
In NDN, you don't request data from a specific host, hence no need to specify the receiving machine's IP, indeed, you send the packet to a p2p network, another with certain data / signature can answer your request.
So what does a URL look like in this system? E.g. If I have put up a poster on a wall somewhere, what do I say instead of "Visit www.example.org for more details"?
Instead of sending a HTTP GET on 'https://news.com/what-is-NDN.html', which must be answered from the server 'news.com' with https cert for prove.
You'll send an interest package '{title: what-is-NDN, type: news, cert: a-public-key}', which can be answer by any node having the data. Be the data source or someone that already got it (like BT download-and-seed sharing)
(The cert is optional, if you can trust an information from anyone)
In NDN, you don't request data from a specific host, hence no need to specify the receiving machine's IP, indeed, you send the packet to a p2p network, another with certain data / signature can answer your request.