Provide clarity on how a TCPRoute affects HTTP traffic that uses TCP as the transport protocol

[shashankram]

TCPRoute is new traffic spec resource as described in https://github.com/servicemeshinterface/smi-spec/blob/master/apis/traffic-specs/traffic-specs-WD.md#tcproute.

Per https://github.com/servicemeshinterface/smi-spec/blob/master/apis/traffic-access/traffic-access-WD.md, it is possible to associate a TrafficTarget policy with both HTTP and TCP routes. In this case, should the HTTP traffic be subjected to the TCP routes specified in the TrafficTarget, considering the HTTP traffic is likely using TCP as the transport? For ex, if an HTTP service is running on port 80, should the TrafficTarget that has HTTP routes to this service also have a TCPRoute for port 80? What is the expected behavior with and without this additional TCPRoute on a TrafficTarget that has an HTTPRouteGroup defined?