On Mar 16 2007, at 01:36, Dominik Kaspar wrote:

RFD nodes should not have to detect their own movement. Their movement should *be detected* by more capable devices

RFD nodes, if relying on that, don't want to fall into the hands of the "more capable devices" of the adversary. So they at least may have to be able to find out whether they are still (or newly) connected to a friendly FFD or in one of the two (not necessarily distinguishable) states "isolated" or "surrounded by adversaries only". We probably need the scenarios fleshed out with some more details before we can see which role(s) calls for RFDs and in which way these particular roles are "mobile" with respect to their FFD friends.

On Mar 19 2007, at 09:22, Samita Chakrabarti wrote:

Currently our architecture ( as discussed in the
wg so far) is
hierarchical with bunch FFDs and RFDs hanging off of FFDs and there is one
IPv6 router at the top ( please see the 6lowpan-ipv6-nd draft for that
assumption).

(Putting WG chair hat on:)
This is correct.
We just have to be careful not to refer to this mental model as "the 6lowpan architecture", as we the WG haven't agreed on one yet.
(Hat off again:)
I personally think this structure would be good as one, but not necessarily the only structure supported by the 6lowpan protocols. But we aren't there yet: As we said during the meeting, we need to understand a reasonable set of 6lowpan scenarios and the (qualitative and quantitative) workloads generated by them. And then we need to work on those we want to support, together with the structural models ("architectures") that will be used to support them.

So, if you want to continue this discussion, please be concrete (as in "I have this airport with several 100 m of hallways that have RFD temp sensors that are each within 8 m of FFD light controllers spaced 12 m apart and a maintenance guy with a set of mutually connected FFD maintenance devices roaming in these hallways").

Gruesse, Carsten


_______________________________________________
6lowpan mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/6lowpan

Reply via email to