Re: [RSN] Update
Anthony Schoofs <anthony.schoofs@philips.com> Wed, 06 June 2007 14: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 1HvwQ8-0004nM-0k; Wed, 06 Jun 2007 10:23:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HvwQ6-0004n7-Gs for rsn@ietf.org; Wed, 06 Jun 2007 10:23:30 -0400
Received: from gw-eur4.philips.com ([161.85.125.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HvwQ5-0005tg-Qb for rsn@ietf.org; Wed, 06 Jun 2007 10:23:30 -0400
Received: from smtpscan-eur8.philips.com (smtpscan-eur8.mail.philips.com [130.144.57.173]) by gw-eur4.philips.com (Postfix) with ESMTP id A774649730; Wed, 6 Jun 2007 14:23:28 +0000 (UTC)
Received: from smtpscan-eur8.philips.com (localhost [127.0.0.1]) by localhost.philips.com (Postfix) with ESMTP id 2D6836D4; Wed, 6 Jun 2007 14:23:28 +0000 (GMT)
Received: from smtprelay-eur2.philips.com (smtprelay-eur2.philips.com [130.144.57.171]) by smtpscan-eur8.philips.com (Postfix) with ESMTP id 129596CC; Wed, 6 Jun 2007 14:23:28 +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 55586A9; Wed, 6 Jun 2007 14:23:27 +0000 (GMT)
In-Reply-To: <OFB2BC8BD9.C98B8CFB-ONC12572F0.00343C6D-C12572F0.00373EF4@philips.com>
To: Anthony Schoofs <anthony.schoofs@philips.com>
Subject: Re: [RSN] Update
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.0.3 September 26, 2003
Message-ID: <OF88D27330.F5A4BB25-ONC12572F2.004D4C6F-C12572F2.004EA42A@philips.com>
From: Anthony Schoofs <anthony.schoofs@philips.com>
Date: Wed, 06 Jun 2007 16:21:05 +0200
X-MIMETrack: Serialize by Router on ehvrmh02/H/SERVER/PHILIPS(Release 6.5.5HF1002 | November 23, 2006) at 06/06/2007 16:25:34, Serialize complete at 06/06/2007 16:25:34
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 65215b440f7ab00ca9514de4a7a89926
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="===============1105545604=="
Errors-To: rsn-bounces@ietf.org
JP, I agree when you said in a previous email: > "the proposal is to design a IP routing solution > specifically for sensor networks, that would of course be independent > to the L1/L2 protocol in use (it may be desirable to take into account > link layer attributes when calculating a route but the routing process > would not be tied up with the link layer). In addition, our routing scheme should know when the PAN coordinator/Gateway location has changed to lower and balance the network energy consumption. Then new timezones can be assigned and data routed accordingly. I am looking forward to seeing this new WG formed, Best regards, Anthony. -- Anthony Schoofs Philips Research WY 7-038 High Tech Campus 37 , 5656 AE Eindhoven, The Netherlands Email: anthony.schoofs@philips.com Anthony Schoofs 04-06-2007 12:06 To JP Vasseur <jvasseur@cisco.com> cc rsn@ietf.org Subject Re: [RSN] Update Classification 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
_______________________________________________ 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