IP Encapsulation within IP
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 14
- Abstract
- This document specifies a method by which an IP datagram may be encapsulated (carried as payload) within an IP datagram. [STANDARDS-TRACK]
- Publication Date
- 1996-10-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC2003- Link
- https://doi.org/10.17487/RFC2003
- Author(s)
- Charles E. Perkins
- Keyword(s)
- IPENCAPIP, IP
Latest version of IETF RFC 2003
Document Versions — IETF RFC 2003
-
▶ IETF RFC 2003 (1996-10-01)THIS DOC [ACTIVE] [LATEST VERSION]
Bibliographic Reference(s)
- Gilligan, R., Nordmark, E., and B. Hinden, "IPAE: The SIPP Interoperability and Transition Mechanism", Work in Progress. EXTERNAL
- IETF RFC 791 [Active*]
- IETF RFC 792 [Active*]
- IETF RFC 1191 [Active*]
- IETF RFC 1254 [Active*]
- IETF RFC 1435 [Active*]
- IETF RFC 1812 [Active*]
- IETF RFC 1826 [Superseded*]
- IETF RFC 1827 [Superseded*]
- IETF RFC 1853 [Active*]
- IETF RFC 2002 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC2003.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 2003, IP Encapsulation within IP. Available at https://doi.org/10.17487/RFC2003
Snippet:
IETF RFC 2003, IP Encapsulation within IP. Available at https://doi.org/10.17487/RFC2003
HTML (ISO 690 compliant)
Preview:
IETF RFC 2003, IP Encapsulation within IP. Available at https://doi.org/10.17487/RFC2003
Snippet:
<span class="citation"><cite>IETF RFC 2003</cite>, IP Encapsulation within IP. Available at <a href="https://doi.org/10.17487/RFC2003" target="_blank" rel="noopener">https://doi.org/10.17487/RFC2003</a></span>
SMPTE's HTML Pub
Preview:
Snippet:
<li> <cite id="bib-rfc2003">IETF RFC 2003</cite>, IP Encapsulation within IP <span class="doi">10.17487/RFC2003</span> </li>
Referenced By
- IETF RFC 2002 [Superseded*]
- IETF RFC 2004 [Active*]
- IETF RFC 2005 [Active*]
- IETF RFC 2006 [Active*]
- IETF RFC 2201 [Active*]
- IETF RFC 2344 [Superseded*]
- IETF RFC 2356 [Active*]
- IETF RFC 2393 [Superseded*]
- IETF RFC 2395 [Active*]
- IETF RFC 2667 [Superseded*]
- IETF RFC 2746 [Active*]
- IETF RFC 2757 [Active*]
- IETF RFC 2764 [Active*]
- IETF RFC 2868 [Active*]
- IETF RFC 2977 [Active*]
- IETF RFC 2983 [Active*]
- IETF RFC 3024 [Active*]
- IETF RFC 3168 [Active*]
- IETF RFC 3173 [Active*]
- IETF RFC 3220 [Superseded*]
- IETF RFC 3252 [Active*]
- IETF RFC 3344 [Superseded*]
- IETF RFC 3682 [Superseded*]
- IETF RFC 3775 [Superseded*]
- IETF RFC 3884 [Active*]
- IETF RFC 4110 [Active*]
- IETF RFC 4301 [Active, Amended*]
- IETF RFC 6040 [Active*]
- IETF RFC 6275 [Active*]