1. abierman-rmonwg-11dec00 1 RMONMIB WG 49th IETF San Diego, CA USA December 11 & 13, 2000 Discussion: rmonmib@ietf.org Admin: http://www.ietf.org/mailman/listinfo/rmonmib

2. abierman-rmonwg-11dec00 2 RMON WG Agenda -- I-Ds l (A) draft-bierman-rmonmib-vds-mib-01.txt l (B) draft-bullard-pcap-00.txt l (C) draft-ietf-rmonmib-apm-mib-02.txt l (D) draft-ietf-rmonmib-appverbs-01.txt l (E) draft-ietf-rmonmib-dsmon-mib-03.txt l (F) draft-ietf-rmonmib-hcrmon-06.txt l (G) draft-ietf-rmonmib-iftopn-mib-03.txt l (H) draft-ietf-rmonmib-tokenring-00.txt l (I) draft-ietf-rmonmib-tpm-mib-01.txt l (J) draft-kalbfleisch-sspmmib-01.txt

3. abierman-rmonwg-11dec00 3 RMON WG Agenda -- IETF 49 1) WG Status 2) Transport Performance Metrics MIB (I) 3) Application Performance Measurement MIB (C) 4) RMON Extensions for Identifying Application Protocol Verbs (D) 5) Token Ring Extensions to the RMON MIB (H) 6) RMON Extensions for Differentiated Services (E) 7) RMON Extensions for Interface Parameters Monitoring (G) 8) Remote Packet Capture (B) 9) Definition of Managed Objects for Synthetic Sources for Performance Monitoring Algorithms. (J) 10) RMON Extensions for Virtual Data Sources (A)

4. abierman-rmonwg-11dec00 4 RMONMIB WG Status (1/2) 1) Status of completed drafts »RMON Protocol Identifiers (Version 2) RFCs published in November 2000 –draft-ietf-rmonmib-rmonprot-ref-01.txt RFC 2895 - Standards Track (Proposed) –draft-ietf-rmonmib-rmonprot-mac-02.txt RFC 2896 - Informational

5. abierman-rmonwg-11dec00 5 RMONMIB WG Status (2/2) 1) Status of completed drafts »High Capacity RMON HC-TOPN issue resolved, need new HC-RMON I-D and FTP archive established –draft-ietf-rmonmib-hcrmon-06.txt is the latest real I-D –draft-ietf-rmonmib-hcrmon-07.txt published as expired I-D –draft-ietf-rmonmib-hcrmon-08.txt will be next version –draft-ietf-rmonmib-rmon2hc-00.txt will be removed –draft-ietf-rmonmib-rmonhc-00.txt will be removed –‘rmon2hc’ and ‘rmonhc’ MIB modules will be posted on IANA FTP site and referenced in HC-RMON

6. abierman-rmonwg-11dec00 6 TPM MIB 2) Transport Performance Metrics MIB »PM-CAPS I-D (draft-ietf-rmonmib-pmcaps-01.txt) is deleted –separate ‘capabilities’ BITS objects each MIB module (APM, TPM, SSPM). –dynamic study attributes only apply to TPM, so the ‘PM Study’ portion of this MIB will be adapted as needed, and moved to the TPM MIB. »need new draft with metrics soon!!!

7. abierman-rmonwg-11dec00 7 APP-VERBS I-D 4) RMON Extensions for Identifying Application Protocol Verbs (D) »Connect Verb –creation of implicit ‘connect(0)’ verb; reserved verb layer value ‘0.0.0.0’ –doesn’t change the number space for explicit verbs in the range ‘0.0.0.1’ to ‘0.255.255.255’ »SNMP Example fixed –‘report’ removed as a verb, since it is a response »HTTP verb added »Issues –need more verbs defined –split documents into REF and MAC like PI Macros v2?

8. abierman-rmonwg-11dec00 8 Verb Identifier Macro Format l construct is extended » = [ | ]… » = "VERB-IDENTIFIER” "DESCRIPTION" string [ "REFERENCE" string ] "::=" "{" "}” » = [ ",” ]… » = "(" ")"

9. abierman-rmonwg-11dec00 9 Verb Identifier Macro Example snmp VERB-IDENTIFIER DESCRIPTION "The set of verbs for SNMP is derived from the list of PDU transaction types in the Protocol Operations document for SNMPv2. Note that the ‘Response’ and ‘Report’ PDUs are not considered verbs, but are classified as belonging to the transaction type associated with the request PDU." REFERENCE "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2), RFC 1905, Section 3." ::= { get(1), get-next(2), get-bulk(3), set(4), inform-request(5), trap(6) }

10. abierman-rmonwg-11dec00 10 PD Index Encoding Example l The verbEnum value is encoded in the verb layer and the verbName is appended to the protocolDirDescr object l ether2.ip.udp.snmp »16.1.0.0.1.0.0.8.0.0.0.0.17.0.0.0.161.4.0.0.0.0 l ether2.ip.udp.snmp.get »20.1.0.0.1.0.0.8.0.0.0.0.17.0.0.0.161.0.0.0.1.5.0.0.0.0.0

11. abierman-rmonwg-11dec00 11 Verb Identifier Number Space l The encoded verbEnum value is a 24 bit value greater or equal to zero. l The most significant byte is reserved for future use and set to zero Verb Layer Format in protocolDirID 0abc

12. abierman-rmonwg-11dec00 12 TR-RMON MIB (1/3) 5) Token Ring Extensions to the RMON MIB (H) »CONTACT-INFO clause (for all WG I-Ds) – RMONMIB WG Chair abierman@cisco.com Editor RMONMIB WG Mailing List rmonmib@ietf.org List Admin: http://www.ietf.org/mailman/listinfo/rmonmib

13. abierman-rmonwg-11dec00 13 TR-RMON MIB (2/3) l More mailing list issues »global MIB: read-write vs. read-create –writable objects (tables w/ EntryStatus) are MAX- ACCESS read-write; should they be read-create instead? »history tables (ML-hist & P-hist) –the syntax of the snapshot deltas in SYNTAX Counter32. This should really be Gauge32. Should these tables be deprecated and redefined to fix this problem? Also broken in RMON1 etherHistoryTable (at Full Standard). »ringStationControlRingState OBJECT-TYPE macro –the 7 enums are not described at all and there is no REFERENCE clause.

14. abierman-rmonwg-11dec00 14 TR-RMON MIB (3/3) l More mailing list issues »ringStationStationStatus OBJECT-TYPE macro –the enums are described in ASN.1 comments. These comments should be moved to the DESCRIPTION clause. »Security Considerations section –no read-write objects are called out for special consideration. The ringStationConfigControlRemove object, which causes the agent to bump a station off the ring (by sending a Remove Station MAC frame) should be described here. »Smilint errors –lots of object descriptors longer than 32 characters

15. abierman-rmonwg-11dec00 15 DS-MON MIB (1/5) 6) RMON Extensions for Differentiated Services (E) »changes to -03 draft –a couple typos fixed –overflow counters STATUS now deprecated –new deprecated OBJECT-GROUPS created to contain the deprecated overflow counters »no ‘on-the-wire’ changes made »no real MIB changes –overflow counters were already optional, so changing the STATUS clause doesn’t impact conformance »deprecated could change to obsolete someday... –Each time the RFC is republished, the WG will decide if the deprecated status should be changed to obsolete for these overflow counters

16. abierman-rmonwg-11dec00 16 DS-MON MIB (2/5) l Mailing List Issues »DSMON Capabilities Object –Is there a way for NMS to check the High Capacity support for DSMON in the agent? Need DSMON Capabilities scalar object? »Why do we need time filter for dsmonPdistStatsTable? »dsmonPdistStatsEntry INDEX component order –pdist AggGroupIndex not the same place as Stats and Host groups

17. abierman-rmonwg-11dec00 17 DS-MON MIB (3/5) l Counter Table Indexing » DsmonStatsEntry –INDEX { dsmonStatsControlIndex, dsmonAggGroupIndex } »DsmonPdistStatsEntry –INDEX { dsmonPdistControlIndex, dsmonPdistTimeMark, protocolDirLocalIndex, dsmonAggGroupIndex } »DsmonHostEntry –INDEX { dsmonHostControlIndex, dsmonHostTimeMark, dsmonAggGroupIndex, protocolDirLocalIndex, dsmonHostAddress }

18. abierman-rmonwg-11dec00 18 DS-MON MIB (4/5) l smilint messages »./DSMON-MIB:1032: [4] object identifier name `dsmonPdistControlMaxDesiredEntries' longer than 32 characters »./DSMON-MIB:1461: [4] object identifier name `dsmonPdistTopNControlTimeRemaining' longer than 32 characters »./DSMON-MIB:1494: [4] object identifier name `dsmonPdistTopNControlGeneratedReports' longer than 32 characters »./DSMON-MIB:1526: [4] object identifier name `dsmonPdistTopNControlRequestedSize' longer than 32 characters »./DSMON-MIB:1881: [4] object identifier name `dsmonHostControlMaxDesiredEntries' longer than 32 characters »./DSMON-MIB:2546: [4] object identifier name `dsmonHostTopNControlTimeRemaining' longer than 32 characters

19. abierman-rmonwg-11dec00 19 DS-MON MIB (5/5) l smilint messages »./DSMON-MIB:2582: [4] object identifier name `dsmonHostTopNControlGeneratedReports' longer than 32 characters »./DSMON-MIB:2610: [4] object identifier name `dsmonHostTopNControlRequestedSize' longer than 32 characters »./DSMON-MIB:2170: [1] index element `dsmonHostAddress' of row `dsmonHostEntry' must have a size restriction »./DSMON-MIB:5: [6] identifier `Counter64' imported from module `SNMPv2-SMI' is never used

20. abierman-rmonwg-11dec00 20 IF-TOPN MIB (1/3) l Normalization Mechanisms »interfaceTopNNormalizationRequired –If the value of the object interfaceTopNSampleType is bandwidthPercentage(3), the object interfaceTopNNormalizationRequired cannot take the value 'true'. »interfaceTopNObjectSampleType OBJECT-TYPE –If the value of this object is bandwidthPercentage(3), the agent records the total number of octets sent over an interval divided by the total number of octets that represent '100% bandwidth’ for that interface. This ratio is multiplied by 1000 to retain a 3 digit integer (0..1000) in units of 'tenth of one percent'. This type of computation is accurate for the octet counters. The usage of this option with respect to packets or error counters is not recommended. »Seems like sampleType=bandwidthPercentage and normalization factor objects do the same thing. Why do we need both mechanisms?

21. abierman-rmonwg-11dec00 21 IF-TOPN MIB (2/3) l smilint messages »./INTERFACETOPN-MIB:97: [4] bit name `dot3StatsInternalMacTransmitErrors' longer than 32 characters »./INTERFACETOPN-MIB:100: [4] bit name `dot3StatsInternalMacReceiveErrors' longer than 32 characters »./INTERFACETOPN-MIB:567: [4] enumeration name `dot3StatsInternalMacTransmitErrors' longer than 32 characters »./INTERFACETOPN-MIB:570: [4] enumeration name `dot3StatsInternalMacReceiveErrors' longer than 32 characters »./INTERFACETOPN-MIB:685: [3] scalar object must not have a `read-create' access value »./INTERFACETOPN-MIB:688: [4] object identifier name `interfaceTopNNormalizationRequired' longer than 32 characters »./INTERFACETOPN-MIB:713: [3] scalar object must not have a `read-create' access value »./INTERFACETOPN-MIB:717: [6] use Integer32 instead of INTEGER in SMIv2

22. abierman-rmonwg-11dec00 22 IF-TOPN MIB (3/3) l smilint messages »./INTERFACETOPN-MIB:736: [3] scalar object must not have a `read-create' access value »./INTERFACETOPN-MIB:738: [4] object identifier name `interfaceTopNControlGeneratedReports' longer than 32 characters »./INTERFACETOPN-MIB:685: [1] unknown object identifier label `interfaceTopNObjectEntry’ »./INTERFACETOPN-MIB:1021: [3] node `interfaceTopNControlIndex' is an invalid member of group `interfaceTopNGroup’ »./INTERFACETOPN-MIB:1021: [3] node `interfaceTopNIndex' is an invalid member of group `interfaceTopNGroup’ »./INTERFACETOPN-MIB:6: [6] identifier `TEXTUAL-CONVENTION' imported from module `SNMPv2-TC' is never used »./INTERFACETOPN-MIB:10: [6] identifier `rmonConformance' imported from module `RMON2-MIB' is never used »./INTERFACETOPN-MIB:10: [6] identifier `probeConfig' imported from module `RMON2-MIB' is never used

23. abierman-rmonwg-11dec00 23 VDS MIB 10) RMON Extensions for Virtual Data Sources (A) »changes from -00 draft –Virtual Circuit (DLCI) selection mechanism removed since DLCIs will be monitored via individual ifIndex assignments –StorageType object added to each control table –IP Precedence support added to the vdsQosSelTable, by defining a new 'ipPrecedence' enumeration for the vdsQosSelType object –URL Query String selection support added to the vdsUrlSelTable, by defining a new 'urlQueryString' BIT field for the vdsUrlSelMatchFields object