Re: [6lowapp] Proposed charter for 6LoWAPP BOF

Hello,

I think for Web messaging there are very nice Web push patterns  
emerging (comet, pubsubhubbub, restms) that are worth considering.  
Sure, work is needed for reliability and security, but the entry  
barrier is much lower than xmpp, and its actually more suited for  
devices with similar features but less verbose which makes that  
solution appealing. I'm sending a paper to WWW about Web based  
messaging, hopefully I'll be able to share it with you soon (if I kick  
my butt enough to get back to work and finish it by tomorrow's  
deadline :)

Vlad

On Nov 1, 2009, at 6:23 PM, Paul Duffy wrote:

> Hi Donn,
>
>> We welcome other suggestions like XMPP and SIP but we did look at  
>> those and
>> ruled them out for reasons like:
>> 1)  Verboseness (using text string exchanges for devices with very  
>> small
>> transmit/receive packet sizes)
>> 2)  Session management overhead
>>
>
>
> SIP in the Smart Grid HAN seems a fundamental misfit to SIPs  
> chartered intent.
>
> But XMPP gives me pause...
>
> - would not an EXI encoding go a long way to alleviate the verbosity  
> issues?
>
> - RESTful HTTP is a fine choice, but there are requirements for more  
> than just request/response messaging patterns in the Smart Grid HAN  
> and NAN.  XMPP would offer request/response (sensor reading), pub/ 
> sub (broadcast announcements), one way async (scheduled reads),  
> presence for endpoint status, etc.
>
> - how is XMPP session management any more onerous that HTTP over  
> TLS?  This assuming of course that TCP is doable.
>
> Cheers
>
>
>> Don
>>
>>
>>
>>
>
> _______________________________________________
> 6lowapp mailing list
> 6lowapp@ietf.org
> https://www.ietf.org/mailman/listinfo/6lowapp