Return-Path: Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) id LAA16509 for nmrg-outgoing; Thu, 4 Nov 1999 11:25:19 +0100 (MET) 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 LAA16500; Thu, 4 Nov 1999 11:25:15 +0100 (MET) Received: from schoenw@localhost by henkell.ibr.cs.tu-bs.de (8.7.6/tubsibr) id LAA17652; Thu, 4 Nov 1999 11:25:15 +0100 Date: Thu, 4 Nov 1999 11:25:15 +0100 Message-Id: <199911041025.LAA17652@henkell.ibr.cs.tu-bs.de> From: Juergen Schoenwaelder To: dthaler@Exchange.Microsoft.com CC: nmrg@ibr.cs.tu-bs.de In-reply-to: <199911041017.LAA23102@henkell.ibr.cs.tu-bs.de> (dthaler@Exchange.Microsoft.com) Subject: Re: [nmrg] MIB<->MOF conversion References: <199911041017.LAA23102@henkell.ibr.cs.tu-bs.de> Sender: owner-nmrg@ibr.cs.tu-bs.de Precedence: bulk >>>>> Dave Thaler (Exchange) writes: Dave> I've asked around here at Microsoft, and found that we already Dave> ship a SMI->MOF conversion tool in the WMI SDK which I'm told Dave> retains all information except for the named nodes (e.g. system Dave> OBJECT IDENTIFIER ::= { mib-2 1 } ) which do not add to the Dave> schema. (WMI is the name of the Windows implementation of CIM.) Can you find out if there is a specification for this SMI to CIM mapping? Dave> Regarding MOF->SMI conversion, there is no current tool we know Dave> of, but the person I exchanged email with said: >> a CIM to MIB will work, however the encoding strategy is going to >> be cumbersome. The bigger problem is the efficient encoding of the >> operational semantics of WMI and how it maps onto the SNMP >> protocol. Yes, mapping CIM methods will be hard without operations in SMIvX. /js Return-Path: Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) id LAA16062 for nmrg-outgoing; Thu, 4 Nov 1999 11:17:45 +0100 (MET) 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 LAA16057 for ; Thu, 4 Nov 1999 11:17:44 +0100 (MET) Received: from schoenw@localhost by henkell.ibr.cs.tu-bs.de (8.7.6/tubsibr) id LAA23102; Thu, 4 Nov 1999 11:17:44 +0100 Message-Id: <199911041017.LAA23102@henkell.ibr.cs.tu-bs.de> From: "Dave Thaler (Exchange)" To: "'nmrg@ibr.cs.tu-bs.de'" Subject: [nmrg] MIB<->MOF conversion Date: Wed, 3 Nov 1999 09:58:35 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-nmrg@ibr.cs.tu-bs.de Precedence: bulk >From the Zurich meeting notes: > An interesting work item might therefore be the mapping between > CIM and SMIv2 / SMI-ng. Dave will try to find if there is already > material on that. I've asked around here at Microsoft, and found that we already ship a SMI->MOF conversion tool in the WMI SDK which I'm told retains all information except for the named nodes (e.g. system OBJECT IDENTIFIER ::= { mib-2 1 } ) which do not add to the schema. (WMI is the name of the Windows implementation of CIM.) Regarding MOF->SMI conversion, there is no current tool we know of, but the person I exchanged email with said: > a CIM to MIB will work, however the encoding strategy is going > to be cumbersome. The bigger problem is the efficient encoding > of the operational semantics of WMI and how it maps onto the > SNMP protocol. -Dave Return-Path: Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) id QAA06515 for nmrg-outgoing; Wed, 3 Nov 1999 16:09:56 +0100 (MET) 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 QAA06372; Wed, 3 Nov 1999 16:07:34 +0100 (MET) Received: from schoenw@localhost by henkell.ibr.cs.tu-bs.de (8.7.6/tubsibr) id QAA13710; Wed, 3 Nov 1999 16:07:16 +0100 Date: Wed, 3 Nov 1999 16:07:16 +0100 Message-Id: <199911031507.QAA13710@henkell.ibr.cs.tu-bs.de> From: Juergen Schoenwaelder To: kzm@cisco.com, abierman@cisco.com, dlevi@nortelnetworks.com, dperkins@snmpinfo.com, rpresuhn@dorothy.peer.com, dbh@cabletron.com, case@snmp.com, sar@epilogue.com, saperia@mediaone.net, nmrg@ibr.cs.tu-bs.de In-reply-to: <199910261500.RAA06436@henkell.ibr.cs.tu-bs.de> (message from Juergen Schoenwaelder on Tue, 26 Oct 1999 17:00:58 +0200) Subject: Re: [nmrg] NMRG meeting Washington (46th IETF) References: <199910261500.RAA06436@henkell.ibr.cs.tu-bs.de> Sender: owner-nmrg@ibr.cs.tu-bs.de Precedence: bulk Here are some more details concerning the NMRG meeting in Washington. We actually managed to organize two meeting slots: (1) The first one is on Sunday evening at 7pm after the IETF reception. The meeting room is not yet finalized. We therefore plan to meet after the reception at the message board. We will leave a message on the board in case someone arrives late. (2) The second one is on Monday in the room Cabinet from 1:00 pm to 3:00 pm. This meeting slot conflicts with the following IETF WGs: calsch, vpim, dnsind, ospf, ipsec, tsvwg, uswg. We can decide on Sunday whether we need this second meeting slot and how we want to split things up. You can find this and some additional information on the NMRG web page at . The meeting will be chaired by David Harrington. (I actually only have his confirmation for Sunday evening. But we will be flexible anyway.) Have a nice trip to Washington DC, /js -- Juergen Schoenwaelder Technical University Braunschweig Dept. Operating Systems & Computer Networks Phone: +49 531 391 3289 Bueltenweg 74/75, 38106 Braunschweig, Germany Fax: +49 531 391 5936 Return-Path: Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) id XAA01959 for nmrg-outgoing; Mon, 1 Nov 1999 23:59:05 +0100 (MET) Received: from wanderer.dcn.davis.ca.us (IDENT:hardaker@dcas102.ucdavis.edu [169.237.210.102]) by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) with ESMTP id XAA01954 for ; Mon, 1 Nov 1999 23:59:03 +0100 (MET) Received: (from hardaker@localhost) by wanderer.dcn.davis.ca.us (8.9.3/8.9.3) id OAA01996; Mon, 1 Nov 1999 14:58:50 -0800 To: Aiko Pras Cc: "nmrg@ibr.cs.tu-bs.de" Subject: Re: [nmrg] Draft minutes of the IRTF-NMRG meeting References: <3814B38C.87AC4EEC@ctit.utwente.nl> From: Wes Hardaker X-URL: http://dcas.ucdavis.edu/~hardaker Organization: U.C.Davis, Information Technology - D.C.A.S. X-Face: #qW^}a%m*T^{A:Cp}$R\"38+d}41-Z}uU8,r%F#c#s:~Nzp0G9](s?,K49KJ]s"*7gvRgA SrAvQc4@/}L7Qc=w{)]ACO\R{LF@S{pXfojjjGg6c;q6{~C}CxC^^&~(F]`1W)%9j/iS/ IM",B1M.?{w8ckLTYD'`|kTr\i\cgY)P4 Date: 01 Nov 1999 14:58:49 -0800 In-Reply-To: Aiko Pras's message of "Mon, 25 Oct 1999 21:46:20 +0200" Message-ID: Lines: 13 User-Agent: Gnus/5.070095 (Pterodactyl Gnus v0.95) XEmacs/21.2 (Shinjuku) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-nmrg@ibr.cs.tu-bs.de Precedence: bulk >>>>> On Mon, 25 Oct 1999 21:46:20 +0200, Aiko Pras said: Aiko> - Via email Wes Hardekker promised to implement it in UCD version 4. FYI, The current CVS snapshot contains TCP support for the manager and agent (cmd line flag: "-T TCP"). It doesn't handle large fragment packets yet, however. I hope to have this fixed by the next release of the ucd-snmp package (4.1)... -- Wes Hardaker Distributed Computing Analysis and Support University of California at Davis Return-Path: Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) id JAA08833 for nmrg-outgoing; Mon, 1 Nov 1999 09:41:48 +0100 (MET) Received: from hansa.ibr.cs.tu-bs.de (IDENT:root@hansa [134.169.34.137]) by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) with ESMTP id JAA08730; Mon, 1 Nov 1999 09:40:52 +0100 (MET) Received: (from strauss@localhost) by hansa.ibr.cs.tu-bs.de (8.9.3/8.9.3) id JAA15178; Mon, 1 Nov 1999 09:40:52 +0100 From: Frank Strauss To: qrsu@hotmail.com ("qr su") Cc: nmrg@ibr.cs.tu-bs.de Subject: Re: [nmrg] Would you please so kind give me a answer? References: <199910301232.OAA00269.nmrg@henkell.ibr.cs.tu-bs.de> Date: 01 Nov 1999 09:40:52 +0100 In-Reply-To: qrsu@hotmail.com's message of "30 Oct 1999 14:33:24 +0200" Message-ID: Lines: 10 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-nmrg@ibr.cs.tu-bs.de Precedence: bulk Hi! qr> If the langusge XML will become useful, what is the SNMP's future? This is no NMRG related question. It is of highly sujective value and cannot be answered in one or two axiomatic sentences. You might consider to post your question to comp.protocols.snmp or comp.dcom.net-management. Frank