Re: [MEXT] Discussion proposal on network-initiated flow binding forMIPv6

Hi Hidetoshi,

Sorry for the late answer, but this long delay does not mean a lack of interest for network-initiated flow binding :-)

Actually, I think we should consider the case where mobility triggers may come from the network, especially in multiple interfaces use-case you are referring to. For instance, the handover could be triggered when the network changes its inter-system handover policy, or when the network detects, or anticipates, network load issues. Note that we are talking only about mobility initiation here; I mean that this model should not preclude the terminal to make the final decision, e.g. considering quality of the radio link.

Then, "network initiated mobility" does not mean "mobility is always initiated by the network"... Obviously, if the terminal looses an interface, the terminal will initiate the mobility whithout waiting for a network trigger....  Actually, I'd say that a complete mobility management process should include both network and terminal initiated mobility, depending on the type of trigger.

This discussion should not be restricted to MIP. PMIP is network-based execution protocols, so it can be awkward not having also a network-based initiation model with PMIP. 

Pierrick  

> -----Message d'origine-----
> De : mext-bounces@ietf.org [mailto:mext-bounces@ietf.org] De 
> la part de Hidetoshi Yokota
> Envoyé : lundi 13 juin 2011 02:36
> À : mext@ietf.org
> Objet : [MEXT] Discussion proposal on network-initiated flow 
> binding forMIPv6
> 
> Hi all,
> 
> A while back, there was a discussion on network-initiated 
> flow binding, whereby the home agent indicates the mobile 
> node to move flows between access networks. At that time, the 
> discussion didn't get enough momentum partly due to lack of a 
> convincing use case. Nowadays, it is rather common for a 
> smartphone to have multiple interfaces pumping a lot of 
> packets into the network. Data traffic offload is becoming a 
> serious issue for mobile operators worldwide. The 
> host-initiated flow binding provided by RFC6089 is a big step 
> to realize fine-grained data traffic offload. And for the 
> next step, it may be a way forward for the network to be able 
> to trigger flow mobility since the network knows more about 
> its conditions and interworks with the policy server or 
> application servers.
> 
> I would therefore like to revitalize the discussion on the 
> network-initiated flow binding for MIPv6. The following I-D, 
> which was once discussed in the past meetings, could be good 
> for restarting the
> discussion:
> 
> "Home Agent Initiated Flow Binding for Mobile IPv6"
> <draft-xia-mext-ha-init-flow-binding>
> http://tools.ietf.org/id/draft-xia-mext-ha-init-flow-binding-05.txt
> 
> In NetExt WG, there is a similar discussion going for PMIPv6, 
> which includes network-initiated flow mobility. As a side 
> note, a related item is being discussed in 3GPP and the 
> discussion in IETF will certainly help them make their way.
> 
> I would appreciate your opinion and hopefully your interest.
> 
> Regards,
> --
> Hidetoshi
> 
> _______________________________________________
> MEXT mailing list
> MEXT@ietf.org
> https://www.ietf.org/mailman/listinfo/mext
> 