On 4/19/06, Philip Levis <[EMAIL PROTECTED]> wrote:
If you take the IPv6 over 15.4 route (no pun intended), under the
assumption of low-power embedded devices, I'd argue that it's not the
data plane that changes, but rather the control plane. E.g., many
existing IP routing approaches become problematic, predominantly due
to the fact that the assume any-to-any connectivity as an end goal,
Agree that IPv6 routing may be redundant in 802.15.4 network.
The format document suggests alternative routing (Mesh) at L2.
Thus, in practice, IPv6 would be useful for addressing, auto-configuration
, device management and running applications while routing within the
PAN takes place at the L2 layer. From IPv6 perspective, a PAN is a
L3 subnet. However, the IPv6 router at the 6lowPAN junction is responsible
for routing a packet to the Internet if the destination address suggests so;
here the IPv6 6lowPan router acts as a default gateway.
while in PANs this is less commonly the case. I think this gets to
the point raised earlier, of whether the group considers 802.15.4
networks being used as transmit networks, which is a very very
important consideration.
Good point. As mentioned earlier, 802.15.4 L2 layer can be used for
data routing within the PAN.
Coming from the world of TinyOS and sensor networks, I'd argue that
it's pretty clear that a set of protocols and mechanisms enabling IP
devices to directly communicate with PAN devices would be very useful
(why I'm here). The most common case for this is management, as it's
a situation where a user definitely wants to talk to a specific
*node*, i.e., an address, rather than use some other naming scheme
(e.g., "the lights in the living room"). The advantage that a direct
IP-level protocol transcoder would provide is that it would preclude
the need for application-level protocol stacks to even communicate
with nodes within a network. Furthermore, you can begin to use all of
the basic IP tricks and techniques when managing these networks
(e.g., firewalls).
Agree.
That being said, if the plan is not to push IPv6 into the PAN, then
this raises the simple question of what L3 protocols will run within
the PAN.
By L3 protocols do you mean any routing protocols? Other than that,
format doc already talks about running UDP, at the last interim folks brought up
needs for running a simple TCP stack as well for running different existing
apps. I'd think it really depends what sort of applications folks will run
on top of 802.15.4 networks? There might be devices other than sensors, which
will run 802.15.4 radio for a different type of applications where node-to-node
communications might be necessary. Any ideas?
Thanks,
-Samita
http://csl.stanford.edu/~pal
_______________________________________________
6lowpan mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/6lowpan
_______________________________________________ 6lowpan mailing list [email protected] https://www1.ietf.org/mailman/listinfo/6lowpan
