[Research-funding] Re: [nmrg] network management research funding text

Frank Strauß <strauss@ibr.cs.tu-bs.de> Wed, 09 July 2003 21:06 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22212 for <research-funding-archive@odin.ietf.org>; Wed, 9 Jul 2003 17:06:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aM8Z-0004kk-B2 for research-funding-archive@odin.ietf.org; Wed, 09 Jul 2003 17:06:04 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h69L63Ns018266 for research-funding-archive@odin.ietf.org; Wed, 9 Jul 2003 17:06:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aM8Z-0004kX-7j for research-funding-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 17:06:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22178; Wed, 9 Jul 2003 17:05:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aM8W-0003UC-00; Wed, 09 Jul 2003 17:06:00 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aM8W-0003U6-00; Wed, 09 Jul 2003 17:06:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aM8X-0004kH-3f; Wed, 09 Jul 2003 17:06:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aL1a-0007jy-It for research-funding@optimus.ietf.org; Wed, 09 Jul 2003 15:54:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18330 for <research-funding@ietf.org>; Wed, 9 Jul 2003 15:54:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aL1Y-0002YQ-00 for research-funding@ietf.org; Wed, 09 Jul 2003 15:54:44 -0400
Received: from agitator.ibr.cs.tu-bs.de ([134.169.34.18]) by ietf-mx with esmtp (Exim 4.12) id 19aL1X-0002YL-00 for research-funding@ietf.org; Wed, 09 Jul 2003 15:54:43 -0400
Received: from ibr.cs.tu-bs.de (dagoba.ibr.cs.tu-bs.de [134.169.34.107]) (authenticated bits=0) by agitator.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian-6.4) with ESMTP id h69JsaKb018869 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Wed, 9 Jul 2003 21:54:37 +0200
Message-ID: <3F0C72EF.50805@ibr.cs.tu-bs.de>
From: =?ISO-8859-15?Q?Frank_Strau=DF?= <strauss@ibr.cs.tu-bs.de>
Organization: IBR, TU Braunschweig, Germany
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: de, en-us, en
MIME-Version: 1.0
To: j.schoenwaelder@iu-bremen.de
CC: research-funding@ietf.org, nmrg@ibr.cs.tu-bs.de
References: <20030708093936.GA1287@iu-bremen.de>
In-Reply-To: <20030708093936.GA1287@iu-bremen.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-IBRFilter-SpamReport: -32.2 () EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, REPLY_WITH_QUOTES, USER_AGENT_MOZILLA_UA
X-Scanned-By: MIMEDefang 2.24 (www . roaringpenguin . com / mimedefang)
Content-Transfer-Encoding: 7bit
Subject: [Research-funding] Re: [nmrg] network management research funding text
Sender: research-funding-admin@ietf.org
Errors-To: research-funding-admin@ietf.org
X-BeenThere: research-funding@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/research-funding>, <mailto:research-funding-request@ietf.org?subject=unsubscribe>
List-Id: draft-iab-research-funding feedback <research-funding.ietf.org>
List-Post: <mailto:research-funding@ietf.org>
List-Help: <mailto:research-funding-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/research-funding>, <mailto:research-funding-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/research-funding/>
Date: Wed, 09 Jul 2003 21:54:23 +0200
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Juergen Schoenwaelder wrote:

> Below is some text for section 3.5 of the IAB research funding draft.
> I basically took the text from <draft-iab-research-funding-01.txt>
> and rearranged it and added a few pieces here and there. I understand
> that the idea is to not be comprehensive and so I tried hard to not
> add lots of additional research topics people actually work on.
> 

Thanks for picking this document up again! Here are some additional
comments...

> ------------------------------------------------------------------------
> 
> 3.5.  Network Management
> 
>    The Internet had early success in network device monitoring with
>    the Simple Network Management Protocol (SNMP) and its associated
>    Management Information Base (MIB).  There has been comparatively
>    less success in managing networks, in contrast to the hierarchical

What do you mean by "hierarchical"? How about just removing this word?

>    monitoring of individual devices. Furthermore, there are a number
>    of operator requirements not well supported by the current Internet
>    management framework.  An enhanced network management architecture
>    that more fully supports real operational network management needs
>    is desirable.
> 
>    Unfortunately, network management research has historically been
>    very underfunded, because it is difficult to get funding bodies to
>    recognize this as legitimate networking research.
> 
> 3.5.1.  Managing Networks, Not Devices
> 
>    At present, there are few or no good tools for managing a whole
>    network of instead of isolated devices. Current network management
              ^^
>    protocols such as SNMP are fine for reading status of well-defined
>    objects from individual boxes. But managing networks instead of
>    isolated devices requires to view the network as a large
>    distributed system. Research is needed on scalable distributed data
>    aggregation mechanisms, scalable distributed event correlation
>    algorithms, and distributed and dependable control mechanisms.
> 
>    Applied research into methods of managing sets of networked devices
>    seems worthwhile.  Ideally such a management approach would support
>    distributed management, rather than being strictly hierarchical.
> 
>    As an example, the current set of network management tools for
>    managing multimedia (voice and video) IP networks is inadequate, and
>    research would be useful in this area.  The lack of appropriate
>    network management tools has also been cited as one of the major
>    barriers to the deployment of IP multicast [Diot00, SP03].
> 
> 3.5.2.  Configuration Management
> 
>    Operators at the IAB Network Management Workshop [RFC-3535] held in
>    2002 reported that scalable distributed configuration management
>    for sets of network devices is a significant challenge today.  In
>    particular, it is desirable to execute configuration transactions
>    across a number of connected devices, which requires protocols that
>    support distributed transactions.  Furthermore, configuration data
>    should be represented in a way which simplifies the processing and
>    generation of configurations with standard tools.
> 
>    Even individual improvements in configuration management for sets
>    of networked devices would be very welcome.  Such improvements
>    would need to include an integrated approach to security for the
>    configuration data.

I think there is quite some overlap with aspects already explained in
3.5.1. However, I regard it reasonable to differentiate what the
titles of both subsections denote. (Sorry, I have to concrete suggestion
for a change.)

> 3.5.3.  Enhanced Monitoring Capabilities
> 
>    SNMP does not scale very well to monitoring large numbers of
>    objects in many devices in different parts of the network.  Some
>    implementations also show inaccuracies (especially when monitoring
>    on shorter time scales) or they lack support for the objects that
>    operators are interested in. An alternative approach worth
>    exploring is how to provide scalable and distributed monitoring,
>    not on individual devices, but instead on groups of devices and
>    networks-as-a-whole.

Sorry, I cannot imagine what you mean by monitoring a network here?
Wouldn't that be comprised of monitoring multiple individual devices
combined with adequate correlation/aggregation? (I don't mind to go
into discussions on solutions on this forum.)

> 3.5.4.  Improving the Scalability of Network Management
> 
>    Current approaches to network management do not scale sufficiently,
>    so network operators often have difficulty operating their
>    network(s) as successfully and economically as desired.  Hence,
>    more work is needed to improve the scalability of network
>    management systems.  This might involve application of control
>    theory, artificial intelligence, expert systems technology, or
>    other mechanisms, for example.

Again some degree of overlap with 3.5.1, I think.

> 3.5.5. Customer Network Management
> 
>    An open issue related to network management is helping users and
>    others to identify and resolve problems in the network.  If a user
>    can't access a web page, it would be useful if the user could find
>    out, easily, without having to run ping and traceroute, whether the
>    problem was that the web server was down, that the network was
>    partitioned due to a link failure, that there was heavy congestion
>    along the path, that the DNS name couldn't be resolved, that the
>    firewall prohibited the access, or something else.  

I think this paragraph misses a final sentence, just stating what kind
of research is required to address this well described problem.


Maybe, we should have a subsection to address research not only on what
new ideas should be evolved in the future but also on what we have to
better understand about the past. The plans on NM traffic measurements
we had during recent NMRG meetings belong to this kind of research.
Sorry, again no concrete proposal yet.



_______________________________________________
Research-funding mailing list
Research-funding@ietf.org
https://www1.ietf.org/mailman/listinfo/research-funding