idnits 2.17.1 draft-ietf-rtfm-meter-mib-10.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 2) being 94 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 50 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. == There are 2 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 1737 has weird spacing: '...taValue flow...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (February 2000) is 8836 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Downref: Normative reference to an Informational RFC: RFC 1272 (ref. 'ACT-BKG') ** Obsolete normative reference: RFC 1700 (ref. 'ASG-NBR') (Obsoleted by RFC 3232) -- Possible downref: Non-RFC (?) normative reference: ref. 'ASN-1' -- Possible downref: Non-RFC (?) normative reference: ref. 'ASN-BER' ** Obsolete normative reference: RFC 1643 (ref. 'ENET-OBJ') (Obsoleted by RFC 3638) -- Possible downref: Non-RFC (?) normative reference: ref. 'FDDI-MIB' ** Downref: Normative reference to an Informational RFC: RFC 2330 (ref. 'IPPM-FRM') ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 1908 (Obsoleted by RFC 2576) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2021 (ref. 'RMON2-MIB') (Obsoleted by RFC 4502) ** Obsolete normative reference: RFC 2063 (ref. 'RTFM-ARC') (Obsoleted by RFC 2722) ** Obsolete normative reference: RFC 2373 (ref. 'V6-ADDR') (Obsoleted by RFC 3513) Summary: 21 errors (**), 0 flaws (~~), 5 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Engineering Task Force Nevil Brownlee 2 INTERNET-DRAFT The University of Auckland 4 August 1999 5 Expires February 2000 7 Traffic Flow Measurement: Meter MIB 9 11 Status of this Memo 13 This document is an Internet-Draft and is in full conformance with all 14 provisions of Section 10 of RFC 2026. 16 Internet-Drafts are working documents of the Internet Engineering Task 17 Force (IETF), its areas, and its working groups. Note that other groups 18 may also distribute working documents as Internet-Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet-Drafts as reference material 23 or to cite them other than as "work in progress." 25 The list of current Internet-Drafts can be accessed at 26 http://www.ietf.org/ietf/1id-abstracts.txt 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html. 31 This Internet Draft is a product of the Realtime Traffic Flow 32 Measurement Working Group of the IETF. 34 Abstract 36 The RTFM Traffic Measurement Architecture provides a general framework 37 for describing and measuring network traffic flows. Flows are defined 38 in terms of their Address Attribute values and measured by a 'Traffic 39 Meter.' 41 This document defines a Management Information Base (MIB) for use in 42 controlling an RTFM Traffic Meter, in particular for specifying the 43 flows to be measured. It also provides an efficient mechanism for 44 retrieving flow data from the meter using SNMP. Security issues 45 concerning the operation of traffic meters are summarised. 47 Contents 49 1 Introduction 2 51 2 The SNMP Management Framework 2 53 3 Overview 3 54 3.1 Scope of Definitions, Textual Conventions . . . . . . . . . . 4 55 3.2 Usage of the MIB variables . . . . . . . . . . . . . . . . . 4 57 4 Definitions 6 59 5 Security Considerations 44 60 5.1 SNMP Concerns . . . . . . .. . . . . . . . . . . . . . . . . 44 61 5.2 Traffic Meter Concerns . .. . . . . . . . . . . . . . . . . 45 63 6 IANA Considerations 46 65 7 Appendix A: Changes Introduced Since RFC 2064 47 67 8 Acknowledgements 48 69 9 References 48 71 10 Author's Address 50 73 1 Introduction 75 This memo defines a portion of the Management Information Base (MIB) for 76 use with network management protocols in the Internet community. In 77 particular, it describes objects for managing and collecting data from 78 network Realtime Traffic Flow Meters, as described in [RTFM-ARC]. 80 The MIB is 'basic' in the sense that it provides more than enough 81 information for everyday traffic measurment. Furthermore, it can be 82 easily extended by adding new attributes as required. The RTFM Working 83 group is actively pursuing the development of the meter in this way. 85 2 The SNMP Management Framework 87 The SNMP Management Framework presently consists of five major 88 components: 90 - An overall architecture, described in RFC 2571 [RFC2571]. 92 - Mechanisms for describing and naming objects and events for the 93 purpose of management. The first version of this Structure of 94 Management Information (SMI) is called SMIv1 and described in STD 95 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 96 [RFC1215]. The second version, called SMIv2, is described in STD 97 58, RFC 2578 [RFC2578], RFC 2579 [RFC2579] and RFC 2580 [RFC2580]. 99 - Message protocols for transferring management information. The 100 first version of the SNMP message protocol is called SNMPv1 and 101 described in STD 15, RFC 1157 [RFC1157]. A second version of the 102 SNMP message protocol, which is not an Internet standards track 103 protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] and 104 RFC 1906 [RFC1906]. The third version of the message protocol is 105 called SNMPv3 and described in RFC 1906 [RFC1906], RFC 2572 106 [RFC2572] and RFC 2574 [RFC2574]. 108 - Protocol operations for accessing management information. The 109 first set of protocol operations and associated PDU formats is 110 described in STD 15, RFC 1157 [RFC1157]. A second set of protocol 111 operations and associated PDU formats is described in RFC 1905 112 [RFC1905]. 114 - A set of fundamental applications described in RFC 2573 [RFC2573] 115 and the view-based access control mechanism described in RFC 2575 116 [RFC2575]. 118 A more detailed introduction to the current SNMP Management Framework 119 can be found in [RFC2570]. 121 Managed objects are accessed via a virtual information store, termed the 122 Management Information Base or MIB. Objects in the MIB are defined using 123 the mechanisms defined in the SMI. 125 This memo specifies a MIB module that is compliant to the SMIv2. A 126 MIB conforming to the SMIv1 can be produced through the appropriate 127 translations. The resulting translated MIB must be semantically 128 equivalent, except where objects or events are omitted because no 129 translation is possible (use of Counter64). Some machine readable 130 information in SMIv2 will be converted into textual descriptions in 131 SMIv1 during the translation process. However, this loss of machine 132 readable information is not considered to change the semantics of the 133 MIB. 135 3 Overview 137 Traffic Flow Measurement seeks to provide a well-defined method for 138 gathering traffic flow information from networks and internetworks. The 139 background for this is given in "Internet Accounting Background" 140 [ACT-BKG]. The Realtime Traffic Flow Measurement (rtfm) Working Group 141 has produced a measurement architecture to achieve this goal; this is 142 documented in "Traffic Flow Measurement: Architecture" [RTFM-ARC]. The 143 architecture defines three entities: 145 - METERS, which observe network traffic flows and build up a table of 146 flow data records for them, 148 - METER READERS, which collect traffic flow data from meters, and 150 - MANAGERS, which oversee the operation of meters and meter readers. 152 This memo defines the SNMP management information for a Traffic Flow 153 Meter (TFM). Work in this field was begun by the Internet Accounting 154 Working Group. It has been further developed and expanded by the 155 Realtime Traffic Flow Measurement Working Group. 157 3.1 Scope of Definitions, Textual Conventions 159 All objects defined in this memo are registered in a single subtree 160 within the mib-2 namespace [MIB-II, RFC2578], and are for use in network 161 devices which may perform a PDU forwarding or monitoring function. For 162 these devices, this MIB defines a group of objects with an SMI Network 163 Management MGMT Code [ASG-NBR] of 40, i.e. 165 flowMIB OBJECT IDENTIFIER ::= mib-2 40 167 as defined below. 169 The RTFM Meter MIB was first produced and tested using SNMPv1. It was 170 converted into SNMPv2 following the guidelines in [RFC1908]. 172 3.2 Usage of the MIB variables 174 The MIB is organised in four parts - control, data, rules and 175 conformance statements. 177 The rules implement the set of packet-matching actions, as described in 178 the "Traffic Flow Measurment: Architecture" document [RTFM-ARC]. In 179 addition they provide for BASIC-style subroutines, allowing a network 180 manager to dramatically reduce the number of rules required to monitor a 181 large network. 183 Traffic flows are identified by a set of attributes for each of their 184 end-points. Attributes include network addresses for each layer of the 185 network protocol stack, and 'subscriber ids,' which may be used to 186 identify an accountable entity for the flow. 188 The conformance statements are set out as defined in [RFC2580]. They 189 explain what must be implemented in a meter which claims to conform to 190 this MIB. 192 To retrieve flow data one could simply do a linear scan of the flow 193 table. This would certainly work, but would require a lot of protocol 194 exchanges. To reduce the overhead in retrieving flow data the flow 195 table uses a TimeFilter variable, defined as a Textual Convention in the 196 RMON2 MIB [RMON2-MIB]. 198 As an alternative method of reading flow data, the MIB provides a view 199 of the flow table called the flowDataPackageTable. This is (logically) 200 a four-dimensional array, subscripted by package selector, RuleSet, 201 activity time and starting flow number. The package selector is a 202 sequence of bytes which specifies a list of flow attributes. 204 A data package (as returned by the meter) is a sequence of values for 205 the attributes specified in its selector, encoded using the Basic 206 Encoding Rules [ASN-BER]. It allows a meter reader to retrieve all the 207 attribute values it requires in a single MIB object. This, when used 208 together with SNMPv2's GetBulk request, allows a meter reader to scan 209 the flow table and upload a specified set of attribute values for flows 210 which have changed since the last reading, and which were created by a 211 specified rule set. 213 One aspect of data collection which needs emphasis is that all the MIB 214 variables are set up to allow multiple independent meter readers to work 215 properly, i.e. the flow table indexes are stateless. An alternative 216 approach would have been to 'snapshot' the flow table, which would mean 217 that the meter readers would have to be synchronized. The stateless 218 approach does mean that two meter readers will never return exactly the 219 same set of traffic counts, but over long periods (e.g. 15-minute 220 collections over a day) the discrepancies are acceptable. If one really 221 needs a snapshot, this can be achieved by switching to an identical rule 222 set with a different RuleSet number, hence asynchronous collections may 223 be regarded as a useful generalisation of synchronised ones. 225 The control variables are the minimum set required for a meter reader. 226 Their number has been whittled down as experience has been gained with 227 the MIB implementation. A few of them are 'general,' i.e. they control 228 the overall behaviour of the meter. These are set by a single 'master' 229 manager, and no other manager should attempt to change their values. 230 The decision as to which manager is the 'master' must be made by the 231 network operations personnel responsible; this MIB does not attempt to 232 define any interaction between managers. 234 There are three other groups of control variables, arranged into tables 235 in the same way as in the RMON2 MIB [RMON2-MIB]. They are used as 236 follows: 238 - RULE SET INFO: Before attempting to download a RuleSet, a manager 239 must create a row in the flowRuleSetInfoTable and set its 240 flowRuleInfoSize to a value large enough to hold the RuleSet. When 241 the rule set is ready the manager must set flowRuleInfoRulesReady 242 to 'true,' indicating that the rule set is ready for use (but not 243 yet 'running'). 245 - METER READER INFO: Any meter reader wishing to collect data 246 reliably for all flows from a RuleSet should first create a row in 247 the flowReaderInfoTable with flowReaderRuleSet set to that 248 RuleSet's index in the flowRuleSetInfoTable. It should write that 249 row's flowReaderLastTime object each time it starts a collection 250 pass through the flow table. The meter will not recover a flow's 251 memory until every meter reader holding a row for that flow's 252 RuleSet has collected the flow's data. 254 - MANAGER INFO: Any manager wishing to run a RuleSet in the meter 255 must create a row in the flowManagerInfo table, specifying the 256 desired RuleSet to run and its corresponding 'standby' RuleSet (if 257 one is desired). A current RuleSet is 'running' if its 258 flowManagerRunningStandby value is false(2), similarly a standby 259 RuleSet is 'running' if flowManagerRunningStandby is true(1). 261 Times within the meter are in terms of its Uptime, i.e. centiseconds 262 since the meter started. For meters implemented as self-contained SNMP 263 agents this will be the same as sysUptime, but this may not be true for 264 meters implemented as subagents. Managers can read the meter's Uptime 265 when neccessary (e.g. to set a TimeFilter value) by setting 266 flowReaderLastTime, then reading its new value. 268 4 Definitions 270 FLOW-METER-MIB DEFINITIONS ::= BEGIN 272 IMPORTS 273 MODULE-IDENTITY, OBJECT-TYPE, 274 Counter32, Counter64, Integer32, mib-2 275 FROM SNMPv2-SMI 276 TEXTUAL-CONVENTION, RowStatus, TimeStamp, TruthValue 277 FROM SNMPv2-TC 278 OBJECT-GROUP, MODULE-COMPLIANCE 279 FROM SNMPv2-CONF 280 ifIndex 281 FROM RFC1213-MIB 282 OwnerString 283 FROM RMON-MIB 284 TimeFilter 285 FROM RMON2-MIB; 287 flowMIB MODULE-IDENTITY 288 LAST-UPDATED "9908191010Z" 289 ORGANIZATION "IETF Realtime Traffic Flow Measurement Working Group" 290 CONTACT-INFO 291 "Nevil Brownlee, The University of Auckland 293 Postal: Information Technology Sytems & Services 294 The University of Auckland 295 Private Bag 92-019 296 Auckland, New Zealand 298 Phone: +64 9 373 7599 x8941 299 E-mail: n.brownlee@auckland.ac.nz" 300 DESCRIPTION 301 "MIB for the RTFM Traffic Flow Meter." 303 REVISION "9908191010Z" 304 DESCRIPTION 305 "Changes to SIZE specification for two variables: 306 - flowRuleInfoName SIZE specified as (0..127) 307 - flowRuleIndex SIZE increased to (1..2147483647)" 309 REVISION "9712230937Z" 310 DESCRIPTION 311 "Two further variables deprecated: 312 - flowRuleInfoRulesReady (use flowRuleInfoStatus intead) 313 - flowDataStatus (contains no useful information)" 315 REVISION "9707071715Z" 316 DESCRIPTION 317 "Significant changes since RFC 2064 include: 318 - flowDataPackageTable added 319 - flowColumnActivityTable deprecated 320 - flowManagerCounterWrap deprecated" 322 REVISION "9603080208Z" 323 DESCRIPTION 324 "Initial version of this MIB (RFC 2064)" 325 ::= { mib-2 40 } 327 flowControl OBJECT IDENTIFIER ::= { flowMIB 1 } 329 flowData OBJECT IDENTIFIER ::= { flowMIB 2 } 331 flowRules OBJECT IDENTIFIER ::= { flowMIB 3 } 333 flowMIBConformance OBJECT IDENTIFIER ::= { flowMIB 4 } 334 -- Textual Conventions 336 MediumType ::= TEXTUAL-CONVENTION 337 STATUS current 338 DESCRIPTION 339 "Specifies the type of a MediumAddress (see below). The 340 values used for IEEE 802 media are from the 'Network 341 Management Parameters (ifType definitions)' section of the 342 Assigned Numbers RFC [ASG-NBR]. Other medium types may also 343 be used, provided only that they are identified by their 344 assigned ifType numbers." 345 SYNTAX INTEGER { 346 ethernet(7), -- ethernet-like [ENET-OBJ], 347 -- includes ethernet-csmacd(6) 348 tokenring(9), 349 fddi(15) } 351 MediumAddress ::= TEXTUAL-CONVENTION 352 STATUS current 353 DESCRIPTION 354 "Specifies the value of a Medium Access Control (MAC) address. 355 Address format depends on the actual medium, as follows: 357 Ethernet: ethernet(7) 358 6-octet 802.3 MAC address in 'canonical' order 360 Token Ring: tokenring(9) 361 6-octet 802.5 MAC address in 'canonical' order 363 FDDI: fddi(15) 364 FddiMACLongAddress, i.e. a 6-octet MAC address 365 in 'canonical' order (defined in [FDDI-MIB]) 366 " 367 SYNTAX OCTET STRING (SIZE (6..20)) 369 PeerType ::= TEXTUAL-CONVENTION 370 STATUS current 371 DESCRIPTION 372 "Indicates the type of a PeerAddress (see below). The values 373 used are from the 'Address Family Numbers' section of the 374 Assigned Numbers RFC [ASG-NBR]. Peer types from other address 375 families may also be used, provided only that they are 376 identified by their assigned Address Family numbers." 377 SYNTAX INTEGER { 378 ipv4(1), 379 ipv6(2), 380 nsap(3), 381 ipx(11), 382 appletalk(12), 383 decnet(13) } 385 PeerAddress ::= TEXTUAL-CONVENTION 386 STATUS current 387 DESCRIPTION 388 "Specifies the value of a peer address for various network 389 protocols. Address format depends on the actual protocol, 390 as indicated below: 392 IPv4: ipv4(1) 393 4-octet IpAddress (defined in the SNMPv2 SMI [RFC2578]) 395 IPv6: ipv6(2) 396 16-octet IpAddress (defined in the 397 IPv6 Addressing RFC [V6-ADDR]) 399 CLNS: nsap(3) 400 NsapAddress (defined in the SNMPv2 SMI [RFC2578]) 402 Novell: ipx(11) 403 4-octet Network number, 404 6-octet Host number (MAC address) 406 AppleTalk: appletalk(12) 407 2-octet Network number (sixteen bits), 408 1-octet Host number (eight bits) 410 DECnet: decnet(13) 411 1-octet Area number (in low-order six bits), 412 2-octet Host number (in low-order ten bits) 413 " 414 SYNTAX OCTET STRING (SIZE (3..20)) 416 AdjacentType ::= TEXTUAL-CONVENTION 417 STATUS current 418 DESCRIPTION 419 "Indicates the type of an adjacent address. 420 Is a superset of MediumType and PeerType." 421 SYNTAX INTEGER { 422 ip(1), 423 nsap(3), 424 ethernet(7), 425 tokenring(9), 426 ipx(11), 427 appletalk(12), 428 decnet(13), 429 fddi(15) } 431 AdjacentAddress ::= TEXTUAL-CONVENTION 432 STATUS current 433 DESCRIPTION 434 "Specifies the value of an adjacent address. 435 Is a superset of MediumAddress and PeerAddress." 436 SYNTAX OCTET STRING (SIZE (3..20)) 438 TransportType ::= TEXTUAL-CONVENTION 439 STATUS current 440 DESCRIPTION 441 "Indicates the type of a TransportAddress (see below). Values 442 will depend on the actual protocol; for IP they will be those 443 given in the 'Protocol Numbers' section of the Assigned Numbers 444 RFC [ASG-NBR], including icmp(1), tcp(6) and udp(17)." 445 SYNTAX Integer32 (1..255) 447 TransportAddress ::= TEXTUAL-CONVENTION 448 STATUS current 449 DESCRIPTION 450 "Specifies the value of a transport address for various 451 network protocols. Format as follows: 453 IP: 454 2-octet UDP or TCP port number 456 Other protocols: 457 2-octet port number 458 " 459 SYNTAX OCTET STRING (SIZE (2)) 461 RuleAddress ::= TEXTUAL-CONVENTION 462 STATUS current 463 DESCRIPTION 464 "Specifies the value of an address. Is a superset of 465 MediumAddress, PeerAddress and TransportAddress." 466 SYNTAX OCTET STRING (SIZE (2..20)) 468 FlowAttributeNumber ::= TEXTUAL-CONVENTION 469 STATUS current 470 DESCRIPTION 471 "Uniquely identifies an attribute within a flow data record." 472 SYNTAX INTEGER { 473 flowIndex(1), 474 flowStatus(2), 475 flowTimeMark(3), 477 sourceInterface(4), 478 sourceAdjacentType(5), 479 sourceAdjacentAddress(6), 480 sourceAdjacentMask(7), 481 sourcePeerType(8), 482 sourcePeerAddress(9), 483 sourcePeerMask(10), 484 sourceTransType(11), 485 sourceTransAddress(12), 486 sourceTransMask(13), 488 destInterface(14), 489 destAdjacentType(15), 490 destAdjacentAddress(16), 491 destAdjacentMask(17), 492 destPeerType(18), 493 destPeerAddress(19), 494 destPeerMask(20), 495 destTransType(21), 496 destTransAddress(22), 497 destTransMask(23), 499 pduScale(24), 500 octetScale(25), 502 ruleSet(26), 503 toOctets(27), -- Source-to-Dest 504 toPDUs(28), 505 fromOctets(29), -- Dest-to-Source 506 fromPDUs(30), 507 firstTime(31), -- Activity times 508 lastActiveTime(32), 510 sourceSubscriberID(33), -- Subscriber ID 511 destSubscriberID(34), 512 sessionID(35), 514 sourceClass(36), -- Computed attributes 515 destClass(37), 516 flowClass(38), 517 sourceKind(39), 518 destKind(40), 519 flowKind(41) } 521 RuleAttributeNumber ::= TEXTUAL-CONVENTION 522 STATUS current 523 DESCRIPTION 524 "Uniquely identifies an attribute which may be tested in 525 a rule. These include attributes whose values come directly 526 from (or are computed from) the flow's packets, and the five 527 'meter' variables used to hold an Attribute Number." 528 SYNTAX INTEGER { 529 null(0), 530 sourceInterface(4), -- Source Address 531 sourceAdjacentType(5), 532 sourceAdjacentAddress(6), 533 sourcePeerType(8), 534 sourcePeerAddress(9), 535 sourceTransType(11), 536 sourceTransAddress(12), 538 destInterface(14), -- Dest Address 539 destAdjacentType(15), 540 destAdjacentAddress(16), 541 destPeerType(18), 542 destPeerAddress(19), 543 destTransType(21), 544 destTransAddress(22), 546 sourceSubscriberID(33), -- Subscriber ID 547 destSubscriberID(34), 548 sessionID(35), 550 sourceClass(36), -- Computed attributes 551 destClass(37), 552 flowClass(38), 553 sourceKind(39), 554 destKind(40), 555 flowKind(41), 557 matchingStoD(50), -- Packet matching 559 v1(51), -- Meter variables 560 v2(52), 561 v3(53), 562 v4(54), 563 v5(55) } 565 ActionNumber ::= TEXTUAL-CONVENTION 566 STATUS current 567 DESCRIPTION 568 "Uniquely identifies the action of a rule, i.e. the Pattern 569 Matching Engine's opcode number. Details of the opcodes 570 are given in the 'Traffic Flow Measurement: Architecture' 571 document [RTFM-ARC]." 572 SYNTAX INTEGER { 573 ignore(1), 574 noMatch(2), 575 count(3), 576 countPkt(4), 577 return(5), 578 gosub(6), 579 gosubAct(7), 580 assign(8), 581 assignAct(9), 582 goto(10), 583 gotoAct(11), 584 pushRuleTo(12), 585 pushRuleToAct(13), 586 pushPktTo(14), 587 pushPktToAct(15), 588 popTo(16), 589 popToAct(17) } 591 -- 592 -- Control Group: RuleSet Info Table 593 -- 595 flowRuleSetInfoTable OBJECT-TYPE 596 SYNTAX SEQUENCE OF FlowRuleSetInfoEntry 597 MAX-ACCESS not-accessible 598 STATUS current 599 DESCRIPTION 600 "An array of information about the RuleSets held in the 601 meter. 603 Any manager may configure a new RuleSet for the meter by 604 creating a row in this table with status active(1), and setting 605 values for all the objects in its rules. At this stage the new 606 RuleSet is available but not 'running,' i.e. it is not being 607 used by the meter to produce entries in the flow table. 609 To actually 'run' a RuleSet a manager must create a row in 610 the flowManagerInfoTable, set it's flowManagerStatus to 611 active(1), and set either its CurrentRuleSet or StandbyRuleSet 612 to point to the RuleSet to be run. 614 Once a RuleSet is running a manager may not change any of the 615 objects within the RuleSet itself. Any attempt to do so should 616 result in a notWritable(17) SNMP error-status for such objects. 618 A manager may stop a RuleSet running by removing all 619 references to it in the flowManagerInfoTable (i.e. by setting 620 CurrentRuleSet and StandbyRuleSet values to 0). This provides 621 a way to stop RuleSets left running if a manager fails. 622 For example, when a manager is started, it could search the 623 meter's flowManager table and stop all RuleSets having a 624 specified value of flowRuleInfoOwner. 626 To prevent a manager from interfering with variables belonging 627 to another manager, the meter should use MIB views [RFC2575] so 628 as to limit each manager's access to the meter's variables, 629 effectively dividing the single meter into several virtual 630 meters, one for each independent manager." 631 ::= { flowControl 1 } 633 flowRuleSetInfoEntry OBJECT-TYPE 634 SYNTAX FlowRuleSetInfoEntry 635 MAX-ACCESS not-accessible 636 STATUS current 637 DESCRIPTION 638 "Information about a particular RuleSet." 639 INDEX { flowRuleInfoIndex } 640 ::= { flowRuleSetInfoTable 1 } 642 FlowRuleSetInfoEntry ::= SEQUENCE { 643 flowRuleInfoIndex Integer32, 644 flowRuleInfoSize Integer32, 645 flowRuleInfoOwner OwnerString, 646 flowRuleInfoTimeStamp TimeStamp, 647 flowRuleInfoStatus RowStatus, 648 flowRuleInfoName OCTET STRING, 649 flowRuleInfoRulesReady TruthValue, 650 flowRuleInfoFlowRecords Integer32 651 } 653 flowRuleInfoIndex OBJECT-TYPE 654 SYNTAX Integer32 (1..2147483647) 655 MAX-ACCESS not-accessible 656 STATUS current 657 DESCRIPTION 658 "An index which selects an entry in the flowRuleSetInfoTable. 659 Each such entry contains control information for a particular 660 RuleSet which the meter may run." 661 ::= { flowRuleSetInfoEntry 1 } 663 flowRuleInfoSize OBJECT-TYPE 664 SYNTAX Integer32 665 MAX-ACCESS read-create 666 STATUS current 667 DESCRIPTION 668 "Number of rules in this RuleSet. Setting this variable will 669 cause the meter to allocate space for these rules." 670 ::= { flowRuleSetInfoEntry 2 } 672 flowRuleInfoOwner OBJECT-TYPE 673 SYNTAX OwnerString 674 MAX-ACCESS read-create 675 STATUS current 676 DESCRIPTION 677 "Identifies the manager which 'owns' this RuleSet. A manager 678 must set this variable when creating a row in this table." 679 ::= { flowRuleSetInfoEntry 3 } 681 flowRuleInfoTimeStamp OBJECT-TYPE 682 SYNTAX TimeStamp 683 MAX-ACCESS read-only 684 STATUS current 685 DESCRIPTION 686 "Time this row's associated RuleSet was last changed." 687 ::= { flowRuleSetInfoEntry 4 } 689 flowRuleInfoStatus OBJECT-TYPE 690 SYNTAX RowStatus 691 MAX-ACCESS read-create 692 STATUS current 693 DESCRIPTION 694 "The status of this flowRuleSetInfoEntry. If this value is 695 not active(1) the meter must not attempt to use the row's 696 associated RuleSet. Once its value has been set to active(1) 697 a manager may not change any of the other variables in the 698 row, nor the contents of the associated uleSet. Any attempt 699 to do so should result in a notWritable(17) SNMP error-status 700 for such variables or objects. 702 To download a RuleSet, a manger could: 703 - Locate an open slot in the RuleSetInfoTable. 704 - Create a RuleSetInfoEntry by setting the status for this 705 open slot to createAndWait(5). 706 - Set flowRuleInfoSize and flowRuleInfoName as required. 707 - Download the rules into the row's rule table. 708 - Set flowRuleInfoStatus to active(1). 710 The RuleSet would then be ready to run. The manager is not 711 allowed to change the value of flowRuleInfoStatus from 712 active(1) if the associated RuleSet is being referenced by any 713 of the entries in the flowManagerInfoTable. 715 Setting RuleInfoStatus to destroy(6) destroys the associated 716 RuleSet together with any flow data collected by it." 717 ::= { flowRuleSetInfoEntry 5 } 719 flowRuleInfoName OBJECT-TYPE 720 SYNTAX OCTET STRING (SIZE (0..127)) 721 MAX-ACCESS read-create 722 STATUS current 723 DESCRIPTION 724 "An alphanumeric identifier used by managers and readers to 725 identify a RuleSet. For example, a manager wishing to run a 726 RuleSet named WWW-FLOWS could search the flowRuleSetInfoTable 727 to see whether the WWW-FLOWS RuleSet is already available on 728 the meter. 730 Note that references to RuleSets in the flowManagerInfoTable 731 use indexes for their flowRuleSetInfoTable entries. These may 732 be different each time the RuleSet is loaded into a meter." 734 ::= { flowRuleSetInfoEntry 6 } 736 flowRuleInfoRulesReady OBJECT-TYPE 737 SYNTAX TruthValue 738 MAX-ACCESS read-create 739 STATUS deprecated 740 DESCRIPTION 741 "Indicates whether the rules for this row's associated RuleSet 742 are ready for use. The meter will refuse to 'run' the RuleSet 743 unless this variable has been set to true(1). 744 While RulesReady is false(2), the manager may modify the 745 RuleSet, for example by downloading rules into it." 746 ::= { flowRuleSetInfoEntry 7 } 748 flowRuleInfoFlowRecords OBJECT-TYPE 749 SYNTAX Integer32 750 MAX-ACCESS read-only 751 STATUS current 752 DESCRIPTION 753 "The number of entries in the flow table for this RuleSet. 754 These may be current (waiting for collection by one or more 755 meter readers) or idle (waiting for the meter to recover 756 their memory)." 757 ::= { flowRuleSetInfoEntry 8 } 759 -- 760 -- Control Group: Interface Info Table 761 -- 763 flowInterfaceTable OBJECT-TYPE 764 SYNTAX SEQUENCE OF FlowInterfaceEntry 765 MAX-ACCESS not-accessible 766 STATUS current 767 DESCRIPTION 768 "An array of information specific to each meter interface." 769 ::= { flowControl 2 } 771 flowInterfaceEntry OBJECT-TYPE 772 SYNTAX FlowInterfaceEntry 773 MAX-ACCESS not-accessible 774 STATUS current 775 DESCRIPTION 776 "Information about a particular interface." 777 INDEX { ifIndex } 778 ::= { flowInterfaceTable 1 } 780 FlowInterfaceEntry ::= SEQUENCE { 781 flowInterfaceSampleRate Integer32, 782 flowInterfaceLostPackets Counter32 783 } 785 flowInterfaceSampleRate OBJECT-TYPE 786 SYNTAX Integer32 787 MAX-ACCESS read-write 788 STATUS current 789 DESCRIPTION 790 "The parameter N for statistical counting on this interface. 791 Set to N to count 1/Nth of the packets appearing at this 792 interface. A sampling rate of 1 counts all packets. 793 A sampling rate of 0 results in the interface being ignored 794 by the meter. 796 A meter should choose its own algorithm to introduce variance 797 into the sampling so that exactly every Nth packet is counted. 798 The IPPM Working Group's RFC 'Framework for IP Performance 799 Metrics' [IPPM-FRM] explains why this should be done, and sets 800 out an algorithm for doing it." 801 DEFVAL { 1 } 802 ::= { flowInterfaceEntry 1 } 804 flowInterfaceLostPackets OBJECT-TYPE 805 SYNTAX Counter32 806 MAX-ACCESS read-only 807 STATUS current 808 DESCRIPTION 809 "The number of packets the meter has lost for this interface. 810 Such losses may occur because the meter has been unable to 811 keep up with the traffic volume." 812 ::= { flowInterfaceEntry 2 } 814 -- 815 -- Control Group: Meter Reader Info Table 816 -- 818 -- Any meter reader wishing to collect data reliably for flows 819 -- should first create a row in this table. It should write that 820 -- row's flowReaderLastTime object each time it starts a collection 821 -- pass through the flow table. 823 -- If a meter reader (MR) does not create a row in this table, e.g. 824 -- because its MIB view [RFC2575] did not allow MR create access to 825 -- flowReaderStatus, collection can still proceed but the meter will 826 -- not be aware of meter reader MR. This could lead the meter to 827 -- recover flows before they have been collected by MR. 829 flowReaderInfoTable OBJECT-TYPE 830 SYNTAX SEQUENCE OF FlowReaderInfoEntry 831 MAX-ACCESS not-accessible 832 STATUS current 833 DESCRIPTION 834 "An array of information about meter readers which have 835 registered their intent to collect flow data from this meter." 836 ::= { flowControl 3 } 838 flowReaderInfoEntry OBJECT-TYPE 839 SYNTAX FlowReaderInfoEntry 840 MAX-ACCESS not-accessible 841 STATUS current 842 DESCRIPTION 843 "Information about a particular meter reader." 844 INDEX { flowReaderIndex } 845 ::= { flowReaderInfoTable 1 } 847 FlowReaderInfoEntry ::= SEQUENCE { 848 flowReaderIndex Integer32, 849 flowReaderTimeout Integer32, 850 flowReaderOwner OwnerString, 851 flowReaderLastTime TimeStamp, 852 flowReaderPreviousTime TimeStamp, 853 flowReaderStatus RowStatus, 854 flowReaderRuleSet Integer32 855 } 857 flowReaderIndex OBJECT-TYPE 858 SYNTAX Integer32 (1..2147483647) 859 MAX-ACCESS not-accessible 860 STATUS current 861 DESCRIPTION 862 "An index which selects an entry in the flowReaderInfoTable." 863 ::= { flowReaderInfoEntry 1 } 865 flowReaderTimeout OBJECT-TYPE 866 SYNTAX Integer32 867 MAX-ACCESS read-create 868 STATUS current 869 DESCRIPTION 870 "Specifies the maximum time (in seconds) between flow data 871 collections for this meter reader. If this time elapses 872 without a collection, the meter should assume that this meter 873 reader has stopped collecting, and delete this row from the 874 table. A value of zero indicates that this row should not be 875 timed out." 876 ::= { flowReaderInfoEntry 2 } 878 flowReaderOwner OBJECT-TYPE 879 SYNTAX OwnerString 880 MAX-ACCESS read-create 881 STATUS current 882 DESCRIPTION 883 "Identifies the meter reader which created this row." 884 ::= { flowReaderInfoEntry 3 } 886 flowReaderLastTime OBJECT-TYPE 887 SYNTAX TimeStamp 888 MAX-ACCESS read-create 889 STATUS current 890 DESCRIPTION 891 "Time this meter reader began its most recent data collection. 893 This variable should be written by a meter reader as its first 894 step in reading flow data. The meter will set this LastTime 895 value to its current Uptime, and set its PreviousTime value 896 (below) to the old LastTime. This allows the meter to 897 recover flows which have been inactive since PreviousTime, 898 for these have been collected at least once. 900 If the meter reader fails to write flowLastReadTime, collection 901 may still proceed but the meter may not be able to recover 902 inactive flows until the flowReaderTimeout has been reached 903 for this entry." 904 ::= { flowReaderInfoEntry 4 } 906 flowReaderPreviousTime OBJECT-TYPE 907 SYNTAX TimeStamp 908 MAX-ACCESS read-only 909 STATUS current 910 DESCRIPTION 911 "Time this meter reader began the collection before last." 912 ::= { flowReaderInfoEntry 5 } 914 flowReaderStatus OBJECT-TYPE 915 SYNTAX RowStatus 916 MAX-ACCESS read-create 917 STATUS current 918 DESCRIPTION 919 "The status of this FlowReaderInfoEntry. A value of active(1) 920 implies that the associated reader should be collecting data 921 from the meter. Once this variable has been set to active(1) 922 a manager may only change this row's flowReaderLastTime and 923 flowReaderTimeout variables." 924 ::= { flowReaderInfoEntry 6 } 926 flowReaderRuleSet OBJECT-TYPE 927 SYNTAX Integer32 (1..2147483647) 928 MAX-ACCESS read-create 929 STATUS current 930 DESCRIPTION 931 "An index to the array of RuleSets. Specifies a set of rules 932 of interest to this meter reader. The reader will attempt to 933 collect any data generated by the meter for this RuleSet, and 934 the meter will not recover the memory of any of the RuleSet's 935 flows until this collection has taken place. Note that a 936 reader may have entries in this table for several RuleSets." 937 ::= { flowReaderInfoEntry 7 } 939 -- 940 -- Control Group: Manager Info Table 941 -- 943 -- Any manager wishing to run a RuleSet must create a row in this 944 -- table. Once it has a table row, the manager may set the control 945 -- variables in its row so as to cause the meter to run any valid 946 -- RuleSet held by the meter. 948 -- A single manager may run several RuleSets; it must create a row 949 -- in this table for each of them. In short, each row of this table 950 -- describes (and controls) a 'task' which the meter is executing. 952 flowManagerInfoTable OBJECT-TYPE 953 SYNTAX SEQUENCE OF FlowManagerInfoEntry 954 MAX-ACCESS not-accessible 955 STATUS current 956 DESCRIPTION 957 "An array of information about managers which have 958 registered their intent to run RuleSets on this meter." 959 ::= { flowControl 4 } 961 flowManagerInfoEntry OBJECT-TYPE 962 SYNTAX FlowManagerInfoEntry 963 MAX-ACCESS not-accessible 964 STATUS current 965 DESCRIPTION 966 "Information about a particular meter 'task.' By creating 967 an entry in this table and activating it, a manager requests 968 that the meter 'run' the indicated RuleSet. 970 The entry also specifies a HighWaterMark and a StandbyRuleSet. 971 If the meter's flow table usage exceeds this task's 972 HighWaterMark the meter will stop running the task's 973 CurrentRuleSet and switch to its StandbyRuleSet. 975 If the value of the task's StandbyRuleSet is 0 when its 976 HighWaterMark is exceeded, the meter simply stops running the 977 task's CurrentRuleSet. By careful selection of HighWaterMarks 978 for the various tasks a manager can ensure that the most 979 critical RuleSets are the last to stop running as the number 980 of flows increases. 982 When a manager has determined that the demand for flow table 983 space has abated, it may cause the task to switch back to its 984 CurrentRuleSet by setting its flowManagerRunningStandby 985 variable to false(2)." 987 INDEX { flowManagerIndex } 988 ::= { flowManagerInfoTable 1 } 990 FlowManagerInfoEntry ::= SEQUENCE { 991 flowManagerIndex Integer32, 992 flowManagerCurrentRuleSet Integer32, 993 flowManagerStandbyRuleSet Integer32, 994 flowManagerHighWaterMark Integer32, 995 flowManagerCounterWrap INTEGER, 996 flowManagerOwner OwnerString, 997 flowManagerTimeStamp TimeStamp, 998 flowManagerStatus RowStatus, 999 flowManagerRunningStandby TruthValue 1000 } 1002 flowManagerIndex OBJECT-TYPE 1003 SYNTAX Integer32 (1..2147483647) 1004 MAX-ACCESS not-accessible 1005 STATUS current 1006 DESCRIPTION 1007 "An index which selects an entry in the flowManagerInfoTable." 1008 ::= { flowManagerInfoEntry 1 } 1010 flowManagerCurrentRuleSet OBJECT-TYPE 1011 SYNTAX Integer32 1012 MAX-ACCESS read-create 1013 STATUS current 1014 DESCRIPTION 1015 "Index to the array of RuleSets. Specifies which set of 1016 rules is the 'current' one for this task. The meter will 1017 be 'running' the current RuleSet if this row's 1018 flowManagerRunningStandby value is false(2). 1020 When the manager sets this variable the meter will stop using 1021 the task's old current RuleSet and start using the new one. 1022 Specifying RuleSet 0 (the empty set) stops flow measurement 1023 for this task." 1024 ::= { flowManagerInfoEntry 2 } 1026 flowManagerStandbyRuleSet OBJECT-TYPE 1027 SYNTAX Integer32 1028 MAX-ACCESS read-create 1029 STATUS current 1030 DESCRIPTION 1031 "Index to the array of RuleSets. After reaching HighWaterMark 1032 (see below) the manager will switch to using the task's 1033 StandbyRuleSet in place of its CurrentRuleSet. For this to be 1034 effective the designated StandbyRuleSet should have a coarser 1035 reporting granularity then the CurrentRuleSet. The manager may 1036 also need to decrease the meter reading interval so that the 1037 meter can recover flows measured by this task's CurrentRuleSet." 1038 DEFVAL { 0 } -- No standby 1039 ::= { flowManagerInfoEntry 3 } 1041 flowManagerHighWaterMark OBJECT-TYPE 1042 SYNTAX Integer32 (0..100) 1043 MAX-ACCESS read-create 1044 STATUS current 1045 DESCRIPTION 1046 "A value expressed as a percentage, interpreted by the meter 1047 as an indication of how full the flow table should be before 1048 it should switch to the standby RuleSet (if one has been 1049 specified) for this task. Values of 0% or 100% disable the 1050 checking represented by this variable." 1051 ::= { flowManagerInfoEntry 4 } 1053 flowManagerCounterWrap OBJECT-TYPE 1054 SYNTAX INTEGER { wrap(1), scale(2) } 1055 MAX-ACCESS read-create 1056 STATUS deprecated 1057 DESCRIPTION 1058 "Specifies whether PDU and octet counters should wrap when 1059 they reach the top of their range (normal behaviour for 1060 Counter64 objects), or whether their scale factors should 1061 be used instead. The combination of counter and scale 1062 factor allows counts to be returned as non-negative binary 1063 floating point numbers, with 64-bit mantissas and 8-bit 1064 exponents." 1065 DEFVAL { wrap } 1066 ::= { flowManagerInfoEntry 5 } 1068 flowManagerOwner OBJECT-TYPE 1069 SYNTAX OwnerString 1070 MAX-ACCESS read-create 1071 STATUS current 1072 DESCRIPTION 1073 "Identifies the manager which created this row." 1074 ::= { flowManagerInfoEntry 6 } 1076 flowManagerTimeStamp OBJECT-TYPE 1077 SYNTAX TimeStamp 1078 MAX-ACCESS read-only 1079 STATUS current 1080 DESCRIPTION 1081 "Time this row was last changed by its manager." 1082 ::= { flowManagerInfoEntry 7 } 1084 flowManagerStatus OBJECT-TYPE 1085 SYNTAX RowStatus 1086 MAX-ACCESS read-create 1087 STATUS current 1088 DESCRIPTION 1089 "The status of this row in the flowManagerInfoTable. A value 1090 of active(1) implies that this task may be activated, by 1091 setting its CurrentRuleSet and StandbyRuleSet variables. 1092 Its HighWaterMark and RunningStandby variables may also be 1093 changed." 1094 ::= { flowManagerInfoEntry 8 } 1096 flowManagerRunningStandby OBJECT-TYPE 1097 SYNTAX TruthValue 1098 MAX-ACCESS read-create 1099 STATUS current 1100 DESCRIPTION 1101 "Set to true(1) by the meter to indicate that it has switched 1102 to runnning this task's StandbyRuleSet in place of its 1103 CurrentRuleSet. To switch back to the CurrentRuleSet, the 1104 manager may simply set this variable to false(2)." 1105 DEFVAL { false } 1106 ::= { flowManagerInfoEntry 9 } 1108 -- 1109 -- Control Group: General Meter Control Variables 1110 -- 1112 flowFloodMark OBJECT-TYPE 1113 SYNTAX Integer32 (0..100) 1114 MAX-ACCESS read-write 1115 STATUS current 1116 DESCRIPTION 1117 "A value expressed as a percentage, interpreted by the meter 1118 as an indication of how full the flow table should be before 1119 it should take some action to avoid running out of resources 1120 to handle new flows, as discussed in section 4.6 (Handling 1121 Increasing Traffic Levels) of the RTFM Architecture RFC 1122 [RTFM-ARC]. 1124 Values of 0% or 100% disable the checking represented by 1125 this variable." 1126 DEFVAL { 95 } -- Enabled by default. 1127 ::= { flowControl 5 } 1129 flowInactivityTimeout OBJECT-TYPE 1130 SYNTAX Integer32 1131 MAX-ACCESS read-write 1132 STATUS current 1133 DESCRIPTION 1134 "The time in seconds since the last packet seen, after which 1135 a flow becomes 'idle.' Note that although a flow may be 1136 idle, it will not be discarded (and its memory recovered) 1137 until after its data has been collected by all the meter 1138 readers registered for its RuleSet." 1139 DEFVAL { 600 } -- 10 minutes 1140 ::= { flowControl 6 } 1142 flowActiveFlows OBJECT-TYPE 1143 SYNTAX Integer32 1144 MAX-ACCESS read-only 1145 STATUS current 1146 DESCRIPTION 1147 "The number of flows which are currently in use." 1148 ::= { flowControl 7 } 1150 flowMaxFlows OBJECT-TYPE 1151 SYNTAX Integer32 1152 MAX-ACCESS read-only 1153 STATUS current 1154 DESCRIPTION 1155 "The maximum number of flows allowed in the meter's 1156 flow table. At present this is determined when the meter 1157 is first started up." 1158 ::= { flowControl 8 } 1160 flowFloodMode OBJECT-TYPE 1161 SYNTAX TruthValue 1162 MAX-ACCESS read-write 1163 STATUS current 1164 DESCRIPTION 1165 "Indicates that the meter has passed its FloodMark and is 1166 not running in its normal mode. 1168 When the manager notices this it should take action to remedy 1169 the problem which caused the flooding. It should then monitor 1170 flowActiveFlows so as to determine when the flood has receded. 1171 At that point the manager may set flowFloodMode to false(2) to 1172 resume normal operation." 1173 ::= { flowControl 9 } 1175 -- 1176 -- The Flow Table 1177 -- 1179 -- This is a table kept by a meter, with one flow data entry for every 1180 -- flow being measured. Each flow data entry stores the attribute 1181 -- values for a traffic flow. Details of flows and their attributes 1182 -- are given in the 'Traffic Flow Measurement: Architecture' 1183 -- document [RTFM-ARC]. 1185 -- From time to time a meter reader may sweep the flow table so as 1186 -- to read counts. This is most effectively achieved by using the 1187 -- TimeMark variable together with successive GetBulk requests to 1188 -- retrieve the values of the desired flow attribute variables. 1190 -- This scheme allows multiple meter readers to independently use the 1191 -- same meter; the meter readers do not have to be synchronised and 1192 -- they may use different collection intervals. 1194 -- If identical sets of counts are required from a meter, a manager 1195 -- could achieve this using two identical copies of a RuleSet in that 1196 -- meter and switching back and forth between them. This is discussed 1197 -- further in the RTFM Architecture document [RTFM-ARC]. 1199 flowDataTable OBJECT-TYPE 1200 SYNTAX SEQUENCE OF FlowDataEntry 1201 MAX-ACCESS not-accessible 1202 STATUS current 1203 DESCRIPTION 1204 "The list of all flows being measured." 1205 ::= { flowData 1 } 1207 flowDataEntry OBJECT-TYPE 1208 SYNTAX FlowDataEntry 1209 MAX-ACCESS not-accessible 1210 STATUS current 1211 DESCRIPTION 1212 "The flow data record for a particular flow." 1213 INDEX { flowDataRuleSet, flowDataTimeMark, flowDataIndex } 1214 ::= { flowDataTable 1 } 1216 FlowDataEntry ::= SEQUENCE { 1217 flowDataIndex Integer32, 1218 flowDataTimeMark TimeFilter, 1219 flowDataStatus INTEGER, 1221 flowDataSourceInterface Integer32, 1222 flowDataSourceAdjacentType AdjacentType, 1223 flowDataSourceAdjacentAddress AdjacentAddress, 1224 flowDataSourceAdjacentMask AdjacentAddress, 1225 flowDataSourcePeerType PeerType, 1226 flowDataSourcePeerAddress PeerAddress, 1227 flowDataSourcePeerMask PeerAddress, 1228 flowDataSourceTransType TransportType, 1229 flowDataSourceTransAddress TransportAddress, 1230 flowDataSourceTransMask TransportAddress, 1232 flowDataDestInterface Integer32, 1233 flowDataDestAdjacentType AdjacentType, 1234 flowDataDestAdjacentAddress AdjacentAddress, 1235 flowDataDestAdjacentMask AdjacentAddress, 1236 flowDataDestPeerType PeerType, 1237 flowDataDestPeerAddress PeerAddress, 1238 flowDataDestPeerMask PeerAddress, 1239 flowDataDestTransType TransportType, 1240 flowDataDestTransAddress TransportAddress, 1241 flowDataDestTransMask TransportAddress, 1243 flowDataPDUScale Integer32, 1244 flowDataOctetScale Integer32, 1246 flowDataRuleSet Integer32, 1248 flowDataToOctets Counter64, -- Source->Dest 1249 flowDataToPDUs Counter64, 1250 flowDataFromOctets Counter64, -- Dest->Source 1251 flowDataFromPDUs Counter64, 1252 flowDataFirstTime TimeStamp, -- Activity times 1253 flowDataLastActiveTime TimeStamp, 1255 flowDataSourceSubscriberID OCTET STRING, 1256 flowDataDestSubscriberID OCTET STRING, 1257 flowDataSessionID OCTET STRING, 1259 flowDataSourceClass Integer32, 1260 flowDataDestClass Integer32, 1261 flowDataClass Integer32, 1262 flowDataSourceKind Integer32, 1263 flowDataDestKind Integer32, 1264 flowDataKind Integer32 1265 } 1267 flowDataIndex OBJECT-TYPE 1268 SYNTAX Integer32 (1..2147483647) 1269 MAX-ACCESS not-accessible 1270 STATUS current 1271 DESCRIPTION 1272 "Value of this flow data record's index within the meter's 1273 flow table." 1274 ::= { flowDataEntry 1 } 1276 flowDataTimeMark OBJECT-TYPE 1277 SYNTAX TimeFilter 1278 MAX-ACCESS not-accessible 1279 STATUS current 1280 DESCRIPTION 1281 "A TimeFilter for this entry. Allows GetNext and GetBulk 1282 to find flow table rows which have changed since a specified 1283 value of the meter's Uptime." 1284 ::= { flowDataEntry 2 } 1286 flowDataStatus OBJECT-TYPE 1287 SYNTAX INTEGER { inactive(1), current(2) } 1288 MAX-ACCESS read-only 1289 STATUS deprecated 1290 DESCRIPTION 1291 "Status of this flow data record." 1292 ::= { flowDataEntry 3 } 1294 flowDataSourceInterface OBJECT-TYPE 1295 SYNTAX Integer32 1296 MAX-ACCESS read-only 1297 STATUS current 1298 DESCRIPTION 1299 "Index of the interface associated with the source address 1300 for this flow. It's value is one of those contained in the 1301 ifIndex field of the meter's interfaces table." 1302 ::= { flowDataEntry 4 } 1304 flowDataSourceAdjacentType OBJECT-TYPE 1305 SYNTAX AdjacentType 1306 MAX-ACCESS read-only 1307 STATUS current 1308 DESCRIPTION 1309 "Adjacent address type of the source for this flow. 1311 If metering is being performed at the network level, 1312 AdjacentType will indicate the medium for the interface on 1313 which the flow was observed and AdjacentAddress will be the 1314 MAC address for that interface. This is the usual case. 1316 If traffic is being metered inside a tunnel, AdjacentType will 1317 be the peer type of the host at the end of the tunnel and 1318 AdjacentAddress will be the peer address for that host." 1319 ::= { flowDataEntry 5 } 1321 flowDataSourceAdjacentAddress OBJECT-TYPE 1322 SYNTAX AdjacentAddress 1323 MAX-ACCESS read-only 1324 STATUS current 1325 DESCRIPTION 1326 "Address of the adjacent device on the path for the source 1327 for this flow." 1328 ::= { flowDataEntry 6 } 1330 flowDataSourceAdjacentMask OBJECT-TYPE 1331 SYNTAX AdjacentAddress 1332 MAX-ACCESS read-only 1333 STATUS current 1334 DESCRIPTION 1335 "1-bits in this mask indicate which bits must match when 1336 comparing the adjacent source address for this flow." 1337 ::= { flowDataEntry 7 } 1339 flowDataSourcePeerType OBJECT-TYPE 1340 SYNTAX PeerType 1341 MAX-ACCESS read-only 1342 STATUS current 1343 DESCRIPTION 1344 "Peer address type of the source for this flow." 1345 ::= { flowDataEntry 8 } 1347 flowDataSourcePeerAddress OBJECT-TYPE 1348 SYNTAX PeerAddress 1349 MAX-ACCESS read-only 1350 STATUS current 1351 DESCRIPTION 1352 "Address of the peer device for the source of this flow." 1353 ::= { flowDataEntry 9 } 1355 flowDataSourcePeerMask OBJECT-TYPE 1356 SYNTAX PeerAddress 1357 MAX-ACCESS read-only 1358 STATUS current 1359 DESCRIPTION 1360 "1-bits in this mask indicate which bits must match when 1361 comparing the source peer address for this flow." 1362 ::= { flowDataEntry 10 } 1364 flowDataSourceTransType OBJECT-TYPE 1365 SYNTAX TransportType 1366 MAX-ACCESS read-only 1367 STATUS current 1368 DESCRIPTION 1369 "Transport address type of the source for this flow. The 1370 value of this attribute will depend on the peer address type." 1371 ::= { flowDataEntry 11 } 1373 flowDataSourceTransAddress OBJECT-TYPE 1374 SYNTAX TransportAddress 1375 MAX-ACCESS read-only 1376 STATUS current 1377 DESCRIPTION 1378 "Transport address for the source of this flow." 1379 ::= { flowDataEntry 12 } 1381 flowDataSourceTransMask OBJECT-TYPE 1382 SYNTAX TransportAddress 1383 MAX-ACCESS read-only 1384 STATUS current 1385 DESCRIPTION 1386 "1-bits in this mask indicate which bits must match when 1387 comparing the transport source address for this flow." 1388 ::= { flowDataEntry 13 } 1390 flowDataDestInterface OBJECT-TYPE 1391 SYNTAX Integer32 1392 MAX-ACCESS read-only 1393 STATUS current 1394 DESCRIPTION 1395 "Index of the interface associated with the dest address for 1396 this flow. This value is one of the values contained in the 1397 ifIndex field of the interfaces table." 1398 ::= { flowDataEntry 14 } 1400 flowDataDestAdjacentType OBJECT-TYPE 1401 SYNTAX AdjacentType 1402 MAX-ACCESS read-only 1403 STATUS current 1404 DESCRIPTION 1405 "Adjacent address type of the destination for this flow." 1406 ::= { flowDataEntry 15 } 1408 flowDataDestAdjacentAddress OBJECT-TYPE 1409 SYNTAX AdjacentAddress 1410 MAX-ACCESS read-only 1411 STATUS current 1412 DESCRIPTION 1413 "Address of the adjacent device on the path for the 1414 destination for this flow." 1415 ::= { flowDataEntry 16 } 1417 flowDataDestAdjacentMask OBJECT-TYPE 1418 SYNTAX AdjacentAddress 1419 MAX-ACCESS read-only 1420 STATUS current 1421 DESCRIPTION 1422 "1-bits in this mask indicate which bits must match when 1423 comparing the adjacent destination address for this flow." 1424 ::= { flowDataEntry 17 } 1426 flowDataDestPeerType OBJECT-TYPE 1427 SYNTAX PeerType 1428 MAX-ACCESS read-only 1429 STATUS current 1430 DESCRIPTION 1431 "Peer address type of the destination for this flow." 1432 ::= { flowDataEntry 18 } 1434 flowDataDestPeerAddress OBJECT-TYPE 1435 SYNTAX PeerAddress 1436 MAX-ACCESS read-only 1437 STATUS current 1438 DESCRIPTION 1439 "Address of the peer device for the destination of this flow." 1440 ::= { flowDataEntry 19 } 1442 flowDataDestPeerMask OBJECT-TYPE 1443 SYNTAX PeerAddress 1444 MAX-ACCESS read-only 1445 STATUS current 1446 DESCRIPTION 1447 "1-bits in this mask indicate which bits must match when 1448 comparing the destination peer type for this flow." 1449 ::= { flowDataEntry 20 } 1451 flowDataDestTransType OBJECT-TYPE 1452 SYNTAX TransportType 1453 MAX-ACCESS read-only 1454 STATUS current 1455 DESCRIPTION 1456 "Transport address type of the destination for this flow. The 1457 value of this attribute will depend on the peer address type." 1458 ::= { flowDataEntry 21 } 1460 flowDataDestTransAddress OBJECT-TYPE 1461 SYNTAX TransportAddress 1462 MAX-ACCESS read-only 1463 STATUS current 1464 DESCRIPTION 1465 "Transport address for the destination of this flow." 1466 ::= { flowDataEntry 22 } 1468 flowDataDestTransMask OBJECT-TYPE 1469 SYNTAX TransportAddress 1470 MAX-ACCESS read-only 1471 STATUS current 1472 DESCRIPTION 1473 "1-bits in this mask indicate which bits must match when 1474 comparing the transport destination address for this flow." 1475 ::= { flowDataEntry 23 } 1477 flowDataPDUScale OBJECT-TYPE 1478 SYNTAX Integer32 (0..255) 1479 MAX-ACCESS read-only 1480 STATUS current 1481 DESCRIPTION 1482 "The scale factor applied to this particular flow. Indicates 1483 the number of bits the PDU counter values should be moved left 1484 to obtain the actual values." 1485 ::= { flowDataEntry 24 } 1487 flowDataOctetScale OBJECT-TYPE 1488 SYNTAX Integer32 (0..255) 1489 MAX-ACCESS read-only 1490 STATUS current 1491 DESCRIPTION 1492 "The scale factor applied to this particular flow. Indicates 1493 the number of bits the octet counter values should be moved 1494 left to obtain the actual values." 1495 ::= { flowDataEntry 25 } 1497 flowDataRuleSet OBJECT-TYPE 1498 SYNTAX Integer32 (1..255) 1499 MAX-ACCESS not-accessible 1500 STATUS current 1501 DESCRIPTION 1502 "The RuleSet number of the RuleSet which created this flow. 1503 Allows a manager to use GetNext or GetBulk requests to find 1504 flows belonging to a particular RuleSet." 1505 ::= { flowDataEntry 26 } 1507 flowDataToOctets OBJECT-TYPE 1508 SYNTAX Counter64 1509 MAX-ACCESS read-only 1510 STATUS current 1511 DESCRIPTION 1512 "The count of octets flowing from source to destination 1513 for this flow." 1514 ::= { flowDataEntry 27 } 1516 flowDataToPDUs OBJECT-TYPE 1517 SYNTAX Counter64 1518 MAX-ACCESS read-only 1519 STATUS current 1520 DESCRIPTION 1521 "The count of packets flowing from source to destination 1522 for this flow." 1523 ::= { flowDataEntry 28 } 1525 flowDataFromOctets OBJECT-TYPE 1526 SYNTAX Counter64 1527 MAX-ACCESS read-only 1528 STATUS current 1529 DESCRIPTION 1530 "The count of octets flowing from destination to source 1531 for this flow." 1532 ::= { flowDataEntry 29 } 1534 flowDataFromPDUs OBJECT-TYPE 1535 SYNTAX Counter64 1536 MAX-ACCESS read-only 1537 STATUS current 1538 DESCRIPTION 1539 "The count of packets flowing from destination to source 1540 for this flow." 1541 ::= { flowDataEntry 30 } 1543 flowDataFirstTime OBJECT-TYPE 1544 SYNTAX TimeStamp 1545 MAX-ACCESS read-only 1546 STATUS current 1547 DESCRIPTION 1548 "The time at which this flow was first entered in the table" 1549 ::= { flowDataEntry 31 } 1551 flowDataLastActiveTime OBJECT-TYPE 1552 SYNTAX TimeStamp 1553 MAX-ACCESS read-only 1554 STATUS current 1555 DESCRIPTION 1556 "The last time this flow had activity, i.e. the time of 1557 arrival of the most recent PDU belonging to this flow." 1558 ::= { flowDataEntry 32 } 1560 flowDataSourceSubscriberID OBJECT-TYPE 1561 SYNTAX OCTET STRING (SIZE (4..20)) 1562 MAX-ACCESS read-only 1563 STATUS current 1564 DESCRIPTION 1565 "Subscriber ID associated with the source address for this 1566 flow. A Subscriber ID is an unspecified text string, used 1567 to ascribe traffic flows to individual users. At this time 1568 the means by which a Subscriber ID may be associated with a 1569 flow is unspecified." 1570 ::= { flowDataEntry 33 } 1572 flowDataDestSubscriberID OBJECT-TYPE 1573 SYNTAX OCTET STRING (SIZE (4..20)) 1574 MAX-ACCESS read-only 1575 STATUS current 1576 DESCRIPTION 1577 "Subscriber ID associated with the destination address for 1578 this flow. A Subscriber ID is an unspecified text string, 1579 used to ascribe traffic flows to individual users. At this 1580 time the means by which a Subscriber ID may be associated 1581 with a flow is unspecified." 1582 ::= { flowDataEntry 34 } 1584 flowDataSessionID OBJECT-TYPE 1585 SYNTAX OCTET STRING (SIZE (4..10)) 1586 MAX-ACCESS read-only 1587 STATUS current 1588 DESCRIPTION 1589 "Session ID for this flow. Such an ID might be allocated 1590 by a network access server to distinguish a series of sessions 1591 between the same pair of addresses, which would otherwise 1592 appear to be parts of the same accounting flow." 1593 ::= { flowDataEntry 35 } 1595 flowDataSourceClass OBJECT-TYPE 1596 SYNTAX Integer32 (1..255) 1597 MAX-ACCESS read-only 1598 STATUS current 1599 DESCRIPTION 1600 "Source class for this flow. Determined by the rules, set by 1601 a PushRule action when this flow was entered in the table." 1602 ::= { flowDataEntry 36 } 1604 flowDataDestClass OBJECT-TYPE 1605 SYNTAX Integer32 (1..255) 1606 MAX-ACCESS read-only 1607 STATUS current 1608 DESCRIPTION 1609 "Destination class for this flow. Determined by the rules, set 1610 by a PushRule action when this flow was entered in the table." 1611 ::= { flowDataEntry 37 } 1613 flowDataClass OBJECT-TYPE 1614 SYNTAX Integer32 (1..255) 1615 MAX-ACCESS read-only 1616 STATUS current 1617 DESCRIPTION 1618 "Class for this flow. Determined by the rules, set by a 1619 PushRule action when this flow was entered in the table." 1620 ::= { flowDataEntry 38 } 1622 flowDataSourceKind OBJECT-TYPE 1623 SYNTAX Integer32 (1..255) 1624 MAX-ACCESS read-only 1625 STATUS current 1626 DESCRIPTION 1627 "Source kind for this flow. Determined by the rules, set by 1628 a PushRule action when this flow was entered in the table." 1629 ::= { flowDataEntry 39 } 1631 flowDataDestKind OBJECT-TYPE 1632 SYNTAX Integer32 (1..255) 1633 MAX-ACCESS read-only 1634 STATUS current 1635 DESCRIPTION 1636 "Destination kind for this flow. Determined by the rules, set 1637 by a PushRule action when this flow was entered in the table." 1638 ::= { flowDataEntry 40 } 1640 flowDataKind OBJECT-TYPE 1641 SYNTAX Integer32 (1..255) 1642 MAX-ACCESS read-only 1643 STATUS current 1644 DESCRIPTION 1645 "Class for this flow. Determined by the rules, set by a 1646 PushRule action when this flow was entered in the table." 1647 ::= { flowDataEntry 41 } 1649 -- 1650 -- The Activity Column Table 1651 -- 1653 flowColumnActivityTable OBJECT-TYPE 1654 SYNTAX SEQUENCE OF FlowColumnActivityEntry 1655 MAX-ACCESS not-accessible 1656 STATUS deprecated 1657 DESCRIPTION 1658 "Index into the Flow Table. Allows a meter reader to retrieve 1659 a list containing the flow table indexes of flows which were 1660 last active at or after a given time, together with the values 1661 of a specified attribute for each such flow." 1662 ::= { flowData 2 } 1664 flowColumnActivityEntry OBJECT-TYPE 1665 SYNTAX FlowColumnActivityEntry 1666 MAX-ACCESS not-accessible 1667 STATUS deprecated 1668 DESCRIPTION 1669 "The Column Activity Entry for a particular attribute, 1670 activity time and flow." 1671 INDEX { flowColumnActivityAttribute, flowColumnActivityTime, 1672 flowColumnActivityIndex } 1673 ::= { flowColumnActivityTable 1 } 1675 FlowColumnActivityEntry ::= SEQUENCE { 1676 flowColumnActivityAttribute FlowAttributeNumber, 1677 flowColumnActivityTime TimeFilter, 1678 flowColumnActivityIndex Integer32, 1679 flowColumnActivityData OCTET STRING 1680 } 1682 flowColumnActivityAttribute OBJECT-TYPE 1683 SYNTAX FlowAttributeNumber 1684 MAX-ACCESS read-only 1685 STATUS deprecated 1686 DESCRIPTION 1687 "Specifies the attribute for which values are required from 1688 active flows." 1689 ::= { flowColumnActivityEntry 1 } 1691 flowColumnActivityTime OBJECT-TYPE 1692 SYNTAX TimeFilter 1693 MAX-ACCESS read-only 1694 STATUS deprecated 1695 DESCRIPTION 1696 "This variable is a copy of flowDataLastActiveTime in the 1697 flow data record identified by the flowColumnActivityIndex 1698 value of this flowColumnActivityTable entry." 1699 ::= { flowColumnActivityEntry 2 } 1701 flowColumnActivityIndex OBJECT-TYPE 1702 SYNTAX Integer32 (1..2147483647) 1703 MAX-ACCESS read-only 1704 STATUS deprecated 1705 DESCRIPTION 1706 "Index of a flow table entry which was active at or after 1707 a specified flowColumnActivityTime." 1708 ::= { flowColumnActivityEntry 3 } 1710 flowColumnActivityData OBJECT-TYPE 1711 SYNTAX OCTET STRING (SIZE (3..1000)) 1712 MAX-ACCESS read-only 1713 STATUS deprecated 1714 DESCRIPTION 1715 "Collection of attribute data for flows active after 1716 flowColumnActivityTime. Within the OCTET STRING is a 1717 sequence of { flow index, attribute value } pairs, one for 1718 each active flow. The end of the sequence is marked by a 1719 flow index value of 0, indicating that there are no more 1720 rows in this column. 1722 The format of objects inside flowColumnFlowData is as follows. 1723 All numbers are unsigned. Numbers and strings appear with 1724 their high-order bytes leading. Numbers are fixed size, as 1725 specified by their SYNTAX in the flow table (above), i.e. one 1726 octet for flowAddressType and small constants, and four octets 1727 for Counter and TimeStamp. Strings are variable-length, with 1728 the length given in a single leading octet. 1730 The following is an attempt at an ASN.1 definition of 1731 flowColumnActivityData: 1733 flowColumnActivityData ::= SEQUENCE flowRowItemEntry 1734 flowRowItemEntry ::= SEQUENCE { 1735 flowRowNumber Integer32 (1..65535), 1736 -- 0 indicates the end of this column 1737 flowDataValue flowDataType -- Choice depends on attribute 1738 } 1739 flowDataType ::= CHOICE { 1740 flowByteValue Integer32 (1..255), 1741 flowShortValue Integer32 (1..65535), 1742 flowLongValue Integer32, 1743 flowStringValue OCTET STRING -- Length (n) in first byte, 1744 -- n+1 bytes total length, trailing zeroes truncated 1745 }" 1746 ::= { flowColumnActivityEntry 4 } 1748 -- 1749 -- The Data Package Table 1750 -- 1752 flowDataPackageTable OBJECT-TYPE 1753 SYNTAX SEQUENCE OF FlowDataPackageEntry 1754 MAX-ACCESS not-accessible 1755 STATUS current 1756 DESCRIPTION 1757 "Index into the Flow Table. Allows a meter reader to retrieve 1758 a sequence containing the values of a specified set of 1759 attributes for a flow which came from a specified RuleSet and 1760 which was last active at or after a given time." 1761 ::= { flowData 3 } 1763 flowDataPackageEntry OBJECT-TYPE 1764 SYNTAX FlowDataPackageEntry 1765 MAX-ACCESS not-accessible 1766 STATUS current 1767 DESCRIPTION 1768 "The data package containing selected variables from 1769 active rows in the flow table." 1770 INDEX { flowPackageSelector, 1771 flowPackageRuleSet, flowPackageTime, flowPackageIndex } 1772 ::= { flowDataPackageTable 1 } 1774 FlowDataPackageEntry ::= SEQUENCE { 1775 flowPackageSelector OCTET STRING, 1776 flowPackageRuleSet Integer32, 1777 flowPackageTime TimeFilter, 1778 flowPackageIndex Integer32, 1779 flowPackageData OCTET STRING 1780 } 1782 flowPackageSelector OBJECT-TYPE 1783 SYNTAX OCTET STRING 1784 MAX-ACCESS not-accessible 1785 STATUS current 1786 DESCRIPTION 1787 "Specifies the attributes for which values are required from 1788 an active flow. These are encoded as a sequence of octets 1789 each containing a FlowAttribute number, preceded by an octet 1790 giving the length of the sequence (not including the length 1791 octet). For a flowPackageSelector to be valid, it must 1792 contain at least one attribute." 1793 ::= { flowDataPackageEntry 1 } 1795 flowPackageRuleSet OBJECT-TYPE 1796 SYNTAX Integer32 (1..255) 1797 MAX-ACCESS not-accessible 1798 STATUS current 1799 DESCRIPTION 1800 "Specifies the index (in the flowRuleSetInfoTable) of the rule 1801 set which produced the required flow." 1802 ::= { flowDataPackageEntry 2 } 1804 flowPackageTime OBJECT-TYPE 1805 SYNTAX TimeFilter 1806 MAX-ACCESS not-accessible 1807 STATUS current 1808 DESCRIPTION 1809 "This variable is a copy of flowDataLastActiveTime in the 1810 flow data record identified by the flowPackageIndex 1811 value of this flowPackageTable entry." 1812 ::= { flowDataPackageEntry 3 } 1814 flowPackageIndex OBJECT-TYPE 1815 SYNTAX Integer32 (1..2147483647) 1816 MAX-ACCESS not-accessible 1817 STATUS current 1818 DESCRIPTION 1819 "Index of a flow table entry which was active at or after 1820 a specified flowPackageTime." 1821 ::= { flowDataPackageEntry 4 } 1823 flowPackageData OBJECT-TYPE 1824 SYNTAX OCTET STRING 1825 MAX-ACCESS read-only 1826 STATUS current 1827 DESCRIPTION 1828 "A collection of attribute values for a single flow, as 1829 specified by this row's indexes. The attribute values are 1830 contained within a BER-encoded sequence [ASN-1, ASN-BER], 1831 in the order they appear in their flowPackageSelector. 1833 For example, to retrieve a flowPackage containing values for 1834 attributes 11, 18 and 29, for a flow in RuleSet 7, with flow 1835 index 3447, one would GET the package whose Object Identifier 1836 (OID) is 1837 flowPackageData . 3.11.18.29 . 7. 0 . 3447 1839 To get a package for the next such flow which had been 1840 active since time 12345 one would GETNEXT the package whose 1841 Object Identifier (OID) is 1842 flowPackageData . 3.11.18.29 . 7. 12345 . 3447" 1843 ::= { flowDataPackageEntry 5 } 1845 -- 1846 -- The Rule Table 1847 -- 1849 -- This is an array of RuleSets; the 'running' ones are indicated 1850 -- by the entries in the meter's flowManagerInfoTable. Several 1851 -- RuleSets can be held in a meter so that the manager can change the 1852 -- running RuleSets easily, for example with time of day. Note that 1853 -- a manager may not change the rules in any RuleSet currently 1854 -- referenced within the flowManagerInfoTable (either as 'current' or 1855 -- 'standby')! See the 'Traffic Flow Measurement: Architecture' 1856 -- document [RTFM-ARC] for details of rules and how they are used. 1858 -- Space for a RuleSet is allocated by setting the value of 1859 -- flowRuleInfoSize in the rule table's flowRuleSetInfoTable row. 1860 -- Values for each row in the RuleSet (Selector, Mask, MatchedValue, 1861 -- Action and Parameter) can then be set by the meter. 1863 -- Although an individual rule within a RuleSet could be modified, 1864 -- it is much safer to simply download a complete new RuleSet. 1866 flowRuleTable OBJECT-TYPE 1867 SYNTAX SEQUENCE OF FlowRuleEntry 1868 MAX-ACCESS not-accessible 1869 STATUS current 1870 DESCRIPTION 1871 "Contains all the RuleSets which may be used by the meter." 1872 ::= { flowRules 1 } 1874 flowRuleEntry OBJECT-TYPE 1875 SYNTAX FlowRuleEntry 1876 MAX-ACCESS not-accessible 1877 STATUS current 1878 DESCRIPTION 1879 "The rule record itself." 1880 INDEX { flowRuleSet, flowRuleIndex } 1881 ::= { flowRuleTable 1 } 1883 FlowRuleEntry ::= SEQUENCE { 1884 flowRuleSet Integer32, 1885 flowRuleIndex Integer32, 1886 flowRuleSelector RuleAttributeNumber, 1887 flowRuleMask RuleAddress, 1888 flowRuleMatchedValue RuleAddress, 1889 flowRuleAction ActionNumber, 1890 flowRuleParameter Integer32 1891 } 1893 flowRuleSet OBJECT-TYPE 1894 SYNTAX Integer32 (1..2147483647) 1895 MAX-ACCESS not-accessible 1896 STATUS current 1897 DESCRIPTION 1898 "Selects a RuleSet from the array of RuleSets." 1899 ::= { flowRuleEntry 1 } 1901 flowRuleIndex OBJECT-TYPE 1902 SYNTAX Integer32 (1..2147483647) 1903 MAX-ACCESS not-accessible 1904 STATUS current 1905 DESCRIPTION 1906 "The index into the Rule table. N.B: These values will 1907 normally be consecutive, given the fall-through semantics 1908 of processing the table." 1909 ::= { flowRuleEntry 2 } 1911 flowRuleSelector OBJECT-TYPE 1912 SYNTAX RuleAttributeNumber 1913 MAX-ACCESS read-write 1914 STATUS current 1915 DESCRIPTION 1916 "Indicates the attribute to be matched. 1918 null(0) is a special case; null rules always succeed. 1920 matchingStoD(50) is set by the meter's Packet Matching Engine. 1921 Its value is true(1) if the PME is attempting to match the 1922 packet with its addresses in Source-to-Destination order (i.e. 1923 as they appear in the packet), and false(2) otherwise. 1924 Details of how packets are matched are given in the 'Traffic 1925 Flow Measurement: Architecture' document [RTFM-ARC]. 1927 v1(51), v2(52), v3(53), v4(54) and v5(55) select meter 1928 variables, each of which can hold the name (i.e. selector 1929 value) of an address attribute. When one of these is used 1930 as a selector, its value specifies the attribute to be 1931 tested. Variable values are set by an Assign action." 1932 ::= { flowRuleEntry 3 } 1934 flowRuleMask OBJECT-TYPE 1935 SYNTAX RuleAddress 1936 MAX-ACCESS read-write 1937 STATUS current 1938 DESCRIPTION 1939 "The initial mask used to compute the desired value. If the 1940 mask is zero the rule's test will always succeed." 1941 ::= { flowRuleEntry 4 } 1943 flowRuleMatchedValue OBJECT-TYPE 1944 SYNTAX RuleAddress 1945 MAX-ACCESS read-write 1946 STATUS current 1947 DESCRIPTION 1948 "The resulting value to be matched for equality. 1949 Specifically, if the attribute chosen by the flowRuleSelector 1950 logically ANDed with the mask specified by the flowRuleMask 1951 equals the value specified in the flowRuleMatchedValue, then 1952 continue processing the table entry based on the action 1953 specified by the flowRuleAction entry. Otherwise, proceed to 1954 the next entry in the rule table." 1955 ::= { flowRuleEntry 5 } 1957 flowRuleAction OBJECT-TYPE 1958 SYNTAX ActionNumber 1959 MAX-ACCESS read-write 1960 STATUS current 1961 DESCRIPTION 1962 "The action to be taken if this rule's test succeeds, or if 1963 the meter's 'test' flag is off. Actions are opcodes for the 1964 meter's Packet Matching Engine; details are given in the 1965 'Traffic Flow Measurement: Architecture' document [RTFM-ARC]." 1966 ::= { flowRuleEntry 6 } 1968 flowRuleParameter OBJECT-TYPE 1969 SYNTAX Integer32 (1..65535) 1970 MAX-ACCESS read-write 1971 STATUS current 1972 DESCRIPTION 1973 "A parameter value providing extra information for this rule's 1974 action. Most of the actions use the parameter value to specify 1975 which rule to excute after this rule's test has failed; details 1976 are given in the 'Traffic Flow Measurement: Architecture' 1977 document [RTFM-ARC]." 1978 ::= { flowRuleEntry 7 } 1980 -- 1981 -- Traffic Flow Meter conformance statement 1982 -- 1984 flowMIBCompliances 1985 OBJECT IDENTIFIER ::= { flowMIBConformance 1 } 1987 flowMIBGroups 1988 OBJECT IDENTIFIER ::= { flowMIBConformance 2 } 1990 flowControlGroup OBJECT-GROUP 1991 OBJECTS { 1992 flowRuleInfoSize, flowRuleInfoOwner, 1993 flowRuleInfoTimeStamp, flowRuleInfoStatus, 1994 flowRuleInfoName, 1995 flowRuleInfoRulesReady, 1996 flowRuleInfoFlowRecords, 1997 flowInterfaceSampleRate, 1998 flowInterfaceLostPackets, 1999 flowReaderTimeout, flowReaderOwner, 2000 flowReaderLastTime, flowReaderPreviousTime, 2001 flowReaderStatus, flowReaderRuleSet, 2002 flowManagerCurrentRuleSet, flowManagerStandbyRuleSet, 2003 flowManagerHighWaterMark, 2004 flowManagerCounterWrap, 2005 flowManagerOwner, flowManagerTimeStamp, 2006 flowManagerStatus, flowManagerRunningStandby, 2007 flowFloodMark, 2008 flowInactivityTimeout, flowActiveFlows, 2009 flowMaxFlows, flowFloodMode } 2010 STATUS deprecated 2011 DESCRIPTION 2012 "The control group defines objects which are used to control 2013 an accounting meter." 2014 ::= {flowMIBGroups 1 } 2016 flowDataTableGroup OBJECT-GROUP 2017 OBJECTS { 2018 -- flowDataIndex, <- INDEX, not-accessible 2019 flowDataStatus, 2020 flowDataSourceInterface, 2021 flowDataSourceAdjacentType, 2022 flowDataSourceAdjacentAddress, flowDataSourceAdjacentMask, 2023 flowDataSourcePeerType, 2024 flowDataSourcePeerAddress, flowDataSourcePeerMask, 2025 flowDataSourceTransType, 2026 flowDataSourceTransAddress, flowDataSourceTransMask, 2027 flowDataDestInterface, 2028 flowDataDestAdjacentType, 2029 flowDataDestAdjacentAddress, flowDataDestAdjacentMask, 2030 flowDataDestPeerType, 2031 flowDataDestPeerAddress, flowDataDestPeerMask, 2032 flowDataDestTransType, 2033 flowDataDestTransAddress, flowDataDestTransMask, 2034 -- flowDataRuleSet, <- INDEX, not-accessible 2035 flowDataToOctets, flowDataToPDUs, 2036 flowDataFromOctets, flowDataFromPDUs, 2037 flowDataFirstTime, flowDataLastActiveTime, 2038 flowDataSourceClass, flowDataDestClass, flowDataClass, 2039 flowDataSourceKind, flowDataDestKind, flowDataKind 2040 } 2041 STATUS deprecated 2042 DESCRIPTION 2043 "The flow table group defines objects which provide the 2044 structure for the flow table, including the creation time 2045 and activity time indexes into it. In addition it defines 2046 objects which provide a base set of flow attributes for the 2047 adjacent, peer and transport layers, together with a flow's 2048 counters and times. Finally it defines a flow's class and 2049 kind attributes, which are set by rule actions." 2050 ::= {flowMIBGroups 2 } 2052 flowDataScaleGroup OBJECT-GROUP 2053 OBJECTS { 2054 flowManagerCounterWrap, 2055 flowDataPDUScale, flowDataOctetScale 2056 } 2057 STATUS deprecated 2058 DESCRIPTION 2059 "The flow scale group defines objects which specify scale 2060 factors for counters." 2061 ::= {flowMIBGroups 3 } 2063 flowDataSubscriberGroup OBJECT-GROUP 2064 OBJECTS { 2065 flowDataSourceSubscriberID, flowDataDestSubscriberID, 2066 flowDataSessionID 2067 } 2068 STATUS current 2069 DESCRIPTION 2070 "The flow subscriber group defines objects which may be used 2071 to identify the end point(s) of a flow." 2072 ::= {flowMIBGroups 4 } 2074 flowDataColumnTableGroup OBJECT-GROUP 2075 OBJECTS { 2076 flowColumnActivityAttribute, 2077 flowColumnActivityIndex, 2078 flowColumnActivityTime, 2079 flowColumnActivityData 2080 } 2081 STATUS deprecated 2082 DESCRIPTION 2083 "The flow column table group defines objects which can be used 2084 to collect part of a column of attribute values from the flow 2085 table." 2086 ::= {flowMIBGroups 5 } 2088 flowDataPackageGroup OBJECT-GROUP 2089 OBJECTS { 2090 flowPackageData 2091 } 2092 STATUS current 2093 DESCRIPTION 2094 "The data package group defines objects which can be used 2095 to collect a specified set of attribute values from a row of 2096 the flow table." 2097 ::= {flowMIBGroups 6 } 2099 flowRuleTableGroup OBJECT-GROUP 2100 OBJECTS { 2101 flowRuleSelector, 2102 flowRuleMask, flowRuleMatchedValue, 2103 flowRuleAction, flowRuleParameter 2104 } 2105 STATUS current 2106 DESCRIPTION 2107 "The rule table group defines objects which hold the set(s) 2108 of rules specifying which traffic flows are to be accounted 2109 for." 2110 ::= {flowMIBGroups 7 } 2112 flowDataScaleGroup2 OBJECT-GROUP 2113 OBJECTS { 2114 -- flowManagerCounterWrap, <- Deprecated 2115 flowDataPDUScale, flowDataOctetScale 2116 } 2117 STATUS current 2118 DESCRIPTION 2119 "The flow scale group defines objects which specify scale 2120 factors for counters. This group replaces the earlier 2121 version of flowDataScaleGroup above (now deprecated)." 2122 ::= {flowMIBGroups 8} 2124 flowControlGroup2 OBJECT-GROUP 2125 OBJECTS { 2126 flowRuleInfoSize, flowRuleInfoOwner, 2127 flowRuleInfoTimeStamp, flowRuleInfoStatus, 2128 flowRuleInfoName, 2129 -- flowRuleInfoRulesReady, <- Deprecated 2130 flowRuleInfoFlowRecords, 2131 flowInterfaceSampleRate, 2132 flowInterfaceLostPackets, 2133 flowReaderTimeout, flowReaderOwner, 2134 flowReaderLastTime, flowReaderPreviousTime, 2135 flowReaderStatus, flowReaderRuleSet, 2136 flowManagerCurrentRuleSet, flowManagerStandbyRuleSet, 2137 flowManagerHighWaterMark, 2138 -- flowManagerCounterWrap, <- Moved to DataScaleGroup 2139 flowManagerOwner, flowManagerTimeStamp, 2140 flowManagerStatus, flowManagerRunningStandby, 2141 flowFloodMark, 2142 flowInactivityTimeout, flowActiveFlows, 2143 flowMaxFlows, flowFloodMode } 2144 STATUS current 2145 DESCRIPTION 2146 "The control group defines objects which are used to control 2147 an accounting meter. It replaces the earlier version of 2148 flowControlGroup above (now deprecated)." 2149 ::= {flowMIBGroups 9 } 2151 flowMIBCompliance MODULE-COMPLIANCE 2152 STATUS current 2153 DESCRIPTION 2154 "The compliance statement for a Traffic Flow Meter." 2155 MODULE 2156 MANDATORY-GROUPS { 2157 flowControlGroup2, 2158 flowDataTableGroup, 2159 flowDataPackageGroup, 2160 flowRuleTableGroup 2161 } 2162 ::= { flowMIBCompliances 1 } 2164 END 2166 5 Security Considerations 2168 5.1 SNMP Concerns 2170 There are a number of management objects defined in this MIB that have a 2171 MAX-ACCESS clause of read-write and/or read-create. Such objects may be 2172 considered sensitive or vulnerable in some network environments. The 2173 support for SET operations in a non-secure environment without proper 2174 protection can have a negative effect on network operations. 2176 There are a number of managed objects in this MIB that may contain 2177 sensitive information. These include all the objects in the Control 2178 Group (since they control access to meter resources by Managers and 2179 Meter Readers) and those in the Flow Table (since they hold the 2180 collected traffic flow data). 2182 It is thus important to control even GET access to these objects and 2183 possibly to even encrypt the values of these object when sending them 2184 over the network via SNMP. Not all versions of SNMP provide features for 2185 such a secure environment. 2187 SNMPv1 by itself is not a secure environment. Even if the network 2188 itself is secure (for example by using IPSec), even then, there is no 2189 control as to who on the secure network is allowed to access and GET/SET 2190 (read/change/create/delete) the objects in this MIB. 2192 It is recommended that the implementers consider the security features 2193 as provided by the SNMPv3 framework. Specifically, the use of the 2194 User-based Security Model [RFC2574] and the View-based Access Control 2195 Model [RFC2575] is recommended. 2197 It is then a customer/user responsibility to ensure that the SNMP entity 2198 giving access to an instance of this MIB is properly configured to give 2199 access to the objects only to those principals (users) that have 2200 legitimate rights to indeed GET or SET (change/create/delete) them. 2202 5.2 Traffic Meter Concerns 2204 This MIB describes how an RTFM traffic meter is controlled, and provides 2205 a way for traffic flow data to be retrieved from it by a meter reader. 2206 This is essentially an application using SNMP as a method of 2207 communication between co-operating hosts; it does not - in itself - have 2208 any inherent security risks. 2210 Since, however, the traffic flow data can be extremely valuable for 2211 network management purposes it is vital that sensible precautions be 2212 taken to keep the meter and its data secure. In particular, an attacker 2213 must not be permitted to write any of the meter's variables! This 2214 requires that access to the meter for control purposes (e.g. loading 2215 RuleSets and reading flow data) be restricted. Such restriction could 2216 be achieved in many ways, for example: 2218 - Physical Separation. Meter(s) and meter reader(s) could be 2219 deployed so that control capabilities are kept within a separate 2220 network, access to which is carefully controlled. 2222 - Application-layer Security. A minimal level of security for SNMP 2223 can be provided by using 'community' strings (which are essentially 2224 clear-text passwords) with SNMPv2C [RFC1157]. Where stronger 2225 security is needed, users should consider using the User-based 2226 Security Model [RFC2574] and the View-based Access Control Model 2227 [RFC2575]. 2229 - Lower-layer Security. Access to the meter can be protected using 2230 encryption at the network layer. For example, one could run SNMP 2231 to the meter through an encrypted TCP tunnel. 2233 When implementing a meter it may be sensible to use separate network 2234 interfaces for control and for metering. If this is done the control 2235 network can be set up so that it doesn't carry any 'user' traffic, and 2236 the metering interfaces can ignore any user attempts to take control of 2237 the meter. 2239 Users should also consider how they will address attempts to circumvent 2240 a meter, i.e. to prevent it from measuring flows. Such attempts are 2241 essentially denial-of-service attacks on the metering interfaces. For 2242 example 2244 - Port Scan attacks. The attacker sends packets to each of a very 2245 large number of IP (Address : Port) pairs. Each of these packets 2246 creates a new flow in the meter; if there are enough of them the 2247 meter will recognise a 'flood' condition, and will probably stop 2248 creating new flows. As a minimum, users (and implementors) should 2249 ensure that meters can recover from flood conditions as soon as 2250 possible after they occur. 2252 - Counter Wrap attacks: The attacker sends enough packets to cause 2253 the counters in a flow to wrap several times between meter 2254 readings, thus causing the counts to be artificially low. The 2255 change to using 64-bit counters in this MIB reduces this problem 2256 significantly. 2258 Users can reduce the severity of both the above attacks by ensuring that 2259 their meters are read often enough to prevent them being flooded. The 2260 resulting flow data will contain a record of the attacking packets, 2261 which may well be useful in determining where any attack came from. 2263 6 IANA Considerations 2265 The RTFM Architecture document [RTFM-ARC], has two sets of assigned 2266 numbers: Opcodes for the PME (Pattern Matching Engine) and RTFM 2267 Attribute numbers. All the assigned numbers used in the Meter MIB 2268 appear in Textual Conventions. The numbers they use are derived as 2269 follows: 2271 The MIB's 'Type' textual conventions use names and numbers from the 2272 Assigned Numbers RFC [ASG-NBR]: 2274 MediumType Uses ifType Definitions 2275 PeerType Uses Address Family Numbers 2276 TransportType Uses Protocol Numbers 2278 The MIB's 'AttributeNumber' textual conventions use RTFM Attribute 2279 names and numbers from the RTFM Architecture document [RTFM-ARC], or 2280 other numbers allocated according to that document's IANA 2281 Considerations section: 2283 FlowAttributeNumber Have values stored in a flow table row 2284 RuleAttributeNumber May be tested in a rule 2286 The MIB's ActionNumber textual convention uses RTFM PME Opcode names and 2287 numbers from the RTFM Architecture document [RTFM-ARC], or other numbers 2288 allocated according to that document's IANA Considerations section. 2290 7 Appendix A: Changes Introduced Since RFC 2064 2292 The first version of the Meter MIB was published as RFC 2064 in January 2293 1997. The most significant changes since then are summarised below. 2295 - TEXTUAL CONVENTIONS: Greater use is made of textual conventions to 2296 describe the various types of addresses used by the meter. 2298 - PACKET MATCHING ATTRIBUTES: Computed attributes (e.g. FlowClass and 2299 FlowKind) may now be tested. This allows one to use these 2300 variables to store information during packet matching. 2301 A new attribute, MatchingStoD, has been added. Its value is 1 2302 while a packet is being matched with its adresses in 'wire' 2303 (source-to-destination) order. 2305 - FLOOD MODE: This is now a read-write variable. Setting it to 2306 false(2) switches the meter out of flood mode and back to normal 2307 operation. 2309 - CONTROL TABLES: Several variables have been added to the RuleSet, 2310 Reader and Manager tables to provide more effective control of the 2311 meter's activities. 2313 - FLOW TABLE: 64-bit counters are used for octet and PDU counts. 2314 This reduces the problems caused by the wrap-around of 32-bit 2315 counters in earlier versions. 2316 flowDataRuleSet is now used as an index to the flow table. This 2317 allows a meter reader to collect only those flow table rows created 2318 by a specified RuleSet. 2320 - DATA PACKAGES: This is a new table, allowing a meter reader to 2321 retrieve values for a list of attributes from a flow as a single 2322 object (a BER-encoded sequence [ASN-1, ASN-BER]). It provides an 2323 efficient way to recover flow data, particularly when used with 2324 SNMP GetBulk requests. 2325 Earlier versions had a 'Column Activity Table;' using this it was 2326 difficult to collect all data for a flow efficiently in a single 2327 SNMP request. 2329 8 Acknowledgements 2331 An early draft of this document was produced under the auspices of the 2332 IETF's Accounting Working Group with assistance from the SNMP Working 2333 Group and the Security Area Advisory Group. Particular thanks are due 2334 to Jim Barnes, Sig Handelman and Stephen Stibler for their support and 2335 their assistance with checking early versions of the MIB. 2337 Stephen Stibler shared the development workload of producing the MIB 2338 changes summarized in chapter 5 (above). 2340 9 References 2342 [ACT-BKG] Mills, C., Hirsch, G. and Ruth, G., "Internet Accounting 2343 Background," RFC 1272, November 1991. 2345 [ASG-NBR] Reynolds, J., Postel, J., "Assigned Numbers," 2346 RFC 1700, ISI, October 1994. 2348 [ASN-1] Information processing systems - Open Systems 2349 Interconnection - Specification of Abstract Syntax Notation 2350 One (ASN.1), International Organization for Standardization, 2351 International Standard 8824, December 1987. 2353 [ASN-BER] Information processing systems - Open Systems 2354 Interconnection - Specification of Basic Encoding Rules for 2355 Abstract Notation One (ASN.1), International Organization 2356 for Standardization, International Standard 8825, 2357 December 1987. 2359 [ENET-OBJ] Kastenholz., F., "Definitions of Managed Objects for the 2360 Ethernet-like Interface Types," RFC 1643, July 1994 2362 [FDDI-MIB] Case, J. and Rijsinghani., A., "FDDI Management 2363 Information Base," September 1993. 2365 [IPPM-FRM] Paxson, V., Almes, G., Mahdavi, J. and Mathis, M., 2366 "Framework for IP Performance Metrics," RFC 2330, May 1998. 2368 [MIB-II] McCloghrie, K. and Rose, M., Editors, "Management 2369 Information Base for Network Management of TCP/IP-based 2370 internets: MIB-II," RFC 1213, March 1991. 2372 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 2373 of Management Information for TCP/IP-based Internets", 2374 STD 16, RFC 1155, May 1990 2376 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 2377 Network Management Protocol", STD 15, RFC 1157, May 1990. 2379 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 2380 STD 16, RFC 1212, March 1991 2382 [RFC1215] M. Rose, "A Convention for Defining Traps for use with 2383 the SNMP", RFC 1215, March 1991 2385 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2386 "Introduction to Community-based SNMPv2", 2387 RFC 1901, January 1996. 2389 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2390 "Protocol Operations for Version 2 of the Simple Network 2391 Management Protocol (SNMPv2)", RFC 1905, January 1996. 2393 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2394 "Transport Mappings for Version 2 of the Simple Network 2395 Management Protocol (SNMPv2)", RFC 1906, January 1996. 2397 [RFC1908] Case, J., McCloghrie, K., Rose, M. and Waldbusser, S., 2398 "Coexistence between version 1 and version 2 of the 2399 Internet-standard Network Management Framework," RFC 1908 2401 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 2402 "Introduction to Version 3 of the Internet-standard Network 2403 Management Framework", RFC 2570, April 1999 2405 [RFC2571] Harrington, D., Presuhn, R., and Wijnen, B., 2406 "An Architecture for Describing SNMP Management Frameworks", 2407 RFC 2571, April 1999 2409 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 2410 Processing and Dispatching for the Simple Network Management 2411 Protocol (SNMP)", RFC 2572, April 1999 2413 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 2414 RFC 2573, April 1999 2416 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 2417 (USM) for version 3 of the Simple Network Management 2418 Protocol (SNMPv3)", RFC 2574, April 1999 2420 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 2421 Access Control Model (VACM) for the Simple Network 2422 Management Protocol (SNMP)", RFC 2575, April 1999 2424 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2425 Rose, M., and S. Waldbusser, "Structure of Management 2426 Information Version 2 (SMIv2)", 2427 STD 58, RFC 2578, April 1999 2429 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2430 Rose, M., and S. Waldbusser, "Textual Conventions for 2431 SMIv2", STD 58, RFC 2579, April 1999 2433 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2434 Rose, M., and S. Waldbusser, "Conformance Statements for 2435 SMIv2", STD 58, RFC 2580, April 1999 2437 [RMON2-MIB] Waldbusser, S., "Remote Network Monitoring Management 2438 Information Base Version 2 using SMIv2," RFC 2021, 2439 January 1997. 2441 [RTFM-ARC] Brownlee, N., Mills, C. and G. Ruth, "Traffic Flow 2442 Measurement: Architecture", RFC 2063, January 1997. 2444 [V6-ADDR] Hinden, R.and Deering, S., "IP Version 6 Addressing 2445 Architecture," RFC 2373, July 1998. 2447 10 Author's Address 2449 Nevil Brownlee 2450 Information Technology Systems & Services 2451 The University of Auckland 2452 Private Bag 92-019 2453 Auckland, New Zealand 2455 Phone: +64 9 373 7599 x8941 2456 E-mail: n.brownlee@auckland.ac.nz 2458 Expires February 2000