TCP/IP, often referred to as the Internet Architecture, is a loose interpretation of the strictly layered architecture called the Open System Interconnection Model, otherwise known as the OSI Model.

This paper explains the 2 popular reference models: OSI reference model and TCP/IP model, by comparing the functionality of each layer in both models.

The general way to change the conduct of the TCP/IP stack is through so-called TCP/IP options. Let's take a look at how you can use them to optimize the data transmission.

$49.95 Thomas Herbert's book The Linux TCP/IP Stack: Networking for Embedded Systems is a thorough guided tour of the Linux kernel TCP/IP implementation. Herbert builds his description of Linux ...

A top-down exploration of networking using the 5-layer model and the TCP/IP stack. HTTP, FTP, DNS, BSD Sockets, concurrent servers, checksums, reliable transport with stop-and-wait, go-back-n, ...

Offloading TCP/IP (transport) processing: In conventional Ethernet, the TCP/IP stack is a software implementation, putting a tremendous load on the host server’s CPU.

The video below is a good starting point, but then read on for a description of how TCP/IP is actually transported over a Lego train carrier.

Going beyond many TCP/IP “offload engines,” the new CAST core is: Complete — It can implement the entire stack in hardware: IP, VLAN, ARP, ICMP (ping), DHCP client, UDP stack, and TCP. Autonomous — It ...

This model has turned out to be highly flexible, offering new opportunities for innovation and productivity that were not present in the old point-to-point model. The TCP/IP stack allows each ...

The hardware UDP/IP stack cores that are described in this paper can be viewed as tailored subsets of the TCP/IP stack and one possible configuration is represented, related to the OSI model, as the ...