[MIB2RDML] XSDMI BOF at IETF-69 [Chicago, July 22-27]

"Natale, Bob" <RNATALE@mitre.org> Wed, 06 June 2007 18:16 UTC

Return-path: <mib2rdml-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hw03q-0003IA-Uc; Wed, 06 Jun 2007 14:16:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hw03p-0003I3-An for mib2rdml@ietf.org; Wed, 06 Jun 2007 14:16:45 -0400
Received: from smtpproxy2.mitre.org ([192.80.55.71] helo=smtp-mclean.mitre.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hw03n-0008ER-Rr for mib2rdml@ietf.org; Wed, 06 Jun 2007 14:16:45 -0400
Received: from smtp-mclean.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-mclean.mitre.org (8.12.11.20060308/8.12.11) with SMTP id l56IGhC5010163 for <mib2rdml@ietf.org>; Wed, 6 Jun 2007 14:16:43 -0400
Received: from smtp-mclean.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-mclean.mitre.org (Postfix) with ESMTP id 2D40A4F8D9 for <mib2rdml@ietf.org>; Wed, 6 Jun 2007 14:16:43 -0400 (EDT)
Received: from IMCFE1.MITRE.ORG (imcfe1.mitre.org [129.83.29.3]) by smtp-mclean.mitre.org (8.12.11.20060308/8.12.11) with ESMTP id l56IGhkn010140 for <mib2rdml@ietf.org>; Wed, 6 Jun 2007 14:16:43 -0400
Received: from IMCSRV2.MITRE.ORG ([129.83.20.164]) by IMCFE1.MITRE.ORG with Microsoft SMTPSVC(6.0.3790.1830); Wed, 6 Jun 2007 14:16:43 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 06 Jun 2007 14:16:41 -0400
Message-ID: <4915F014FDD99049A9C3A8C1B832004F01DFB2D1@IMCSRV2.MITRE.ORG>
In-Reply-To: <4915F014FDD99049A9C3A8C1B832004F01DFA7A6@IMCSRV2.MITRE.ORG>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: XSDMI BOF at IETF-69 [Chicago, July 22-27]
Thread-Index: AceiG0jeNchBcHo/RQ2zJW30sjCxzQGSdrWA
References: <4915F014FDD99049A9C3A8C1B832004F01DFA7A6@IMCSRV2.MITRE.ORG>
From: "Natale, Bob" <RNATALE@mitre.org>
To: mib2rdml@ietf.org
X-OriginalArrivalTime: 06 Jun 2007 18:16:43.0037 (UTC) FILETIME=[D5CB9CD0:01C7A866]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: df9edf1223802dd4cf213867a3af6121
Subject: [MIB2RDML] XSDMI BOF at IETF-69 [Chicago, July 22-27]
X-BeenThere: mib2rdml@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: converting MIB modules into resource models <mib2rdml.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mib2rdml>, <mailto:mib2rdml-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mib2rdml>
List-Post: <mailto:mib2rdml@ietf.org>
List-Help: <mailto:mib2rdml-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mib2rdml>, <mailto:mib2rdml-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1036187319=="
Errors-To: mib2rdml-bounces@ietf.org

Hi,
 
For those MIB2RMDL participants who are not on the OPS-NM list
(ops-nm@ietf.org), a proposal for work that could feed a part of what
MIB2RMDL needs is being actively discussed on the OPS-NM list at this
time.
 
Here is the BoF proposal for reference (with a few admin corrections
since it was first published): 

	
	XSD for accessing SMIv2 data models (xsdmi) BOF
	Status: request submitted including proposed WG charter
	Discussions:  OPS-NM (ops-nm@ietf.org)
	Responsible AD: Dan Romascanu
	BOF Chair: David Harrington (ietfdbh@comcast.net
<mailto:ietfdbh@comcast.net> )
	Internet-Drafts:
	draft-romascanu-netconf-datatypes-02 (XSD for SMIv2 Data Types
and
	Textual Conventions)
	draft-li-ngo-access-mib-00  (SMIv2 Data Access for NETCONF)
	Summary and Scope: Future WG Formation - The XSDMI WG will
undertake the
	following work items:
	(A) Development of a standard XML Schema Definition [XSD] to
specify the
	XML encoding of the core SMIv2 data types defined in RFC2578.
	(B) Development of a standard XML Schema Definition [XSD] to
specify the
	XML encoding of some generic and common SMIv2 textual
conventions, as
	identified at http://www.ops.ietf.org/mib-common-tcs.html
<http://www.ops.ietf.org/mib-common-tcs.html> .
	(C) Definition of a standard set of security requirements for
accessing
	MIB management data by potentially multiple protocols.
	(D) Development of a standard set of algorithms for accessing
SMIv2
	management information, possibly using the NETCONF <get>
operation
	and/or <notification> data delivery mechanism. 

Given the working assumption that the resource model artifacts portion
(RMDL) of MIB2RMDL will *likely* consist of sets of XSD, RMD, and WSDL
files, work items (A) and (B) of the XSDMI proposal seem directly
relevant.  If MIB2RMDL can leverage those outputs from the XSDMI
effort, so much the better.
 
(Work items (C) and (D) are still begin discussed on the OPS-NM list.)
 
I would urge everyone interested in MIB2RMDL to read the I-Ds listed
above and to following and contribute to the XSDMI effort.
 
Cheers,
BobN
xxx 

	 

_______________________________________________
MIB2RDML mailing list
MIB2RDML@ietf.org
https://www1.ietf.org/mailman/listinfo/mib2rdml