4885
INFORMATIONAL
Network Mobility Support Terminology
Authors: T. Ernst, H-Y. Lach
Date: July 2007
Area: int
Working Group: nemo
Stream: IETF
Abstract
This document defines a terminology for discussing network mobility (NEMO) issues and solution requirements. This memo provides information for the Internet community.
RFC 4885
INFORMATIONAL
Errata Exist
Network Working Group T. Ernst
Request for Comments: 4885 INRIA
Category: Informational H-Y. Lach
Motorola
July 2007
<span class="h1">Network Mobility Support Terminology</span>
Status of This Memo
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 (C) The IETF Trust (2007).
Abstract
This document defines a terminology for discussing network mobility
(NEMO) issues and solution requirements.
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2">2</a>. Architectural Components . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2.1">2.1</a>. Mobile Network (NEMO) . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-2.2">2.2</a>. Mobile Subnet . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-2.3">2.3</a>. Mobile Router (MR) . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-2.4">2.4</a>. Egress Interface . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-2.5">2.5</a>. Ingress Interface . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-2.6">2.6</a>. Mobile Network Prefix (MNP) . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-2.7">2.7</a>. Mobile Network Node (MNN) . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-2.8">2.8</a>. Correspondent Node (CN) . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-2.9">2.9</a>. Correspondent Router (CR) . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-2.10">2.10</a>. Correspondent Entity (CE) . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-3">3</a>. Functional Terms . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-3.1">3.1</a>. Local Fixed Node (LFN) . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-3.2">3.2</a>. Visiting Mobile Node (VMN) . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-3.3">3.3</a>. Local Mobile Node (LMN) . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-3.4">3.4</a>. NEMO-Enabled Node (NEMO-Node) . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-3.5">3.5</a>. MIPv6-Enabled Node (MIPv6-Node) . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-4">4</a>. Nested Mobility Terms . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-4.1">4.1</a>. Nested Mobile Network (nested-NEMO) . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-4.2">4.2</a>. Root-NEMO . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-4.3">4.3</a>. Parent-NEMO . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<span class="grey">Ernst & Lach Informational [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc4885">RFC 4885</a> NEMO Terminology July 2007</span>
<a href="#section-4.4">4.4</a>. Sub-NEMO . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-4.5">4.5</a>. Root-MR . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-4.6">4.6</a>. Parent-MR . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-4.7">4.7</a>. Sub-MR . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-4.8">4.8</a>. Depth . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-5">5</a>. Multihoming Terms . . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
<a href="#section-5.1">5.1</a>. Multihomed Host or MNN . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
<a href="#section-5.2">5.2</a>. Multihomed Mobile Router . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
<a href="#section-5.3">5.3</a>. Multihomed Mobile Network (multihomed-NEMO) . . . . . . . <a href="#page-12">12</a>
<a href="#section-5.4">5.4</a>. Nested Multihomed Mobile Network . . . . . . . . . . . . . <a href="#page-12">12</a>
<a href="#section-5.5">5.5</a>. Split-NEMO . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
<a href="#section-5.6">5.6</a>. Illustration . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
<a href="#section-6">6</a>. Home Network Model Terms . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
<a href="#section-6.1">6.1</a>. Home Link . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
<a href="#section-6.2">6.2</a>. Home Network . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
<a href="#section-6.3">6.3</a>. Home Address . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
<a href="#section-6.4">6.4</a>. Mobile Home Network . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
<a href="#section-6.5">6.5</a>. Distributed Home Network . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
<a href="#section-6.6">6.6</a>. Mobile Aggregated Prefix . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
<a href="#section-6.7">6.7</a>. Aggregated Home Network . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
<a href="#section-6.8">6.8</a>. Extended Home Network . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
<a href="#section-6.9">6.9</a>. Virtual Home Network . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
<a href="#section-7">7</a>. Mobility Support Terms . . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
<a href="#section-7.1">7.1</a>. Host Mobility Support . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
<a href="#section-7.2">7.2</a>. Network Mobility Support (NEMO Support) . . . . . . . . . <a href="#page-15">15</a>
<a href="#section-7.3">7.3</a>. NEMO Basic Support . . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
<a href="#section-7.4">7.4</a>. NEMO Extended Support . . . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
<a href="#section-7.5">7.5</a>. NEMO Routing Optimization (NEMO RO) . . . . . . . . . . . <a href="#page-16">16</a>
<a href="#section-7.6">7.6</a>. MRHA Tunnel . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
<a href="#section-7.7">7.7</a>. Pinball Route . . . . . . . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
<a href="#section-8">8</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
<a href="#section-9">9</a>. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
<a href="#section-10">10</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-17">17</a>
<a href="#section-10.1">10.1</a>. Normative References . . . . . . . . . . . . . . . . . . . <a href="#page-17">17</a>
<a href="#section-10.2">10.2</a>. Informative References . . . . . . . . . . . . . . . . . . <a href="#page-17">17</a>
<span class="grey">Ernst & Lach Informational [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc4885">RFC 4885</a> NEMO Terminology July 2007</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
Network mobility support is concerned with managing the mobility of
an entire network. This arises when a router connecting a network to
the Internet dynamically changes its point of attachment to the fixed
infrastructure, thereby causing the reachability of the entire
network to be changed in relation to the fixed Internet topology.
Such a network is referred to as a mobile network. Without
appropriate mechanisms to support network mobility, sessions
established between nodes in the mobile network and the global
Internet cannot be maintained after the mobile router changes its
point of attachment. As a result, existing sessions would break and
connectivity to the global Internet would be lost.
This document defines the specific terminology needed to describe the
problem space, the design goals [<a href="#ref-1" title=""Network Mobility (NEMO) Support Goals and Requirements"">1</a>], and the solutions for network
mobility support. This terminology aims to be consistent with the
usual IPv6 terminology [<a href="#ref-2" title=""Internet Protocol Version 6 (IPv6)"">2</a>] and the generic mobility-related terms
already defined in the Mobility Related Terminology [<a href="#ref-3" title=""Mobility Related Terminology"">3</a>] and in the
Mobile IPv6 specification [<a href="#ref-4" title=""Mobility Support in IPv6"">4</a>]. Some terms introduced in this
document may only be useful for defining the problem scope and
functional requirements of network mobility support.
Note that the abbreviation NEMO stands for either "a NEtwork that is
MObile" or "NEtwork MObility". The former (see <a href="#section-2.1">Section 2.1</a>) is used
as a noun, e.g., "a NEMO" meaning "a mobile network". The latter
(see <a href="#section-7">Section 7</a>) refers to the concept of "network mobility", as in
"NEMO Basic Support", and is also the working group's name.
<a href="#section-2">Section 2</a> introduces terms to define the architecture, while terms
needed to emphasize the distinct functionalities of those
architectural components are described in <a href="#section-3">Section 3</a>. <a href="#section-4">Section 4</a>,
<a href="#section-5">Section 5</a>, and <a href="#section-6">Section 6</a> describe terms pertaining to nested
mobility, multihoming, and different configurations of mobile
networks at home, respectively. The different types of mobility are
defined in <a href="#section-7">Section 7</a>. The last section lists miscellaneous terms
that do not fit into any other section.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Architectural Components</span>
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
Internet by means of one or more mobile routers (MRs). Nodes behind
the MR (referred to as MNNs) primarily comprise fixed nodes (nodes
unable to change their point of attachment while maintaining ongoing
sessions), and possibly mobile nodes (nodes able to change their
point of attachment while maintaining ongoing sessions). In most
<span class="grey">Ernst & Lach Informational [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc4885">RFC 4885</a> NEMO Terminology July 2007</span>
cases, the internal structure of the mobile network will be stable
(no dynamic change of the topology), but this is not always true.
Figure 1 illustrates the architectural components involved in network
mobility and are defined in the following paragraphs: Mobile Router
(MR), Mobile Network (NEMO), Mobile Network Node (MNN), "ingress
interface", "egress interface", and Correspondent Node (CN). The
other terms, "access router" (AR), "Fixed Node (FN)", "Mobile Node
(MN)", "home agent" (HA), "home link", and "foreign link", are not
terms specific to network mobility and thus are defined in [<a href="#ref-3" title=""Mobility Related Terminology"">3</a>].
_
CN ->|_|-| Internet
| _____
|-| | |<- home link
_ | |-| _ | _
|-|_|-|_____| |-|_|-|-|_|<- HA (Home Agent)
| \ | _
foreign link ->| ^ |-|_|<- MR (Mobile Router)
.. AR (access ___|___
router) _| |_
|_| |_|
^ ^
MNN1 MNN2
Figure 1: Mobile Network on the Home Link
Figure 2 shows a single mobile subnet. Figure 3 illustrates a larger
mobile network comprising several subnets, attached to a foreign
link.
_
CN ->|_|-|
| _____
_ | |-| | |<- home link
|_|-| _ | _ | |-| _ | _
2 MNNs -> _ |-|_|-|-|_|-|_____| |-|_|-|-|_|<- HA
|_|-| . | \ \ |
| . |<- foreign ^AR
mobile subnet -> . link
.
^ MR
Figure 2: Single Mobile Subnet on a Foreign Link
<span class="grey">Ernst & Lach Informational [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc4885">RFC 4885</a> NEMO Terminology July 2007</span>
_
CN->|_|-|
mobile subnet->| | _____
_ | |-| | |<- home link
MNN1->|_|-|'i'_'e'| _ | |-| _ | _
|--|_|--|-|_|-|_____| |-|_|-|-|_|<- HA
'i'| | \ |
____|__ |
mobile subnet-^ _| . |<- foreign
|_| . link
MNN2 -^ .
^
MR
'i': MR's ingress interface
'e': MR's egress interface
Figure 3: Larger Mobile Network Made up of 2 Mobile Subnets
At the network layer, MRs get access to the global Internet from an
Access Router (AR) on a visited link. An MR maintains the Internet
connectivity for the entire mobile network. A given MR has one or
more egress interfaces and one or more ingress interfaces. When
forwarding a packet to the Internet, the packet is transmitted
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
packet is transmitted downstream through one of the MR's ingress
interfaces.
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Mobile Network (NEMO)</span>
As defined in [<a href="#ref-3" title=""Mobility Related Terminology"">3</a>]:
An entire network, moving as a unit, which dynamically changes its
point of attachment to the Internet and thus its reachability in the
topology. The mobile network is composed of one or more IP-subnets
and is connected to the global Internet via one or more Mobile
Routers (MR). The internal configuration of the mobile network is
assumed to be relatively stable with respect to the MR.
Rearrangement of the mobile network and changing the attachment point
of the egress interface to the foreign link are orthogonal processes
and do no affect each other.
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Mobile Subnet</span>
A link (subnet) that comprises, or is located within, the mobile
network.
<span class="grey">Ernst & Lach Informational [Page 5]</span><span id="page-6" ></span>
<span class="grey"><a href="./rfc4885">RFC 4885</a> NEMO Terminology July 2007</span>
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Mobile Router (MR)</span>
As defined in [<a href="#ref-3" title=""Mobility Related Terminology"">3</a>]:
A router capable of changing its point of attachment to the Internet,
moving from one link to another link. The MR is capable of
forwarding packets between two or more interfaces, and possibly
running a dynamic routing protocol modifying the state by which it
does packet forwarding.
An MR acts as a gateway between an entire mobile network and the rest
of the Internet, and has one or more egress interfaces and one or
more ingress interfaces. Packets forwarded upstream to the rest of
the Internet are transmitted through one of the MR's egress
interfaces; packets forwarded downstream to the mobile network are
transmitted through one of the MR's ingress interfaces.
<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. Egress Interface</span>
As defined in [<a href="#ref-3" title=""Mobility Related Terminology"">3</a>]:
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
network.
<span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>. Ingress Interface</span>
As defined in [<a href="#ref-3" title=""Mobility Related Terminology"">3</a>]:
The interface of an MR attached to a link inside the mobile network.
<span class="h3"><a class="selflink" id="section-2.6" href="#section-2.6">2.6</a>. Mobile Network Prefix (MNP)</span>
As defined in [<a href="#ref-3" title=""Mobility Related Terminology"">3</a>]:
A bit string that consists of some number of initial bits of an IP
address which identifies the entire mobile network within the
Internet topology. All nodes in a mobile network necessarily have an
address containing this prefix.
<span class="h3"><a class="selflink" id="section-2.7" href="#section-2.7">2.7</a>. Mobile Network Node (MNN)</span>
As defined in [<a href="#ref-3" title=""Mobility Related Terminology"">3</a>]:
Any node (host or router) located within a mobile network, either
permanently or temporarily. A Mobile Network Node may be either a
fixed node (LFN) or a mobile node (either VMN or LMN).
<span class="grey">Ernst & Lach Informational [Page 6]</span><span id="page-7" ></span>
<span class="grey"><a href="./rfc4885">RFC 4885</a> NEMO Terminology July 2007</span>
<span class="h3"><a class="selflink" id="section-2.8" href="#section-2.8">2.8</a>. Correspondent Node (CN)</span>
Any node that is communicating with one or more MNNs. A CN could be
either located within a fixed network or within a mobile network, and
could be either fixed or mobile.
<span class="h3"><a class="selflink" id="section-2.9" href="#section-2.9">2.9</a>. Correspondent Router (CR)</span>
Refers to the entity that is capable of terminating a Route
Optimization session on behalf of a Correspondent Node (see also NEMO
Route Optimization in <a href="#section-7.5">Section 7.5</a>).
<span class="h3"><a class="selflink" id="section-2.10" href="#section-2.10">2.10</a>. Correspondent Entity (CE)</span>
Refers to the entity with which a Mobile Router or Mobile Network
Node attempts to establish a Route Optimization session. Depending
on the Route Optimization approach, the Correspondent Entity may be a
Correspondent Node or Correspondent Router (see also NEMO Route
Optimization in <a href="#section-7.5">Section 7.5</a>).
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Functional Terms</span>
Within the term Mobile Network Node (MNN), we can distinguish between
Local Fixed Nodes (LFN), Visiting Mobile Nodes (VMN), and Local
Mobile Nodes (LMN). The distinction is a property of how different
types of nodes can move in the topology and is necessary to discuss
issues related to mobility management and access control; however, it
does not imply that network mobility or host mobility should be
handled differently. Nodes are classified according to their
function and capabilities with the rationale that nodes with
different properties may have different requirements.
Figure 4 illustrates a VMN changing its point of attachment from its
home link located outside the mobile network to within a mobile
network. The figure also illustrates an LMN changing its point of
attachment within the mobile network.
<span class="grey">Ernst & Lach Informational [Page 7]</span><span id="page-8" ></span>
<span class="grey"><a href="./rfc4885">RFC 4885</a> NEMO Terminology July 2007</span>
mobile subnet 1 | _ +++++++<<<+++++++++++
|-|_|-| + +
++<<<LMN-| \ | + |-MR
+ | + _____ | _ HA_MR
+ | _ | + | |-|-|_|
+ LMN _ |-|_|-| _ | _ | | _
++++>|_|-| \ |--|_|--|-|_|-|_____|-|-|_|
| | ^ | \ | HA_VMN
VMN _ | MR |
|_|-| |-VMN
^ mobile subnet 2 +
+ +
++++++++<<<+++++++++++++++++++++++++
+++>>>+++ = changing point of attachment
Figure 4: LFN vs LMM vs VMN
In a typical-use case of NEMO Basic Support [<a href="#ref-5" title=""Network Mobility (NEMO) Basic Support Protocol"">5</a>], only the MR and the
HA are NEMO-enabled. LFNs are not MIPv6-enabled nor NEMO-enabled.
On the other hand, a VMN or an LMN acting as a mobile router may be
NEMO-enabled, whereas a VMN or an LMN acting as a mobile node may be
MIPv6-enabled.
For NEMO Extended Support, details of the capabilities are not yet
known at the time of this writing, but NEMO-enabled nodes may be
expected to implement some sort of Route Optimization.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Local Fixed Node (LFN)</span>
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
maintaining ongoing sessions. Its address is taken from an MNP.
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Visiting Mobile Node (VMN)</span>
Either a mobile node (MN) or a mobile router (MR), assigned to a home
link that doesn't belong to the mobile network and that is able to
change its point of attachment while maintaining ongoing sessions. 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
taken from an MNP).
<span class="grey">Ernst & Lach Informational [Page 8]</span><span id="page-9" ></span>
<span class="grey"><a href="./rfc4885">RFC 4885</a> NEMO Terminology July 2007</span>
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Local Mobile Node (LMN)</span>
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
point of attachment while maintaining ongoing sessions. Its address
is taken from an MNP.
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. NEMO-Enabled Node (NEMO-Node)</span>
A node that has been extended with network mobility support
capabilities as described in NEMO specifications.
<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. MIPv6-Enabled Node (MIPv6-Node)</span>
A node that has been extended with host mobility support capabilities
as defined in the Mobile IPv6 specification [<a href="#ref-4" title=""Mobility Support in IPv6"">4</a>].
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Nested Mobility Terms</span>
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
visiting nodes to attach to it. There are two cases of nested
mobility:
o The attaching node is a single VMN (see Figure 4). For instance,
when a passenger carrying a mobile phone gets Internet access from
the public access network deployed on a bus.
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
PAN gets Internet access from the public access network deployed
on a bus.
For the second case, we introduce the following terms:
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Nested Mobile Network (nested-NEMO)</span>
A mobile network is said to be nested when a mobile network (sub-
NEMO) is attached to a larger mobile network (parent-NEMO). The
aggregated hierarchy of mobile networks becomes a single nested
mobile network (see Figure 5).
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Root-NEMO</span>
The mobile network at the top of the hierarchy connecting the
aggregated nested mobile networks to the Internet (see Figure 5).
<span class="grey">Ernst & Lach Informational [Page 9]</span><span id="page-10" ></span>
<span class="grey"><a href="./rfc4885">RFC 4885</a> NEMO Terminology July 2007</span>
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Parent-NEMO</span>
The upstream mobile network providing Internet access to another
mobile network further down the hierarchy (see Figure 5).
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. Sub-NEMO</span>
The downstream mobile network attached to another mobile network up
in the hierarchy. It becomes subservient of the parent-NEMO. The
sub-NEMO is getting Internet access through the parent-NEMO and does
not provide Internet access to the parent-NEMO (see Figure 5).
<span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a>. Root-MR</span>
The MR(s) of the root-NEMO used to connect the nested mobile network
to the fixed Internet (see Figure 5).
<span class="h3"><a class="selflink" id="section-4.6" href="#section-4.6">4.6</a>. Parent-MR</span>
The MR(s) of the parent-NEMO.
<span class="h3"><a class="selflink" id="section-4.7" href="#section-4.7">4.7</a>. Sub-MR</span>
The MR(s) of the sub-NEMO, which is connected to a parent-NEMO
<span class="h3"><a class="selflink" id="section-4.8" href="#section-4.8">4.8</a>. Depth</span>
In a nested NEMO, indicates the number of sub-MRs a packet has to
cross between a MNN and the root-MR.
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.
_____
_ | _ | |
_ |-|_|-| _ |-|_|-|-| |-| _
_ |-|_|-| \ |-|_|-| \ | |_____| | _ |-|_|
_ |-|_|-| | | | |-|_|-|
|_|-| \ | \ |
|
MNN AR sub-MR AR root-MR AR AR HA
<--------------><----------><----><---------><-------->
sub-NEMO root-NEMO fl Internet Home Network
Figure 5: Nested Mobility: a sub-NEMO attached to a larger mobile
network
<span class="grey">Ernst & Lach Informational [Page 10]</span><span id="page-11" ></span>
<span class="grey"><a href="./rfc4885">RFC 4885</a> NEMO Terminology July 2007</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Multihoming Terms</span>
Multihoming, as currently defined by the IETF, covers site-
multihoming [<a href="#ref-9" title=""Goals for IPv6 Site- Multihoming Architectures"">9</a>] and host multihoming. We enlarge this terminology to
include "multihomed mobile router" and "multihomed mobile network".
The specific configurations and issues pertaining to multihomed
mobile networks are covered in [<a href="#ref-10" title=""Analysis of Multihoming in Network Mobility Support"">10</a>].
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Multihomed Host or MNN</span>
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:
o Multi-prefixed: multiple prefixes are advertised on the link(s) to
which the host is attached, or
o Multi-interfaced: the host has multiple interfaces to choose from,
on or not on the same link.
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Multihomed Mobile Router</span>
From the definition of a multihomed host, it follows that a mobile
router is multihomed when it has several addresses to choose between,
i.e., in the following cases when the MR is:
o Multi-prefixed: multiple prefixes are advertised on the link(s) to
which an MR's egress interface is attached, or
o Multi-interfaced: the MR has multiple egress interfaces to choose
between, on or not on the same link (see Figure 6).
_____
_ _ | |
|_|-| _ |-|_|-| |-| _
_ |-|_|=| \ |_____| | _ |-|_|
|_|-| | |-|_|-|
\ |
MNNs MR AR Internet AR HA
Figure 6: Multihoming: MR with multiple E-faces
<span class="grey">Ernst & Lach Informational [Page 11]</span><span id="page-12" ></span>
<span class="grey"><a href="./rfc4885">RFC 4885</a> NEMO Terminology July 2007</span>
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Multihomed Mobile Network (multihomed-NEMO)</span>
A mobile network is multihomed when a MR is multihomed or there are
multiple MRs to choose between (see the corresponding analysis in
[<a href="#ref-10" title=""Analysis of Multihoming in Network Mobility Support"">10</a>]).
MR1
_ |
_ |-|_|-| _____
|_|-| |-| |
MNNs _ | | |-| _
|_|-| _ |-|_____| | _ |-|_|
|-|_|-| |-|_|-|
| |
MR2
Figure 7: Multihoming: NEMO with Multiple MRs
<span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. Nested Multihomed Mobile Network</span>
A nested mobile network is multihomed when either a root-MR is
multihomed or there are multiple root-MRs to choose between.
<span class="h3"><a class="selflink" id="section-5.5" href="#section-5.5">5.5</a>. Split-NEMO</span>
Split-NEMO refers to the case where a mobile network becomes two or
more independent mobile networks due to the separation of Mobile
Routers that are handling the same MNP (or MNPs) in the original
mobile network before the separation.
<span class="h3"><a class="selflink" id="section-5.6" href="#section-5.6">5.6</a>. Illustration</span>
Figure 6 and Figure 7 show two examples of multihomed mobile
networks. Figure 8 shows two independent mobile networks. NEMO-1 is
single-homed to the Internet through MR1. NEMO-2 is multihomed to
the Internet through MR2a and MR2b. Both mobile networks offer
access to visiting nodes and networks through an AR.
Let's consider the two following nested scenarios in Figure 8:
Scenario 1: What happens when MR2a's egress interface is attached to
AR1?
* NEMO-2 becomes subservient to NEMO-1
<span class="grey">Ernst & Lach Informational [Page 12]</span><span id="page-13" ></span>
<span class="grey"><a href="./rfc4885">RFC 4885</a> NEMO Terminology July 2007</span>
* NEMO-1 becomes the parent-NEMO to NEMO-2 and the root-NEMO for
the aggregated nested mobile network
* NEMO-2 becomes the sub-NEMO
* MR1 is the root-MR for 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
* The aggregated nested mobile network is not multihomed, since
NEMO-2 cannot be used as a transit network for NEMO-1
Scenario 2: What happens when MR1's egress interface is attached to
AR2?
* NEMO-1 becomes subservient to NEMO-2
* NEMO-1 becomes the sub-NEMO
* NEMO-2 becomes the parent_NEMO to NEMO-1 and also the root-NEMO
for the aggregated nested mobile network
* MR2a and MR2b are both root-MRs for the aggregated nested
mobile network
* MR1 is a sub-MR in the aggregated nested mobile network
* NEMO-1 is not multihomed
* The aggregated nested mobile network is multihomed
_ | _ |
|_|-|-|_|-| _ _____
NEMO-1 MNNs _ | MR1 |-|_|-| |
|_|-| ARx | |-| _
AR1 \ | | _ | | | _ |-|_|
_ |-|_|-| | |-|_|-|
_ |-|_|-| ARy | | |
|_|-| MR2a _ | |
NEMO-2 MNNs _ | |-|_|-| |
|_|-| _ | ARz |_____|
\ |-|_|-|
AR2 MR2b
Figure 8: Nested Multihomed NEMO
<span class="grey">Ernst & Lach Informational [Page 13]</span><span id="page-14" ></span>
<span class="grey"><a href="./rfc4885">RFC 4885</a> NEMO Terminology July 2007</span>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Home Network Model Terms</span>
The terms in this section are useful to describe the possible
configurations of mobile networks at the home. For a better
understanding of the definitions, the reader is recommended to read
[<a href="#ref-6" title=""Network Mobility (NEMO) Home Network Models"">6</a>], where such configurations are detailed.
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Home Link</span>
The link attached to the interface at the Home Agent on which the
Home Prefix is configured. The interface can be a virtual interface,
in which case the Home Link is a Virtual Home Link.
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Home Network</span>
The Network formed by the application of the Home Prefix to the Home
Link. With NEMO, the concept of Home Network is extended as
explained below.
<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. Home Address</span>
With Mobile IPv6, a Home Address is derived from the Home Network
prefix. This is generalized in NEMO with some limitations: A Home
Address can be derived either from the Home Network or from one of
the Mobile Router's MNPs.
<span class="h3"><a class="selflink" id="section-6.4" href="#section-6.4">6.4</a>. Mobile Home Network</span>
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
mobile nodes in the Mobile Home Network.
<span class="h3"><a class="selflink" id="section-6.5" href="#section-6.5">6.5</a>. Distributed Home Network</span>
A Distributed Home Network is a Home Network that is distributed
geographically between sites. The aggregated Home Prefix is
partitioned between the sites and advertised by all sites.
This aggregated Home Prefix can be further aggregated within a
service provider network or between service providers, to form a
prefix that is announced into the Internet by the service provider(s)
from multiple points.
The sites may be connected using a mesh of private links and tunnels.
A routing protocol is used within and between sites to exchange
routes to the subnets associated to the sites and, eventually, to
Mobile Routers registered off-site.
<span class="grey">Ernst & Lach Informational [Page 14]</span><span id="page-15" ></span>
<span class="grey"><a href="./rfc4885">RFC 4885</a> NEMO Terminology July 2007</span>
<span class="h3"><a class="selflink" id="section-6.6" href="#section-6.6">6.6</a>. Mobile Aggregated Prefix</span>
An aggregation of Mobile Network Prefixes.
<span class="h3"><a class="selflink" id="section-6.7" href="#section-6.7">6.7</a>. Aggregated Home Network</span>
The Home Network associated with a Mobile Aggregated Prefix. This
aggregation is advertised as a subnet on the Home Link, and thus used
as the Home Network for NEMO purposes.
<span class="h3"><a class="selflink" id="section-6.8" href="#section-6.8">6.8</a>. Extended Home Network</span>
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 that is a subnet, the Extended Home Network is an aggregation
and is further subnetted.
<span class="h3"><a class="selflink" id="section-6.9" href="#section-6.9">6.9</a>. Virtual Home Network</span>
An aggregation of Mobile Network Prefixes that is in turn advertised
as the Home Link Prefix. The Extended Home Network and the
Aggregated Home Network can be configured as Virtual Home Network.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Mobility Support Terms</span>
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Host Mobility Support</span>
Host Mobility Support is a mechanism that maintains session
continuity between mobile nodes and their correspondents upon the
mobile host's change of point of attachment. It can be achieved
using Mobile IPv6 or other mobility support mechanisms.
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Network Mobility Support (NEMO Support)</span>
Network Mobility Support is a mechanism that maintains session
continuity between mobile network nodes and their correspondents upon
a mobile router's change of point of attachment. Solutions for this
problem are classified into NEMO Basic Support, and NEMO Extended
Support.
<span class="h3"><a class="selflink" id="section-7.3" href="#section-7.3">7.3</a>. NEMO Basic Support</span>
NEMO Basic Support is a solution to preserve session continuity by
means of bidirectional tunneling between MRs and their HAs, much like
what is done with Mobile IPv6 [<a href="#ref-4" title=""Mobility Support in IPv6"">4</a>] for mobile nodes when Routing
Optimization is not used. Only the HA and the MR are NEMO-enabled.
<a href="./rfc3963">RFC 3963</a> [<a href="#ref-5" title=""Network Mobility (NEMO) Basic Support Protocol"">5</a>] is the solution specified by the NEMO Working Group for
NEMO Basic Support.
<span class="grey">Ernst & Lach Informational [Page 15]</span><span id="page-16" ></span>
<span class="grey"><a href="./rfc4885">RFC 4885</a> NEMO Terminology July 2007</span>
<span class="h3"><a class="selflink" id="section-7.4" href="#section-7.4">7.4</a>. NEMO Extended Support</span>
NEMO Extended support is to provide performance optimizations,
including routing optimization between arbitrary MNNs and CNs.
<span class="h3"><a class="selflink" id="section-7.5" href="#section-7.5">7.5</a>. NEMO Routing Optimization (NEMO RO)</span>
The term "Route Optimization" is accepted in a broader sense than
already defined for IPv6 Host Mobility in [<a href="#ref-4" title=""Mobility Support in IPv6"">4</a>] to loosely refer to any
approach that optimizes the transmission of packets between a Mobile
Network Node and a Correspondent Node.
For more information about NEMO Route Optimization in the NEMO
context, see the problem statement [<a href="#ref-7" title=""Network Mobility Route Optimization Problem Statement"">7</a>] and the solution space
analysis [<a href="#ref-8" title=""Network Mobility Route Optimization Solution Space Analysis"">8</a>].
<span class="h3"><a class="selflink" id="section-7.6" href="#section-7.6">7.6</a>. MRHA Tunnel</span>
The bidirectional tunnel between a Mobile Router and its Home Agent.
<span class="h3"><a class="selflink" id="section-7.7" href="#section-7.7">7.7</a>. Pinball Route</span>
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
Mobile Network Node and a Correspondent Node.
A packet following a pinball route would appear like a ball bouncing
off one or more Home Agents before reaching its final destination.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Considerations</span>
As this document only provides terminology and describes neither a
protocol, procedure, or an implementation, there are no security
considerations associated with it.
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Acknowledgments</span>
The material presented in this document takes most of the text from
documents initially submitted to the former MobileIP WG and MONET BOF
and was published as part of a PhD dissertation [<a href="#ref-11" title=""Network Mobility Support in IPv6"">11</a>]. The authors
would therefore like to thank both Motorola Labs Paris and INRIA
(PLANETE team, Grenoble, France), where this terminology originated,
for the opportunity to bring it to the IETF, and particularly Claude
Castelluccia for his advice, suggestions, and direction, Alexandru
Petrescu and Christophe Janneteau. We also acknowledge input from
Erik Nordmark, Hesham Soliman, Mattias Petterson, Marcelo Bagnulo,
T.J. Kniveton, Masafumi Watari, Chan-Wah Ng, JinHyeock Choi, and
numerous other people from the NEMO Working Group. The Home Network
<span class="grey">Ernst & Lach Informational [Page 16]</span><span id="page-17" ></span>
<span class="grey"><a href="./rfc4885">RFC 4885</a> NEMO Terminology July 2007</span>
Model section is contributed by Pascal Thubert, Ryuji Wakikawa, and
Vijay Devaparalli.
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. References</span>
<span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. Normative References</span>
[<a id="ref-1">1</a>] Ernst, T., "Network Mobility (NEMO) Support Goals and
Requirements", <a href="./rfc4886">RFC 4886</a>, July 2007.
[<a id="ref-2">2</a>] Deering, S. and R. Hinden, "Internet Protocol Version 6
(IPv6)", <a href="./rfc2460">RFC 2460</a>, December 1998.
[<a id="ref-3">3</a>] Manner, J. and M. Kojo, "Mobility Related Terminology",
<a href="./rfc3753">RFC 3753</a>, June 2004.
[<a id="ref-4">4</a>] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in
IPv6", <a href="./rfc3775">RFC 3775</a>, June 2004.
[<a id="ref-5">5</a>] Devarapalli, V., Wakikawa, R., Petrescu, A., and P. Thubert,
"Network Mobility (NEMO) Basic Support Protocol", <a href="./rfc3963">RFC 3963</a>,
January 2005.
[<a id="ref-6">6</a>] Thubert, P., Wakikawa, R., and V. Devarapalli, "Network
Mobility (NEMO) Home Network Models", <a href="./rfc4887">RFC 4887</a>, July 2007.
[<a id="ref-7">7</a>] Ng, C-W., Thubert, P., Watari, M., and F. Zhao, "Network
Mobility Route Optimization Problem Statement", <a href="./rfc4888">RFC 4888</a>,
July 2007.
[<a id="ref-8">8</a>] Ng, C-W., Zhao, F., Watari, M., and P. Thubert, "Network
Mobility Route Optimization Solution Space Analysis", <a href="./rfc4889">RFC 4889</a>,
July 2007.
<span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. Informative References</span>
[<a id="ref-9">9</a>] Abley, J., Black, B., and V. Gill, "Goals for IPv6 Site-
Multihoming Architectures", <a href="./rfc3582">RFC 3582</a>, August 2003.
[<a id="ref-10">10</a>] Ng, C-W., Paik, E-K., Ernst, T., and M. Bagnulo, "Analysis of
Multihoming in Network Mobility Support", Work in Progress,
February 2007.
[<a id="ref-11">11</a>] Ernst, T., "Network Mobility Support in IPv6", PhD's Thesis.,
Universite Joseph Fourier, Grenoble, France , October 2001.
<span class="grey">Ernst & Lach Informational [Page 17]</span><span id="page-18" ></span>
<span class="grey"><a href="./rfc4885">RFC 4885</a> NEMO Terminology July 2007</span>
Authors' Addresses
Thierry Ernst
INRIA
Rocquencourt
Domaine de Voluceau B.P. 105
78153 Le Chesnay Cedex,
France
Phone: +33 (0)1 39 63 59 30
Fax: +33 (0)1 39 63 54 91
EMail: [email protected]
URI: <a href="http://www-rocq.inria.fr/imara">http://www-rocq.inria.fr/imara</a>
Hong-Yon Lach
Motorola
Parc les Algorithmes - Saint-Aubin
911193 Gif-sur-Yvette Cedex,
France
Phone: +33 (0)1 69-35-25-36
EMail: [email protected]
<span class="grey">Ernst & Lach Informational [Page 18]</span><span id="page-19" ></span>
<span class="grey"><a href="./rfc4885">RFC 4885</a> NEMO Terminology July 2007</span>
Full Copyright Statement
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, 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 <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
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
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
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
[email protected].
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Ernst & Lach Informational [Page 19]
Annotations
Select text to annotate