RFC 1326: Mutual Encapsulation Considered Dangerous
In plain English — editorial summary, not part of the RFC
This memo describes a packet explosion problem that can occur with mutual encapsulation of protocols (A encapsulates B and B encapsulates A). This memo provides information for the Internet community. It does not specify an Internet standard.
Document record
- Document ID
- RFC1326
- Published
- May 1992
- Authors
- P. Tsuchiya
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 5
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3205On the use of HTTP as a SubstrateObsoleted
February 2002
- RFC 9599Guidelines for Adding Congestion Notification to Protocols that Encapsulate IPCurrent
August 2024
- RFC 9601Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a ShimCurrent
August 2024
- RFC 1335A Two-Tier Address Structure for the Internet: A Solution to the Problem of Address Space ExhaustionCurrent
May 1992
- RFC 1379Extending TCP for Transactions -- ConceptsObsoleted
November 1992
- RFC 1250IAB Official Protocol StandardsObsoleted
August 1991
- RFC 1249DIXIE Protocol SpecificationCurrent
August 1991
- RFC 1200IAB official protocol standardsObsoleted
April 1991
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?