MIB Dr. Review for draft-ietf-ccamp-gmpls-te-mib-14.txt

[<jcucchiara@mindspring.com>]

Hello Tom and Adrian,

Here are a few comments on
draft-ietf-ccamp-gmpls-te-mib-14.txt.
Thank you for the great updates.

Thanks,
-Joan


Compiles with both smicngPRO and smilint.

1) There is a disconnect in the numbers under the
under gmplsTeGroup, was this intentional, if so,
please explain, otherwise, please correct it.

1.3.6.1.2.1.10.166.555.3.1  gmplsTeGroups  [GMPLS-TE-STD-MIB]:
oid-value-assignment
1.3.6.1.2.1.10.166.555.3.1.1  gmplsTunnelGroup  [GMPLS-TE-STD-MIB]:
object-group
1.3.6.1.2.1.10.166.555.3.1.2  gmplsTunnelSignaledGroup  [GMPLS-TE-STD-MIB]:
object-group
1.3.6.1.2.1.10.166.555.3.1.3  gmplsTunnelScalarGroup  [GMPLS-TE-STD-MIB]:
object-group
1.3.6.1.2.1.10.166.555.3.1.6  gmplsTunnelOptionalGroup  [GMPLS-TE-STD-MIB]:
object-group
1.3.6.1.2.1.10.166.555.3.1.7  gmplsTeNotificationGroup  [GMPLS-TE-STD-MIB]:
notification-group


2) Expiration date in the page header is incorrect
Nadeau and Farrel             Expires April 2006             [Page 1]


3) 1.1. Migration Strategy
   "The gmplsTunnelLSPEncoding may be set to tunnelLspNotGmpls to allow an
   MPLS-TE LSP tunnel to benefit from the additional objects and tables
   of GMPLS-LSR-STD-MIB without supporting the GMPLS protocols.

Think you mean, GMPLS-TE-STD-MIB in the latter part of the above sentence.


4) 1.1. Migration Strategy
   "Textual conventions are defined in [RFC3811] and [GMPLSTCMIB]."

There aren't any TCs from GMPLSTCMIB, but there are
from the IANA-GMPLS-TC-MIB, so perhaps adding IANA-GMPLS-TC-MIB to this
statement would be appropriate.


5) (NIT) 2. Terminology

   "These segment and cross-connect objects are defined in the MPLS Label
   Switch Router MIB (MPLS-LSR-STD-MIB) [RFC3813], but see also the
   GMPLS Label Switch Router MIB (GMPLS-LSR-STD-MIB) [GMPLSLSRMIB] for..."

Please be sure to use "Label Switching Router" (and not Label Switch
Router).


6) Typos:
       gmplsTunnelLinkProtection

          This glag is set to indicate that the LSP should not use any
          link layer protection.

s/glag/flag

        shared
          This flage is set to indicate that a shared link layer

s/flage/flag



7)    gmplsTunnelErrorEntry OBJECT-TYPE


The use of the term "discontinuity" implies that the counters
suffered a discontinuity,but the situation you are describing is
that another error occurred.  Please rephrase this to something
like:

"Note that systems which read the objects in this table one at
a time should read gmplsTunnelErrorLastTime prior to the first
object and after reading the last object of this table to
ensure that no additional errors occurred."



8) gmplsTunnelUnnumIf does not appear in the
ReadOnly Conformance.

9) I am still unclear about what objects can be supported within
MPLS only.  Was expecting to see this clarified in the conformance
statements.  There does seem to be more of a division here than
in the GMPLS-LSR-STD-MIB.

Could some clarification be made to this point?

10)  IANA-GMPLS-TC-MIB

Would remove parts of the DESCRIPTION clauses which
refer to the GMPLS-TE-STD-MIB module.  The reason is
that these TCs may eventually be used in other MIB modules
and since this particular module will be controlled by
IANA, these sort of statements don't appear in IANA
MIB Modules as far as I know.

            "This data type is used as the syntax of the
             gmplsTunnelLSPEncoding object in the definition of
             GMPLS-TE-STD-MIB's gmplsTunnelTable."

            "This data type is used as the syntax of the
             gmplsTunnelSwitchingType object in the definition of
             GMPLS-TE-STD-MIB's gmplsTunnelTable."

            "This data type is used as the syntax of the
             gmplsTunnelGPid object in the definition of
             GMPLS-TE-STD-MIB's gmplsTunnelTable."

            "This data type is used as the syntax of the
             gmplsTunnelAdminStatusFlags object in the definition of
             GMPLS-TE-STD-MIB's gmplsTunnelTable."


-- the end --