IPv 4 Support for Proxy Mobile IPv 6
IPv 4 Support for Proxy Mobile IPv 6 Ryuji Wakikawa (Keio U) Sri Gundavelli (Cisco) IETF 71 th NETLMM WG
Updates (plan) l l l Changes to signaling flow related to IPv 4 Home Address management Default Router Address option and related changes Clarifications on IPv 4 private addressing support MTU considerations based on the Transport AD review of the base Proxy Mobile IPv 6 specification Inter-Media Handover
IPv 4 Home Address Management l LMA always manages the IPv 4 home address pool. l l MAG is required to complete PMIP signaling before the DHCP signaling is allowed. When MAG is a DHCP server l l When MAG is a DHCP relay l l MAG assigns the address to the MN by sending DHCP reply MAG inserts the assigned IPv 4 Ho. A as a subnet hint in the relayed DHCP messages. Why? l l If DHCP manages the address pool, LMA needs some interaction with a DHCP server to verify the IPv 4 Ho. A requested in PBU. This interaction is not specified today. There is no guarantee that the DHCP server might change the assigned Ho. A during active PMIP session. LMA should handle the address management on behalf of DHCP server.
Default Router Address l l l An MN needs an IPv 4 default-router address. LMA manages the address pools and each pool has an associated default-router address. After receiving a PBU with 0. 0 set in the IPv 4 home address option, LMA sends an assigned IPv 4 home address and the corresponding default-router address in the PBA. l New Default Router’s option defined.
NAT Consideration l l When IPv 4 private addressing is in use, the operator should ensure there is no overlap of this address space with the private addresses used by MAG’s operating behind NAT. When a MAG configures with a private address, it MUST NOT enable direct local routing.
MTU Consideration l l l Based on the transport network and the negotiated encapsulation modes between the LMA and MAG, the PMTU between the LMA and the attached MAG may be different. The MN may not always trigger DHCP procedure after a handoff and hence the new MTU can not be delivered to the mobile node. The operator SHOULD calculate the least MTU of all the managed access link in the same PMIP domain and all the possible tunneling types. l l They SHOULD configure the least MTU to the DHCP server provides the least MTU to mobile nodes during the address assignment.
Inter-Media Handover l l Added Multi-homing considerations to comply with the changes in the base PMIPv 6 specification. Defined LMA processing rules for handing multihoming scenarios
- Slides: 7