Iljitsch van Beijnum wrote:
2) The first hit is of critical importance to content providers (many of whom couldn't legitimately justify a /32). Hunting through DNS to find a locator that works won't fly.Right. So how do we solve this? Second shim? Shim-before-syn?
It is very hard *under* the current socket API, since the connect() and sendto() calls do not know that there is alternative addresses to try.
But if the application is using some middleware that has the equivalent of a connect_to_name(), then it isn't hard to implement that API on top of the socket API by using non-blocking connect() and trying different addresses relatively quickly (instead of waiting for a minute or so until TCP times out, it could try a second connect on a different socket after a few seconds).
Erik