> > > > Enabling HTTP on the nodes would really be a nice contribution. > However, I dont agree with using that for management. Reusability of > the tools that are already available for management, monitoring, and > configuration of IP networks is also something that we cannot neglect. > Moreover, SNMP is datagram oriented and also pretty lightweight if it > is coded well - it may fit 6LowPAN applications pretty well. >
SNMP definitely has the strong allure of network management. HTTP has the strong allure of information management. So perhaps the question is do we expect 6LoWPAN devices to speak multiple protocols? One of the very cool things about 6LoWPAN is that as IP it embraces multiple application level protocols. This is quite opposed to the various industry-vertical standards which try to solve the whole problem top-to-bottom in what mostly turns out as a monolith stack. However here is the rub - I don't think most 6LoWPAN devices really have the horse power to be running multiple protocols. Based on the technology we are using, I'm pretty sure that we will be required to pick one general purpose protocol and use it for most everything. My personal opinion is that the concerns of information management and integrating smart devices into the Web is the dominating criteria for selection of what that general protocol is. The industry will be looking to the IETF to see what the strategy is for application level protocols over 6LoWPAN. So whatever that strategy is, I think it is important to figure out how many and what protocols are expected to create interoperable 6LoWPAN devices.
_______________________________________________ 6lowpan mailing list [email protected] https://www.ietf.org/mailman/listinfo/6lowpan
