<?xml version='1.0'?>

<reference anchor='RFC2004'>

<front>
<title abbrev='Minimal Encapsulation for IP'>Minimal Encapsulation within IP</title>
<author initials='C.' surname='Perkins' fullname='Charles Perkins'>
<organization>Room H3-D34</organization>
<address>
<postal>
<street>T. J. Watson Research Center</street>
<street>IBM Corporation</street>
<street>30 Saw Mill River Rd.</street>
<street>Hawthorne</street>
<street>NY  10532</street></postal>
<facsimile>+1-914-784-6205</facsimile>
<email>perk@watson.ibm.com</email></address></author>
<date month='October' year='1996' />
<area>Internet</area>
<keyword>encapsulate</keyword>
<keyword>mobile ip</keyword>
<keyword>routing</keyword>
<keyword>wireless</keyword>
<abstract>
<t>
   This document specifies a method by which an IP datagram may be
   encapsulated (carried as payload) within an IP datagram, with less
   overhead than &quot;conventional&quot; IP encapsulation that adds a second IP
   header to each encapsulated datagram.  Encapsulation is suggested as
   a means to alter the normal IP routing for datagrams, by delivering
   them to an intermediate destination that would otherwise not be
   selected by the (network part of the) IP Destination Address field in
   the original IP header.  Encapsulation may be serve a variety of
   purposes, such as delivery of a datagram to a mobile node using
   Mobile IP.
</t></abstract></front>

<seriesInfo name='RFC' value='2004' />
<format type='HTML' octets='25587' target='http://xml.resource.org/public/rfc/html/rfc2004.html' />
<format type='XML' octets='13915' target='http://xml.resource.org/public/rfc/xml/rfc2004.xml' />
</reference>
