From arjunrc@gmail.com Fri Dec 4 12:50:47 2009 Return-Path: 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 1E2733A68F3 for <6lowapp@core3.amsl.com>; Fri, 4 Dec 2009 12:50:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.976 X-Spam-Level: X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001] 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 xjvme73zIEj2 for <6lowapp@core3.amsl.com>; Fri, 4 Dec 2009 12:50:46 -0800 (PST) Received: from mail-qy0-f203.google.com (mail-qy0-f203.google.com [209.85.221.203]) by core3.amsl.com (Postfix) with ESMTP id BA97A3A6892 for <6lowapp@ietf.org>; Fri, 4 Dec 2009 12:50:45 -0800 (PST) Received: by qyk41 with SMTP id 41so1204133qyk.29 for <6lowapp@ietf.org>; Fri, 04 Dec 2009 12:50:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:reply-to:received :in-reply-to:references:from:date:x-google-sender-auth:message-id :subject:to:cc:content-type; bh=4lqYzswQ9Fo3676IWof/sXf36Tqg0XBKpHgH+fVHp4s=; b=GfHSErtFo7sCXBIxzf0IFkoLlJ76AOkDMbbeaK5HO996qYa/kkSCwQtZHpKka0TULN 11ZRUx5FWzF9iaqY4fSSq2paQGMxOCGHhxHgipyxDIUmvJzcvEiMsI3Te4rGQIMUMu8e iMTRQMUaN3WsYgmzAbZYebyniJCoapS4mu5FU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:reply-to:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=heDmPpDDdD4Pgrl1/Jm7bWKv0Azha4+s5rDq8RPmdmGrDRGRuSxIH/GUkdvWEgSurV FrVJ7ql6VhOauJb8108YHCUKEpVNCLSWsbm6mYIUi/ve/vQMFHi4RKj3cLzyv3x6K5JC DNZvzECPmX/eEBQP7C4NW8COx2dcl2STVEnCc= MIME-Version: 1.0 Sender: arjunrc@gmail.com Received: by 10.224.94.68 with SMTP id y4mr1983138qam.178.1259959833364; Fri, 04 Dec 2009 12:50:33 -0800 (PST) In-Reply-To: <87321337-9927-4468-A03E-6FB3D086D682@sensinode.com> References: <1220434074.5410511259332678903.JavaMail.root@polinya> <87321337-9927-4468-A03E-6FB3D086D682@sensinode.com> From: Arjun Roychowdhury Date: Fri, 4 Dec 2009 15:50:13 -0500 X-Google-Sender-Auth: 3762bbc058b38c0f Message-ID: To: Zach Shelby Content-Type: multipart/alternative; boundary=000feaf109484c8c7a0479ed424a Cc: "6lowapp@ietf.org" <6lowapp@ietf.org> Subject: Re: [6lowapp] the role of gateway nodes X-BeenThere: 6lowapp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: arjun.lists@hsc.com List-Id: Application protocols for constrained nodes and networks <6lowapp.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Dec 2009 20:50:47 -0000 --000feaf109484c8c7a0479ed424a Content-Type: text/plain; charset=ISO-8859-1 On Mon, Nov 30, 2009 at 8:24 AM, Zach Shelby wrote: > > > We can probably get away with CoRE and CoAP being the only acronyms used > here. CoRE describes the WG and the general set of requirements, but is not > any particular network. CoAP makes sense as the name for a protocol. > > The simplification of the charter suggested in the Hiroshima BOF hints that > we probably don't need to talk about CoGIIs at all, just that there is an > HTTP mapping. And I don't see a need for CE, CoNet and CoNode all that. We > can just talk about CoRE or write it out as constrained environments? > ARC> I'd much rather that CoGII be retained as an 'abstract concept'. In some cases, it may be a stateful protocol mapping, some cases stateless mapping and in some cases a null function (i.e. smart appliances that can directly talk "Internet protocols" as Carsten's email indicates. This architecturally separates the concept of the need for protocol conversion and the fact that HTTP is one of may protocols that may need interworking. Even if the focus of the core group (whatever it is called in 6lowapp) is just to map HTTP, it should make it clear that this is a CoGII function and in future, this may change depending on the device in question and the network in question. > > Zach > > > Thanks. > > > > JP. > > > >> Gruesse, Carsten > >> > >> _______________________________________________ > >> 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 > > -- > http://www.sensinode.com > http://zachshelby.org - My blog "On the Internet of Things" > http://6lowpan.net - New book - "6LoWPAN: The Wireless Embedded Internet" > 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. > > > > > _______________________________________________ > 6lowapp mailing list > 6lowapp@ietf.org > https://www.ietf.org/mailman/listinfo/6lowapp > > > > > > > > *********************************************DISCLAIMER********************************************* > The email is subject to Disclaimer as per - > http://www.hsc.com/tabid/91/Default.aspx#emaildisclaimer > > > -- Arjun Roychowdhury --000feaf109484c8c7a0479ed424a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Mon, Nov 30, 2009 at 8:24 AM, Zach Sh= elby <zach@sensi= node.com> wrote:


We can probably get away with CoRE and CoAP being the only acronyms used he= re. CoRE describes the WG and the general set of requirements, but is not a= ny particular network. CoAP makes sense as the name for a protocol.

The simplification of the charter suggested in the Hiroshima BOF hints that= we probably don't need to talk about CoGIIs at all, just that there is= an HTTP mapping. And I don't see a need for CE, CoNet and CoNode all t= hat. We can just talk about CoRE or write it out as constrained environment= s?

ARC> I'd much rather that CoGII be = retained as an 'abstract concept'. In some cases, it may be a state= ful protocol mapping, some cases stateless mapping and in some cases a null= function (i.e. smart appliances that can directly talk "Internet prot= ocols" as Carsten's email indicates. This architecturally separate= s the concept of the need for protocol conversion and the fact that HTTP is= one of may protocols that may need interworking. Even if the focus of the = core group (whatever it is called in 6lowapp) is just to map HTTP, it shoul= d make it clear that this is a CoGII function and in future, this may chang= e depending on the device in question and the network in question.
=A0

Zach

> Thanks.
>
> JP.
>
>> Gruesse, Carsten
>>
>> _______________________________________________
>> 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

--
http://www.sensinode= .com
http://zachshelby.org - My blog "On the Internet of Things"
http://6lowpan.net - N= ew book - "6LoWPAN: The Wireless Embedded Internet"
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 lega= lly privileged information. If you are not the intended recipient, please c= ontact the sender and delete the e-mail from your system without producing,= distributing or retaining copies thereof.




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






*********************************************DISCLAIMER********************= *************************
The email is subject to Disclaimer as per - http://www.hsc.com/= tabid/91/Default.aspx#emaildisclaimer





--
Arjun Roych= owdhury

--000feaf109484c8c7a0479ed424a-- From arjunrc@gmail.com Fri Dec 4 12:57:30 2009 Return-Path: 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 C456E3A6892 for <6lowapp@core3.amsl.com>; Fri, 4 Dec 2009 12:57:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.976 X-Spam-Level: X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001] 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 fGHZI02g7qUy for <6lowapp@core3.amsl.com>; Fri, 4 Dec 2009 12:57:30 -0800 (PST) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.27]) by core3.amsl.com (Postfix) with ESMTP id BAD373A6810 for <6lowapp@ietf.org>; Fri, 4 Dec 2009 12:57:29 -0800 (PST) Received: by qw-out-2122.google.com with SMTP id 9so562332qwb.31 for <6lowapp@ietf.org>; Fri, 04 Dec 2009 12:57:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:reply-to:received :in-reply-to:references:from:date:x-google-sender-auth:message-id :subject:to:cc:content-type; bh=xCnXWsDW2kbd8eEc2jL450Vxp8397mvp3vXlva+X5qY=; b=VJacGb0lPSlTlSucuz7Dt6jw4utegNmudixUyUFqo8W2Fjjl9gOjFb7dI4Rvh2cb6c pK8f/haZ4bi6uWn7RlXIPR73mCBnxj3TRTKSdduNgLJGmqJtOR8kwI70foQ5cBk0bZ4r WTZ3ZHEEoMGND92g0wci6mZgWVdeCmr78Fj2g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:reply-to:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=iICO2A9wGTpCqvSDD/pJE7KokwBG3UBSnUDEcp/6KTsHBsAQUFPC4GJKfS/2K0xT8+ hLN9UomvnKdgp7dV6TvGE3YCfX2P4TpTNRqahbFHEVn+e9Rx74WSE9JEsXmPBT91Z/Ro RS7++f1CgRE84ghHcKCv9rqFX0Ptub543LV9E= MIME-Version: 1.0 Sender: arjunrc@gmail.com Received: by 10.224.113.96 with SMTP id z32mr1990864qap.112.1259960238096; Fri, 04 Dec 2009 12:57:18 -0800 (PST) In-Reply-To: References: <1220434074.5410511259332678903.JavaMail.root@polinya> From: Arjun Roychowdhury Date: Fri, 4 Dec 2009 15:56:58 -0500 X-Google-Sender-Auth: 05ad673786b7fe4e Message-ID: To: Carsten Bormann Content-Type: multipart/alternative; boundary=00c09f99e4d76c42f90479ed5a44 Cc: "6lowapp@ietf.org" <6lowapp@ietf.org> Subject: Re: [6lowapp] the role of gateway nodes X-BeenThere: 6lowapp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: arjun.lists@hsc.com List-Id: Application protocols for constrained nodes and networks <6lowapp.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Dec 2009 20:57:30 -0000 --00c09f99e4d76c42f90479ed5a44 Content-Type: text/plain; charset=ISO-8859-1 On Fri, Nov 27, 2009 at 10:00 AM, Carsten Bormann wrote: > On Nov 27, 2009, at 15:37, Xavi Vilajosana Guillen wrote: > > > what's the approach at 6LowApp? anyone knows ongoing work on that issue? > > I would summarize the thinking that went into the BOF as follows: > > Some nodes in a CE (constrained environment) may actually be not that > constrained (as nodes and with respect to their network). These can > directly speak the appropriate application protocol (HTTP, SNMP, XMPP, SIP) > to some correspondent node outside (or inside) the CE. (We didn't put this > on the slides because that is nothing new.) > ARC> This may be just my opinion but I think thats an important point to put in even if its not new. To some of us, the assertions being made in the group about network bandwidth and device constrained are not coupled with concrete proof and makes us wonder why such stringent constraints are being laid out. It goes back to Henning Schulzrinne's points made in these threads: http://www.ietf.org/mail-archive/web/6lowapp/current/msg00266.html http://www.ietf.org/mail-archive/web/6lowapp/current/msg00257.html http://www.ietf.org/mail-archive/web/6lowapp/current/msg00215.html If this group were to make this classification clear that there will be devices that adhere to stringent needs and those that can accommodate richer protocols, even in what is called a 'LowPAN' network, then it completes the story better. > -- Arjun Roychowdhury --00c09f99e4d76c42f90479ed5a44 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Fri, Nov 27, 2009 at 10:00 AM, Carste= n Bormann <cabo@tzi.or= g> wrote:
On Nov 27, 2009, at 15:37, Xavi Vilajosana Guillen wrote:=

> what's the approach at 6LowApp? anyone knows ongoing work on that = issue?

I would summarize the thinking that went into the BOF as follows:

Some nodes in a CE (constrained environment) may actually be not that const= rained (as nodes and with respect to their network). =A0These can directly = speak the appropriate application protocol (HTTP, SNMP, XMPP, SIP) to some = correspondent node outside (or inside) the CE. =A0(We didn't put this o= n the slides because that is nothing new.)

ARC> This may be just my opinion but I = think thats an important point to put in even if its not new. To some of us= , the assertions being made in the group about network bandwidth and device= constrained are not coupled with concrete proof and makes us wonder why su= ch stringent constraints are being laid out. It goes back to Henning Schulz= rinne's points made in these threads:

If this group were to make this classificatio= n clear that there will be devices that adhere to stringent needs and those= that can=A0accommodate richer protocols, even in what is called a 'Low= PAN' network, then it completes the story better.

=A0
=A0
= --=A0
Arjun Roychowdhury

--00c09f99e4d76c42f90479ed5a44-- From guido.moritz@uni-rostock.de Fri Dec 18 03:45:01 2009 Return-Path: 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 D6E623A6A59 for <6lowapp@core3.amsl.com>; Fri, 18 Dec 2009 03:45:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.941 X-Spam-Level: X-Spam-Status: No, score=-2.941 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HELO_EQ_DE=0.35, MSGID_MULTIPLE_AT=1.449, RCVD_IN_DNSWL_MED=-4] 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 H5lclq1niKR1 for <6lowapp@core3.amsl.com>; Fri, 18 Dec 2009 03:45:00 -0800 (PST) Received: from ida.uni-rostock.de (ida.uni-rostock.de [139.30.8.34]) by core3.amsl.com (Postfix) with ESMTP id 4B34A3A69C7 for <6lowapp@ietf.org>; Fri, 18 Dec 2009 03:45:00 -0800 (PST) Received: from email2.uni-rostock.de (139.30.8.209) by ida.uni-rostock.de (139.30.8.162) with Microsoft SMTP Server (TLS) id 8.2.213.0; Fri, 18 Dec 2009 12:44:44 +0100 Received: from schlappi (139.30.201.173) by email2.uni-rostock.de (139.30.8.210) with Microsoft SMTP Server (TLS) id 8.2.213.0; Fri, 18 Dec 2009 12:44:44 +0100 From: Guido Moritz To: 6LoWAPP <6lowapp@ietf.org> Date: Fri, 18 Dec 2009 12:44:37 +0100 Message-ID: <000c01ca7fd7$7a1408f0$6e3c1ad0$@moritz@uni-rostock.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acp/13baXJSupKmBRGy6Xcx1RQl/Fw== Content-Language: de x-cr-hashedpuzzle: AaSy BUrj CjM4 Cmiq EkQV FMx7 Fd6h Fp2F G3oL HHQ/ HJMq IIcO IMgs IcRj Ikkm Im/+; 1; NgBsAG8AdwBhAHAAcABAAGkAZQB0AGYALgBvAHIAZwA=; Sosha1_v1; 7; {1B94018D-4C96-4A60-93F8-C959B8165D88}; ZwB1AGkAZABvAC4AbQBvAHIAaQB0AHoAQAB1AG4AaQAtAHIAbwBzAHQAbwBjAGsALgBkAGUA; Fri, 18 Dec 2009 11:44:32 GMT; SQAtAEQAIABEAFAAVwBTACAAaQBuACAANgBMAG8AVwBQAEEATgA= x-cr-puzzleid: {1B94018D-4C96-4A60-93F8-C959B8165D88} Subject: [6lowapp] I-D DPWS in 6LoWPAN 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: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 11:45:02 -0000 Dear *, because we already have been mentioned in IETF 6LoWAPP mailing list, let = me briefly introduce myself and activities of our research group. We are = part of the Web Services for Devices Initiative (www.ws4d.org), which has implemented several compliant toolkits for the Devices Profile for Web Services (DPWS). We are also voting member of the OASIS WS-DD TC (www.oasis-open.org/committees/ws-dd/), which has defined three = different specifications (DPWS, WS-Discovery, SOAP-over-UDP), common known as = DPWS. We now have submitted an informational I-D on "DPWS in 6LoWPAN = networks". It is available at: http://www.ietf.org/id/draft-moritz-6lowapp-dpws-enhancements-00.txt. I = am not sure if and how it will make its way to the 6LoWAPP wiki site.=20 I would like to invite everybody to give comments on the I-D or for = further fruitful discussions on this topic. Especially section 3.3 might be discussed more in general in 6LoWAPP, independent of the specific application layer protocol.=20 Regards, Guido Moritz ------------------------- Dipl. Ing. Guido Moritz University of Rostock, Department of CS and EE Institute of Applied Microelectronics and Computer Engineering Richard-Wagner Str. 31, 18119 Rostock-Warnemuende Phone:=A0 +49 (0)381 498 - 7269 http://www.imd.uni-rostock.de From zach@sensinode.com Fri Dec 18 03:56:28 2009 Return-Path: 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 5BCE93A6922 for <6lowapp@core3.amsl.com>; Fri, 18 Dec 2009 03:56:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 eKaVaiJOxTjN for <6lowapp@core3.amsl.com>; Fri, 18 Dec 2009 03:56:27 -0800 (PST) Received: from auth-smtp.nebula.fi (auth-smtp.nebula.fi [217.30.180.105]) by core3.amsl.com (Postfix) with ESMTP id 2FB493A6819 for <6lowapp@ietf.org>; Fri, 18 Dec 2009 03:56:26 -0800 (PST) Received: from [62.145.172.51] ([62.145.172.51]) (authenticated bits=0) by auth-smtp.nebula.fi (8.13.4/8.13.4) with ESMTP id nBIBu7mA011437 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 18 Dec 2009 13:56:08 +0200 Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii From: Zach Shelby In-Reply-To: <000c01ca7fd7$7a1408f0$6e3c1ad0$@moritz@uni-rostock.de> Date: Fri, 18 Dec 2009 13:56:08 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <000c01ca7fd7$7a1408f0$6e3c1ad0$@moritz@uni-rostock.de> To: Guido Moritz X-Mailer: Apple Mail (2.1077) Cc: 6LoWAPP <6lowapp@ietf.org> Subject: Re: [6lowapp] I-D DPWS in 6LoWPAN 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: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 11:56:28 -0000 Guido, I added a link to your draft on the Wiki. = http://trac.tools.ietf.org/area/app/trac/wiki/6LowApp Interesting draft, I'll be back with comments next week after a good = reading! Regards, Zach On Dec 18, 2009, at 13:44 , Guido Moritz wrote: > Dear *, >=20 > because we already have been mentioned in IETF 6LoWAPP mailing list, = let me > briefly introduce myself and activities of our research group. We are = part > of the Web Services for Devices Initiative (www.ws4d.org), which has > implemented several compliant toolkits for the Devices Profile for Web > Services (DPWS). We are also voting member of the OASIS WS-DD TC > (www.oasis-open.org/committees/ws-dd/), which has defined three = different > specifications (DPWS, WS-Discovery, SOAP-over-UDP), common known as = DPWS. >=20 > We now have submitted an informational I-D on "DPWS in 6LoWPAN = networks". It > is available at: > http://www.ietf.org/id/draft-moritz-6lowapp-dpws-enhancements-00.txt. = I am > not sure if and how it will make its way to the 6LoWAPP wiki site.=20 >=20 > I would like to invite everybody to give comments on the I-D or for = further > fruitful discussions on this topic. Especially section 3.3 might be > discussed more in general in 6LoWAPP, independent of the specific > application layer protocol.=20 >=20 > Regards, > Guido Moritz >=20 > ------------------------- > Dipl. Ing. Guido Moritz > University of Rostock, Department of CS and EE > Institute of Applied Microelectronics and Computer Engineering > Richard-Wagner Str. 31, 18119 Rostock-Warnemuende > Phone: +49 (0)381 498 - 7269 > http://www.imd.uni-rostock.de >=20 > _______________________________________________ > 6lowapp mailing list > 6lowapp@ietf.org > https://www.ietf.org/mailman/listinfo/6lowapp --=20 http://www.sensinode.com http://zachshelby.org - My blog "On the Internet of Things" http://6lowpan.net - New book - "6LoWPAN: The Wireless Embedded = Internet" 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.=20 From zach@sensinode.com Wed Dec 23 14:30:34 2009 Return-Path: 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 81A1F3A6882 for <6lowapp@core3.amsl.com>; Wed, 23 Dec 2009 14:30:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 e+rOa7W9VTkV for <6lowapp@core3.amsl.com>; Wed, 23 Dec 2009 14:30:33 -0800 (PST) Received: from auth-smtp.nebula.fi (auth-smtp.nebula.fi [217.30.180.105]) by core3.amsl.com (Postfix) with ESMTP id F02343A69B1 for <6lowapp@ietf.org>; Wed, 23 Dec 2009 14:30:32 -0800 (PST) Received: from [192.168.1.4] (line-4671.dyn.kponet.fi [85.29.64.144]) (authenticated bits=0) by auth-smtp.nebula.fi (8.13.4/8.13.4) with ESMTP id nBNMU9iT029063 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <6lowapp@ietf.org>; Thu, 24 Dec 2009 00:30:10 +0200 From: Zach Shelby Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Thu, 24 Dec 2009 00:30:14 +0200 References: <20091223222559.A5E6D3A68BF@core3.amsl.com> To: 6LoWAPP <6lowapp@ietf.org> Message-Id: Mime-Version: 1.0 (Apple Message framework v1077) X-Mailer: Apple Mail (2.1077) Subject: [6lowapp] Fwd: New Version Notification for draft-shelby-6lowapp-coap-00 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: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Dec 2009 22:32:10 -0000 Just in case anybody needs something to read over the holidays ;-) Some = background work on the CoAP work item of the WG proposal, we hope this = is helpful to get things started. http://www.ietf.org/id/draft-shelby-6lowapp-coap-00.txt Merry Christmas! Zach Begin forwarded message: > From: IETF I-D Submission Tool > Date: December 24, 2009 0:25:59 GMT+02:00 > To: zach@sensinode.com > Cc: = Michael.Stuber@itron.com,d.sturek@att.net,brian.tridium@gmail.com,richard.= kelsey@ember.com > Subject: New Version Notification for draft-shelby-6lowapp-coap-00=20 >=20 >=20 > A new version of I-D, draft-shelby-6lowapp-coap-00.txt has been = successfuly submitted by Zach Shelby and posted to the IETF repository. >=20 > Filename: draft-shelby-6lowapp-coap > Revision: 00 > Title: CoAP Feature Analysis > Creation_date: 2009-12-24 > WG ID: Independent Submission > Number_of_pages: 16 >=20 > Abstract: > This document considers the requirements and resulting features > needed for the design of the Constrained Application Protocol (CoAP). > Starting from requirements for energy and building automation > applications, the basic features are identified along with an > analysis of possible realizations. The goal of the document is to > provide a basis for protocol design and related discussion. >=20 > Status of this Memo >=20 > This Internet-Draft is submitted to IETF in full conformance with the > provisions of BCP 78 and BCP 79. >=20 > Internet-Drafts are working documents of the Internet Engineering > Task Force (IETF), its areas, and its working groups. Note that > other groups may also distribute working documents as Internet- > Drafts. >=20 > Internet-Drafts are draft documents valid for a maximum of six months > and may be updated, replaced, or obsoleted by other documents at any > time. It is inappropriate to use Internet-Drafts as reference > material or to cite them other than as "work in progress." >=20 > The list of current Internet-Drafts can be accessed at > http://www.ietf.org/ietf/1id-abstracts.txt. >=20 > The list of Internet-Draft Shadow Directories can be accessed at > http://www.ietf.org/shadow.html. >=20 > This Internet-Draft will expire on June 27, 2010.Copyright Notice >=20 > Copyright (c) 2009 IETF Trust and the persons identified as the > document authors. All rights reserved. >=20 > This document is subject to BCP 78 and the IETF Trust's Legal > Provisions Relating to IETF Documents > (http://trustee.ietf.org/license-info) in effect on the date of > publication of this document. Please review these documents > carefully, as they describe your rights and restrictions with respect > to this document. Code Components extracted from this document must > include Simplified BSD License text as described in Section 4.e of > the Trust Legal Provisions and are provided without warranty as > described in the BSD License. >=20 > This document may contain material from IETF Documents or IETF > Contributions published or made publicly available before November > 10, 2008. The person(s) controlling the copyright in some of this > material may not have granted the IETF Trust the right to allow > modifications of such material outside the IETF Standards Process. > Without obtaining an adequate license from the person(s) controlling > the copyright in such materials, this document may not be modified > outside the IETF Standards Process, and derivative works of it may > not be created outside the IETF Standards Process, except to format > it for publication as an RFC or to translate it into languages other > than English. >=20 >=20 >=20 > The IETF Secretariat. >=20 >=20 --=20 http://www.sensinode.com http://zachshelby.org - My blog "On the Internet of Things" http://6lowpan.net - New book - "6LoWPAN: The Wireless Embedded = Internet" 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.=20 From trifa@inf.ethz.ch Wed Dec 23 15:39:14 2009 Return-Path: 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 1AB523A67EA for <6lowapp@core3.amsl.com>; Wed, 23 Dec 2009 15:39:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] 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 myNiyOFkHlJP for <6lowapp@core3.amsl.com>; Wed, 23 Dec 2009 15:39:13 -0800 (PST) Received: from gwse.ethz.ch (gwse.ethz.ch [129.132.178.237]) by core3.amsl.com (Postfix) with ESMTP id 83B583A67D6 for <6lowapp@ietf.org>; Wed, 23 Dec 2009 15:39:11 -0800 (PST) Received: from CAS02.d.ethz.ch (129.132.178.236) by gws00.d.ethz.ch (129.132.178.237) with Microsoft SMTP Server (TLS) id 8.2.213.0; Thu, 24 Dec 2009 00:38:53 +0100 Received: from [192.168.1.188] (77.58.230.3) by mail.ethz.ch (129.132.178.227) with Microsoft SMTP Server (TLS) id 8.2.213.0; Thu, 24 Dec 2009 00:38:31 +0100 Message-ID: <2B8AA1EF-498F-4C3E-B1F3-450DDAC79168@inf.ethz.ch> From: Vlad Trifa To: Zach Shelby In-Reply-To: Content-Type: text/plain; charset="US-ASCII"; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit MIME-Version: 1.0 (Apple Message framework v936) Date: Thu, 24 Dec 2009 00:38:09 +0100 References: <20091223222559.A5E6D3A68BF@core3.amsl.com> X-Mailer: Apple Mail (2.936) Cc: 6LoWAPP <6lowapp@ietf.org> Subject: Re: [6lowapp] Fwd: New Version Notification for draft-shelby-6lowapp-coap-00 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: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Dec 2009 23:39:14 -0000 Congrats folks, this is fantastic (and a fantastic christmas present). Blogged on WoT, and looking forward to make it real! Looking forward to see what's next! Merry christmas to all of you! Vlad On Dec 23, 2009, at 11:30 PM, Zach Shelby wrote: > Just in case anybody needs something to read over the holidays ;-) > Some background work on the CoAP work item of the WG proposal, we > hope this is helpful to get things started. > > http://www.ietf.org/id/draft-shelby-6lowapp-coap-00.txt > > Merry Christmas! > Zach > > Begin forwarded message: > >> From: IETF I-D Submission Tool >> Date: December 24, 2009 0:25:59 GMT+02:00 >> To: zach@sensinode.com >> Cc: >> Michael.Stuber@itron.com,d.sturek@att.net,brian.tridium@gmail.com,richard.kelsey@ember.com >> Subject: New Version Notification for draft-shelby-6lowapp-coap-00 >> >> >> A new version of I-D, draft-shelby-6lowapp-coap-00.txt has been >> successfuly submitted by Zach Shelby and posted to the IETF >> repository. >> >> Filename: draft-shelby-6lowapp-coap >> Revision: 00 >> Title: CoAP Feature Analysis >> Creation_date: 2009-12-24 >> WG ID: Independent Submission >> Number_of_pages: 16 >> >> Abstract: >> This document considers the requirements and resulting features >> needed for the design of the Constrained Application Protocol (CoAP). >> Starting from requirements for energy and building automation >> applications, the basic features are identified along with an >> analysis of possible realizations. The goal of the document is to >> provide a basis for protocol design and related discussion. >> >> Status of this Memo >> >> This Internet-Draft is submitted to IETF in full conformance with the >> provisions of BCP 78 and BCP 79. >> >> Internet-Drafts are working documents of the Internet Engineering >> Task Force (IETF), its areas, and its working groups. Note that >> other groups may also distribute working documents as Internet- >> Drafts. >> >> Internet-Drafts are draft documents valid for a maximum of six months >> and may be updated, replaced, or obsoleted by other documents at any >> time. It is inappropriate to use Internet-Drafts as reference >> material or to cite them other than as "work in progress." >> >> The list of current Internet-Drafts can be accessed at >> http://www.ietf.org/ietf/1id-abstracts.txt. >> >> The list of Internet-Draft Shadow Directories can be accessed at >> http://www.ietf.org/shadow.html. >> >> This Internet-Draft will expire on June 27, 2010.Copyright Notice >> >> Copyright (c) 2009 IETF Trust and the persons identified as the >> document authors. All rights reserved. >> >> This document is subject to BCP 78 and the IETF Trust's Legal >> Provisions Relating to IETF Documents >> (http://trustee.ietf.org/license-info) in effect on the date of >> publication of this document. Please review these documents >> carefully, as they describe your rights and restrictions with respect >> to this document. Code Components extracted from this document must >> include Simplified BSD License text as described in Section 4.e of >> the Trust Legal Provisions and are provided without warranty as >> described in the BSD License. >> >> This document may contain material from IETF Documents or IETF >> Contributions published or made publicly available before November >> 10, 2008. The person(s) controlling the copyright in some of this >> material may not have granted the IETF Trust the right to allow >> modifications of such material outside the IETF Standards Process. >> Without obtaining an adequate license from the person(s) controlling >> the copyright in such materials, this document may not be modified >> outside the IETF Standards Process, and derivative works of it may >> not be created outside the IETF Standards Process, except to format >> it for publication as an RFC or to translate it into languages other >> than English. >> >> >> >> The IETF Secretariat. >> >> > > -- > http://www.sensinode.com > http://zachshelby.org - My blog "On the Internet of Things" > http://6lowpan.net - New book - "6LoWPAN: The Wireless Embedded > Internet" > 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. > > > > > _______________________________________________ > 6lowapp mailing list > 6lowapp@ietf.org > https://www.ietf.org/mailman/listinfo/6lowapp From arjunrc@gmail.com Thu Dec 24 07:14:34 2009 Return-Path: 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 041803A6995 for <6lowapp@core3.amsl.com>; Thu, 24 Dec 2009 07:14:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.976 X-Spam-Level: X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001] 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 vgLwiQza2P6g for <6lowapp@core3.amsl.com>; Thu, 24 Dec 2009 07:14:33 -0800 (PST) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.27]) by core3.amsl.com (Postfix) with ESMTP id E9F6D3A6994 for <6lowapp@ietf.org>; Thu, 24 Dec 2009 07:14:32 -0800 (PST) Received: by qw-out-2122.google.com with SMTP id 9so1775927qwb.31 for <6lowapp@ietf.org>; Thu, 24 Dec 2009 07:14:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:reply-to:received:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=O7WCAxIKNwQN5fvscjFhdh9lttZh9KPl7sFcvtb+exA=; b=Hvr3I7mIX7bPwY+f50ooRRuUeycubvoNlCw8LU8y2F9d7bYIVEdn3OnXJSy+U8Pqu2 TMGsfbwr2qpS+nZ+H+uOYkTdpBaHjIWADhaGzsrJpPtDrkRFgjY/nPJj4umD+6kwlZrq zgam6ZlC6Ii5vgZQDbYc6JJJ02iu9dlppULA0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:reply-to:from:date:x-google-sender-auth :message-id:subject:to:content-type; b=HANpYNz/TadDSV3B0xpSpuVFPTJuDBbAUyQkwsIYME863vdX6FoKmJZqHCPvioo9VC GfOcntP04K2rQLyzZ67M9NWxIWAPuUm24UBLMaS5v5uAlXf3FGl0ykyqeAVxvmldLBdS EQlOiICU4yjS6pZR9xxB4Mg8OxXkD5XKQ8oEc= MIME-Version: 1.0 Sender: arjunrc@gmail.com Received: by 10.224.78.163 with SMTP id l35mr5849044qak.347.1261667653101; Thu, 24 Dec 2009 07:14:13 -0800 (PST) From: Arjun Roychowdhury Date: Thu, 24 Dec 2009 10:13:53 -0500 X-Google-Sender-Auth: e2beea46a8cd0ae1 Message-ID: To: 6lowapp@ietf.org Content-Type: multipart/alternative; boundary=00c09f99e1d249aa61047b7ae4c5 Subject: [6lowapp] Realization of an automated demand & response system (mapped to OpenADR) - applicable to energy management systems/CoGII in the HAN X-BeenThere: 6lowapp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: arjun.lists@hsc.com List-Id: Application protocols for constrained nodes and networks <6lowapp.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Dec 2009 15:17:16 -0000 --00c09f99e1d249aa61047b7ae4c5 Content-Type: text/plain; charset=ISO-8859-1 Hi, the SIP Forum Smartgrid group has released an updated whitepaper on how an automated Demand & Response system can be effectively implemented using SIP Event service. The constitutes the DRAS (not of direct interest to this group) and the DRAS client, which will likely be resident in the CoGII that this group is defining. Comments welcome. Document link: http://www.sipforum.org/component/option,com_docman/task,doc_details/gid,375/Itemid,261/ regds arjun -- Arjun Roychowdhury --00c09f99e1d249aa61047b7ae4c5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, the SIP Forum Smartgrid group has released an updated whitepaper on how= an automated Demand & Response system can be effectively implemented u= sing SIP Event service.
The constitutes the DRAS (not of direct interes= t to this group) and the DRAS client, which will likely be resident in the = CoGII that this group is defining.

Comments welcome.



regds
arjun
<= br>--
Arjun Roychowdhury

--00c09f99e1d249aa61047b7ae4c5-- From jonsmirl@gmail.com Tue Dec 29 17:14:31 2009 Return-Path: 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 34CFF3A68D2 for <6lowapp@core3.amsl.com>; Tue, 29 Dec 2009 17:14:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.001 X-Spam-Level: X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001] 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 Pzbx+AjlYoHR for <6lowapp@core3.amsl.com>; Tue, 29 Dec 2009 17:14:30 -0800 (PST) Received: from mail-pw0-f50.google.com (mail-pw0-f50.google.com [209.85.160.50]) by core3.amsl.com (Postfix) with ESMTP id 8BD713A67A1 for <6lowapp@ietf.org>; Tue, 29 Dec 2009 17:14:30 -0800 (PST) Received: by pwi20 with SMTP id 20so7725366pwi.29 for <6lowapp@ietf.org>; Tue, 29 Dec 2009 17:14:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=N9gXEED9MOdQO7wnoctlVxSV/UQnD92nTLNE21fgLAg=; b=pjOVfTZdha/URaL96t9TrH6dHfW43GEBhEJpXt6mwRYMUZ/SXiyGK8og7LYwPBi62+ DZlwqK082t6GOCQyUyTLpervtIWlPoeDeaUIlT/EYzW2VbWCcLq60TDBs0BtZYsyHVNZ uRrBSAgkUfcx9N8Ju9iLNJwS0482eNdBnYGu0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=S29sOyHCP0+3UffvSBIhW4ajaspSoWqdIhwTVfW4oXRzK34aWn2rfQlOHU6zeZM9Ou pM8kvTogJUzyAbzJ5wEVFukpyDIKw0ja+DFKWrFo2wA7SaqWnjRbuKf1Dyo+8TDb6Gjz 7YIZN0/z5eaJPbGw9m99e7dWfJEU7OV+0z0Gc= MIME-Version: 1.0 Received: by 10.142.7.18 with SMTP id 18mr11598770wfg.126.1262135648025; Tue, 29 Dec 2009 17:14:08 -0800 (PST) Date: Tue, 29 Dec 2009 20:14:08 -0500 Message-ID: <9e4733910912291714q39a2c560gd1d3172f424014fd@mail.gmail.com> From: Jon Smirl To: 6lowapp@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Subject: [6lowapp] Device profiles 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: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Dec 2009 01:14:31 -0000 Is 6lowapp planning to develop something like Zigbee device profiles and cluster library? I'm looking at the Zigbee specs for these and I can't use them because of their GPL incompatibly. What alternatives exist? I currently have 6lowpan and http running on a mc13224. -- Jon Smirl jonsmirl@gmail.com From d.sturek@att.net Tue Dec 29 18:29:51 2009 Return-Path: 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 D17843A6817 for <6lowapp@core3.amsl.com>; Tue, 29 Dec 2009 18:29:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.785 X-Spam-Level: * X-Spam-Status: No, score=1.785 tagged_above=-999 required=5 tests=[BAYES_50=0.001, IP_NOT_FRIENDLY=0.334, MSGID_MULTIPLE_AT=1.449, UNPARSEABLE_RELAY=0.001] 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 sz7d+zB+ZAeH for <6lowapp@core3.amsl.com>; Tue, 29 Dec 2009 18:29:51 -0800 (PST) Received: from smtp101.sbc.mail.gq1.yahoo.com (smtp101.sbc.mail.gq1.yahoo.com [67.195.15.60]) by core3.amsl.com (Postfix) with SMTP id 204563A6405 for <6lowapp@ietf.org>; Tue, 29 Dec 2009 18:29:51 -0800 (PST) Received: (qmail 25267 invoked from network); 30 Dec 2009 02:29:31 -0000 Received: from adsl-69-225-120-111.dsl.sndg02.pacbell.net (d.sturek@69.225.120.111 with login) by smtp101.sbc.mail.gq1.yahoo.com with SMTP; 29 Dec 2009 18:29:31 -0800 PST X-Yahoo-SMTP: fvjol_aswBAraSJvMLe2r1XTzhBhbFxY8q8c3jo- X-YMail-OSG: 9zyG9OEVM1mQY2X0gkaQVc9wRAkfg0iI6.9mX8SUPqwulkwoOv02xiRohe.guSd6CVPwgagnzbctYeIv42amNrfIeOKoJzud6F5HrA.pa_a.6v.zCpbhkCBHNX0pnC6XBypBcirHS2O2yH9514yCuGaeGsmrCJ2cqRSMuX0kjJi7pwzoYDaoCRytgPSGLuQbZsLThuw47CbRAcu2zUWsZ7xlMMFFx5eOls0vltupeLpVEKaNQyw5kk4PEuZbn2ofSxHy7nhlmATVVh5xc7mC7ZTVkRNeo_hcL.uXmvQFawgh2EgxUOE- X-Yahoo-Newman-Property: ymail-3 From: "Don Sturek" To: "'Jon Smirl'" , <6lowapp@ietf.org> References: <9e4733910912291714q39a2c560gd1d3172f424014fd@mail.gmail.com> In-Reply-To: <9e4733910912291714q39a2c560gd1d3172f424014fd@mail.gmail.com> Date: Tue, 29 Dec 2009 18:29:19 -0800 Message-ID: <011501ca88f7$e43c30d0$acb49270$@sturek@att.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcqI7WguYjdeMalmR7KuHiqHo5so2AACggug Content-Language: en-us Subject: Re: [6lowapp] Device profiles X-BeenThere: 6lowapp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: d.sturek@att.net List-Id: Application protocols for constrained nodes and networks <6lowapp.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Dec 2009 02:29:51 -0000 Hi Jon, Right now, the CoAP envisions an attribute protocol that follows REST (GET, SET, PUT and DELETE). The structures and attribute content formats are not addressed (and probably would not be). It would then be up to individual application developers to define these structures. In this regard, I would assume that CoAP would not end up looking like either existing ZigBee device profiles or have the application specifics of the ZigBee Cluster Library. Don -----Original Message----- From: 6lowapp-bounces@ietf.org [mailto:6lowapp-bounces@ietf.org] On Behalf Of Jon Smirl Sent: Tuesday, December 29, 2009 5:14 PM To: 6lowapp@ietf.org Subject: [6lowapp] Device profiles Is 6lowapp planning to develop something like Zigbee device profiles and cluster library? I'm looking at the Zigbee specs for these and I can't use them because of their GPL incompatibly. What alternatives exist? I currently have 6lowpan and http running on a mc13224. -- Jon Smirl jonsmirl@gmail.com _______________________________________________ 6lowapp mailing list 6lowapp@ietf.org https://www.ietf.org/mailman/listinfo/6lowapp From jonsmirl@gmail.com Tue Dec 29 18:47:05 2009 Return-Path: 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 2DC113A6A02 for <6lowapp@core3.amsl.com>; Tue, 29 Dec 2009 18:47:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.299 X-Spam-Level: X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599] 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 nJjXcPlIzbuZ for <6lowapp@core3.amsl.com>; Tue, 29 Dec 2009 18:47:04 -0800 (PST) Received: from mail-px0-f179.google.com (mail-px0-f179.google.com [209.85.216.179]) by core3.amsl.com (Postfix) with ESMTP id 6E2183A6A01 for <6lowapp@ietf.org>; Tue, 29 Dec 2009 18:47:04 -0800 (PST) Received: by pxi9 with SMTP id 9so9103332pxi.32 for <6lowapp@ietf.org>; Tue, 29 Dec 2009 18:46:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=uirVgSocpjVuOfhevA11gDvZUZ9/gCu/LWzLZsF01Rg=; b=BiPCRqL4N18R/yPrA7ZuhO4E710PItC+syVkaK3hmq/UE2g57cGokzsXMc9QsDBJj5 we/v8OCYaKIlr7emw+uxm/a/k92moSP870CeddLy1Qv1RUqJfaKhdXrDA20AG7lkMpcW lyy+QDHumZ0Zj056UIH3yQJD3T2xazkACTT4s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=iRpMKUpqfjfBnS491iYhyO9Q+zwvAeuBzZtavQcA+kKb3mpqiM9cPIFVDsS4VLi2rD EIrD3LNdftEn2r1xK0MR1gWPrIRbmvXphlIeiMoPs6tXPJFQLJ6AoHEviP27h+KpPKDb S2qKIloCIlqOvc7iQFLSd3wUcIx9A0qcMCWs0= MIME-Version: 1.0 Received: by 10.142.8.38 with SMTP id 38mr11992737wfh.58.1262141202054; Tue, 29 Dec 2009 18:46:42 -0800 (PST) In-Reply-To: <2862115855827857077@unknownmsgid> References: <9e4733910912291714q39a2c560gd1d3172f424014fd@mail.gmail.com> <2862115855827857077@unknownmsgid> Date: Tue, 29 Dec 2009 21:46:42 -0500 Message-ID: <9e4733910912291846v22cd4fb9k6d56cde3ef1d5ce5@mail.gmail.com> From: Jon Smirl To: d.sturek@att.net Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: 6lowapp@ietf.org Subject: Re: [6lowapp] Device profiles 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: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Dec 2009 02:47:05 -0000 On Tue, Dec 29, 2009 at 9:29 PM, Don Sturek wrote: > Hi Jon, > > Right now, the CoAP envisions an attribute protocol that follows REST (GE= T, > SET, PUT and DELETE). =A0 The structures and attribute content formats ar= e not > addressed (and probably would not be). =A0It would then be up to individu= al > application developers to define these structures. This approach works fine for me too. It would make sense to define standard names for the http parameters and responses in order to achieve interoperability. How are you going to integrate a constrained node that only xmits periodically like a temperature sensors? UDP with a cache and a TTL? The cache would need to respond to http requests. What about service discovery? > > In this regard, I would assume that CoAP would not end up looking like > either existing ZigBee device profiles or have the application specifics = of > the ZigBee Cluster Library. Is the idea to provide a parallel solution minus the the Zigbee licensing baggage? --=20 Jon Smirl jonsmirl@gmail.com From d.sturek@att.net Wed Dec 30 08:40:24 2009 Return-Path: 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 D1C8B3A6A5F for <6lowapp@core3.amsl.com>; Wed, 30 Dec 2009 08:40:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.414 X-Spam-Level: * X-Spam-Status: No, score=1.414 tagged_above=-999 required=5 tests=[AWL=0.370, BAYES_20=-0.74, IP_NOT_FRIENDLY=0.334, MSGID_MULTIPLE_AT=1.449, UNPARSEABLE_RELAY=0.001] 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 B14EYykiGPLA for <6lowapp@core3.amsl.com>; Wed, 30 Dec 2009 08:40:24 -0800 (PST) Received: from smtp107.sbc.mail.gq1.yahoo.com (smtp107.sbc.mail.gq1.yahoo.com [67.195.14.110]) by core3.amsl.com (Postfix) with SMTP id 0AECB3A6A5C for <6lowapp@ietf.org>; Wed, 30 Dec 2009 08:40:24 -0800 (PST) Received: (qmail 75705 invoked from network); 30 Dec 2009 16:40:04 -0000 Received: from adsl-69-105-138-137.dsl.sndg02.pacbell.net (d.sturek@69.105.138.137 with login) by smtp107.sbc.mail.gq1.yahoo.com with SMTP; 30 Dec 2009 08:40:04 -0800 PST X-Yahoo-SMTP: fvjol_aswBAraSJvMLe2r1XTzhBhbFxY8q8c3jo- X-YMail-OSG: tL45OTEVM1ljn4kydG_inJa0UfHZsNbdcSG.Ygx.U7nDpTKaKdMYGEW2qcJy1smTh5vcjYOQC7yC8H8BgVKIvtZxxOT1zWpHdIuww45QGXbMqYULwr_1tNALknR4V3lEta5bVfnMwxzrf2uUER6a8DJZ17keOk838ywHwPZL9XWXI4478UQBBrIEgvVD3UPTcN8xFWZcGQeQX4Bh4_M4wwGBjc32rvgpOC1MLB3U.22eZwaMLekGCcUMmZcx6J1ODSPLwClFhgJDvzv64AFrBk3cWLII1aNXmsCfXfIxVNBbeG_FIw-- X-Yahoo-Newman-Property: ymail-3 From: "Don Sturek" To: "'Jon Smirl'" References: <9e4733910912291714q39a2c560gd1d3172f424014fd@mail.gmail.com> <2862115855827857077@unknownmsgid> <9e4733910912291846v22cd4fb9k6d56cde3ef1d5ce5@mail.gmail.com> In-Reply-To: <9e4733910912291846v22cd4fb9k6d56cde3ef1d5ce5@mail.gmail.com> Date: Wed, 30 Dec 2009 08:40:03 -0800 Message-ID: <004a01ca896e$bcc8e210$365aa630$@sturek@att.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcqI+lJzMjy5OIYBQPObjl1uhl6ivAAdCSBQ Content-Language: en-us Cc: 6lowapp@ietf.org Subject: Re: [6lowapp] Device profiles X-BeenThere: 6lowapp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: d.sturek@att.net List-Id: Application protocols for constrained nodes and networks <6lowapp.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Dec 2009 16:40:25 -0000 Hi Jon, Here is a link to the problem statement for CoAP: http://www.ietf.org/id/draft-shelby-6lowapp-coap-00.txt I think most of the points you asked about are to be addressed. Don -----Original Message----- From: Jon Smirl [mailto:jonsmirl@gmail.com]=20 Sent: Tuesday, December 29, 2009 6:47 PM To: d.sturek@att.net Cc: 6lowapp@ietf.org Subject: Re: [6lowapp] Device profiles On Tue, Dec 29, 2009 at 9:29 PM, Don Sturek wrote: > Hi Jon, > > Right now, the CoAP envisions an attribute protocol that follows REST (GET, > SET, PUT and DELETE). =A0 The structures and attribute content formats = are not > addressed (and probably would not be). =A0It would then be up to = individual > application developers to define these structures. This approach works fine for me too. It would make sense to define standard names for the http parameters and responses in order to achieve interoperability. How are you going to integrate a constrained node that only xmits periodically like a temperature sensors? UDP with a cache and a TTL? The cache would need to respond to http requests. What about service discovery? > > In this regard, I would assume that CoAP would not end up looking like > either existing ZigBee device profiles or have the application = specifics of > the ZigBee Cluster Library. Is the idea to provide a parallel solution minus the the Zigbee licensing baggage? --=20 Jon Smirl jonsmirl@gmail.com From jonsmirl@gmail.com Wed Dec 30 09:12:01 2009 Return-Path: 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 915AA3A65A6 for <6lowapp@core3.amsl.com>; Wed, 30 Dec 2009 09:12:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.949 X-Spam-Level: X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599] 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 tIKjAOwVCgVQ for <6lowapp@core3.amsl.com>; Wed, 30 Dec 2009 09:11:59 -0800 (PST) Received: from mail-qy0-f203.google.com (mail-qy0-f203.google.com [209.85.221.203]) by core3.amsl.com (Postfix) with ESMTP id 167E93A689B for <6lowapp@ietf.org>; Wed, 30 Dec 2009 09:11:58 -0800 (PST) Received: by qyk41 with SMTP id 41so5721972qyk.29 for <6lowapp@ietf.org>; Wed, 30 Dec 2009 09:11:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=/51xwCy4yZqrNVJvM2o1Nd0VIgmdjZhoPgUEyWBJQBU=; b=Eg/rq21BQ8p8Crsy7awLT0cpO2dE2Wst7O2zvS1hoyLNzlvWmC0TtSqwv96VFz5Zw+ +vjBc+vfUXkqgQuRRKEtdJ6Mun8g3me/fnvvtNK1xT/MwmfTe+cXwe0Xgsxr9UszIW/T hl5/mcU0aFF4fQh3Ffk3qf3LWLcD0P4Sgc2g0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=FzZmb1ckH6evN9Rh/xl5RXynHBcgju5GqmNKtmlri3X2Sv2bnG+cKNz4xFaOWTBL9W g38O5p2MoZcdctmiHHTVhQBSMEW88Pl18ve/s2PPFtM1CkHfc/60B1uVamFr7+8TsUSA nwIzf2bIjdVAFvUfd/MHxE4Ep/jT+gfeBn94E= MIME-Version: 1.0 Received: by 10.229.4.196 with SMTP id 4mr4167128qcs.101.1262193094930; Wed, 30 Dec 2009 09:11:34 -0800 (PST) Date: Wed, 30 Dec 2009 12:11:34 -0500 Message-ID: <9e4733910912300911m513f7826uc29d2b6e2abc132e@mail.gmail.com> From: Jon Smirl To: 6lowapp@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Subject: [6lowapp] Reference implementation 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: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Dec 2009 17:12:02 -0000 What are the plans for a 6lowapp reference implementation? For example there is a 6lowpan implementation in Contiki, but nobody is updating it to track the current proposals. Does a ROLL reference implementation exist? -- Jon Smirl jonsmirl@gmail.com From jmamodio@gmail.com Wed Dec 30 09:50:58 2009 Return-Path: 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 9F3223A6846 for <6lowapp@core3.amsl.com>; Wed, 30 Dec 2009 09:50:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.145 X-Spam-Level: X-Spam-Status: No, score=-3.145 tagged_above=-999 required=5 tests=[AWL=-0.546, BAYES_00=-2.599] 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 mMduNupIyNIz for <6lowapp@core3.amsl.com>; Wed, 30 Dec 2009 09:50:57 -0800 (PST) Received: from mail-px0-f179.google.com (mail-px0-f179.google.com [209.85.216.179]) by core3.amsl.com (Postfix) with ESMTP id B5BA93A682A for <6lowapp@ietf.org>; Wed, 30 Dec 2009 09:50:57 -0800 (PST) Received: by pxi9 with SMTP id 9so9563070pxi.32 for <6lowapp@ietf.org>; Wed, 30 Dec 2009 09:50:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=kEyPfS3lZs0DI/oX7VCLhzgWoNjfWu0fPG29CiqO0oI=; b=jLMPeb2iogVsjGdrWfxpgjG9ieJpNaVkdhLs88d5jlUJY0fBlBKsHT9xEeJPBcZcat AEwmEIllmXIvYDYX5LAcluJqkO4Att9iOqn9UU8G0sCY28JGBrYnzddEKofCysVXez6o v96sNXMIeJ0UpAZ+TDkylG7NIhH/dQG+ENgIU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=nTqqrUUSMMPTAKTcuwBBIC5YtbhA9rhM/E3KJbO0WBy0HnZS7bw4v6nUxtOm2UoK2e MIEfQlMlkEdC/RhXIf3zU1eRpck3ShGtHytyDFm9sWNyf5MVU0AE556JFad5J1soC+J5 ICn6GIrkLSvlSLg/qMlIJ+IYLzbyqeX42OSyo= MIME-Version: 1.0 Received: by 10.142.75.15 with SMTP id x15mr526430wfa.152.1262195435578; Wed, 30 Dec 2009 09:50:35 -0800 (PST) In-Reply-To: <9e4733910912300911m513f7826uc29d2b6e2abc132e@mail.gmail.com> References: <9e4733910912300911m513f7826uc29d2b6e2abc132e@mail.gmail.com> Date: Wed, 30 Dec 2009 11:50:35 -0600 Message-ID: <202705b0912300950x41be9b9dgf5e6da59f8548f0@mail.gmail.com> From: Jorge Amodio To: Jon Smirl Content-Type: text/plain; charset=ISO-8859-1 Cc: 6lowapp@ietf.org Subject: Re: [6lowapp] Reference implementation 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: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Dec 2009 17:50:58 -0000 I second Jon's question, I'm planning to put together a reference implementation using a Microchip MCU and MRF24J40 but besides Contiki, ArchRock and few more incomplete efforts it's hard to find an active open reference implementation. Any pointers ? suggestions ? Regards Jorge On Wed, Dec 30, 2009 at 11:11 AM, Jon Smirl wrote: > What are the plans for a 6lowapp reference implementation? > > For example there is a 6lowpan implementation in Contiki, but nobody > is updating it to track the current proposals. > Does a ROLL reference implementation exist? > > -- > Jon Smirl > jonsmirl@gmail.com From brian.tridium@gmail.com Wed Dec 30 10:14:37 2009 Return-Path: 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 BCFB73A698F for <6lowapp@core3.amsl.com>; Wed, 30 Dec 2009 10:14:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] 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 OtkGMc6Pwm0s for <6lowapp@core3.amsl.com>; Wed, 30 Dec 2009 10:14:36 -0800 (PST) Received: from mail-bw0-f223.google.com (mail-bw0-f223.google.com [209.85.218.223]) by core3.amsl.com (Postfix) with ESMTP id 5084E3A6972 for <6lowapp@ietf.org>; Wed, 30 Dec 2009 10:14:36 -0800 (PST) Received: by bwz23 with SMTP id 23so7880225bwz.29 for <6lowapp@ietf.org>; Wed, 30 Dec 2009 10:14:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=R0d5csQOeij/OnHI0uqhEfpz0HnKM5mszyT1v4OD6wU=; b=GWmM8m66c0/m8MidxY0Ajuah6CLXF+dsXVIBapH1qDEV56LgJKsPJZJSVLv/m7l+uQ jiTW8t1KgyIJwsHm+NRKVvFR5NJh4tpap0CCecekxbdyq91mTg7gWJ0auZGHFHWn78tA jaNeEl8WaR31fUkpzYkI1LXlJzv7RD80axM4w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=j9b2Hn3jibMBcu/t3W47NeqYjj4XTcPKqrOWhmpWRQnQ7NIbhBMlGqKxnlXs53+Dl5 Wmdd1x0pTjl1KH3SYZTBA+0F3Qla4TlAMLC+B5cFwXeW6fgswy9lDFJq75rlmKrwTd0x LBKRfSYz41KJm0FT1qfR7VUASi1U5FYwvSHr4= MIME-Version: 1.0 Received: by 10.204.14.74 with SMTP id f10mr1341420bka.5.1262196852448; Wed, 30 Dec 2009 10:14:12 -0800 (PST) In-Reply-To: <202705b0912300950x41be9b9dgf5e6da59f8548f0@mail.gmail.com> References: <9e4733910912300911m513f7826uc29d2b6e2abc132e@mail.gmail.com> <202705b0912300950x41be9b9dgf5e6da59f8548f0@mail.gmail.com> Date: Wed, 30 Dec 2009 13:14:12 -0500 Message-ID: <7b191a110912301014h8fa4b60n55af83d6eebbe72a@mail.gmail.com> From: Brian Frank To: Jorge Amodio Content-Type: multipart/alternative; boundary=0003255581fa06defe047bf61b35 Cc: 6lowapp@ietf.org Subject: Re: [6lowapp] Reference implementation 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: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Dec 2009 18:14:37 -0000 --0003255581fa06defe047bf61b35 Content-Type: text/plain; charset=ISO-8859-1 It is likely that Tridium will build an open source implementation of CoAP as part of their Sedona framework project (http://sedonadev.org/index.html). Note Sedona's 6LoWPAN stack is *not* open source (they use Jennic's stack), but the CoAP protocol likely will be open source. On Wed, Dec 30, 2009 at 12:50 PM, Jorge Amodio wrote: > I second Jon's question, I'm planning to put together a reference > implementation > using a Microchip MCU and MRF24J40 but besides Contiki, ArchRock and few > more incomplete efforts it's hard to find an active open reference > implementation. > > Any pointers ? suggestions ? > > Regards > Jorge > > On Wed, Dec 30, 2009 at 11:11 AM, Jon Smirl wrote: > > What are the plans for a 6lowapp reference implementation? > > > > For example there is a 6lowpan implementation in Contiki, but nobody > > is updating it to track the current proposals. > > Does a ROLL reference implementation exist? > > > > -- > > Jon Smirl > > jonsmirl@gmail.com > _______________________________________________ > 6lowapp mailing list > 6lowapp@ietf.org > https://www.ietf.org/mailman/listinfo/6lowapp > --0003255581fa06defe047bf61b35 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable It is likely that Tridium will build an open source implementation of CoAP = as part of their Sedona framework project (http://sedonadev.org/index.html). =A0Note Sedona's 6LoW= PAN stack is *not* open source (they use Jennic's stack), but the CoAP = protocol likely will be open source.

On Wed, Dec 30, 2009 at 12:50 PM, Jorge Amod= io <jmamodio@gma= il.com> wrote:
I second Jon's question, I'm planning to put together a reference i= mplementation
using a Microchip MCU and MRF24J40 but besides Contiki, ArchRock and few more incomplete efforts it's hard to find an active open reference
implementation.

Any pointers ? suggestions ?

Regards
Jorge

On Wed, Dec 30, 2009 at 11:11 AM, Jon Smirl <jonsmirl@gmail.com> wrote:
> What are the plans for a 6lowapp reference implementation?
>
> For example there is a 6lowpan implementation in Contiki, but nobody > is updating it to track the current proposals.
> Does a ROLL reference implementation exist?
>
> --
> Jon Smirl
> jonsmirl@gmail.com
_______________________________________________
6lowapp mailing list
6lowapp@ietf.org
https://www.ietf.org/mailman/listinfo/6lowapp

--0003255581fa06defe047bf61b35-- From jonsmirl@gmail.com Wed Dec 30 10:37:21 2009 Return-Path: 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 5F4DE3A6824 for <6lowapp@core3.amsl.com>; Wed, 30 Dec 2009 10:37:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.166 X-Spam-Level: X-Spam-Status: No, score=-2.166 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599] 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 nrhM1zgjBALh for <6lowapp@core3.amsl.com>; Wed, 30 Dec 2009 10:37:20 -0800 (PST) Received: from mail-qy0-f203.google.com (mail-qy0-f203.google.com [209.85.221.203]) by core3.amsl.com (Postfix) with ESMTP id E5DEC3A659A for <6lowapp@ietf.org>; Wed, 30 Dec 2009 10:37:19 -0800 (PST) Received: by qyk41 with SMTP id 41so5750347qyk.29 for <6lowapp@ietf.org>; Wed, 30 Dec 2009 10:36:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=nM094CwupgU7xssGuLBAyusTPVezNWj/2907j9mpKkw=; b=MrnaHJrjO8iTzP5p7Sh6pO7XuEcp+MFFYh/AxycLG3NWcDH2LqTGSBBGMlIQzoRM/e 7pXAX3u6dxTyaI2p36zk+XebLs40CcxsEVsW50ceRMzEXBgS0bAHORMKYzBw01fHcspw xhHtFA9orIjJ4aVDkV48W5DJzX1QwRjX2/go4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Ju83shL63WO2Sk7IzgXXaCyDs1q3RYKDtQ10gymyw9TbR+uB7z3PuNM/fhRLO1/jyI /tCwYjlrDBZn88fC09y6669oShDJFJr7qj0KtLNR5rkrl7q7kNrKholSuYmEDQq0du1q LpIEs0HBCWxaEZ3Tq2Q+42+bxEmrDYMt5tgAo= MIME-Version: 1.0 Received: by 10.229.49.132 with SMTP id v4mr4459910qcf.50.1262198215465; Wed, 30 Dec 2009 10:36:55 -0800 (PST) In-Reply-To: <202705b0912300950x41be9b9dgf5e6da59f8548f0@mail.gmail.com> References: <9e4733910912300911m513f7826uc29d2b6e2abc132e@mail.gmail.com> <202705b0912300950x41be9b9dgf5e6da59f8548f0@mail.gmail.com> Date: Wed, 30 Dec 2009 13:36:55 -0500 Message-ID: <9e4733910912301036s343176c4gf76127d42c134ad2@mail.gmail.com> From: Jon Smirl To: Jorge Amodio Content-Type: text/plain; charset=ISO-8859-1 Cc: 6lowapp@ietf.org Subject: Re: [6lowapp] Reference implementation 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: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Dec 2009 18:37:21 -0000 On Wed, Dec 30, 2009 at 12:50 PM, Jorge Amodio wrote: > I second Jon's question, I'm planning to put together a reference implementation > using a Microchip MCU and MRF24J40 but besides Contiki, ArchRock and few > more incomplete efforts it's hard to find an active open reference > implementation. In my past experiences an open reference implementation makes the standardization process go much faster and the end result is way more compatible. This is no way implies that companies aren't free to do closed implementations also. 6lowapp could be developed as a user space program using sockets until everything is sorted out. Then take the core code and port it into the devices. Building ten different implementations of this code doesn't benefit anyone since it introduces compatibility problems. Compatibility problems are extremely expensive to fix once they get into the customer's hands. The idea is to sell finished devices not dev tools. Expanding the market through compatibility maximizes the volume of devices sold. Look at the mess Zigbee is in. The Zigbee IP license is GPL incompatible. Every one of those little home routers run Linux. The Zigbee license makes it impossible to build a simple Linux based router with a SPI connected 802.15.4 radio in it. I picked Contiki because it already has a working TCP stack both IPv4 and IPv6. It has been ported to these CPUs: 6502 arm at91sam7s avr cc2430 mc1322x msp430 x86 z80 It isn't hard to port it to other CPUs. The license has almost no restrictions other than leaving the copyright notice in. My hardware is based on the mc13224. I have a little IPv6/6lowpan web server running on it under Contiki. I'll share my code. Here's a cheap place to get mc13224 hardware (i bought my dev hardware there). http://www.redwirellc.com/store/ There is also a USB stick with integrated JTAG (ft2232) that will be coming out soon. > > Any pointers ? suggestions ? > > Regards > Jorge > > On Wed, Dec 30, 2009 at 11:11 AM, Jon Smirl wrote: >> What are the plans for a 6lowapp reference implementation? >> >> For example there is a 6lowpan implementation in Contiki, but nobody >> is updating it to track the current proposals. >> Does a ROLL reference implementation exist? >> >> -- >> Jon Smirl >> jonsmirl@gmail.com > -- Jon Smirl jonsmirl@gmail.com