Re: [RSN] Update
Mark Townsley <townsley@cisco.com> Sun, 03 June 2007 21:16 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 1HuxRS-0004eQ-Td; Sun, 03 Jun 2007 17:16:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HuxRR-0004Yo-4i; Sun, 03 Jun 2007 17:16:49 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HuxRQ-0001xW-9d; Sun, 03 Jun 2007 17:16:49 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 03 Jun 2007 17:16:48 -0400
X-IronPort-AV: i="4.16,378,1175486400"; d="scan'208"; a="122679267:sNHT46819934"
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 l53LGlM1017769; Sun, 3 Jun 2007 17:16:47 -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 l53LGh5f018841; Sun, 3 Jun 2007 21:16:43 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 17:16:43 -0400
Received: from [10.83.1.98] ([10.83.1.98]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 3 Jun 2007 17:16:42 -0400
Message-ID: <46632FB9.6080705@cisco.com>
Date: Sun, 03 Jun 2007 23:16:41 +0200
From: Mark Townsley <townsley@cisco.com>
User-Agent: Thunderbird 1.5.0.12 (Macintosh/20070509)
MIME-Version: 1.0
To: "Timothy J. Salo" <salo@saloits.com>
Subject: Re: [RSN] Update
References: <023E7560-E91C-4805-9EA0-90F8EA3874EA@cisco.com> <46632986.3000401@saloits.com>
In-Reply-To: <46632986.3000401@saloits.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 03 Jun 2007 21:16:43.0177 (UTC) FILETIME=[7BF0F190:01C7A624]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2126; t=1180905408; x=1181769408; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=townsley@cisco.com; z=From:=20Mark=20Townsley=20<townsley@cisco.com> |Subject:=20Re=3A=20[RSN]=20Update |Sender:=20 |To:=20=22Timothy=20J.=20Salo=22=20<salo@saloits.com>; bh=qTwwHhviIRIG/qDj8bcSUlBDjuHrB7v8oWCaP4zQs7o=; b=U2F2JcCkq4aDz8bsh8LUnWZE/UY2WJ5R93v9mZyLj1CL2wClJY0V31vCP1upBFZe0vhh3W+8 cV6YEBBldOwcJeXO2RUzegnBGG3kBq5m0jm1fXnImGESIZOQQtMcA/MJ;
Authentication-Results: rtp-dkim-1; header.From=townsley@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
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
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. > > "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.) I agree that this is an important topic that should be part of both charters. - 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
- 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