RFC 2004: Minimal Encapsulation within IP
In plain English — editorial summary, not part of the RFC
This document specifies a method by which an IP datagram may be encapsulated (carried as payload) within an IP datagram, with less overhead than "conventional" IP encapsulation that adds a second IP header to each encapsulated datagram. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2004
- Published
- October 1996
- Authors
- C. Perkins
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2005Applicability Statement for IP Mobility SupportCurrent
October 1996
- RFC 2003IP Encapsulation within IPUpdated
October 1996
- RFC 2006The Definitions of Managed Objects for IP Mobility Support using SMIv2Current
October 1996
- RFC 2002IP Mobility SupportObsoleted
October 1996
- RFC 2023IP Version 6 over PPPObsoleted
October 1996
- RFC 1981Path MTU Discovery for IP version 6Obsoleted
August 1996
- RFC 1972A Method for the Transmission of IPv6 Packets over Ethernet NetworksObsoleted
August 1996
- RFC 1970Neighbor Discovery for IP Version 6 (IPv6)Obsoleted
August 1996
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?