[6lowapp] HTTP and SIP

[Shidan <[e-mail]>]

I'm going through the 6LoWAPP problem statement:

"request-response protocols like HTTP may require battery-operated, mostly
sleeping nodes to be listening for requests much more frequently than their
application processing requirements alone would need them to wake up."

"In addition, some of the applications may require optimizations in terms of
bandwidth usage; for example, the usual data formats (both headers and body)
are perceived to be too chatty for the 50-60 byte payloads possible in
LoWPANs.  Their interpretation and generation may require too much code for
the 8-bit and 16-bit processors dominating LoWPAN nodes."


None of these points seem evident to me. We are in co-operation with two
multinationals and faculty at Columbia University implementing,
unadulterated SIP for smart meter PLC communications and I'm
personally trying to steer the group to do a proof of concept of running our
sub 40K stack over 6 LoWPAN on Contiki.

Going back to the problem statement, definitely the second point is only
valid if considering XML .

For the first point, if we are assuming there is a gateway present that
isn't constrained by power requirements then the ways to tackle this issue
become wider.

My bias is not towards SIP, some sort of adulterated HTTP or anything else,
but I think anyone in this space should consider the fact that a SIP based
architecture will be the defacto standard for mobile networks, which is
already the most ubiquitos system out there. Thats why I'm interested in
both SIP for this space.

Its one thing standardizing how to implement application layers over 6LoWPAN
but standardizing around specific REST architecures, SIP architectures,
desription logics or anything else at this point without understanding
requirements is quite unreasonable.