TCP Three-Way Handshake Infographic | visio network diagram examples download

Tech architecture infographic titled "TCP Three-Way Handshake" using archetype PROTOCOL HANDSHAKE. Show a precise numbered exchange between two endpoint boxes and the underlying network context, designed for architect / staff audience. Create a retro 1980s computing look with blueprint cyan palette, subtle grid paper background, CRT-terminal accents, neon-cyan linework, white annotation text, and restrained technical editorial mood. Use editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout.

Layout: left-to-right network handshake diagram with large labeled boxes connected by directional arrows. Primary boxes: 
1) "TCP Client" with workstation icon — "Initiates connection from ephemeral source port"
2) "TCP Server" with rack-server icon — "Listens on destination port and accepts sessions"
Support context boxes around the main flow to satisfy architecture-diagram composition:
3) "Client Application" with terminal-window icon — "Requests a reliable byte-stream connection"
4) "Server Application" with service-gear icon — "Consumes accepted socket after handshake completes"
5) "Network Path" with generic cloud icon — "IP network carrying TCP segments between endpoints"
6) "Client TCP Stack" with layered-protocol icon — "Builds segments, tracks sequence numbers and state"
7) "Server TCP Stack" with layered-protocol icon — "Validates flags, allocates state, replies with acknowledgments"

Connections and arrows must clearly show packet direction and protocol semantics:
- Arrow from Client Application to Client TCP Stack labeled "connect() request"
- Arrow from Client TCP Stack through Network Path to Server TCP Stack labeled "1. SYN, Seq=x, dst port=open service"
- Arrow from Server TCP Stack through Network Path to Client TCP Stack labeled "2. SYN-ACK, Seq=y, Ack=x+1"
- Arrow from Client TCP Stack through Network Path to Server TCP Stack labeled "3. ACK, Seq=x+1, Ack=y+1"
- Arrow from Server TCP Stack to Server Application labeled "accept() returns established socket"
- Optional thin data-phase arrow after handshake from TCP Client to TCP Server labeled "TCP payload bytes"

Add compact state annotations near the TCP stack boxes:
- Client states: "CLOSED → SYN-SENT → ESTABLISHED"
- Server states: "LISTEN → SYN-RECEIVED → ESTABLISHED"
- Small metric callouts: "Flags: SYN, ACK", "Reliable ordered stream", "No payload required in handshake"

Do not use browser, API, DB, cache, or queue semantics unless represented only as generic placeholder mini-icons in a faint side strip titled "Typical system components not used in this protocol example"; the main diagram must remain technically accurate to TCP handshake behavior.

Add a numbered legend 1-7 in English explaining lifecycle:
1. "Client application opens a TCP connection to a server port."
2. "Client TCP stack sends SYN with initial sequence number x."
3. "Network forwards the TCP segment over IP to the server."
4. "Server in LISTEN state receives SYN and reserves connection state."
5. "Server replies with SYN-ACK using sequence number y and acknowledgment x+1."
6. "Client validates SYN-ACK and sends final ACK with acknowledgment y+1."
7. "Both sides enter ESTABLISHED state and application data can flow."

Include small caution footer text in English: "Conceptual protocol diagram for explanation, not an audited reference architecture." Emphasize clean packet arrows, sequence-number callouts, port semantics, and handshake timing. No real cloud-vendor logos; if any network symbol is needed, use only a generic cloud icon. All text MUST be written in English (array). Every heading, label, caption, legend and metric name in the image must be in English — not English. Spell each English word correctly using English characters and diacritics. Numbers stay as digits, no real cloud-vendor logos (AWS / GCP / Azure) — use generic cloud icons, no watermarks No real cloud-vendor logos (AWS, GCP, Azure) beyond generic cloud icons. Common protocol names (HTTPS, TCP, JWT, OAuth, REST, GraphQL) stay in canonical English form. No security-claim overstatements (do not present diagrams as audited reference architectures).