A Traffic Engineering (TE) MIB
RFC 3970

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>, 
    tewg mailing list <te-wg@ops.ietf.org>, 
    tewg chair <tewg-chairs@tools.ietf.org>
Subject: Protocol Action: 'A Traffic Engineering MIB' to 
         Proposed Standard 

The IESG has approved the following document:

- 'A Traffic Engineering MIB '
   <draft-ietf-tewg-mib-09.txt> as a Proposed Standard

This document is the product of the Internet Traffic Engineering Working 
Group. 

The IESG contact persons are Bert Wijnen and Alex Zinin.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tewg-mib-09.txt

Technical Summary
 
   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it describes managed objects for Traffic Engineered
   Tunnels, for example, Multi-Protocol Label Switched Paths. 
Working Group Summary
 
   The WG has consensus to publish this doc as a Proposed Standard RFC.
 
Protocol Quality
 
   Bert Wijnen reviewed this document for the IESG

RFC-Editor note:

- Pls replace last para of Introduction (sect 1, page 3)

  OLD:
   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.
  NEW:
   As it stands, this MIB module can only be used to configure or
   monitor a TE Tunnel at its ingress.  The ingress is then expected
   to use some protocol (such as RSVP-TE) to signal the other routers
   in the path the information they need to set up the tunnel.  The
   extension of this module for use at other points of a Tunnel is for
   further study.

- Pls add some text (one sentence) to DESCRIPTION clause of 
  teTunnelLastPathChange on page 19.

  OLD:
    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 }
  NEW:
    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.

                     Path changes may be caused by network events or by
                     reconfiguration that affects the path.
                    "
        ::= { teTunnelEntry 22 }