Re: [OPSAWG] network management data models - a rewrite

"Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com> Thu, 17 November 2011 06:17 UTC

Return-Path: <mehmet.ersue@nsn.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F03C221F90F2 for <opsawg@ietfa.amsl.com>; Wed, 16 Nov 2011 22:17:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.573
X-Spam-Level:
X-Spam-Status: No, score=-106.573 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EZXnbAzQ4rpP for <opsawg@ietfa.amsl.com>; Wed, 16 Nov 2011 22:17:48 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id C371621F979D for <opsawg@ietf.org>; Wed, 16 Nov 2011 22:17:47 -0800 (PST)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id pAH6HjiH013897 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 17 Nov 2011 07:17:46 +0100
Received: from DEMUEXC048.nsn-intra.net ([10.159.32.94]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id pAH6HjHw008306; Thu, 17 Nov 2011 07:17:45 +0100
Received: from DEMUEXC006.nsn-intra.net ([10.150.128.18]) by DEMUEXC048.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675); Thu, 17 Nov 2011 07:17:45 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 17 Nov 2011 07:17:44 +0100
Message-ID: <80A0822C5E9A4440A5117C2F4CD36A640301A26B@DEMUEXC006.nsn-intra.net>
In-Reply-To: <20111117041857.GA25801@elstar.local>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [OPSAWG] network management data models - a rewrite
Thread-Index: Acyk4BfDtLLjahf4SD2ftcdCWd2wAwADLafg
References: <20111117041857.GA25801@elstar.local>
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, opsawg@ietf.org
X-OriginalArrivalTime: 17 Nov 2011 06:17:45.0724 (UTC) FILETIME=[9F37C3C0:01CCA4F0]
Subject: Re: [OPSAWG] network management data models - a rewrite
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Nov 2011 06:17:52 -0000

Dear Juergen,

thank you for your contribution. It is valuable and fits the discussion 
in the OPSAWG session for the second view in the document.

> Hi,
> 
> draft-ietf-opsawg-management-stds-02 has a section on "Network
> Management Data Models" which is structured around FCAPS which I
> happen to dislike for several reasons (data model work in the IETF is
> not organized around FCAPS, the discussion is constantly changing
> abstraction levels, some of the examples picked are somewhat
> surprising). 

Please comment on the examples you find as not suitable.

> To be constructive, I have written a replacement for this

As discussed and agreed in the OPSAWG session (by the persons in the 
session; unfortunately you were not in the meeting room at that time) 
the best approach is to have both views in the document. 

> section that I think better summarizes what the IETF has to offer and
> how data modeling work happens to be done in the IETF. In addition, it
> is also shorter.
> 
> I do not mind if my proposed rewrite is followed by a section
> discussing how all this fits into an FCAPS view of the world but such
> a section should be much shorter and different from what is in the
> current section 4. (For me, a short explanation that the IETF does not
> organize data models around FCAPS is really sufficient but I guess
> Mehmet and Benoit might not agree with that.)

>From the very first version of the draft our aim was to provide a
detailed 
data model survey as a guidance for the audience outside of the IETF. 
The survey can be for sure tuned or optimized as necessary. However,
we should strive for a publishing soon rather than having more cycles.

Mehmet