In-band OAM proxy/cache (for Comcast)

Overview:
Anycast is often used to have a client choose one out of multiple servers. This might be due to performance, scale, or availability reasons. If a client initiates a TCP connection in an anycast scenario, the TCP session is usually established with the server which answers the quickest.
There are cases where it is desirable to:
allow choosing the destination server not based on "fastest response time", but based on the delay between server and client (e.g. for a streaming application).
allow choosing the destination server based on other parameters, such as server load information.
ensure that all TCP connections of a particular client are hooked up to the same server, i.e. that all TCP sessions following the first one are connected to the same server as the first session.
M-anycast combines in-band OAM and segment routing to provide for a solution:
In-band OAM information is added to the initial TCP SYN packet to understand the transmit delay, as well as to the SYN-ACK packet to understand the return delay.
Segment routing is used to steer traffic to the set of servers, rather than rely on anycast procedures.
Client and Servers are left unchanged. SR and iOAM information is added and removed "in transit"