Re: [RSN] Industrial
Zach Shelby <zach.shelby@sensinode.com> Mon, 04 June 2007 05:23 UTC
Return-path: <rsn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hv52W-00023X-MU; Mon, 04 Jun 2007 01:23:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hv52V-00022M-65 for rsn@ietf.org; Mon, 04 Jun 2007 01:23:35 -0400
Received: from auth-smtp.nebula.fi ([217.30.180.105]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hv52T-0004nI-M6 for rsn@ietf.org; Mon, 04 Jun 2007 01:23:35 -0400
Received: from s-cwc-pc199.local (addr-213-139-165-97.baananet.fi [213.139.165.97]) (authenticated bits=0) by auth-smtp.nebula.fi (8.13.4/8.13.4) with ESMTP id l544tLLB008470 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <rsn@ietf.org>; Mon, 4 Jun 2007 07:55:22 +0300
Message-ID: <4663A1D0.2000406@sensinode.com>
Date: Mon, 04 Jun 2007 08:23:28 +0300
From: Zach Shelby <zach.shelby@sensinode.com>
User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326)
MIME-Version: 1.0
To: rsn@ietf.org
Subject: Re: [RSN] Industrial
References: <023E7560-E91C-4805-9EA0-90F8EA3874EA@cisco.com>
In-Reply-To: <023E7560-E91C-4805-9EA0-90F8EA3874EA@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
X-BeenThere: rsn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Sensor Networks <rsn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rsn>, <mailto:rsn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/rsn>
List-Post: <mailto:rsn@ietf.org>
List-Help: <mailto:rsn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rsn>, <mailto:rsn-request@ietf.org?subject=subscribe>
Errors-To: rsn-bounces@ietf.org
Hi, I would like to contribute to the Industrial application-specific ID. - Zach JP Vasseur wrote: > Dear all, > > Here is an update on where we stand: good progress ! > > 1) We've been having quite a bit of off-line and on-line discussions and > there is apparently a good level of interest in this work. > There are currently 5 IDs in the works: > * The generic routing requirements: draft-culler-rsn-routing-reqs > * Two application-specific routing requirements: > - Home Networking > - Industrial > * A problem statement > * An ID on routing metrics > > Of course, if you're interested to work on these IDs or other items, > feel free ! > > 2) New name > Although we called this initiative RSN: Routing for Sensor Networks, it > does apply more generally to constrained nodes (Low Power) > operating in Lossy Networks. Objects in general would typically be part > of those networks. So from now on, let's rename this work > R2LN: "Routing issues for Low Power, Lossy Networks", and use that > acronym in all IDs. > > 3) Next IETF > We asked for a presentation slot for the next IETF. Depending on the > feedback, the next step would then to request a BOF in Vancouver. > > Thanks. > > JP and David. > > _______________________________________________ > RSN mailing list > RSN@ietf.org > https://www1.ietf.org/mailman/listinfo/rsn -- Zach Shelby | Managing Director | +358 40 7796297 Sensinode Ltd. www.sensinode.com _______________________________________________ RSN mailing list RSN@ietf.org https://www1.ietf.org/mailman/listinfo/rsn
- Re: [RSN] Update Cuda Alberto
- [RSN] Update JP Vasseur
- Fwd: [RSN] Update JP Vasseur
- Re: [RSN] Update Timothy J. Salo
- Re: [RSN] Update Mark Townsley
- Re: [RSN] Update JP Vasseur
- Re: [RSN] Industrial Zach Shelby
- Re: [RSN] Update Anthony Schoofs
- RE: [RSN] Update dculler
- Re: [RSN] Update Traian MUNTEAN
- Re: [RSN] Update Timothy J. Salo
- RE: [RSN] Update Anders Brandt
- Re: [RSN] Update JP Vasseur
- Re: [RSN] Update Anthony Schoofs
- [RSN] The need for RSN Geoff Mulligan
- Re: [RSN] The need for RSN Dominik Kaspar
- Re: [RSN] Update Philip Levis
- [RSN] Update JP Vasseur
- Re: [RSN] Update JP Vasseur
- [RSN] Update JP Vasseur