TCP/IP Protocol Suite
Layers and core protocols of the TCP/IP model.
The four-layer TCP/IP model with the protocols that live at each layer: application, transport, internet and network access. It is the model the internet actually uses and a compact reference for where a given protocol belongs.
Use it when
- You want the simpler four-layer view instead of the seven-layer OSI model.
- You are placing a protocol such as DNS, TCP or ARP in its layer.
Watch out for
- The layer names are not used identically in every textbook; some split network access into link and physical.
- Protocols such as ARP and TLS do not fit one layer cleanly.
The data
4 rows
| Layer | Protocols |
|---|---|
| Application | HTTP, HTTPS, FTP, SMTP, DNS, SSH |
| Transport | TCP, UDP |
| Internet | IP, ICMP, ARP, IGMP |
| Network Access | Ethernet, Wi-Fi, PPP |
Fields
The shape of this dataset, read from the data itself: every column, its type and a real value. Agents can use this to plan a query without fetching the whole document.
| Section | Field | Type | Example |
|---|---|---|---|
| data | layer | string | Application |
| data | protocols | string | HTTP, HTTPS, FTP, SMTP, DNS, SSH |
Fetch the same bytes
The static files contain the same reference rows as the API, with no API rate limit. Live metadata, such as view counts, may differ. Use the API for content negotiation; use the static files for a cacheable snapshot.
curl "https://yjtoon.yunusemrevurgun.com/api/dataset/tcp-ip-protocol-suite?format=toon"
const res = await fetch( "https://yjtoon.yunusemrevurgun.com/static-data/dataset/tcp-ip-protocol-suite.toon" ); const toon = await res.text();
Rate limit: 120 requests per minute per IP, no key and no signup. API reference →