| Internet-Draft | MN-UTIL-01 | September 2026 |
| Nichols | Expires 29 March 2027 | [Page] |
TCP/IP standardized interoperability and end to end transport semantics. The World Wide Web standardized publishing and retrieval. Neither TCP/IP nor the Web specifies, provisions, or enforces the path properties required for utility grade Internet operation at scale.¶
This memo defines terminology to distinguish interoperability standards from utility grade operation and specifies operational requirements for "infrastructure activation": provisioned transport, interconnection strategy, routing policy control, redundancy, locality, continuous monitoring, incident response, and enforceable service accountability. This memo proposes no protocol changes.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 29 March 2027.¶
Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
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:¶
+------------------------------------------------------------+ | Layer 3: Infrastructure activation | | Utility grade Internet behavior | +------------------------------------------------------------+ | Layer 2: The Web | | Publishing and retrieval | +------------------------------------------------------------+ | Layer 1: Protocols | | Interoperability | +------------------------------------------------------------+
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.¶
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 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
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.¶
The following observable conditions can occur while protocols remain correct:¶
These failures are utility failures, not protocol definition failures.¶
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:¶
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.¶
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:¶
The Web can make "content exists" true. It cannot make "content arrives predictably at distance" true without an engineered corridor underneath.¶
A deployment that claims utility grade Internet operation across borders MUST satisfy the requirements in this section for the scope of its claimed service.¶
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).¶
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.¶
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.¶
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.¶
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.¶
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.¶
The operator MUST define measurable obligations appropriate to the claimed service, including targets, reporting, accountability, and enforceable commitments such as SLAs and remedies.¶
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 process document states the distinction this memo draws. RFC 2026, The Internet Standards Process, Revision 3 [RFC2026], 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 Section 1.1 of this memo: protocol authorship is not creation of the interconnected, operated system.¶
RFC 2026, Section 3.3 [RFC2026], 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 [RFC1200], graded IP Required and TCP Recommended, and STD 1 in its June 1997 edition, RFC 2200 [RFC2200], 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 [RFC7100] 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.¶
The requirements of Section 7 of this memo have a documented ancestor in the earliest specification of the ARPANET. Request for Quotations No. DAHC15 69 Q 0002 [RFQ1968], 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 Section 7 of this memo requires for utility grade operation, and the owner of the ARPANET specified all four in 1968, twelve years before RFC 761 [RFC0761] of January 1980 specified TCP on the assumption of a potentially unreliable datagram service beneath it. The activation gap defined in Section 3 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.¶
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.¶
None.¶