draft-ietf-seamoby-mobility-terminology-01.txt   draft-ietf-seamoby-mobility-terminology-02.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: May, 2003 University of Helsinki Expires: September, 2003 University of Helsinki
November, 2002 March, 2003
Mobility Related Terminology Mobility Related Terminology
<draft-ietf-seamoby-mobility-terminology-01.txt> <draft-ietf-seamoby-mobility-terminology-02.txt>
Status of this Memo Status of this Memo
This document is a working group document of 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
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 May, 2003. This Internet-Draft will expire in September, 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,
but not limited in scope to the terms needed by the Seamoby Working but not limited in scope to the terms needed by the Seamoby Working
Group. Other working groups dealing with mobility may take advantage Group. Other working groups dealing with mobility may take advantage
of this terminology. of this terminology.
Changes from -01
- Added security terminology
- Miscellaneous small refinements of definitions
Changes from -00 Changes from -00
- Added definition for Routing Proxy - Added definition for Routing Proxy
- Added basic terminology about mobile networks - Added basic terminology about mobile networks
- Added Link-Layer Trigger from FMIPv6 - Added Link-Layer Trigger from FMIPv6
- Edited the CAR terminology section - Edited the CAR terminology section
- Added definitions for MPR, CoA, BU - Added definitions for MPR, CoA, BU
- Changed the definition of Home Address - Changed the definition of Home Address
- Added a mobile network into Figure 1 - Added a mobile network into Figure 1
- Edited the Network Components section - Edited the Network Components section
TODO's
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 ................................................. 2 1 Introduction ................................................. 2
2 General Terms ................................................ 3 2 General Terms ................................................ 3
3 Mobile Access Network Components ............................. 8 3 Mobile Access Networks and Mobile Networks ................... 8
4 Handover Terminology ......................................... 11 4 Handover Terminology ......................................... 12
4.1 Scope of Handover .......................................... 12 4.1 Scope of Handover .......................................... 12
4.2 Handover Control ........................................... 13 4.2 Handover Control ........................................... 14
4.3 Simultaneous connectivity to Access Routers ................ 14 4.3 Simultaneous connectivity to Access Routers ................ 15
4.4 Performance and Functional Aspects ......................... 15 4.4 Performance and Functional Aspects ......................... 15
4.5 Micro Diversity, Macro Diversity, and IP Diversity ......... 16 4.5 Micro Diversity, Macro Diversity, and IP Diversity ......... 16
4.6 Paging, and Mobile Node States and Modes ................... 17 4.6 Paging, and Mobile Node States and Modes ................... 17
4.7 Context Transfer ........................................... 18 4.7 Context Transfer ........................................... 19
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 ........................... 20
5 Specific Terminology for Mobile Ad-Hoc Networking ............ 21 5 Specific Terminology for Mobile Ad-Hoc Networking ............ 21
6 Mobile Networks .............................................. 22 6 Security-related Terminology ................................. 22
7 Security-related Terminology ................................. 22 7 Security Considerations ...................................... 23
8 Security Considerations ...................................... 23 8 Contributors ................................................. 23
9 Contributors ................................................. 23 9 Acknowledgement .............................................. 24
10 Acknowledgement ............................................. 23 10 References .................................................. 24
11 References .................................................. 23 11 Author's Addresses .......................................... 26
12 Author's Addresses .......................................... 25 12 Appendix A - Examples ....................................... 28
13 Appendix A - Examples ....................................... 27 13 Appendix B - Index of Terms ................................. 30
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 in IP order to create a common terminology for the area of mobility in IP
networks. These groups would include MIP, MANET, ROHC and 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
skipping to change at page 5, line 4 skipping to change at page 4, line 50
Home Address Home Address
An IP address assigned to a mobile node, used as the permanent An IP address assigned to a mobile node, used as the permanent
address of the mobile node. This address is within the mobile address of the mobile node. This address is within the mobile
node's home link. Standard IP routing mechanisms will deliver node's home link. Standard IP routing mechanisms will deliver
packets destined for a mobile node's home address to its home packets destined for a mobile node's home address to its home
link [12]. 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 local 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, while visiting a foreign
unsuitable for use by any but the most short-lived applications. network the former may be considered unsuitable for use as an
end-point address by any but the most short-lived applications.
Instead, the IP access address is typically used as the care-of
address of the node.
Link Link
A communication facility or physical medium that can sustain data A communication facility or physical medium that can sustain data
communications between multiple network nodes, such as an communications between multiple network nodes, such as an
Ethernet (simple or bridged). A link is the layer immediately Ethernet (simple or bridged). A link is the layer immediately
below IP. below IP.
Asymmetric Link Asymmetric Link
A link with transmission characteristics which are different A link with transmission characteristics which are different
depending upon the relative position or design characteristics of depending upon the relative position or design characteristics of
the transmitter and the receiver of data on the link. For the transmitter and the receiver of data on the link. For
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 local 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) Link-layer Trigger (L2 Trigger)
Information from L2 that informs L3 of the detailed events Information from L2 that informs L3 of the detailed events
involved in handover sequencing at L2. L2 triggers are not involved in handover sequencing at L2. L2 triggers are not
specific to any particular L2, but rather represent specific to any particular L2, but rather represent
generalizations of L2 information available from a wide variety generalizations of L2 information available from a wide variety
of L2 protocols [4]. of L2 protocols [4].
skipping to change at page 8, line 26 skipping to change at page 8, line 21
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. Mobile Access Network Components 3. Mobile Access Networks and Mobile Networks
In order to support host mobility a set of nodes towards the network In order to support host mobility a set of nodes towards the network
edge often need to have specific functions. Such a set of nodes form edge may need to have specific functions. Such a set of nodes form a
a mobile access network that may or may not be part of the global mobile access network that may or may not be part of the global
Internet. The Figure 1 presents two examples of such access network Internet. The Figure 1 presents two examples of such access network
(AN) topologies. The figure depicts a reference architecture which topologies. The figure depicts a reference architecture which
illustrates an IP network with components defined in this section. illustrates an IP network with components defined in this section.
We intend to define the concept of the Access Network (AN) which may We intend to define the concept of the Access Network (AN) which may
also support enhanced mobility. It is possible that to support also support enhanced mobility. It is possible that to support
routing and QoS for mobile nodes, existing routing protocols (i.e., routing and QoS for mobile nodes, existing routing protocols (i.e.,
OSPF or other standard IGPs) may not be appropriate to maintain OSPF or other standard IGPs) may not be appropriate to maintain
forwarding information for these mobile nodes as they change their forwarding information for these mobile nodes as they change their
points of 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
distinguish three types of Access Network components: Access Routers three types of Access Network components: Access Routers (AR) which
(AR) which handle the last hop to the mobile, typically over a handle the last hop to the mobile, typically over a wireless link;
wireless link; Access Network Gateways (ANG) which form the boundary Access Network Gateways (ANG) which form the boundary on the fixed
on the fixed network side and shield the fixed network from the network side and shield the fixed network from the specialized
specialized routing protocols; and (optionally) other internal Access routing protocols; and (optionally) other internal Access Network
Network Routers which may also be needed in some cases to support the Routers which may also be needed in some cases to support the
protocols. The Access Network consists of the equipment needed to protocols. The Access Network consists of the equipment needed to
support this specialized routing, i.e. AR/ANG/ANR. AR and ANG may be support this specialized routing, i.e. AR/ANG/ANR. AR and ANG may be
the same physical nodes. the same physical nodes.
In addition, we present a few basic terms on mobile networks, that
is, mobile network, mobile router (MR), and mobile network node
(MNN). A more thorough discussion on mobile networks can be found in
the working group documents of the NEMO Working Group [13].
Note: this reference architecture is not well suited for people Note: this reference architecture is not well suited for people
dealing with MANETs. dealing with MANETs.
--- ------ ------- | --- ------ ------- |
--- | <--> | | -------| AR | -------------------| | | --- | <--> | | -------| AR | -------------------| | |
| |--[] --- /------ \ /| ANG |--| | |--[] --- /------ \ /| ANG |--|
--- AP / \ / | | | --- AP / \ / | | |
MN / \ / ------- | MH / \ / ------- |
(+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 / / ------- | MH / / ------- |
(+wireless ___ / / | (+wireless ___ / / |
device) | |---- / | device) | |---- / |
--- / | --- / |
AP / | AP / |
/ | / |
--- ------ ------- | --- ------ ------- |
--- | I<--> | |-------| AR |---------| ANR | | --- | I<--> | |-------| AR |---------| ANR | |
| |--| ------ --- \ ------ ------- | | |--| ------ --- \ ------ ------- |
--- |--| MR | AP \ / | --- |--| MR | AP \ / |
MNN | ------ \ / | MNN | ------ \ / |
skipping to change at page 9, line 51 skipping to change at page 9, line 51
--- | | |-------| AR |------- | --- | | |-------| AR |------- |
| |--| --- ------ | | |--| --- ------ |
--- | AP | --- | AP |
MNN MNN
Figure 1: Reference Network Architecture Figure 1: Reference Network Architecture
Mobile Node (MN) Mobile Node (MN)
An IP node capable of changing its point of attachment to the An IP node capable of changing its point of attachment to the
network. A Mobile Node may have routing functionality. network. A Mobile Node may or may not have forwarding
functionality.
Mobile Host (MH) Mobile Host (MH)
A mobile node that is an end host and not a router. A mobile node that is an end host and not a router. A Mobile host
is capable of sending and receiving packets, that is, being a
source or destination of traffic, but not a forwarder of it.
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 node (host or router) located within a mobile network, either
permanently or temporarily. A Mobile Network Node may be a Mobile
Router.
Access Link (AL) Access Link (AL)
A last-hop link between a Mobile Node and an Access Router. That 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 is, a facility or medium over which an Access Point and the
Mobile Node can communicate at the link layer, i.e., the layer Mobile Node can communicate at the link layer, i.e., the layer
immediately below IP. immediately below IP.
Access Point (AP) Access Point (AP)
skipping to change at page 13, line 9 skipping to change at page 13, line 34
A handover between equipment of the same technology. A handover between equipment of the same technology.
Inter-technology Handover Inter-technology Handover
A handover between equipment of different technologies. A handover between equipment of different technologies.
Horizontal Handover Horizontal Handover
A handover in which the mobile node's network interface does not A handover in which the mobile node's network interface does not
change (from the IP point of view); the MN communicates with the change (from the IP point of view); the MN communicates with the
access network via the same network interface before and after access router via the same network interface before and after the
the handover. A horizontal handover is typically also an intra- handover. A horizontal handover is typically also an intra-
technology handover but it can be an inter-technology handover if technology handover but it can be an inter-technology handover if
the MN can do a layer 2 handover between two different the MN can do a layer 2 handover between two different
technologies without changing the network interface seen by the technologies without changing the network interface seen by the
IP layer. IP layer.
Vertical Handover Vertical Handover
In a vertical handover the mobile node's network interface to the In a vertical handover the mobile node's network interface to the
Access Network changes. A vertical handover is typically an access network changes. A vertical handover is typically an
inter-technology handover but it may also be an intra- technology inter-technology handover but it may also be an intra- technology
handover if the MN has several network interfaces of the same handover if the MN has several network interfaces of the same
type. That is, after the handover, the IP layer communicates with type. That is, after the handover, the IP layer communicates with
the Access Network through a different network interface. the access network through a different network interface.
The different handover types defined in this section and in section The different handover types defined in this section and in section
4.1 have no direct relationship. In particular, a MN can do an 4.1 have no direct relationship. In particular, a MN can do an
intra-AN handover of any of the types defined above. intra-AN handover of any of the types defined above.
Note that the horizontal and vertical handovers are not tied to a Note that the horizontal and vertical handovers are not tied to a
change in the link layer technology. They define whether, after a change in the link layer technology. They define whether, after a
handover, the IP packet flow goes through the same (horizontal handover, the IP packet flow goes through the same (horizontal
handover) or a different (vertical handover) network interface. handover) or a different (vertical handover) network interface.
These two handovers do not define whether the AR changes as a result These two handovers do not define whether the AR changes as a result
skipping to change at page 22, line 4 skipping to change at page 22, line 27
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. Mobile Networks 6. Security-related Terminology
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) This section includes terminology commonly used around mobile and
wireless networking. Only a mobility-related subset of the entire
security terminology is presented.
Any host or router located within the mobile network, either Authorization-enabling extension
permanently or temporarily. A Mobile Network Node may be a Mobile
Router.
7. Security-related Terminology An authentication which makes a (registration) message acceptable
to the ultimate recipient of the registration message. An
authorization-enabling extension must contain an SPI [14].
<This section will include terminology commonly used around mobile Mobility Security Association
and wireless networking. Only a subset of the entire security
terminology is actually needed.>
The following were in the previous versions of this document: A collection of security contexts, between a pair of nodes, which
may be applied to mobility-related protocol messages exchanged
between them. In Mobile IP, each context indicates an
authentication algorithm and mode, a secret (a shared key, or
appropriate public/private key pair), and a style of replay
protection in use. Mobility security associations may be stored
separately from the node's IPsec Security Policy Database (SPD)
[14].
Mobility Security Association Registration Key
A collection of security contexts, between a pair IP nodes, each A key used as the basis of a Mobility Security Association
of which is configured to be applied to mobility-related protocol between a mobile node and a foreign agent. A registration key is
messages exchanged between them. Mobility security associations typically only used once or a very few times, and only for the
MAY be stored separately from the node's IPsec Security Policy purposes of verifying a small volume of Authentication data [16].
Database (SPD).
Security Context Security Context
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.
8. Security Considerations Stale challenge
There are no security issues in this document. Any challenge that has been used by the mobile node in a
Registration Request message and processed by the Foreign Agent
by relaying or generating The Foreign Agent may not be able to
keep records for all previously used challenges [15].
9. Contributors Unknown challenge
Any challenge from a particular mobile node that the foreign
agent has no record of having put either into one of its recent
Agent Advertisements or into a registration reply message to that
mobile node [15].
Unused challenge
A challenge that has not been already accepted by the Foreign
Agent challenge in a corresponding Registration Reply message --
i.e., a challenge that is neither unknown nor previously used
[15].
The Mobile IPv6 specification includes more security terminology
related to MIPv6 bindings [RFC3xxx].
7. Security Considerations
This document presents only terminology. There are no security issues
in this document.
8. 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 of the document draft-manner-seamoby-terms-02.txt, Since revision -02 of the document draft-manner-seamoby-terms-02.txt,
Charles Perkins has given as input terminology related to ad-hoc Charles Perkins has given as input terminology related to ad-hoc
networks. networks.
10. Acknowledgement 9. 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], [11], [12] and [13]. [2], [4], [9], [10], [11], [12] and [13].
11. References 10. 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.
skipping to change at page 25, line 4 skipping to change at page 25, line 25
draft-ietf-seamoby-cardiscovery-issues-04.txt, October 2002. draft-ietf-seamoby-cardiscovery-issues-04.txt, October 2002.
[12] David B. Johnson, Charles E. Perkins, Jari Arkko, "Mobility [12] David B. Johnson, Charles E. Perkins, Jari Arkko, "Mobility
Support in IPv6". Internet Draft, Support in IPv6". Internet Draft,
draft-ietf-mobileip-ipv6-18.txt (work in progress), June 2002. draft-ietf-mobileip-ipv6-18.txt (work in progress), June 2002.
[13] Thierry Ernst and Hong-Yon Lach, "Network Mobility Support [13] Thierry Ernst and Hong-Yon Lach, "Network Mobility Support
Terminology". Internet Draft, Terminology". Internet Draft,
draft-ernst-monet-terminology-01.txt (work in progress), July draft-ernst-monet-terminology-01.txt (work in progress), July
2002. 2002.
[14] Charles Perkins (ed.), "IP Mobility Support for IPv4". Request
for Comments 3344, August 2002.
12. Author's Addresses [15] Charles Perkins, Pat Calhoun, Jayshree Bharatia, "Mobile
IPv4 Challenge/Response Extensions (revised)". Internet Draft,
December, 2002 (draft-ietf-mobileip-rfc3012bis-04.txt).
[16] Charles Perkins, Pat Calhoun, "AAA Registration Keys for Mobile
IP". Internet Draft, October 2002,
(draft-ietf-mobileip-aaa-key-10.txt).
11. 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 27, line 5 skipping to change at page 28, 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)
13. Appendix A - Examples 12. 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 29, line 46 skipping to change at page 30, 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.
14. Appendix B - Index of Terms 13. 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/