The title is misleading - it makes it sound like this is a description of how anycast works. However, this appears to be a proposal for how anycast could be imp

The title is misleading - it makes it sound like this is a description of how anycast works. However, this appears to be a proposal for how anycast could be implemented. But, its not clear to me that it's actually implemented this way in practice. A big chunk of the proposal seems to involve maintaining state between distributed servers - which is hard to do at all and even harder to scale. There also seems to be some layering violations - if a transaction is going to be too large, this proposes using an HTTP redirect. I might have missed it, but, this is hard to do when working at the TCP layer. The redirect would have to be done to a non-anycast address. Which means that every server needs to know about all the other potential servers that are running.