TCP Three-Way Handshake Blueprint for Network Diagram Examples

Tech architecture infographic titled "TCP Three-Way Handshake" using the PROTOCOL HANDSHAKE archetype, adapted as a clear state-machine / lifecycle diagram for a non-technical executive audience. Show a blueprint schematic composition with minimal monochrome palette: deep navy blueprint background, white and light gray linework, subtle cyan highlights, restrained technical grid, calm professional mood. Editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout.

Layout: two main endpoint boxes facing each other horizontally, with a small network path/cloud in between. Left box: "Client" with a computer icon, subtitle: "Initiates TCP connection". Include a small sublabel inside the box: "Example IP: 192.168.1.10:51514". Right box: "Server" with a server rack icon, subtitle: "Listens for incoming TCP sessions". Include a small sublabel inside the box: "Example IP: 203.0.113.20:443". Middle connector: generic cloud/network icon labeled "IP Network" with subtitle: "Routes TCP segments between endpoints". Also include three small state boxes near the flow: "SYN-SENT" with subtitle "Client has sent SYN"; "SYN-RECEIVED" with subtitle "Server received SYN and replied"; "ESTABLISHED" with subtitle "Both sides can exchange data".

Use labeled boxes connected by directional arrows. Step 1 arrow from Client to Server through IP Network labeled: "TCP SYN, Seq=x, dst port 443". Step 2 arrow from Server back to Client through IP Network labeled: "TCP SYN-ACK, Seq=y, Ack=x+1". Step 3 arrow from Client to Server through IP Network labeled: "TCP ACK, Ack=y+1". After the third exchange, add a final subtle double-headed data arrow between Client and Server labeled: "TCP payload data".

Inside or near each endpoint, add tiny technical callouts in English for clarity: on Client: "Active open" and "Chooses initial sequence number"; on Server: "Passive open" and "Confirms receipt and allocates session state". Add small port notation labels near arrows: "Source port: ephemeral" on client side and "Destination port: 443" on server side. Keep all wording simple and executive-friendly while technically accurate.

Add a numbered legend 1-7 in English along the bottom or right side:
1. "Client starts a TCP connection to the server IP address and port."
2. "Client sends SYN to request a new session and advertise its initial sequence number x."
3. "Server receives SYN, creates half-open state, and replies with SYN-ACK."
4. "Server acknowledges x by sending Ack=x+1 and includes its own sequence number y."
5. "Client receives SYN-ACK and sends final ACK with Ack=y+1."
6. "Both endpoints transition to ESTABLISHED state and the TCP session becomes usable."
7. "Application data can now flow reliably over the connection until later termination."

Add a small footer note in English: "Illustrative protocol lifecycle only — not an audited reference architecture." Avoid unrelated components such as browser, API, DB, cache, or queue unless shown as faint crossed-out placeholders outside the main flow with note "Not used in this protocol diagram"; prioritize protocol endpoints and states instead. No real cloud-vendor logos — use generic cloud icons only. 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).