Re: [MIB2RDML] Expressing SNMP SMI Datatypes in XML Schema Definition Language -03 draft submitted

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Mon, 28 July 2008 19:18 UTC

Return-Path: <mib2rdml-bounces@ietf.org>
X-Original-To: mib2rdml-archive@optimus.ietf.org
Delivered-To: ietfarch-mib2rdml-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 67AB03A6AC0; Mon, 28 Jul 2008 12:18:37 -0700 (PDT)
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 484623A6845; Mon, 28 Jul 2008 12:18:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.475
X-Spam-Level:
X-Spam-Status: No, score=-1.475 tagged_above=-999 required=5 tests=[AWL=-0.426, BAYES_00=-2.599, HELO_EQ_DE=0.35, J_CHICKENPOX_210=0.6, J_CHICKENPOX_29=0.6]
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 xC7eggnrtA7f; Mon, 28 Jul 2008 12:18:35 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id BD9123A694E; Mon, 28 Jul 2008 12:18:34 -0700 (PDT)
Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id B3349C002D; Mon, 28 Jul 2008 21:18:44 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 94VEebI9NYpJ; Mon, 28 Jul 2008 21:18:38 +0200 (CEST)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 3B74CC0034; Mon, 28 Jul 2008 21:18:38 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 186D267942B; Mon, 28 Jul 2008 21:18:37 +0200 (CEST)
Date: Mon, 28 Jul 2008 21:18:37 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: ellison@ieee.org
Message-ID: <20080728191837.GA9535@elstar.local>
Mail-Followup-To: ellison@ieee.org, "Natale, Bob" <RNATALE@mitre.org>, mib2rdml@ietf.org, opsawg@ietf.org
References: <4915F014FDD99049A9C3A8C1B832004F0277F329@IMCSRV2.MITRE.ORG> <4915F014FDD99049A9C3A8C1B832004F027F586E@IMCSRV2.MITRE.ORG> <4915F014FDD99049A9C3A8C1B832004F02DB3EFD@IMCSRV2.MITRE.ORG> <4915F014FDD99049A9C3A8C1B832004F02E47157@IMCSRV2.MITRE.ORG> <488E196F.2080304@EllisonSoftware.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <488E196F.2080304@EllisonSoftware.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: mib2rdml@ietf.org, opsawg@ietf.org
Subject: Re: [MIB2RDML] Expressing SNMP SMI Datatypes in XML Schema Definition Language -03 draft submitted
X-BeenThere: mib2rdml@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: j.schoenwaelder@jacobs-university.de
List-Id: converting MIB modules into resource models <mib2rdml.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mib2rdml>, <mailto:mib2rdml-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/mib2rdml>
List-Post: <mailto:mib2rdml@ietf.org>
List-Help: <mailto:mib2rdml-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib2rdml>, <mailto:mib2rdml-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mib2rdml-bounces@ietf.org
Errors-To: mib2rdml-bounces@ietf.org

On Mon, Jul 28, 2008 at 03:09:35PM -0400, Mark Ellison wrote:

> - In section 5.2, "OctetString", second paragraph says "each octet is  
> encoded as two hexadecimal digits" and the third bullet indicates the  
> "maxLength" restriction of 65535 octets.  However, the xs:simpleType  
> "OctetString" definition in section 4 indicates an xs:maxLength  
> value="65535".  If the intent is to represent 65535 octets then the  
> xs:maxLength value should be twice this number, "131070".

I think the maxLength restriction is counted in the number of decoded
bytes not the number of bytes needed for the encoding. Please check
section 4.3.3 of <http://www.w3.org/TR/xmlschema-2/>. (I did run into
this before; perhaps it is worth adding a comment so that we do not
run into this question again - or worse someone "fixes" this later
on.)

> - [more of a personal wish] In section 5.5, "ObjectIdentifier", I  
> realize the text is written to be faithful to the definition of the SMI  
> OBJECT IDENTIFIER.  In this regard, it is probably not appropriate to  
> place support for "OID fragments" here.  I find I use a lot of OID  
> fragments (1 or more subids that do not have the initial 2 subid  
> restrictions) to represent instance components for a set of related  
> OBJECT-TYPE OIDs.  Possibly there is a place, either in this memo, or in  
> another related memo to support the notion of an OID fragment?  I  
> suppose I could use the ObjectIdentifier "as is" by prepending any  
> fragment with 1.1, but I regard this as a programmatic contortion with  
> undesirable overhead.

Your ObjectIdentifierFragment simply is not an ObjectIdentifier...

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
_______________________________________________
MIB2RDML mailing list
MIB2RDML@ietf.org
https://www.ietf.org/mailman/listinfo/mib2rdml