Document: draft-ietf-tewg-mib-08
Reviewer: Spencer Dawkins
Date: June 8, 2004

Summary: this document is clearly written and seems very
straightforward to implement. I had one question, and one
meta-question.

If you like the answers you get to these questions, the document is
ready for Proposed Standard.

Spencer

1. Introduction

   As it stands, this MIB module can only be used to configure or
   monitor a TE Tunnel at its ingress.  The extension of this module
for
   use at other points of a Tunnel is for further study.

Spencer: this seems like a pretty significant limitation. Is the idea
that you configure a TE tunnel at its ingress, and the tunnel ingress
router configures the rest of the tunnel routers using some other
mechanism not specified here? or that a management system configures
all of the tunnel routers using some other mechanism not specified
here? I guess what I'm asking is, is this document worth standardizing
with the restriction as stated?

3. Overview of the MIB Module

   teTunnelLastPathChange OBJECT-TYPE
       SYNTAX       TimeTicks
       MAX-ACCESS   read-only
       STATUS       current
       DESCRIPTION "The time in hundredths of a second since the last
                    path change occurred on this Tunnel.

                    Note that if the last transition was over 16
                    months ago, this value will be inaccurate.
                   "
       ::= { teTunnelEntry 22 }

   teTunnelConfiguredPaths OBJECT-TYPE

Spencer: not to be pedantic here, but is this the time since the
past path change occurred or the time since the last configuration
operation took place (if the configuration option did not change
the path from what was previously specified)?