From mib2rdml-bounces@ietf.org Wed Jun 06 14:16:48 2007 Return-path: 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 ; 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 ; 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 ; 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, 6 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" To: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1036187319==" Errors-To: mib2rdml-bounces@ietf.org This is a multi-part message in MIME format. --===============1036187319== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C7A866.D534BC15" This is a multi-part message in MIME format. ------_=_NextPart_001_01C7A866.D534BC15 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, =20 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. =20 Here is the BoF proposal for reference (with a few admin corrections since it was first published):=20 =09 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 ) 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 . (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 operation and/or data delivery mechanism.=20 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. =20 (Work items (C) and (D) are still begin discussed on the OPS-NM list.) =20 I would urge everyone interested in MIB2RMDL to read the I-Ds listed above and to following and contribute to the XSDMI effort. =20 Cheers, BobN xxx=20 =20 ------_=_NextPart_001_01C7A866.D534BC15 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Hi,
 
For those MIB2RMDL participants who are not = on the=20 OPS-NM list (ops-nm@ietf.org), a = proposal=20 for work that could feed a part of what MIB2RMDL needs is being actively = discussed on the OPS-NM list at this time.
 
Here=20 is the BoF proposal for reference (with = a few=20 admin corrections since it was first published): 

XSD for accessing = SMIv2 data models=20 (xsdmi) BOF
Status: request submitted including proposed WG=20 charter
Discussions:  OPS-NM (ops-nm@ietf.org)=
Responsible = AD: Dan=20 Romascanu
BOF Chair: David Harrington (ietfdbh@comcast.net)
Internet-Drafts:
draft-romascanu-netconf-datatypes-02 = (XSD for=20 SMIv2 Data Types and
Textual = Conventions)
draft-li-ngo-access-mib-00  (SMIv2 Data Access for=20 NETCONF)
Summary and Scope: Future WG Formation - The XSDMI WG will = undertake the
following work items:
(A) Development of a = standard XML=20 Schema Definition [XSD] to specify the
XML encoding of the core = SMIv2 data=20 types defined in RFC2578.
(B) Development of a standard XML Schema=20 Definition [XSD] to specify the
XML encoding of some generic and = common=20 SMIv2 textual conventions, as
identified at http://www.ops.ietf.org/mib-common-tcs.html.
(C) Definition of a standard set of = security=20 requirements for accessing
MIB management data by potentially = multiple=20 protocols.
(D) Development of a standard set of algorithms for = accessing=20 SMIv2
management information, possibly using the NETCONF = <get>=20 operation
and/or <notification> data delivery mechanism. 
Given the working assumption = that the=20 resource model artifacts portion (RMDL) of MIB2RMDL will *likely* = consist of=20 sets of XSD, RMD, and WSDL files, work items (A) and (B) of the XSDMI = proposal=20 seem directly relevant.  If MIB2RMDL can leverage those outputs = from the=20 XSDMI effort, so much the better.
 
(Work items (C) and (D) are = still begin=20 discussed on the OPS-NM list.)
 
I would urge everyone = interested in=20 MIB2RMDL to read the I-Ds listed above and to following and contribute = to the=20 XSDMI effort.
 
Cheers,
BobN
xxx 
 
------_=_NextPart_001_01C7A866.D534BC15-- --===============1036187319== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MIB2RDML mailing list MIB2RDML@ietf.org https://www1.ietf.org/mailman/listinfo/mib2rdml --===============1036187319==-- From mib2rdml-bounces@ietf.org Mon Jun 18 02:09:58 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I0AR2-0006kj-I6; Mon, 18 Jun 2007 02:09:56 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I0AQt-0006hI-TP; Mon, 18 Jun 2007 02:09:47 -0400 Received: from de307622-de-outbound.net.avaya.com ([198.152.71.100]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0AQs-0007sQ-0v; Mon, 18 Jun 2007 02:09:47 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16]) by de307622-de-outbound.net.avaya.com with ESMTP; 18 Jun 2007 02:09:44 -0400 X-IronPort-AV: i="4.16,433,1175486400"; d="scan'208"; a="27969696:sNHT12457254" X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 18 Jun 2007 08:08:56 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Request to forward the Nomcom 2007-8 Announcement to lists youmanage Thread-Index: AcewN0+aaYBjAEmrQgWJQH6H2csCrwBN4uig From: "Romascanu, Dan (Dan)" To: , "Ops-Nm" , "MIB Doctors (E-mail)" , "Aaa-Doctors (E-mail)" , , , , "Hub Mib" X-Spam-Score: 0.1 (/) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 Cc: Subject: [MIB2RDML] FW: Request to forward the Nomcom 2007-8 Announcement to lists youmanage X-BeenThere: mib2rdml@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: converting MIB modules into resource models List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mib2rdml-bounces@ietf.org Please consider the message below forwarded at the request of the Nomcom chair.=20 Dan =20 -----Original Message----- From: Lakshminath Dondeti [mailto:ldondeti@qualcomm.com]=20 Sent: Saturday, June 16, 2007 7:55 PM To: wgchairs@ietf.org; irsg@isi.edu; bofchairs@ietf.org Subject: Request to forward the Nomcom 2007-8 Announcement to lists youmanage Folks, We have around 50 volunteers so far for Nomcom 2007-8 voting member selection. We need a lot more! Not everyone subscribes to the IETF-Announce list. Could you please forward the announcement https://datatracker.ietf.org/public/show_nomcom_message.cgi?id=3D1234 to WG, RG, BoF, Area lists that you manage? Thanks in advance. best regards, Lakshminath _______________________________________________ MIB2RDML mailing list MIB2RDML@ietf.org https://www1.ietf.org/mailman/listinfo/mib2rdml From mib2rdml-bounces@ietf.org Mon Jun 18 14:46:32 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I0MFE-0005JP-C6; Mon, 18 Jun 2007 14:46:32 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I0MFC-0005GX-54; Mon, 18 Jun 2007 14:46:30 -0400 Received: from nj300815-nj-outbound.net.avaya.com ([198.152.12.100] helo=nj300815-nj-outbound.avaya.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0MFA-00064J-UZ; Mon, 18 Jun 2007 14:46:30 -0400 Received: from 16.140.64.135.in-addr.arpa (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16]) by nj300815-nj-outbound.avaya.com with ESMTP; 18 Jun 2007 14:46:27 -0400 X-IronPort-AV: i="4.16,435,1175486400"; d="scan'208"; a="28702339:sNHT7851684" X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 18 Jun 2007 20:46:26 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Submission cut-off dates before Chicago Thread-Index: Acex2PmEtxbDklB8TrC3YaXjv/x7Yw== From: "Romascanu, Dan (Dan)" To: , , "Netconf (E-mail)" , , , , , X-Spam-Score: 0.1 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Cc: Subject: [MIB2RDML] Submission cut-off dates before Chicago X-BeenThere: mib2rdml@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: converting MIB modules into resource models List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mib2rdml-bounces@ietf.org Working Group and BOF Chairs and Contributors, Please note the submission dates for Internet-Drafts before Chicago.=20 July 2, Monday - Internet Draft Cut-off for initial document (-00) submission by 09:00 ET (13:00 UTC/GMT) July 9, Monday - Internet Draft final submission cut-off by 09:00 ET (13:00 UTC/GMT) Dan =20 _______________________________________________ MIB2RDML mailing list MIB2RDML@ietf.org https://www1.ietf.org/mailman/listinfo/mib2rdml From mib2rdml-bounces@ietf.org Tue Jun 19 07:36:22 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I0c0T-00039H-Rv; Tue, 19 Jun 2007 07:36:21 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I0c0S-00038y-2y; Tue, 19 Jun 2007 07:36:20 -0400 Received: from de307622-de-outbound.net.avaya.com ([198.152.71.100]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0c0P-0006GY-NQ; Tue, 19 Jun 2007 07:36:20 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by de307622-de-outbound.net.avaya.com with ESMTP; 19 Jun 2007 07:36:16 -0400 X-IronPort-AV: i="4.16,438,1175486400"; d="url'?scan'208"; a="28476622:sNHT11474352" Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C7B265.F4484B25" X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Tue, 19 Jun 2007 13:35:35 +0200 Message-ID: X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Thread-Topic: I-D ACTION:draft-schoenw-sming-lessons-00.txt Thread-Index: Acex4tL425YvGqACTXeztnJY2/kEFgAgquUQ From: "Romascanu, Dan (Dan)" To: "Netconf (E-mail)" , , , X-Spam-Score: 0.1 (/) X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024 Cc: Subject: [MIB2RDML] FW: I-D ACTION:draft-schoenw-sming-lessons-00.txt X-BeenThere: mib2rdml@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: converting MIB modules into resource models List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mib2rdml-bounces@ietf.org This is a multi-part message in MIME format. ------_=_NextPart_001_01C7B265.F4484B25 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable This I-D written by Juergen includes some information about the SMIng development experience. I believe that it's good reading for folks involved in the data modeling work related to NETCONF, and other discussions happening in the BOFs and lists of the area. Dan =20 -----Original Message----- From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]=20 Sent: Monday, June 18, 2007 10:50 PM To: i-d-announce@ietf.org Subject: I-D ACTION:draft-schoenw-sming-lessons-00.txt=20 A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Lessons Learned from the SMIng Project Author(s) : J. Schoenwaelder Filename : draft-schoenw-sming-lessons-00.txt Pages : 12 Date : 2007-6-18 =09 A data modeling language for network management protocols called SMIng was developed within the Network Management Research Group of the Internet Research Task Force over a period of several years. This memo documents some of the lessons learned during the project for consideration by designers of future data modeling languages for network management protocols. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-schoenw-sming-lessons-00.txt To remove yourself from the I-D Announcement list, send a message to=20 i-d-announce-request@ietf.org with the word unsubscribe in the body of=20 the message.=20 You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce=20 to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the=20 username "anonymous" and a password of your e-mail address. After=20 logging in, type "cd internet-drafts" and then=20 "get draft-schoenw-sming-lessons-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html=20 or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-schoenw-sming-lessons-00.txt". =09 ------_=_NextPart_001_01C7B265.F4484B25 Content-Type: application/octet-stream; name="draft-schoenw-sming-lessons-00.URL" Content-Transfer-Encoding: base64 Content-Description: draft-schoenw-sming-lessons-00.URL Content-Disposition: attachment; filename="draft-schoenw-sming-lessons-00.URL" W0ludGVybmV0U2hvcnRjdXRdDQpVUkw9ZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0 cy9kcmFmdC1zY2hvZW53LXNtaW5nLWxlc3NvbnMtMDAudHh0DQo= ------_=_NextPart_001_01C7B265.F4484B25 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MIB2RDML mailing list MIB2RDML@ietf.org https://www1.ietf.org/mailman/listinfo/mib2rdml ------_=_NextPart_001_01C7B265.F4484B25--