1 / 6

Flow Bindings in MIPv6 and NEMO

Learn about flow bindings in MIPv6 and NEMO, which enable optimal utilization of available interfaces and efficient flow management. Understand how flow identification options and modular formats enhance flow control. This draft also addresses issues related to field alignment, prefixes, port number ranges, and prioritization.

sutterfield
Download Presentation

Flow Bindings in MIPv6 and NEMO

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. Flow bindings in MIPv6 and NEMOdraft-soliman-monami-flow-binding-01

  2. Why is Flow binding needed? • Applications may run more efficiently on one access technology than others (e.g. VoIP needs QoS capabilities in the radio access, FTP doesn’t). • Different access technologies may be available through different IP subnets => different interfaces on a host. • MIPv6 does not allow a MN to allocate different CoAs to different flows. • Flow bindings allow the MN to associate flows to different CoAs for optimal utilisation of available interfaces. • Flow bindings as MIPv6 extensions allow the MN to split flows from HA/CN/MAP, for flows initiated or terminated by MN. • Flow bindings in MIPv6 are independent of application capability (i.e. whether session control is present or not).

  3. Included in BU and BA messages Modular format Flow Identification Option

  4. Flow identification option • Add/modify/remove flows • Must identify a default address • Allows for more forwarding policies to be added in future • Allows for addresses/prefixes => Support for MRs • Support for IPv4 addresses (DSMIP) • BW efficient, flow description is only sent once, index FID only is needed afterwards. • The entire option is not needed to describe a flow

  5. Issues addressed in this revision • Better alignment for fields in the option • Allow for prefixes • Allow for port number ranges • Added priorities to allow for overlaps between flows. • Increased the range for default addresses to allow for a prioritised list of default addresses. • Clarifications all over the draft.

  6. WG item?

More Related