CARVIEW |
Select Language
HTTP/2 200
date: Wed, 08 Oct 2025 01:11:34 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=VtrY5NbcGLF3iLA3dwn9xEyb5L0v0WDatWmCzRACbaU-1759885894-1.0.1.1-lxGGanPwR7QD7nsfvShfudMiVDuBs.e.JCKyZ.Q3y0.ZrawFAZWQQETKnYyBEqhnGyrzWOdHDFUEDRhtq6f1iUxV9KXL6fgS1aeGz4Ns90w; path=/; expires=Wed, 08-Oct-25 01:41:34 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98b1c3cfab5fc143-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 2004 » RFC Editor
Search RFCs
RFC 2004
Minimal Encapsulation within IP, October 1996
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC2004
Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 2004
Abstract
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]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us