Network Working Group K. Kim Ed.
Internet-Draft C. Lim
Intended status: Standards Track picosNet Corp/Ajou Univ.
Expires: December 21, 2007 S. Yoo
Ajou University
S. Daniel Park, Ed.
SAMSUNG Electronics
G. Mulligan
June 19, 2007
Commissioning in 6LoWPAN
draft-daniel-6lowpan-commissioning-00.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that any
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
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on December 21, 2007.
Copyright Notice
Copyright (C) The IETF Trust (2007).
Abstract
The commisioning process defines the startup procedure taken by the
6LoWPAN device. This document defines the startup procedure that all
kinds of devices must take to become part of the network.
Kim, et al. Expires December 21, 2007 [Page 1]
Internet-Draft Commissioning in 6LoWPAN June 2007
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Requirements notation . . . . . . . . . . . . . . . . . . . 4
3. Bootstrapping . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Scanning through channels . . . . . . . . . . . . . . . . . 4
3.2. Starting a new network . . . . . . . . . . . . . . . . . . 5
3.3. Joining the network . . . . . . . . . . . . . . . . . . . . 5
3.3.1. Joining the network with association . . . . . . . . . 5
3.3.2. Joining the network without association . . . . . . . . 5
3.4. Setting the beacon data structure . . . . . . . . . . . . . 6
4. Assigning the short address . . . . . . . . . . . . . . . . . . 6
5. Obtaining IPv6 address . . . . . . . . . . . . . . . . . . . . 6
6. IANA Consideration . . . . . . . . . . . . . . . . . . . . . . 6
7. Security Considerations . . . . . . . . . . . . . . . . . . . . 7
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7
9.1. Normative References . . . . . . . . . . . . . . . . . . . 7
9.2. Informative References . . . . . . . . . . . . . . . . . . 7
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7
Intellectual Property and Copyright Statements . . . . . . . . . . 9
Kim, et al. Expires December 21, 2007 [Page 2]
Internet-Draft Commissioning in 6LoWPAN June 2007
1. Introduction
6LoWPAN is a low-power wireless personal area network(LoWPAN) which
is comprised of the IEEE 802.15.4-2003 standard [ieee802.15.4]
devices. Every device needs specific procedure to start their
functioning. This procedure needs to be well defined for
interoperability of devices from different vendors. This document
defines the procedure taken by 6LoWPAN constituent devices when they
first start operation. This procedure involves starting a new
network, becoming part of existing network and obtaining IP settings.
2. Terminology
Active Scan
An active scan is used by an FFD to locate all coordinators
transmitting beacon frames within its personal operating space,
which is provided by IEEE 802.15.4. It request other devices
to transmit the beacon frame.
Association
A IEEE 802.15.4 device can be assigned a dynamic 16 bit short
address during an association operation with a neighbor device
(or router) which is also called as the parent device. After
getting the short address, a device can communicate with its
parent or child by using only the assigned short address.
Coordinator
A full-function device (FFD) which is the principal controller
of a 6LoWPAN. It is also called as PAN coordinator. It MAY
initiate the synchronization of the entire 6LoWPAN by
transmitting beacons.
ED Scan
An ED scan allows a device to obtain a measure of the peak
energy in each requested channel, which is provided by IEEE
802.15.4.
Full Function Device (FFD)
A device implementing the complete protocol set of IEEE
802.15.4. It is capable of operating as a router (multi-hop
packet forwarding) for its associated neighbors.
Neighbor Table
A table which has the information of neighbor devices in a
personal operating space.
Kim, et al. Expires December 21, 2007 [Page 3]
Internet-Draft Commissioning in 6LoWPAN June 2007
PAN Id
The 16 bit 6LoWPAN identifier which is administratively
assigned to a 6LoWPAN.
Passive Scan
A passive scan, like an active scan, is used by an FFD to
locate all coordinators transmitting beacon frames within its
personal operating space, which is provided by IEEE 802.15.4.
The difference is that the passive scan is a receive-only
operation and does not request the beacon frame.
Personal Operating Space (POS)
The area within the reception range of the wireless
transmission of a IEEE 802.15.4 packet.
Reduced Function Device (RFD)
A IEEE 802.15.4 device of 6LoWPAN which does not have the
functionality of the router. That is, it can not forward IPv6
packets to the next hop device. It can only be the end device
of 6LoWPAN.
Short Address
A 16 bit address dynamically assigned to a device from its
parent.
2.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].
3. Bootstrapping
Bootstrapping is defined as associating with the network and
obtaining IPv6 address. Specifically, this includes the process of
starting the network, associating with other nodes, obtaining the
unique IPv6 address, and constructing security credentials for
6LoWPAN.
3.1. Scanning through channels
For getting the information of other devices within POS, the device
should perform a scan across a specified list of channels. The
device can use either an active scan or a passive scan. During
scanning procedure, the device receive beacon frames from other
Kim, et al. Expires December 21, 2007 [Page 4]
Internet-Draft Commissioning in 6LoWPAN June 2007
devices. The beacon frame contains the information about the device
sending it, which is used for determine whether a device is 6LoWPAN
device or not. If the device which send the beacon frame is
distingushed as the 6LoWPAN device, its information should be stored
in the neighbor table.
3.2. Starting a new network
A node which starts a new network may become the coordinator. Which
devices become the coordinator depends on the configuration of the
device and the state of existing networks.
Prior to starting a new network, the device first perform a scan for
locating the PAN within its POS. Detailed procedure of a scan is
described in Section 4. The device should select a channel with the
least number of networks, preferrably selecting a channel with no
network if possible. On this step, The device may use an ED scan to
select a channel which has less channel usage.
After selecting a channel for a new network, the device shall select
a PAN Id which is unique among PANs within its POS. The algorithm
for selecting a suitable PAN Id is TBD.
3.3. Joining the network
3.3.1. Joining the network with association
To joining the network, the device first perform scanning for
discoverying the PAN within its POS. Detailed procedure of a scan is
described in Section 4. On completion of scan, the device selects
the network it wishes to join from the scanning result. It then
finds the device which corresponds to that network in its neighbor
table and it requests to associate using MAC primitive to that
particular device. The algorithm for selecting a device it wishes to
associate among devices in the network is TBD.
3.3.2. Joining the network without association
The device doesn't need to associate with other devices to become
part of the network. The non-associated device, however, must use
the 64-bit extended address to communicate. In this case, the device
should perform scanning periodically since devices aren't bound to
each other strongly. Detailed procedure of a scan is described in
Section 4.
Kim, et al. Expires December 21, 2007 [Page 5]
Internet-Draft Commissioning in 6LoWPAN June 2007
3.4. Setting the beacon data structure
After associating with the network, The device should set its beacon
data structure, which is attached to the beacon frame. The beacon
data structure should contain the following information at least.
o Vendor ID
o Stack Version
o The Extended Address
4. Assigning the short address
During association procedure, every device except the coordinator is
given its short address from the parent device which is being
requested to associate. The coordinator assigns its short address
after selecting a PAN Id by itself. The short address must be unique
in a network and may be given by a distributed way. The specific
algorithm for assigning the short address is TBD.
5. Obtaining IPv6 address
An IPv6 interface identifier can be obtained as described in
[I-D.ietf-6lowpan-format].
After having unique IPv6 interface identifier, the device begins to
obtain IPv6 address prefix. The IPv6 address prefix for a particular
6LoWPAN are stored by the IPv6 router in that network. ICMPv6 is
used to share these parameters. Routers in 6LoWPAN are supposed to
send Router Advertisements(RA) message periodically. RA must contain
the prefix option which can be used in 6Lowpan. Devices wish to
obtain IPv6 address prefix may wait for an RA until RA_WAIT_TIME
elapsed. After that if there is still no RA received, they may send
Router Solicitation(RS) message to request it.
If there are multiple routers in a 6LoWPAN, the device should
consider which one is chosen as a default router. One possible way
to do is to compare the hop count traveled of each RA message. More
detailed algorithm for selecting one from multiple router is TBD.
6. IANA Consideration
TBD.
Kim, et al. Expires December 21, 2007 [Page 6]
Internet-Draft Commissioning in 6LoWPAN June 2007
7. Security Considerations
IEEE 802.15.4 devices is required to support AES link-layer security.
MAC layer also provides all keying material necessary to provide the
security services.
It isn't defined, however, when security shall be used especially
combining with bootstrapping. After the device start and join the
network, security services such as key management and device
authentication should be done automatically. Detailed algorithm for
security on bootstrapping is TBD.
8. Acknowledgments
N/A
9. References
9.1. Normative References
[I-D.ietf-6lowpan-format]
Montenegro, G., "Transmission of IPv6 Packets over IEEE
802.15.4 Networks", draft-ietf-6lowpan-format (work in
progress), February 2007.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[ieee802.15.4]
IEEE Computer Society, "IEEE Std. 802.15.4-2003".
9.2. Informative References
[RFC2461] Narten, T., Nordmark, E., and W. Simpson, "Neighbor
Discovery for IP Version 6 (IPv6)", RFC 2461,
December 1998.
[RFC3513] Hinden, R. and S. Deering, "Internet Protocol Version 6
(IPv6) Addressing Architecture", RFC 3513, April 2003.
Kim, et al. Expires December 21, 2007 [Page 7]
Internet-Draft Commissioning in 6LoWPAN June 2007
Author's Address
Kim, Ki Hyung (editor)
picosNet Corp/Ajou Univ.
San 5 Wonchun-dong, Yeongtong-gu
Suwon-si, Gyeonggi-do 442-749
KOREA
Phone: +82 31 219 2433
EMail: kkim86@picosnet.com
Chae-Seong Lim
picosNet Corp/Ajou Univ.
San 5 Wonchun-dong, Yeongtong-gu
Suwon-si, Gyeonggi-do 442-749
KOREA
Phone: +82 10 2892 2469
EMail: crimsuni@picosnet.com
Seung Wha Yoo
Ajou University
San 5 Wonchun-dong, Yeongtong-gu
Suwon-si, Gyeonggi-do 442-749
KOREA
Phone: +82 31 219 1603
EMail: swyoo@ajou.ac.kr
Soohong Daniel Park (editor)
SAMSUNG Electronics
Mobile Platform Laboratory, SAMSUNG Electronics 416 Maetan-3dong,
Yeongtong-gu Suwon-si, Gyeonggi-do 442-742
KOREA
Phone: +82 31 200 4508
EMail: soohong.park@samsung.com
Geoffrey Mulligan
EMail: geoff@mulligan.com
Kim, et al. Expires December 21, 2007 [Page 8]
Internet-Draft Commissioning in 6LoWPAN June 2007
Full Copyright Statement
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
Kim, et al. Expires December 21, 2007 [Page 9]