24-12-2012, 05:42 PM
Mobility Support in IPv6
Mobility Support in IPv6.pdf (Size: 2.03 MB / Downloads: 334)
Why Mobile IPv6? -- Propellant factors.
• Huge growth of mobile Internet terminals will exhaust IPv4 address space
– All wireless terminals will have WAP and GPRS
• IPv6 brings enough IP addresses
• Ease of scalability
– Supporting billions of new devices and huge amounts of new bandwidth
– Simplified, cost-efficient architecture without NATs , Proxies, ALGs,...
• Always-on connection establishes a variety of new services.
– Push, location-based, etc.
• Integrated Security
• Efficiency: IPv6 improves efficiency in a number of areas.
– Routing, Broadcast handling
• Quality of Service improvements
– Fragmentation, Flows
• Mobility Across Access Technologies
Text Representation of IPv6 Address
“Preferred” form: 1080:0:FF:0:8:800:200C:417A
Compressed form: FF01:0:0:0:0:0:0:43 becomes FF01::43
IPv4-compatible: 0:0:0:0:0:0:13.1.68.3 or ::13.1.68.3
There is no broadcast addresses, only multicast.
Loopback address is ::1
Binding Update Option Header Format
A Bit : Indicates whether receiver should reply
or not with Binding Acknowledgement.
H Bit: Use when mobile node wants the
receiving node to act a Home Agent.
L Bit: Set if the mobile node want to receive
packet destined to its link-local address.
Lifetime: Lease time for the address.
Identification Field: Counter is use to insure
Binding Updates are order-wise. Counter
increment for each new BU ( not for
retransmission) .
Care-of Address: current address of MN.
When care-of address = Home address.
Destination Cache entries should be
deleted.