FLAT ADDRESS AND MOBILITY FIRST

"New features like mobility, multi-homing, security and inter-networking among heterogeneous network domains are challenging the current Internet architecture. The service offered today, provides end-to-end communication using a global and hierarchical addressing space , i.e., unique IP address for both localization and identification functions. A common view present in the current literature is that an homogeneous inter-networking protocol as represented today by the IP protocol is no more convenient for supporting the introduction of new services.Requirements for mobility and security emphasize the need of a new inter-networking architecture."

---

The main points to make a new approach for the Internet architecture viable are

• Separation of identity and localization
• The creation of overlay networks for introducing new control plane
  • Address Allocation
  • Routing
  • Name Resolution
• The adoption of new routing strategies for these overlay networks

Use cases that drive this new architecture

Along with above mentioned points, we may also want to look at the use cases that might guide us in design process

1. MULTI-HOMING

This refers to the scenario where-in the end device may come with multi-home capability i.e., interfaces for different technologies on same device . This implies a requirement to support

---

MOBILITY FIRST

1. GNRS (Global Name Resolution Service)- To address the separation of identity and location

• Each node in the network shall be assigned a GUID (Globally Unique ID), that shall serve as the unique identity of the node.
• This GUID is associated with current network reachability information of the node
• This serves to separate addressing from location => support for mobility
• GNRS functionality is attained using Distributed system ( DHT)

Q

• Who assigns these GUID ?
• Levels of GNRS required ? => Only Local and Global ?
• Is this a service of control plane ?

---

2. Routing