[nmrg] smiv2/sppi/sming integration meeting
Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de> Mon, 21 August 2000 10:06 UTC
Return-Path: <owner-nmrg@ibr.cs.tu-bs.de>
Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) id MAA16809 for nmrg-outgoing; Mon, 21 Aug 2000 12:06:42 +0200 (MET DST)
Received: from henkell.ibr.cs.tu-bs.de (schoenw@henkell [134.169.34.191]) by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) with ESMTP id MAA16740; Mon, 21 Aug 2000 12:06:36 +0200 (MET DST)
Received: from schoenw@localhost by henkell.ibr.cs.tu-bs.de (8.7.6/tubsibr) id MAA16810; Mon, 21 Aug 2000 12:06:36 +0200
Date: Mon, 21 Aug 2000 12:06:36 +0200
Message-Id: <200008211006.MAA16810@henkell.ibr.cs.tu-bs.de>
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: Network Management Research Group <nmrg@ibr.cs.tu-bs.de>
Subject: [nmrg] smiv2/sppi/sming integration meeting
Sender: owner-nmrg@ibr.cs.tu-bs.de
Precedence: bulk
Status: O
Content-Length: 2264
Lines: 55
During the IETF meeting in Pittsburgh, many people expressed that it is valuable to merge SMIv2/SMIng/SPPI into a single next generation data definition language to be used at least with SNMP and COPS, but perhaps also with DIAMETER and other protocols which separate data definitions from the protocol itself. There is also a NIM requirements document which identifies language features that are considered important by the "modeling experts". I got the impression that the time has come to seriously dive into the details and to find out whether we can come up with a language proposal which can actually reduce the number of languages in use within the IETF for defining data models. In order to move forward quickly, I am organizing a meeting next month to address this issue. Here are the logistic details as known right now: Date: September 6-8 (Wednesday-Friday) Place: Frankfurt, Germany Host: <under discussion> Some people who are not members of the NMRG are likely to attend this meeting in order to get additional subject matter experts involved. This meeting is intended to dive into the technical details. For this to be possible, I expect that participants are well prepared and are willing to work effectively towards the stated goal of the meeting. In particular, I expect participants to be familiar with the following documents: - SMIv2 as defined in RFC 2578-2580 - SMIng as defined in <draft-irtf-nmrg-sming-02.txt> - SPPI as defined in <draft-ietf-rap-sppi-01.txt> - NIM requirements as described in <draft-durham-nim-req-01.txt> Participants should also understand the SNMP and COPS-PR protocols. Knowledge in other related areas (e.g. diameter, other data definition languages, mappings between data definition languages) is of course helpful and welcome. If you plan to attend, then please drop me a note as soon as possible so that I can better plan ahead and inform the local host about the meeting facilities we actually need. /js -- Juergen Schoenwaelder Technical University Braunschweig <schoenw@ibr.cs.tu-bs.de> Dept. Operating Systems & Computer Networks Phone: +49 531 391 3289 Bueltenweg 74/75, 38106 Braunschweig, Germany Fax: +49 531 391 5936 <URL:http://www.ibr.cs.tu-bs.de/~schoenw/>
- Re: [nmrg] smiv2/sppi/sming integration meeting Juergen Schoenwaelder
- Re: [nmrg] smiv2/sppi/sming integration meeting Juergen Schoenwaelder
- RE: [nmrg] smiv2/sppi/sming integration meeting David T. Perkins
- RE: [nmrg] smiv2/sppi/sming integration meeting David T. Perkins
- RE: [nmrg] smiv2/sppi/sming integration meeting Andrea Westerinen
- [nmrg] smiv2/sppi/sming integration meeting Juergen Schoenwaelder