RFC 2003: IP Encapsulation within IP

This document specifies a method by which an IP datagram may be encapsulated (carried as payload) within an IP datagram. [STANDARDS-TRACK]

Read RFC 2003 on the RFC Editor

Outgoing relationships (9 related RFCs)

Informative reference — RFC 1191: Path MTU discovery
Informative reference — RFC 792: Internet Control Message Protocol
Informative reference — RFC 1812: Requirements for IP Version 4 Routers
Informative reference — RFC 1826: IP Authentication Header
Informative reference — RFC 2002: IP Mobility Support
Informative reference — RFC 1827: IP Encapsulating Security Payload (ESP)
Informative reference — RFC 1435: IESG Advice from Experience with Path MTU Discovery
Informative reference — RFC 1853: IP in IP Tunneling
Informative reference — RFC 1254: Gateway Congestion Control Survey

Incoming relationships (51 related RFCs)

Showing 50 of 51 related RFCs.

Updated by — RFC 3168: The Addition of Explicit Congestion Notification (ECN) to IP
Updated by, Normatively referenced by — RFC 6864: Updated Specification of the IPv4 ID Field
Normatively referenced by — RFC 6040: Tunnelling of Explicit Congestion Notification
Normatively referenced by — RFC 5944: IP Mobility Support for IPv4, Revised
Normatively referenced by — RFC 7637: NVGRE: Network Virtualization Using Generic Routing Encapsulation
Normatively referenced by — RFC 4459: MTU and Fragmentation Issues with In-the-Network Tunneling
Normatively referenced by — RFC 8926: Geneve: Generic Network Virtualization Encapsulation
Normatively referenced by — RFC 5512: The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute
Normatively referenced by — RFC 5565: Softwire Mesh Framework
Normatively referenced by — RFC 5845: Generic Routing Encapsulation (GRE) Key Option for Proxy Mobile IPv6
Normatively referenced by — RFC 6576: IP Performance Metrics (IPPM) Standard Advancement Testing
Normatively referenced by — RFC 3682: The Generalized TTL Security Mechanism (GTSM)
Normatively referenced by — RFC 5579: Transmission of IPv4 Packets over Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) Interfaces
Normatively referenced by — RFC 9634: Operations, Administration, and Maintenance (OAM) for Deterministic Networking (DetNet) with the IP Data Plane
Normatively referenced by — RFC 8350: Alternate Tunnel Encapsulation for Data Frames in Control and Provisioning of Wireless Access Points (CAPWAP)
Informatively referenced by — RFC 4301: Security Architecture for the Internet Protocol
Informatively referenced by — RFC 3775: Mobility Support in IPv6
Informatively referenced by — RFC 6275: Mobility Support in IPv6
Informatively referenced by — RFC 6513: Multicast in MPLS/BGP IP VPNs
Informatively referenced by — RFC 2002: IP Mobility Support
Informatively referenced by — RFC 2004: Minimal Encapsulation within IP
Informatively referenced by — RFC 3173: IP Payload Compression Protocol (IPComp)
Informatively referenced by — RFC 8900: IP Fragmentation Considered Fragile
Informatively referenced by — RFC 3024: Reverse Tunneling for Mobile IP, revised
Informatively referenced by — RFC 2393: IP Payload Compression Protocol (IPComp)
Informatively referenced by — RFC 4110: A Framework for Layer 3 Provider-Provisioned Virtual Private Networks (PPVPNs)
Informatively referenced by — RFC 4782: Quick-Start for TCP and IP
Informatively referenced by — RFC 2344: Reverse Tunneling for Mobile IP
Informatively referenced by — RFC 2356: Sun's SKIP Firewall Traversal for Mobile IP
Informatively referenced by — RFC 2395: IP Payload Compression Using LZS
Informatively referenced by — RFC 2764: A Framework for IP Based Virtual Private Networks
Informatively referenced by — RFC 4087: IP Tunnel MIB
Informatively referenced by — RFC 6077: Open Research Issues in Internet Congestion Control
Informatively referenced by — RFC 9181: A Common YANG Data Model for Layer 2 and Layer 3 VPNs
Informatively referenced by — RFC 5566: BGP IPsec Tunnel Encapsulation Attribute
Informatively referenced by — RFC 2005: Applicability Statement for IP Mobility Support
Informatively referenced by — RFC 4093: Problem Statement: Mobile IPv4 Traversal of Virtual Private Network (VPN) Gateways
Informatively referenced by — RFC 5320: The Subnetwork Encapsulation and Adaptation Layer (SEAL)
Informatively referenced by — RFC 5975: QSPEC Template for the Quality-of-Service NSIS Signaling Layer Protocol (NSLP)
Informatively referenced by — RFC 9833: A Common YANG Data Model for Attachment Circuits
Informatively referenced by — RFC 2896: Remote Network Monitoring MIB Protocol Identifier Macros
Informatively referenced by — RFC 5720: Routing and Addressing in Networks with Global Enterprise Recursion (RANGER)
Informatively referenced by — RFC 5979: NSIS Operation over IP Tunnels
Informatively referenced by — RFC 6981: A Framework for IP and MPLS Fast Reroute Using Not-Via Addresses
Informatively referenced by — RFC 9599: Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP
Informatively referenced by — RFC 2006: The Definitions of Managed Objects for IP Mobility Support using SMIv2
Informatively referenced by — RFC 4728: The Dynamic Source Routing Protocol (DSR) for Mobile Ad Hoc Networks for IPv4
Informatively referenced by — RFC 5058: Explicit Multicast (Xcast) Concepts and Options
Informatively referenced by — RFC 6252: A Framework of Media-Independent Pre-Authentication (MPA) for Inter-Domain Handover Optimization
Informatively referenced by — RFC 6312: Mobile Networks Considerations for IPv6 Deployment