Re: [MIB2RDML] SNMP MIB to XSD mapping I-D available

[Juergen Schoenwaelder <j.schoenwaelder at jacobs-university.de>]

On Wed, Nov 28, 2007 at 01:48:33AM -0500, Natale, Bob wrote:
  
> In the meantime, please feel free to raise any issues or post any
> comments concerning the draft or the plans here and on the ops-area
> list (unless the ADs give other guidance about which list(s) to use).

It might be helpful to clarify what is meant with the following
stated requirements:

  R3.  The XSD datatype specified for a given SMI datatype MUST include
       and restrictions on values associated with the SMI datatype.

  R4.  The XSD datatype specified for a given SMI datatype MUST be the
       most direct XSD datatype, with the most parsimonious
       restrictions, which matches the foregoing requirements.

You seem to want SMI <=> XSD equivalence (I assume this because you
carry the 128 subidentifier OID restriction forward) while in other
places people are fine with just SMI => XSD mapping. Note that it is a
very fundamental design decision to require equivalence and will be of
much more importance once you move to TCs and you look at the stuff
that is more challenging.

/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 at ietf.org
https://www1.ietf.org/mailman/listinfo/mib2rdml