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

Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de> Tue, 15 July 2003 14:54 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 KAA22810 for <research-funding-archive@odin.ietf.org>; Tue, 15 Jul 2003 10:54:55 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cRCF-0001xM-9f for research-funding-archive@odin.ietf.org; Tue, 15 Jul 2003 10:54:27 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6FEsRT0007512 for research-funding-archive@odin.ietf.org; Tue, 15 Jul 2003 10:54:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cRCF-0001x4-4m for research-funding-web-archive@optimus.ietf.org; Tue, 15 Jul 2003 10:54:27 -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 KAA22777; Tue, 15 Jul 2003 10:54:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cRC7-0002eg-00; Tue, 15 Jul 2003 10:54:19 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19cRC1-0002eY-00; Tue, 15 Jul 2003 10:54:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cRBp-0001wa-BL; Tue, 15 Jul 2003 10:54:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cRBG-0001vx-Pg for research-funding@optimus.ietf.org; Tue, 15 Jul 2003 10:53:26 -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 KAA22738 for <research-funding@ietf.org>; Tue, 15 Jul 2003 10:53:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cRB9-0002eM-00 for research-funding@ietf.org; Tue, 15 Jul 2003 10:53:19 -0400
Received: from [81.160.180.141] (helo=james) by ietf-mx with esmtp (Exim 4.12) id 19cRAy-0002eF-00 for research-funding@ietf.org; Tue, 15 Jul 2003 10:53:08 -0400
Received: by james (Postfix, from userid 1000) id 5A3C084B9; Tue, 15 Jul 2003 16:52:50 +0200 (CEST)
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: Frank Strau? <strauss@ibr.cs.tu-bs.de>
Cc: research-funding@ietf.org, nmrg@ibr.cs.tu-bs.de
Message-ID: <20030715145250.GC757@iu-bremen.de>
Reply-To: j.schoenwaelder@iu-bremen.de
Mail-Followup-To: Frank Strau? <strauss@ibr.cs.tu-bs.de>, research-funding@ietf.org, nmrg@ibr.cs.tu-bs.de
References: <20030708093936.GA1287@iu-bremen.de> <3F0C72EF.50805@ibr.cs.tu-bs.de> <20030710083253.GC660@iu-bremen.de> <3F12952C.50003@ibr.cs.tu-bs.de>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="qDbXVdCdHGoSgWSk"
Content-Disposition: inline
In-Reply-To: <3F12952C.50003@ibr.cs.tu-bs.de>
User-Agent: Mutt/1.5.4i
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: Tue, 15 Jul 2003 16:52:50 +0200

On Mon, Jul 14, 2003 at 01:34:04PM +0200, Frank Strau? wrote:
 
> I agree that there are different intentions to be expressed by the
> two sections (and by any of the other sections). Just reading the text
> from a certain distance (like potential people that are addressed by
> this document) lets me think that there are some common arguments.
> The same is true for my initial comment on 3.5.4.

Any concrete proposals for changes?

> >3.5.4.  Autonomous Network Management
> >
> >   Current approaches to network management do not scale sufficiently,
> >   so network operators often have difficulty operating their
> 
>                                                ^ plural?

fixed
 
> >   network(s) as successfully and economically as desired.  Hence,
> >   more work is needed to improve the automation achieved by network
> >   management systems.  This might involve application of control
> >   theory, artificial intelligence, expert systems technology, or
> >   other mechanisms, for example.
> 
> Either "or other mechanisms" or "for example", not both, I suggest.

fixed
 
> >   Applied research is needed how to translate data that exists in a
> >   network or a network management system into terms understandable by
> >   customers. This also requires to be able to determine which
> >   customers are affected and how if something breaks. Of course,
> >   customer network management mechanisms must not reveal any
> >   internals that are considered to be secrets of organization
> 
>                                                      ^the

fixed
 
> >   operating a network.
> 
> Sounds good to me.

[...]
 
> Ok. How do you think about this...?
> 
> Analysis of Current Network Management Application
> 
> In the past much work has been spent on the specification and
> implementation of a network management architecture. However, most
> administrators use far less components of this architecture than
> possible. There are only vague estimations about the reasons for
> this reluctance. A better understanding of what is used for which
> purpose and what is not for which reasons is highly disirable.
> This can be done by an automated analysis of network management
> protocol traffic and applications at operators' sites and enhanced
> by additional conversations with the operators.

What about this rewrite:

3.5.6 Analysis of Current Management Protocol Usage

   In the past, much work has been spent on the specification and
   implementation of the current Internet network management
   architecture. However, operators reported that they use only a
   subset of this architecture.  A better understanding of what is
   used for which purpose (and what is not used) is highly desirable.
   This issue can be addressed by automated network management
   protocol traffic measurements and subsequent analysis in close
   cooperation with operators.

[Attached is the complete current version.]

/js

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