STUDY 01 - FLAT ADDRESS AND ROUTING

" This section shall provide an overview on the literature study in the domain of using flat address for routing. It shall begin with the requirements of Mobility First Architecture and then extend to an overview on each of the related literature currently available. "

---

MOBILITY FIRST AND FLAT ADDRESS

• Problems with present Internet Architecture
  • Need to assign address based on topological location
  • Inter domain routing

---

APPROACH 01 - HAIR

HAIR Hierarchical Architecture for Internet Routing

• Routing table growth
• Restrict visibility of Routing updates
• Support Traffic Engineering
• Mobility and Multipath

Edge Based Approach

N layer -Hierarchial Structure :

Today’s Internet consists of a stable “core”, formed by large transit providers, and a more dynamic edge,consisting of enterprise networks or small access providers.The typical Internet cost structure together with peering policies ensures that the number of links between an “edge” network and the “core” is limited. Most “edge” networks have a small number of upstream providers in the “core” and typically, due to costs, do not have too many upstream links to a single provider.

*	Group core networks into level 1 of a hierarchy, edge or intermediate networks into levels 2 to n − 1, and local area networks into level n, obtaining a hierarchy consisting of n levels

EDGE

• This would refer to level -n ( directly interact with the end hosts. (bottom layer of hierarchy) [ Ethernet LAN]

INT

• This is the intermediate level ( 2 to n-1).
• Network of routers only
• It provides routing between attached EDGEs or INTs of the next higher level.

CORE

• Ensures global reachability by routing packets between INTs (level-2)

• Levels are connected via attachment points : a level -k (LkAP) connects level k routing domain to level k+1 one.
• Allows peering

---

Routing Tables

Within a INT

• Need entries for all routers within the INT,
• Routes to the attached EDGEs/INTs,
• Default routes to the INTs of the next higher level or the CORE

Within a CORE

• All routers within CORE
• Routes to directly connected ISPs

---

LOCATION/IDENTIFIER SEPARATION

• Separation of location and identity
• locators are variable length ( to allow core towards end host)

Note | Use GUID