Most of requirements seem to be related to scenarios, not to specific mobility requirements.
Given the relevant scenarios and use cases, we can end up to any specific requirements. That's my sense since 6lowpan mobility is really peculiar issue in IETF due to its link characteristics.
Do you think handover-related signaling should be involved in 6lowpan devices (e.g., "full-function devices")? if so, reduction in handover-related signaling should be also considered as one of requirements. How about "reduced-function devices" ? So, do we need two different mobility mechanisms ?
I guess further study should take place in here. This document is trying to list up mobility concerns in terms of 6lowpan at this stage. Solution space will be forthcoming if folks interest occurs in this group.
> o A lowpan node in a isolated IEEE802.15.4 network that has no > connectivity outside itself, does not require to have global IPv6 > address configuration.If the routing of packets are performed at > the lowpan layer using M bit, then only link-local address > configuration is sufficient. Are routing protocols enough to support this scenario ?
What you mean by routing protocols ?
> o When a lowpan node moves from one personal area network(6lowpan) > to another, it should immediately inform the new PAN co-ordinator > about its presence. The PAN co-ordinator through its IPv6 router > should inform the previous IPv6 router about the new IPv6 address > of the new node that was present in the old-lowpan network. Thus > it is possible that the roaming node can still talk to its > corresponder at the old-lowpan network. Mapping from old address to new address is required ? In this case, handover-related signalling should be also involved in mobile devices ?
Well, addresses (I am saying both short address and long address) needs to be binded. Otherwise, those who want to initiate its talk to mobile device can't find out its changable location. So far, I don't have any idea whether we should design a new signaling for that or resue something optimized...
> o A inter-6lowpan gateway protocol is needed to comunicate the new > location (IPv6 global prefixes) of the roaming 6lowpan node which > moves across different 6lowpan networks I think if mobile lowpan nodes inform home network of its new address, this inter-6lowpan gateway protocol is not required.
It belongs to 6lowpan architectural issue. I know this group will start working on 6lowpan architecture. Let's see what architecture will stir up...
> o As with any network, the movement of a lowpan node may introduce > security threats in the old and new LowPan Networks. Thus, > authentication of mobile lowpan node is required when it updates > the movement information to the new and old IPv6 6lowpan routers. Do you mean Binding Update - like signals with IPsec funcions ?
Well, we'd like to focus on mobility requirements as well as feasible scenarios at this stage. Once spelling out those clearly, then we will go to details especially solution spaces if allowed. But, yes we should live up to those kinds of functions in IETF in my thought.
> o A 6lowpan network may be attached to a mobile network through a > IPv6 router. For example, in a vehicle, a few 6lowpan networks > are connected through some Wifi access points to the operator's > network or Internet. The vehicle transmits data to a central > location via Internet or operator's network. In this case, there > could be 2 scenarios - 1) the 6lowpan nodes are always inside the > vehicle and they are stationary. 2) the 6lowpan nodes move and > join/detatch different 6lowpan networks within the vehicle 3) A > 6lowpan network may step out of the vehicle and find a different > wireless access point to talk to the Internet. This is one of scenarios for MANEMO. I think many folks are interested in this scenario. (this is a kind of scenario, not requirement. move it to the sec 4.)
It will take place in manemo bof in Prague. I will speak about that in there. Please join us if you are of interest. Daniel Park _______________________________________________ 6lowpan mailing list [email protected] https://www1.ietf.org/mailman/listinfo/6lowpan
