Multiple Encapsulation Methods Considered Harmful
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 27
- Abstract
- This document describes architectural and operational issues that arise from link-layer protocols supporting multiple Internet Protocol encapsulation methods. This memo provides information for the Internet community.
- Publication Date
- 2007-04-01
- Status Note
- Informational
- DOI
10.17487/RFC4840- Link
- https://doi.org/10.17487/RFC4840
- Author(s)
- Dr. Bernard D. AbobaElwyn B. DaviesDave Thaler
- Keyword(s)
- Internet Architecture Board, Link-layer Protocol, IP Encapsulation, Internet Protocol Encapsulation
Latest version of IETF RFC 4840
Document Versions — IETF RFC 4840
-
▶ IETF RFC 4840 (2007-04-01)THIS DOC [ACTIVE] [LATEST VERSION]
Bibliographic Reference(s)
- IEEE.STD802.1A.1990 — 10 EXTERNAL
- IEEE.STD802.1D.2004 — 802.1D-2004 EXTERNAL
- IEEE.STD802.3.2002 — IEEE802.3 EXTERNAL
- IEEE.STD802.11.2003 — 802.11 EXTERNAL
- IEEE.STD802.16.2004 — IEEE-802.16.2004 EXTERNAL
- IEEE.STD802.16E.2005 — IEEE-802.16e EXTERNAL
- IEEE Standards for Local and Metropolitan Area Networks: Draft Standard for Virtual Bridged Local Area Networks, P802.1Q-2003, January 2003. EXTERNAL
- Bittau, A., Handley, M., and J. Lackey, "The Final Nail in WEP's Coffin", Proceedings of the 2006 IEEE Symposium on Security and Privacy, pp. 386-400. EXTERNAL
- Hewlett Packard, "A Primer on HP Probe", http://www.hp.com/rnd/support/manuals/pdf/ hp_probe.pdf , July 1993. EXTERNAL
- Wang, L. et al, "A Generic Packet Convergence Sublayer (GPCS) for Supporting Multiple Protocols over 802.16 Air Interface", Submission to IEEE 802.16g: CB0216g_05_025r4.pdf, November 2005, < http://www.ieee802.org/16/netman/contrib/ C80216g-05_025r4.pdf >. EXTERNAL
- Digital Equipment Corporation, Intel Corporation, and Xerox Corporation, "The Ethernet -- A Local Area Network: Data Link Layer and Physical Layer (Version 2.0)", November 1982. EXTERNAL
- IETF RFC 826 [Active*]
- IETF RFC 893 [Active*]
- IETF RFC 894 [Active*]
- IETF RFC 903 [Active*]
- IETF RFC 948 [Superseded*]
- IETF RFC 1010 [Superseded*]
- IETF RFC 1042 [Active*]
- IETF RFC 1122 [Active*]
- IETF RFC 1144 [Active*]
- IETF RFC 1661 [Active*]
- IETF RFC 1958 [Active*]
- IETF RFC 1962 [Active*]
- IETF RFC 1972 [Superseded*]
- IETF RFC 2464 [Active*]
- IETF RFC 2472 [Superseded*]
- IETF RFC 2507 [Active*]
- IETF RFC 2508 [Active*]
- IETF RFC 2615 [Active*]
- IETF RFC 2684 [Active*]
- IETF RFC 3095 [Active*]
- IETF RFC 3241 [Active*]
- IETF RFC 3518 [Active*]
- IETF RFC 3544 [Active*]
- IETF RFC 3545 [Active*]
- IETF RFC 3759 [Active*]
- IETF RFC 4541 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC4840.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 4840, Multiple Encapsulation Methods Considered Harmful. Available at https://doi.org/10.17487/RFC4840
Snippet:
IETF RFC 4840, Multiple Encapsulation Methods Considered Harmful. Available at https://doi.org/10.17487/RFC4840
HTML (ISO 690 compliant)
Preview:
IETF RFC 4840, Multiple Encapsulation Methods Considered Harmful. Available at https://doi.org/10.17487/RFC4840
Snippet:
<span class="citation"><cite>IETF RFC 4840</cite>, Multiple Encapsulation Methods Considered Harmful. Available at <a href="https://doi.org/10.17487/RFC4840" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4840</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 4840, Multiple Encapsulation Methods Considered Harmful
doi: 10.17487/RFC4840
url: https://doi.org/10.17487/RFC4840
doi: 10.17487/RFC4840
url: https://doi.org/10.17487/RFC4840
Snippet:
<li> <cite id="bib-rfc4840">IETF RFC 4840</cite>, Multiple Encapsulation Methods Considered Harmful <span class="doi">10.17487/RFC4840</span> </li>
Referenced By
- IETF RFC 4947 [Active*]
- IETF RFC 5181 [Active*]