Re: [RSN] Update

Anthony Schoofs <anthony.schoofs@philips.com> Mon, 04 June 2007 10:04 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 1Hv9Pv-0000jF-Hx; Mon, 04 Jun 2007 06:04:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hv9Pu-0000j9-Ek for rsn@ietf.org; Mon, 04 Jun 2007 06:04:02 -0400
Received: from gw-eur4.philips.com ([161.85.125.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hv9Pt-0007gZ-Rj for rsn@ietf.org; Mon, 04 Jun 2007 06:04:02 -0400
Received: from smtpscan-eur5.philips.com (smtpscan-eur5.mail.philips.com [130.144.57.168]) by gw-eur4.philips.com (Postfix) with ESMTP id 1D0D749712; Mon, 4 Jun 2007 10:04:01 +0000 (UTC)
Received: from smtpscan-eur5.philips.com (localhost [127.0.0.1]) by localhost.philips.com (Postfix) with ESMTP id DDA68619; Mon, 4 Jun 2007 10:04:00 +0000 (GMT)
Received: from smtprelay-eur2.philips.com (smtprelay-eur2.philips.com [130.144.57.171]) by smtpscan-eur5.philips.com (Postfix) with ESMTP id B63E13EE; Mon, 4 Jun 2007 10:04:00 +0000 (GMT)
Received: from ehvrmh02.diamond.philips.com (ehvrmh02-srv.diamond.philips.com [130.139.27.125]) by smtprelay-eur2.philips.com (Postfix) with ESMTP id 96E228E; Mon, 4 Jun 2007 10:04:00 +0000 (GMT)
In-Reply-To: <023E7560-E91C-4805-9EA0-90F8EA3874EA@cisco.com>
To: JP Vasseur <jvasseur@cisco.com>
Subject: Re: [RSN] Update
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.0.3 September 26, 2003
Message-ID: <OFB2BC8BD9.C98B8CFB-ONC12572F0.00343C6D-C12572F0.00373EF4@philips.com>
From: Anthony Schoofs <anthony.schoofs@philips.com>
Date: Mon, 04 Jun 2007 12:06:04 +0200
X-MIMETrack: Serialize by Router on ehvrmh02/H/SERVER/PHILIPS(Release 6.5.5HF1002 | November 23, 2006) at 04/06/2007 12:06:05, Serialize complete at 04/06/2007 12:06:05
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 93df555cbdbcdae9621e5b95d44b301e
Cc: rsn@ietf.org
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>
Content-Type: multipart/mixed; boundary="===============0496628291=="
Errors-To: rsn-bounces@ietf.org

We did some work to schedule a coordinate switching on and off of sensor 
nodes in order to reduce at maximum the energy consumption of the network.
We came up with a routing protocol that allows us to route data throughout 
 the network according to the ON/OFF state of the nodes.

We would like to provide input for an ID on routing schemes that have 
energy consumption as the first focus.

Best regards,
Anthony.

--
Anthony Schoofs
Philips Research
High Tech Campus 37 , 5656 AE Eindhoven, The Netherlands
Email: anthony.schoofs@philips.com









JP Vasseur <jvasseur@cisco.com> 
03-06-2007 14:02

To
rsn@ietf.org
cc

Subject
[RSN] Update
Classification







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

_______________________________________________
RSN mailing list
RSN@ietf.org
https://www1.ietf.org/mailman/listinfo/rsn