RFC 4840: Multiple Encapsulation Methods Considered Harmful
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC4840
- Published
- April 2007
- Authors
- B. Aboba; E. Davies; D. Thaler
- Status
- INFORMATIONAL
- Stream
- IAB
- Area
- —
- Pages
- 27
- Also known as
- —
Topics
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 7687Report from the Strengthening the Internet (STRINT) WorkshopCurrent
December 2015
- RFC 1958Architectural Principles of the InternetUpdated
June 1996
- RFC 8728RFC Editor Model (Version 2)Obsoleted
February 2020
- RFC 8730Independent Submission Editor ModelUpdated
February 2020
- RFC 3777IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall CommitteesObsoleted
June 2004
- RFC 3439Some Internet Architectural Guidelines and PhilosophyCurrent
December 2002
- RFC 2600Internet Official Protocol StandardsObsoleted
March 2000
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?