Professional Documents
Culture Documents
Versions: 00 01
P. Estrela
Internet Draft A.Grilo
T. Vaz?o
M. Nunes
Document: draft-estrela-timip-00.txt INESC
Expires: September 2002 March 2002
Abstract
Table of Contents
1. Introduction
1.1 Applicability
It is assumed that the data link layer of the Access Points is able
to perform terminal power-up detection and to notify the TIMIP
layer.
Estrela [Page 2]
It is also assumed that the Access Routers of the TIMIP domain form
a logical tree, with the Access Network Gateway located at the top.
2. Terminology
Access Network
An IP network that includes one or more Access Routers and a Access
Network Gateway.
Subnet
A range of IP address designed by a common prefix.
3. Architecture
As a Legacy Mobile Node (LMN) has a legacy IP stack and cannot issue
any signaling during handoff, handoff detection by the AR relies on
notification from layer-2. This notification triggers routing
reconfiguration of the TIMIP domain, leading to routing table
updating at the ARs.
4. Registration
Estrela [Page 4]
5. Power-up
Estrela [Page 5]
Estrela [Page 6]
6. Micromobility
An example of handoff between two APs that belong to the same access
subnetwork is depicted in 2.
The first four steps of the Handoff procedure are the same as those
of the Power-up case. The remaining steps are the following:
5. Exchange of RoutingUpdate/RoutingUpdateAck messages climbs up the
hierarchy levels, until the crossover AR (the AR that belongs
simultaneously to the old path and to the new path) is reached
(in the example above, node AR5). Now that the new routing path
is completely created, the old path must be deleted. This
procedure starts when the crossover AR sends a RoutingUpdate
message addressed to the MT through the old routing path. The AR
that receives the message realizes that the MT is no longer
accessible through it, updates its routing path by deleting the
entry that corresponds to the MT and replies with a
RoutingUpdateAck message.
Estrela [Page 7]
7. Macromobility
Estrela [Page 8]
As already seen, all traffic that crosses the boundary of the TIMIP
domain must pass through the ANG, which is the IP Gateway to the
core network. Nevertheless, whenever an MT moves to a different
domain, the IP address of the ANG changes. In order to keep
consistency, the MT must change its IP Gateway configuration at each
handoff between TIMIP domains, otherwise the ARP requests to obtain
the MAC address of the IP Gateway would not be answered by the APs.
This inconvenience is avoided by configuring the MTs with a well-
known ANG IP address recognized by all APs of all TIMIP domains. The
latter broadcast gratuitous ARP messages associating their own MAC
addresses with the well-known ANG IP address each time a terminal
performs an association.
When the MT supports MIP but belongs to a different domain, the ANG
plays the role of FA. The MT powers-on in the same way as legacy MTs
in the TIMIP domain. Once this is completed, the MIP signaling
starts. The ANG broadcasts RFC 1256 [7] Router Advertisement
messages periodically, specifying its IP address as the MIP CoAddr.
In order to haste the process, the MT can request the advertisement
by broadcasting a Router Solicitation message, which is then
forwarded by the AP to the ANG.
Estrela [Page 9]
domain. Handoff between APs within the foreign TIMIP domain are
dealt with TIMIP micromobility procedures only (see above) as the FA
is always the same (i.e. the ANG).
It should be noted that in this case it is the MT itself that
authenticates the MIP messages when communicating with the HA.
8. References
1 Grilo A., Estrela P., Nunes M., Terminal Independent Mobility for
IP (TIMIP)?EEE Communications, Vol. 39 N?12, December 2001.
9. Author's Addresses
Pedro Estrela
INESC
Rua Alves Redol, N.9 Phone: +351-213100324
1000 Lisboa, Portugal Email: pedro.estrela@inesc.pt
Antnio Grilo
INESC
Rua Alves Redol, N.9 Phone: +351-213100226
1000 Lisboa, Portugal Email: amg@cris.inesc.pt
Teresa Vaz?o
INESC
Rua Alves Redol, N.9 Phone: +351-213100286
1000 Lisboa, Portugal Email: teresa.vazao@inesc.pt
߲
Mio Nunes
INESC
Rua Alves Redol, N.9 Phone: +351-213100256
1000 Lisboa, Portugal Email: msn@inesc.pt