Protocol Architects Are Not the Creators of the Internet
draft-mnichols-protocols-not-the-internet-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Mark Nichols | ||
| Last updated | 2026-08-02 (Latest revision 2026-01-29) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
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. Figure 1. Three layer model. Protocols enable interoperability. The Web enables publishing. Utility grade Internet behavior requires infrastructure activation.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)