draft-ietf-nemo-terminology-04.txt   draft-ietf-nemo-terminology-05.txt 
NEMO Working Group T. Ernst NEMO Working Group T. Ernst
Internet-Draft Keio University / WIDE Internet-Draft Keio University / WIDE
Expires: April 27, 2006 H-Y. Lach Expires: September 7, 2006 H-Y. Lach
Motorola Labs Motorola Labs
October 24, 2005 March 6, 2006
Network Mobility Support Terminology Network Mobility Support Terminology
draft-ietf-nemo-terminology-04 draft-ietf-nemo-terminology-05
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 35 skipping to change at page 1, line 35
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 27, 2006. This Internet-Draft will expire on September 7, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2006).
Abstract Abstract
This document defines a terminology for discussing network mobility This document defines a terminology for discussing network mobility
issues and solution requirements. issues and solution requirements.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Architectural Components . . . . . . . . . . . . . . . . . . . 5 2. Architectural Components . . . . . . . . . . . . . . . . . . . 5
2.1. Mobile Network (NEMO) . . . . . . . . . . . . . . . . . . 6 2.1. Mobile Network (NEMO) . . . . . . . . . . . . . . . . . . 6
2.2. Mobile Router (MR) . . . . . . . . . . . . . . . . . . . . 6 2.2. Mobile Subnet . . . . . . . . . . . . . . . . . . . . . . 7
2.3. Egress Interface (E-face) . . . . . . . . . . . . . . . . 7 2.3. Mobile Router (MR) . . . . . . . . . . . . . . . . . . . . 7
2.4. Ingress Interface (I-face) . . . . . . . . . . . . . . . . 7 2.4. Egress Interface . . . . . . . . . . . . . . . . . . . . . 7
2.5. Mobile Network Prefix (MNP) . . . . . . . . . . . . . . . 7 2.5. Ingress Interface . . . . . . . . . . . . . . . . . . . . 7
2.6. NEMO-link . . . . . . . . . . . . . . . . . . . . . . . . 7 2.6. Mobile Network Prefix (MNP) . . . . . . . . . . . . . . . 8
2.7. Mobile Network Node (MNN) . . . . . . . . . . . . . . . . 7 2.7. Mobile Network Node (MNN) . . . . . . . . . . . . . . . . 8
2.8. Correspondent Node (CN) . . . . . . . . . . . . . . . . . 7 2.8. Correspondent Node (CN) . . . . . . . . . . . . . . . . . 8
2.9. Correspondent Router (CR) . . . . . . . . . . . . . . . . 8 2.9. Correspondent Router (CR) . . . . . . . . . . . . . . . . 8
2.10. Correspondent Entity (CE) . . . . . . . . . . . . . . . . 8 2.10. Correspondent Entity (CE) . . . . . . . . . . . . . . . . 8
3. Functional Terms . . . . . . . . . . . . . . . . . . . . . . . 9 3. Functional Terms . . . . . . . . . . . . . . . . . . . . . . . 9
3.1. Local Fixed Node (LFN) . . . . . . . . . . . . . . . . . . 9 3.1. Local Fixed Node (LFN) . . . . . . . . . . . . . . . . . . 10
3.2. Visiting Mobile Node (VMN) . . . . . . . . . . . . . . . . 9 3.2. Visiting Mobile Node (VMN) . . . . . . . . . . . . . . . . 10
3.3. Local Mobile Node (LMN) . . . . . . . . . . . . . . . . . 10 3.3. Local Mobile Node (LMN) . . . . . . . . . . . . . . . . . 10
3.4. NEMO-enabled node (NEMO-node) . . . . . . . . . . . . . . 10 3.4. NEMO-enabled node (NEMO-node) . . . . . . . . . . . . . . 10
3.5. MIPv6-enabled (MIPv6-node) . . . . . . . . . . . . . . . . 10 3.5. MIPv6-enabled (MIPv6-node) . . . . . . . . . . . . . . . . 10
4. Nested Mobility Terms . . . . . . . . . . . . . . . . . . . . 11 4. Nested Mobility Terms . . . . . . . . . . . . . . . . . . . . 11
4.1. Nested Mobile Network (nested-NEMO) . . . . . . . . . . . 11 4.1. Nested Mobile Network (nested-NEMO) . . . . . . . . . . . 11
4.2. root-NEMO . . . . . . . . . . . . . . . . . . . . . . . . 11 4.2. Root-NEMO . . . . . . . . . . . . . . . . . . . . . . . . 11
4.3. parent-NEMO . . . . . . . . . . . . . . . . . . . . . . . 11 4.3. Parent-NEMO . . . . . . . . . . . . . . . . . . . . . . . 11
4.4. sub-NEMO . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.4. Sub-NEMO . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.5. root-MR . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.5. Root-MR . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.6. parent-MR . . . . . . . . . . . . . . . . . . . . . . . . 12 4.6. Parent-MR . . . . . . . . . . . . . . . . . . . . . . . . 12
4.7. sub-MR . . . . . . . . . . . . . . . . . . . . . . . . . . 12 4.7. Sub-MR . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.8. Depth . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5. Multihoming Terms . . . . . . . . . . . . . . . . . . . . . . 13 5. Multihoming Terms . . . . . . . . . . . . . . . . . . . . . . 13
5.1. Multihomed host or MNN . . . . . . . . . . . . . . . . . . 13 5.1. Multihomed host or MNN . . . . . . . . . . . . . . . . . . 13
5.2. Multihomed Mobile Router . . . . . . . . . . . . . . . . . 13 5.2. Multihomed Mobile Router . . . . . . . . . . . . . . . . . 13
5.3. Multihomed Mobile Network (multihomed-NEMO) . . . . . . . 14 5.3. Multihomed Mobile Network (multihomed-NEMO) . . . . . . . 14
5.4. Nested Multihomed Mobile Network . . . . . . . . . . . . . 14 5.4. Nested Multihomed Mobile Network . . . . . . . . . . . . . 14
5.5. Illustration . . . . . . . . . . . . . . . . . . . . . . . 14 5.5. Split NEMO . . . . . . . . . . . . . . . . . . . . . . . . 14
5.6. Illustration . . . . . . . . . . . . . . . . . . . . . . . 14
6. Home Network Model Terms . . . . . . . . . . . . . . . . . . . 17 6. Home Network Model Terms . . . . . . . . . . . . . . . . . . . 17
6.1. Home Link . . . . . . . . . . . . . . . . . . . . . . . . 17 6.1. Home Link . . . . . . . . . . . . . . . . . . . . . . . . 17
6.2. Home Network . . . . . . . . . . . . . . . . . . . . . . . 17 6.2. Home Network . . . . . . . . . . . . . . . . . . . . . . . 17
6.3. Home Address . . . . . . . . . . . . . . . . . . . . . . . 17 6.3. Home Address . . . . . . . . . . . . . . . . . . . . . . . 17
6.4. Mobile Home Network . . . . . . . . . . . . . . . . . . . 17 6.4. Mobile Home Network . . . . . . . . . . . . . . . . . . . 17
6.5. Distributed Home Network . . . . . . . . . . . . . . . . . 17 6.5. Distributed Home Network . . . . . . . . . . . . . . . . . 17
6.6. Mobile Aggregated Prefix . . . . . . . . . . . . . . . . . 17 6.6. Mobile Aggregated Prefix . . . . . . . . . . . . . . . . . 17
6.7. Aggregated Home Network . . . . . . . . . . . . . . . . . 17 6.7. Aggregated Home Network . . . . . . . . . . . . . . . . . 17
6.8. Extended Home Network . . . . . . . . . . . . . . . . . . 18 6.8. Extended Home Network . . . . . . . . . . . . . . . . . . 18
6.9. Virtual Home Network . . . . . . . . . . . . . . . . . . . 18 6.9. Virtual Home Network . . . . . . . . . . . . . . . . . . . 18
7. Mobility Support Terms . . . . . . . . . . . . . . . . . . . . 19 7. Mobility Support Terms . . . . . . . . . . . . . . . . . . . . 19
7.1. Host Mobility Support . . . . . . . . . . . . . . . . . . 19 7.1. Host Mobility Support . . . . . . . . . . . . . . . . . . 19
7.2. Network Mobility Support (NEMO Support) . . . . . . . . . 19 7.2. Network Mobility Support (NEMO Support) . . . . . . . . . 19
7.3. NEMO Basic Support . . . . . . . . . . . . . . . . . . . . 19 7.3. NEMO Basic Support . . . . . . . . . . . . . . . . . . . . 19
7.4. NEMO Extended Support . . . . . . . . . . . . . . . . . . 19 7.4. NEMO Extended Support . . . . . . . . . . . . . . . . . . 19
7.5. MRHA Tunnel . . . . . . . . . . . . . . . . . . . . . . . 19 7.5. NEMO Routing Optimization (NEMO RO) . . . . . . . . . . . 19
7.6. MRHA Tunnel . . . . . . . . . . . . . . . . . . . . . . . 19
7.7. Pinball Route . . . . . . . . . . . . . . . . . . . . . . 19
8. Security Considerations . . . . . . . . . . . . . . . . . . . 20 8. Security Considerations . . . . . . . . . . . . . . . . . . . 21
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 22 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 23
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 24
11.1. Normative References . . . . . . . . . . . . . . . . . . . 23 11.1. Normative References . . . . . . . . . . . . . . . . . . . 24
11.2. Informative References . . . . . . . . . . . . . . . . . . 23 11.2. Informative References . . . . . . . . . . . . . . . . . . 24
Appendix A. Change Log From Earlier Versions . . . . . . . . . . 24 Appendix A. Change Log From Earlier Versions . . . . . . . . . . 25
A.1. Changes since draft-nemo-terminology-03.txt . . . . . . . 24 A.1. Changes since draft-nemo-terminology-04.txt . . . . . . . 25
A.2. Changes since draft-nemo-terminology-02.txt . . . . . . . 24 A.2. Changes since draft-nemo-terminology-03.txt . . . . . . . 26
A.3. Changes since draft-nemo-terminology-01.txt . . . . . . . 24 A.3. Changes since draft-nemo-terminology-02.txt . . . . . . . 26
A.4. Changes since draft-nemo-terminology-00.txt . . . . . . . 25 A.4. Changes since draft-nemo-terminology-01.txt . . . . . . . 26
A.5. Changes since draft-nemo-terminology-00.txt . . . . . . . 27
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 26 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 28
Intellectual Property and Copyright Statements . . . . . . . . . . 27 Intellectual Property and Copyright Statements . . . . . . . . . . 29
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 5, line 7 skipping to change at page 5, line 7
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 mobility,
multihoming and different configurations of mobile networks at home, multihoming and different configurations of mobile networks at home,
respectively. The different types of mobility are defined in respectively. The different types of mobility are defined in
Section 7. The last section lists miscellaneous terms which do not Section 7. The last section lists miscellaneous terms which do not
fit in any other section. fit in any other section.
2. Architectural Components 2. Architectural Components
A mobile network is composed of one or more mobile IP-subnets (NEMO- A mobile network is composed of one or more mobile IP-subnets and is
link) and is viewed as a single unit. This network unit is connected viewed as a single unit. This network unit is connected to the
to the Internet by means of one or more mobile routers (MRs). Nodes Internet by means of one or more mobile routers (MRs). Nodes behind
behind the MR (referred to as MNNs) primarily comprise fixed nodes the MR (referred to as MNNs) primarily comprise fixed nodes (nodes
(nodes unable to change their point of attachment while maintaining unable to change their point of attachment while maintaining ongoing
ongoing sessions), and possibly mobile nodes (nodes able to change sessions), and possibly mobile nodes (nodes able to change their
their point of attachment while maintaining ongoing sessions). In point of attachment while maintaining ongoing sessions). In most
most cases, the internal structure of the mobile network will be cases, the internal structure of the mobile network will be stable
stable (no dynamic change of the topology), but this is not always (no dynamic change of the topology), but this is not always true.
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 defined in the following paragraphs: Mobile Router (MR),
NEMO-link, Mobile Network Node (MNN), "ingress interface", "egress Mobile Network (NEMO), Mobile Network Node (MNN), "ingress
interface", and Correspondent Node (CN). The other terms "access interface", "egress interface", and Correspondent Node (CN). The
router" (AR), "Fixed Node (FN)", "Mobile Node (MN)", "home agent" other terms "access router" (AR), "Fixed Node (FN)", "Mobile Node
(HA), "home link" and "foreign link" are not terms specific to (MN)", "home agent" (HA), "home link" and "foreign link" are not
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 subnetwork. Figure 3 illustrates a Figure 2 shows a single mobile subnet. Figure 3 illustrates a larger
larger mobile network comprising several subnetworks, attached to a mobile network comprising several subnetworks, attached to a foreign
foreign link. link.
_ _
CN ->|_|-| CN ->|_|-|
| _____ | _____
_ | |-| | |<- home link _ | |-| | |<- home link
|_|-| _ | _ | |-| _ | _ |_|-| _ | _ | |-| _ | _
2 MNNs -> _ |-|_|-|-|_|-|_____| |-|_|-|-|_|<- HA 2 MNNs -> _ |-|_|-|-|_|-|_____| |-|_|-|-|_|<- HA
|_|-| . | \ \ | |_|-| . | \ \ |
| . |<- foreign ^AR | . |<- foreign ^AR
single NEMO-link -> . link mobile subnet -> . link
. .
^ MR ^ MR
Figure 2: Single Mobile Subnetwork on a Foreign Link Figure 2: Single Mobile Subnet on a Foreign Link
_
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 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 the
Access Router(s) (AR) on a visited link. An MR maintains the Access Router(s) (AR) on a visited link. An MR maintains the
Internet connectivity for the entire mobile network. A given MR has Internet connectivity for the entire mobile network. A given MR has
one or more egress interface and one or more ingress interface. When one or more egress interface and one or more ingress interface. 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.
skipping to change at page 6, line 44 skipping to change at page 7, line 16
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 Re-arrangement of the mobile network and changing the attachment
point of the egress interface to the foreign link are orthogonal point of the egress interface to the foreign link are orthogonal
processes and do no affect each other. processes and do no affect each other.
2.2. Mobile Router (MR) 2.2. Mobile Subnet
A link (subnet) which comprises, or is located within, the mobile
network.
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 interface and one or more
ingress interface. Packets forwarded upstream to the rest of the ingress interface. Packets forwarded upstream to the rest of the
Internet are transmitted through one of the MR's egress interfaces; Internet are transmitted through one of the MR's egress interfaces;
packets forwarded downstream to the mobile network are transmitted packets forwarded downstream to the mobile network are transmitted
through one of the MR's ingress interfaces. through one of the MR's ingress interfaces.
2.3. Egress Interface (E-face) 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.4. Ingress Interface (I-face) 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.5. Mobile Network Prefix (MNP) 2.6. Mobile Network Prefix (MNP)
As defined in [3]: As defined in [3]:
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.6. NEMO-link
A link (subnet) which comprises, or is located within, the mobile
network.
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 either be a
fixed node (LFN) or a mobile node (VMN or LMN). fixed node (LFN) or a mobile node (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 another mobile
network, and could be either fixed or mobile. network, and could be either fixed or mobile.
2.9. Correspondent Router (CR) 2.9. Correspondent Router (CR)
This refers to the entity which is capable of terminating a Route Refers to the entity which is capable of terminating a Route
Optimization [7] session on behalf of a Correspondent Node. Optimization session on behalf of a Correspondent Node (see also NEMO
Route Optimization in Section 7.5).
2.10. Correspondent Entity (CE) 2.10. Correspondent Entity (CE)
This refers to the entity which a Mobile Router or Mobile Network Refers to the entity which a Mobile Router or Mobile Network Node
Node attempts to establish a Route Optimization session with. attempts to establish a Route Optimization session with. Depending
Depending on the Route Optimization approach [7], the Correspondent on the Route Optimization approach, the Correspondent Entity maybe a
Entity maybe a Correspondent Node or Correspondent Router. Correspondent Node or Correspondent Router (see also NEMO Route
Optimization in Section 7.5)
3. Functional Terms 3. Functional Terms
_
CN->|_|-|
NEMO-link 1->| | _____
_ | |-| | |<- home link
MNN1->|_|-|'i'_'e'| _ | |-| _ | _
|--|_|--|-|_|-|_____| |-|_|-|-|_|<- HA
'i'| | \ |
____|__ |
NEMO-link 2-^ _| . |<- foreign
|_| . link
MNN2 -^ .
^
MR
'i': MR's ingress interface
'e': MR's egress interface
Figure 3: Larger Mobile Network with 2 subnets
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 Mobile
Nodes (LMN). The distinction is a property of how different types of Nodes (LMN). The distinction is a property of how different types of
nodes can move in the topology and is necessary to discuss issues nodes can move in the topology and is necessary to discuss issues
related to mobility management and access control; however it does related to mobility management and access control; however it does
not imply that network mobility or host mobility should be handled not imply that network mobility or host mobility should be handled
differently. Nodes are classified according to their function and differently. Nodes are classified according to their function and
capabilities with the rationale that nodes with different properties capabilities with the rationale that nodes with different properties
may have different requirements. 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 a LMN changing its point of
attachment within the mobile network.
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 [5], only the MR and the
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
NEMO-enabled whereas a VMN or a LMN acting as a mobile node may be
MIPv6-enabled.
For NEMO Extended Support, details of the capabilities are not known
yet at the time of this writing, but NEMO-enabled nodes may be
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 located within 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 which 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 NEMO-link (used as a foreign VMN that is temporarily attached to a mobile subnet (used as a
link) obtains an address on that link (i.e. the address is taken from foreign link) obtains an address on that subnet (i.e. the address is
an MNP). Figure 4 illustrates a VMN changing its point of attachment taken from an MNP).
from its HA to within a mobile network.
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. Figure 4 illustrates a LMN changing its point is taken from an MNP.
of attachment within the mobile network.
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.
In NEMO Basic Support [5], only the MR and the HA are NEMO-enabled.
For NEMO Extended Support, details of the capabilities are not known
yet at the time of this writing, but NEMO-enabled nodes may be
expected to implement some sort of Route Optimization.
NEMO-link 1 | _ +++++++<<<+++++++++++
|-|_|-| + +
++<<<LMN-| \ | + |-MR
+ | + _____ | _ HA_MR
+ | _ | + | |-|-|_|
+ LMN _ |-|_|-| _ | _ | | _
++++>|_|-| \ |--|_|--|-|_|-|_____|-|-|_|
| | ^ | \ | HA_VMN
VMN _ | MR |
|_|-| |-VMN
^ NEMO-link 2 +
+ +
++++++++<<<+++++++++++++++++++++++++
+++>+++ = changing point of attachment
Figure 4: LFN vs LMM vs VMN
3.5. MIPv6-enabled (MIPv6-node) 3.5. MIPv6-enabled (MIPv6-node)
A node which has been extended with host mobility support A node which has been extended with host mobility support
capabilities as defined in the Mobile IPv6 specification [4]. capabilities 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
skipping to change at page 11, line 30 skipping to change at page 11, line 30
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
aggregated hierarchy of mobile networks becomes a single nested aggregated hierarchy of mobile networks becomes a single nested
mobile network (see Figure 5). mobile network (see Figure 5).
4.2. root-NEMO 4.2. Root-NEMO
The mobile network at the top of the hierarchy connecting the The mobile network at the top of the hierarchy connecting the
aggregated nested mobile networks to the Internet (see Figure 5). aggregated nested mobile networks to the Internet (see Figure 5).
4.3. parent-NEMO 4.3. Parent-NEMO
The upstream mobile network providing Internet access to another The upstream mobile network providing Internet access to another
mobile network further down the hierarchy (see Figure 5). mobile network further down the hierarchy (see Figure 5).
4.4. sub-NEMO 4.4. Sub-NEMO
The downstream mobile network attached to another mobile network up The downstream mobile network attached to another mobile network up
in the hierarchy. It becomes subservient of the parent-NEMO. The in the hierarchy. It becomes subservient of the parent-NEMO. The
sub-NEMO is getting Internet access through the parent-NEMO and does sub-NEMO is getting Internet access through the parent-NEMO and does
not provide Internet access to the parent-NEMO (see Figure 5). not provide Internet access to the parent-NEMO (see Figure 5).
4.5. root-MR 4.5. Root-MR
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). Note: was referred to as to the fixed Internet (see Figure 5).
"TMLR" (Top-Level Mobile Router) in former versions of this document
.
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
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 a 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 MNN AR sub-MR AR root-MR AR AR HA
<--------------><----------><----><---------><--------> <--------------><----------><----><---------><-------->
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 [8] and host multihoming. We enlarge this terminology to multihoming [10] and host multihoming. We enlarge this terminology
include "multihomed mobile router" and "multihomed mobile network". to include "multihomed mobile router" and "multihomed mobile
The specific configurations and issues pertaining to multihomed network". The specific configurations and issues pertaining to
mobile networks are covered in [9]. multihomed mobile networks are covered in [6].
5.1. Multihomed host or MNN 5.1. Multihomed host or MNN
A host (e.g. an MNN) is multihomed when it has several IPv6 addresses A host (e.g. an MNN) is multihomed when it has several addresses to
to choose between, i.e. in the following cases when it is either: choose between, i.e. in the following cases when it is either:
Multi-prefixed: multiple prefixes are advertised on the link(s) Multi-prefixed: multiple prefixes are advertised on the link(s)
the host is attached to, or the host is attached to, or
Multi-interfaced: the host has multiple interfaces to choose Multi-interfaced: the host has multiple interfaces to choose
between, on the same link or not. between, on the same link or not.
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 IPv6 addresses to choose router is multihomed when it has several addresses to choose between,
between, i.e. in the following cases when the MR is either: i.e. in the following cases when the MR is either:
Multi-prefixed: multiple prefixes are advertised on the link(s) an Multi-prefixed: multiple prefixes are advertised on the link(s) an
MR's egress interface is attached to, or. MR's egress interface is attached to, or.
Multi-interfaced: the MR has multiple egress interfaces to choose Multi-interfaced: the MR has multiple egress interfaces to choose
between, on the same link or not (see Figure 6). between, on the same link or not (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 either a MR is multihomed or
there are multiple MRs to choose between, or multiple prefixes are there are multiple MRs to choose between (see the corresponding
advertised in the mobile network. analysis in [6]).
MR1 MR1
_ | _ |
_ |-|_|-| _____ _ |-|_|-| _____
|_|-| |-| | |_|-| |-| |
MNNs _ | | |-| _ MNNs _ | | |-| _
|_|-| _ |-|_____| | _ |-|_| |_|-| _ |-|_____| | _ |-|_|
|-|_|-| |-|_|-| |-|_|-| |-|_|-|
| | | |
MR2 MR2
Figure 7: Multihoming: Single NEMO-link with Multiple MRs Figure 7: Multihoming: NEMO with Multiple MRs
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 or multihomed or there are multiple root-MRs to choose between.
multiple prefixes are advertised in the nested mobile network.
5.5. Illustration 5.5. Split NEMO
TBD. See the "issue" web page http://www.sfc.wide.ad.jp/~ernst/nemo/
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
skipping to change at page 16, line 4 skipping to change at page 16, line 16
NEMO-1 MNNs _ | MR1 |-|_|-| | NEMO-1 MNNs _ | MR1 |-|_|-| |
|_|-| ARx | |-| _ |_|-| ARx | |-| _
AR1 \ | | _ | | | _ |-|_| AR1 \ | | _ | | | _ |-|_|
_ |-|_|-| | |-|_|-| _ |-|_|-| | |-|_|-|
_ |-|_|-| ARy | | | _ |-|_|-| ARy | | |
|_|-| MR2a _ | | |_|-| MR2a _ | |
NEMO-2 MNNs _ | |-|_|-| | NEMO-2 MNNs _ | |-|_|-| |
|_|-| _ | ARz |_____| |_|-| _ | ARz |_____|
\ |-|_|-| \ |-|_|-|
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. Such configurations configurations of mobile networks at the home. For a better
are detailed in [6] understanding of the definitions, the reader is recommended to read
[7] 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
skipping to change at page 19, line 35 skipping to change at page 19, line 35
means of bi-directional tunneling between MRs and their HAs much like means of bi-directional 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.
The solution for doing this is solely specified in [5]. The solution for doing this is solely specified in [5].
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 the necessary optimization,
including routing optimization between arbitrary MNNs and CNs. including routing optimization between arbitrary MNNs and CNs.
7.5. MRHA Tunnel 7.5. NEMO Routing Optimization (NEMO RO)
The term "Route Optimization" is accepted in a broader sense than
already defined for IPv6 Host Mobility in [4] 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 [8] and the solution space
analysis [9].
7.6. MRHA Tunnel
The bi-directional tunnel between a Mobile Router and its Home Agent. The bi-directional tunnel between a Mobile Router and its Home Agent.
7.7. Pinball Route
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.
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 nor an implementation or a procedure, there are no security
considerations associated with it. considerations associated with it.
9. IANA Considerations 9. IANA Considerations
This document requires no IANA actions. This document requires no IANA actions.
10. Acknowledgments 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 submitted to the former MobileIP WG and the MONET internet-drafts initially submitted to the former MobileIP WG and the
BOF. The authors would therefore like to thank both Motorola Labs MONET BOF and was published as part of a PhD dissertation [11]. The
Paris and INRIA (PLANETE team, Grenoble, France) where this authors would therefore like to thank both Motorola Labs Paris and
terminology originated, for the opportunity to bring it to the IETF, INRIA (PLANETE team, Grenoble, France) where this terminology
and particularly Claude Castelluccia for his advice, suggestion, and 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 direction, Alexandru Petrescu and Christophe Janneteau. We also
acknowledge input from Hesham Soliman, Mattias Petterson, Marcelo acknowledge input from Erik Nordmark, Hesham Soliman, Mattias
Bagnulo, TJ Kniveton and numerous other people from the NEMO Working Petterson, Marcelo Bagnulo, TJ Kniveton, Masafumi Watari, Chan-Wah
Ng, JinHyeock Choi and numerous other people from the NEMO Working
Group. The Home Network Model section is contributed by Pascal Group. The Home Network Model section is contributed by Pascal
Thubert, Ryuji Wakikawa and Vijay Devaparalli. Thubert, Ryuji Wakikawa and Vijay Devaparalli.
11. References 11. References
11.1. Normative References 11.1. Normative References
[1] Ernst, T., "Network Mobility Support Goals and Requirements", [1] Ernst, T., "Network Mobility Support Goals and Requirements",
draft-ietf-nemo-requirements-05 (work in progress), draft-ietf-nemo-requirements-05 (work in progress),
October 2005. October 2005.
skipping to change at page 23, line 26 skipping to change at page 24, line 26
[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] Thubert, P., Wakikawa, R., and V. Devarapalli, "NEMO Home [6] Ng, C., "Analysis of Multihoming in Network Mobility Support",
draft-ietf-nemo-multihoming-issues-05 (work in progress),
February 2006.
[7] Thubert, P., Wakikawa, R., and V. Devarapalli, "NEMO Home
Network Models", draft-ietf-nemo-home-network-models-05 (work in Network Models", draft-ietf-nemo-home-network-models-05 (work in
progress), June 2005. progress), June 2005.
11.2. Informative References [8] Ng, C., Pascal, P., Masafumi, M., and F. Fan, "Network Mobility
Route Optimization Problem Statement",
[7] Ng, C., "Network Mobility Route Optimization Problem Statement",
draft-ietf-nemo-ro-problem-statement-01 (work in progress), draft-ietf-nemo-ro-problem-statement-01 (work in progress),
October 2005. October 2005.
[8] Abley, J., Black, B., and V. Gill, "Goals for IPv6 Site- [9] Ng, C., Fan, F., Masafumi, M., and P. Pascal, "Network Mobility
Route Optimization Solution Space Analysis",
draft-ietf-nemo-ro-space-analysis-01 (work in progress),
October 2005.
11.2. Informative References
[10] Abley, J., Black, B., and V. Gill, "Goals for IPv6 Site-
Multihoming Architectures", RFC 3582, August 2003. Multihoming Architectures", RFC 3582, August 2003.
[9] Ng, C., Ernst, T., Paik, E., and M. Bagnulo, "Analysis of [11] Ernst, T., "Network Mobility Support in IPv6", PhD's Thesis. ,
Multihoming in Network Mobility Support", Universite Joseph Fourier, Grenoble, France , October 2001.
draft-ietf-nemo-multihoming-issues-04 (work in progress),
October 2005.
Appendix A. Change Log From Earlier Versions Appendix A. Change Log From Earlier Versions
The discussions behind the changes in the lattest versions of this The discussions behind the changes in the lattest versions of this
documents are reflected in the "issue" web page: documents are reflected in the "issue" web page:
http://www.sfc.wide.ad.jp/~ernst/nemo/ http://www.sfc.wide.ad.jp/~ernst/nemo/
A.1. Changes since draft-nemo-terminology-03.txt A.1. Changes since draft-nemo-terminology-04.txt
In Section 3, added in the introduction a note about NEMO-enabled and
MIP6-enabled (part of this text was in the definition of NEMO-
enabled):
Removed Abbreviation "i-face" and "e-face"
Replaced "HA" with "home link located outside the mobile network" in
the definition of VMN
Replaced "address located within a MNP" with "address taken from a
MNP" [or derived is better ?] in the definitions of LFN and LMN
Replaced term NEMO-Link with Mobile Subnet
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 a LMN changing its
point of attachment within the mobile network.
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. On the other hand, a VMN or a LMN acting as a mobile
router may be NEMO-enabled whereas a VMN or a LMN acting as a
mobile node may be MIPv6-enabled.
For NEMO Extended Support, details of the capabilities are not
known yet at the time of this writing, but NEMO-enabled nodes may
be expected to implement some sort of Route Optimization.
Removed this note from the definition of "root-MR": "note: this term
was referred to as Top-Level Mobile Router, or TLMR in short in
former versions of this document).".
Added term "Depth"
Removed "IPv6" in front of "address" in the definition of a
multihomed host and a multihomed mobile router
Removed "or multiple prefixes are advertised in the mobile network"
from the definition of a multihomed NEMO (5.3) and nested multihomed
NEMO (5.4)
Added definition for "Routing Optimization" (see Section 7.5).
Added definition "Pinball Route" following the discussion on the ML
in Dec.05
Added reference to [11] in the ACK section
A.2. Changes since draft-nemo-terminology-03.txt
Updated the Home Network Model section with new definitions provided Updated the Home Network Model section with new definitions provided
by Vijay by Vijay
Added definitions of CR and CE as suggested by the RO PB Statement Added definitions of CR and CE as suggested by the RO PB Statement
and Analysis authors [7] and Analysis authors [8]
A.2. Changes since draft-nemo-terminology-02.txt Completed figure improvement
A.3. Changes since draft-nemo-terminology-02.txt
- Issue A18: Redesigned Figure 3 - Issue A18: Redesigned Figure 3
- Issue A22: The follolwing comment added in the definition of - Issue A22: The follolwing comment added in the definition of
"Mobile Network": "Re-arrangement of the mobile network and changing "Mobile Network": "Re-arrangement of the mobile network and changing
the attachment point of the egress interface to the foreign link are the attachment point of the egress interface to the foreign link are
orthogonal processes and do no affect each other." (as suggested by orthogonal processes and do no affect each other." (as suggested by
TJ) TJ)
- Issue A23: Clarified in definition of "NEMO-link" that the link may - Issue A23: Clarified in definition of "NEMO-link" that the link may
comprise the mobile network: "A link (subnet) which comprises, or is comprise the mobile network: "A link (subnet) which comprises, or is
located within, the mobile network." (as suggested by TJ) located within, the mobile network." (as suggested by TJ)
- Issue A24: Removed definition of CR (as suggested by TJ) - Issue A24: Removed definition of CR (as suggested by TJ)
- Issue A25: Removed the miscellaneous terms "Idle MNN" and "Idle - Issue A25: Removed the miscellaneous terms "Idle MNN" and "Idle
mobile network" (as suggested by TJ) mobile network" (as suggested by TJ)
- Issue A26: English brush up. - Issue A26: English brush up.
A.3. Changes since draft-nemo-terminology-01.txt A.4. Changes since draft-nemo-terminology-01.txt
- Shorten abstract. - Shorten abstract.
- Reshaped some figures. - Reshaped some figures.
- LFN, VMN, LMN: said that the node is able/unable to move while - LFN, VMN, LMN: said that the node is able/unable to move while
maintaining/not maintaining ongoing sessions. Text already maintaining/not maintaining ongoing sessions. Text already
appareared in the document, but not in the definition itself. appareared in the document, but not in the definition itself.
- NEMO-enabled: said that MR and HA are the only NEMO-enabled nodes - NEMO-enabled: said that MR and HA are the only NEMO-enabled nodes
skipping to change at page 25, line 28 skipping to change at page 27, line 33
- Updated References - Updated References
- Added new term "Correspondent Router" - Added new term "Correspondent Router"
- Permanently removed NEMO-Prefix. Only MNP will be used - Permanently removed NEMO-Prefix. Only MNP will be used
- Added terms "Mobile Home Network" and "Distributed Home Network" in - Added terms "Mobile Home Network" and "Distributed Home Network" in
the Home Network Model section. These 2 terms were provided by the Home Network Model section. These 2 terms were provided by
Pascal Thubert on July 30th 2004 Pascal Thubert on July 30th 2004
A.4. Changes since draft-nemo-terminology-00.txt A.5. Changes since draft-nemo-terminology-00.txt
- NEMO will be used either as the concept for NEtwork MObility and a - NEMO will be used either as the concept for NEtwork MObility and a
noun meaning "NEtwork that is MObile" noun meaning "NEtwork that is MObile"
- Deprecated TMLR and MONET. - Deprecated TLMR and MONET.
- Added NEMO-prefix, NEMO-link, NEMO-enabled MR. - Added NEMO-prefix, NEMO-link, NEMO-enabled MR.
- Precision that IP address of LFN, LMN, or VMN is taken from a MNP - Precision that IP address of LFN, LMN, or VMN is taken from a MNP
- Added abbreviation E-face (Egress interface) and I-face (Ingress - Added abbreviation E-face (Egress interface) and I-face (Ingress
interface) interface)
- Some re-ordering of terms, and a few typos. - Some re-ordering of terms, and a few typos.
skipping to change at page 27, line 41 skipping to change at page 29, line 41
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 AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 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.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 66 change blocks. 
169 lines changed or deleted 276 lines changed or added

This html diff was produced by rfcdiff 1.29, available from http://www.levkowetz.com/ietf/tools/rfcdiff/