Re: I-D ACTION:draft-kzm-hcdata-types-04.txt

[Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>]

The ID says:

   This memo specifies a MIB module that is compliant to the SMIv2.  A
   MIB conforming to the SMIv1 cannot be produced through any
   translation, since textual conventions are not supported in SMIv1.

This is not correct. You can of course translate textual conventions
into ASN.1 type definitions. The reason why this translation does not
work here is that Counter64 does not exist in SMIv1. In fact, using
smidump, the MIB translates to:

HCNUM-TC DEFINITIONS ::= BEGIN

IMPORTS
    mib-2
        FROM RFC1213-MIB;

hcnumTC OBJECT IDENTIFIER
    ::= { mib-2 xxx }

END

I suggest to replace the quoted paragraph with something like this:

   This memo specifies a MIB module that is compliant to the SMIv2.
   The textual conventions defined in this MIB module cannot be
   translated to SMIv1 since the Counter64 type does not exist in
   SMIv1.

/js

-- 
Juergen Schoenwaelder      Technical University Braunschweig
<schoenw@ibr.cs.tu-bs.de>  Dept. Operating Systems & Computer Networks
Phone: +49 531 391 3289    Bueltenweg 74/75, 38106 Braunschweig, Germany
Fax:   +49 531 391 5936    <URL:http://www.ibr.cs.tu-bs.de/~schoenw/>