RFC 1958: Architectural Principles of the Internet
In plain English — editorial summary, not part of the RFC
The Internet and its architecture have grown in evolutionary fashion from modest beginnings, rather than from a Grand Plan. While this process of evolution is one of the main reasons for the technology's success, it nevertheless seems useful to record a snapshot of the current principles of the Internet architecture. This is intended for general guidance and general interest, and is in no way intended to be a formal or invariant reference model. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1958
- Published
- June 1996
- Authors
- B. Carpenter
- Status
- INFORMATIONAL
- Stream
- IAB
- Area
- —
- Pages
- 8
- Also known as
- —
- Updated by:
- RFC 3439
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3245The History and Context of Telephone Number Mapping (ENUM) Operational Decisions: Informational Documents Contributed to ITU-T Study Group 2 (SG2)Current
March 2002
- RFC 4840Multiple Encapsulation Methods Considered HarmfulCurrent
April 2007
- RFC 7687Report from the Strengthening the Internet (STRINT) WorkshopCurrent
December 2015
- RFC 8728RFC Editor Model (Version 2)Obsoleted
February 2020
- RFC 8730Independent Submission Editor ModelUpdated
February 2020
- RFC 1787Routing in a Multi-provider InternetCurrent
April 1995
- RFC 2200Internet Official Protocol StandardsObsoleted
June 1997
- RFC 1640The Process for Organization of Internet Standards Working Group (POISED)Current
June 1994
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?