You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
90<br />
Domain<br />
GFA/MAP<br />
Figure 3-3 Architecture of<br />
a multiple care of address<br />
scheme<br />
Internet<br />
Border<br />
Router<br />
Router Router Router<br />
FA FA FA<br />
need to maintain a forwarding entry for all active<br />
nodes. It also means that table look-up becomes<br />
a demanding task in terms of processing. These<br />
schemes may thus present scalability problems<br />
as the network grows and the number of active<br />
nodes increases. Furthermore operation assumes<br />
a tree-like structure since the gateway is a single<br />
entry point into the cellular IP domain. Reliability<br />
and performance are thus also a concern.<br />
3.3 Multiple Care-of Addresses<br />
3.3.1 Principles<br />
There are several proposals that follow the multiple<br />
care-of address approach. Among others,<br />
Mobile Regional Registration and Hierarchical<br />
Mobile IP (for IPv6) have gained considerable<br />
attention in IETF. All these proposals allow the<br />
domain to have any arbitrary topology. The<br />
architecture (Figure 3-3) typically consists of<br />
subnet-level agents, which essentially provide<br />
an MH with a local COA (LCOA). This COA<br />
identifies the MH’s current subnet of attachment.<br />
A separate agent, the GFA (Global Foreign<br />
Agent) or MAP (Mobility Anchor Point)<br />
resides at a higher level in the domain hierarchy<br />
and provides the MH with a stable point of<br />
attachment. This point of attachment remains the<br />
same while the MH is in the same domain. The<br />
global care-of address either refers to an address<br />
associated with the top-level agent or an address<br />
for which packets are intercepted by the agent.<br />
Since only the global COA is available to a CH<br />
located outside the domain, all packets destined<br />
to the MH use this COA. The MA/GFA intercepts<br />
these packets and then forwards them to<br />
the MH’s local COA.<br />
Having previously focused on IPv4, we thought<br />
it adequate to present a scheme designed primarily<br />
for IPv6, so we only present Hierarchical<br />
Mobile IPv6 in this chapter.<br />
3.3.2 Hierarchical Mobile IPv6<br />
In this scheme [6] the MH discovers the address<br />
of the MAP through router advertisements. The<br />
MH registers with the MAP using its local careof<br />
address and permanent home address. Then<br />
it sends binding updates to the CH and the HA<br />
indicating the MAP’s address as the alternative<br />
care-of address (ACOA). The CH can then transmit<br />
packets using the routing header option<br />
directly to this ACOA. The MAP will then forward<br />
the packet towards the Local CoA<br />
(LCOA).<br />
On subsequent movement within the domain, the<br />
MH obtains a new Local COA (based on the<br />
stateless autoconfiguration mechanism) and then<br />
updates its MAP of this new LCOA. The MAP<br />
can then tunnel packets to this new LCOA.<br />
The domain of a MAP is defined as the area<br />
where the router advertisement is advertising<br />
the identity of the MAP. Thus movement across<br />
domains is detected when the MAP address in<br />
the router advertisement has changed. When the<br />
MH has moved into a new domain, it sends the<br />
address of the new MAP (ACOA) in separate<br />
BUs to each of its CHs and its HA.<br />
The MH must also check for the existence of<br />
a routing header in the inner packet; if such a<br />
header exists, the MH can assume that the CH is<br />
aware of its ACOA and does not need to receive<br />
a new BU.<br />
3.3.3 Analysis<br />
The main benefit of a scheme like HMIPv6 is of<br />
course the reduced global signalling compared to<br />
Mobile IPv6. It also enables the use of standard<br />
IP routers in each domain thus avoiding the cost<br />
of manufacturing special routers. The main<br />
drawback is that tunnelling is required inside the<br />
domain (between the MAP and the MH) which<br />
results in<br />
• Poor transport efficiency;<br />
• High Header processing complexity in the<br />
MH and Intermediate foreign agents.<br />
Telektronikk 1.2001