< draft-ietf-6lowpan-problem-07.txt   draft-ietf-6lowpan-problem-08.txt >
Network Working Group N. Kushalnagar Network Working Group N. Kushalnagar
Internet-Draft Intel Corp Internet-Draft Intel Corp
Intended status: Standards Track G. Montenegro Intended status: Informational G. Montenegro
Expires: August 6, 2007 Microsoft Corporation Expires: August 30, 2007 Microsoft Corporation
C. Schumacher C. Schumacher
Danfoss A/S Danfoss A/S
February 2, 2007 February 26, 2007
6LoWPAN: Overview, Assumptions, Problem Statement and Goals 6LoWPAN: Overview, Assumptions, Problem Statement and Goals
draft-ietf-6lowpan-problem-07.txt draft-ietf-6lowpan-problem-08.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 37 skipping to change at page 1, line 37
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 6, 2007. This Internet-Draft will expire on August 30, 2007.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document describes the assumptions, problem statement and goals This document describes the assumptions, problem statement and goals
for transmitting IP over IEEE 802.15.4 networks. The set of goals for transmitting IP over IEEE 802.15.4 networks. The set of goals
enumerated in this document form an initial set only. enumerated in this document form an initial set only.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements notation . . . . . . . . . . . . . . . . . . 3
2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.1. IP Connectivity . . . . . . . . . . . . . . . . . . . . . 5 4.1. IP Connectivity . . . . . . . . . . . . . . . . . . . . . 5
4.2. Topologies . . . . . . . . . . . . . . . . . . . . . . . . 6 4.2. Topologies . . . . . . . . . . . . . . . . . . . . . . . . 6
4.3. Limited Packet Size . . . . . . . . . . . . . . . . . . . 6 4.3. Limited Packet Size . . . . . . . . . . . . . . . . . . . 6
4.4. Limited configuration and management . . . . . . . . . . . 7 4.4. Limited configuration and management . . . . . . . . . . . 7
4.5. Service discovery . . . . . . . . . . . . . . . . . . . . 7 4.5. Service discovery . . . . . . . . . . . . . . . . . . . . 7
4.6. Security . . . . . . . . . . . . . . . . . . . . . . . . . 7 4.6. Security . . . . . . . . . . . . . . . . . . . . . . . . . 7
5. Goals . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 5. Goals . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
7. Security Considerations . . . . . . . . . . . . . . . . . . . 10 7. Security Considerations . . . . . . . . . . . . . . . . . . . 9
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
9.1. Normative References . . . . . . . . . . . . . . . . . . . 11 9.1. Normative References . . . . . . . . . . . . . . . . . . . 11
9.2. Informative References . . . . . . . . . . . . . . . . . . 11 9.2. Informative References . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12
Intellectual Property and Copyright Statements . . . . . . . . . . 13 Intellectual Property and Copyright Statements . . . . . . . . . . 13
1. Introduction 1. Introduction
Low-power wireless personal area networks (LoWPANs) comprise devices Low-power wireless personal area networks (LoWPANs) comprise devices
that conform to the IEEE 802.15.4-2003 standard by the IEEE that conform to the IEEE 802.15.4-2003 standard by the IEEE
skipping to change at page 3, line 26 skipping to change at page 3, line 26
LoWPAN requirements with regards to the IP layer and above, and LoWPAN requirements with regards to the IP layer and above, and
spells out the underlying assumptions of IP for LoWPANs. Finally, it spells out the underlying assumptions of IP for LoWPANs. Finally, it
describes problems associated with enabling IP communication with describes problems associated with enabling IP communication with
devices in a LoWPAN, and defines goals to address these in a devices in a LoWPAN, and defines goals to address these in a
prioritized manner. Admittedly, not all items on this list may be prioritized manner. Admittedly, not all items on this list may be
necessarily appropriate tasks for the IETF. Nevertheless, they are necessarily appropriate tasks for the IETF. Nevertheless, they are
documented here to give a general overview of the larger problem. documented here to give a general overview of the larger problem.
This is useful both to structure work within the IETF as well as to This is useful both to structure work within the IETF as well as to
understand better how to coordinate with external organizations. understand better how to coordinate with external organizations.
1.1. Requirements notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
2. Overview 2. Overview
A LoWPAN is a simple low cost communication network that allows A LoWPAN is a simple low cost communication network that allows
wireless connectivity in applications with limited power and relaxed wireless connectivity in applications with limited power and relaxed
throughput requirements. A LoWPAN typically includes devices that throughput requirements. A LoWPAN typically includes devices that
work together to connect the physical environment to real-world work together to connect the physical environment to real-world
applications, e.g., wireless sensors. LoWPANs conform to the IEEE applications, e.g., wireless sensors. LoWPANs conform to the IEEE
802.15.4-2003 standard. [ieee802.15.4]. 802.15.4-2003 standard. [ieee802.15.4].
Some of the characteristics of LoWPANs are: Some of the characteristics of LoWPANs are:
skipping to change at page 11, line 4 skipping to change at page 10, line 44
message integrity, such as CCM* mode. 6LoWPAN networks can operate in message integrity, such as CCM* mode. 6LoWPAN networks can operate in
any of the previous modes, but it is desirable to utilize the most any of the previous modes, but it is desirable to utilize the most
secure modes available for link-layer security (e.g., CCM*), and secure modes available for link-layer security (e.g., CCM*), and
build upon it. build upon it.
For network layer security, two models are applicable: end-to-end For network layer security, two models are applicable: end-to-end
security, e.g. using IPsec transport mode, or security that is security, e.g. using IPsec transport mode, or security that is
limited to the wireless portion of the network, e.g. using a security limited to the wireless portion of the network, e.g. using a security
gateway and IPsec tunnel mode. The disadvantage of the latter is the gateway and IPsec tunnel mode. The disadvantage of the latter is the
larger header size, which is significant at the 6LoWPAN frame MTUs. larger header size, which is significant at the 6LoWPAN frame MTUs.
To simplify 6LoWPAN implementations, it is beneficial to identify the To simplify 6LoWPAN implementations, it is beneficial to identify the
relevant security model, and to identify a preferred set of cipher relevant security model, and to identify a preferred set of cipher
suites that are appropriate given the constraints. suites that are appropriate given the constraints.
8. Acknowledgements 8. Acknowledgements
Thanks to Geoff Mulligan, Soohong Daniel Park, Samita Chakrabarti and Thanks to Geoff Mulligan, Soohong Daniel Park, Samita Chakrabarti,
Brijesh Kumar for their comments and help in shaping this document. Brijesh Kumar and Miguel Garcia for their comments and help in
shaping this document.
9. References 9. References
9.1. Normative References 9.1. Normative References
[I-D.ietf-ipv6-2461bis]
Narten, T., "Neighbor Discovery for IP version 6 (IPv6)",
draft-ietf-ipv6-2461bis-10 (work in progress),
January 2007.
[I-D.ietf-ipv6-rfc2462bis]
Thomson, S., "IPv6 Stateless Address Autoconfiguration",
draft-ietf-ipv6-rfc2462bis-08 (work in progress),
May 2005.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998. (IPv6) Specification", RFC 2460, December 1998.
[ieee802.15.4] [ieee802.15.4]
IEEE Computer Society, "IEEE Std. 802.15.4-2003", IEEE Computer Society, "IEEE Std. 802.15.4-2003",
October 2003. October 2003.
9.2. Informative References 9.2. Informative References
[EUI64] "GUIDELINES FOR 64-BIT GLOBAL IDENTIFIER (EUI-64) [EUI64] "GUIDELINES FOR 64-BIT GLOBAL IDENTIFIER (EUI-64)
REGISTRATION AUTHORITY", IEEE http://standards.ieee.org/ REGISTRATION AUTHORITY", IEEE http://standards.ieee.org/
regauth/oui/tutorials/EUI64.html. regauth/oui/tutorials/EUI64.html.
[I-D.ietf-ipv6-rfc2462bis]
Thomson, S., "IPv6 Stateless Address Autoconfiguration",
draft-ietf-ipv6-rfc2462bis-08 (work in progress),
May 2005.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing Simple Network Management Architecture for Describing Simple Network Management
Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
December 2002. December 2002.
[RFC3561] Perkins, C., Belding-Royer, E., and S. Das, "Ad hoc On- [RFC3561] Perkins, C., Belding-Royer, E., and S. Das, "Ad hoc On-
Demand Distance Vector (AODV) Routing", RFC 3561, Demand Distance Vector (AODV) Routing", RFC 3561,
July 2003. July 2003.
[RFC3626] Clausen, T. and P. Jacquet, "Optimized Link State Routing [RFC3626] Clausen, T. and P. Jacquet, "Optimized Link State Routing
 End of changes. 11 change blocks. 
30 lines changed or deleted 15 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/