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

On Nov 1, 2009, at 19:50 , Don Sturek wrote:

> Hi Paul,
>
> Yes, XMPP would be quite interesting if the text exchange could be  
> avoided.

I think it should be possible to use an encoded XMPP over CoAP (so in  
the payload of CoAP). The XMPP model doesn't seem like an option for  
CoAP itself, as it would a) require the same encoding for everything,  
b) requires you to parse the whole thing to know what the heck it is  
and c) assumes a stream and thus TCP.

> Can we add this possibility to our CoAp charter as a application  
> transport
> possibility?

I think the charter could mention XMPP as something that can be run  
over the framework or be integrated with. The charter doesn't need to  
say what the solution for CoAP is yet, but rather concentrate on what  
it should achieve. As of now it is agnostic about that, which is good.

There was an important point by Paul below that the interaction models  
offered by HTTP are not sufficient, and I totally agree. CoAP can't be  
limited to only request/response and unicast interactions. So is this  
like REST+?

Zach

>
> Don
>
>
> -----Original Message-----
> From: Paul Duffy [mailto:paduffy@cisco.com]
> Sent: Sunday, November 01, 2009 9:23 AM
> To: d.sturek@att.net
> Cc: 'Cullen Jennings'; 6lowapp@ietf.org
> Subject: Re: [6lowapp] Proposed charter for 6LoWAPP BOF
>
> 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

-- 
http://www.sensinode.com
http://zachshelby.org - My blog “On the Internet of Things”
Mobile: +358 40 7796297

Zach Shelby
Head of Research
Sensinode Ltd.
Kidekuja 2
88610 Vuokatti, FINLAND

This e-mail and all attached material are confidential and may contain  
legally privileged information. If you are not the intended recipient,  
please contact the sender and delete the e-mail from your system  
without producing, distributing or retaining copies thereof.