[storm] MIB Dr. review of draft-ietf-storm-ifcpmib-05

["Joan Cucchiara" <[e-mail]>]

Hello Prakash,

Thank you for providing this updated MIB document.

This MIB compiles cleanly with both smiLint and
smicngPRO MIB compilers.

Comments follow.  Please let me know if you 
have any questions.

Thanks,
  -Joan



COMMENTS
---------

GENERAL Comment:  When an object, or Conformance Group
is deprecated, the DESCRIPTION clause needs to be updated
to state this and the reason for the deprecation.

Almost all the DESCRIPTION clauses do mention the deprecation but
this is at the very end of the DESCRIPTION clause,  Please 
start the DESCRIPTION clause with this information, such as:

DESCRIPTION:
"This object is deprecated.  It has been deprecated because ...
Then include the original description.

Specific examples are included in the comments below.

 

1)  NIT:  Please put a UNITS clause on the objects
that use these TCs:
IfcpIpTOVorZero  UNITS: seconds
IfcpLTIorZero    UNITS: seconds



2)  * IfcpAddressMode TEXTUAL-CONVENTION

Why was the STATUS not changed to "deprecated"?
Please do so.  

Also, as discussed above, please change the DESCRIPTION to state that the
TC is deprecated and why as the first statement(s) of the
DESCRIPTION clause.


3) ifcpLclGtwyInstAddrTransMode     IfcpAddressMode,

The ifcpLclGtwyInstAddrTransMode object is the only
object which uses the (deprecated) IfcpAddressMode TC.

This object should also be deprecated.

A new read-only object could be added if this is thought to be
beneficial.. 


4)  ifcpLclGtwyInstStorageType should be deprecated also.

   ifcpLclGtwyInstStorageType OBJECT-TYPE
       SYNTAX            StorageType
       MAX-ACCESS        read-only
       STATUS            current
       DESCRIPTION
   "The storage type for this row.  Parameter values defined
    for a gateway are usually non-volatile, but may be volatile
    or permanent in some configurations.  If permanent, then
    the following parameters must have read-write access:
    ifcpLclGtwyInstAddrTransMode, ifcpLclGtwyInstDefaultIpTOV,
    and ifcpLclGtwyInstDefaultLTInterval."
       DEFVAL            { nonVolatile }
       ::= {ifcpLclGtwyInstEntry      11}


The DESCRIPTION clause specifies ifcpLclGtwyInstAddrTransMode as one of
the values to provide read-write access for when the value of this object
is permanent, as such this object should be deprecated.

A new StorageType object which excludes the ifcpLclGtwyInstAddrTransMode
should also probably be added.   

A related question on this object, why was ifcpLclGtwyInstFcBrdcstSupport
not included in this list of read-write objects?



5) ifcpLclGatewayGroup may need to be deprecated and replaced by another
group after 1-4  is done.


6)  According to rfc2580, Section 7.1

If changing a STATUS to "deprecated"
the DESCRIPTION clause should be updated
to explain.

*ifcpLclGatewaySessionGroup STATUS was
changed to "deprecated" but the DESCRIPTION
has not been changed.   Again, please state
that the group has been deprecated and why as the
first sentence of the DESCRIPTION clause.


7). Naming of the new Compliance Group

ifcpLclGatewaySessionGroupNoTrans

(original name:  ifcpLlGatewaySessionGroup)

The "NoTrans" suffix is not specific enough  because this
could stand for No Translation Mode  or No Transparent Mode,
in other words, please replace the "NoTrans" with
something definitive such as:

NoTranslationMode or NoTranslation


8) Security Considerations 

This section needs to be updated to reflect the deprecation of
the Translation Mode.  For example, the ifcpLclGtwyInstAddrTransMode
is mentioned and this is now deprecated.

--End of comments--