draft-ietf-nemo-terminology-02.txt   draft-ietf-nemo-terminology-03.txt 
NEMO Working Group T. Ernst
Internet-Draft WIDE at Keio University
Expires: April 25, 2005 H-Y. Lach
Motorola Labs
October 25, 2004
Network Mobility Support Terminology
draft-ietf-nemo-terminology-02
Abstract
This document defines a terminology for discussing network mobility
issues and solution requirements.
NEMO Working Group T. Ernst NEMO Working Group T. Ernst
Internet-Draft WIDE at Keio University Internet-Draft WIDE at Keio University
Expires: April 25, 2005 H-Y. Lach Expires: August 25, 2005 H-Y. Lach
Motorola Labs Motorola Labs
October 25, 2004 February 21, 2005
Network Mobility Support Terminology Network Mobility Support Terminology
draft-ietf-nemo-terminology-02 draft-ietf-nemo-terminology-03
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions This document is an Internet-Draft and is subject to all provisions
of section 3 of RFC 3667. By submitting this Internet-Draft, each of Section 3 of RFC 3667. By submitting this Internet-Draft, each
author represents that any applicable patent or other IPR claims of author represents that any applicable patent or other IPR claims of
which he or she is aware have been or will be disclosed, and any of which he or she is aware have been or will be disclosed, and any of
which he or she become aware will be disclosed, in accordance with which he or she become aware will be disclosed, in accordance with
RFC 3668. RFC 3668.
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
other groups may also distribute working documents as other groups may also distribute working documents as
Internet-Drafts. Internet-Drafts.
skipping to change at page 1, line 50 skipping to change at page 1, line 37
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 25, 2005. This Internet-Draft will expire on August 25, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). Copyright (C) The Internet Society (2005).
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. Architecture Components . . . . . . . . . . . . . . . . . . . 4 2. Architectural Components . . . . . . . . . . . . . . . . . . . 4
2.1 Mobile Network (NEMO) . . . . . . . . . . . . . . . . . . 6 2.1 Mobile Network (NEMO) . . . . . . . . . . . . . . . . . . 6
2.2 Mobile Router (MR) . . . . . . . . . . . . . . . . . . . . 6 2.2 Mobile Router (MR) . . . . . . . . . . . . . . . . . . . . 6
2.3 Egress Interface (E-face) . . . . . . . . . . . . . . . . 7 2.3 Egress Interface (E-face) . . . . . . . . . . . . . . . . 7
2.4 Ingress Interface (I-face) . . . . . . . . . . . . . . . . 7 2.4 Ingress Interface (I-face) . . . . . . . . . . . . . . . . 7
2.5 Mobile Network Prefix (MNP) . . . . . . . . . . . . . . . 7 2.5 Mobile Network Prefix (MNP) . . . . . . . . . . . . . . . 7
2.6 NEMO-link . . . . . . . . . . . . . . . . . . . . . . . . 7 2.6 NEMO-link . . . . . . . . . . . . . . . . . . . . . . . . 7
2.7 Mobile Network Node (MNN) . . . . . . . . . . . . . . . . 7 2.7 Mobile Network Node (MNN) . . . . . . . . . . . . . . . . 7
2.8 Correspondent Node (CN) . . . . . . . . . . . . . . . . . 7 2.8 Correspondent Node (CN) . . . . . . . . . . . . . . . . . 7
3. Functional Terms . . . . . . . . . . . . . . . . . . . . . . . 8 3. Functional Terms . . . . . . . . . . . . . . . . . . . . . . . 8
3.1 Local Fixed Node (LFN) . . . . . . . . . . . . . . . . . . 8 3.1 Local Fixed Node (LFN) . . . . . . . . . . . . . . . . . . 8
3.2 Visiting Mobile Node (VMN) . . . . . . . . . . . . . . . . 9 3.2 Visiting Mobile Node (VMN) . . . . . . . . . . . . . . . . 8
3.3 Local Mobile Node (LMN) . . . . . . . . . . . . . . . . . 9 3.3 Local Mobile Node (LMN) . . . . . . . . . . . . . . . . . 9
3.4 NEMO-enabled node (NEMO-node) . . . . . . . . . . . . . . 9 3.4 NEMO-enabled node (NEMO-node) . . . . . . . . . . . . . . 9
3.5 MIPv6-enabled (MIPv6-node) . . . . . . . . . . . . . . . . 10 3.5 MIPv6-enabled (MIPv6-node) . . . . . . . . . . . . . . . . 10
3.6 Correspondent Router (CR) . . . . . . . . . . . . . . . . 10
4. Nested Mobility Terms . . . . . . . . . . . . . . . . . . . . 10 4. Nested Mobility Terms . . . . . . . . . . . . . . . . . . . . 10
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 . . . . . . . . . . . . . . . . . . . . . . . . 11 4.6 parent-MR . . . . . . . . . . . . . . . . . . . . . . . . 11
4.7 sub-MR . . . . . . . . . . . . . . . . . . . . . . . . . . 12 4.7 sub-MR . . . . . . . . . . . . . . . . . . . . . . . . . . 11
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 . . . . . . . . . . . . . . . . . . . . . . . 15 5.5 Illustration . . . . . . . . . . . . . . . . . . . . . . . 14
6. Home Network Model Terms . . . . . . . . . . . . . . . . . . . 16 6. Home Network Model Terms . . . . . . . . . . . . . . . . . . . 16
6.1 Home Link . . . . . . . . . . . . . . . . . . . . . . . . 16 6.1 Home Link . . . . . . . . . . . . . . . . . . . . . . . . 16
6.2 Home Network . . . . . . . . . . . . . . . . . . . . . . . 17 6.2 Home Network . . . . . . . . . . . . . . . . . . . . . . . 16
6.3 Home Address . . . . . . . . . . . . . . . . . . . . . . . 17 6.3 Home Address . . . . . . . . . . . . . . . . . . . . . . . 16
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 . . . . . . . . . . . . . . . . . . 17 6.8 Extended Home Network . . . . . . . . . . . . . . . . . . 17
6.9 Virtual Home Network . . . . . . . . . . . . . . . . . . . 17 6.9 Virtual Home Network . . . . . . . . . . . . . . . . . . . 17
7. Mobility Support Terms . . . . . . . . . . . . . . . . . . . . 18 7. Mobility Support Terms . . . . . . . . . . . . . . . . . . . . 17
7.1 Host Mobility Support . . . . . . . . . . . . . . . . . . 18 7.1 Host Mobility Support . . . . . . . . . . . . . . . . . . 17
7.2 Network Mobility Support (NEMO Support) . . . . . . . . . 18 7.2 Network Mobility Support (NEMO Support) . . . . . . . . . 18
7.3 NEMO Basic Support . . . . . . . . . . . . . . . . . . . . 18 7.3 NEMO Basic Support . . . . . . . . . . . . . . . . . . . . 18
7.4 NEMO Extended Support . . . . . . . . . . . . . . . . . . 18 7.4 NEMO Extended Support . . . . . . . . . . . . . . . . . . 18
7.5 MRHA Tunnel . . . . . . . . . . . . . . . . . . . . . . . 18 7.5 MRHA Tunnel . . . . . . . . . . . . . . . . . . . . . . . 18
8. Miscellaneous Terms . . . . . . . . . . . . . . . . . . . . . 18 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 18
8.1 Idle MNN . . . . . . . . . . . . . . . . . . . . . . . . . 18
8.2 Idle Mobile Network . . . . . . . . . . . . . . . . . . . 18
9. Changes since draft-nemo-terminology-01.txt . . . . . . . . . 19
10. Changes since draft-nemo-terminology-00.txt . . . . . . . . 19
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 20 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 21 A. Change Log From Earlier Versions . . . . . . . . . . . . . . . 20
A.1 Changes since draft-nemo-terminology-02.txt . . . . . . . 20
A.2 Changes since draft-nemo-terminology-01.txt . . . . . . . 20
A.3 Changes since draft-nemo-terminology-00.txt . . . . . . . 21
Intellectual Property and Copyright Statements . . . . . . . . 22 Intellectual Property and Copyright Statements . . . . . . . . 22
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 an entire an entire network. This arises when a router connecting a network to
network to the Internet dynamically changes its point of attachment the Internet dynamically changes its point of attachment to the fixed
to the Internet therefrom causing the reachability of the entire infrastructure, thereby causing the reachability of the entire
network to be changed in the topology. Such network is referred to network to be changed in relation to the fixed Internet topology.
as a mobile network. Without appropriate mechanisms to support Such a network is referred to as a mobile network. Without
network mobility, sessions established between nodes in the mobile appropriate mechanisms to support network mobility, sessions
network and the global Internet cannot be maintained while the mobile established between nodes in the mobile network and the global
router changes its point of attachment. As a result, existing Internet cannot be maintained after the mobile router changes its
sessions would break and connectivity to the global Internet would be point of attachment. As a result, existing sessions would break and
lost. connectivity to the global Internet would be lost.
This document defines the specific terminology needed to describe the This document defines the specific terminology needed to describe the
problem space, the design goals [4], and the solutions for network problem space, the design goals [4], and the solutions for network
mobility support. This terminology complies with the usual IPv6 mobility support. This terminology aims to be consistent with the
terminology [7] and the generic mobility-related terms already usual IPv6 terminology [7] and the generic mobility-related terms
defined in [3] and in the Mobile IPv6 [1] specifications. Some terms already defined in the Mobility Related Terminology [1] and in the
introduced in the present version of the draft may only be useful for Mobile IPv6 specification [2]. Some terms introduced in this
the purpose of defining the problem scope and functional requirements document may only be useful for defining the problem scope and
of network mobility support. functional requirements of network mobility support.
Note that the abbreviation NEMO stands either for "a NEtwork that is Note that the abbreviation NEMO stands for either "a NEtwork that is
MObile" and for "NEtwork MObility". The former (see Section 2.1 is MObile" or "NEtwork MObility". The former (see Section 2.1) is used
used as a noun, e.g. "a NEMO" meaning "a mobile network". The as a noun, e.g. "a NEMO" meaning "a mobile network". The latter
latter (see Section 7 refers to the concept of "network mobility" as (see Section 7) refers to the concept of "network mobility" as in
in "NEMO Basic Support" and is also the working group's name. "NEMO Basic Support" and is also the working group's name.
Section 2 introduces terms to define the architecture while terms Section 2 introduces terms to define the architecture while terms
needed to emphasize the distinct functionalities of those needed to emphasize the distinct functionalities of those
architecture components are described in Section 3. Section 4, architectural components are described in Section 3. Section 4,
Section 5 and Section 6 respectively describe terms pertaining to Section 5 and Section 6 describe terms pertaining to nested mobility,
nested mobility, multihoming and those necessary to describe the multihoming and different configurations of mobile networks at home,
different configurations of mobile networks at home. The different respectively. The different types of mobility are defined in
types of mobility are defined in Section 7. The last section lists Section 7. The last section lists miscellaneous terms which do not
miscellaneous terms which do not fit in either sections. fit in any other section.
2. Architecture Components 2. Architectural Components
A mobile network is composed by one or more mobile IP-subnet A mobile network is composed of one or more mobile IP-subnets
(NEMO-link) and is viewed as a single unit. The unit is connected to (NEMO-link) and is viewed as a single unit. This network unit is
the Internet by means of mobile routers (MRs). Nodes behind the MR connected to the Internet by means of one or more mobile routers
(MNNs) primarily comprise fixed nodes (nodes unable to change their (MRs). Nodes behind the MR (referred to as MNNs) primarily comprise
point of attachment while maintaining ongoing sessions), and fixed nodes (nodes unable to change their point of attachment while
additionally mobile nodes (nodes able to change their point of maintaining ongoing sessions), and possibly mobile nodes (nodes able
attachment while maintaining ongoing sessions). In most cases, the to change their point of attachment while maintaining ongoing
internal structure of the mobile network will in effect be relatively sessions). In most cases, the internal structure of the mobile
stable (no dynamic change of the topology), but this is not a general network will be stable (no dynamic change of the topology), but this
assumption. is not always true.
Figure 1 illustrates the architecture components involved in network Figure 1 illustrates the architectural components involved in network
mobility and defined in the below paragraphs: Mobile Router (MR), mobility and defined in the following paragraphs: Mobile Router (MR),
NEMO-link, Mobile Network Node (MNN), "ingress interface", "egress NEMO-link, Mobile Network Node (MNN), "ingress interface", "egress
interface", and Correspondent Nodes (CNs). The other terms "access interface", and Correspondent Node (CN). The other terms "access
router" (AR), "Fixed Node (FN)", "Mobile Node (MN)", "home agent" router" (AR), "Fixed Node (FN)", "Mobile Node (MN)", "home agent"
(HA), "home link" and "foreign link" are not terms specific to (HA), "home link" and "foreign link" are not terms specific to
network mobility and are thus defined in [3]. network mobility and thus are defined in [1].
_ _
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 subnetwork. Figure 3 illustrates a
larger mobile network comprising several subnetworks, attached on a larger mobile network comprising several subnetworks, attached to a
foreign link. foreign link.
_ _
CN ->|_|-| CN ->|_|-|
| _____ | _____
_ | |-| | |<- home link _ | |-| | |<- home link
|_|-| _ | _ | |-| _ | _ |_|-| _ | _ | |-| _ | _
2 MNNs -> _ |-|_|-|-|_|-|_____| |-|_|-|-|_|<- HA 2 MNNs -> _ |-|_|-|-|_|-|_____| |-|_|-|-|_|<- HA
|_|-| . | . | |_|-| . | . |
| . |<- foreign . | . |<- foreign .
single NEMO-link -> . link ^ AR single NEMO-link -> . link ^ AR
. .
^ MR ^ MR
Figure 2: Single Mobile Subnetwork on a Foreign Link Figure 2: Single Mobile Subnetwork on a Foreign Link
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 Routers (ARs) on the visited link. The MRs maintain 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(s) and one or more ingress interface(s). one or more egress interface and one or more ingress interface. When
When forwarding a packet to the Internet the packet is transmitted forwarding a packet to the Internet, the packet is transmitted
upstream through one of the MR's egress interfaces to the AR; when upstream through one of the MR's egress interfaces to the AR; when
forwarding a packet from the AR down to the mobile network, the forwarding a packet from the AR down to the mobile network, the
packet is transmitted downstream through one of the MR's ingress packet is transmitted downstream through one of the MR's ingress
interfaces. interfaces.
2.1 Mobile Network (NEMO) 2.1 Mobile Network (NEMO)
As defined in [3]: As defined in [1]:
An entire network, moving as a unit, which dynamically changes its An entire network, moving as a unit, which dynamically changes its
point of attachment to the Internet and thus its reachability in the point of attachment to the Internet and thus its reachability in the
topology. The mobile network is composed of one or more IP-subnets topology. The mobile network is composed of one or more IP-subnets
and is connected to the global Internet via one or more Mobile and is connected to the global Internet via one or more Mobile
Routers (MR). The internal configuration of the mobile network is Routers (MR). The internal configuration of the mobile network is
assumed to be relatively stable with respect to the MR. assumed to be relatively stable with respect to the MR.
Re-arrangement of the mobile network and changing the attachment
point of the egress interface to the foreign link are orthogonal
processes and do no affect each other.
2.2 Mobile Router (MR) 2.2 Mobile Router (MR)
As defined in [3]: As defined in [1]:
A router capable of changing its point of attachment to the network, 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.
A MR acting as a gateway between an entire mobile network and the An MR acts as a gateway between an entire mobile network and the rest
rest of the Internet has one or more egress interface(s) and one or of the Internet, and has one or more egress interface and one or more
more ingress interface(s). Packets forwarded upstream to the rest of ingress interface. Packets forwarded upstream to the rest of the
the Internet are transmitted through one of the MR's egress Internet are transmitted through one of the MR's egress interfaces;
interface; packets forwarded downstream to the mobile network are packets forwarded downstream to the mobile network are transmitted
transmitted through one of the MR's ingress interface. through one of the MR's ingress interfaces.
2.3 Egress Interface (E-face) 2.3 Egress Interface (E-face)
As defined in [3]: As defined in [1]:
The interface of a MR attached to the home link if the MR is at home, The network interface of an MR attached to the home link if the MR is
or attached to a foreign link if the MR is in a foreign network. at home, or attached to a foreign link if the MR is in a foreign
network.
2.4 Ingress Interface (I-face) 2.4 Ingress Interface (I-face)
As defined in [3]: As defined in [1]:
The interface of a 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.5 Mobile Network Prefix (MNP)
As defined in [3]: As defined in [1]:
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.
MNP is an acronym for Mobile Network Prefix.
2.6 NEMO-link 2.6 NEMO-link
A link (subnet) located within the mobile network. 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 [1]:
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 a mobile network, and either located within a fixed network or within another mobile
could be either fixed or mobile. network, and could be either fixed or mobile.
3. Functional Terms 3. Functional Terms
________________________ _
| | CN->|_|-|
| | NEMO-link 1->| | _____
| Internet | _ | |-| | |<- home link
| | MNN1->|_|-|'i'_'e'| _ | |-| _ | _
|________________________| |--|_|--|-|_|-|_____| |-|_|-|-|_|<- HA
__|_ 'i'| | |
Access | | NEMO-link 2->____|__ |
Router | AR | _| . |<- foreign
|____| MNN2> |_| . link
foreign _____|_____________ .
link | ^
| 'e' MR
__|__
| 'i'| | 'i': MR's ingress interface 'e': MR's egress interface
|____| MR | Mobile Router
| |_____|
| |'i'
| |
| ____|________________ NEMO-link 1
| __|__ __|__
_____ | | | | |
| |__| | MNN | | MNN |
| MNN | | |_____| |_____|
|_____| |
| NEMO-link 2 'i': MR's ingress interface
'e': MR's egress interface
Figure 3: Larger Mobile Network with 2 subnets 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 Node (LFN), Visiting Mobile Node (VMN) and Local Mobile Local Fixed Nodes (LFN), Visiting Mobile Nodes (VMN) and Local Mobile
Node (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, but does not imply related to mobility management and access control; however it does
that network mobility or host mobility should be handled differently. not imply that network mobility or host mobility should be handled
Nodes are classified according to their function and capabilities differently. Nodes are classified according to their function and
with the rationale that nodes with different properties (may) have capabilities with the rationale that nodes with different properties
different requirements. may have different requirements.
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 which is unable to change its point of attachment mobile network and is unable to change its point of attachment while
while maintaining ongoing sessions. Its address is taken from a MNP. maintaining ongoing sessions. Its address is located within an MNP.
3.2 Visiting Mobile Node (VMN) 3.2 Visiting Mobile Node (VMN)
A mobile node (MN), either a host or a router whose home link doesn't Either a mobile node (MN) or a mobile router (MR), assigned to a home
belong to the mobile network and which is able to change its point of link that doesn't belong to the mobile network and which is able to
attachment while maintaining ongoing sessions. A VMN that gets change its point of attachment while maintaining ongoing sessions. A
temporarily attached to a NEMO-link (used as a foreign link) obtains VMN that is temporarily attached to a NEMO-link (used as a foreign
an address on that link (i.e. the address is taken from a MNP). link) obtains an address on that link (i.e. the address is taken
from an MNP).
3.3 Local Mobile Node (LMN) 3.3 Local Mobile Node (LMN)
A mobile node (MN), either a host or a router whose home link belongs Either a mobile node (MN) or a mobile router (MR), assigned to a home
to the mobile network and which is able to change its point of link belonging to the mobile network and which is able to change its
attachment while maintaining ongoing sessions. Its address is taken point of attachment while maintaining ongoing sessions. Its address
from a MNP. Figure 4 illustrates a LMN changing its point of is taken from an MNP. Figure 4 illustrates a LMN changing its point
attachment within the mobile network. 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 and that may take special actions based on that. capabilities as described in NEMO specifications.
In NEMO Basic Support, only the MR and the HA are NEMO-enabled. In NEMO Basic Support [3], only the MR and the HA are NEMO-enabled.
In NEMO Extended Support, details of the capabilities are not known For NEMO Extended Support, details of the capabilities are not known
yet, but NEMO-enabled nodes may be implementing some sort of Route yet at the time of this writing, but NEMO-enabled nodes may be
Optimization. expected to implement some sort of Route Optimization.
________________________ ________________________
| | | |
| | | |
| Internet | | Internet |
| | | |
|________________________| |________________________|
__|_ __|_ __|_ __|_
| | Access | | | | Access | |
| AR | Router | AR | | AR | Router | AR |
skipping to change at page 10, line 35 skipping to change at page 10, line 35
| |_____| | | | |_____| | |
| | NEMO-link 2 | | | NEMO-link 2 |
| | | |
|------------------------------| |------------------------------|
Figure 4: LFN versus LMN Figure 4: LFN versus LMN
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 Mobile IPv6 in [1] and that may take special capabilities as defined in the Mobile IPv6 specification [2].
actions based on that.
3.6 Correspondent Router (CR)
A router topologically close to the CN that has been extented with
some mobility support capabilities and that may take special actions
based on that. Details of the capabilities do not matter in the
present documents. The CR is said NEMO-enabled if such capabilities
are defined for network mobility support.
4. Nested Mobility Terms 4. Nested Mobility Terms
Nested mobility occurs when there are more than one level of Nested mobility occurs when there is more than one level of mobility,
mobility, i.e. when a mobile networks acts as an access network and i.e. when a mobile network acts as an access network and allows
allows visiting nodes to get attached to it. There are two cases of visiting nodes to attach to it. There are two cases of nested
nested mobility: mobility:
o when the attaching node is a single VMN (see figure 4). For o The attaching node is a single VMN (see figure 4). For instance,
instance, when a passenger carrying a mobile phone gets Internet when a passenger carrying a mobile phone gets Internet access from
access from the public access network deployed into a bus. the public access network deployed on a bus.
o when the attaching node is a MR with nodes behind it, i.e. a o The attaching node is a MR with nodes behind it, i.e. a mobile
mobile network (see figure 5). For instance, when a passenger network (see figure 5). For instance, when a passenger carrying a
carrying a PAN gets Internet access from the public access network PAN gets Internet access from the public access network deployed
deployed in the bus. on a bus.
For the second case, we introduce the following terms: For the second case, we introduce the following terms:
4.1 Nested Mobile Network (nested-NEMO) 4.1 Nested Mobile Network (nested-NEMO)
A mobile network is said to be nested when a mobile network A mobile network is said to be nested when a mobile network
(sub-NEMO) is getting attached to a larger mobile network (sub-NEMO) is attached to a larger mobile network (parent-NEMO). The
(parent-NEMO). The aggregated hierarchy of mobile networks becomes a aggregated hierarchy of mobile networks becomes a single nested
single nested mobile network. mobile network.
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 network to the Internet. aggregated nested mobile networks to the Internet.
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 down the hierarchy. mobile network further down the hierarchy.
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
the hierarchy. It becomes a 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. not provide Internet access to the parent-NEMO.
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. Was referred to as "TMLR" (Top-Level Mobile to the fixed Internet. Was referred to as "TMLR" (Top-Level Mobile
Router) in former versions of this document. 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 connected to a parent-NEMO The MR(s) of the sub-NEMO which is connected to a parent-NEMO
________________________ ________________________
| | | |
| | | |
| Internet | | Internet |
| | | |
|________________________| |________________________|
__|_ __|_ __|_ __|_
| | Access | | | | Access | |
| AR | Router | AR | | AR | Router | AR |
|____| |____| |____| |____|
skipping to change at page 12, line 32 skipping to change at page 12, line 27
| _____ |__| MR | Mobile Router | _____ |__| MR | Mobile Router
| | |__| |____| | | |__| |____|
----------> | VMN | | __|_____________ NEMO-link 1 ----------> | VMN | | __|_____________ NEMO-link 1
|_____| | __|__ __|__ |_____| | __|__ __|__
_____ | | | | | _____ | | | | |
| |__| | LFN | | LMN | | |__| | LFN | | LMN |
| LFN | | |_____| |_____| | LFN | | |_____| |_____|
|_____| | |_____| |
| NEMO-link 2 | NEMO-link 2
Figure 5: Nested Mobility: single VMN attached to a mobile network Figure 5: Nested Mobility: a single VMN attached to a mobile network
_____ _____
_ | | _ | |
_ |--|_|-| |-| _ _ |--|_|-| |-| _
_ |--|_|--| |_____| | _ |-|_| _ |--|_|--| |_____| | _ |-|_|
_ |--|_|--| | |-|_|-| _ |--|_|--| | |-|_|-|
|_|-| | | |_|-| | |
| |
MNN sub-MR root-MR AR AR HA MNN sub-MR root-MR AR AR HA
<--------><------><-------><------><------------> <--------><------><-------><------><------------>
sub-NEMO root-NEMO fl Internet Home Network sub-NEMO root-NEMO fl Internet Home Network
Figure 6: Nested Mobility: sub-NEMO attached to a larger mobile Figure 6: 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 Multihoming, as currently defined by the IETF, covers
site-multihoming [8] and host multihoming. We enlarge this site-multihoming [8] and host multihoming. We enlarge this
terminology to include "multihomed mobile router" and "multihomed terminology to include "multihomed mobile router" and "multihomed
mobile network". The specific configurations and issues pertaining mobile network". The specific configurations and issues pertaining
to multihomed mobile networks are coverd in [5]. to multihomed mobile networks are covered in [5].
5.1 Multihomed host or MNN 5.1 Multihomed host or MNN
A host (e.g. a MNN) is multihomed when it has several IPv6 addresses A host (e.g. an MNN) is multihomed when it has several IPv6
to choose between, i.e. in the following cases when it is either: addresses to 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 router is From the definition of a multihomed host, it follows that a mobile
multihomed when it has several IPv6 addresses to choose between, i.e. router is multihomed when it has several IPv6 addresses to choose
in the following cases when the MR is either: between, i.e. in the following cases when the MR is either:
multi-prefixed: multiple prefixes are advertised on the link(s) a 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. between, on the same link or not.
_____ _____
_ _ | | _ _ | |
|_|-| _ |-|_|-| |-| _ |_|-| _ |-|_|-| |-| _
_ |-|_|=| |_____| | _ |-|_| _ |-|_|=| |_____| | _ |-|_|
|_|-| | |-|_|-| |_|-| | |-|_|-|
| |
MNNs MR AR Internet AR HA MNNs MR AR Internet AR HA
skipping to change at page 15, line 15 skipping to change at page 14, line 39
5.5 Illustration 5.5 Illustration
Figure 7 and Figure 8 show two examples of multihomed mobile Figure 7 and Figure 8 show two examples of multihomed mobile
networks. Figure 9 shows two independent mobile networks. NEMO-1 is networks. Figure 9 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 9: Let's consider the two following nested scenarios in Figure 9:
Scenario 1: what happens when MR2a's egress interfaced is attached to Scenario 1: What happens when MR2a's egress interface is attached to
AR1 ? AR1 ?
* NEMO-2 becomes a subservient of NEMO-1 * NEMO-2 becomes subservient of NEMO-1
* NEMO-1 becomes the parent-NEMO for NEMO-2 and the root-NEMO for * NEMO-1 becomes the parent-NEMO for NEMO-2 and the root-NEMO for
the aggregated nested mobile network the aggregated nested mobile network
* NEMO-2 becomes the sub-NEMO * NEMO-2 becomes the sub-NEMO
* MR1 is the root-MR for the aggregated nested mobile network * MR1 is the root-MR for the aggregated nested mobile network
* MR2a is a sub-MR in the aggregated nested mobile network * MR2a is a sub-MR in the aggregated nested mobile network
* NEMO-2 is still multihomed to the Internet through AR1 and ARz * NEMO-2 is still multihomed to the Internet through AR1 and ARz
* The aggregated nested mobile network is not multihomed since * The aggregated nested mobile network is not multihomed, since
NEMO-2 cannot be used as a transit network for NEMO-1 NEMO-2 cannot be used as a transit network for NEMO-1
Scenario 2: what happens when MR1's egress interface is attached to Scenario 2: What happens when MR1's egress interface is attached to
AR2 ? AR2 ?
* NEMO-1 becomes a subservient of NEMO-2 * NEMO-1 becomes subservient of NEMO-2
* NEMO-1 becomes the sub-NEMO * NEMO-1 becomes the sub-NEMO
* NEMO-2 becomes the parent_NEMO for NEMO-1 and also the * NEMO-2 becomes the parent_NEMO for NEMO-1 and also the
root-NEMO for the aggregated nested mobile network) root-NEMO for the aggregated nested mobile network
* MR2a and MR2b are both root-MRs for the aggregated nested * MR2a and MR2b are both root-MRs for the aggregated nested
mobile network mobile network
* MR1 is a sub-MR in the aggregated nested mobile network * MR1 is a sub-MR in the aggregated nested mobile network
* NEMO-1 is not multihomed * NEMO-1 is not multihomed
* The aggregated nested mobile network is multihomed * The aggregated nested mobile network is multihomed
_____________________________ _____________________________
| | | |
| | | |
| Internet | | Internet |
| | | |
|_____________________________| |_____________________________|
__|__ __|__ __|__ __|__ __|__ __|__
| | | | | | | | | | | |
| ARx | | ARy | | ARz | | ARx | | ARy | | ARz |
|_____| |_____| |_____| |_____| |_____| |_____|
skipping to change at page 16, line 34 skipping to change at page 16, line 30
__|__ __|__ __|__ __|__
| | | | | | | |
| LFN | AR1 | LFN | AR2 | LFN | AR1 | LFN | AR2
|_____| |_____| |_____| |_____|
Figure 9: Nested Multihomed Mobile Network Figure 9: Nested Multihomed Mobile Network
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 are home. The configurations are configurations of mobile networks at the home. Such configurations
illustrated in [6] are detailed in [6]
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 on the Home The Network formed by the application of the Home Prefix to the Home
Link. With Nemo, the concept of Home Network is extended as Link. With NEMO, the concept of Home Network is extended as
explained below. explained below.
6.3 Home Address 6.3 Home Address
With Mobile IPv6, a Home Address is derived from the Home Network With Mobile IPv6, a Home Address is derived from the Home Network
prefix. This is generalized in Nemo, with some limitations: A Home prefix. This is generalized in NEMO, with some limitations: A Home
Address can be either derived from the Home Network or from one of Address can be derived either from the Home Network or from one of
the Mobile Router's Mobile Network prefixes. the Mobile Router's MNPs.
6.4 Mobile Home Network 6.4 Mobile Home Network
A Mobile Network that also serves as a Home Network. The MR that A Mobile Network that also serves as a Home Network. The MR that
owns the MNP acts as a Home Agent for it. owns the MNP acts as a Home Agent for it.
6.5 Distributed Home Network 6.5 Distributed Home Network
A Distributed Home Network is advertised by several sites that are A Distributed Home Network is advertised by several sites that are
geographically distributed and meshed using tunnels in a VPN fashion. geographically distributed and meshed using tunnels in a VPN fashion.
6.6 Mobile Aggregated Prefix 6.6 Mobile Aggregated Prefix
An aggregation of Mobile Network Prefixes. An aggregation of Mobile Network Prefixes.
6..7 Aggregated Home Network 6.7 Aggregated Home Network
The Home Network associated with a Mobile Aggregated Prefix. This The Home Network associated with a Mobile Aggregated Prefix. This
Aggregation is advertised as a subnet on the Home Link, and thus used Aggregation is advertised as a subnet on the Home Link, and thus used
as Home Network for Nemo purposes. as Home Network for Nemo purposes.
6.8 Extended Home Network 6.8 Extended Home Network
The network associated with the aggregation of one or more Home The network associated with the aggregation of one or more Home
Network(s) and Mobile Network(s). As opposed to the Mobile IPv6 Home Network(s) and Mobile Network(s). As opposed to the Mobile IPv6 Home
Network that is a subnet, the extended Home Network is an aggregation Network that is a subnet, the extended Home Network is an aggregation
skipping to change at page 18, line 17 skipping to change at page 18, line 8
7.1 Host Mobility Support 7.1 Host Mobility Support
Host Mobility Support is a mechanism which maintains session Host Mobility Support is a mechanism which maintains session
continuity between mobile nodes and their correspondents upon the continuity between mobile nodes and their correspondents upon the
mobile host's change of point of attachment. It can be achieved mobile host's change of point of attachment. It can be achieved
using Mobile IPv6 or other mobility support mechanisms. using Mobile IPv6 or other mobility support mechanisms.
7.2 Network Mobility Support (NEMO Support) 7.2 Network Mobility Support (NEMO Support)
Network Mobility Support is a mechanism which maintains session Network Mobility Support is a mechanism which maintains session
continuity between mobile network nodes and their correspondent upon continuity between mobile network nodes and their correspondents upon
a mobile router's change of point of attachment. Solutions for this a mobile router's change of point of attachment. Solutions for this
problem are classified into NEMO Basic Support, and NEMO Extended problem are classified into NEMO Basic Support, and NEMO Extended
Support. Support.
7.3 NEMO Basic Support 7.3 NEMO Basic Support
NEMO Basic Support is a solution to preserve session continuity by NEMO Basic Support is a solution to preserve session continuity by
means of bidirectional tunneling between MRs and their HAs much like means of bi-directional tunneling between MRs and their HAs much like
what is done with [1] for mobile nodes when Routing Optimization is what is done with Mobile IPv6 [2] for mobile nodes when Routing
not used. Only the HA and the MR are NEMO-enabled. The solution for Optimization is not used. Only the HA and the MR are NEMO-enabled.
doing this is solely specified in [2]. The solution for doing this is solely specified in [3].
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 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.
8.. Miscellaneous Terms 8. Acknowledgments
8.1 Idle MNN The material presented in this document takes most of the text from
internet-drafts submitted to the former MobileIP WG and the MONET
BOF. 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, suggestion, and
direction, Alexandru Petrescu and Christophe Janneteau. We also
acknowledge input from Hesham Soliman, Mattias Petterson, Marcelo
Bagnulo, TJ Kniveton and numerous other people from the NEMO Working
Group. The Home Network Model section is contributed by Pascal
Thubert, Ryuji Wakikawa and Vijay Devaparalli.
A MNN that does not engage in any communication. 9. References
8.2 Idle Mobile Network [1] Manner, J. and M. Kojo, "Mobility Related Terminology",
RFC 3753, June 2004.
A mobile network that does not engage in any communication outside [2] Johnson, D., Perkins, C. and J. Arkko, "Mobility Support in
the network can be considered idle from the global Internet. This IPv6", RFC 3775, June 2004.
doesn't imply that MNNs are themselves idle. Internal traffic
between any two MNNs located in the same mobile network is not
concerned by this statement.
9. Changes since draft-nemo-terminology-01.txt [3] Devarapalli, V., Wakikawa, R., Petrescu, A. and P. Thubert,
"Network Mobility (NEMO) Basic Support Protocol", RFC 3963,
January 2005.
[4] Ernst, T., "Network Mobility Support Goals and Requirements",
Internet-Draft draft-ietf-nemo-requirements-04, February 2005.
[5] Ng, C., Paik, E. and T. Ernst, "Analysis of Multihoming in
Network Mobility Support",
Internet-Draft draft-ietf-nemo-multihoming-issues-02, February
2005.
[6] Thubert, P., Wakikawa, R. and V. Devarapalli, "NEMO Home Network
Models", Internet-Draft draft-ietf-nemo-home-network-models-01,
October 2004.
[7] Deering, S. and R. Hinden, "Internet Protocol Version 6 (IPv6)",
IETF RFC 2460, December 1998.
[8] Abley, J., Black, B. and V. Gill, "Goals for IPv6
Site-Multihoming Architectures", RFC 3582, August 2003.
Authors' Addresses
Thierry Ernst
WIDE at Keio University
Jun Murai Lab., Keio University.
K-square Town Campus, 1488-8 Ogura, Saiwa-Ku
Kawasaki, Kanagawa 212-0054
Japan
Phone: +81-44-580-1600
Fax: +81-44-580-1437
Email: ernst@sfc.wide.ad.jp
URI: http://www.sfc.wide.ad.jp/~ernst/
Hong-Yon Lach
Motorola Labs Paris
Espace Technologique - Saint Aubin
Gif-sur-Yvette Cedex, 91 193
France
Phone: +33-169-35-25-36
Fax:
Email: hong-yon.lach@motorola.com
URI:
Appendix A. Change Log From Earlier Versions
The discussions behind the changes in the lattest versions of this
documents are reflected in the "issue" web page:
http://www.sfc.wide.ad.jp/~ernst/nemo/
A.1 Changes since draft-nemo-terminology-02.txt
- Issue A18: Redesigned Figure 3
- Issue A22: The follolwing comment added in the definition of
"Mobile Network": "Re-arrangement 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." (as suggested by
TJ)
- Issue A23: Clarified in definition of "NEMO-link" that the link may
comprise the mobile network: "A link (subnet) which comprises, or is
located within, the mobile network." (as suggested by TJ)
- Issue A24: Removed definition of CR (as suggested by TJ)
- Issue A25: Removed the miscellaneous terms "Idle MNN" and "Idle
mobile network" (as suggested by TJ)
- Issue A26: English brush up.
A.2 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 19, line 42 skipping to change at page 21, line 21
- 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
10. Changes since draft-nemo-terminology-00.txt A.3 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 TMLR 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.
- Added some text from the usage draft-thubert-usages (now home - Added some text from the usage draft-thubert-usages (now home
network model draft-ietf-nemo-home-network-models) network model draft-ietf-nemo-home-network-models)
11. Acknowledgments
The material presented in this document takes most of the text from
former internet-drafts submitted to the former MobileIP WG and the
MONET BOF. 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 advices, suggestions,
and direction, Alexandru Petrescu and Christophe Janneteau. We also
acknowledge input from Hesham Soliman, Mattias Petterson, Marcelo
Bagnulo and numerous other people from the NEMO Working Group. The
Home Network Model section is contributed by Pascal Thubert, Ryuji
Wakikawa and Vijay Devaparalli.
12 References
[1] Johnson, D., Perkins, C. and J. Arkko, "Mobility Support in
IPv6", RFC 3775, June 2004.
[2] Devarapalli, V., "Network Mobility (NEMO) Basic Support
Protocol", draft-ietf-nemo-basic-support-03 (work in progress),
June 2004.
[3] Manner, J. and M. Kojo, "Mobility Related Terminology", RFC
3753, June 2004.
[4] Ernst, T., "Network Mobility Support Goals and Requirements",
draft-ietf-nemo-requirements-03 (work in progress), October
2004.
[5] Ng, C-W., Paik, E-K. and T. Ernst, "Analysis of Multihoming in
Network Mobility Support", draft-ietf-nemo-multihoming-issues-01
(work in progress), October 2004.
[6] Thubert, P., Wakikawa, R. and V. Devarapalli, "NEMO Home Network
Models", draft-ietf-nemo-home-network-models-01 (work in
progress), October 2004.
[7] Deering, S. and R. Hinden, "Internet Protocol Version 6 (IPv6)",
IETF RFC 2460, December 1998.
[8] Abley, J., Black, B. and V. Gill, "Goals for IPv6
Site-Multihoming Architectures", RFC 3582, August 2003.
Authors' Addresses
Thierry Ernst
WIDE at Keio University
Jun Murai Lab., Keio University.
K-square Town Campus, 1488-8 Ogura, Saiwa-Ku
Kawasaki, Kanagawa 212-0054
Japan
Phone: +81-44-580-1600
Fax: +81-44-580-1437
EMail: ernst@sfc.wide.ad.jp
URI: http://www.sfc.wide.ad.jp/~ernst/
Hong-Yon Lach
Motorola Labs Paris
Espace Technologique - Saint Aubin
Gif-sur-Yvette Cedex, 91 193
France
Phone: +33-169-35-25-36
Fax:
EMail: hong-yon.lach@motorola.com
URI:
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 22, line 41 skipping to change at page 22, 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 (2004). This document is subject Copyright (C) The Internet Society (2005). 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. 

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