Fwd: [RSN] Update
JP Vasseur <jvasseur@cisco.com> Sun, 03 June 2007 20:33 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 1HuwlF-0002jb-JZ; Sun, 03 Jun 2007 16:33:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HuwlD-0002YP-WE for rsn@ietf.org; Sun, 03 Jun 2007 16:33:12 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HuwlC-0005XO-Ga for rsn@ietf.org; Sun, 03 Jun 2007 16:33:11 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 03 Jun 2007 16:33:10 -0400
X-IronPort-AV: i="4.16,378,1175486400"; d="scan'208,217"; a="61831353:sNHT334339496"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l53KX9bB011153 for <rsn@ietf.org>; Sun, 3 Jun 2007 16:33:09 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l53KX15j013847 for <rsn@ietf.org>; Sun, 3 Jun 2007 20:33:09 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 3 Jun 2007 16:33:03 -0400
Received: from [10.86.104.179] ([10.86.104.179]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 3 Jun 2007 16:33:03 -0400
Mime-Version: 1.0 (Apple Message framework v752.2)
To: rsn@ietf.org
Message-Id: <28107EC3-7BBC-4299-BF9E-39A2BA298C11@cisco.com>
References: <023E7560-E91C-4805-9EA0-90F8EA3874EA@cisco.com>
From: JP Vasseur <jvasseur@cisco.com>
Subject: Fwd: [RSN] Update
Date: Sun, 03 Jun 2007 16:31:49 -0400
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 03 Jun 2007 20:33:03.0283 (UTC) FILETIME=[625CD830:01C7A61E]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=8790; t=1180902789; x=1181766789; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jvasseur@cisco.com; z=From:=20JP=20Vasseur=20<jvasseur@cisco.com> |Subject:=20Fwd=3A=20[RSN]=20Update |Sender:=20 |To:=20rsn@ietf.org; bh=kSb94ibrYBPZa3CJQCBilYE8/8zPijbrE0yFvruvEi8=; b=VGMwz9Us8G2EHFUFcDOs+naMNcmmfP26oz7/lIvEitzocZtaq84a2EM7lXZcJHXGDY2y+chN wvLUf7binUEOexNreeuMMymP9xFfo1DOJ1IpdMbi7jAUJ3iEXljV5Ntx;
Authentication-Results: rtp-dkim-1; header.From=jvasseur@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
X-Spam-Score: 0.2 (/)
X-Scan-Signature: d890c9ddd0b0a61e8c597ad30c1c2176
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="===============1144355250=="
Errors-To: rsn-bounces@ietf.org
Begin forwarded message: > From: JP Vasseur <jvasseur@cisco.com> > Date: June 3, 2007 8:02:45 AM EDT > To: rsn@ietf.org > Subject: [RSN] Update > > 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", It should actually read RL2N: "Routing issues for Low power, Lossy Networks" Thanks. JP. > 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
- 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