draft-ietf-nemo-terminology-06.txt   rfc4885.txt 
NEMO Working Group T. Ernst Network Working Group T. Ernst
Internet-Draft INRIA Request for Comments: 4885 INRIA
Intended status: Informational H-Y. Lach Category: Informational H-Y. Lach
Expires: May 13, 2007 Motorola Labs Motorola
November 9, 2006
Network Mobility Support Terminology Network Mobility Support Terminology
draft-ietf-nemo-terminology-06
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 Status of This Memo
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 13, 2007. This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document defines a terminology for discussing network mobility This document defines a terminology for discussing network mobility
(NEMO) issues and solution requirements. (NEMO) issues and solution requirements.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Architectural Components . . . . . . . . . . . . . . . . . . . 3
2. Architectural Components . . . . . . . . . . . . . . . . . . . 5 2.1. Mobile Network (NEMO) . . . . . . . . . . . . . . . . . . 5
2.1. Mobile Network (NEMO) . . . . . . . . . . . . . . . . . . 7 2.2. Mobile Subnet . . . . . . . . . . . . . . . . . . . . . . 5
2.2. Mobile Subnet . . . . . . . . . . . . . . . . . . . . . . 7 2.3. Mobile Router (MR) . . . . . . . . . . . . . . . . . . . . 6
2.3. Mobile Router (MR) . . . . . . . . . . . . . . . . . . . . 7 2.4. Egress Interface . . . . . . . . . . . . . . . . . . . . . 6
2.4. Egress Interface . . . . . . . . . . . . . . . . . . . . . 7 2.5. Ingress Interface . . . . . . . . . . . . . . . . . . . . 6
2.5. Ingress Interface . . . . . . . . . . . . . . . . . . . . 8 2.6. Mobile Network Prefix (MNP) . . . . . . . . . . . . . . . 6
2.6. Mobile Network Prefix (MNP) . . . . . . . . . . . . . . . 8 2.7. Mobile Network Node (MNN) . . . . . . . . . . . . . . . . 6
2.7. Mobile Network Node (MNN) . . . . . . . . . . . . . . . . 8 2.8. Correspondent Node (CN) . . . . . . . . . . . . . . . . . 7
2.8. Correspondent Node (CN) . . . . . . . . . . . . . . . . . 8 2.9. Correspondent Router (CR) . . . . . . . . . . . . . . . . 7
2.9. Correspondent Router (CR) . . . . . . . . . . . . . . . . 8 2.10. Correspondent Entity (CE) . . . . . . . . . . . . . . . . 7
2.10. Correspondent Entity (CE) . . . . . . . . . . . . . . . . 8 3. Functional Terms . . . . . . . . . . . . . . . . . . . . . . . 7
3.1. Local Fixed Node (LFN) . . . . . . . . . . . . . . . . . . 8
3. Functional Terms . . . . . . . . . . . . . . . . . . . . . . . 9 3.2. Visiting Mobile Node (VMN) . . . . . . . . . . . . . . . . 8
3.1. Local Fixed Node (LFN) . . . . . . . . . . . . . . . . . . 10 3.3. Local Mobile Node (LMN) . . . . . . . . . . . . . . . . . 9
3.2. Visiting Mobile Node (VMN) . . . . . . . . . . . . . . . . 10 3.4. NEMO-Enabled Node (NEMO-Node) . . . . . . . . . . . . . . 9
3.3. Local Mobile Node (LMN) . . . . . . . . . . . . . . . . . 10 3.5. MIPv6-Enabled Node (MIPv6-Node) . . . . . . . . . . . . . 9
3.4. NEMO-enabled node (NEMO-node) . . . . . . . . . . . . . . 10 4. Nested Mobility Terms . . . . . . . . . . . . . . . . . . . . 9
3.5. MIPv6-enabled (MIPv6-node) . . . . . . . . . . . . . . . . 10 4.1. Nested Mobile Network (nested-NEMO) . . . . . . . . . . . 9
4.2. Root-NEMO . . . . . . . . . . . . . . . . . . . . . . . . 9
4. Nested Mobility Terms . . . . . . . . . . . . . . . . . . . . 11 4.3. Parent-NEMO . . . . . . . . . . . . . . . . . . . . . . . 10
4.1. Nested Mobile Network (nested-NEMO) . . . . . . . . . . . 11 4.4. Sub-NEMO . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.2. Root-NEMO . . . . . . . . . . . . . . . . . . . . . . . . 11 4.5. Root-MR . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.3. Parent-NEMO . . . . . . . . . . . . . . . . . . . . . . . 11 4.6. Parent-MR . . . . . . . . . . . . . . . . . . . . . . . . 10
4.4. Sub-NEMO . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.7. Sub-MR . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.5. Root-MR . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.8. Depth . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.6. Parent-MR . . . . . . . . . . . . . . . . . . . . . . . . 12 5. Multihoming Terms . . . . . . . . . . . . . . . . . . . . . . 11
4.7. Sub-MR . . . . . . . . . . . . . . . . . . . . . . . . . . 12 5.1. Multihomed Host or MNN . . . . . . . . . . . . . . . . . . 11
4.8. Depth . . . . . . . . . . . . . . . . . . . . . . . . . . 12 5.2. Multihomed Mobile Router . . . . . . . . . . . . . . . . . 11
5.3. Multihomed Mobile Network (multihomed-NEMO) . . . . . . . 12
5. Multihoming Terms . . . . . . . . . . . . . . . . . . . . . . 13 5.4. Nested Multihomed Mobile Network . . . . . . . . . . . . . 12
5.1. Multihomed host or MNN . . . . . . . . . . . . . . . . . . 13 5.5. Split-NEMO . . . . . . . . . . . . . . . . . . . . . . . . 12
5.2. Multihomed Mobile Router . . . . . . . . . . . . . . . . . 13 5.6. Illustration . . . . . . . . . . . . . . . . . . . . . . . 12
5.3. Multihomed Mobile Network (multihomed-NEMO) . . . . . . . 14 6. Home Network Model Terms . . . . . . . . . . . . . . . . . . . 14
5.4. Nested Multihomed Mobile Network . . . . . . . . . . . . . 14 6.1. Home Link . . . . . . . . . . . . . . . . . . . . . . . . 14
5.5. Split-NEMO . . . . . . . . . . . . . . . . . . . . . . . . 14 6.2. Home Network . . . . . . . . . . . . . . . . . . . . . . . 14
5.6. Illustration . . . . . . . . . . . . . . . . . . . . . . . 14 6.3. Home Address . . . . . . . . . . . . . . . . . . . . . . . 14
6.4. Mobile Home Network . . . . . . . . . . . . . . . . . . . 14
6. Home Network Model Terms . . . . . . . . . . . . . . . . . . . 17 6.5. Distributed Home Network . . . . . . . . . . . . . . . . . 14
6.1. Home Link . . . . . . . . . . . . . . . . . . . . . . . . 17 6.6. Mobile Aggregated Prefix . . . . . . . . . . . . . . . . . 15
6.2. Home Network . . . . . . . . . . . . . . . . . . . . . . . 17 6.7. Aggregated Home Network . . . . . . . . . . . . . . . . . 15
6.3. Home Address . . . . . . . . . . . . . . . . . . . . . . . 17 6.8. Extended Home Network . . . . . . . . . . . . . . . . . . 15
6.4. Mobile Home Network . . . . . . . . . . . . . . . . . . . 17 6.9. Virtual Home Network . . . . . . . . . . . . . . . . . . . 15
6.5. Distributed Home Network . . . . . . . . . . . . . . . . . 17 7. Mobility Support Terms . . . . . . . . . . . . . . . . . . . . 15
6.6. Mobile Aggregated Prefix . . . . . . . . . . . . . . . . . 18 7.1. Host Mobility Support . . . . . . . . . . . . . . . . . . 15
6.7. Aggregated Home Network . . . . . . . . . . . . . . . . . 18 7.2. Network Mobility Support (NEMO Support) . . . . . . . . . 15
6.8. Extended Home Network . . . . . . . . . . . . . . . . . . 18 7.3. NEMO Basic Support . . . . . . . . . . . . . . . . . . . . 15
6.9. Virtual Home Network . . . . . . . . . . . . . . . . . . . 18 7.4. NEMO Extended Support . . . . . . . . . . . . . . . . . . 16
7.5. NEMO Routing Optimization (NEMO RO) . . . . . . . . . . . 16
7. Mobility Support Terms . . . . . . . . . . . . . . . . . . . . 19 7.6. MRHA Tunnel . . . . . . . . . . . . . . . . . . . . . . . 16
7.1. Host Mobility Support . . . . . . . . . . . . . . . . . . 19 7.7. Pinball Route . . . . . . . . . . . . . . . . . . . . . . 16
7.2. Network Mobility Support (NEMO Support) . . . . . . . . . 19 8. Security Considerations . . . . . . . . . . . . . . . . . . . 16
7.3. NEMO Basic Support . . . . . . . . . . . . . . . . . . . . 19 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16
7.4. NEMO Extended Support . . . . . . . . . . . . . . . . . . 19 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
7.5. NEMO Routing Optimization (NEMO RO) . . . . . . . . . . . 19 10.1. Normative References . . . . . . . . . . . . . . . . . . . 17
7.6. MRHA Tunnel . . . . . . . . . . . . . . . . . . . . . . . 19 10.2. Informative References . . . . . . . . . . . . . . . . . . 17
7.7. Pinball Route . . . . . . . . . . . . . . . . . . . . . . 20
8. Security Considerations . . . . . . . . . . . . . . . . . . . 21
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 23
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 24
11.1. Normative References . . . . . . . . . . . . . . . . . . . 24
11.2. Informative References . . . . . . . . . . . . . . . . . . 24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 25
Intellectual Property and Copyright Statements . . . . . . . . . . 26
1. Introduction 1. Introduction
Network mobility support is concerned with managing the mobility of Network mobility support is concerned with managing the mobility of
an entire network. This arises when a router connecting a network to an entire network. This arises when a router connecting a network to
the Internet dynamically changes its point of attachment to the fixed the Internet dynamically changes its point of attachment to the fixed
infrastructure, thereby causing the reachability of the entire infrastructure, thereby causing the reachability of the entire
network to be changed in relation to the fixed Internet topology. network to be changed in relation to the fixed Internet topology.
Such a network is referred to as a mobile network. Without Such a network is referred to as a mobile network. Without
appropriate mechanisms to support network mobility, sessions appropriate mechanisms to support network mobility, sessions
skipping to change at page 4, line 30 skipping to change at page 3, line 30
problem space, the design goals [1], and the solutions for network problem space, the design goals [1], and the solutions for network
mobility support. This terminology aims to be consistent with the mobility support. This terminology aims to be consistent with the
usual IPv6 terminology [2] and the generic mobility-related terms usual IPv6 terminology [2] and the generic mobility-related terms
already defined in the Mobility Related Terminology [3] and in the already defined in the Mobility Related Terminology [3] and in the
Mobile IPv6 specification [4]. Some terms introduced in this Mobile IPv6 specification [4]. Some terms introduced in this
document may only be useful for defining the problem scope and document may only be useful for defining the problem scope and
functional requirements of network mobility support. functional requirements of network mobility support.
Note that the abbreviation NEMO stands for either "a NEtwork that is Note that the abbreviation NEMO stands for either "a NEtwork that is
MObile" or "NEtwork MObility". The former (see Section 2.1) is used MObile" or "NEtwork MObility". The former (see Section 2.1) is used
as a noun, e.g. "a NEMO" meaning "a mobile network". The latter (see as a noun, e.g., "a NEMO" meaning "a mobile network". The latter
Section 7) refers to the concept of "network mobility" as in "NEMO (see Section 7) refers to the concept of "network mobility", as in
Basic Support" and is also the working group's name. "NEMO Basic Support", and is also the working group's name.
Section 2 introduces terms to define the architecture while terms Section 2 introduces terms to define the architecture, while terms
needed to emphasize the distinct functionalities of those needed to emphasize the distinct functionalities of those
architectural components are described in Section 3. Section 4, architectural components are described in Section 3. Section 4,
Section 5 and Section 6 describe terms pertaining to nested mobility, Section 5, and Section 6 describe terms pertaining to nested
multihoming and different configurations of mobile networks at home, mobility, multihoming, and different configurations of mobile
respectively. The different types of mobility are defined in networks at home, respectively. The different types of mobility are
Section 7. The last section lists miscellaneous terms which do not defined in Section 7. The last section lists miscellaneous terms
fit in any other section. that do not fit into any other section.
2. Architectural Components 2. Architectural Components
A mobile network is composed of one or more mobile IP-subnets and is A mobile network is composed of one or more mobile IP-subnets and is
viewed as a single unit. This network unit is connected to the viewed as a single unit. This network unit is connected to the
Internet by means of one or more mobile routers (MRs). Nodes behind Internet by means of one or more mobile routers (MRs). Nodes behind
the MR (referred to as MNNs) primarily comprise fixed nodes (nodes the MR (referred to as MNNs) primarily comprise fixed nodes (nodes
unable to change their point of attachment while maintaining ongoing unable to change their point of attachment while maintaining ongoing
sessions), and possibly mobile nodes (nodes able to change their sessions), and possibly mobile nodes (nodes able to change their
point of attachment while maintaining ongoing sessions). In most point of attachment while maintaining ongoing sessions). In most
cases, the internal structure of the mobile network will be stable cases, the internal structure of the mobile network will be stable
(no dynamic change of the topology), but this is not always true. (no dynamic change of the topology), but this is not always true.
Figure 1 illustrates the architectural components involved in network Figure 1 illustrates the architectural components involved in network
mobility and defined in the following paragraphs: Mobile Router (MR), mobility and are defined in the following paragraphs: Mobile Router
Mobile Network (NEMO), Mobile Network Node (MNN), "ingress (MR), Mobile Network (NEMO), Mobile Network Node (MNN), "ingress
interface", "egress interface", and Correspondent Node (CN). The interface", "egress interface", and Correspondent Node (CN). The
other terms "access router" (AR), "Fixed Node (FN)", "Mobile Node other terms, "access router" (AR), "Fixed Node (FN)", "Mobile Node
(MN)", "home agent" (HA), "home link" and "foreign link" are not (MN)", "home agent" (HA), "home link", and "foreign link", are not
terms specific to network mobility and thus are defined in [3]. terms specific to network mobility and thus are defined in [3].
_ _
CN ->|_|-| Internet CN ->|_|-| Internet
| _____ | _____
|-| | |<- home link |-| | |<- home link
_ | |-| _ | _ _ | |-| _ | _
|-|_|-|_____| |-|_|-|-|_|<- HA (Home Agent) |-|_|-|_____| |-|_|-|-|_|<- HA (Home Agent)
| \ | _ | \ | _
foreign link ->| ^ |-|_|<- MR (Mobile Router) foreign link ->| ^ |-|_|<- MR (Mobile Router)
.. AR (access ___|___ .. AR (access ___|___
router) _| |_ router) _| |_
|_| |_| |_| |_|
^ ^ ^ ^
MNN1 MNN2 MNN1 MNN2
Figure 1: Mobile Network on the Home Link Figure 1: Mobile Network on the Home Link
Figure 2 shows a single mobile subnet. Figure 3 illustrates a larger Figure 2 shows a single mobile subnet. Figure 3 illustrates a larger
mobile network comprising several subnetworks, attached to a foreign mobile network comprising several subnets, attached to a foreign
link. link.
_ _
CN ->|_|-| CN ->|_|-|
| _____ | _____
_ | |-| | |<- home link _ | |-| | |<- home link
|_|-| _ | _ | |-| _ | _ |_|-| _ | _ | |-| _ | _
2 MNNs -> _ |-|_|-|-|_|-|_____| |-|_|-|-|_|<- HA 2 MNNs -> _ |-|_|-|-|_|-|_____| |-|_|-|-|_|<- HA
|_|-| . | \ \ | |_|-| . | \ \ |
| . |<- foreign ^AR | . |<- foreign ^AR
skipping to change at page 6, line 36 skipping to change at page 5, line 21
____|__ | ____|__ |
mobile subnet-^ _| . |<- foreign mobile subnet-^ _| . |<- foreign
|_| . link |_| . link
MNN2 -^ . MNN2 -^ .
^ ^
MR MR
'i': MR's ingress interface 'i': MR's ingress interface
'e': MR's egress interface 'e': MR's egress interface
Figure 3: Larger Mobile Network Made of 2 Mobile Subnets Figure 3: Larger Mobile Network Made up of 2 Mobile Subnets
At the network layer, MRs get access to the global Internet from the At the network layer, MRs get access to the global Internet from an
Access Router(s) (AR) on a visited link. An MR maintains the Access Router (AR) on a visited link. An MR maintains the Internet
Internet connectivity for the entire mobile network. A given MR has connectivity for the entire mobile network. A given MR has one or
one or more egress interface and one or more ingress interface. When more egress interfaces and one or more ingress interfaces. When
forwarding a packet to the Internet, the packet is transmitted forwarding a packet to the Internet, the packet is transmitted
upstream through one of the MR's egress interfaces to the AR; when upstream through one of the MR's egress interfaces to the AR; when
forwarding a packet from the AR down to the mobile network, the forwarding a packet from the AR down to the mobile network, the
packet is transmitted downstream through one of the MR's ingress packet is transmitted downstream through one of the MR's ingress
interfaces. interfaces.
2.1. Mobile Network (NEMO) 2.1. Mobile Network (NEMO)
As defined in [3]: As defined in [3]:
An entire network, moving as a unit, which dynamically changes its An entire network, moving as a unit, which dynamically changes its
point of attachment to the Internet and thus its reachability in the point of attachment to the Internet and thus its reachability in the
topology. The mobile network is composed of one or more IP-subnets topology. The mobile network is composed of one or more IP-subnets
and is connected to the global Internet via one or more Mobile and is connected to the global Internet via one or more Mobile
Routers (MR). The internal configuration of the mobile network is Routers (MR). The internal configuration of the mobile network is
assumed to be relatively stable with respect to the MR. assumed to be relatively stable with respect to the MR.
Re-arrangement of the mobile network and changing the attachment Rearrangement of the mobile network and changing the attachment point
point of the egress interface to the foreign link are orthogonal of the egress interface to the foreign link are orthogonal processes
processes and do no affect each other. and do no affect each other.
2.2. Mobile Subnet 2.2. Mobile Subnet
A link (subnet) which comprises, or is located within, the mobile A link (subnet) that comprises, or is located within, the mobile
network. network.
2.3. Mobile Router (MR) 2.3. Mobile Router (MR)
As defined in [3]: As defined in [3]:
A router capable of changing its point of attachment to the Internet, A router capable of changing its point of attachment to the Internet,
moving from one link to another link. The MR is capable of moving from one link to another link. The MR is capable of
forwarding packets between two or more interfaces, and possibly forwarding packets between two or more interfaces, and possibly
running a dynamic routing protocol modifying the state by which it running a dynamic routing protocol modifying the state by which it
does packet forwarding. does packet forwarding.
An MR acts as a gateway between an entire mobile network and the rest An MR acts as a gateway between an entire mobile network and the rest
of the Internet, and has one or more egress interface and one or more of the Internet, and has one or more egress interfaces and one or
ingress interface. Packets forwarded upstream to the rest of the more ingress interfaces. Packets forwarded upstream to the rest of
Internet are transmitted through one of the MR's egress interfaces; the Internet are transmitted through one of the MR's egress
packets forwarded downstream to the mobile network are transmitted interfaces; packets forwarded downstream to the mobile network are
through one of the MR's ingress interfaces. transmitted through one of the MR's ingress interfaces.
2.4. Egress Interface 2.4. Egress Interface
As defined in [3]: As defined in [3]:
The network interface of an MR attached to the home link if the MR is The network interface of an MR attached to the home link if the MR is
at home, or attached to a foreign link if the MR is in a foreign at home, or attached to a foreign link, if the MR is in a foreign
network. network.
2.5. Ingress Interface 2.5. Ingress Interface
As defined in [3]: As defined in [3]:
The interface of an MR attached to a link inside the mobile network. The interface of an MR attached to a link inside the mobile network.
2.6. Mobile Network Prefix (MNP) 2.6. Mobile Network Prefix (MNP)
skipping to change at page 8, line 25 skipping to change at page 6, line 50
A bit string that consists of some number of initial bits of an IP A bit string that consists of some number of initial bits of an IP
address which identifies the entire mobile network within the address which identifies the entire mobile network within the
Internet topology. All nodes in a mobile network necessarily have an Internet topology. All nodes in a mobile network necessarily have an
address containing this prefix. address containing this prefix.
2.7. Mobile Network Node (MNN) 2.7. Mobile Network Node (MNN)
As defined in [3]: As defined in [3]:
Any node (host or router) located within a mobile network, either Any node (host or router) located within a mobile network, either
permanently or temporarily. A Mobile Network Node may either be a permanently or temporarily. A Mobile Network Node may be either a
fixed node (LFN) or a mobile node (VMN or LMN). fixed node (LFN) or a mobile node (either VMN or LMN).
2.8. Correspondent Node (CN) 2.8. Correspondent Node (CN)
Any node that is communicating with one or more MNNs. A CN could be Any node that is communicating with one or more MNNs. A CN could be
either located within a fixed network or within another mobile either located within a fixed network or within a mobile network, and
network, and could be either fixed or mobile. could be either fixed or mobile.
2.9. Correspondent Router (CR) 2.9. Correspondent Router (CR)
Refers to the entity which is capable of terminating a Route Refers to the entity that is capable of terminating a Route
Optimization session on behalf of a Correspondent Node (see also NEMO Optimization session on behalf of a Correspondent Node (see also NEMO
Route Optimization in Section 7.5). Route Optimization in Section 7.5).
2.10. Correspondent Entity (CE) 2.10. Correspondent Entity (CE)
Refers to the entity which a Mobile Router or Mobile Network Node Refers to the entity with which a Mobile Router or Mobile Network
attempts to establish a Route Optimization session with. Depending Node attempts to establish a Route Optimization session. Depending
on the Route Optimization approach, the Correspondent Entity maybe a on the Route Optimization approach, the Correspondent Entity maybe a
Correspondent Node or Correspondent Router (see also NEMO Route Correspondent Node or Correspondent Router (see also NEMO Route
Optimization in Section 7.5) Optimization in Section 7.5).
3. Functional Terms 3. Functional Terms
Within the term Mobile Network Node (MNN), we can distinguish between Within the term Mobile Network Node (MNN), we can distinguish between
Local Fixed Nodes (LFN), Visiting Mobile Nodes (VMN) and Local Mobile Local Fixed Nodes (LFN), Visiting Mobile Nodes (VMN), and Local
Nodes (LMN). The distinction is a property of how different types of Mobile Nodes (LMN). The distinction is a property of how different
nodes can move in the topology and is necessary to discuss issues types of nodes can move in the topology and is necessary to discuss
related to mobility management and access control; however it does issues related to mobility management and access control; however, it
not imply that network mobility or host mobility should be handled does not imply that network mobility or host mobility should be
differently. Nodes are classified according to their function and handled differently. Nodes are classified according to their
capabilities with the rationale that nodes with different properties function and capabilities with the rationale that nodes with
may have different requirements. different properties may have different requirements.
Figure 4 illustrates a VMN changing its point of attachment from its Figure 4 illustrates a VMN changing its point of attachment from its
home link located outside the mobile network to within a mobile home link located outside the mobile network to within a mobile
network. The figure also illustrates a LMN changing its point of network. The figure also illustrates an LMN changing its point of
attachment within the mobile network. attachment within the mobile network.
mobile subnet 1 | _ +++++++<<<+++++++++++ mobile subnet 1 | _ +++++++<<<+++++++++++
|-|_|-| + + |-|_|-| + +
++<<<LMN-| \ | + |-MR ++<<<LMN-| \ | + |-MR
+ | + _____ | _ HA_MR + | + _____ | _ HA_MR
+ | _ | + | |-|-|_| + | _ | + | |-|-|_|
+ LMN _ |-|_|-| _ | _ | | _ + LMN _ |-|_|-| _ | _ | | _
++++>|_|-| \ |--|_|--|-|_|-|_____|-|-|_| ++++>|_|-| \ |--|_|--|-|_|-|_____|-|-|_|
| | ^ | \ | HA_VMN | | ^ | \ | HA_VMN
VMN _ | MR | VMN _ | MR |
|_|-| |-VMN |_|-| |-VMN
^ mobile subnet 2 + ^ mobile subnet 2 +
+ + + +
++++++++<<<+++++++++++++++++++++++++ ++++++++<<<+++++++++++++++++++++++++
+++>>>+++ = changing point of attachment +++>>>+++ = changing point of attachment
Figure 4: LFN vs LMM vs VMN Figure 4: LFN vs LMM vs VMN
In a typical use case of NEMO Basic Support [5], only the MR and the In a typical-use case of NEMO Basic Support [5], only the MR and the
HA are NEMO-enabled. LFNs are not MIPv6-enabled nor NEMO-enabled. HA are NEMO-enabled. LFNs are not MIPv6-enabled nor NEMO-enabled.
On the other hand, a VMN or a LMN acting as a mobile router may be On the other hand, a VMN or an LMN acting as a mobile router may be
NEMO-enabled whereas a VMN or a LMN acting as a mobile node may be NEMO-enabled, whereas a VMN or an LMN acting as a mobile node may be
MIPv6-enabled. MIPv6-enabled.
For NEMO Extended Support, details of the capabilities are not known For NEMO Extended Support, details of the capabilities are not yet
yet at the time of this writing, but NEMO-enabled nodes may be known at the time of this writing, but NEMO-enabled nodes may be
expected to implement some sort of Route Optimization. expected to implement some sort of Route Optimization.
3.1. Local Fixed Node (LFN) 3.1. Local Fixed Node (LFN)
A fixed node (FN), either a host or a router, that belongs to the A fixed node (FN), either a host or a router, that belongs to the
mobile network and is unable to change its point of attachment while mobile network and is unable to change its point of attachment while
maintaining ongoing sessions. Its address is taken from an MNP. maintaining ongoing sessions. Its address is taken from an MNP.
3.2. Visiting Mobile Node (VMN) 3.2. Visiting Mobile Node (VMN)
Either a mobile node (MN) or a mobile router (MR), assigned to a home Either a mobile node (MN) or a mobile router (MR), assigned to a home
link that doesn't belong to the mobile network and which is able to link that doesn't belong to the mobile network and that is able to
change its point of attachment while maintaining ongoing sessions. A change its point of attachment while maintaining ongoing sessions. A
VMN that is temporarily attached to a mobile subnet (used as a VMN that is temporarily attached to a mobile subnet (used as a
foreign link) obtains an address on that subnet (i.e. the address is foreign link) obtains an address on that subnet (i.e., the address is
taken from an MNP). taken from an MNP).
3.3. Local Mobile Node (LMN) 3.3. Local Mobile Node (LMN)
Either a mobile node (MN) or a mobile router (MR), assigned to a home Either a mobile node (MN) or a mobile router (MR), assigned to a home
link belonging to the mobile network and which is able to change its link belonging to the mobile network and which is able to change its
point of attachment while maintaining ongoing sessions. Its address point of attachment while maintaining ongoing sessions. Its address
is taken from an MNP. is taken from an MNP.
3.4. NEMO-enabled node (NEMO-node) 3.4. NEMO-Enabled Node (NEMO-Node)
A node that has been extended with network mobility support A node that has been extended with network mobility support
capabilities as described in NEMO specifications. capabilities as described in NEMO specifications.
3.5. MIPv6-enabled (MIPv6-node) 3.5. MIPv6-Enabled Node (MIPv6-Node)
A node which has been extended with host mobility support A node that has been extended with host mobility support capabilities
capabilities as defined in the Mobile IPv6 specification [4]. as defined in the Mobile IPv6 specification [4].
4. Nested Mobility Terms 4. Nested Mobility Terms
Nested mobility occurs when there is more than one level of mobility, Nested mobility occurs when there is more than one level of mobility,
i.e. when a mobile network acts as an access network and allows i.e., when a mobile network acts as an access network and allows
visiting nodes to attach to it. There are two cases of nested visiting nodes to attach to it. There are two cases of nested
mobility: mobility:
o The attaching node is a single VMN (see Figure 4). For instance, o The attaching node is a single VMN (see Figure 4). For instance,
when a passenger carrying a mobile phone gets Internet access from when a passenger carrying a mobile phone gets Internet access from
the public access network deployed on a bus. the public access network deployed on a bus.
o The attaching node is a MR with nodes behind it, i.e. a mobile o The attaching node is an MR with nodes behind it, i.e., a mobile
network (see Figure 5). For instance, when a passenger carrying a network (see Figure 5). For instance, when a passenger carrying a
PAN gets Internet access from the public access network deployed PAN gets Internet access from the public access network deployed
on a bus. on a bus.
For the second case, we introduce the following terms: For the second case, we introduce the following terms:
4.1. Nested Mobile Network (nested-NEMO) 4.1. Nested Mobile Network (nested-NEMO)
A mobile network is said to be nested when a mobile network (sub- A mobile network is said to be nested when a mobile network (sub-
NEMO) is attached to a larger mobile network (parent-NEMO). The NEMO) is attached to a larger mobile network (parent-NEMO). The
skipping to change at page 12, line 11 skipping to change at page 10, line 28
The MR(s) of the root-NEMO used to connect the nested mobile network The MR(s) of the root-NEMO used to connect the nested mobile network
to the fixed Internet (see Figure 5). to the fixed Internet (see Figure 5).
4.6. Parent-MR 4.6. Parent-MR
The MR(s) of the parent-NEMO. The MR(s) of the parent-NEMO.
4.7. Sub-MR 4.7. Sub-MR
The MR(s) of the sub-NEMO which is connected to a parent-NEMO The MR(s) of the sub-NEMO, which is connected to a parent-NEMO
4.8. Depth 4.8. Depth
In a nested NEMO indicates the number of sub-MRs a packet has to In a nested NEMO, indicates the number of sub-MRs a packet has to
cross between a MNN and the root-MR. cross between a MNN and the root-MR.
A MNN in the root-NEMO is at depth 1. If there are multiple root- A MNN in the root-NEMO is at depth 1. If there are multiple root-
NEMOs, a different depth is computed from each root-MR. NEMOs, a different depth is computed from each root-MR.
_____ _____
_ | _ | | _ | _ | |
_ |-|_|-| _ |-|_|-|-| |-| _ _ |-|_|-| _ |-|_|-|-| |-| _
_ |-|_|-| \ |-|_|-| \ | |_____| | _ |-|_| _ |-|_|-| \ |-|_|-| \ | |_____| | _ |-|_|
_ |-|_|-| | | | |-|_|-| _ |-|_|-| | | | |-|_|-|
skipping to change at page 13, line 8 skipping to change at page 11, line 8
<--------------><----------><----><---------><--------> <--------------><----------><----><---------><-------->
sub-NEMO root-NEMO fl Internet Home Network sub-NEMO root-NEMO fl Internet Home Network
Figure 5: Nested Mobility: a sub-NEMO attached to a larger mobile Figure 5: Nested Mobility: a sub-NEMO attached to a larger mobile
network network
5. Multihoming Terms 5. Multihoming Terms
Multihoming, as currently defined by the IETF, covers site- Multihoming, as currently defined by the IETF, covers site-
multihoming [10] and host multihoming. We enlarge this terminology multihoming [9] and host multihoming. We enlarge this terminology to
to include "multihomed mobile router" and "multihomed mobile include "multihomed mobile router" and "multihomed mobile network".
network". The specific configurations and issues pertaining to The specific configurations and issues pertaining to multihomed
multihomed mobile networks are covered in [6]. mobile networks are covered in [10].
5.1. Multihomed host or MNN 5.1. Multihomed Host or MNN
A host (e.g. an MNN) is multihomed when it has several addresses to A host (e.g., an MNN) is multihomed when it has several addresses to
choose between, i.e. in the following cases when it is either: choose between, i.e., in the following cases when it is:
o Multi-prefixed: multiple prefixes are advertised on the link(s) o Multi-prefixed: multiple prefixes are advertised on the link(s) to
the host is attached to, or which the host is attached, or
o Multi-interfaced: the host has multiple interfaces to choose o Multi-interfaced: the host has multiple interfaces to choose from,
between, on the same link or not. on or not on the same link.
5.2. Multihomed Mobile Router 5.2. Multihomed Mobile Router
From the definition of a multihomed host, it follows that a mobile From the definition of a multihomed host, it follows that a mobile
router is multihomed when it has several addresses to choose between, router is multihomed when it has several addresses to choose between,
i.e. in the following cases when the MR is either: i.e., in the following cases when the MR is:
o Multi-prefixed: multiple prefixes are advertised on the link(s) an o Multi-prefixed: multiple prefixes are advertised on the link(s) to
MR's egress interface is attached to, or. which an MR's egress interface is attached, or
o Multi-interfaced: the MR has multiple egress interfaces to choose o Multi-interfaced: the MR has multiple egress interfaces to choose
between, on the same link or not (see Figure 6). between, on or not on the same link (see Figure 6).
_____ _____
_ _ | | _ _ | |
|_|-| _ |-|_|-| |-| _ |_|-| _ |-|_|-| |-| _
_ |-|_|=| \ |_____| | _ |-|_| _ |-|_|=| \ |_____| | _ |-|_|
|_|-| | |-|_|-| |_|-| | |-|_|-|
\ | \ |
MNNs MR AR Internet AR HA MNNs MR AR Internet AR HA
Figure 6: Multihoming: MR with multiple E-faces Figure 6: Multihoming: MR with multiple E-faces
5.3. Multihomed Mobile Network (multihomed-NEMO) 5.3. Multihomed Mobile Network (multihomed-NEMO)
A mobile network is multihomed when either a MR is multihomed or A mobile network is multihomed when a MR is multihomed or there are
there are multiple MRs to choose between (see the corresponding multiple MRs to choose between (see the corresponding analysis in
analysis in [6]). [10]).
MR1 MR1
_ | _ |
_ |-|_|-| _____ _ |-|_|-| _____
|_|-| |-| | |_|-| |-| |
MNNs _ | | |-| _ MNNs _ | | |-| _
|_|-| _ |-|_____| | _ |-|_| |_|-| _ |-|_____| | _ |-|_|
|-|_|-| |-|_|-| |-|_|-| |-|_|-|
| | | |
MR2 MR2
skipping to change at page 14, line 32 skipping to change at page 12, line 32
5.4. Nested Multihomed Mobile Network 5.4. Nested Multihomed Mobile Network
A nested mobile network is multihomed when either a root-MR is A nested mobile network is multihomed when either a root-MR is
multihomed or there are multiple root-MRs to choose between. multihomed or there are multiple root-MRs to choose between.
5.5. Split-NEMO 5.5. Split-NEMO
Split-NEMO refers to the case where a mobile network becomes two or Split-NEMO refers to the case where a mobile network becomes two or
more independent mobile networks due to the separation of Mobile more independent mobile networks due to the separation of Mobile
Routers which are handling the same MNP (or MNPs) in the original Routers that are handling the same MNP (or MNPs) in the original
mobile network before the separation. mobile network before the separation.
5.6. Illustration 5.6. Illustration
Figure 6 and Figure 7 show two examples of multihomed mobile Figure 6 and Figure 7 show two examples of multihomed mobile
networks. Figure 8 shows two independent mobile networks. NEMO-1 is networks. Figure 8 shows two independent mobile networks. NEMO-1 is
single-homed to the Internet through MR1. NEMO-2 is multihomed to single-homed to the Internet through MR1. NEMO-2 is multihomed to
the Internet through MR2a and MR2b. Both mobile networks offer the Internet through MR2a and MR2b. Both mobile networks offer
access to visiting nodes and networks through an AR. access to visiting nodes and networks through an AR.
Let's consider the two following nested scenarios in Figure 8: Let's consider the two following nested scenarios in Figure 8:
Scenario 1: What happens when MR2a's egress interface is attached to Scenario 1: What happens when MR2a's egress interface is attached to
AR1 ? AR1 ?
* NEMO-2 becomes subservient of NEMO-1
* NEMO-1 becomes the parent-NEMO for NEMO-2 and the root-NEMO for * NEMO-2 becomes subservient to NEMO-1
* NEMO-1 becomes the parent-NEMO to NEMO-2 and the root-NEMO for
the aggregated nested mobile network the aggregated nested mobile network
* NEMO-2 becomes the sub-NEMO * NEMO-2 becomes the sub-NEMO
* MR1 is the root-MR for the aggregated nested mobile network * MR1 is the root-MR for the aggregated nested mobile network
* MR2a is a sub-MR in the aggregated nested mobile network * MR2a is a sub-MR in the aggregated nested mobile network
* NEMO-2 is still multihomed to the Internet through AR1 and ARz * NEMO-2 is still multihomed to the Internet through AR1 and ARz
* The aggregated nested mobile network is not multihomed, since * The aggregated nested mobile network is not multihomed, since
NEMO-2 cannot be used as a transit network for NEMO-1 NEMO-2 cannot be used as a transit network for NEMO-1
Scenario 2: What happens when MR1's egress interface is attached to Scenario 2: What happens when MR1's egress interface is attached to
AR2 ? AR2 ?
* NEMO-1 becomes subservient of NEMO-2 * NEMO-1 becomes subservient to NEMO-2
* NEMO-1 becomes the sub-NEMO * NEMO-1 becomes the sub-NEMO
* NEMO-2 becomes the parent_NEMO for NEMO-1 and also the root- * NEMO-2 becomes the parent_NEMO to NEMO-1 and also the root-NEMO
NEMO for the aggregated nested mobile network for the aggregated nested mobile network
* MR2a and MR2b are both root-MRs for the aggregated nested * MR2a and MR2b are both root-MRs for the aggregated nested
mobile network mobile network
* MR1 is a sub-MR in the aggregated nested mobile network * MR1 is a sub-MR in the aggregated nested mobile network
* NEMO-1 is not multihomed * NEMO-1 is not multihomed
* The aggregated nested mobile network is multihomed * The aggregated nested mobile network is multihomed
_ | _ | _ | _ |
|_|-|-|_|-| _ _____ |_|-|-|_|-| _ _____
NEMO-1 MNNs _ | MR1 |-|_|-| | NEMO-1 MNNs _ | MR1 |-|_|-| |
|_|-| ARx | |-| _ |_|-| ARx | |-| _
AR1 \ | | _ | | | _ |-|_| AR1 \ | | _ | | | _ |-|_|
_ |-|_|-| | |-|_|-| _ |-|_|-| | |-|_|-|
_ |-|_|-| ARy | | | _ |-|_|-| ARy | | |
|_|-| MR2a _ | | |_|-| MR2a _ | |
NEMO-2 MNNs _ | |-|_|-| | NEMO-2 MNNs _ | |-|_|-| |
|_|-| _ | ARz |_____| |_|-| _ | ARz |_____|
skipping to change at page 17, line 10 skipping to change at page 14, line 10
\ |-|_|-| \ |-|_|-|
AR2 MR2b AR2 MR2b
Figure 8: Nested Multihomed NEMO Figure 8: Nested Multihomed NEMO
6. Home Network Model Terms 6. Home Network Model Terms
The terms in this section are useful to describe the possible The terms in this section are useful to describe the possible
configurations of mobile networks at the home. For a better configurations of mobile networks at the home. For a better
understanding of the definitions, the reader is recommended to read understanding of the definitions, the reader is recommended to read
[7] where such configurations are detailed [6], where such configurations are detailed.
6.1. Home Link 6.1. Home Link
The link attached to the interface at the Home Agent on which the The link attached to the interface at the Home Agent on which the
Home Prefix is configured. The interface can be a virtual interface, Home Prefix is configured. The interface can be a virtual interface,
in which case the Home Link is a Virtual Home Link. in which case the Home Link is a Virtual Home Link.
6.2. Home Network 6.2. Home Network
The Network formed by the application of the Home Prefix to the Home The Network formed by the application of the Home Prefix to the Home
Link. With NEMO, the concept of Home Network is extended as Link. With NEMO, the concept of Home Network is extended as
explained below. explained below.
6.3. Home Address 6.3. Home Address
With Mobile IPv6, a Home Address is derived from the Home Network With Mobile IPv6, a Home Address is derived from the Home Network
prefix. This is generalized in NEMO, with some limitations: A Home prefix. This is generalized in NEMO with some limitations: A Home
Address can be derived either from the Home Network or from one of Address can be derived either from the Home Network or from one of
the Mobile Router's MNPs. the Mobile Router's MNPs.
6.4. Mobile Home Network 6.4. Mobile Home Network
A Mobile Network (NEMO) that is also a Home Network. The MR or one A Mobile Network (NEMO) that is also a Home Network. The MR, or one
of the MR(s) that owns the MNP may act as the Home Agent for the of the MR(s), that owns the MNP may act as the Home Agent for the
mobile nodes in the Mobile Home Network. mobile nodes in the Mobile Home Network.
6.5. Distributed Home Network 6.5. Distributed Home Network
A Distributed Home Network is a Home Network that is distributed A Distributed Home Network is a Home Network that is distributed
geographically between sites. The aggregated Home Prefix is geographically between sites. The aggregated Home Prefix is
partitioned between the sites and advertised by all sites. partitioned between the sites and advertised by all sites.
This aggregated Home Prefix can be further aggregated within a This aggregated Home Prefix can be further aggregated within a
service provider network or between service providers, to form a service provider network or between service providers, to form a
prefix that is announced into the Internet by the service provider(s) prefix that is announced into the Internet by the service provider(s)
from multiple points. from multiple points.
The sites may be connected using a mesh of private links and tunnels. The sites may be connected using a mesh of private links and tunnels.
A routing protocol is used within and between sites to exchange A routing protocol is used within and between sites to exchange
routes to the subnets associated to the sites, and, eventually, to routes to the subnets associated to the sites and, eventually, to
Mobile Routers registered off-site. Mobile Routers registered off-site.
6.6. Mobile Aggregated Prefix 6.6. Mobile Aggregated Prefix
An aggregation of Mobile Network Prefixes. An aggregation of Mobile Network Prefixes.
6.7. Aggregated Home Network 6.7. Aggregated Home Network
The Home Network associated with a Mobile Aggregated Prefix. This The Home Network associated with a Mobile Aggregated Prefix. This
Aggregation is advertised as a subnet on the Home Link, and thus used aggregation is advertised as a subnet on the Home Link, and thus used
as Home Network for NEMO purposes. as the Home Network for NEMO purposes.
6.8. Extended Home Network 6.8. Extended Home Network
The network associated with the aggregation of one or more Home The network associated with the aggregation of one or more Home
Network(s) and Mobile Network(s). As opposed to the Mobile IPv6 Home Network(s) and Mobile Network(s). As opposed to the Mobile IPv6 Home
Network that is a subnet, the extended Home Network is an aggregation Network that is a subnet, the Extended Home Network is an aggregation
and is further subnetted. and is further subnetted.
6.9. Virtual Home Network 6.9. Virtual Home Network
An aggregation of Mobile Network Prefixes that is in turn advertised An aggregation of Mobile Network Prefixes that is in turn advertised
as the Home Link Prefix. The Extended Home Network and the as the Home Link Prefix. The Extended Home Network and the
Aggregated Home Network can be configured as Virtual Home Network. Aggregated Home Network can be configured as Virtual Home Network.
7. Mobility Support Terms 7. Mobility Support Terms
7.1. Host Mobility Support 7.1. Host Mobility Support
Host Mobility Support is a mechanism which maintains session Host Mobility Support is a mechanism that maintains session
continuity between mobile nodes and their correspondents upon the continuity between mobile nodes and their correspondents upon the
mobile host's change of point of attachment. It can be achieved mobile host's change of point of attachment. It can be achieved
using Mobile IPv6 or other mobility support mechanisms. using Mobile IPv6 or other mobility support mechanisms.
7.2. Network Mobility Support (NEMO Support) 7.2. Network Mobility Support (NEMO Support)
Network Mobility Support is a mechanism which maintains session Network Mobility Support is a mechanism that maintains session
continuity between mobile network nodes and their correspondents upon continuity between mobile network nodes and their correspondents upon
a mobile router's change of point of attachment. Solutions for this a mobile router's change of point of attachment. Solutions for this
problem are classified into NEMO Basic Support, and NEMO Extended problem are classified into NEMO Basic Support, and NEMO Extended
Support. Support.
7.3. NEMO Basic Support 7.3. NEMO Basic Support
NEMO Basic Support is a solution to preserve session continuity by NEMO Basic Support is a solution to preserve session continuity by
means of bi-directional tunneling between MRs and their HAs much like means of bidirectional tunneling between MRs and their HAs, much like
what is done with Mobile IPv6 [4] for mobile nodes when Routing what is done with Mobile IPv6 [4] for mobile nodes when Routing
Optimization is not used. Only the HA and the MR are NEMO-enabled. Optimization is not used. Only the HA and the MR are NEMO-enabled.
RFC 3963 [5] is the solution specified by the NEMO Working Group for RFC 3963 [5] is the solution specified by the NEMO Working Group for
NEMO Basic Support. NEMO Basic Support.
7.4. NEMO Extended Support 7.4. NEMO Extended Support
NEMO Extended support is to provide the necessary optimization, NEMO Extended support is to provide performance optimizations,
including routing optimization between arbitrary MNNs and CNs. including routing optimization between arbitrary MNNs and CNs.
7.5. NEMO Routing Optimization (NEMO RO) 7.5. NEMO Routing Optimization (NEMO RO)
The term "Route Optimization" is accepted in a broader sense than The term "Route Optimization" is accepted in a broader sense than
already defined for IPv6 Host Mobility in [4] to loosely refer to any already defined for IPv6 Host Mobility in [4] to loosely refer to any
approach that optimizes the transmission of packets between a Mobile approach that optimizes the transmission of packets between a Mobile
Network Node and a Correspondent Node. Network Node and a Correspondent Node.
For more information about NEMO Route Optimization in the NEMO For more information about NEMO Route Optimization in the NEMO
context, see the problem statement [8] and the solution space context, see the problem statement [7] and the solution space
analysis [9]. analysis [8].
7.6. MRHA Tunnel 7.6. MRHA Tunnel
The bi-directional tunnel between a Mobile Router and its Home Agent. The bidirectional tunnel between a Mobile Router and its Home Agent.
7.7. Pinball Route 7.7. Pinball Route
A pinball route refers to the non-direct path taken by packets, which A pinball route refers to the non-direct path taken by packets, which
are routed via one or more Home Agents, as they transit between a are routed via one or more Home Agents, as they transit between a
Mobile Network Node and a Correspondent Node. Mobile Network Node and a Correspondent Node.
A packet following a pinball route would appear like a ball bouncing A packet following a pinball route would appear like a ball bouncing
off one or more Home Agents before reaching its final destination. off one or more Home Agents before reaching its final destination.
8. Security Considerations 8. Security Considerations
As this document only provides terminology and describes neither a As this document only provides terminology and describes neither a
protocol nor an implementation or a procedure, there are no security protocol, procedure, or an implementation, there are no security
considerations associated with it. considerations associated with it.
9. IANA Considerations 9. Acknowledgments
This document requires no IANA actions.
10. Acknowledgments
The material presented in this document takes most of the text from The material presented in this document takes most of the text from
internet-drafts initially submitted to the former MobileIP WG and the documents initially submitted to the former MobileIP WG and MONET BOF
MONET BOF and was published as part of a PhD dissertation [11]. The and was published as part of a PhD dissertation [11]. The authors
authors would therefore like to thank both Motorola Labs Paris and would therefore like to thank both Motorola Labs Paris and INRIA
INRIA (PLANETE team, Grenoble, France) where this terminology (PLANETE team, Grenoble, France), where this terminology originated,
originated, for the opportunity to bring it to the IETF, and for the opportunity to bring it to the IETF, and particularly Claude
particularly Claude Castelluccia for his advice, suggestions, and Castelluccia for his advice, suggestions, and direction, Alexandru
direction, Alexandru Petrescu and Christophe Janneteau. We also Petrescu and Christophe Janneteau. We also acknowledge input from
acknowledge input from Erik Nordmark, Hesham Soliman, Mattias Erik Nordmark, Hesham Soliman, Mattias Petterson, Marcelo Bagnulo,
Petterson, Marcelo Bagnulo, TJ Kniveton, Masafumi Watari, Chan-Wah T.J. Kniveton, Masafumi Watari, Chan-Wah Ng, JinHyeock Choi, and
Ng, JinHyeock Choi and numerous other people from the NEMO Working numerous other people from the NEMO Working Group. The Home Network
Group. The Home Network Model section is contributed by Pascal Model section is contributed by Pascal Thubert, Ryuji Wakikawa, and
Thubert, Ryuji Wakikawa and Vijay Devaparalli. Vijay Devaparalli.
11. References 10. References
11.1. Normative References 10.1. Normative References
[1] Ernst, T., "Network Mobility Support Goals and Requirements", [1] Ernst, T., "Network Mobility (NEMO) Support Goals and
draft-ietf-nemo-requirements-06 (work in progress), Requirements", RFC 4886, July 2007.
November 2006.
[2] Deering, S. and R. Hinden, "Internet Protocol Version 6 (IPv6)", [2] Deering, S. and R. Hinden, "Internet Protocol Version 6
RFC 2460, December 1998. (IPv6)", RFC 2460, December 1998.
[3] Manner, J. and M. Kojo, "Mobility Related Terminology", [3] Manner, J. and M. Kojo, "Mobility Related Terminology",
RFC 3753, June 2004. RFC 3753, June 2004.
[4] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in [4] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in
IPv6", RFC 3775, June 2004. IPv6", RFC 3775, June 2004.
[5] Devarapalli, V., Wakikawa, R., Petrescu, A., and P. Thubert, [5] Devarapalli, V., Wakikawa, R., Petrescu, A., and P. Thubert,
"Network Mobility (NEMO) Basic Support Protocol", RFC 3963, "Network Mobility (NEMO) Basic Support Protocol", RFC 3963,
January 2005. January 2005.
[6] Ng, C., Paik, Ernst, and C. Bagnulo, "Analysis of Multihoming in [6] Thubert, P., Wakikawa, R., and V. Devarapalli, "Network
Network Mobility Support", draft-ietf-nemo-multihoming-issues-06 Mobility (NEMO) Home Network Models", RFC 4887, July 2007.
(work in progress), June 2006.
[7] Thubert, P., Wakikawa, R., and V. Devarapalli, "NEMO Home
Network Models", draft-ietf-nemo-home-network-models-06 (work in
progress), February 2006.
[8] Ng, C., Thubert, P., Watari, M., and F. Zhao, "Network Mobility [7] Ng, C-W., Thubert, P., Watari, M., and F. Zhao, "Network
Route Optimization Problem Statement", Mobility Route Optimization Problem Statement", RFC 4888,
draft-ietf-nemo-ro-problem-statement-03 (work in progress), July 2007.
September 2006.
[9] Ng, C., Zhao, F., Watari, M., and P. Thubert, "Network Mobility [8] Ng, C-W., Zhao, F., Watari, M., and P. Thubert, "Network
Route Optimization Solution Space Analysis", Mobility Route Optimization Solution Space Analysis", RFC 4889,
draft-ietf-nemo-ro-space-analysis-03 (work in progress), July 2007.
September 2006.
11.2. Informative References 10.2. Informative References
[10] Abley, J., Black, B., and V. Gill, "Goals for IPv6 Site- [9] Abley, J., Black, B., and V. Gill, "Goals for IPv6 Site-
Multihoming Architectures", RFC 3582, August 2003. Multihoming Architectures", RFC 3582, August 2003.
[10] Ng, C-W., Paik, E-K., Ernst, T., and M. Bagnulo, "Analysis of
Multihoming in Network Mobility Support", Work in Progress,
February 2007.
[11] Ernst, T., "Network Mobility Support in IPv6", PhD's Thesis. , [11] Ernst, T., "Network Mobility Support in IPv6", PhD's Thesis. ,
Universite Joseph Fourier, Grenoble, France , October 2001. Universite Joseph Fourier, Grenoble, France , October 2001.
Authors' Addresses Authors' Addresses
Thierry Ernst Thierry Ernst
INRIA INRIA
INRIA Rocquencourt Rocquencourt
Domaine de Voluceau B.P. 105 Domaine de Voluceau B.P. 105
Le Chesnay, 78153 78153 Le Chesnay Cedex,
France France
Phone: +33 1 39 63 59 30 Phone: +33 (0)1 39 63 59 30
Fax: +33 1 39 63 54 91 Fax: +33 (0)1 39 63 54 91
Email: thierry.ernst@inria.fr EMail: thierry.ernst@inria.fr
URI: http://www-rocq.inria.fr/imara URI: http://www-rocq.inria.fr/imara
Hong-Yon Lach Hong-Yon Lach
Motorola Labs Paris Motorola
Espace Technologique - Saint Aubin Parc les Algorithmes - Saint-Aubin
Gif-sur-Yvette Cedex, 91 193 911193 Gif-sur-Yvette Cedex,
France France
Phone: +33-169-35-25-36 Phone: +33 (0)1 69-35-25-36
Fax: EMail: hong-yon.lach@motorola.com
Email: hong-yon.lach@motorola.com
URI:
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights 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 might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
skipping to change at page 26, line 45 skipping to change at page 19, line 45
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgment Acknowledgement
Funding for the RFC Editor function is provided by the IETF Funding for the RFC Editor function is currently provided by the
Administrative Support Activity (IASA). Internet Society.
 End of changes. 87 change blocks. 
263 lines changed or deleted 217 lines changed or added

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