Protocol Architects Are Not the Creators of the Internet

Introduction Public headlines and institutional profiles frequently use "created the Internet" as shorthand for protocol authorship. Some extend the same shorthand to the Web (HTTP, HTML, URIs). This memo separates:

Interoperability standards, which define protocol semantics enabling heterogeneous systems and networks to exchange data.
Utility grade Internet operation, which is repeatable, measurable, and enforceable service behavior suitable for commerce and institutional dependence across borders.

Three layer model. Protocols enable interoperability. The Web enables publishing. Utility grade Internet behavior requires infrastructure activation.

Category statement Designing protocols, or leading development of protocols or the Web software system, is not equivalent to creating utility grade Internet operation. A whole system creation claim requires whole system evidence. Protocol correctness and adoption do not imply utility grade operation. Protocol authorship is often interpreted as whole system authorship in public narratives. This memo does not diminish protocol invention credit. It clarifies a different claim: creation of utility grade, enforceable service behavior. Misattribution is now appearing in educational materials, where simplified creator narratives are presented as literal technical history. For example, a recent school textbook presented a single person "created the Internet" claim as fact.

Scope Protocols and the Web define semantics. The Internet is the deployed, interconnected, operated system those semantics run on. Protocols are necessary. They are not the Internet.

Thesis Protocols enable interoperability. The Web enables publishing and retrieval. Internet operation requires infrastructure activation. Protocols are necessary. They are not the Internet.

Conventions and requirement language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this memo are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

Terminology

Interoperability:: The ability of heterogeneous systems and networks to exchange data using shared protocol semantics.
Internet (internetwork):: A network of networks in which packets can be forwarded between administrative domains.
Internet utility (utility grade Internet operation):: A service environment in which end to end outcomes are sufficiently predictable and accountable to support commerce and institutional dependence across borders. Defining attributes include measurability, repeatability, enforceability, and operational accountability.
Corridor:: The practical end to end path experienced by a flow, shaped by transport, interconnection, routing policy, and queue treatment.
Infrastructure activation:: The work required to turn interoperable networking into a dependable utility, including provisioned transport, interconnection strategy, routing policy control, redundancy, locality, and continuous operations.
Activation gap:: The difference between: (a) standards compliant endpoint behavior, and (b) corridor properties required for predictable long lived sessions and secure transactions across borders.

Problem statement: interoperability without utility In an interoperable internetwork, reachability may exist while utility grade behavior does not. The activation gap exists when endpoints remain standards compliant but corridor properties fall outside the envelope required by applications and transactions.

Common failure modes The following observable conditions can occur while protocols remain correct:

high RTT variance and multi second spikes
loss and jitter that collapse long lived sessions
congested interconnects and chokepoints
policy driven queue treatment and class of service degradation
middlebox or application time budgets expiring before recovery converges
unstable routing policy interactions under load or failure

These failures are utility failures, not protocol definition failures.

What TCP/IP and routing do, and do not do

TCP transport semantics TCP provides end to end transport semantics between endpoints, including reliable delivery, ordering, flow control, congestion response, and session recovery state. TCP does not and cannot guarantee corridor viability across independent networks. Specifically, TCP:

does not select paths and does not control interdomain routing policy
does not provision capacity or ensure headroom
does not require redundancy or diverse corridors to exist
does not enforce priority, scheduling, or QoS across domains
cannot prevent application or middlebox timeouts
does not provide network operations alarms by itself

IP and interdomain routing IP provides addressing and forwarding semantics and a best effort abstraction for internetworking. IP and interdomain routing protocols can exchange reachability and can support failover only when alternate topology exists and policy permits its use. Reachability is not equivalent to utility. Interconnect capacity and routing policy frequently dominate user outcomes.

What the Web does, and does not do The Web defines a publishing and retrieval system: naming (URIs), retrieval (HTTP request and response), and documents with links (HTML) implemented in clients and servers. The Web does not create corridor viability or utility grade delivery. It:

does not create transport capacity or corridor headroom
does not control interconnection capacity, routing policy, or queue treatment
does not ensure that secure sessions complete at global distance
does not provide operational accountability for performance

The Web can make "content exists" true. It cannot make "content arrives predictably at distance" true without an engineered corridor underneath.

Requirements for utility grade Internet operation A deployment that claims utility grade Internet operation across borders MUST satisfy the requirements in this section for the scope of its claimed service.

Transport provisioning The operator MUST provision transport with sufficient headroom to keep RTT variance, loss, and jitter within bounds required by intended sessions and transactions. The operator SHOULD provision diverse corridors across meaningful failure domains (facility, carrier, geography).

Interconnection capacity and strategy The operator MUST ensure POP level interconnection capacity consistent with intended service outcomes, including port capacity, cross connects, exchange strategy, and congestion avoidance at handoffs. The operator MUST treat persistent interconnect congestion as a service failure requiring remediation.

Routing policy control The operator MUST implement routing policy control using operator controlled equipment and AS level intent at backbone facing handoffs. The operator MUST validate failover behavior under realistic failure conditions and policy constraints.

Redundancy and disaster recovery The operator MUST implement redundancy across meaningful failure domains and MUST demonstrate that redundancy is usable under policy and operational constraints. The operator SHOULD conduct regular failover and restoration drills.

Locality The operator SHOULD implement locality via distributed hosting, caching, replication, or placement to reduce dependency on long haul corridors for common retrieval paths and transaction flows.

Continuous operations The operator MUST implement continuous operations sufficient to detect, isolate, and remediate corridor failures and performance collapse, including monitoring, alerting, escalation, incident response, and change control.

Accountability and enforceability The operator MUST define measurable obligations appropriate to the claimed service, including targets, reporting, accountability, and enforceable commitments such as SLAs and remedies.

Attribution clarification It is technically accurate to credit protocol architects and standards bodies for interoperability. It is not technically accurate to credit interoperability standards alone for the emergence of a commercial utility. The Internet utility is an operational outcome produced by infrastructure activation and operations discipline at scale. Protocols are necessary for interoperability. They are not sufficient for utility grade behavior.

The IETF's own definition of the Internet The IETF's own process document states the distinction this memo draws. RFC 2026, The Internet Standards Process, Revision 3 , published in October 1996 as BCP 9 with Scott O. Bradner of Harvard University as its author, defines the Internet in Section 1.1 as a loosely organized international collaboration of autonomous, interconnected networks, and states that the Internet supports host-to-host communication through "voluntary adherence to open protocols and procedures defined by Internet Standards." Section 1.1 further states that many isolated interconnected networks use the Internet Standards without being connected to the global Internet, and that the Internet Standards Process covers protocols, procedures, and conventions used in or by the Internet whether or not they are part of the TCP/IP protocol suite. Section 5 of RFC 2026 states that the Internet is composed of networks operated by a great variety of organizations with diverse goals and rules. Under the IETF's own definition, therefore, the Internet is a collaboration of networks, adherence to the protocols is voluntary, and a network that runs the Internet Standards is not thereby connected to the Internet. Each of those three statements is the IETF's own, and each is consistent with the category statement in of this memo: protocol authorship is not creation of the interconnected, operated system.

The IETF's own requirement levels never required TCP RFC 2026, Section 3.3 , defines the requirement levels applied to Internet Standards: Required means implementation is required for minimal conformance by Internet systems using the TCP/IP Protocol Suite, with IP and ICMP as the section's own example; Recommended means implementation is recommended but not required; and Elective means the applicability statement creates no explicit necessity to implement the specification. The IETF's standards registry applied those levels. STD 1 in its April 1991 edition, RFC 1200 , graded IP Required and TCP Recommended, and STD 1 in its June 1997 edition, RFC 2200 , carried the same two grades unchanged. The Required grade binds the conformance of a system that has elected to implement the suite; no Internet Standard requires a network to adopt the suite, and the registry never graded TCP Required even inside the suite's own conformance vocabulary. The IETF retired STD 1 itself by RFC 7100 in December 2013, which obsoleted RFC 5000 and moved STD 1 to Historic status. The statement "the Internet requires TCP/IP" therefore appears in no IETF instrument: the IETF's definition names networks, the IETF's adherence is voluntary, and the IETF's own grade for TCP was Recommended.

Historical note: the 1968 ARPANET specification placed reliability and a delay bound in the network The requirements of of this memo have a documented ancestor in the earliest specification of the ARPANET. Request for Quotations No. DAHC15 69 Q 0002 , issued July 29, 1968 by the Defense Supply Service-Washington of the Department of the Army for the Advanced Research Projects Agency under ARPA Order No. 1260, solicited the Interface Message Processors for the ARPA computer network and specified nineteen nodes on 50 kilobit per second leased common-carrier lines. Its Statement of Work required the network contractor to provide fault detection and recovery to guarantee virtually error-free transmission, through acknowledgment and retransmission performed by the Interface Message Processors inside the network; it made error checking, fault detection, fault recovery, line switching, and carrier quality assessment the sole responsibility of the network contractor; and it required an average message delay under one half second for a fully loaded network, ranking message delay first among the network's performance criteria, ahead of reliability and capacity. Provisioned transport, a delay bound, reliability inside the network, and a single accountable operator are the properties of this memo requires for utility grade operation, and the owner of the ARPANET specified all four in 1968, twelve years before RFC 761 of January 1980 specified TCP on the assumption of a potentially unreliable datagram service beneath it. The activation gap defined in of this memo therefore did not originate with internetworking; it originated when the reliability and delay obligations that the 1968 specification placed on the network operator were reassigned to the end hosts.

Security considerations This memo proposes no protocol changes. Predictable completion of secure sessions depends on corridor viability and on operational practices including monitoring, incident response, and accountable interconnection. Corridor instability and policy driven impairment SHOULD be treated as availability and security risks, not merely performance issues.

IANA considerations None.