| CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 17:47:49 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=o7d0KEKXaQi8h6b1r3KI1f_XwwuUbncGnQ7yOxDoDKI-1760204869-1.0.1.1-F7yMxrmGirg6w9OiW121YvjPNmMN.voTOtmtnL.SX_px4crlN94FtuUTonelGMP66E3i6p5e9bYCgMCywfnt5e_IAEIv68odGvjFQpukfZo; path=/; expires=Sat, 11-Oct-25 18:17:49 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98d02f4b9e0a165e-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