Document Action: 'Design and Application Spaces for 6LoWPANs' to Informational RFC (draft-ietf-6lowpan-usecases-10.txt)
The IESG <iesg-secretary@ietf.org> Tue, 24 January 2012 17:35 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6D7E21F84DD for <ietf-announce@ietfa.amsl.com>; Tue, 24 Jan 2012 09:35:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.558
X-Spam-Level:
X-Spam-Status: No, score=-102.558 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eI0DLzTHaeEe; Tue, 24 Jan 2012 09:35:25 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12BEE21F84E7; Tue, 24 Jan 2012 09:35:25 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Document Action: 'Design and Application Spaces for 6LoWPANs' to Informational RFC (draft-ietf-6lowpan-usecases-10.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20120124173525.20842.73229.idtracker@ietfa.amsl.com>
Date: Tue, 24 Jan 2012 09:35:25 -0800
Cc: 6lowpan mailing list <6lowpan@lists.ietf.org>, 6lowpan chair <6lowpan-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jan 2012 17:35:26 -0000
The IESG has approved the following document: - 'Design and Application Spaces for 6LoWPANs' (draft-ietf-6lowpan-usecases-10.txt) as an Informational RFC This document is the product of the IPv6 over Low power WPAN Working Group. The IESG contact persons are Ralph Droms and Jari Arkko. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-6lowpan-usecases/ Technical Summary This document investigates potential application scenarios and use cases for low-power wireless personal area networks (LoWPANs). This document provides dimensions of design space for LoWPAN applications. Working Group Summary This document completed WGLC. Document Quality This document was well reviewed by the 6lowpan WG. Personnel Geoff Mulligan <geoff.ietf@mulligan.com> is the document shepherd. Ralph Droms <rdroms@rdroms.ietf@gmail.com> is the responsible AD. RFC Editor Note Change fourth paragraph of Section 4: OLD: While IPsec is mandatory with IPv6 [4], considering the power constraints and limited processing capabilities of IEEE802.15.4 devices, IPsec is computationally expensive; Internet key exchange (IKEv2) messaging described in [5] is not suited for LoWPANs as the amount of signaling in these networks should be minimized. Thus, LoWPANs may need to define their own keying management method that requires minimum overhead in terms of packet size and message exchange [12]. IPsec provides authentication and confidentiality between end nodes and across multiple LoWPAN links, and may be useful only when two nodes want to apply security to all exchanged messages. However, in many cases, the security may be requested at the application layer as needed, while other messages can flow in the network without security overhead. NEW: While IPsec is mandatory with IPv6 [4], considering the power constraints and limited processing capabilities of IEEE802.15.4 devices, IPsec is computationally expensive; Internet key exchange (IKEv2) messaging described in [5] is not suited for LoWPANs as the amount of signaling in these networks should be minimized. Thus, LoWPANs may need to define their own keying management method that requires minimum overhead in terms of packet size and message exchange [12]. IPsec provides authentication and confidentiality between end nodes and across multiple LoWPAN links, and may be useful only when two nodes want to apply security to all exchanged messages. However, in many cases, the security may be requested at the application layer as needed, while other messages can flow in the network without security overhead. Recent work [13] shows some promise for minimal IKEv2 implementations. Add to Section 7.2: [13] T. Kivinen, "Minimal IKEv2", kivinen-ipsecme-ikev2-minimal-00.txt, work-in-progress, February 2011.