Beruflich Dokumente
Kultur Dokumente
Internet-Draft
Expires: May 14, 2008
M-K. Shin
ETRI
T. Camilo
J. Silva
University of Coimbra
D. Kaspar
ETRI
November 11, 2007
Copyright Notice
Shin, et al.
[Page 1]
Internet-Draft
November 2007
Abstract
Table of Contents
1.
Introduction . . . . . . . . . . . . . . . . . . .
1.1. Requirements Notation . . . . . . . . . . . .
1.2. Terms Used . . . . . . . . . . . . . . . . . .
2. Goals . . . . . . . . . . . . . . . . . . . . . .
3. Scenario Considerations . . . . . . . . . . . . .
3.1. Device Movement within a Single WPAN Domain .
3.2. Device Movement between Multiple WPAN Domains
3.3. Single WPAN Movement (NEMO) . . . . . . . . .
3.4. MANEMO - Nested NEMO . . . . . . . . . . . . .
4. Mobility Support in 6LoWPAN . . . . . . . . . . .
4.1. Device Movement within a Single WPAN Domain .
4.2. Device Movement between Multiple WPAN DomainsS
4.3. Single WPAN movement (NEMO) . . . . . . . . .
4.4. MANEMO - Nested NEMO . . . . . . . . . . . . .
5. IANA Considerations . . . . . . . . . . . . . . .
6. Security Considerations . . . . . . . . . . . . .
7. Acknowledgements . . . . . . . . . . . . . . . . .
8. References . . . . . . . . . . . . . . . . . . . .
8.1. Normative References . . . . . . . . . . . . .
8.2. Informative References . . . . . . . . . . . .
Authors' Addresses . . . . . . . . . . . . . . . . . .
Intellectual Property and Copyright Statements . . . .
Shin, et al.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
3
3
5
6
6
7
8
9
11
11
11
14
14
15
16
17
18
18
18
20
21
[Page 2]
Internet-Draft
1.
November 2007
Introduction
1.1.
Requirements Notation
1.2.
Terms Used
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].
o
Shin, et al.
[Page 3]
Internet-Draft
November 2007
Shin, et al.
[Page 4]
Internet-Draft
2.
November 2007
Goals
Shin, et al.
[Page 5]
Internet-Draft
3.
November 2007
Scenario Considerations
3.1.
Shin, et al.
[Page 6]
Internet-Draft
November 2007
+----------------------------+
|
FFD
|
+----+
|
|CFD |
RFD
|
+----+
|
|
FFD
|
|
RFD
|
|
|
+----------------------------+
3.2.
[Page 7]
Internet-Draft
November 2007
former domain of CFD1 will need to elect a new CFD, in the example
the CFD3.
+-----------------+
+------------------+
|
FFD
|
|
FFD
|
|
+----+
|
+----+
|
|
|CFD3|
|
|CFD2|
RFD
|
|
+----+
|
+----+
|
|
+----+
|
|
|
RFD
|CFD1|-------> FFD
|
|
+----+
|
|
+-----------------+
+------------------+
WPAN1
WPAN2
3.3.
[Page 8]
Internet-Draft
November 2007
3.4.
[Page 9]
Internet-Draft
November 2007
overhead).
Shin, et al.
[Page 10]
Internet-Draft
4.
November 2007
4.1.
The other way is to develop a new routing protocol for 6LoWPAN. The
work is also being discussed in [I-D.culler-rsn-routing-reqs] and is
especially focused on sensor networks (e.g., RL2N: Routing For Low
Power and Lossy Networks). Considering the variety of sensor based
applications, there may not be a single routing protocol satisfying
the entire list of requirements, in which case it may be decided to
define a limited set of routing protocols that could be combined to
satisfy the overall objective.
4.2.
Shin, et al.
[Page 11]
Internet-Draft
November 2007
Location Privacy
o
o
o
o
o
o
o
o
Almost of the goal above fits to our goals for mobility support in
6LoWPAN described in section 2.
[Page 12]
Internet-Draft
November 2007
+------------+
+----------+
|
|
|
|
|
| +--------+ |
| +------+ |
| | PMIPv6 |<-------->|PMIPv6| |
|
| +--------+ |
| +------+ |
|
^
^ |
|
^
|
+----------+
|
|
|
| |
|
|
|
|
|
|
v
| |
|
|
|
| +------+ |
|
| +-----+ | |
|
|
|
| | MANET| |
| |MANET| | |
|
|
|
| | L2 Rt|<------|------>|L2 Rt| | |
|
|
|
| | RL2N | |
| |RL2N | | |
|
|
|
| +------+ |
| +-----+ | |
|
|
|
|
^
|
|
|
^
| |
|
|
|
|
|
|
|
|
| |
|
|
|
|
v
|
|
|
v
| |
|
v
|
| +------+ |
| +----+ | |
| +------+ |
| |
| |
|
| |
|<-+ |
| |
| |
| |
| |
IPv6
| |
|
| IPv6 | |
| |
| | IPv6 |<------|------>|IPv6|<------------>| IPv6 | |
| +------+ |
| +----+
|
| +------+ |
| 6LoWPAN |
|
|
|
|
|
| device |
|
MAG
|
|
LMA
|
+----------+
|
+------------+
+----------+
|
[Page 13]
Internet-Draft
4.3.
November 2007
4.4.
MANEMO is a special case for Nested NEMO. When mobile routers (CFDs)
and mobile nodes (RFDs/FFDs) converge at the edge of the Internet
using wireless interfaces, they can form a 6LoWPAN network in an adhoc fashion and are able to provide Internet connectivity to one
another. Several issues exist in this network configuration such as
network loop, un-optimized path and multiple exit routers to the
Internet. They are well-known MANEMO' issues. While fixed routers
provide constantly connectivity, mobile routers (CFDs) can experience
intermittent connectivity to the Internet due to their movement.
When NEMO Basic Support [RFC3963] is used in this context, network
loops naturally occur. So, a new MANEMO solution is required in
6LoWPAN.
MANEMO solution is not finalized yet and it is at initial stage.
When it is done, to support this scenario, it should be also
supported in 6LoWPAN.
Shin, et al.
[Page 14]
Internet-Draft
5.
November 2007
IANA Considerations
Shin, et al.
[Page 15]
Internet-Draft
6.
November 2007
Security Considerations
More to be defined.
Shin, et al.
[Page 16]
Internet-Draft
7.
November 2007
Acknowledgements
TBD
Shin, et al.
[Page 17]
Internet-Draft
November 2007
8. References
8.1. Normative References
[RFC2119]
[RFC2460]
[RFC3756]
[RFC3775]
[RFC3963]
8.2.
Informative References
[RFC4831]
[RFC4886]
[RFC4919]
[I-D.dokaspar-6lowpan-routreq]
Kaspar, D., "Problem Statement, Design Goals and
Requirements for 6LoWPAN Mesh Routing",
draft-dokaspar-6lowpan-routreq-02 (work in progress),
July 2007.
[I-D.ietf-netlmm-proxymip6]
Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K.,
and B. Patil, "Proxy Mobile IPv6",
draft-ietf-netlmm-proxymip6-07 (work in progress),
November 2007.
[I-D.chakrabarti-mobopts-lowpan-req]
Park, S. and S. Chakrabarti, "LowPan Mobility Requirements
Shin, et al.
[Page 18]
Internet-Draft
November 2007
[I-D.ietf-netlmm-mn-ar-if]
Narayanan, S. and J. Laganier, "Network-based Localized
Mobility Management Interface between Mobile Node and
Mobility Access Gateway", draft-ietf-netlmm-mn-ar-if-02
(work in progress), May 2007.
Shin, et al.
[Page 19]
Internet-Draft
November 2007
Authors' Addresses
Myung-Ki Shin
ETRI
161 Gajeong-dong Yuseng-gu
Daejeon, 305-350
Korea
Email: tandre@dei.uc.pt
Jorge Sa Silva
University of Coimbra
Email: sasilva@dei.uc.pt
Dominik Kaspar
ETRI
161 Gajeong-dong Yuseng-gu
Daejeon, 305-350
Korea
Phone: +82 42 860 1702
Email: dominik@etri.re.kr
Shin, et al.
[Page 20]
Internet-Draft
November 2007
Acknowledgment
Shin, et al.
[Page 21]