In this proposed design, only traffic selected by the ISP's security policy goes through the TaraSec gateway. Normal traffic stays on the existing path. Additional gateway processing and latency therefore apply primarily to redirected connections.
Capacity depends on affected connection numbers, traffic volumes, the routing design, restrictions and how long customers remain on the security path. Prompt notification and practical help may shorten that time. Once cleared, customers can return to their normal path—an incentive to resolve the problem.
Measure throughput, connection capacity and latency in a pilot, including peak and failure conditions. The selection mechanism on existing infrastructure also needs capacity testing. TaraSec is experimental; this architecture is a deployment proposal, not a claim of ISP-scale performance.