api: YAML JSON TOON Database
version: 1.0.0
format: toon
category:
  id: 397
  slug: networking
  name: Networking
  description: "Network protocols, models, and architecture."
  icon: globe
  created_at: 1783090350
  dataset_count: 7
  topic:
    overview: "Networking reference data describes how bytes get from one machine to another: the layered models that organize protocols (OSI and TCP/IP), the addresses and ports that name endpoints, the DNS records that map names to them, the routing protocols that choose paths, and the transport changes that separate HTTP/1.1 from HTTP/2 and HTTP/3. Almost everything here is a convention agreed in an RFC, so the details are precise and checkable, but real networks add middleboxes, NAT and filtering that the clean models leave out."
    key_ideas[7]{term,meaning}:
      Layering and encapsulation,"Each layer wraps the data from the layer above with its own header. A web request becomes an HTTP message, then a TCP segment, then an IP packet, then an Ethernet frame."
      Port,"A 16-bit number that, together with an IP address and protocol, identifies a specific service on a host. Well-known ports are conventions, not guarantees."
      TCP vs UDP,"TCP gives ordered, reliable delivery with connection setup; UDP sends independent datagrams with no delivery guarantee. QUIC rebuilds reliability on top of UDP."
      DNS record,"A typed answer from the Domain Name System. The type (A, AAAA, MX, TXT) says what kind of data the name maps to."
      Routing,Choosing the next hop for a packet. Interior protocols such as OSPF run inside one organization; BGP exchanges reachability between autonomous systems on the internet.
      NAT,"Network address translation rewrites addresses and ports so many private hosts share a public IP address, which breaks the end-to-end assumption of the original design."
      Latency vs bandwidth,"Latency is how long one bit takes to arrive; bandwidth is how many bits per second a link carries. Round trips, not raw bandwidth, dominate many protocol designs."
    pitfalls[4]: "Treating well-known ports as certain. A service can run on any port, and firewalls often decide what is reachable.","Mapping the OSI model onto real protocols too literally. TCP/IP does not have separate session and presentation layers, and several protocols span layers.","Assuming HTTP/3 uses its own port or TCP. It runs over QUIC on UDP, usually port 443.",Forgetting that DNS also uses TCP (for large responses and zone transfers) and now encrypted transports such as DNS over TLS.
    agent_tips[3]: "When a user asks 'what port does X use', give the default and say it is a convention that the deployment may change.",Quote the layer number and the layer name together when using the OSI model; the numbers are what people refer to in conversation.,"For DNS questions, ask for the record type before answering; the same name has different answers per type."
    start_with[2]: network-ports-reference,osi-model-layers
datasets[7]{id,slug,title,description,tags,view_count,created_at,entry_count,summary}:
  2857,network-ports-reference,Common Network Ports,Well-known TCP and UDP ports for common network services.,"networking,ports,tcp,udp,reference",35,1793403093,45,"Default port numbers and transport protocols for the services that account for most real traffic and most firewall rules: web, mail, remote access, name resolution, directory, file sharing, messaging and common databases. Each row gives the number, whether it is TCP or UDP, the service and what it is for."
  2782,dns-fundamentals,DNS Fundamentals,Common DNS record types and their purposes.,"networking,dns,records",52,1793403093,16,"The DNS record types that appear in everyday zone files: address records, aliases, mail routing, delegation, text records and zone authority, plus the reverse-lookup, service-location, certificate-authority and DNSSEC types operators meet next. Each row says what the record maps and what it is used for."
  2824,http2-http3-features,HTTP/2 and HTTP/3 Features,Key features and improvements introduced in HTTP/2 and HTTP/3 over HTTP/1.1.,"networking,http2,http3,protocols,performance",32,1793403093,13,"The features that distinguish HTTP/2 and HTTP/3 from HTTP/1.1, each tagged with the version it belongs to and the problem it addresses: multiplexing, header compression, transport changes in QUIC and connection behavior on mobile networks."
  2859,network-topologies,Network Topologies,Common physical and logical network layouts.,"networking,topology,architecture",42,1793403093,10,"The classic ways to wire a network, from bus and ring to star and mesh, with the trade-offs of each, plus point-to-point, hub-and-spoke, spine-leaf and daisy-chain layouts that appear in modern WANs and data centers."
  2866,osi-model-layers,OSI Model Layers,The seven layers of the OSI reference model.,"networking,osi,protocols",35,1793403093,7,"The seven layers of the OSI reference model, numbered from the physical layer (1) up to the application layer (7), each with its function and example protocols. It is the shared vocabulary for saying where in the stack a device, protocol or fault belongs."
  2884,routing-protocols,Routing Protocols,Algorithms and protocols that determine packet paths.,"networking,routing,protocols",41,1793403093,12,"The routing protocols and routing techniques network engineers meet most: distance-vector and link-state interior protocols, BGP for the internet, and the static and default routes that tie them together. Each row gives the protocol, its type and what it does."
  2912,tcp-ip-protocol-suite,TCP/IP Protocol Suite,Layers and core protocols of the TCP/IP model.,"networking,tcp,ip,protocols",177,1793403093,4,"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."