IETF Logo Mail Archive

[RSN] The need for RSN

Geoff Mulligan <geoff-ietf@mulligan.org> Thu, 07 June 2007 20:57 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 1HwP39-0003xa-SG; Thu, 07 Jun 2007 16:57:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HwP38-0003wy-4h for rsn@ietf.org; Thu, 07 Jun 2007 16:57:42 -0400
Received: from grab.coslabs.com ([199.233.92.34]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwP36-0007Dl-Qf for rsn@ietf.org; Thu, 07 Jun 2007 16:57:42 -0400
Received: from [199.233.92.20] (dev20.coslabs.com [199.233.92.20]) by grab.coslabs.com (8.13.6/8.13.6) with ESMTP id l57KvQmF001156; Thu, 7 Jun 2007 14:57:26 -0600 (MDT)
From: Geoff Mulligan <geoff-ietf@mulligan.org>
To: JP Vasseur <jvasseur@cisco.com>
In-Reply-To: <D291504E-9D23-4D2A-B5D5-A88976104AE4@cisco.com>
References: <023E7560-E91C-4805-9EA0-90F8EA3874EA@cisco.com> <46632986.3000401@saloits.com> <46632FB9.6080705@cisco.com> <4664D24E.2000803@saloits.com> <6D9687E95918C04A8B30A7D6DA805A3E77B2D1@zensys17.zensys.local> <D291504E-9D23-4D2A-B5D5-A88976104AE4@cisco.com>
Content-Type: text/plain
Date: Thu, 07 Jun 2007 14:57:41 -0600
Message-Id: <1181249862.5731.132.camel@dellx1>
Mime-Version: 1.0
X-Mailer: Evolution 2.10.1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: rsn@ietf.org
Subject: [RSN] The need for RSN
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

I would like to reiterate that I think that the work RSN group has
suggested taking on is very important to my working group - 6lowpan.

Our working group is looking to recharter and the scope of the work will
be focused on issues related to interoperability for 6lowpan networks.
This include things like MIC identifiers, alternative mesh headers,
security, ...

What is not in the scope is routing.  I think the RSN concept is
important in that the devices we are anticipating have significant
constraints (power, memory, processing) and as such the current set of
protocols and development is probably not appropriate for these types of
devices.

	geoff



_______________________________________________
RSN mailing list
RSN@ietf.org
https://www1.ietf.org/mailman/listinfo/rsn

v2.23.0 | Report a Bug | By Email