Download PPT Version

Vancouver, November 2005
IETF 64th – netlmm BOF
NETLMM
with distributed anchor routers
draft-giaretta-netlmm-protocol-00
Gerardo Giaretta
[email protected]
Ivano Guardini
Elena Demaria
Purpose of the draft
• Network-based LMM protocol that fulfills the
requirements of draft-kempf-netlmm-nohost-req
• Main requirements considered in the design
– Req#2: Reduction in handover-related signaling volume
– Req#4: Efficient use of wireless resources (minimization of per
packet overhead over the air interface)
– Req #5: Reduction of signaling and packet overhead in the wired
network
• The purpose is to use this protocol as the basic
core network mobility management mechanism
for 3GPP Long Term Evolution network (i.e. 4G)
November, 2005
IETF 64th
2
Main Features (1)
• MN keeps the same IP address while moving in
the same NETLMM Domain
– same prefixes are not advertised by different ARs
• simplification of distributed anchor points allocation
• a solution similar to landmark DNA may be used to let MN keep the
same IP address
• Protocol architecture similar to Mobile IPv6
– the visited AR sends a Location Update message to the Home
Anchor Router (HAR) of the MN when the MN attaches on the link
– HAR mantains a Location Cache which stores current position of the
MN in terms of the AR it is attached to (IP-MN, IP-AR)
– HAR acts as a Mobility Anchor Point for MN
– each AR implements a Location Update List that contains one entry
for each MN attached on the related link
November, 2005
IETF 64th
3
Main features (2)
• MN is identified by the IP address
– CGAs may be used to avoid address ownership issues
• Flexibility in MAP allocation
– may be an aggregation router
• to improve location privacy (e.g. upon user request)
– may be co-located with Access Routers
• optimized support for sensors or “users” with minimal movement ability
• AR may span a large area (similar to a MSC area)
• Multiple MAPs located in a NETLMM Domain
– needed to have a scalable solution and load balance among them
• In the draft also
– some considerations on MN-AR interface
– some ideas about Route Optimization
November, 2005
IETF 64th
4
Routing of data packets
Standard IP
Routing
Edge mobility
Domain
Tunneling
Edge mobility
Domain
AR1
AR2
HAR
for MN
AR3
AR1
AR2
HAR
for MN
CN
MN
IP addr = IPMN
HAR – Home Anchor Router
acts as Mobility Anchor Point
for the MN
MN
IP addr = IPMN
AR3
CN
November, 2005
IETF 64th
5