| CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 06:55:48 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=ATDofRnACdtbYhkTAZwWdVy7lAbS565UoRK7ZD373ag-1760079348-1.0.1.1-IcAaEETJrSFIfwWW1NwxttaQ.tgByqQwmo9FctFSmTm9EO7Rtglk.Tbdg2em2fG76h5Qqn_ecfj.Nqtj.4il.iNBF.SFZ79Vgjw1J5s5cQI; path=/; expires=Fri, 10-Oct-25 07:25:48 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c436ced95f3585-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 2003 » RFC Editor
Search RFCs
RFC 2003
IP Encapsulation within IP, October 1996
- File formats:
- Status:
- PROPOSED STANDARD
- Updated by:
- RFC 3168, RFC 6864
- Author:
- C. Perkins
- Stream:
- IETF
- Source:
- mobileip (int)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC2003
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 2003
Abstract
This document specifies a method by which an IP datagram may be encapsulated (carried as payload) within an IP 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