Re: [RSN] Update
"Cuda Alberto" <alberto.cuda@telecomitalia.it> Tue, 05 June 2007 08:03 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 1HvU0Y-0002Bx-FX; Tue, 05 Jun 2007 04:03:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HvU0Y-0002Bp-4e for RSN@ietf.org; Tue, 05 Jun 2007 04:03:14 -0400
Received: from mailf.telecomitalia.it ([156.54.233.32]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HvU0V-0003K4-M8 for RSN@ietf.org; Tue, 05 Jun 2007 04:03:14 -0400
Received: from ptpxch008ba020.idc.cww.telecomitalia.it ([156.54.240.51]) by mailf.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830); Tue, 5 Jun 2007 10:03:10 +0200
Received: from PTPEVS108BA020.idc.cww.telecomitalia.it ([156.54.241.227]) by ptpxch008ba020.idc.cww.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830); Tue, 5 Jun 2007 10:03:10 +0200
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
Importance: normal
Priority: normal
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [RSN] Update
Date: Tue, 05 Jun 2007 10:03:10 +0200
Message-ID: <9E577E61D0108D4F8CD482029B613F5C302A9B@PTPEVS108BA020.idc.cww.telecomitalia.it>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [RSN] Update
thread-index: AcenPRvvGg0mjqs4Tzq1Kl3AuEdoPAAAMYCQAAI5CJg=
References: <46643FFE.1040400@telecomitalia.it> <466445C0.9040307@telecomitalia.it> <9E577E61D0108D4F8CD482029B613F5C302A99@PTPEVS108BA020.idc.cww.telecomitalia.it> <F1E1B8678B20F44CACBFCCA41A728543012C554A@PTPEVS108BA020.idc.cww.telecomitalia.it>
From: Cuda Alberto <alberto.cuda@telecomitalia.it>
To: RSN@ietf.org
X-OriginalArrivalTime: 05 Jun 2007 08:03:10.0564 (UTC) FILETIME=[F5704240:01C7A747]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc:
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 all, This e-mail just to state that Telecom Italia welcomes a solution of the issues listed in the scope of this initiative. In particular Telecom Italia would like to see a smooth and fruitful integration of the IP layer with existing layer 2 protocols to enrich the IP devices' ecosystem once a suitable routing protocol has been developed. Telecom Italia welcomes a solution which is well harmonized with existing standards for Wireless Sensor Networks, in particular ZigBee. The solution should also envisage for a network comprising sleeping routers, i.e. nodes having routing facility and comprising a radio transceiver that is intermittently operating (typically battery powered). Cheers. Alberto. > 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. -------------------------------------------------------------------- CONFIDENTIALITY NOTICE This message and its attachments are addressed solely to the persons above and may contain confidential information. If you have received the message in error, be informed that any use of the content hereof is prohibited. Please return it immediately to the sender and delete the message. Should you have any questions, please contact us by replying to webmaster@telecomitalia.it. Thank you www.telecomitalia.it -------------------------------------------------------------------- _______________________________________________ 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