EVOPEDIA

← all systems · see it in The System

Internet protocol suite (TCP/IP): the layered datagram protocols every host and router runs, the RFC record that specifies them, and the community that keeps them

The Internet protocol suite, commonly known as TCP/IP, is a framework for organizing the communication protocols used in the Internet and similar computer networks according to functional criteria ... [It] provides end-to-end data communication specifying how data should be packetized, addressed, transmitted, routed, and received. This functionality is organized into four abstraction layers ... The technical standards underlying the Internet protocol suite and its constituent protocols are maintained by the Internet Engineering Task Force (IETF).

Properties published scienceour proposal

Sourced fields, and our own readings.

aliasesTCP/IP, Internet protocol suite, TCP/IP (the layered end-to-end datagram rule plus the RFC process for adding more)
arrivesdesign 1973, published May 1974; IPv4 installed in ARPANET 1983; DoD standard March 1982
born atdesigned summer 1973, published May 1974; first three-network transmission 22 November 1977; ARPANET flag day 1 January 1983
born precisionmonths (1973-1974 design); a day (flag day)
boundaryInside: the generating rule, which is one common internetwork datagram format and its layering (link, internet, transport, application), the end-to-end split (reliability 'delegated to the hosts'), the robustness rule, and the open rule for adding more (Internet Draft into a numbered RFC; IANA registry values). Also inside: its shell, the closed-to-edit RFC series ('never rescinded or modified') and the IETF tradition of rough consensus and running code that keeps it. Outside: what it unpacks into (the Internet, application protocols), the links and packet switching it rides on, middleboxes on the path, rival suites, and the stored-program machines that run it.
nested levelA Seed within stored-program computing ('protocols are to communication what programming languages are to computations'); built on packet switching (Baran early 1960s, Davies 1965) and the ARPANET's RFC practice (1969); above it the Internet, 'a network of networks'.
quantumthe protocol specification: a common internetwork datagram format and layering rules, published as RFCs, which any network and any application can copy and implement
scaletechnological
shellthe RFC canon closed to edits: 'Once submitted, accepted, and published, an RFC cannot be changed'; changes need a new RFC with a new serial number; the IETF standards track is the codifier

Measures (74) published science

RFC 1 (Host Software, Steve Crocker)7 April 1969 date
RFC series length (RFC 9280, the RFC Editor Model v3)numbered past 9,280 by June 2022; not all RFCs are standards
IANA protocol registriesover 2,800 registries and subregistries (2015)
first port-number registry proposed (Postel, RFC 433)December 1972 date
design of the common internetwork protocol (Kahn and Cerf)summer 1973; published May 1974 date
first specification of the Transmission Control Program (RFC 675)December 1974 date
first three-network internetworked transmission22 November 1977 (packet radio, satellite network, ARPANET) date
DoD standard for all military networking; ARPANET flag dayMarch 1982; 1 January 1983 date
BSD TCP/IP code placed in the public domainJune 1989 date
IPv4 address space (32-bit)c. 4.3e9 addresses
IPv6 address space (128-bit)c. 3.4e38 addresses
IPv6 share of Google's trafficover 41% (January 2023) percent
Internet users (ITU estimate)6 billion, 74% of the world's population; 2.2 billion offline (2025) people
share of two-way telecommunicated information carried over the Internet1% (1993); 51% (2000); more than 97% (2007) percent
first observed congestive collapse (NSFNET phase-I backbone)32 kbit/s fell to 40 bit/s (three orders of magnitude), October 1986; until end-node congestion control 1987-1988
paths with an intermediary that modifies TCP metadataa third of paths; 6.5% with harmful ossifying effects fraction of paths
IETF meeting attendance21 at the first (16 January 1986); maximum 2810 (December 2000, San Diego) attendees
TCP/UDP port rangesregistered 1024-49151; dynamic or private 49152-65535 port numbers
transport protocols, OSI against TCP/IPfive against two protocols
selective acknowledgment throughput gain (Bruyeron, Hemon and Zhang 1998)up to 45% percent
characteristic clock: IETF meetingsthree per year since 1991 (quarterly before) meetings per year
characteristic clock: TCP sequence-number space wrapsafter 2^32 bytes ('Is this sequence number in the first 4 GB or the second?')
characteristic clock: retransmission timeoutdynamically determined; initial value smoothed RTT + max(G, 4 x RTT variation) (formula, no number given) seconds
characteristic clock: protocol generations at the waistIPv4 defined 1981 (RFC 791); IPv6 Draft Standard December 1998, Internet Standard 14 July 2017 years
split of TCP and IP (version 4)1978 date
DoD standard for all military computer networkingMarch 1982 date
ARPANET flag day (NCP to TCP/IP)1 January 1983 date
IPv4 address space32-bit; approximately four billion hosts addresses
IPv6 standardised1998; 128-bit addresses; production implementations about 2006 date
last unassigned IPv4 top-level blocks allocated by IANA to the RIRsFebruary 2011 (blocks of 16 million addresses) date
users reaching Google over IPv6approximately 50% (June 2026); over 41% of Google's traffic (January 2023) percent
significant ossification set inby 2005 date
IANA registries and subregistriesover 2,800 (2015) registries
first port-number registry (Postel, RFC 433)December 1972 date
NomCom sizeten randomly chosen volunteers, a non-voting chair and 4 or 5 liaisons people
RFC 9293 obsoletesRFC 793 and RFCs 879, 2873, 6093, 6429, 6528 and 6691 (August 2022) documents
transmission speeds the design must allow fordiffering by at least 7 orders of magnitude
growth over the ARPANET's first 25 yearsfactors between 1000 (backbone speed) and 1000000 (number of hosts)
standards track maturity levelsthree in RFC 2026 (Proposed, Draft, Standard); reduced to two by RFC 6410 (2011) levels
characteristic clock: minimum time at a standards-track levelat least six months at Proposed Standard; at least four months, or one IETF meeting, at Draft Standard (RFC 2026)
characteristic clock: Internet-Draft lifetimeremoved after more than six months unchanged without IESG recommendation
characteristic clock: TCP initial sequence number generator cycleapproximately every 4.55 hours (clock ticking about every 4 microseconds)
minimum IPv4 header5 x 32-bit words (20 octets)
default send MSS (IPv4)536 (576 - 40) octets
payload share at the default MSS (per-hand-off efficiency, IP + TCP headers)536/576 = 0.93 ratio (usable out / sent in)
1986 congestion collapse throughput (LBL to UC Berkeley)32 Kbps to 40 bps (a factor of about 1000) bit/s
gateway drop rate in 1988 congestion10% of incoming packets fraction
dynamic range TCP spanned in 1988800 Mbps (Cray channels) to 1200 bps (packet radio) bit/s
reassembly timer (initial setting)15 s initial; at most the maximum time to live, about 4.25 minutes
characteristic clock: TIME-WAIT (2 x MSL)2 x MSL; MSL 'arbitrarily defined to be 2 minutes'
fast retransmit threshold3 duplicate ACKs
congestion response: slow start threshold after lossssthresh = max(FlightSize / 2, 2*SMSS) bytes
TCP initial window (experiment)10 segments (from 2-4)
TCP options passing, by port (Honda 2011)96% (port 34343), 80% (port 80) fraction of paths
paths with layer-4 middlebox interference (Honda 2011)at least 25% fraction of paths
implementations needed to advance a standardat least two independent and interoperable, from different code bases implementations
protocols at the waistone network protocol (IPv4), two major transports (TCP, UDP) protocols
characteristic clock: ack clock (one window per round trip)packet spacing matches 'the packet time on the slowest link in the path'
RIP periodic routing timer (characteristic clock of the routing channel)30 s
router processing time for one routing message (Xerox PARC measurement)about 300 (1 ms per route x 300 routes)
randomness needed to keep those routers out of stepat least 1
loss rate during synchronized routing-update events (1992 audiocast)50 to 85 %
TCP throughput under loss (Mathis et al. model)BW = (MSS/RTT) x C/sqrt(p), C = sqrt(3/2) = 1.22 for periodic loss with every packet acknowledged (1.31 random loss; 0.87 and 0.93 with delayed ACKs) bytes/s
QUIC share of Internet traffic (2017)7 %
QUIC 0-RTT handshake share (desktop)about 88 %
clients unable to use QUIC (2016)4.4 (95.3 used it; 0.3 rate-limited) %
QUIC default payload size (set by the 1500-byte Ethernet MTU)1350 bytes
Internet hosts, Jan 1997 to Dec 200016 million to 100 million (about 60%/year) computers
USENET traffic growth since 1984about 80 %/year
CoDel target sojourn time and intervalTARGET 5 ms; INTERVAL 100 ms
TCP handshake share of HTTP transaction latencyup to 25 (3.3 transactions per connection on average) %
TCP Fast Open page-load improvement (selected popular sites)10 to 40 %
IETF meeting frequency3 per year
IPv6 share of global Internet traffic (2013)approximately 1 %

Open contentions (5) open contention

Where sources or readings disagree. Both stay on the map.

Partners and parts published science

Built from / builds (16)

Sits inside / holds (5)

Trades with (valence) (21)

expressed by (29)

floor filled by (37)

represents (1)

seed within (1)

Kinds (1)

Notes published science

Layers

The ways it takes in its world, where they meet, and how it acts back, each from L1 (where it meets the world) up.

mental representation: rough consensus and running code held by the IETF community

  1. L1: Volunteer engineers: 'There is no membership in the IETF. Anyone can participate by signing up for a working group mailing list or registering for an IETF meeting'; 21 at the first meeting (16 January 1986).
  2. L2: Sensing the room: humming rather than hand-raising 'allows a group to quickly discern the prevalence of dissent'.
  3. L3: The shared principles held, not written: 'no architecture, but only a tradition, which was not written down for the first 25 years'; the end-to-end principle 'continuously reinterpreted'; 'The principle of constant change is perhaps the only principle of the Internet that should survive indefinitely.'
  4. L4: Working groups: decisions 'taken later on the working group mailing list'; the community belief that 'the goal is connectivity, the tool is the Internet Protocol, and the intelligence is end to end'.
  5. L5: 'Rough consensus is the primary basis for decision making'; support as 'the lack of disagreement ... rather than affirmative agreement'; consensus 'when all issues are addressed, but not necessarily accommodated' (RFC 7282).
  6. L6: The IESG (area directors and the IETF Chair) 'responsible for the overall operation of the IETF'; a NomCom of 'ten randomly chosen volunteers' appoints and removes the leadership.
  7. L7: Clark: 'We reject: kings, presidents, and voting. We believe in: rough consensus and running code'; purpose 'Creating voluntary standards to maintain and improve the usability and interoperability of the Internet'.

packet internetwork: the four TCP/IP layers over link signals (parked on EM; see newMediums sys:packet-network)

  1. L1: Transmission media: the networks are 'linked by electronic, wireless, and optical networking technologies'; the suite 'may be implemented on top of virtually any link-layer technology' (VPNs and tunnels included). Below the link layer, 'All other aspects ... are implicitly assumed to exist and are not explicitly defined in the TCP/IP model'.
  2. L2: Link layer: device driver, firmware or chipset 'functions, such as framing, to prepare the internet layer packets for transmission'; IP addresses translated to link-layer (MAC) addresses.
  3. L3: Internet layer, the waist: the IP datagram ('a header and a payload'), source and destination addresses (32-bit IPv4, 128-bit IPv6), a protocol number naming the upper protocol, best-effort delivery; 'a uniform networking interface that hides the actual topology'; ideally 'one, and only one, protocol at the Internet level'.
  4. L4: Transport layer, at the hosts: TCP's 'reliable, in-order, byte-stream service' (sequence numbers, checksums, retransmission, three-way handshake, ports, passive open) and UDP's connectionless datagrams; state kept only in the endpoints (fate-sharing).
  5. L5: Flow and congestion control: the receive window; slow start, congestion avoidance, fast retransmit and fast recovery (AIMD, 'a closed-loop control algorithm'); a retransmission timeout set from the smoothed round-trip time; RED and ECN signals from routers; 'an approximately max-min fair allocation between flows'.
  6. L6: Routing among independent networks: routers forward datagrams hop by hop and do not read what they carry; they 'communicate with one another via specially designed routing protocols'; routing state must be 'self-healing'; IANA delegates address blocks to five regional registries.
  7. L7: Application layer: 'process-to-process data exchange for applications' (SMTP, FTP, SSH, HTTP); services at well-known ports; the stated goal, RFC 1958: 'the goal is connectivity, the tool is the Internet Protocol, and the intelligence is end to end rather than hidden in the network'.

the boardroom (shared floors)

  1. L3: IP in every host and router, the narrow waist: header checks, the destination address, time to live, fragmentation; forwarding each datagram on its own
  2. L4: Transport in the hosts: each TCP connection's state (sequence numbers, windows, timers, the retransmission queue) and congestion control; UDP; ports
  3. L5: The application layer: the programs' protocols and the support protocols (naming, routing, management) that run over transport
  4. L6: The RFC series and the standards track: the numbered text every implementer reads; drafts, running code and attack reports land here
  5. L7: The IETF community: rough consensus and running code; humming instead of voting; the IESG approves; decides what the suite becomes

the protocol suite as network engineers draw it: link signals up to the community that keeps it (reader's view)

  1. L1: Transmission media: the copper, fibre and radio that link the packet switches; signals carrying frames
  2. L2: Link layer: each directly connected network's own protocol (Ethernet, Wi-Fi, PPP and the rest) moves a frame to the next hop
  3. L3: Internet layer (IP, with ICMP): one connectionless datagram format and address space; gateways (routers) forward each datagram independently, keeping no connection state; fragmentation, time to live
  4. L4: Transport layer, in the hosts: TCP's reliable, ordered byte stream (sequence numbers, acknowledgments, retransmission, flow and congestion control); UDP's bare datagrams; ports name the processes
  5. L5: Application layer: the protocols people's programs speak (web, mail, file transfer, remote login) and the support protocols (DNS, routing and management)
  6. L6: The specifications: the numbered RFC series and its standards track, the shared text that lets independent code interoperate
  7. L7: The community that keeps it: the IETF's working groups, rough consensus (humming, not voting) and running code; the IESG approves; the purpose is a network anyone can join

way in: Arriving datagrams (traffic at a host's or router's interface)

  1. L1: Signals on the attached link (copper, fibre, radio)
  2. L2: The interface's link-layer driver takes the frame off the network

way in: Attacks and the reports of them

  1. L1: An attacker controls some machine connected to the Internet
  2. L3: Source addresses spoofed; hosts that trust the IP source address are fooled
  3. L4: TCP sequence numbers predicted; SYN floods fill half-open connection state
  4. L5: The flaws written up for the community

way in: Congestion (the path's own load)

  1. L1: Offered traffic exceeds a link; the gateway's buffer overflows
  2. L3: The datagram is dropped, or (ECN) marked Congestion Experienced in the IP header

way in: Data handed in by local programs

  1. L1: A process in the host holds the data it wants to send
  2. L2: The SEND call hands the user's buffer to the connection

way in: Proposals from engineers (the inner channel)

  1. L1: An engineer's idea, from anyone: 'There is no membership in the IETF. Anyone can participate'
  2. L2: Written up as an Internet-Draft, with no institution behind it needed
  3. L3: Posted in the Internet-Drafts directory, which removes it after six months unless it moves on
  4. L4: Discussed on the working group's list
  5. L5: Working-group consensus lets it go forward as an RFC

way in: Reports from the path (ICMP errors, Datagram Too Big, redirects)

  1. L1: A router or host on the path sends a report about a datagram it could not deliver
  2. L2: Link frame on the directly connected network
  3. L3: ICMP, carried in IP and read by the IP module

way in: Routing information from neighbouring routers

  1. L1: A link or neighbouring router changes; signals on the links between routers
  2. L2: Link frames between neighbouring routers
  3. L3: Routing messages carried in IP datagrams; routing is the gateways' job, not the hosts'
  4. L4: Between networks, BGP sessions run over TCP

way in: Running code and operational experience

  1. L1: Code running in hosts and routers, built and tested before standards are set
  2. L2: Independent implementations tested against each other
  3. L4: Problems and fixes found in use, documented piecemeal
  4. L5: Discussed on a working group's mailing list

way in: Time (timers in the hosts, time to live on every datagram)

  1. L1: The host's clock ticks
  2. L3: Every datagram carries a time to live, set by the sender and reduced along the route

way out: Acknowledgments and the advertised window

  1. L1: Signals on the return path, where they arrive on the sender's datagrams channel
  2. L3: Carried back in IP datagrams
  3. L4: The receiver acknowledges the next byte it expects and advertises its window, even when the window is zero

way out: Forwarding (a router passes each datagram on)

  1. L1: Out on the next link
  2. L2: Framed for the next network
  3. L3: Each datagram forwarded on its own, by its destination address

way out: Reporting back (ICMP from routers and hosts)

  1. L1: Back along the path to the source's icmp channel
  2. L3: A router that cannot forward a datagram (too big with Don't Fragment set, no route, TTL expired) reports it to the source

way out: Sending (data down the stack onto the link)

  1. L1: Signals on the link
  2. L2: Framed for the attached network
  3. L3: IP addresses each datagram toward its destination
  4. L4: TCP cuts the stream into segments, numbers them and keeps a copy until acknowledged
  5. L5: A program hands its data to transport

way out: Standards and running code (the suite changes itself)

  1. L3: New fields in the IP header (ECN, 2001)
  2. L4: New algorithms go into the hosts' TCP (4BSD, 1988); defences into ISN generation (RFC 6528)
  3. L6: An RFC published; later RFCs obsolete earlier ones (RFC 9293 obsoleted RFC 793 and six updates)
  4. L7: Rough consensus; the IESG approves

way out: Throttling (the sender backs off)

  1. L1: Less traffic reaches the bottleneck; the queue drains
  2. L4: The sender cuts its congestion window (ssthresh to half the data in flight)

written record: the RFC series (closed-to-edit specifications plus the rule for adding more)

  1. L1: RFCs as plain text: typewritten hard copies among ARPA researchers from 1969 (RFC 1, 'Host Software', 7 April 1969); over the ARPANET from December 1969; 'Every RFC is submitted as plain ASCII text'.
  2. L2: Internet Draft: submitted by experts 'without support from an external institution'; written with a shared requirement vocabulary ('MUST', 'NOT RECOMMENDED'); removed after six months unchanged unless recommended.
  3. L3: Number bound once: 'The RFC Editor assigns each RFC a serial number. Once assigned a number and published, an RFC is never rescinded or modified'; IANA binds globally unique names and numbers (ports, protocol numbers) once to one meaning.
  4. L4: The series as a whole: 'a continuous historical record'; later RFCs obsolete earlier ones; STD numbers that keep pointing while the RFCs behind them change; over 2,800 IANA registries (2015); the four-layer structure 'never modified'.
  5. L5: Status and selection: Informational, Experimental, Best Current Practice, Standards Track, Historic; only the IESG approves standards-track RFCs; Draft Standard needed 'at least two independent and interoperable implementations from different code bases'; cut to two maturity levels (RFC 6410); 'Nothing gets standardised until there are multiple instances of running code.'
  6. L6: Streams and editing: 'five streams of RFCs: IETF, IRTF, IAB, independent submission, and Editorial'; the RFC Editor (Jon Postel 1969-1998).
  7. L7: Stated role: the RFCs 'shape the Internet's inner workings and have played a significant role in its success'.

Sources (54) published science

Request for Comments (Wikipedia via Wikimedia Enterprise, cached research/showcase/cache/wme)
Internet protocol suite (Wikipedia via Wikimedia Enterprise, cached research/showcase/cache/wme)
RFC 1122, Requirements for Internet Hosts: Communication Layers (1989) (behind its links)
Communication protocol (Wikipedia, rev 1379515493, 2026-10-10, via Wikimedia Enterprise; read by section) (behind its links)
RFC 1958: Architectural Principles of the Internet (B. Carpenter, ed., IAB, June 1996) (behind its links)
RFC 1: Host Software (S. Crocker, 7 April 1969) (behind its links)
Internet Assigned Numbers Authority (Wikipedia, rev 1378730556, 2026-10-05, via Wikimedia Enterprise; read by section) (behind its links)
Internet Protocol (Wikipedia, rev 1381410383, 2026-10-22, via Wikimedia Enterprise) (behind its links)
Internet (Wikipedia, rev 1381320565, 2026-10-21, via Wikimedia Enterprise; read by section) (behind its links)
Network congestion (Wikipedia, rev 1380967227, 2026-10-19, via Wikimedia Enterprise) (behind its links)
Protocol ossification (Wikipedia, rev 1380274676, 2026-10-14, via Wikimedia Enterprise) (behind its links)
Internet Engineering Task Force (Wikipedia, rev 1381825033, 2026-10-25, via Wikimedia Enterprise) (behind its links)
Transmission Control Protocol (Wikipedia, rev 1379364197, 2026-10-09, via Wikimedia Enterprise; read by section) (behind its links)
Protocol Wars (Wikipedia, rev 1380571779, 2026-10-16, via Wikimedia Enterprise; read by section) (behind its links)
IPv6 (Wikipedia, via Wikimedia Enterprise) (behind its links)
RFC 9293: Transmission Control Protocol (TCP) (W. Eddy, ed., August 2022; STD 7) (behind its links)
Internet Standard (Wikipedia, via Wikimedia Enterprise) (behind its links)
RFC 2026: The Internet Standards Process, Revision 3 (S. Bradner, October 1996) (behind its links)
RFC 791, Internet Protocol (1981) (behind its links)
Jacobson and Karels, Congestion Avoidance and Control (November 1988; SIGCOMM '88, doi:10.1145/52324.52356) (behind its links)
RFC 5681, TCP Congestion Control (2009) (behind its links)
RFC 6928: Increasing TCP's Initial Window (J. Chu, N. Dukkipati, Y. Cheng, M. Mathis, April 2013) (behind its links)
Honda, M., Nishida, Y., Raiciu, C., Greenhalgh, A., Handley, M. & Tokuda, H. (2011) Is it Still Possible to Extend TCP? Proc. ACM IMC 2011, doi:10.1145/2068816.2068834 (behind its links)
Akhshabi, S. & Dovrolis, C. The Evolution of Layered Protocol Stacks Leads to an Hourglass-Shaped Architecture (extended version of the ACM SIGCOMM 2011 paper; read via fetch summary) (behind its links)
Floyd, S. & Jacobson, V. (1994) The Synchronization of Periodic Routing Messages. IEEE/ACM Transactions on Networking 2(2) (author copy, icir.org) (behind its links)
Mathis, M., Semke, J., Mahdavi, J. & Ott, T. (1997) The Macroscopic Behavior of the TCP Congestion Avoidance Algorithm. ACM SIGCOMM Computer Communication Review 27(3) (behind its links)
Langley, A. et al. (2017) The QUIC Transport Protocol: Design and Internet-Scale Deployment. Proc. ACM SIGCOMM 2017, doi:10.1145/3098822.3098842 (behind its links)
Floyd, S. & Paxson, V. (2001) Difficulties in Simulating the Internet. IEEE/ACM Transactions on Networking 9(4) (author copy, icir.org) (behind its links)
RFC 8289: Controlled Delay Active Queue Management (K. Nichols, V. Jacobson, A. McGregor, J. Iyengar, January 2018) (behind its links)
RFC 7413: TCP Fast Open (Y. Cheng, J. Chu, S. Radhakrishnan, A. Jain, December 2014) (behind its links)
Migault, D. (2022) Estimating Meetings' Air Flight CO2 Equivalent Emissions: An Illustrative Example with IETF meetings. arXiv:2212.03172 (behind its links)
Russell, A. L. (2013) OSI: The Internet That Wasn't. IEEE Spectrum, July 2013 (a historian's account, from interviews and archives) (behind its links)
Robustness principle (Wikipedia, rev 1362213472, 2026-07-02, via Wikimedia Enterprise) (behind its links)
Rough consensus (Wikipedia, via Wikimedia Enterprise) (behind its links)
Bellovin, S. M. (1989) Security Problems in the TCP/IP Protocol Suite. Computer Communication Review 19(2):32-48, doi:10.1145/378444.378449 (behind its links)
RFC 1191: Path MTU Discovery (J. Mogul, S. Deering, November 1990) (behind its links)
End-to-end principle (Wikipedia, rev 1340005850, 2026-02-23, via Wikimedia Enterprise) (behind its links)
Wikipedia: Operating system (behind its links)
RFC 6528: Defending against Sequence Number Attacks (F. Gont, S. Bellovin, February 2012) (behind its links)
Packet switching (Wikipedia, rev 1376334725, 2026-09-23, via Wikimedia Enterprise; read by section) (behind its links)
Ali, I., Hong, S. & Cheung, T. (2024) Congestion or No Congestion: Packet Loss Identification and Prediction Using Machine Learning. arXiv:2408.03007 (behind its links)
Wikipedia: Network interface controller (behind its links)
Eddy 2007, RFC 4987: TCP SYN Flooding Attacks and Common Mitigations (doi:10.17487/RFC4987) (behind its links)
Freed N. Behavior of and Requirements for Internet Firewalls. RFC 2979, IETF, October 2000 (doi:10.17487/RFC2979) (behind its links)
Computer network (Wikipedia, via Wikimedia Enterprise snapshot 2026-11-01) (behind its links)
Cerf and Kahn, A Protocol for Packet Network Intercommunication, IEEE Transactions on Communications 22(5), 1974 (doi:10.1109/TCOM.1974.1092259) (behind its links)
RFC 7282: On Consensus and Humming in the IETF (P. Resnick, June 2014) (behind its links)
RFC 3168, The Addition of Explicit Congestion Notification (ECN) to IP (2001) (behind its links)
RFC 4271, A Border Gateway Protocol 4 (BGP-4) (2006) (behind its links)
Clark, The Design Philosophy of the DARPA Internet Protocols, ACM SIGCOMM 1988 (doi:10.1145/52324.52336) (behind its links)
Leiner, Cerf, Clark, Kahn, Kleinrock, Lynch, Postel, Roberts, Wolff, A Brief History of the Internet (Internet Society; arXiv cs/9901011) (behind its links)
Eddy W. TCP SYN Flooding Attacks and Common Mitigations. RFC 4987, IETF, August 2007 (doi:10.17487/RFC4987) (behind its links)
Saltzer, Reed and Clark, End-to-End Arguments in System Design, ACM TOCS 2(4), 1984 (doi:10.1145/357401.357402) (behind its links)
RFC 9413: Maintaining Robust Protocols (M. Thomson, D. Schinazi, June 2023) (behind its links)