Re: [nmrg] Re: [Research-funding] updates research funding draft

Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de> Thu, 27 November 2003 16:24 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12051 for <research-funding-archive@odin.ietf.org>; Thu, 27 Nov 2003 11:24:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APOvz-000083-3I for research-funding-archive@odin.ietf.org; Thu, 27 Nov 2003 11:24:03 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hARGO3ax000491 for research-funding-archive@odin.ietf.org; Thu, 27 Nov 2003 11:24:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APOvz-00007q-01 for research-funding-web-archive@optimus.ietf.org; Thu, 27 Nov 2003 11:24:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12043; Thu, 27 Nov 2003 11:23:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1APOvx-0002Lq-00; Thu, 27 Nov 2003 11:24:01 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1APOvx-0002Lj-00; Thu, 27 Nov 2003 11:24:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APOvx-00007T-Dw; Thu, 27 Nov 2003 11:24:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APOvq-00007E-EY for research-funding@optimus.ietf.org; Thu, 27 Nov 2003 11:23:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12035 for <research-funding@ietf.org>; Thu, 27 Nov 2003 11:23:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1APOvp-0002La-00 for research-funding@ietf.org; Thu, 27 Nov 2003 11:23:53 -0500
Received: from merkur.iu-bremen.de ([212.201.44.27]) by ietf-mx with esmtp (Exim 4.12) id 1APOvo-0002LE-00 for research-funding@ietf.org; Thu, 27 Nov 2003 11:23:52 -0500
Received: from localhost (localhost [127.0.0.1]) by merkur.iu-bremen.de (Postfix) with ESMTP id 2FFD87C544; Thu, 27 Nov 2003 17:23:18 +0100 (CET)
Received: from james.eecs.iu-bremen.de (unknown [212.201.47.4]) by merkur.iu-bremen.de (Postfix) with ESMTP id B196555E7E; Thu, 27 Nov 2003 17:23:16 +0100 (CET)
Received: by james.eecs.iu-bremen.de (Postfix, from userid 1000) id E265581E8; Thu, 27 Nov 2003 17:23:14 +0100 (CET)
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: Sally Floyd <floyd@icir.org>
Cc: research-funding@ietf.org, nmrg@ibr.cs.tu-bs.de, iab@iab.org, Ran Atkinson <rja@extremenetworks.com>
Subject: Re: [nmrg] Re: [Research-funding] updates research funding draft
Message-ID: <20031127162314.GA2980@iu-bremen.de>
Reply-To: j.schoenwaelder@iu-bremen.de
Mail-Followup-To: Sally Floyd <floyd@icir.org>, research-funding@ietf.org, nmrg@ibr.cs.tu-bs.de, iab@iab.org, Ran Atkinson <rja@extremenetworks.com>
References: <200310202011.h9KKBKGa047443@cougar.icir.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200310202011.h9KKBKGa047443@cougar.icir.org>
User-Agent: Mutt/1.5.4i
X-Virus-Scanned: by AMaViS 0.3.12pre8
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/mail-archive/working-groups/research-funding/>
Date: Thu, 27 Nov 2003 17:23:14 +0100

On Mon, Oct 20, 2003 at 01:11:20PM -0700, Sally Floyd wrote:

[...]

> * The subsection on Autonomous Network Management, originally from
> draft-iab-research-funding-01.txt, was deleted from
> draft-iab-research-funding-02.txt in the interests of shortening
> the Network Management section.
 
> * The subsection on "Configuration Management", originally from
> draft-iab-research-funding-01.txt, was also deleted in the interests of
> shortening the Network Management section.
 
> * The new material in the NRMG's subsection on "Customer Network
> Management" is the last paragraph, and this material was not included.
> Some of that paragraph is more detailed than is needed for this
> document, in terms of the specific needs of customer network
> management mechanisms.

I have now looked at both versions again and I want to provide one 
more time some feedback. I have had issues with the section titled
"Application of Expert Systems to Network Management" in the past and 
some of our proposed text was written to overcome the problem. Let me 
explain...

The first paragraph in this section is about what we people in the
community typically call Customer Network Management. This paragraph 
has in my view nothing to do with expert systems per se. And this 
motived us to move the text into a subsection titled Customer Network 
Management in the proposal we submitted earlier. You have decided to 
cut this section and you have moved the text back into the expert system
section where I think it is somewhat misplaced. (Or is the intention to
say that expert systems are the way to produce meaningful explanations
for users? But then again is that not too specific?)

The second issue I have is that the second paragraph stresses expert 
systems (which is a technique) while the underlying goal is what people
call autonomous network management.  In fact, if you look at NM research 
publications, then quite some papers were written in the early 90s about 
expert systems in network management. But nothing ground breaking has
appeared in this area for quite some years now. If you look at more
recent NM research publications, you will notice that more substantial
research comes from the application of control theory concepts to NM.
Hence, I would feel much more comfortable if the text would have been
written to stress the goal (autonomous network management) and just
names some techniques to get there, among them being expert systems,
other AI techniques or classic control theory. This was the reason
for use to propose the section on "Autonomous Network Management"
which did not make it into the current revision.

To illustrate this, here is another concrete proposal for changes, 
basically to rework and split section 3.5.3.:

OLD:

3.5.3.  Application of Expert Systems to 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 that some other specific event
   occurred.

   It would be useful to examine whether expert systems technology or
   artificial intelligence technology could be used to enhance network
   management systems, reducing the operational burden created by the
   network and improving scalability.

NEW:

3.5.3.  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 that some other specific event
   occurred.


3.5.4.  Autonomous Network Management

   More research is needed to improve the degree of automation achieved
   by network management systems and to localize management. Autonomous
   network management might involve the application of control theory,
   artificial intelligence or expert system technologies to network
   management problems.

This new text is roughly the same number of words so this change does not
expand the network management section. Of course, I personally find it
a pity that configuration management is not mentioned in the document 
even though it practically seems to be a real big issue. But I understand 
that this document can only touch selected issues.

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany

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