Brian, We've been looking at similar use of HTTP for delay-disruption-tolerant networks - which overlap with sensor networks in application quite a lot; we're working on a DTN that is also a sensor network.
Details of this HTTP use in: http://tools.ietf.org/html/draft-wood-dtnrg-http-dtn-delivery http://personal.ee.surrey.ac.uk/Personal/L.Wood/publications/internet-drafts/draft-wood-dtnrg-http-dtn-delivery/lloyd-wood-http-dtn-delivery-ietf-71-dtnrg-session.pdf RFC2616 is worded to allow HTTP not just over TCP, but over any bidirectional stream; this could even be HDLC between connected nodes. For HTTP over UDP, we propose streaming over the Saratoga protocol, which adds sequence numbers retransmission in the face of errors, etc. My take is that HTTP's strength is text, and that we'd want to be able to compress any generic text well, perhaps starting with a common dictionary of HTTP tokens (GET etc.) for the text compressor. food for thought/discussion in Stockholm? cheers, L. > I have posted an Internet-Draft with some of my ideas on what I've been > calling "Chopan" for "Compressed HTTP Over PANs": > > http://www.ietf.org/internet-drafts/draft-frank-6lowpan-chopan-00.txt > > The ideas aren't fully flushed out, and I'm sure a broader group could > probably do a lot to refine these ideas. But hopefully this will be enough > to get some ideas flowing. > > Brian <http://www.ee.surrey.ac.uk/Personal/L.Wood/><[email protected]>
_______________________________________________ 6lowpan mailing list [email protected] https://www.ietf.org/mailman/listinfo/6lowpan
