[6lowapp] BOF proposal: update

nicolas.riou@fr.schneider-electric.com Mon, 28 September 2009 20:40 UTC

Return-Path: <nicolas.riou@fr.schneider-electric.com>
X-Original-To: 6lowapp@core3.amsl.com
Delivered-To: 6lowapp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DBEC33A63EC for <6lowapp@core3.amsl.com>; Mon, 28 Sep 2009 13:40:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.448
X-Spam-Level:
X-Spam-Status: No, score=-3.448 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UbbmsRyWGzwT for <6lowapp@core3.amsl.com>; Mon, 28 Sep 2009 13:40:05 -0700 (PDT)
Received: from mailX01.eud.schneider-electric.com (mailx01.eud.schneider-electric.com [205.167.7.35]) by core3.amsl.com (Postfix) with ESMTP id 96EFC3A691E for <6lowapp@ietf.org>; Mon, 28 Sep 2009 13:40:05 -0700 (PDT)
Received: from ATEUI01.schneider-electric.com ([10.198.14.9]) by mailX01.eud.schneider-electric.com with ESMTP id 2009092822412049-25632 ; Mon, 28 Sep 2009 22:41:20 +0200
To: 6lowapp@ietf.org
MIME-Version: 1.0
Sensitivity:
X-Priority: 3 (Normal)
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OF0AD7E9AA.9D7E2A9C-ONC125763B.006A8849-C125763F.0071A57F@schneider-electric.com>
From: nicolas.riou@fr.schneider-electric.com
Date: Mon, 28 Sep 2009 22:31:18 +0200
X-MIMETrack: Serialize by Router on ATEUI01.Schneider-Electric.com/T/SVR/Schneider at 28/09/2009 22:41:23, Serialize complete at 28/09/2009 22:41:23, Itemize by SMTP Server on AXEU1OUT.schneider-electric.com/X/SVR/SEIxtra at 09/28/2009 10:41:20 PM, Serialize by Router on AXEU1OUT.schneider-electric.com/X/SVR/SEIxtra at 09/28/2009 10:41:22 PM, Serialize complete at 09/28/2009 10:41:22 PM
Content-Type: multipart/alternative; boundary="=_alternative 0071A57BC125763F_="
Subject: [6lowapp] BOF proposal: update
X-BeenThere: 6lowapp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Application protocols for constrained nodes and networks <6lowapp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/6lowapp>, <mailto:6lowapp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6lowapp>
List-Post: <mailto:6lowapp@ietf.org>
List-Help: <mailto:6lowapp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lowapp>, <mailto:6lowapp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Sep 2009 20:40:07 -0000

Hi Carsten and al,

I have a few remarks/suggestions to complement the BOF proposal.
I would like to emphasize on the need for seamless integration of 
up-and-coming architectures and Web Services.

> Description:
> ...
> Still, it would be a mistake to start a new silo of application
> protocols that do not benefit from existing application area Internet
> experience. 
> The goal of 6lowapp is to produce application protocol and
> application commissioning solutions suitable for providing us the web
> for resource constrained devices suitable for use also over very
> constrained networks such as 6LoWPAN.
In the world of wireline embedded solution, the Device Profile for Web 
Services (DPWS) is now a recognized OASIS standard to provide low cost 
SOA solution at the device level, providing a complete solution both at 
the application protocol level and at the commissioning level.
In the wireless world, the DPWS solution can be used in conjunction with 
Binary XML encoding solutions such as EXI.


> 6lowapp WG Charter Outline:
> ---------------------------
> * This working group will not work on new content formats
>   or encodings, nor the compression or adaptation of HTTP. (to be 
expanded)
...but does not exclude considering standardized binary XML solutions to 
compress messages.


> 2. Application protocol:
>  ...
>   -- Features will include e.g. support for URLs, content types and
>      encodings, PULL and PUSH interaction models, basic REST methods,
>      both UDP and TCP, a simple form of cachability, and statelessness. 
Eventing is also important, e.g. WS-eventing (as provided by DPWS) using 
SOAP over UDP and Binary XML encoding.


>   -- Proxying with HTTP and SNMP must be straightforward.
Proposal:
   -- Proxying with HTTP, SNMP and WS-Management must be straightforward.

SNMP, despite a large installed based will likely decline in new 
architectures and will be replaced by new protocols like WS-Management. 
Seamless integration of WS-Management must be considered.

>  3. Application commissioning:
>  ...
>    -- Proxying with IP service discovery protocols such as SLP, SSDP or
>    DNS-SD must be straightforward.
Proposal:
     -- Proxying with IP service discovery protocols such as SLP, SSDP or
     DNS-SD or WS-Discovery as provided by DPWS must be straightforward.

Looking forward for your feedback.
Nicolas