There’s a viewpoint issue with these measurements. ATS will record when the
last byte was written to the inbound socket. This will always appear longer
from the client point of view because those bytes will take time to move from
the kernel socket buffers to the client and this depends strongly
> 3. Allow `$N` (capturing) support in the tunnel_route field as is
Does this mean we keep allowing "*.example.com" to be used for "
for.bar.example.com" ? And multiple wildcards as well? Just for
tunnel_route use case? If it's going to be an incompatible change anyway, I
think we should provide a
