wiki:Internal/SummerInternship/Logs/SangeethaSiddegowda
close Warning: Can't synchronize with repository "(default)" ("(default)" is not readable or not a Git repository.). Look in the Trac log for more information.

Version 14 (modified by sansid, 13 years ago) ( diff )

--

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 location 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. In an attempt to overcome this problem, we could route directly on host identifiers themselves, eliminating the need for network-layer protocols to include any information on location. The key to achieving this is the ability to route on flat address ."


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

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 multiple interface.

Q
  • Use "Multi-homed" gateways for -
    • Address Translation and
    • Protocol Translation between two domains ?
  • Binding interface information to GUID => Authentication?
  • Selection of interface by network ?

  1. HOST MOBILITY

Support for host mobility requires -

  • dynamic binding of end host to network when connection point to network changes
  • Redirection of in-transit packet without support from specific entity
  • Support parallel binding to multiple networks --- (GUID : NA Mapping)
  • Frequency of updates (GUID:NA) => Network sensitivity to change

  1. NETWORK MOBILITY


  1. VEHICULAR COMMUNICATION

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 ?

2. Routing GSTAR (Global Storage Aware Routing) Features -

  • Delay Tolerance
  • Storage Aware
  • Decisions based on link quality Currently the above are limited to intra-domain routing There is a need for attaining routing on flat address : GUID ?

This implies a need for


  • Disclaimer : This is just a log of my study ...

Attachments (2)

Download all attachments as: .zip

Note: See TracWiki for help on using the wiki.