[OPSAWG] network management data models - a rewrite
Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Thu, 17 November 2011 04:19 UTC
Return-Path: <j.schoenwaelder@jacobs-university.de>
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 84EBC11E8106 for <opsawg@ietfa.amsl.com>; Wed, 16 Nov 2011 20:19:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.193
X-Spam-Level:
X-Spam-Status: No, score=-103.193 tagged_above=-999 required=5 tests=[AWL=0.056, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, 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 KhguFuhJjyQ4 for <opsawg@ietfa.amsl.com>; Wed, 16 Nov 2011 20:19:17 -0800 (PST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 15CFC11E80BB for <opsawg@ietf.org>; Wed, 16 Nov 2011 20:19:17 -0800 (PST)
Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id 6BC2F20D9F for <opsawg@ietf.org>; Thu, 17 Nov 2011 05:19:16 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius2.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id bp2jLIG1n4n6; Thu, 17 Nov 2011 05:19:14 +0100 (CET)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id D69E420DF9; Thu, 17 Nov 2011 05:19:13 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 30D781BB8002; Thu, 17 Nov 2011 05:18:57 +0100 (CET)
Date: Thu, 17 Nov 2011 05:18:57 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: opsawg@ietf.org
Message-ID: <20111117041857.GA25801@elstar.local>
Mail-Followup-To: opsawg@ietf.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="liOOAslEiF7prFVr"
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: [OPSAWG] network management data models - a rewrite
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
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 04:19:22 -0000
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). To be constructive, I have written a replacement for this 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.) /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 <http://www.jacobs-university.de/>
- [OPSAWG] network management data models - a rewri… Juergen Schoenwaelder
- Re: [OPSAWG] network management data models - a r… Romascanu, Dan (Dan)
- Re: [OPSAWG] network management data models - a r… Ersue, Mehmet (NSN - DE/Munich)
- Re: [OPSAWG] network management data models - a r… Christopher LILJENSTOLPE
- Re: [OPSAWG] network management data models - a r… Juergen Schoenwaelder
- Re: [OPSAWG] network management data models - a r… Juergen Schoenwaelder
- Re: [OPSAWG] network management data models - a r… Romascanu, Dan (Dan)
- Re: [OPSAWG] network management data models - a r… Ersue, Mehmet (NSN - DE/Munich)
- Re: [OPSAWG] network management data models - a r… Bert Wijnen (IETF)
- Re: [OPSAWG] network management data models - a r… Juergen Schoenwaelder
- Re: [OPSAWG] network management data models - a r… Randy Presuhn
- Re: [OPSAWG] network management data models - a r… Ersue, Mehmet (NSN - DE/Munich)
- Re: [OPSAWG] network management data models - a r… Benoit Claise
- Re: [OPSAWG] network management data models - a r… t.petch
- Re: [OPSAWG] network management data models - a r… Benoit Claise
- Re: [OPSAWG] network management data models - a r… Juergen Schoenwaelder
- Re: [OPSAWG] network management data models - a r… Benoit Claise
- Re: [OPSAWG] network management data models - a r… Romascanu, Dan (Dan)