[OPS-NM] Re: [NGO] XSDMI work

Andy Bierman <ietf@andybierman.com> Fri, 10 August 2007 17:20 UTC

Return-path: <ops-nm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IJYA9-0008IJ-5X; Fri, 10 Aug 2007 13:20:37 -0400
Received: from ops-nm by megatron.ietf.org with local (Exim 4.43) id 1IJYA7-0008Fg-A8 for ops-nm-confirm+ok@megatron.ietf.org; Fri, 10 Aug 2007 13:20:35 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IJYA6-0008Cg-IL for ops-nm@ietf.org; Fri, 10 Aug 2007 13:20:34 -0400
Received: from smtp113.sbc.mail.re2.yahoo.com ([68.142.229.92]) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IJYA5-0000sI-MH for ops-nm@ietf.org; Fri, 10 Aug 2007 13:20:34 -0400
Received: (qmail 19580 invoked from network); 10 Aug 2007 17:20:33 -0000
Received: from unknown (HELO ?192.168.1.11?) (andybierman@att.net@75.50.187.99 with plain) by smtp113.sbc.mail.re2.yahoo.com with SMTP; 10 Aug 2007 17:20:33 -0000
X-YMail-OSG: 5YbGH1kVM1laI9JAbitXA1RfgJFCfe0m7.8titlRT4MQm.iePsMevKglmdqwDDyzDoaLJOkkNdss1XKuHfPes14ufoEbZFSpdq33f_XXaOapaOfj5DuZ.Q--
Message-ID: <46BC9E07.3030502@andybierman.com>
Date: Fri, 10 Aug 2007 10:19:03 -0700
From: Andy Bierman <ietf@andybierman.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: David Harrington <ietfdbh@comcast.net>
References: <019701c7db6f$674c3990$6702a8c0@china.huawei.com>
In-Reply-To: <019701c7db6f$674c3990$6702a8c0@china.huawei.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: ngo@ietf.org, mib2rdml@ietf.org, opsawg@ietf.org, ops-nm@ietf.org
Subject: [OPS-NM] Re: [NGO] XSDMI work
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>, <mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>, <mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org

David Harrington wrote:
> Hi,
> 
> The XSDMI BOF proposed the creation of a WG to develop 1) the XSD
> equivalents of datatypes and textual conventions from SMIv2, and 2)
> algorithms to translate MIB module specifications into XSD
> equivalents. The BOF demonstrated community support for these two work
> items. 
> 
> People in the BOF volunteered to commit to being editors (3) and
> reviewers (14) for these work items. Starting documents and
> implementations already exist. The work is expected to take less than
> 12 months.
> 
> At Dan's suggestion, rather than starting a new WG for this work, we
> have proposed that the SMI-to-XSD translation work be done in the
> OPSAWG.
> 

I have an objection to this "translation" work.
You will make all kinds of assumptions about data organization
and data naming, and I'm not sure what people are supposed
to do with the XSDs.

The term "XSD translation" is misleading.
The XML on the wire is what is at stake here.
The smidump translation of a MIB has SNMP operations
built into it.  Is this work supposed to produce
a standard way to send an SNMP PDU over any protocol
designed to encode SNMP PDUs in XML?  Why do we need this?

Is the charter going to state that the XSD translation will
be suitable for use for any particular protocol?
NETCONF needs to standardize XML data organization,
namespace usage, and Xpath-based data naming.
Is this translation going to be compatible with that standard
when it eventually comes out?

I would like the charter to be clear on the purpose of this work item,
and what 'protocols' are signed up to use it.


> The OPSAWG chairs need to determine whether the OPSAWG WG should
> accept this work. Please send email to opsawg@ietf.org with comments
> about your support/lack of support for having the OPSAWG do this work.
> (If you do not subscribe to opsawg, you might want to do so, in order
> to follow the discussions.)
> 
> David Harrington
> dbharrington@comcast.net
> ietfdbh@comcast.net
> 
> 


Andy


_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm