1 / 9

Prefix Delegation for Proxy Mobile IPv6

Prefix Delegation for Proxy Mobile IPv6. draft-zhou-netext-pd-pmip Xingyue Zhou Jouni Korhonen Carl Williams. What is the problem?. There is a gap currently for supporting NEMO [RFC3963] and generally DHCPv6-PD in PMIPv6 architecture.

ozzie
Download Presentation

Prefix Delegation for Proxy Mobile IPv6

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Prefix Delegation for Proxy Mobile IPv6 draft-zhou-netext-pd-pmip Xingyue Zhou Jouni Korhonen Carl Williams

  2. What is the problem? • There is a gap currently for supporting NEMO [RFC3963] and generally DHCPv6-PD in PMIPv6 architecture. • In Proxy Mobile IPv6, the prefix that is assigned to a mobile node is hosted on the access link shared between the mobile node and the MAG. These prefixes are not delegated prefixes. /64 HNP /64 MN MAG … Not delegated prefix /64 Not specified..

  3. What is the problem?

  4. Approach for solving the problem • For supporting a deployment where the mobile node is a mobile router, we need to be able to allow the hosts behind the mobile node to obtain address configuration • The right model is to make this a routed network with the mobile node as the mobile router and by allowing DHCP-PD. This model was already adopted for client-based mobility  (RFC-6276, RFC-3963) and is also specified in 3GPP Rel-10 for GTP (TS 29.061).

  5. Approach for solving the problem • Key point: delegated prefix(es) need to be associated with PMIPv6 binding and forwarding state: • Extend or clarify Proxy Mobile IPv6 signaling to make the association in case of prefix delegation.

  6. Approach to solving the problem (one signaling example, there are others)

  7. Next Step: Adopt • NETEXT is expected to make an consensus to address this problem. • Adopt as a Working Group document.

  8. BACKUP SLIDE

  9. Extension in the handover procedure • After a handover the new target MAG has to be aware of the delegated prefix, not only the HNP. Otherwise, the forwarding to and from MN fails: • The target MAG may know the delegated prefix “out of band”. In this case the forwarding in the target MAG is up to date and the MAG informs the LMA about this by including the delegated prefix in lifetime extending PBU (after a handover). • Otherwise, the LMA is responsible to notify the target MAG of the previously assigned mobile network prefix in the PBA sent as a response to lifetime extending PBU.

More Related