Optimized Mobile IPv4 UDP Encapsulation draft-vaarala-mip4-optudp-00.txt Farid Adrangi Sami Vaarala

Motivation / Purpose Minimize MIPv4 data packet overhead when –UDP encapsulation [RFC-3519] is used –Most of Mobile node’s data traffic is destined to one particular CN Applicability –MIP/VPN or basic IPsec-over-MIPv4 –VoIP over MIP Specify an extension to be used in conjunction with RFC-3519 to enable the overhead optimization

Solution Overview RRQ { Optimized UDP Tunnel Request Extension: Preferred-CN : a.b.c.d UDP Tunnel Request Extension (RFC 3519) Flags: F= R= } RRP { Optimized UDP Tunnel Reply Extension: Accept/Reject Indication UDP Tunnel Request Extension (RFC 3519) Flags: F= R= } UPD tunneled Data Packets (RFC 3519) { UPD Tunnel Request Extension: (RFC 3519) O-Flag=1 } MN HA

Solution Details (1) New extensions to request and acknowledge optimized UDP encapsulation for a “preferred” CN selected by MN A new state: “Preferred” CN, in Mobility Binding A new flag in MIP Tunnel Data Message header [RFC-3519] indicating optimized UDP encapsulation in use Inner IP header eliminated, reconstructed by HA and MN –20 bytes optimized from baseline [RFC-3519] encaps. –NOTE: Unoptimized packets are processed normally

Solution Details (2) Outbound Packet Processing (from MN to HA) 1.Receive form stack IP1 ! TCP ! data 2.Check Preconditions 3.Strip header TCP ! data 4.Encapsulate IP2 ! UDP ! MIP-TD (next=TCP, O=1) ! TCP ! data 5.Send to network Unoptimized: (CoA->HA) ! (UDP) ! (UDP Tunnel Header) ! (MN- >CN) ! Payload Optimized: (CoA->HA) ! (UDP) ! (UDP Tunnel Header) ! Payload

Solution Details (3) Inbound Packet Processing 1.Receive from network IP2 ! UDP ! MIP-TD (next=TCP, O=1) ! TCP ! data 2. Check precondition 3.(De)capsulate TCP ! Data 4. Reconstruct IP1 ! TCP ! Data 5.Send to stack Unoptimized: (HA->CoA) ! UDP ! UDP Tunnel Header ! CN->MN ! Payload Optimized: (HA->CoA) ! UDP ! UDP Tunnel Header ! Payload

Proposed WG Action Standardize as a stand-alone extension; or Include it in a revised RFC-3519