[META-MODEL] IETF68 Follow-Up: NE/Facilities/Lines/Protocols/Services Data Modeling

Michael Alexander <malexand@wu-wien.ac.at> Fri, 13 April 2007 18:04 UTC

Return-path: <meta-model-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HcQ8b-0000K8-MD; Fri, 13 Apr 2007 14:04:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HcQ8Z-0000Ey-8Q for meta-model@ietf.org; Fri, 13 Apr 2007 14:04:43 -0400
Received: from ug-out-1314.google.com ([66.249.92.173]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HcQ8Y-0001rJ-M1 for meta-model@ietf.org; Fri, 13 Apr 2007 14:04:43 -0400
Received: by ug-out-1314.google.com with SMTP id 72so486149ugd for <meta-model@ietf.org>; Fri, 13 Apr 2007 11:04:42 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; b=MVG04+pe3Nb/cwu+0Stjoue/iSL4729jlPVSWLcomlo/1TTvdTHv5wQq4kGyVjfafx2at1N4Qz37lUGxUGF4dx8lg9RwkPM1vsst1cqQ1omxqZi86WRbkpAEQKtGj/ZU0OSk07S6XzDU4z51CX24YQ9EbSSQlIGgB0+/rjGOgPs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; b=D/vGKLc0LLS69PRK8NihgLniAx3ELtAj1Gmya9sahZzfqos/6orM9PnNvi0wk4dGZ/YE2k6rs2/aB5myULuKI6CMJDoShnJ9HXKKOxSBhzQlJpIStmoZnA7h/nh1rOthpG/FQ0v2dZrAJ2LiXhnMIhRghZ6vbXNGnKz900pbnnI=
Received: by 10.66.232.11 with SMTP id e11mr2156458ugh.1176487481877; Fri, 13 Apr 2007 11:04:41 -0700 (PDT)
Received: from ?137.208.224.46? ( [137.208.224.46]) by mx.google.com with ESMTP id y37sm5490263iky.2007.04.13.11.04.37; Fri, 13 Apr 2007 11:04:40 -0700 (PDT)
Message-ID: <461FC612.5080606@wu-wien.ac.at>
Date: Fri, 13 Apr 2007 20:04:02 +0200
From: Michael Alexander <malexand@wu-wien.ac.at>
User-Agent: Thunderbird 2.0b2 (Windows/20070116)
MIME-Version: 1.0
To: ops-area@ietf.org, mib2rdml@ietf.org, nmrg@ibr.cs.tu-bs.de, meta-model@ietf.org
References: <AAB4B3D3CF0F454F98272CBE187FDE2F0CA56E57@is0004avexu1.global.avaya.com>
In-Reply-To: <AAB4B3D3CF0F454F98272CBE187FDE2F0CA56E57@is0004avexu1.global.avaya.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc:
Subject: [META-MODEL] IETF68 Follow-Up: NE/Facilities/Lines/Protocols/Services Data Modeling
X-BeenThere: meta-model@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: discussions about a meta data model in the network management space <meta-model.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/meta-model>, <mailto:meta-model-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/meta-model>
List-Post: <mailto:meta-model@ietf.org>
List-Help: <mailto:meta-model-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/meta-model>, <mailto:meta-model-request@ietf.org?subject=subscribe>
Errors-To: meta-model-bounces@ietf.org

In follow-up to the IETF 68 Mini-BOF on 
NE/Facilities/Lines/Protocols/Services Data Modeling:

Effort Summary:
===============

Modeling network of network elements (NE), facilities, lines, protocols 
and services for substantially easing development and operation of 
element manager systems (EMS), network management systems (NMS) and 
operations support systems (OSS). The framework is independent of the 
access method used, including SNMP, CLI, Netconf, Corba, CMIP, XML-RPC, 
etc.)  It covers configuration, alarms, current-historical performance, 
accounting management and security.  The frameworks builds on and reuses 
the existing base of MIBs.

Effort Sub-Projects:
====================

- Namespaces
- Object Model
- Base Meta Model
- Alarm Template Base Meta Model
- Device/Line/Service/Protocol Class Meta Model
- Device/Line/Service/Protocol Type Meta Model
- Device/Line/Service/Protocol Model
- MIB Transformation
- Model Instances three devices, one line type, one protocol and
   one service.

Draft: http://www.ietf.org/internet-drafts/draft-alexan-datamod-00.txt
ppt: http://www3.ietf.org/proceedings/07mar/slides/opsarea-4/opsarea-4.ppt

Next Steps:
===========

This is a complex project which needs the cooperation of multiple foci 
in order to produce meta models and namespaces which very substantially 
decrease the burden of building EMS/NMS/OSSs and model protocols, 
devices etc.

At this stage there has been a fair amount of interest for:

- creating a base meta model (language)
- and to a lesser extent an object model

Skill that is in definite need is for:

- Device Class Specialists: (IP-Router, ATM, SONET/SDH, IP PBX etc.)
- Protocol Specialists: e.g. BGP, OSPF, SIP, MPLS
- Service Specialists: eg. SIP IP Voice

Provided the necessary skill comes together, and a structure is built 
that supports the required interaction for a layered modeling effort, a 
full BoF towards a Data Modeling WG at either at IETF69 or 70 would be 
targeted.


FP7 Filing:
===========

There has been substantial interest from many parties in the filing of 
this as an EU framework project 7 (FP7) project. The targeted filing 
budget sum would exceed EUR 8 Million. The number of participants would 
be >20, and can be from all over the world (NOT only the EU). Please 
send me an email if you or your organization is interested in participating.


Please use the list meta-model@ietf.org for discussion.



Best Regards,

Dr. Michael Alexander
WU Wien Dept. of Information Systems
malexand@wu-wien.ac.at / +43.1.31336.4467 GSM +43.699.1228.3586

_______________________________________________
META-MODEL mailing list
META-MODEL@ietf.org
https://www1.ietf.org/mailman/listinfo/meta-model