Mutual Encapsulation Considered Dangerous
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 5
- Abstract
- 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.
- Publication Date
- 1992-05-01
- Status Note
- Informational
- DOI
10.17487/RFC1326- Link
- https://doi.org/10.17487/RFC1326
- Author(s)
- Paul Tsuchiya
- Keyword(s)
- Protocol
Latest version of IETF RFC 1326
Document Versions — IETF RFC 1326
-
▶ IETF RFC 1326 (1992-05-01)THIS DOC [ACTIVE] [LATEST VERSION]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC1326.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 1326, Mutual Encapsulation Considered Dangerous. Available at https://doi.org/10.17487/RFC1326
Snippet:
IETF RFC 1326, Mutual Encapsulation Considered Dangerous. Available at https://doi.org/10.17487/RFC1326
HTML (ISO 690 compliant)
Preview:
IETF RFC 1326, Mutual Encapsulation Considered Dangerous. Available at https://doi.org/10.17487/RFC1326
Snippet:
<span class="citation"><cite>IETF RFC 1326</cite>, Mutual Encapsulation Considered Dangerous. Available at <a href="https://doi.org/10.17487/RFC1326" target="_blank" rel="noopener">https://doi.org/10.17487/RFC1326</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 1326, Mutual Encapsulation Considered Dangerous
doi: 10.17487/RFC1326
url: https://doi.org/10.17487/RFC1326
doi: 10.17487/RFC1326
url: https://doi.org/10.17487/RFC1326
Snippet:
<li> <cite id="bib-rfc1326">IETF RFC 1326</cite>, Mutual Encapsulation Considered Dangerous <span class="doi">10.17487/RFC1326</span> </li>
Referenced By
- IETF RFC 1701 [Active*]
- IETF RFC 1888 [Superseded*]
- IETF RFC 2784 [Active*]