Host ID/Loc Splitting, Mobility, Multihoming

Antônio Marcos Alberti

alberti@inatel.br
antonioalberti@gmail.com
http://antonioalberti.blogspot.com/
www.inatel.br/docentes/alberti

Topics
 Mobile IP
 HIP (Host Identity Protocol)
 LISP (Locator ID Separation Protocol)
 MILSA (Mobility and Multihoming Supporting Identifier Locator
Split Architecture)
 Akari
 MCP (Mobility Control Protocol)

© Antônio M. Alberti 2011

1
Mobile IP
 Idea:
 Two IP addresses:
 Home-address  static; works as an ID for app. layer;
 Care-of-address  dynamic; according to node’s location.

 Two components:
 Home-agent  atributes home-address; mantains mapping to current
location;
 Foreign-agent  atributes care-of-address; informs home-agent.

 Identification:
 Home-Address

 Location:
 Care-of-Address

© Antônio M. Alberti 2011

Mobile IP

© Antônio M. Alberti 2011

2
HIP (Host Identity Protocol)
 Idea:
 New namespace between network and transport layers: Host ID
Layer

Without HIP With HIP

 Identification:
 Host Identifier  Public key as a flat name; provides unique IDs;

 Location:
 IP address.

© Antônio M. Alberti 2011

LISP (Locator ID Separation Protocol)

 Idea:
 Address mapping between edge and core IP networks; IP over
UDP over IP; two IP addresses:
 EIDs (Endpoint Identifiers)  persistent; used as an ID;
 RLOCs (Routing Locators)  used to locate edge routers.

 Two components:
 ITR (Ingress Tunnel Router)  maps EIDs on RLOCs;
 ETR (Egress Tunnel Router)  maps RLOCs on EIDs.

 End Host Identification/Location:

 EIDs

 Edge Router Identification/Location:

 RLOCs

© Antônio M. Alberti 2011

3
LISP (Locator ID Separation Protocol)

© Antônio M. Alberti 2011

MILSA (Mobility and Multihoming Supporting Identifier Locator Split Architecture)

 Idea:
 Separation of trust relations, called domains, and the relations of
connectivity, called zones;
 Separation between signaling and data plan.
 RZBS (Zone Bridging Realm Server) - provides dynamic mapping
between IDs and locators.

 Identification:
 Assigned at domain level;

 Location:
 Assigned at zone level;

© Antônio M. Alberti 2011

4
MILSA (Mobility and Multihoming Supporting Identifier Locator Split Architecture)

Domains

Zones

© Antônio M. Alberti 2011

Akari
 Idea:
 New namespace between network and transport layers: ID Layer.

 Identification:
 By name and/or by identifier (ID) obtained by hash function;
 Legible and unique local names;
 Includes hierachical topology information in global names;

 Location:
 IP, non-IP, post-IP.

© Antônio M. Alberti 2011

5
Akari
Identification

Local Name
+IMS Domain Name

Global Name
Hash Function

ID

Locator
Location
Source: Akari Prpject

© Antônio M. Alberti 2011

MCP (Mobility Control Protocol)

 Idea:
 New namespace between network and transport layers: HID-based
Communication Layer.

 Identification:
 HIDs (Host Identifiers)  hash function of host’s proprietary public
key.
Application/Transport
 Location:
 Two protocols: HID-based Communication
 ADP (Access Delivery Protocol);
 BDP (Backbone Delivery). Network Delivery (ADP/BDP)

© Antônio M. Alberti 2011

6
Comparison

© Antônio M. Alberti 2011

Conclusion
 ID/Loc splitting is one of the most important solutions to address
some of the current Internet limitations.

 Legible names are important to people.

 Approaches need to support post-IP designs.

 We need to evaluate the introduction of new layers.

 We need more holistic and integrated designs:

 To cover relationships among identifiers, names, locators and
routing.
 To improve security and trust.
 To integrate with information ID/Loc splitting.
© Antônio M. Alberti 2011