| | 1 | || ''' MOBILITY FIRST : '''NOTE - 01|| |
| | 2 | ---- |
| | 3 | |
| | 4 | ||''' NEW ARCHITECTURE ''' || |
| | 5 | The main points to make a new approach for the Internet architecture viable are |
| | 6 | * '''Separation of identity and localization''' |
| | 7 | * The creation of overlay networks for introducing '''new control plane''' |
| | 8 | * Address Allocation |
| | 9 | * Routing |
| | 10 | * Name Resolution |
| | 11 | * The adoption of '''new routing strategies''' for these overlay networks |
| | 12 | |
| | 13 | ---- |
| | 14 | ||'''Use cases '''|| |
| | 15 | Along with above mentioned points, we may also want to look at the use cases that might guide us in design process |
| | 16 | |
| | 17 | 1. ''' MULTI-HOMING ''' |
| | 18 | 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. |
| | 19 | |
| | 20 | ||'''Q'''|| |
| | 21 | |
| | 22 | * '''Use "Multi-homed" gateways for -''' |
| | 23 | * Address Translation and |
| | 24 | * Protocol Translation between two domains ? |
| | 25 | * Binding interface information to '''GUID ''' => Authentication? |
| | 26 | * '''Selection of interface by network''' ? |
| | 27 | |
| | 28 | ---- |
| | 29 | 2. ''' HOST MOBILITY ''' |
| | 30 | Support for host mobility requires - |
| | 31 | * dynamic binding of end host to network when connection point to network changes |
| | 32 | * Redirection of in-transit packet without support from specific entity |
| | 33 | * Support parallel binding to multiple networks --- (GUID : NA Mapping) |
| | 34 | * Frequency of updates (GUID:NA) => '''Network sensitivity to change''' |
| | 35 | |
| | 36 | ---- |
| | 37 | 3. '''NETWORK MOBILITY''' |
| | 38 | |
| | 39 | |
| | 40 | ---- |
| | 41 | 4. '''STRANGE COMMUNICATION SCENARIOS''' |
| | 42 | This section includes but is not limited to |
| | 43 | * vehicular communication, |
| | 44 | * Personal area networks, |
| | 45 | * Military communication and |
| | 46 | * Disaster recovery systems |
| | 47 | |
| | 48 | ||Q|| |
| | 49 | * What are the requirements? |
| | 50 | * How to attain considerable uniformity in network design ? |
| | 51 | |
| | 52 | |
| | 53 | ---- |
| | 54 | |
| | 55 | || ''' MOBILITY FIRST '''|| |
| | 56 | |
| | 57 | ''' 1. GNRS '''(Global Name Resolution Service)- '''To address the separation of identity and location ''' |
| | 58 | * Each node in the network shall be assigned a '''GUID''' (Globally Unique ID), that shall serve as the '''unique''' identity of the node. |
| | 59 | * This '''GUID''' is associated with current network reachability information of the node |
| | 60 | * This serves to separate addressing from location => support for '''mobility''' |
| | 61 | * '''GNRS''' functionality is attained using Distributed system ( '''DHT''') |
| | 62 | |
| | 63 | ||''' Q '''|| |
| | 64 | * Who assigns these '''GUID''' ? |
| | 65 | * Levels of '''GNRS''' required ? => '''Only Local and Global '''? |
| | 66 | ----- |
| | 67 | |
| | 68 | ''' 2. Routing ''' |
| | 69 | '''GSTAR''' (Global Storage Aware Routing) Features - |
| | 70 | * Delay Tolerance |
| | 71 | * Storage Aware |
| | 72 | * Decisions based on link quality |
| | 73 | |
| | 74 | Currently the above are hinted to be used for intra-domain routing. |
| | 75 | There is a need for attaining routing on flat address : '''GUID ?''' |
