| C. Perkins, "Minimal Encapsulation within IP," Internet RFC 2004. |
....to B 1 . The packets going out on interface A 2 then get encapsulated in a new IP packet with an extra header having destination address B 1 and source address A 2 . The protocol field for the outer header should be IP in IP (also used for tunneling in the mobile IP standard and implementations [28, 29, 30, 31]) The destination, B, can then recognize IP in IP packets and strip the outer header. This leaves the original packet with proper source and destination addresses to be delivered up the network stack to TCP in a transparent manner. The TCP stack at B is unaware that A tunneled the packet through ....
....of the lower bandwidth path(s) Thus any added bandwidth utilization is available for free, meaning it is simply not realizable by the conventional single path TCP connection, in this sense the term overhead is a misnomer. In addition, the minimal encapsulation proposed in the mobile IP standard [30] along with header compression techniques can be employed as well to mitigate any IP in IP overhead. Now only the last question from above remains, the question of TCP performance. This is considered in detail in Section 4, however first a quantitative analysis of data splitting is presented. 3 ....
C. Perkins, Minimal Encapsulation within IP, October 1996.
....MobileIP, a problem which is especially acute when MobileIP reverse tunneling is employed. We evaluated existing encapsulation protocols, but were concerned with either their consumption of data space (IPIP [13] or GRE [5] or lack of flexibility and general applicability. Minimal Encapsulation [15] is an optimization to IP in IP encapsulation: instead of adding an entire envelope IP header to the encapsulated packet, it stores a single extra IP address (the original destination address of the tunneled packet) and 4 bytes of accounting overhead. The very low overhead (8 bytes per packet) of ....
C. Perkins. Minimal Encapsulation within IP. Request for Comments (Proposed Standard) RFC 2004.
....approach. 3.1 Mobile IP Mobile IP is probably the most widely known mobility management proposal. Its simplicity and scalability give it a growing success. Mobile IP is described in [2] a good review paper can be found in [31] Several extensions and enhancements are described in [28, 29, 35, 9]. Here, we discuss the principles of Mobile IP and ignore the differences between the IPv6 and IPv4 versions. To allow a mobile IP node to change its WIPPOA, Mobile IP defines two types of Mobility Agent (MA) the Home Agent (HA) and the Foreign Agent (FA) The HA is located inside the home ....
C. Perkins. Minimal Encapsulation within IP. Internet RFC, RFC
....saved by direct tunneling are small in comparison to the authentication and key distribution necessary to do it securely. 11 For detailed information about Mobile IP version 4, please consult these documents: RFC 2002 [1] which defines the Mobile IP protocol itself; RFC 2003 [2] 2004 [3], and 1701[4] which define three types of tunneling used in MIP; RFC 2005 [5] which describes the applicability of Mobile IP; and . RFC 2006, 6] which defines the Mobile IP Management Information Base (MIB) Draft ietf mobileip optim xx.txt for route optimization in Mobile IP 2.5 Mobile ....
C. Perkins "Minimal Encapsulation within IP", October 1996.
....compression is based on Jacobson s algorithm defined in different RFCs and is applied mainly for differential coding. The documents related to header compression concern the mechanisms and protocols developed in [5] which only concerns TCP IPv4 compression, the IP Header Compression developed in [8], which describes compression of multiple protocol headers, i.e. TCP or UDP (User Datagram Protocol) over IPv4 or IPv6, the Compression of RTP (Reliable Transfer Protocol) header developed in [7] and the minimal encapsulation within IP developed in [8] mainly for encapsulation of IP over IP for ....
.... the IP Header Compression developed in [8] which describes compression of multiple protocol headers, i.e. TCP or UDP (User Datagram Protocol) over IPv4 or IPv6, the Compression of RTP (Reliable Transfer Protocol) header developed in [7] and the minimal encapsulation within IP developed in [8] mainly for encapsulation of IP over IP for mobility purposes. It is worth noticing that the header compression is restricted to a number of applications and only useful in some specific cases. Fragmented packets cannot have their header compressed in most of their figures. SYN, FIN or RST TCP ....
C. Perkins, Minimal Encapsulation within IP, RFC 2004.
No context found.
Perkins, C., "Minimal Encapsulation within IP", RFC 2004.
No context found.
Perkins, C., "Minimal Encapsulation within IP", RFC 2004.
No context found.
Perkins C., "Minimal Encapsulation within IP", RFC 2004.
No context found.
Perkins, C., "Minimal Encapsulation within IP", RFC 2004.
No context found.
Perkins, C., "Minimal Encapsulation within IP", RFC 2004.
No context found.
Perkins, C., "Minimal Encapsulation within IP", RFC 2004.
No context found.
C. Perkins, "Minimal Encapsulation within IP," Internet RFC 2004.
No context found.
C. Perkins, "Minimal Encapsulation within IP," Internet RFC 2004.
No context found.
Perkins, C., Editor, "Minimal Encapsulation within IP", RFC 2004, October 1994. 9. Author's Address Questions about this memo can be directed to:
No context found.
C. Perkins. Minimal Encapsulation within IP. Internet Engineering Task Force, RFC 2004.
No context found.
C. Perkins, "Minimal Encapsulation within IP," Internet RFC, RFC 2004.
No context found.
C. Perkins, `Minimal Encapsulation within IP', RFC 2004.
No context found.
Perkins, C., "Minimal Encapsulation within IP", RFC 2004.
No context found.
C. Perkins. Minimal encapsulation within IP. RFC
No context found.
Perkins, C., "Minimal Encapsulation within IP", RFC 2004, October 1996.
No context found.
C. Perkins, "Minimal Encapsulation within IP," IETF RFC 2004, Oct. 1996.
No context found.
Perkins, C., "Minimal Encapsulation within IP", RFC 2004, October 1996.
No context found.
Perkins, C., "Minimal Encapsulation within IP", RFC 2004, October 1996.
No context found.
Perkins, C., "Minimal Encapsulation within IP", RFC 2004.
No context found.
C. Perkins, "Minimal Encapsulation within IP," RFC 2004.
First 50 documents
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC