1 / 7

IETF#88 Mobility API for DMM

IETF#88 Mobility API for DMM. draft-liu-dmm-mobility-api-00 Dapeng Liu , Hui Deng, Charlie Perkins. Background-RFC5014.

kelli
Download Presentation

IETF#88 Mobility API for DMM

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. IETF#88Mobility API for DMM draft-liu-dmm-mobility-api-00 Dapeng Liu, HuiDeng,Charlie Perkins

  2. Background-RFC5014 • RFC 5014 defines socket API extension used for source address selection. Application can use this API to override the default source address selection mechanism for IPv6. • Currently, RFC 5014 defines the following type of source address selection preference: • IPV6_PREFER_SRC_HOME /* Prefer Home address as source */ • IPV6_PREFER_SRC_COA /* Prefer Care-of address as source */ • IPV6_PREFER_SRC_TMP /* Prefer Temporary address as source */ • IPV6_PREFER_SRC_PUBLIC /* Prefer Public address as source */ • IPV6_PREFER_SRC_CGA /* Prefer CGA address as source */ • IPV6_PREFER_SRC_NONCGA /* Prefer a non-CGA address as source */

  3. Problem • In DMM scenario, applications on the MN need to select the proper IP address based on the prefix type • RFC5014 need to be extended to allow MN in DMM scenario select source address

  4. New extensions of RFC5014 • IPV6_PREFER_SRC_LOCAL_HNP: • Prefer to use locally allocated home network prefix. • IPV6_PREFER_SRC_REMOTE_HNP: • Prefer to use the home network prefix that allocated by other access router instead of the one that the MN currently attach.

  5. Usage example • In appropriate DMM scenarios, the application on the mobile node can always select the IPV6_PREFER_SRC_LOCAL_HNP as the most preferred source address. • The mobile node's operating system must guarantee that the on-going session will not be interrupted even if a new prefix is available.

  6. Implementation example • [I-D.ietf-6man-rfc3484bis] document indicates possible implementation strategies for getaddrinfo(). • The address selection hint flags for the getaddrinfo() specified in this document extend the 'intai_eflags' field in the structaddrinfo [RFC5014]. • The IPV6 source address preference values (IPV6_PREFER_SRC_HNP and IPV6_PREFER_SRC_HNP_TMP) defined for the IPV6_ADDR_PREFERENCES socket option are also defined as address selection preference flags in <netdb.h> header for the "ai_eflags" extended flag-set field of the addrinfo data structure. • Corresponding extensions can be done for mobility address selection.

  7. Q&A

More Related