1 / 8

Overlapping IPv4 Address Assignment Support for Dual-stack Mobile IPv6 Sri Gundavelli

Overlapping IPv4 Address Assignment Support for Dual-stack Mobile IPv6 Sri Gundavelli Julien Laganier Hidetoshi Yokota Carl Williams. draft-gundavelli-mext-dsmip-ipv4-overlap-01.txt. 1. 1. 1.

yeva
Download Presentation

Overlapping IPv4 Address Assignment Support for Dual-stack Mobile IPv6 Sri Gundavelli

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. Overlapping IPv4 Address Assignment Support for Dual-stack Mobile IPv6 Sri Gundavelli Julien Laganier Hidetoshi Yokota Carl Williams draft-gundavelli-mext-dsmip-ipv4-overlap-01.txt 1 1 1 IETF 79: MEXT Working Group – Overlapping IPv4 Address Assignment Support for Dual-stack Mobile IPv6

  2. Motivation • IPv4 address assignment support for Mobile IPv6 is specified in Dual-stack Mobile IPv6 (RFC-5555). However, DSMIPv6 does not have explicit support for allocating overlapping IPv4 addresses to the mobile nodes that it is serving. • There are number deployment scenarios where there is a need for a home agent to allocate a private IPv4 address from the same overlapping private IPv4 address block to multiple mobile nodes. - Service Provider Hosted Enterprise Home Agent Deployment Model - 3GPP System Architecture, a Home Agent supporting multiple Packet Data Networks - Support for IPv4 Transitioning Solutions (as specified in 3GPP TR 23.975, Ex: Per-Interface NAT Bindings, or GI DS-Lite)

  3. Use Case: Hosted Home Agent Service • In service provider hosted home agent deployment models, two mobile nodes from different enterprises may have to be assigned IPv4 addresses from the same overlapping address space. 203.0.113.9 MN-A@Ent-A.com 203.0.113.0/24 Ent-A DSMIP Tunnel HA 203.0.113.0/24 DSMIP Tunnel Ent-B 203.0.113.9 MN-B@Ent-B.com

  4. Use Case: Multiple Packet Data Networks • In 3GPP system architecture, a single home agent serves multiple packet data networks that uses overlapping private address space. In this case, two mobile nodes attached to each of these packet data networks may have to be assigned overlapping IPv4 addresses. 203.0.113.9 APN-1 203.0.113.0/24 APN-A DSMIP Tunnel PGW 203.0.113.0/24 DSMIP Tunnel APN-B 203.0.113.9 APN-2

  5. Use Case: Per-Interface NAT Bindings • In this scenario, the home agent supports Per-Interface NAT Bindings as specified in [draft-arkko-dual-stack-extra-lite]. The CGN is collocated with the home agent, and each the mobile node NAT binding entries have the interface identifier of the DSMIPv6 tunnel, established between the mobile node and the home agent. The home agent uses the interface identifier for making packet forwarding decisions. 203.0.113.9 Tunnel-0 DSMIP Tunnel CGN HA internet DSMIP Tunnel Tunnel-1 203.0.113.9

  6. Use Case: Gateway Initiated DS Lite • In this scenario, the home agent has support for the Gateway Initiated Dual-stack lite solution, specified in [draft-softwire-gateway-init-ds-lite]. There is typically a GRE tunnel between the CGN and the home agent. Every IPv4 packet tunneled between the CGN and the home agent carries a context identifier in the GRE Key header unique to the mobile node. 203.0.113.9 Tunnel-0 DSMIP Tunnel CGN HA internet DSMIP Tunnel Tunnel-1 203.0.113.9

  7. Protocol Considerations • No new extensions to protocol messages are needed. The changes are primarily to the IPv4 address assignment procedures with respect to allocating addresses from an overlapping IPv4 address space. • There are additional considerations related to IPv4 route setup and packet forwarding. The home agent needs to follow additional considerations. • Extension to the Binding Cache entry conceptual data structure for including additional parameter (Overlapping IPv4 Context Id) with respect to supporting this capability • Additional Protocol Configuration options for enabling/disabling this feature and the specific scenario

  8. Questions ?

More Related