Re: [RSN] Update
"Timothy J. Salo" <salo@saloits.com> Sun, 03 June 2007 20:50 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 1Hux22-0004sl-Py; Sun, 03 Jun 2007 16:50:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hux20-0004rU-LA for rsn@ietf.org; Sun, 03 Jun 2007 16:50:32 -0400
Received: from saloits.com ([208.42.140.127] helo=newbsd.saloits.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hux1y-00074o-7V for rsn@ietf.org; Sun, 03 Jun 2007 16:50:32 -0400
Received: from [127.0.0.1] (saloits.com [208.42.140.127]) by newbsd.saloits.com (8.13.1/8.13.1) with ESMTP id l53KoKep080418 for <rsn@ietf.org>; Sun, 3 Jun 2007 15:50:27 -0500 (CDT) (envelope-from salo@saloits.com)
Message-ID: <46632986.3000401@saloits.com>
Date: Sun, 03 Jun 2007 15:50:14 -0500
From: "Timothy J. Salo" <salo@saloits.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: rsn@ietf.org
Subject: Re: [RSN] Update
References: <023E7560-E91C-4805-9EA0-90F8EA3874EA@cisco.com>
In-Reply-To: <023E7560-E91C-4805-9EA0-90F8EA3874EA@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
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
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: "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.) -tjs _______________________________________________ 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