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.

Changes between Initial Version and Version 1 of Internal/NetworkManagement/Workingdocuments


Ignore:
Timestamp:
Nov 1, 2010, 8:49:14 PM (13 years ago)
Author:
byrav
Comment:

Initial work package writeup (1.txt)

Legend:

Unmodified
Added
Removed
Modified
  • Internal/NetworkManagement/Workingdocuments

    v1 v1  
     1The goal of the management team involves three high level goals.
     2
     31. Design of an API for the management / control plane of the network. Design of
     4   appropriate access control for various management functions. (Banerjee, UW-Madison + others???)
     5   Why? A lot of new and different components are being proposed in the MobilityFirst
     6   architecture. They include a new fast and scalable naming service, inherent support
     7   for multi-path routing, content caching through a store and forward architecture,
     8   and many others. Any management function requires better visibility into these
     9   new constructs and an efficient API for the management / control plane would be
     10   needed for this.
     11   The API specification needs to come with some way of presenting access control.
     12   Maybe there are secure credentials that need to be shared and made available to
     13   different management agents in the network that needs to be designed.
     14
     15   This is particularly important in considering management issues that span
     16   multiple domains of administrative control, e.g., across enterprises, across
     17   paths through multiple ISPs, etc. There are economic issues that will come into
     18   this design.
     19
     202. Exploration of separation between the control and management planes. (???)
     21   < MORLEY, JIM - DO YOU WANT TO FILL THIS IN>
     22
     233. Client support for management tasks. (Banerjee, UW-Madison)
     24   Why? Mobility is going to be a key part of this future Internet. Mobile devices,
     25   therefore, are first class citizens in this network. A challenge of an infrastructure-only
     26   management structure is that they provide insufficient visibility into performance
     27   problems observed at the clients. However, if the clients are able and willing to
     28   participate in management tasks, that can provide unique vantage points into the
     29   network's overall performance leading to better manageability of the network.
     30
     31
     32Research prototypes, demos, and deliverables:
     33
     341.
     35
     362.
     37
     383. A system for client assisted management implemented on mobile phones. We will present
     39   an infrastructure tied into visual map-based interface that shows network performance
     40   across a wide-area wireless environment. Various performance issues will be automatically
     41   identified in this system that are not possible to recognize without the client-assisted
     42   management part.
     43
     44   The system will include a client-side (Android/iPhone/Windows Mobile) software and associated
     45   cloud based services.