1 / 8

On Demand Mobility Management

This draft outlines solutions for managing on-demand mobility in networks, allowing mobile nodes to choose between care-of addresses and home addresses based on application needs. Key requirements include bypassable network-layer mobility support and enhanced IPv6 socket APIs for address selection. The proposal introduces new IPv6_ADDR_PREFERENCES flags for fixed, sustained, and nomadic IP addresses, enabling applications to request configurations only when needed. This dynamic approach optimizes resource use while ensuring necessary address types are available for varied application scenarios.

kasie
Télécharger la présentation

On Demand Mobility Management

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. On DemandMobility Management draft-yegin-dmm-ondemand-mobility-02 Alper Yegin, Kisuk Kweon, Jinsung Lee, Jungshin Park Samsung Electronics IETF 90

  2. On Demand New charter: “… define solutions that allow, for example, mobile nodes to select either a care-of address or a home address depending on an application' mobility needs. “ Requirements: “REQ2: Bypassable network-layer mobility support for each application session”

  3. Types of IP Addresses(withrespectto IP-layermobilitymanagement)

  4. RFC 5014 • “IPv6 Socket API for Source Address Selection” • Defines IPV6_ADDR_PREFERENCES socket flags to influence source address selection • IPV6_PREFER_SRC_HOME • IPV6_PREFER_SRC_COA

  5. RFC 5014 – Not sufficient for DMM • Home vs. CoA distinction not sufficient to capture 3 different types of IP addresses • Selectsamongavailableaddresses, but on-demandconfiguration is neededtoo • Example use: Don’t automatically configure the rarely-used Fixed IP Address until it’s requested by an app. • Indication of “Prefer(ence)” is not sufficient, we need “require(ment)”

  6. Solution • New IPV6_ADDR_PREFERENCES flags • IPV6_REQ_FIXED_IP • IPV6_REQ_SUSTAINED_IP • IPV6_REQ_NOMADIC_IP • Works with RFC 5014 framework • If the requested type IP address is not already configured, then the IP stack attempts to dynamically configure one

  7. Questions and comments?

  8. Policy • Following are policy matters: • The type of IP addresses configured on the host at the boot time. • Permission to grant various types of IP addresses to a requesting application. • Determination of a default address type when an application does not use the API.

More Related