[Monami6] MIPv4 based flow movement

Hi,

We have published a draft providing a solution for per flow movement in
the context of MIPv4. The proposal provides equivalent functionality to
the draft-ietf-monami6-multiplecoa-00 and
draft-soliman-monami6-flow-binding-01.txt but the design in based on
extensions to MIPv4 instead of MIPv6.

The draft defines Alternate-CoA and Flow Identification extensions. The
later supports IPv4 and IPv6 filters and it is compatible to related
NEMOv4 and DSMIPv4 work.

You can find the draft at:
http://www.ietf.org/internet-drafts/draft-tsirtsis-mip4-flowmove-00.txt

To limit cross-posting I would suggest that if you have comments related
to the concepts of multiple CoA and per flow movement, you should post
them to Monami6 list. If you have comments on the details of how the
proposal works over MIPv4 you should send them to the MIP4 list.

Regards
George

P.S.: Abstract

   Mobile IPv4 allows Mobile Nodes (MN) to create mobility bindings
   between their Home Address (HoA) and their current Care-of Address
   (CoA) in a Home Agent (HA) so that the HA can redirect traffic for
   the MN to its current location.  This draft extends MIPv4 so that the
   binding granularity is on a per flow basis.  Extensions are defined
   to allow the registration of multiple CoAs and the definition of
   individual flows.  Individual flows can then be pointed to the
   registered CoAs.

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6