TCP Three-Way Handshake Infographic | Cisco ESA Mail Flow Diagram

Tech architecture infographic titled "TCP Three-Way Handshake" using archetype PROTOCOL HANDSHAKE. Show a beginner-friendly network protocol diagram with labeled boxes connected by directional arrows: left box "TCP Client" with computer terminal icon and one-line role description "Initiates a TCP connection to a remote host"; center top small box "Network Path" with generic cloud icon and one-line role description "Transports TCP segments between endpoints"; right box "TCP Server" with rack server icon and one-line role description "Listens on a port and accepts incoming TCP connections". Add optional small side callout boxes for "Client TCP Stack" and "Server TCP Stack" with chip icons and one-line role descriptions "Tracks sequence numbers and connection state" and "Manages SYN-RECEIVED and ESTABLISHED states". Use 3 large numbered exchange arrows across the client and server through the network path: arrow 1 from client to server labeled "SYN, Seq=x"; arrow 2 from server to client labeled "SYN-ACK, Seq=y, Ack=x+1"; arrow 3 from client to server labeled "ACK, Ack=y+1". Add a subtle final state arrow or badge on both endpoints labeled "Connection established". Include tiny technical annotations near endpoints: "Client state: SYN-SENT -> ESTABLISHED" and "Server state: LISTEN -> SYN-RECEIVED -> ESTABLISHED". Add a small footer note box labeled "Purpose" with one-line description "Synchronizes sequence numbers before data transfer begins". Add another note box labeled "What happens next" with one-line description "Application data can now flow over the TCP session". Render all components as clean labeled boxes with icons, canonical English names, and concise English descriptions; all arrows must clearly show data direction and carry short English labels describing what crosses. Include a numbered legend 1-7 in English for the lifecycle: 1. "Client wants to open a TCP connection to the server port." 2. "Client sends a SYN segment with its initial sequence number." 3. "The network forwards the SYN toward the listening server." 4. "Server replies with SYN-ACK, acknowledging the client sequence and sending its own." 5. "The network returns the SYN-ACK to the client." 6. "Client sends the final ACK to confirm the server sequence number." 7. "Both sides enter ESTABLISHED state and data transfer may begin." Visual style: retro 1980s computing, blueprint cyan palette, dark navy background with cyan linework, grid-paper blueprint texture, glowing vector strokes, pixel-terminal accents, crisp geometric boxes, educational and approachable mood for curious beginners. Composition should feel like an editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Keep it technically accurate to TCP, avoid unrelated components such as browser, API, DB, cache, or queue unless shown only as faint crossed-out non-applicable examples outside the main flow. 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).