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

Hello,
I don't get one point here. Help me to understand.
Are we searching for a well known protocol to use as CoAP for 6lowPAN and WSN networks or are we searching for a "model" to use for?

I'm seeing here a lot of proposal like HTTP, SNMP, SIP, XMPP on the plate. Each of these protocols have been developed for a specific purpose keeping in mind specific constraints and requirements and each of them is a valid choice for the respective domain. On the other side, each of them have some drawbacks for 6lowPAN and WSN networks and I see a lot of diverged opinions here.

Why we fear for define a new application protocol especially designed for 6lowPAN and WSN networks?

I'm a newbie for 6lowPAN but my feeling is that a simple lightweight protocol (I also prefer LoAP instead of CoAP) with a minimal set of primitives (e.g. SET/SET-Reply, GET/GET-Reply and Event/Ack) is sufficient to cover the most part of the use cases and interaction models for 6lowPAN and WSN networks. Other items can be further added on the plate like security, service discovery, nodes and network management, and so on .. but all they can be solved with the same minimal approach keeping in mind the real nature and the scope of 6lowPAN networks. At the end of day, we are talking about CSMA/CA radio networks with high lossy and few kilobytes of useful throughput. Also the nodes spend most part of their time sleeping down to save power or can be inactive for days (or months). I've some doubts that complex protocols/frameworks (developed for other scopes than 6lowPAN) can run efficiently on our small poor devices. But that's only the feeling of a newbie ....

Adriano

-----Original Message-----
From: 6lowapp-bounces@ietf.org [mailto:6lowapp-bounces@ietf.org] On Behalf Of Paul Duffy (paduffy)
Sent: mercoledì 4 novembre 2009 13.50
To: nicolas.riou@fr.schneider-electric.com
Cc: 6lowapp@ietf.org
Subject: Re: [6lowapp] Proposed charter for 6LoWAPP BOF

I agree there is a need for more than request/response messaging, but 
WS_*  gives me pause for constrained devices and links. It is probably 
the most compute intensive, bandwidth hungry way to interface HAN-like 
endpoints.

>
> Hi Cullen,
>
>     >----- Message de Cullen Jennings <fluffy@cisco.com> sur Sat, 31 
> Oct 2009 11:29:41 -0600 -----
>     >Pour:        arjun.lists@hsc.com
>     >cc:        Don Sturek <donsturek@grid2home.com>om>, 6lowapp@ietf.org
>     >Objet:        Re: [6lowapp] Proposed charter for 6LoWAPP BOF
>     >
>     >On Oct 29, 2009, at 12:11 , Arjun Roychowdhury wrote:
>     >
>     > ...
>     >OK - The way I want to try and derive us towards a decision here 
> is  
>     >get a list of candidate protocols then for each one ask the 
> yes/no is  
>     >the their agreement that we should do a mapping to that protocol. 
>  The  
>     >protocols I have heard so far are HTTP, SNMP,  SMTP. So two 
> questions
>     >
>     >1) what other protocols mapping should we do?
>
> The charter has significantly changed these days and I would like to 
> re-state the need for
> seamless interfacing between 6lowapp and the DPWS world. DPWS is a low 
> cost SOA solution at
> device level and will play a major role in future Building and 
> Industrial Automation systems
> (embedded in zone controllers, Automation servers, industrial 
> PLCs...). Besides, in some
> cases, native support of DPWS in VISTA and Windows 7 network explorer 
> might help in simplifying
> discovery and commissioning of devices.
> The HTTP REST model proposed in the new charter is sufficient for 
> simple get/set operations but
> I join Vlad Trifa when saying that there are requirements for more 
> than just request/response
> messaging patterns like e.g. publish/subscribe (multicast). IMO 
> seamless interfacing with WS_*
> (at least straightforward proxying) must be provided to ensure 
> efficient integration of 6lowpan networks
> in upcoming architectures.
>
> Regards.
> Nicolas
> ------------------------------------------------------------------------
>
> _______________________________________________
> 6lowapp mailing list
> 6lowapp@ietf.org
> https://www.ietf.org/mailman/listinfo/6lowapp
>   

_______________________________________________
6lowapp mailing list
6lowapp@ietf.org
https://www.ietf.org/mailman/listinfo/6lowapp