TL / TL2 transport architecture
Trace the channel from local request to returned bytes.
TL2 implementation traced; TL identity retained separately
Purpose
The recovered TL2 implementation multiplexes channels over a TCP tunnel and encrypts data with AES-256-GCM. Its framing, payload encoding and control path are visible components that can be tested separately.
How it works
The TL2 binary frame supplies a 17-byte header with channel, sequence, length and CRC fields.
The encryption engine derives a session key with HKDF-SHA256 and authenticates channel, sequence and timestamp alongside encrypted data.
The current implementation carries encrypted bytes as hexadecimal text inside JSON. Any transfer-saving claim must count this encoding and the outer network traffic.
A practical workflow
Choose a bounded local test workload and a declared endpoint.
Record input bytes and the complete encoded traffic.
Check returned bytes and authentication failures.
Compare identical useful work against an explicit baseline before claiming reduced overhead.
Where it fits
Private application tunnels
Multiplexed service channels
Transport and protocol test workbenches