From mailman-bounces@core3.amsl.com Fri Feb 1 06:13:19 2008 Return-Path: X-Original-To: ietfarch-mib2rdml-archive@core3.amsl.com Delivered-To: ietfarch-mib2rdml-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5F12D28DEEA for ; Fri, 1 Feb 2008 06:08:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.589 X-Spam-Level: X-Spam-Status: No, score=-2.589 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599] Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xbGfyFP7ByCa for ; Fri, 1 Feb 2008 06:08:00 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A08DB293D90 for ; Fri, 1 Feb 2008 05:44:23 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: ietf.org mailing list memberships reminder From: mailman-owner@ietf.org To: mib2rdml-archive@optimus.ietf.org X-No-Archive: yes Message-ID: Date: Fri, 01 Feb 2008 05:06:02 -0800 Precedence: bulk X-BeenThere: mailman@core3.amsl.com X-Mailman-Version: 2.1.9 List-Id: X-List-Administrivia: yes Sender: mailman-bounces@core3.amsl.com Errors-To: mailman-bounces@core3.amsl.com This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, mailman-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. If you have questions, problems, comments, etc, send them to mailman-owner@ietf.org. Thanks! http://www.ietf.org/mailman/options/mib2rdml/mib2rdml-archive%40optimus.ietf.org From mailman-bounces@core3.amsl.com Fri Feb 1 06:15:55 2008 Return-Path: X-Original-To: ietfarch-mib2rdml-archive@core3.amsl.com Delivered-To: ietfarch-mib2rdml-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E5EDA28E8A5 for ; Fri, 1 Feb 2008 06:08:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.589 X-Spam-Level: X-Spam-Status: No, score=-2.589 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599] Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eSDTFMzM5EHm for ; Fri, 1 Feb 2008 06:08:39 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 864CD28D13D for ; Fri, 1 Feb 2008 05:44:29 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: ietf.org mailing list memberships reminder From: mailman-owner@ietf.org To: mib2rdml-archive@optimus.ietf.org X-No-Archive: yes Message-ID: Date: Fri, 01 Feb 2008 05:06:02 -0800 Precedence: bulk X-BeenThere: mailman@core3.amsl.com X-Mailman-Version: 2.1.9 List-Id: X-List-Administrivia: yes Sender: mailman-bounces@core3.amsl.com Errors-To: mailman-bounces@core3.amsl.com This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, mailman-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. If you have questions, problems, comments, etc, send them to mailman-owner@ietf.org. Thanks! http://www.ietf.org/mailman/options/mib2rdml/mib2rdml-archive%40optimus.ietf.org From mib2rdml-bounces@ietf.org Mon Feb 11 00:17:20 2008 Return-Path: X-Original-To: ietfarch-mib2rdml-archive@core3.amsl.com Delivered-To: ietfarch-mib2rdml-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5E3273A6AD5; Mon, 11 Feb 2008 00:17:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.782 X-Spam-Level: X-Spam-Status: No, score=0.782 tagged_above=-999 required=5 tests=[AWL=-2.381, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, HTML_MESSAGE=1, RDNS_NONE=0.1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WCSQiCXQKry8; Mon, 11 Feb 2008 00:17:19 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 87B303A685F; Mon, 11 Feb 2008 00:17:19 -0800 (PST) X-Original-To: mib2rdml@core3.amsl.com Delivered-To: mib2rdml@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 58E6D3A685F; Mon, 11 Feb 2008 00:17:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jnw099tc8Dzd; Mon, 11 Feb 2008 00:17:17 -0800 (PST) Received: from smtp-bedford.mitre.org (smtp-bedford.mitre.org [129.83.20.191]) by core3.amsl.com (Postfix) with ESMTP id 72D0B3A6808; Mon, 11 Feb 2008 00:17:17 -0800 (PST) Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id m1B8Igpw027296; Mon, 11 Feb 2008 03:18:42 -0500 Received: from IMCFE1.MITRE.ORG (imcfe1.mitre.org [129.83.29.3]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id m1B8IfM5027293; Mon, 11 Feb 2008 03:18:41 -0500 Received: from IMCSRV2.MITRE.ORG ([129.83.20.164]) by IMCFE1.MITRE.ORG with Microsoft SMTPSVC(6.0.3790.1830); Mon, 11 Feb 2008 03:18:41 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Mon, 11 Feb 2008 03:18:40 -0500 Message-ID: <4915F014FDD99049A9C3A8C1B832004F0277F329@IMCSRV2.MITRE.ORG> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Expressing SNMP SMI Datatypes in XML Schema Definition Language draft submitted Thread-Index: AchshrU9Eh9mtU+dQEyJvMbrsqa/2w== From: "Natale, Bob" To: , X-OriginalArrivalTime: 11 Feb 2008 08:18:41.0830 (UTC) FILETIME=[B6336C60:01C86C86] Cc: ops-area@ietf.org Subject: [MIB2RDML] Expressing SNMP SMI Datatypes in XML Schema Definition Language draft submitted X-BeenThere: mib2rdml@ietf.org X-Mailman-Version: 2.1.9 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="===============1287969819==" Sender: mib2rdml-bounces@ietf.org Errors-To: mib2rdml-bounces@ietf.org This is a multi-part message in MIME format. --===============1287969819== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C86C86.B5CE20E5" This is a multi-part message in MIME format. ------_=_NextPart_001_01C86C86.B5CE20E5 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, =20 I have submitted "Expressing SNMP SMI Datatypes in XML Schema Definition Language", draft-ietf-opsawg-smi-datatypes-in-xsd-00.txt, via the Internet-Drafts submission tool, but had to do it via a "manual entry" due to administrative complications. Manual submissions can take up two business days to process. =20 In the meantime, I have posted a copy at http://home.comcast.net/~bobnatale/draft-ietf-opsawg-smi-datatypes-in-x sd-00.txt. =20 For those who might want to review the slides I presented at the Vancouver IETF for background info, you can get them at http://home.comcast.net/~bobnatale/Converting_SNMP_MIBs_to_XML_via_XSD. ppt. The I-D has updated wording relative to the slides. Slide 7 helps to narrow the focus of the current effort relative to the original MIB2RMDL scope on slide 6. =20 Apologies for cross-posting to the ops-area list -- this is an "Ops Area WG" and "MIB2RMDL" item, but just wanted to be sure to alert all interested parties without going too far afield. =20 Cheers, BobN =20 =20 ------_=_NextPart_001_01C86C86.B5CE20E5 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Hi,
 
I=20 have submitted "Expressing SNMP SMI Datatypes in XML Schema = Definition=20 Language", draft-ietf-opsawg-smi-datatypes-in-xsd-00.txt, via the=20 Internet-Drafts submission tool, but had to do it via a "manual entry" = due to=20 administrative complications.  Manual submissions can take up two = business=20 days to process.
 
In=20 the meantime, I have posted a copy at http://home.comcast.net/~bobnatale/draft-ietf-opsawg-smi= -datatypes-in-xsd-00.txt.
 
For=20 those who might want to review the slides I presented at the Vancouver = IETF for=20 background info, you can get them at http://home.comcast.net/~bobnatale/Converting_SNMP_MIBs_to_XML= _via_XSD.ppt. =20 The I-D has updated wording relative to the slides.  = Slide 7=20 helps to narrow the focus of the current effort relative to the original = MIB2RMDL scope on slide 6.
 
Apologies for cross-posting to the ops-area = list --=20 this is an "Ops Area WG" and "MIB2RMDL" item, but just wanted to be sure = to=20 alert all interested parties without going too far = afield.
 
Cheers,
BobN
 
 
------_=_NextPart_001_01C86C86.B5CE20E5-- --===============1287969819== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MIB2RDML mailing list MIB2RDML@ietf.org http://www.ietf.org/mailman/listinfo/mib2rdml --===============1287969819==-- From mib2rdml-bounces@ietf.org Mon Feb 11 07:17:04 2008 Return-Path: X-Original-To: ietfarch-mib2rdml-archive@core3.amsl.com Delivered-To: ietfarch-mib2rdml-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A4FF43A6C5F; Mon, 11 Feb 2008 07:17:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.01 X-Spam-Level: X-Spam-Status: No, score=-0.01 tagged_above=-999 required=5 tests=[AWL=0.427, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B5eLN1v11jfO; Mon, 11 Feb 2008 07:17:03 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B42173A6C54; Mon, 11 Feb 2008 07:17:03 -0800 (PST) X-Original-To: mib2rdml@core3.amsl.com Delivered-To: mib2rdml@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 827BC3A6C54 for ; Mon, 11 Feb 2008 07:17:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K5Wz9pX7V4yA for ; Mon, 11 Feb 2008 07:17:01 -0800 (PST) Received: from smtp-bedford.mitre.org (smtp-bedford.mitre.org [129.83.20.191]) by core3.amsl.com (Postfix) with ESMTP id 3B4B03A67D5 for ; Mon, 11 Feb 2008 07:17:01 -0800 (PST) Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id m1BFIPwl007225 for ; Mon, 11 Feb 2008 10:18:25 -0500 Received: from imcfe2.MITRE.ORG (imcfe2.mitre.org [129.83.29.4]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id m1BFIPN4007213 for ; Mon, 11 Feb 2008 10:18:25 -0500 Received: from IMCSRV2.MITRE.ORG ([129.83.20.164]) by imcfe2.MITRE.ORG with Microsoft SMTPSVC(6.0.3790.1830); Mon, 11 Feb 2008 10:18:24 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Mon, 11 Feb 2008 10:18:24 -0500 Message-ID: <4915F014FDD99049A9C3A8C1B832004F0277F3B2@IMCSRV2.MITRE.ORG> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [OPSAWG] Expressing SNMP SMI Datatypes in XML SchemaDefinitionLanguage draft submitted Thread-Index: AchsjRY9zCEPEn5mRfGlep2Moa2FngAF6nVgAAb3UOA= From: "Natale, Bob" To: X-OriginalArrivalTime: 11 Feb 2008 15:18:24.0513 (UTC) FILETIME=[583FE710:01C86CC1] Subject: [MIB2RDML] FW: [OPSAWG] Expressing SNMP SMI Datatypes in XML SchemaDefinitionLanguage draft submitted X-BeenThere: mib2rdml@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: converting MIB modules into resource models List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mib2rdml-bounces@ietf.org Errors-To: mib2rdml-bounces@ietf.org Hi, People on the MIB2RMDL list but not on the OPSAWG list who want to follow or participate in the "MIB to XML via XSD" work should subscribe to the OPSAWG list at https://www1.ietf.org/mailman/listinfo/opsawg. Only periodic status updates will be posted to the MIB2RMDL list wrt this work. Once (and if) the IETF publishes standards track RFCs for this work, the MIB2RMDL list will likely be more active in the "to RMDL" effort (and then perhaps only to help find the right venue for it outside the IETF). Cheers, BobN -----Original Message----- From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On Behalf Of Natale, Bob Sent: Monday, February 11, 2008 7:00 AM To: j.schoenwaelder@jacobs-university.de Cc: opsawg@ietf.org Subject: Re: [OPSAWG] Expressing SNMP SMI Datatypes in XML SchemaDefinitionLanguage draft submitted Hi Juergen, Thanks..."base types" will be fine. Original intent was to distinguish this set _in a concrete manner_ from TCs which, of course, are not recognizable as types on the wire. Cheers, BobN -----Original Message----- From: Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs-university.de] Sent: Monday, February 11, 2008 4:01 AM To: Natale, Bob Cc: opsawg@ietf.org Subject: Re: [OPSAWG] Expressing SNMP SMI Datatypes in XML SchemaDefinition Language draft submitted On Mon, Feb 11, 2008 at 03:18:40AM -0500, Natale, Bob wrote: > I have submitted "Expressing SNMP SMI Datatypes in XML Schema > Definition Language", draft-ietf-opsawg-smi-datatypes-in-xsd-00.txt, > via the Internet-Drafts submission tool, but had to do it via a "manual > entry" due to administrative complications. Manual submissions can > take up two business days to process. > > In the meantime, I have posted a copy at > http://home.comcast.net/~bobnatale/draft-ietf-opsawg-smi-datatypes-in-x > sd-00.txt. I see the following text: This document concerns the SMI datatypes that are carried "on-the- wire" -- i.e., have tag values defined in the SMI carried in varbinds in SNMP PDUs -- between SNMP management applications and SNMP agents: o INTEGER o Integer32 o Unsigned32 o Counter32 o Gauge32 o TimeTicks o Counter64 o OctetString o Opague o IpAddress o ObjectIdentifier By the very nature of ASN.1, values of any type carried in an SNMP varbind list have a tag. If your idea is to look at types with distinct tag values, then the list does not make sense since INTEGER and Integer32 or Gauge32 and Unsigned32 use the same tag. Perhaps it is better to talk about SMIv1/SMIv2 base types. This term is used in several places in RFC 2578. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 _______________________________________________ OPSAWG mailing list OPSAWG@ietf.org http://www.ietf.org/mailman/listinfo/opsawg _______________________________________________ MIB2RDML mailing list MIB2RDML@ietf.org http://www.ietf.org/mailman/listinfo/mib2rdml From mib2rdml-bounces@ietf.org Sun Feb 24 23:17:41 2008 Return-Path: X-Original-To: ietfarch-mib2rdml-archive@core3.amsl.com Delivered-To: ietfarch-mib2rdml-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7AE7628C168; Sun, 24 Feb 2008 23:17:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.33 X-Spam-Level: X-Spam-Status: No, score=0.33 tagged_above=-999 required=5 tests=[AWL=-0.233, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, HTML_MESSAGE=1, RDNS_NONE=0.1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a-SJ39sxKQ5e; Sun, 24 Feb 2008 23:17:41 -0800 (PST) Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 833D928C1B3; Sun, 24 Feb 2008 23:17:39 -0800 (PST) X-Original-To: mib2rdml@core3.amsl.com Delivered-To: mib2rdml@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3613D3A6C0C; Sun, 24 Feb 2008 23:17:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5meR2e-M3Onc; Sun, 24 Feb 2008 23:17:38 -0800 (PST) Received: from smtp-bedford.mitre.org (smtp-bedford.mitre.org [129.83.20.191]) by core3.amsl.com (Postfix) with ESMTP id 4EC153A6C52; Sun, 24 Feb 2008 23:17:38 -0800 (PST) Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id m1P7HWAT019115; Mon, 25 Feb 2008 02:17:32 -0500 Received: from imcfe2.MITRE.ORG (imcfe2.mitre.org [129.83.29.4]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id m1P7HW3I019109; Mon, 25 Feb 2008 02:17:32 -0500 Received: from IMCSRV2.MITRE.ORG ([129.83.20.164]) by imcfe2.MITRE.ORG with Microsoft SMTPSVC(6.0.3790.1830); Mon, 25 Feb 2008 02:17:31 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Mon, 25 Feb 2008 02:17:30 -0500 Message-ID: <4915F014FDD99049A9C3A8C1B832004F027F586E@IMCSRV2.MITRE.ORG> In-Reply-To: <4915F014FDD99049A9C3A8C1B832004F0277F329@IMCSRV2.MITRE.ORG> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Expressing SNMP SMI Datatypes in XML Schema Definition Language -01 draft submitted Thread-Index: AchshrU9Eh9mtU+dQEyJvMbrsqa/2wK9u9bg References: <4915F014FDD99049A9C3A8C1B832004F0277F329@IMCSRV2.MITRE.ORG> From: "Natale, Bob" To: X-OriginalArrivalTime: 25 Feb 2008 07:17:31.0246 (UTC) FILETIME=[7C2540E0:01C8777E] Cc: mib2rdml@ietf.org Subject: [MIB2RDML] Expressing SNMP SMI Datatypes in XML Schema Definition Language -01 draft submitted X-BeenThere: mib2rdml@ietf.org X-Mailman-Version: 2.1.9 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="===============0508364842==" Sender: mib2rdml-bounces@ietf.org Errors-To: mib2rdml-bounces@ietf.org This is a multi-part message in MIME format. --===============0508364842== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8777E.7C5E7A53" This is a multi-part message in MIME format. ------_=_NextPart_001_01C8777E.7C5E7A53 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, =20 I have submitted an updated version of "Expressing SNMP SMI Datatypes in XML Schema Definition Language", draft-ietf-opsawg-smi-datatypes-in-xsd-01.txt, via the Internet-Drafts submission tool, but had to do it via a "manual entry" due to administrative complications. Pending formal publication, you can get a copy from the "staging" area at: http://www3.ietf.org/proceedings/staging/draft-ietf-opsawg-smi-datatype s-in-xsd-01.txt. =20 This draft includes changes made for comments on the -00 version received from Juergen Schoenwaelder and David Harrington. =20 I will post a more detailed description of the changes later today or tomorrow. =20 Cheers, BobN =20 =20 ------_=_NextPart_001_01C8777E.7C5E7A53 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Hi,
 
I = have submitted an=20 updated version of "Expressing SNMP SMI Datatypes in XML Schema = Definition=20 Language", draft-ietf-opsawg-smi-datatypes-in-xsd-01.txt, via the=20 Internet-Drafts submission tool, but had to do it via a "manual entry" = due to=20 administrative complications.  Pending formal publication, you can = get a=20 copy from the "staging" area at: http://www3.ietf.org/proceedings/staging/draft-iet= f-opsawg-smi-datatypes-in-xsd-01.txt.
 
This draft includes changes made for comments = on the -00=20 version received from Juergen Schoenwaelder and David=20 Harrington.
 
I will post a more detailed description of the = changes=20 later today or tomorrow.
 
Cheers,
BobN
 
 
------_=_NextPart_001_01C8777E.7C5E7A53-- --===============0508364842== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MIB2RDML mailing list MIB2RDML@ietf.org http://www.ietf.org/mailman/listinfo/mib2rdml --===============0508364842==--