Re: [RSN] Update
JP Vasseur <jvasseur@cisco.com> Sun, 03 June 2007 22:07 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 1HuyE4-0003K0-0I; Sun, 03 Jun 2007 18:07:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HuyE2-0003Js-7e; Sun, 03 Jun 2007 18:07:02 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HuyE1-0007Xb-UL; Sun, 03 Jun 2007 18:07:02 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 03 Jun 2007 18:07:00 -0400
X-IronPort-AV: i="4.16,378,1175486400"; d="scan'208"; a="122680616:sNHT49884948"
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 l53M6xtJ026791; Sun, 3 Jun 2007 18:06:59 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l53M6x5f025316; Sun, 3 Jun 2007 22:06:59 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 3 Jun 2007 18:06:59 -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 18:06:58 -0400
In-Reply-To: <46632FB9.6080705@cisco.com>
References: <023E7560-E91C-4805-9EA0-90F8EA3874EA@cisco.com> <46632986.3000401@saloits.com> <46632FB9.6080705@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <5B8C1A92-0FC1-4627-8F08-AE189D00078C@cisco.com>
Content-Transfer-Encoding: 7bit
From: JP Vasseur <jvasseur@cisco.com>
Subject: Re: [RSN] Update
Date: Sun, 03 Jun 2007 18:06:26 -0400
To: Mark Townsley <townsley@cisco.com>, "Timothy J. Salo" <salo@saloits.com>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 03 Jun 2007 22:06:58.0969 (UTC) FILETIME=[817E4890:01C7A62B]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2838; t=1180908419; x=1181772419; 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:=20Re=3A=20[RSN]=20Update |Sender:=20 |To:=20Mark=20Townsley=20<townsley@cisco.com>, =20=22Timothy=20J.=20Salo=2 2=20<salo@saloits.com>; bh=EghmwqmZ5lRcfca+J7Tqtuzd1tie/JDCEQx7xrpocNo=; b=j0+vJsj0kC5nFgGD5Z6cOL2+kCqidN46gEm3Ep96LUDK8RCP9gbPxl4u8p7XYzkuNW8DhzOE 0Ul+AElmwUnDj5SZ4OJ1lA9wIEFhyQku0dzoSQy6uCjkLe2V25jurLfJ;
Authentication-Results: rtp-dkim-1; header.From=jvasseur@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: rsn@ietf.org, 6lowpan@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>
Errors-To: rsn-bounces@ietf.org
Hi, On Jun 3, 2007, at 5:16 PM, Mark Townsley wrote: > Timothy J. Salo wrote: >> JP Vasseur wrote: >>> 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. >> >> I suggest that "Routing Issues in Low-Power Wireless Networks" >> might be more descriptive. >> >> "Wireless" implies "lossy". "Wireless" also implies a variety >> of other behaviors, such as a limited-range broadcast (usually), >> and a variety of others. >> >> I doubt that we will spend any time at all thinking about >> low power wired networks. >> >> "Low-Power" sounds better than "Resource-Constrained", although >> the latter might be more descriptive. >> >> And finally, to do the job well, this group must look at more >> than just routing issues (e.g., neighbor discovery and management >> in low-power wireless networks). We might consider: > This part should be part of the 6lowpan recharter. The idea amongst > the ADs has been to split off the routing portion of the work on > low-power networks to the routing area, and continue forward with > work on ND, bootstrapping, etc. within the int-area. Indeed ... By the way this gives the opportunity to re-enforce the fact that this initiative deals with routing issues *only*. If we need additional specifications for the routing that do not deal with pure routing issues, then we need to ask to 6lowpan indeed. >> >> "Internetworking Issues in Low-Power Wireless Networks" >> >> or >> >> "Internetworking Issues in Resource-Constrained Wireless Networks" >> >> or even >> >> "Internetworking Issues in Resource-Constrained Networks" (I2RCN) >> >> One (non-trivial) advantage of "Internetworking" is that it >> helps answer the question: Why should the IETF (e.g., rather than >> the IEEE) be interested in this work? (Assuming that we think >> about how low-power wireless networks should be interconnected >> with the Internet.) Because I think that these devices will soon be part of the Internet ;-) Quite seriously. And we need to keep the word Routing here. > I agree that this is an important topic that should be part of both > charters. > Thanks. JP. > - Mark >> >> -tjs >> >> >> _______________________________________________ >> 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