RMONMIB WG minutes for IETF #62

OPS Area
RMONMIB WG Meeting Minutes
IETF #62
March 10, 2005
Minutes by Andy Bierman

Review Material
---------------

(A) draft-ietf-rmonmib-raqmon-framework-11.txt
(B) draft-ietf-rmonmib-raqmon-pdu-10.txt
(C) draft-ietf-rmonmib-raqmon-mib-07.txt
(D) draft-ietf-rmonmib-tpm-mib-14.txt
(E) draft-ietf-rmonmib-sspm-mib-12.txt
(F) draft-ietf-rmonmib-rmon2-v2-02.txt

Agenda
------

  1) WG Status
  2) RMON TimeFilter
  3) Real-time Application Quality of Service Monitoring

Minutes
-------

1) Working Group Status

The following work items have been completed by the WG, 
but not yet published as RFCs.

1.1) Advancement of RFC 2613 (SMON) to DS

The WG is currently waiting for IESG action for 
advancement to Draft Standard.  This action is on 
hold because RFC 2613 has a normative reference
to RFC 2021 (RMON-2).  It cannot advance until
RMON-2 advances to Draft Standard.

1.2) Advancement of RFC 2021 (RMON-2) to DS

The current draft of the RMON-2 MIB (F) will be updated when
the TimeFilter issues have been resolved.  (See sec. 2).
This draft should be updated within a month.

1.3) TPM-MIB

The TPM-MIB is approved and currently in the RFC Editor queue.
This document is held up due to a normative reference to the
IPPM-REGISTRY-MIB (in the tpmMetricDefGlobalID DESCRIPTION clause).
The IPPM-REGISTRY-MIB has been held up due to some minor issues.
The IANA work for that MIB should be done within two weeks and
the MIB published within two to six months.

>From TPM-MIB (D):
    tpmMetricDefGlobalID OBJECT-TYPE
        SYNTAX      OBJECT IDENTIFIER
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
            "This object contains a reference to the Object ID
            in a metrics registration MIB being developed
            in the IPPM WG at the IETF, e.g., the
            IPPM-REGISTRY-MIB [RFCXXX3], which defines the metric.
            In the event that this metric has no corresponding
            OID or until the IPPM-REGISTRY-MIB is defined, then
            the value should be set to 0.0 for none."
        ::= { tpmMetricDefEntry 6 }

Note the term "e.g.," in this description clause.  It is unclear
why this constitutes a normative rather than informative reference.
The object syntax is OBJECT IDENTIFIER to allow any registration
OID to be specified.  The WG never agreed to limit this object
contents to the IPPM Metric Registry.  Also, the DESCRIPTION text
needs to be updated, since the MIB is held up for the IPPM-REGISTRY-MIB,
the text "or until the IPPM-REGISTRY-MIB is defined" can be removed.

1.4) SSPM-MIB

The SSPM-MIB was approved in August and still in the RFC Editor queue.
This document is held up due to a normative reference to the
TPM-MIB in the IMPORTS clause.

2) RMON TimeFilter Issues

There has been an issued raised in the TimeFilter example
in the section 8 appendix.  The WG has two weeks to come up with
extended examples to demonstrate more complex TimeFilter processing 
than currently contained in the draft.  Otherwise the latest
TimeFilter text (see WG mailing list) will be used. 

3) Real-time Application Quality of Service Monitoring

The RAQMON Framework (A), RAQMON PDU (B), and RAQMON MIB (C)
documents were discussed together.  A presentation on these
drafts was given, explaining the changes from the last versions.
Refer to the slides for details on this presentation. 

There was a minor bug (type Unsigned 32 should be Integer32) introduced 
in the -07 version of the RAQMON-MIB.  In addition, some DESCRIPTION 
clause text regarding the size limit of an InetAddress object in an 
INDEX clause will be added.  The conformance section will be updated
to reflect the limited usage of InetAddress in this MIB.

The RAQMON documents have completed their final WG Last Calls.
When the MIB document is updated (-08), all three drafts will
be forwarded to the IESG for publication consideration as
Proposed Standard RFCs.