draft-ietf-seamoby-mobility-terminology-00.txt   draft-ietf-seamoby-mobility-terminology-01.txt 
Internet Engineering Task Force J. Manner (ed.) Internet Engineering Task Force J. Manner (ed.)
Internet-Draft M. Kojo (ed.) Internet-Draft M. Kojo (ed.)
Expires: February 28, 2003 University of Helsinki Expires: May, 2003 University of Helsinki
August 31, 2002 November, 2002
Mobility Related Terminology Mobility Related Terminology
<draft-ietf-seamoby-mobility-terminology-00.txt> <draft-ietf-seamoby-mobility-terminology-01.txt>
Status of this Memo Status of this Memo
This document is a working group contribution for the Seamoby Working This document is a working group document of the Seamoby Working
Group. Group.
Distribution of this memo is unlimited. Distribution of this memo is unlimited.
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. Internet-Drafts are working all provisions of Section 10 of RFC2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
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 in February, 2003. This Internet-Draft will expire in May, 2003.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
Abstract Abstract
There is a need for common definitions of terminology in the work to There is a need for common definitions of terminology in the work to
be done around IP mobility. This memo defines terms for mobility be done around IP mobility. This memo defines terms for mobility
related terminology. It is intended as a living document for use by related terminology. It is intended as a living document for use by
the Seamoby working group in Seamoby drafts and in WG discussions. the Seamoby Working Group in Seamoby drafts and in WG discussions,
Other working groups dealing with mobility may also take advantage of but not limited in scope to the terms needed by the Seamoby Working
this terminology. Group. Other working groups dealing with mobility may take advantage
of this terminology.
Changes from -03
- Added CAR Discovery terminology
- Added placeholder for security terminology
- Edited the introduction and the figure in the network nodes section
Changes from draft-manner-seamoby-terms-04.txt
- Removed a few security related terms based on discussions in
Yokohama. Some key mobility-related security terms will be added
later.
TODOs (some ideas)
- Add basic terminology about mobile networks.
- Re-write the Network Components section
- Compare to the definitions in FMIPv6 and add missing parts
- Add more terms, eg. MPR (Multipoint Relay), "Reverse Routability", Changes from -00
BU, FBU, etc. - Added definition for Routing Proxy
- Added basic terminology about mobile networks
- Added Link-Layer Trigger from FMIPv6
- Edited the CAR terminology section
- Added definitions for MPR, CoA, BU
- Changed the definition of Home Address
- Added a mobile network into Figure 1
- Edited the Network Components section
- Compare against definitions in the LMM documents of the IRTF MM- TODO's
subgroup. See if there is some harmonization to be done. The draft-irtf-mm-taxonomy-00.txt (expired) includes several good
additional candidate definitions, eg.:
o Mobility identities
o Transports
o Others?
We also need someone to write the Security Terminology section.
Table of Contents Table of Contents
1 Introduction ................................................. 3 1 Introduction ................................................. 2
2 General Terms ................................................ 3 2 General Terms ................................................ 3
3 Network Components ........................................... 7 3 Mobile Access Network Components ............................. 8
4 Handover Terminology ......................................... 11 4 Handover Terminology ......................................... 11
4.1 Scope of Handover .......................................... 11 4.1 Scope of Handover .......................................... 12
4.2 Handover Control ........................................... 13 4.2 Handover Control ........................................... 13
4.3 Simultaneous connectivity to Access Routers ................ 14 4.3 Simultaneous connectivity to Access Routers ................ 14
4.4 Performance and Functional Aspects ......................... 14 4.4 Performance and Functional Aspects ......................... 15
4.5 Micro Diversity, Macro Diversity, and IP Diversity ......... 15 4.5 Micro Diversity, Macro Diversity, and IP Diversity ......... 16
4.6 Paging, and Mobile Node States and Modes ................... 16 4.6 Paging, and Mobile Node States and Modes ................... 17
4.7 Context Transfer ........................................... 18 4.7 Context Transfer ........................................... 18
4.8 Candidate Access Router Discovery .......................... 19 4.8 Candidate Access Router Discovery .......................... 19
4.9 User, Personal and Host Mobility ........................... 19 4.9 User, Personal and Host Mobility ........................... 19
5 Specific Terminology for Mobile Ad-Hoc Networking ............ 20 5 Specific Terminology for Mobile Ad-Hoc Networking ............ 21
6 Security-related Terminology ................................. 21 6 Mobile Networks .............................................. 22
7 Security Considerations ...................................... 22 7 Security-related Terminology ................................. 22
8 Contributors ................................................. 22 8 Security Considerations ...................................... 23
9 Acknowledgement .............................................. 22 9 Contributors ................................................. 23
10 References .................................................. 23 10 Acknowledgement ............................................. 23
11 Author's Addresses .......................................... 24 11 References .................................................. 23
12 Appendix A - Examples ....................................... 26 12 Author's Addresses .......................................... 25
13 Appendix B - Index of Terms ................................. 28 13 Appendix A - Examples ....................................... 27
14 Appendix B - Index of Terms ................................. 29
1. Introduction 1. Introduction
This document presents terminology to be used for documents and This document presents terminology to be used for documents and
discussions within the Seamoby Working Group. Other mobility related discussions within the Seamoby Working Group. Other mobility related
working groups could like take advantage of this terminology, in working groups could like take advantage of this terminology, in
order to create a common terminology for the area of mobility. These order to create a common terminology for the area of mobility in IP
groups would include MIP, MANET, ROHC and possibly NEMO. networks. These groups would include MIP, MANET, ROHC and NEMO.
Some terms and their definitions that are not directly related to the Some terms and their definitions that are not directly related to the
IP world are included for the purpose of harmonizing the terminology, IP world are included for the purpose of harmonizing the terminology,
for example, 'Access Point' and 'base station' refer to the same for example, 'Access Point' and 'base station' refer to the same
component, from the point of view of IP, but 'Access Router' has a component, from the point of view of IP, but 'Access Router' has a
very different meaning. The presented terminology may also, it is very different meaning. The presented terminology may also, it is
hoped, be adequate to cover mobile ad-hoc networks. hoped, be adequate to cover mobile ad-hoc networks.
The proposed terminology is not meant to assert any new terminology. The proposed terminology is not meant to assert any new terminology.
Rather the authors would welcome discussion on more exact definitions Rather the authors would welcome discussion on more exact definitions
as well as missing or unnecessary terms. This work is a as well as missing or unnecessary terms. This work is a
collaborative enterprise between people from many different collaborative enterprise between people from many different
engineering backgrounds and so already presents a first step in engineering backgrounds and so already presents a first step in
harmonizing the terminology. harmonizing the terminology.
The terminology in this draft is divided into several sections. The terminology in this draft is divided into several sections.
First, there is a list of terms for general use, followed by some First, there is a list of terms for general use and mobile access
terms related to handovers, and finally some terms used within the networks followed by terms related to handovers, and finally some
MANET working group. terms used within the MANET and NEMO working group.
2. General Terms 2. General Terms
Bandwidth Bandwidth
The total capacity of a link to carry information (typically The total capacity of a link to carry information (typically
bits). bits).
Bandwidth Utilization Bandwidth Utilization
The actual amount of information delivered over a link, expressed The actual amount of information delivered over a link, expressed
as a percent of the available bandwidth on that link. as a percent of the available bandwidth on that link.
Beacon Beacon
A control message broadcast by a node (especially, a base A control message broadcast by a node (especially, a base
station) informing all the other nodes in its neighborhood of the station) informing all the other nodes in its neighborhood of the
continuing presence of the broadcasting node, possibly along with continuing presence of the broadcasting node, possibly along with
additional status or configuration information. additional status or configuration information.
Channel Binding update (BU)
A message indicating a mobile node's current mobility binding,
and in particular its care-of address.
Care-of Address (CoA)
An IP address associated with a mobile node while visiting a
foreign link; the subnet prefix of this IP address is a foreign
subnet prefix. Among the multiple care-of addresses that a
mobile node may have at any given time (e.g., with different
subnet prefixes), the one registered with the mobile node's home
agent is called its "primary" care-of address [12].
Channel
A subdivision of the physical medium allowing possibly shared A subdivision of the physical medium allowing possibly shared
independent uses of the medium. Channels may be made available independent uses of the medium. Channels may be made available
by subdividing the medium into distinct time slots, or distinct by subdividing the medium into distinct time slots, or distinct
spectral bands, or decorrelated coding sequences. spectral bands, or decorrelated coding sequences.
Channel Access Protocol Channel Access Protocol
A protocol for mediating access to, and possibly allocation of, A protocol for mediating access to, and possibly allocation of,
the various channels available within the physical communications the various channels available within the physical communications
medium. Nodes participating in the channel access protocol can medium. Nodes participating in the channel access protocol can
skipping to change at page 4, line 46 skipping to change at page 4, line 50
The process of delivering data or control messages to every node The process of delivering data or control messages to every node
within the network under consideration. within the network under consideration.
Forwarding node Forwarding node
A node which performs the function of forwarding datagrams from A node which performs the function of forwarding datagrams from
one of its neighbors to another. one of its neighbors to another.
Home Address Home Address
An IP address that is assigned for an extended period of time to An IP address assigned to a mobile node, used as the permanent
a mobile node. It remains unchanged regardless of where the node address of the mobile node. This address is within the mobile
is attached to the Internet [10]. node's home link. Standard IP routing mechanisms will deliver
packets destined for a mobile node's home address to its home
link [12].
Interface Interface
A node's attachment to a link. A node's attachment to a link.
IP access address IP access address
An IP address (often dynamically allocated) which a node uses to An IP address (often dynamically allocated) which a node uses to
designate its current point of attachment to the access network. designate its current point of attachment to the access network.
The IP access address is typically to be distinguished from the The IP access address is typically to be distinguished from the
mobile node's home address; in fact, the former may be considered mobile node's home address; in fact, the former may be considered
unsuitable for use by any but the most short-lived applications. unsuitable for use by any but the most short-lived applications.
skipping to change at page 5, line 29 skipping to change at page 5, line 36
instance, the range of one transmitter may be much higher than instance, the range of one transmitter may be much higher than
the range of another transmitter on the same medium. the range of another transmitter on the same medium.
Link Establishment Link Establishment
The process of establishing a link between the mobile node and The process of establishing a link between the mobile node and
the access network. This may involve allocating a channel, or the access network. This may involve allocating a channel, or
other local wireless resources, possibly including a minimum other local wireless resources, possibly including a minimum
level of service or bandwidth. level of service or bandwidth.
Link-layer Trigger (L2 Trigger)
Information from L2 that informs L3 of the detailed events
involved in handover sequencing at L2. L2 triggers are not
specific to any particular L2, but rather represent
generalizations of L2 information available from a wide variety
of L2 protocols [4].
Link State Link State
A style of routing protocol in which every node within the A style of routing protocol in which every node within the
network is expected to maintain information about every link network is expected to maintain information about every link
within the network topology. within the network topology.
Link-level Acknowledgement Link-level Acknowledgement
A protocol strategy, typically employed over wireless media, A protocol strategy, typically employed over wireless media,
requiring neighbors to acknowledge receipt of packets (typically requiring neighbors to acknowledge receipt of packets (typically
skipping to change at page 6, line 16 skipping to change at page 6, line 33
medium access protocol can communicate only when they have medium access protocol can communicate only when they have
uncontested access to the medium, so that there will be no uncontested access to the medium, so that there will be no
interference. When the physical medium is a radio channel, the interference. When the physical medium is a radio channel, the
MAC is the same as the Channel Access Protocol. MAC is the same as the Channel Access Protocol.
Mobility Factor Mobility Factor
The relative frequency of node movement, compared to the The relative frequency of node movement, compared to the
frequency of application initiation. frequency of application initiation.
Multipoint relay (MPR)
A node which is selected by its one-hop neighbor to re-transmit
all broadcast messages that it receives. The message must be new
and the time-to-live field of the message must be greater than
one. Multipoint relaying is a technique to reduce the number of
redundant re-transmissions while diffusing a broadcast message in
the network.
Neighbor Neighbor
A "neighbor" is any other node to which data may be propagated A "neighbor" is any other node to which data may be propagated
directly over the communications medium without relying the directly over the communications medium without relying the
assistance of any other forwarding node assistance of any other forwarding node
Neighborhood Neighborhood
All the nodes which can receive data on the same link from one All the nodes which can receive data on the same link from one
node whenever it transmits data. node whenever it transmits data.
skipping to change at page 6, line 33 skipping to change at page 7, line 4
All the nodes which can receive data on the same link from one All the nodes which can receive data on the same link from one
node whenever it transmits data. node whenever it transmits data.
Next Hop Next Hop
A neighbor which has been selected to forward packets along the A neighbor which has been selected to forward packets along the
way to a particular destination. way to a particular destination.
Payload Payload
The actual data within a packet, not including network protocol The actual data within a packet, not including network protocol
headers which were not inserted by an application. headers which were not inserted by an application. Note, that
payloads are different between layers: user data is the payload
DISCUSSION: How shall we say that payloads are different between of TCP, which are the payload of IP, which three are the payload
layers: user data is the payload of TCP, which are the payload of of link layer protocols etc. Thus, it is important to identify
IP, which three are the payload of link layer protocols etc. the scope when talking about payloads.
Prefix Prefix
A bit string that consists of some number of initial bits of an A bit string that consists of some number of initial bits of an
address. address.
Route Table Route Table
The table where forwarding nodes keep information (including next The table where forwarding nodes keep information (including next
hop) for various destinations. hop) for various destinations.
skipping to change at page 7, line 4 skipping to change at page 7, line 27
The table where forwarding nodes keep information (including next The table where forwarding nodes keep information (including next
hop) for various destinations. hop) for various destinations.
Route Entry Route Entry
An entry for a specific destination (unicast or multicast) in the An entry for a specific destination (unicast or multicast) in the
route table. route table.
Route Establishment Route Establishment
The process of determining a route between a source and a The process of determining a route between a source and a
destination. destination.
Route Activation Route Activation
The process of putting a route into use after it has been The process of putting a route into use after it has been
determined. determined.
Routing Proxy
A node that routes packets by overlays, eg. by tunneling, between
communicating partners. The Home Agent and Foreign Agent are
examples of routing proxies, in that they receive packets
destined for the mobile node and tunnel them to the current
address of the mobile node.
Signal Strength Signal Strength
The detectable power of the signal carrying the data bits, as The detectable power of the signal carrying the data bits, as
seen by the receiver of the signal. seen by the receiver of the signal.
Source Route Source Route
A source route from node A to node B is an ordered list of IP A source route from node A to node B is an ordered list of IP
addresses, starting with the IP address of node A and ending with addresses, starting with the IP address of node A and ending with
the IP address of the node B. Between A and B, the source route the IP address of the node B. Between A and B, the source route
skipping to change at page 7, line 47 skipping to change at page 8, line 26
A network can be viewed abstractly as a "graph" whose "topology" A network can be viewed abstractly as a "graph" whose "topology"
at any point in time is defined by set of "points" connected by at any point in time is defined by set of "points" connected by
(possibly directed) "edges." (possibly directed) "edges."
Triggered Update Triggered Update
An unsolicited route update transmitted by an router along a path An unsolicited route update transmitted by an router along a path
to a destination. to a destination.
3. Network Components 3. Mobile Access Network Components
Figure 1 presents a reference architecture which illustrates an IP In order to support host mobility a set of nodes towards the network
network with components defined in this section. The figure presents edge often need to have specific functions. Such a set of nodes form
two examples of access network (AN) topologies. a mobile access network that may or may not be part of the global
Internet. The Figure 1 presents two examples of such access network
(AN) topologies. The figure depicts a reference architecture which
illustrates an IP network with components defined in this section.
We intend to define the concept of the Access Network (AN) which We intend to define the concept of the Access Network (AN) which may
supports enhanced mobility.It is possible that to support routing and also support enhanced mobility. It is possible that to support
QoS for mobile nodes, existing routing protocols (i.e., OSPF or other routing and QoS for mobile nodes, existing routing protocols (i.e.,
standard IGPs) may not be appropriate to maintain forwarding OSPF or other standard IGPs) may not be appropriate to maintain
information for these mobile nodes as they change their points of forwarding information for these mobile nodes as they change their
attachment to the Access Network. These new functions are points of attachment to the Access Network. These new functions are
implemented in routers with additional capability. We can implemented in routers with additional capability. We can
distinguish three types of Access Network components: Access Routers distinguish three types of Access Network components: Access Routers
(AR) which handle the last hop to the mobile; Access Network Gateways (AR) which handle the last hop to the mobile, typically over a
(ANG) which form the boundary on the fixed network side and shield wireless link; Access Network Gateways (ANG) which form the boundary
the fixed network from the specialized routing protocols; and on the fixed network side and shield the fixed network from the
(optionally) other internal Access Network Routers which may also be specialized routing protocols; and (optionally) other internal Access
needed in some cases to support the protocols. The Access Network Network Routers which may also be needed in some cases to support the
consists of the equipment needed to support this specialized routing, protocols. The Access Network consists of the equipment needed to
i.e. AR/ANG/ANR. support this specialized routing, i.e. AR/ANG/ANR. AR and ANG may be
the same physical nodes.
Note: this reference architecture is not well suited for people Note: this reference architecture is not well suited for people
dealing with MANETs. We need to refine this section in the future. dealing with MANETs.
Mobile Node (MN)
An IP node capable of changing its point of attachment to the
network. A Mobile Node may have routing functionality.
Mobile Host (MH)
A mobile node that is an end host and not a router.
Access Link (AL)
A last-hop link between a Mobile Node and an Access Router. That
is, a facility or medium over which an Access Point and the
Mobile Node can communicate at the link layer, i.e., the layer
immediately below IP.
--- ------ ------- | --- ------ ------- |
--- | <--> | | -------| AR | -------------------| | | --- | <--> | | -------| AR | -------------------| | |
| |--[] --- /------ \ /| ANG |--| | |--[] --- /------ \ /| ANG |--|
--- AP / \ / | | | --- AP / \ / | | |
MN / \ / ------- | MN / \ / ------- |
(+wireless ___ / ------- | (+wireless ___ / ------- |
device) | |---- | ANR | | device) | |---- | ANR | |
--- ------- | --- ------- |
AP / \ | AP / \ |
/ \ ------- | / \ ------- |
--- ------ / \| | | --- ------ / \| | |
| |-------| AR |---------------------| ANG |--| | |-------| AR |---------------------| ANG |--|
--- ------ | | | --- ------ | | |
AP ------- | AP ------- |
| |
Access Network (AN) 1 | Access Network (AN) 1 |
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -|
Access Network (AN) 2 | Access Network (AN) 2 |
| |
| |
--- ------ ------- | --- ------ ------- |
--- |<--> | | -------| AR | -------------------| | | --- |<--> | | -------| AR | -------------------| | |
| |--[] --- /------ /| ANG |--| | |--[] --- /------ /| ANG |--|
--- AP / / | | | --- AP / / | | |
MN / / ------- | MN / / ------- |
(+wireless ___ / / | (+wireless ___ / / |
device) | |---- / | device) | |---- / |
--- / | --- / |
AP / | AP / |
/ | / |
--- ------ ------- | --- ------ ------- |
| |-------| AR |---------| ANR | | --- | I<--> | |-------| AR |---------| ANR | |
--- \ ------ ------- | | |--| ------ --- \ ------ ------- |
AP \ / | --- |--| MR | AP \ / |
\ / | MNN | ------ \ / |
--- \ ------ / | | --- \ ------ / |
| |-------| AR |------- | --- | | |-------| AR |------- |
--- ------ | | |--| --- ------ |
AP | --- | AP |
MNN
Figure 1: Reference Network Architecture Figure 1: Reference Network Architecture
Mobile Node (MN)
An IP node capable of changing its point of attachment to the
network. A Mobile Node may have routing functionality.
Mobile Host (MH)
A mobile node that is an end host and not a router.
Access Link (AL)
A last-hop link between a Mobile Node and an Access Router. That
is, a facility or medium over which an Access Point and the
Mobile Node can communicate at the link layer, i.e., the layer
immediately below IP.
Access Point (AP) Access Point (AP)
An Access Point is a layer 2 device which is connected to one or An Access Point is a layer 2 device which is connected to one or
more Access Routers and offers the wireless link connection to more Access Routers and offers the wireless link connection to
the Mobile Node. Access Points are sometimes called base the Mobile Node. Access Points are sometimes called base
stations or access point transceivers. An Access Point may be a stations or access point transceivers. An Access Point may be a
separate entity or co-located with an Access Router. separate entity or co-located with an Access Router.
Radio Cell Radio Cell
skipping to change at page 10, line 28 skipping to change at page 10, line 48
Points may be of different technology. An Access Router offers Points may be of different technology. An Access Router offers
IP connectivity to Mobile Nodes, acting as a default router to IP connectivity to Mobile Nodes, acting as a default router to
the Mobile Nodes it is currently serving. The Access Router may the Mobile Nodes it is currently serving. The Access Router may
include intelligence beyond a simple forwarding service offered include intelligence beyond a simple forwarding service offered
by ordinary IP routers. by ordinary IP routers.
Access Network Gateway (ANG) Access Network Gateway (ANG)
An Access Network Router that separates an Access Network from An Access Network Router that separates an Access Network from
other IP networks, much in the same way as an ordinary gateway other IP networks, much in the same way as an ordinary gateway
router. An Access Router and an Access Network Gateway may be router. The Access Network Gateway looks to the other IP networks
the same physical node. The Access Network Gateway looks to the like a standard IP router.
other IP networks like a standard IP router.
Access Network (AN) Access Network (AN)
An IP network which includes one or more Access Network Routers. An IP network which includes one or more Access Network Routers.
Administrative Domain (AD) Administrative Domain (AD)
A collection of networks under the same administrative control A collection of networks under the same administrative control
and grouped together for administrative purposes. [5] and grouped together for administrative purposes. [5]
Serving Access Router (SAR) Serving Access Router (SAR)
The Access Router currently offering the connectivity to the The Access Router currently offering the connectivity to the
Mobile Host. This is usually the point of departure for the Mobile Host. This is usually the point of departure for the
Mobile Node as it makes its way towards a new Access Router (then Mobile Node as it makes its way towards a new Access Router (then
Serving Access Router takes the role of the Old Access Router). Serving Access Router takes the role of the Old Access Router).
There may be several Serving Access Routers serving the Mobile There may be several Serving Access Routers serving the Mobile
Node at the same time. Node at the same time.
Old Access Router (OAR) Old Access Router (OAR)
skipping to change at page 19, line 7 skipping to change at page 19, line 23
host. An example of a routing-related service is header host. An example of a routing-related service is header
compression. The service may also be indirectly related to compression. The service may also be indirectly related to
routing, for example, security. Security may not affect the routing, for example, security. Security may not affect the
forwarding decision of all intermediate routers, but a packet may forwarding decision of all intermediate routers, but a packet may
be dropped if it fails a security check (can't be encrypted, be dropped if it fails a security check (can't be encrypted,
authentication failed, etc.). Dropping the packet is basically a authentication failed, etc.). Dropping the packet is basically a
routing decision. routing decision.
4.8. Candidate Access Router Discovery 4.8. Candidate Access Router Discovery
Geographically Adjacent AR (GAAR)
An AR whose coverage area is such that an MN may move from the
coverage area of the AR currently serving the MN into the
coverage area of this AR. In other words, GAARs have APs whose
coverage areas are geographically adjacent or overlap.
Capability of AR Capability of AR
A characteristic of the service offered by an AR that may be of A characteristic of the service offered by an AR that may be of
interest to an MN when the AR is being considered as a handoff interest to an MN when the AR is being considered as a handoff
candidate. candidate.
Candidate AR (CAR) Candidate AR (CAR)
This is an AR that is a candidate for MN's handoff. CAR is An AR to which MN has a choice of performing IP-level handoff.
necessarily a GAAR of the AR currently serving the MN, and also has This means that MN has the right radio interface to connect to an
the capability set required to serve the MN. AP that is served by this AR, as well as the coverage of this AR
overlaps with that of the AR to which MN is currently attached
to.
Target AR (TAR) Target AR (TAR)
This is an AR with which the procedures for the MN's IP-level An AR with which the procedures for the MN's IP-level handoff are
handoff are initiated. TAR is usually selected from the set of initiated. TAR is selected after running a TAR Selection
CARs. Algorithm that takes into account the capabilities of CARs,
preferences of MN and any local policies.
TAR Selection Algorithm
The algorithm that determines a unique TAR for MN's handoff from
the set of CARs. The exact nature and definition of this
algorithm is outside the scope of this document.
4.9. User, Personal and Host Mobility 4.9. User, Personal and Host Mobility
Different sorts of mobility management may be required of a mobile Different sorts of mobility management may be required of a mobile
system. We can differentiate between user, personal and host system. We can differentiate between user, personal and host
mobility. mobility.
User mobility User mobility
refers to the ability of a user to access services from different refers to the ability of a user to access services from different
skipping to change at page 20, line 49 skipping to change at page 20, line 56
Micro mobility Micro mobility
Mobility over a small area. Usually this means mobility within Mobility over a small area. Usually this means mobility within
an IP domain with an emphasis on support for active mode using an IP domain with an emphasis on support for active mode using
handover, although it may include idle mode procedures also. handover, although it may include idle mode procedures also.
Micro-mobility protocols exploit the locality of movement by Micro-mobility protocols exploit the locality of movement by
confining movement related changes and signalling to the access confining movement related changes and signalling to the access
network. network.
Local Mobility Management
Local Mobility Management (LMM) is a generic term for protocols
dealing with IP mobility management confined within the access
network. LMM messages itself are not routed outside the access
network, although, a handover may trigger Mobile IP messages to
be sent to correspondent nodes and home agents.
5. Specific Terminology for Mobile Ad-Hoc Networking 5. Specific Terminology for Mobile Ad-Hoc Networking
Cluster Cluster
A group of nodes located within close physical proximity, A group of nodes located within close physical proximity,
typically all within range of one another, which can be grouped typically all within range of one another, which can be grouped
together for the purpose of limiting the production and together for the purpose of limiting the production and
propogation of routing information. propogation of routing information.
Cluster head Cluster head
skipping to change at page 21, line 43 skipping to change at page 22, line 4
The relative physical location of the nodes within the ad hoc The relative physical location of the nodes within the ad hoc
network. network.
Pathloss matrix Pathloss matrix
A matrix of coefficients describing the pathloss between any two A matrix of coefficients describing the pathloss between any two
nodes in an ad hoc network. When the links are asymmetric, the nodes in an ad hoc network. When the links are asymmetric, the
matrix is also asymmetric. matrix is also asymmetric.
Scenario Scenario
The tuple <laydown, pathloss matrix, mobility factor, traffic> The tuple <laydown, pathloss matrix, mobility factor, traffic>
characterizing a class of ad hoc networks. characterizing a class of ad hoc networks.
6. Security-related Terminology 6. Mobile Networks
This section presents a few basic terms about mobile networks. A more
thorough discussion on mobile networks can be found in the working
group documents of the NEMO Working Group [13].
Mobile Network
An entire network, moving as a unit, which dynamically changes
its point of attachment to the Internet and thus its reachability
in the topology. The mobile network is connected to the global
Internet via one or more mobile router(s). The internal
configuration of the mobile network is assumed to be relatively
stable with respect to the MR and is not a matter of concern.
Mobile Router (MR)
A router which is capable of changing its point of attachment to
IP networks, moving from one link to another link. A mobile
router is capable of forwarding packets between two or more
interfaces, and possibly running a dynamic routing protocol
modifying the state by which to do packet forwarding.
Mobile Network Node (MNN)
Any host or router located within the mobile network, either
permanently or temporarily. A Mobile Network Node may be a Mobile
Router.
7. Security-related Terminology
<This section will include terminology commonly used around mobile <This section will include terminology commonly used around mobile
and wireless networking. Only a subset of the entire security and wireless networking. Only a subset of the entire security
terminology is actually needed.> terminology is actually needed.>
The following were in the previous versions of this document: The following were in the previous versions of this document:
Mobility Security Association Mobility Security Association
A collection of security contexts, between a pair IP nodes, each A collection of security contexts, between a pair IP nodes, each
skipping to change at page 22, line 20 skipping to change at page 23, line 11
A security context between two routers defines the manner in A security context between two routers defines the manner in
which two routers choose to mutually authentication each other, which two routers choose to mutually authentication each other,
and indicates an authentication algorithm and mode. and indicates an authentication algorithm and mode.
Security Parameter Index (SPI) Security Parameter Index (SPI)
An index identifying a security context between a pair of routers An index identifying a security context between a pair of routers
among the contexts possible in the mobility security association. among the contexts possible in the mobility security association.
7. Security Considerations 8. Security Considerations
There are no security issues in this document. There are no security issues in this document.
8. Contributors 9. Contributors
This draft was initially based on the work of This draft was initially based on the work of
o Tapio Suihko, VTT Information Technology, Finland o Tapio Suihko, VTT Information Technology, Finland
o Phil Eardley and Dave Wisely, BT, UK o Phil Eardley and Dave Wisely, BT, UK
o Robert Hancock, Siemens/Roke Manor Research, UK, o Robert Hancock, Siemens/Roke Manor Research, UK,
o Nikos Georganopoulos, King's College London o Nikos Georganopoulos, King's College London
o Markku Kojo and Jukka Manner, University of Helsinki, Finland. o Markku Kojo and Jukka Manner, University of Helsinki, Finland.
Since revision -02, Charles Perkins has given as input terminology Since revision -02 of the document draft-manner-seamoby-terms-02.txt,
related to ad-hoc networks. Charles Perkins has given as input terminology related to ad-hoc
networks.
9. Acknowledgement 10. Acknowledgement
This work has been partially performed in the framework of the IST This work has been partially performed in the framework of the IST
project IST-2000-28584 MIND, which is partly funded by the European project IST-2000-28584 MIND, which is partly funded by the European
Union. The authors would like to acknowledge the help of their Union. The authors would like to acknowledge the help of their
colleagues in preparing this document. colleagues in preparing this document.
Some definitions of terminology have been adapted from [1], [7], [3], Some definitions of terminology have been adapted from [1], [7], [3],
[2], [4], [9], [10] and [11]. [2], [4], [9], [10], [11], [12] and [13].
10. References 11. References
[1] D. Blair, A. Tweedly, M. Thomas, J. Trostle, and [1] D. Blair, A. Tweedly, M. Thomas, J. Trostle, and
M. Ramalho. Realtime Mobile IPv6 Framework (work in M. Ramalho. Realtime Mobile IPv6 Framework (work in
progress). Internet Draft, Internet Engineering Task Force. progress). Internet Draft, Internet Engineering Task Force.
draft-blair-rt-mobileipv6-seamoby-00.txt, November 2000. draft-blair-rt-mobileipv6-seamoby-00.txt, November 2000.
[2] P. Calhoun, G. Montenegro, and C. Perkins. Mobile IP [2] P. Calhoun, G. Montenegro, and C. Perkins. Mobile IP
Regionalized Tunnel Management (work in progress). Internet Regionalized Tunnel Management (work in progress). Internet
Draft, Internet Engineering Task Force, November 1998. Draft, Internet Engineering Task Force, November 1998.
[3] S. Deering and R. Hinden. Internet Protocol, Version 6 (IPv6) [3] S. Deering and R. Hinden. Internet Protocol, Version 6 (IPv6)
Specification. Request for Comments (Draft Standard) 2460, Specification. Request for Comments (Draft Standard) 2460,
Internet Engineering Task Force, December 1998. Internet Engineering Task Force, December 1998.
[4] G. Dommety (ed.). Fast Handovers for Mobile IPv6 (work [4] G. Dommety (ed.). Fast Handovers for Mobile IPv6 (work
in progress). draft-ietf-mobileip-fast-mipv6-04.txt, November in progress). draft-ietf-mobileip-fast-mipv6-05.txt,
2001. September, 2002.
[5] Yavatkar et al. A Framework for Policy-based Admission Control. [5] Yavatkar et al. A Framework for Policy-based Admission
Request for Comments 2753, Internet Engineering Task Force, Control. Request for Comments 2753, Internet Engineering Task
January 2000. Force, January 2000.
[6] J. Kempf, P. McCann, and P. Roberts. IP Mobility and the CDMA [6] J. Kempf, P. McCann, and P. Roberts. IP Mobility and the CDMA
Radio Access Network: Applicability Statement for Soft Handoff Radio Access Network: Applicability Statement for Soft Handoff
(work in progress). Internet Draft, Internet Engineering Task (work in progress). Internet Draft,
Force. draft-kempf-cdma-appl-00.txt, July 2000. draft-kempf-cdma-appl-00.txt, July 2000.
[7] J. Kempf (ed.). Problem Description: Reasons For Doing Context [7] J. Kempf (ed.). Problem Description: Reasons For Doing
Transfers Between Nodes in an IP Access Network. Internet Draft, Context Transfers Between Nodes in an IP Access Network.
Internet Engineering Task Force. RFC 3374, Internet Engineering Task Force, September, 2002.
draft-ietf-seamoby-context-transfer-problem-stat-04.txt, May 2002.
[8] R. Pandya. Emerging Mobile and Personal Communication Systems. [8] R. Pandya. Emerging Mobile and Personal Communication Systems.
IEEE Communications Magazine, 33:44--52, June 1995. IEEE Communications Magazine, 33:44--52, June 1995.
[9] C. Perkins. IP Mobility Support. Request for Comments [9] C. Perkins. IP Mobility Support. Request for Comments
(Proposed Standard) 2002, Internet Engineering Task Force, (Proposed Standard) 2002, Internet Engineering Task Force,
October 1996. October 1996.
[10] R. Ramjee, T. La Porta, S. Thuel, K. Varadhan, and [10] R. Ramjee, T. La Porta, S. Thuel, K. Varadhan, and
L. Salgarelli. IP micro-mobility support using HAWAII (work in L. Salgarelli. IP micro-mobility support using HAWAII (work in
progress). Internet Draft, Internet Engineering Task Force, progress). Internet Draft, Internet Engineering Task Force,
June 1999. June 1999.
[11] D. Trossen, G. Krishnamurthi, H. Chaskar, J. Kempf, "Issues in candidate [11] D. Trossen, G. Krishnamurthi, H. Chaskar, J. Kempf, "Issues in
access router discovery for seamless IP-level handoffs. Internet Draft candidate access router discovery for seamless IP-level
(work in progress), draft-ietf-seamoby-cardiscovery-issues-02.txt, handoffs. Internet Draft (work in progress),
January 2002. draft-ietf-seamoby-cardiscovery-issues-04.txt, October 2002.
11. Author's Addresses [12] David B. Johnson, Charles E. Perkins, Jari Arkko, "Mobility
Support in IPv6". Internet Draft,
draft-ietf-mobileip-ipv6-18.txt (work in progress), June 2002.
[13] Thierry Ernst and Hong-Yon Lach, "Network Mobility Support
Terminology". Internet Draft,
draft-ernst-monet-terminology-01.txt (work in progress), July
2002.
12. Author's Addresses
Questions about this document may be directed to: Questions about this document may be directed to:
Jukka Manner Jukka Manner
Department of Computer Science Department of Computer Science
University of Helsinki University of Helsinki
P.O. Box 26 (Teollisuuskatu 23) P.O. Box 26 (Teollisuuskatu 23)
FIN-00014 HELSINKI FIN-00014 HELSINKI
Finland Finland
skipping to change at page 26, line 5 skipping to change at page 27, line 5
Nikos Georganopoulos Nikos Georganopoulos
King's College London King's College London
Strand Strand
London WC2R 2LS London WC2R 2LS
United Kingdom United Kingdom
Voice: +44-20-78482889 Voice: +44-20-78482889
Fax: +44-20-78482664 Fax: +44-20-78482664
E-Mail: nikolaos.georganopoulos@kcl.ac.uk) E-Mail: nikolaos.georganopoulos@kcl.ac.uk)
12. Appendix A - Examples 13. Appendix A - Examples
This appendix provides examples for the terminology presented. This appendix provides examples for the terminology presented.
A.1. Mobility A.1. Mobility
Host mobility is logically independent of user mobility, although in Host mobility is logically independent of user mobility, although in
real networks, at least the address management functions are often real networks, at least the address management functions are often
required to initially attach the host to the network. In addition, required to initially attach the host to the network. In addition,
if the network wishes to determine whether access is authorized (and if the network wishes to determine whether access is authorized (and
if so, who to charge for it), then this may be tied to the identity if so, who to charge for it), then this may be tied to the identity
skipping to change at page 28, line 46 skipping to change at page 29, line 46
GSM/GPRS/UMTS presentations, for example. From the IP point of view GSM/GPRS/UMTS presentations, for example. From the IP point of view
APs are not directly visible. An AP should only be seen from the APs are not directly visible. An AP should only be seen from the
MN's or AR's IP layer as a link (interface) connecting MNs to the AR. MN's or AR's IP layer as a link (interface) connecting MNs to the AR.
When the mobile moves through the network, depending on the mobility When the mobile moves through the network, depending on the mobility
mechanism, the OAR will forward packets destined to the old MNs mechanism, the OAR will forward packets destined to the old MNs
address to the SAR which currently serves the MN. At the same time address to the SAR which currently serves the MN. At the same time
the handover mechanism may be studying CARs to find the best NAR the handover mechanism may be studying CARs to find the best NAR
where the MN will be handed next. where the MN will be handed next.
13. Appendix B - Index of Terms 14. Appendix B - Index of Terms
<TBA when terminology finalized> <TBA when terminology finalized>
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2001). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
 End of changes. 

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