idnits 2.17.1 draft-siddiqui-rmonmib-raqmon-mib-02.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: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 29 longer pages, the longest (page 1) being 61 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 29 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 43 instances of too long lines in the document, the longest one being 175 characters in excess of 72. ** The abstract seems to contain references ([SIDDIQUI1], [RFC2819]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 280 has weird spacing: '... field octet...' -- 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.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC2274' is mentioned on line 1282, but not defined ** Obsolete undefined reference: RFC 2274 (Obsoleted by RFC 2574) == Missing Reference: 'RFC2275' is mentioned on line 1283, but not defined ** Obsolete undefined reference: RFC 2275 (Obsoleted by RFC 2575) ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) == Outdated reference: A later version (-02) exists of draft-siddiqui-rmonmib-raqmon-mib-01 -- Possible downref: Normative reference to a draft: ref. 'SIDDIQUI1' -- No information found for draft-siddiqui-raqmon-framework - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'SIDDIQUI2' -- No information found for draft-siddiqui-raqmon-pdu - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'SIDDIQUI3' Summary: 21 errors (**), 0 flaws (~~), 8 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft Anwar Siddiqui 3 Avaya Inc. 4 Dan Romascanu 5 Avaya Inc. 6 Eugene Golovinsky 7 BMC Software 8 Richard Smith 9 Avaya Inc. 10 22 Oct. 2002 12 Real-time Application Quality of Service 13 Monitoring (RAQMON) MIB 15 17 Status of this Memo 19 This document is an Internet-Draft and is in full conformance with 20 all provisions of Section 10 of RFC2026. Internet-Drafts are working 21 documents of the Internet Engineering Task Force (IETF), its areas, 22 and its working groups. Note that other groups may also distribute 23 working documents as Internet-Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet- Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/1id-abstracts.html 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html 36 Copyright Notice 38 Copyright (C) The Internet Society (2001). All Rights Reserved. 40 Abstract 42 This memo defines a portion of the Management Information Base (MIB) 43 for use with network management protocols in the Internet community. 44 The document proposes an extension to the Remote Monitoring MIB 45 [RFC2819]. In particular, it describes managed objects used for 46 realtime application QOS monitoring. 48 This memo also updates the [SIDDIQUI1] with several options of 49 protocols that could be used between RAQMON Data Sources and RAQMON 50 Report Collectors. 52 Distribution of this memo is unlimited. 54 Table of Contents 56 Status of this Memo 1 57 Abstract 1 58 1 Introduction 2 59 2 The SNMP Management Framework 3 60 3 RAQMON Framework 4 61 4 Structure of the RAQMON MIB 5 62 5 RAQMON MIB Definitions 5 63 6 References 25 64 7 Intellectual Property 26 65 8 Security Considerations 27 66 9 Author's Address 28 67 A Full Copyright Statement 28 68 B Log of Changes 29 70 1. Introduction 72 This memo defines a portion of the Management Information Base (MIB) 73 for use with network management protocols in the Internet community. 74 In particular, it defines a method of sorting the interfaces of a 75 monitored device according to values of parameters specific to this 76 interface. 78 The original RAQMON draft [SIDDIQUI1] was split into 3 parts to 79 identify the RAQMON Framework, RAQMON QOS PDU and RAQMON MIB. 81 This memo updates [SIDDIQUI1] that defined the Management Information 82 Base (MIB) for use with network management protocols in the Internet 83 community. The document proposes an extension to the Remote 84 Monitoring MIB [RFC2819] to accommodate RAQMON solution. 86 The memo [SIDDIQUI2] defines a Real-Time Application QOS Monitoring 87 (RAQMON) Framework that extends the RMON Framework to allow Real-time 88 Application QoS information of these types of end devices as outlined 89 by RAQMON Charter of the RMON Workgroup. 91 The memo [SIDDIQUI3] takes a portion of that defined RAQMON QOS PDU and describes how 93 various PDUs can be transported over existing Application level 94 transport protocol like Real Time Communication Protocol (RTCP) and 95 Simple Network Management Protocol (SNMP) to transport statistics 96 between RDS and RRC. 98 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 99 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 100 document are to be interpreted as described in [RFC2119]. 102 2. The SNMP Management Framework 104 The SNMP Management Framework presently consists of five major 105 components: 107 o An overall architecture, described in RFC 2571 [RFC2571]. 109 o Mechanisms for describing and naming objects and events for the 110 purpose of management. The first version of this Structure of 111 Management Information (SMI) is called SMIv1 and described in 112 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 113 1215 [RFC1215]. The second version, called SMIv2, is described 114 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 115 STD 58, RFC 2580 [RFC2580]. 117 o Message protocols for transferring management information. The 118 first version of the SNMP message protocol is called SNMPv1 and 119 described in STD 15, RFC 1157 [RFC1157]. A second version of 120 the SNMP message protocol, which is not an Internet standards 121 track protocol, is called SNMPv2c and described in RFC 1901 122 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 123 message protocol is called SNMPv3 and described in RFC 1906 124 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 126 o Protocol operations for accessing management information. The 127 first set of protocol operations and associated PDU formats is 128 described in STD 15, RFC 1157 [RFC1157]. A second set of 129 protocol operations and associated PDU formats is described in 130 RFC 1905 [RFC1905]. 132 o A set of fundamental applications described in RFC 2573 133 [RFC2573] and the view-based access control mechanism described 134 in RFC 2575 [RFC2575]. 136 A more detailed introduction to the current SNMP Management Framework 137 can be found in RFC 2570 [RFC2570]. 139 Managed objects are accessed via a virtual information store, termed 140 the Management Information Base or MIB. Objects in the MIB are 141 defined using the mechanisms defined in the SMI. 143 This memo specifies a MIB module that is compliant to the SMIv2. A 144 MIB conforming to the SMIv1 can be produced through the appropriate 145 translations. The resulting translated MIB must be semantically 146 equivalent, except where objects or events are omitted because no 147 translation is possible (use of Counter64). Some machine readable 148 information in SMIv2 will be converted into textual descriptions in 149 SMIv1 during the translation process. However, this loss of machine 150 readable information is not considered to change the semantics of the 151 MIB. 153 3. RAQMON Framework 155 As outlined in [SIDDIQUI2] the RAQMON framework is based on three 156 entities: 158 - RAQMON Data Source (RDS) - RAQMON Report Collector (RRC) - RAQMON 159 MIB Structure 161 Figure 1 below shows various interfaces in RAQMON Framework. This 162 draft specifies the Management Information Base (MIB) Modules used by 163 the RAQMON Report Collectors to store data derived from RAQMON PDUs. 165 +----------------------+ +---------------------------+ 166 | IP End Device | | IP End Device >----+ | 167 |+--------------------+| |+--------------------+ | | 168 || APPLICATION || || APPLICATION | | | 169 || -Voice over IP <----(1)----> -Voice over IP >- + | | 170 || -Instant Messaging|| || -Instant Messaging| | 3 | 171 || -Email || || -Email | 2 | | 172 |+--------------------+| |+--------------------+ | | | 173 | | | | | | 174 | | | +------------------+ | | | 175 +----------------------+ | |RAQMON Data Source|<-+ | | 176 | | (RDS) |<---+ | 177 | +------------------+ | 178 +-----------|---------------+ 179 | 180 (4) 181 | 182 +----------------------------+ 183 | | 184 |/ |/ 185 +------------------+ +------------------+ +-------------+ 186 |RAQMON Report | .. |RAQMON Report | | RAQMON | 187 |Collector (RRC) #n| |Collector (RRC) #1|<--5-->| Manager | 188 +------------------+ +------------------+ +-------------+ 190 Figure 1 - RAQMON Framework. 192 (1) Communication Session between IP end devices/apps affected by 193 underlying transport network 195 (2) Context-Sensitive transport network Specific Metrics 197 (3) Device State Specific Metrics 199 (4) RAQMON PDU transmitted over this interface (IP Address, port) 201 (5) RAQMON MIB running between RRCs and a RAQMON Application ('RAQMON manager') 203 4. Structure of the RAQMON MIB 205 The RAQMON MIB is composed of three MIB groups: 207 The raqmonSession MIB group incorporates the following tables: 208 - raqmonParticpantTable contains information about participants in open and closed (terminated) sessions 209 - raqmonQosTable contains historical information about QoS during sessions 210 - raqmonParticpantAddrTable maps particpant addresses into the index of the raqmonParticpantTable 212 The raqmonException MIB group includes a table of filters that trigger notifications for sessions with poor QoS. 214 The raqmonConfig MIB group includes object that define the configuration of the RAQMON collector. 216 All objects in the MIB MUST be implemented by the RAQMON collectors, with the exception of the raqmonPDUBasicPDU object and raqmonSNMPTransportNotification which MUST be implemented by a RAQMON device. This is reflected in the conformance clauses. 218 5. RAQMON MIB Definitions 220 -- 221 -- The original version of this MIB was created by Richard Smith from 222 -- Avaya Labs Australia 224 RAQMON-MIB DEFINITIONS ::= BEGIN 226 IMPORTS 227 OBJECT-GROUP, NOTIFICATION-GROUP 228 FROM SNMPv2-CONF 229 mib-2, enterprises, IpAddress, Integer32, Unsigned32, 230 Gauge32, Counter32, OBJECT-TYPE, 231 MODULE-IDENTITY, NOTIFICATION-TYPE 232 FROM SNMPv2-SMI 234 RowStatus, TEXTUAL-CONVENTION, TruthValue 235 FROM SNMPv2-TC 236 Utf8String 237 FROM SYSAPPL-MIB 238 Dscp 239 FROM DIFFSERV-DSCP-TC; 241 raqmon MODULE-IDENTITY 242 LAST-UPDATED "200210140000Z" 243 ORGANIZATION 244 "Avaya Inc." 245 CONTACT-INFO 246 "Dan Romascanu 247 Postal: Avaya Israel 248 Atidim Technology Park, Bldg. #3 249 Tel Aviv, 61131 250 Israel 251 Tel: +972 3 6458414 252 Email: dromasca@avaya.com 253 " 254 DESCRIPTION 255 "RAQMON MIB" 256 ::= { mib-2 6889 } 258 -- 259 -- Type definitions 260 -- 262 Duration ::= Unsigned32 264 -- 265 -- Textual conventions 266 -- 268 RaqmonDateAndTime ::= TEXTUAL-CONVENTION 269 DISPLAY-HINT 270 "2d-1d-1d,1d:1d:1d" 271 STATUS current 272 DESCRIPTION 273 "A date-time specification in Coordinated Universal 274 Time (UTC). 275 This definition is used rather than DateAndTime 276 from SNMPv2-TC or ExtUTCTime from SMIv2 277 since a fixed length field in UTC was preferred 278 for use as an INDEX. 280 field octets contents range 281 ----- ------ -------- ----- 282 1 1-2 year 0..65536 283 2 3 month 1..12 284 3 4 day 1..31 285 4 5 hour 0..23 286 5 6 minutes 0..59 287 6 7 seconds 0..59 289 For example, Tuesday May 26, 1992 at 1:30:15 UTC 290 would be displayed as: 292 1992-5-26,13:30:15." 293 SYNTAX OCTET STRING (SIZE (7)) 295 -- 296 -- Node definitions 297 -- 299 raqmonEvents OBJECT IDENTIFIER ::= { raqmon 0 } 301 raqmonSessionAlarm NOTIFICATION-TYPE 302 OBJECTS { raqmonParticipantAddr, 303 raqmonParticipantName, 304 raqmonParticipantPeerAddr, raqmonQosRTT, 306 raqmonQosJitter, 307 raqmonQosLostPackets, raqmonQosRcvdPackets } 308 STATUS current 309 DESCRIPTION 310 "A notification generated by an entry in the 311 raqmonSessionExceptionTable." 312 ::= { raqmonEvents 1 } 314 raqmonSNMPTransportNotofication NOTIFICATION-TYPE 315 OBJECTS { raqmonPDUBasicPDU } 316 STATUS current 317 DESCRIPTION 318 "A Notification generated by a RAQMON device to a 319 collector, if an SNMP agent is implemented in the 320 RAQMON device. Note that similar format PDUs MAY 321 Be generated by RAQMON devices without a full 322 SNMP agent being REQUIRED." 323 ::= { raqmonEvents 2 } 325 raqmonMIBObjects OBJECT IDENTIFIER ::= { raqmon 1 } 327 raqmonSession OBJECT IDENTIFIER ::= { raqmonMIBObjects 1 } 328 raqmonParticipantTable OBJECT-TYPE 329 SYNTAX SEQUENCE OF RaqmonParticipantEntry 330 MAX-ACCESS not-accessible 331 STATUS current 332 DESCRIPTION 333 "Table of information about participants in sessions. 334 Contains both active and closed (terminated) sessions. 335 " 336 ::= { raqmonSession 1 } 338 raqmonParticipantEntry OBJECT-TYPE 339 SYNTAX RaqmonParticipantEntry 340 MAX-ACCESS not-accessible 341 STATUS current 342 DESCRIPTION 343 "Each entry contains information from a single session 344 participant. 345 Rows are removed for inactive sessions 346 when implementation 347 specific age or space limits are reached. 348 " 349 INDEX { raqmonParticipantStartDate, raqmonParticipantIndex } 350 ::= { raqmonParticipantTable 1 } 352 RaqmonParticipantEntry ::= 353 SEQUENCE { 354 raqmonParticipantStartDate 355 RaqmonDateAndTime, 356 raqmonParticipantIndex 357 Integer32, 358 raqmonParticipantAddr 359 IpAddress, 360 raqmonParticipantSendPort 361 INTEGER, 362 raqmonParticipantRecvPort 363 Integer32, 364 raqmonParticipantSetupDelay 365 Unsigned32, 366 raqmonParticipantName 367 Utf8String, 368 raqmonParticipantTool 369 Utf8String, 370 raqmonParticipantQosCount 371 Unsigned32, 372 raqmonParticipantEndDate 373 RaqmonDateAndTime, 374 raqmonParticipantRcvdPT 375 INTEGER, 377 raqmonParticipantSentPT 378 INTEGER, 379 raqmonParticipantActive 380 TruthValue, 381 raqmonParticipantPeerIndex 382 OCTET STRING, 383 raqmonParticipantPeerAddr 384 IpAddress, 385 raqmonParticipantSrcLayer2 386 INTEGER, 387 raqmonParticipantDestLayer2 388 INTEGER, 389 raqmonParticipantSrcLayer3 390 Dscp, 391 raqmonParticipantDestLayer3 392 Dscp, 393 raqmonParticipantCPUMean 394 INTEGER, 395 raqmonParticipantCPUMin 396 INTEGER, 397 raqmonParticipantCPUMax 398 INTEGER, 399 raqmonParticipantMemoryMean 400 INTEGER, 401 raqmonParticipantMemoryMin 402 INTEGER, 403 raqmonParticipantMemoryMax 404 INTEGER, 405 raqmonParticipantRTTMean 406 Gauge32, 407 raqmonParticipantRTTMin 408 Gauge32, 409 raqmonParticipantRTTMax 410 Gauge32, 411 raqmonParticipantJitterMean 412 Gauge32, 413 raqmonParticipantJitterMin 414 Gauge32, 415 raqmonParticipantJitterMax 416 Gauge32, 417 raqmonParticipantPackets 418 Counter32, 419 raqmonParticipantLostPackets 420 Counter32 421 } 423 raqmonParticipantStartDate OBJECT-TYPE 424 SYNTAX RaqmonDateAndTime 425 MAX-ACCESS not-accessible 426 STATUS current 427 DESCRIPTION 428 "The date and time of this entry. 429 It will be the date and time 430 of the first report received." 431 ::= { raqmonParticipantEntry 1 } 433 raqmonParticipantIndex OBJECT-TYPE 434 SYNTAX Integer32 (1..2147483647) 435 MAX-ACCESS not-accessible 436 STATUS current 437 DESCRIPTION 438 "The index of the conceptual row which is for 439 SNMP purposes 440 only and has no relation to any protocol value. 441 There is 442 no requirement that these rows are created or maintained 443 sequentially. The index will be unique for a 444 particular date and time." 445 ::= { raqmonParticipantEntry 2 } 447 raqmonParticipantAddr OBJECT-TYPE 448 SYNTAX IpAddress 449 MAX-ACCESS read-only 450 STATUS current 451 DESCRIPTION 452 "IP Address of the participant for this session." 453 ::= { raqmonParticipantEntry 3 } 455 raqmonParticipantSendPort OBJECT-TYPE 456 SYNTAX INTEGER (0..65535) 457 MAX-ACCESS read-only 458 STATUS current 459 DESCRIPTION 460 "Port from which session data is sent." 461 ::= { raqmonParticipantEntry 4 } 463 raqmonParticipantRecvPort OBJECT-TYPE 464 SYNTAX Integer32 465 MAX-ACCESS read-write 466 STATUS current 467 DESCRIPTION 468 "Port on which session data is received." 469 ::= { raqmonParticipantEntry 5 } 471 raqmonParticipantSetupDelay OBJECT-TYPE 472 SYNTAX Unsigned32 473 MAX-ACCESS read-only 474 STATUS current 475 DESCRIPTION 476 "Session setup time in milliseconds." 477 ::= { raqmonParticipantEntry 6 } 479 raqmonParticipantName OBJECT-TYPE 480 SYNTAX Utf8String 481 MAX-ACCESS read-only 482 STATUS current 483 DESCRIPTION 484 "The data source name for the participant." 485 ::= { raqmonParticipantEntry 7 } 487 raqmonParticipantTool OBJECT-TYPE 488 SYNTAX Utf8String 489 MAX-ACCESS read-only 490 STATUS current 491 DESCRIPTION 492 "A string giving the name and possibly version 493 of the application 494 generating the stream, e.g., videotool 1.2. 495 This information may be 496 useful for debugging purposes and is similar 497 to the Mailer or Mail- 498 System-Version SMTP headers. The tool value 499 is expected to remain 500 constant for the duration of the session." 501 ::= { raqmonParticipantEntry 8 } 503 raqmonParticipantQosCount OBJECT-TYPE 504 SYNTAX Unsigned32 505 MAX-ACCESS read-only 506 STATUS current 507 DESCRIPTION 508 "Count of entries in the QOS history table 509 for this participant and 510 session." 511 ::= { raqmonParticipantEntry 9 } 513 raqmonParticipantEndDate OBJECT-TYPE 514 SYNTAX RaqmonDateAndTime 515 MAX-ACCESS read-only 516 STATUS current 517 DESCRIPTION 518 "The date and time of the last report received." 519 ::= { raqmonParticipantEntry 10 } 521 raqmonParticipantRcvdPT OBJECT-TYPE 522 SYNTAX INTEGER (0..127) 523 MAX-ACCESS read-only 524 STATUS current 525 DESCRIPTION 526 "Payload type of received packets." 527 ::= { raqmonParticipantEntry 11 } 529 raqmonParticipantSentPT OBJECT-TYPE 530 SYNTAX INTEGER (0..127) 531 MAX-ACCESS read-write 532 STATUS current 533 DESCRIPTION 534 "Payload type of sent packets." 535 ::= { raqmonParticipantEntry 12 } 537 raqmonParticipantActive OBJECT-TYPE 538 SYNTAX TruthValue 539 MAX-ACCESS read-only 540 STATUS current 541 DESCRIPTION 542 "Value 'true' ndicates that the session 543 for this participant is active (open). 544 Value 'false' indicates that the session 545 is closed (terminated). 546 " 547 ::= { raqmonParticipantEntry 13 } 549 raqmonParticipantPeerIndex OBJECT-TYPE 550 SYNTAX OCTET STRING (SIZE (0 | 11)) 551 MAX-ACCESS read-only 552 STATUS current 553 DESCRIPTION 554 "The index of the corresponding entry in this table for 555 the other peer participant. If there is no 556 such entry then the 557 value will be a zero length string. Otherwise it will 558 be a string of length 11 consisting of 559 the raqmonParticipantStartDate 560 octet string appended with an octet string of length 4 561 containing raqmonParticipantIndex (most 562 significant octet first). 563 Note, the entry may no longer exist even if the index is 564 not zero length since the entry may have 565 been deleted due 566 to implementation defined limits being exceeded. 567 " 568 ::= { raqmonParticipantEntry 14 } 570 raqmonParticipantPeerAddr OBJECT-TYPE 571 SYNTAX IpAddress 572 MAX-ACCESS read-only 573 STATUS current 574 DESCRIPTION 575 "IP address of peer endpoint." 576 ::= { raqmonParticipantEntry 15 } 578 raqmonParticipantSrcLayer2 OBJECT-TYPE 579 SYNTAX INTEGER (0..7) 580 MAX-ACCESS read-only 581 STATUS current 582 DESCRIPTION 583 "Source Layer 2 priority" 584 ::= { raqmonParticipantEntry 16 } 586 raqmonParticipantDestLayer2 OBJECT-TYPE 587 SYNTAX INTEGER (0..7) 588 MAX-ACCESS read-only 589 STATUS current 590 DESCRIPTION 591 "Destination Layer 2 priority." 592 ::= { raqmonParticipantEntry 17 } 594 raqmonParticipantSrcLayer3 OBJECT-TYPE 595 SYNTAX Dscp 596 MAX-ACCESS read-only 597 STATUS current 598 DESCRIPTION 599 "Source Layer 3 DSCP value" 600 ::= { raqmonParticipantEntry 18 } 602 raqmonParticipantDestLayer3 OBJECT-TYPE 603 SYNTAX Dscp 604 MAX-ACCESS read-write 605 STATUS current 606 DESCRIPTION 607 "Destination Layer 3 DSCP value" 608 ::= { raqmonParticipantEntry 19 } 610 raqmonParticipantCPUMean OBJECT-TYPE 611 SYNTAX INTEGER (0..100) 612 MAX-ACCESS read-only 613 STATUS current 614 DESCRIPTION 615 "Mean CPU utilization as a percentage." 616 ::= { raqmonParticipantEntry 20 } 618 raqmonParticipantCPUMin OBJECT-TYPE 619 SYNTAX INTEGER (0..100) 620 MAX-ACCESS read-only 621 STATUS current 622 DESCRIPTION 623 "Minimum CPU utilization as a percentage." 624 ::= { raqmonParticipantEntry 21 } 626 raqmonParticipantCPUMax OBJECT-TYPE 627 SYNTAX INTEGER (0..100) 628 MAX-ACCESS read-write 629 STATUS current 630 DESCRIPTION 631 "Maximum CPU utilization as a percentage." 632 ::= { raqmonParticipantEntry 22 } 634 raqmonParticipantMemoryMean OBJECT-TYPE 635 SYNTAX INTEGER (0..100) 636 MAX-ACCESS read-only 637 STATUS current 638 DESCRIPTION 639 "Mean memory utilization as a percentage." 640 ::= { raqmonParticipantEntry 23 } 642 raqmonParticipantMemoryMin OBJECT-TYPE 643 SYNTAX INTEGER (0..100) 644 MAX-ACCESS read-only 645 STATUS current 646 DESCRIPTION 647 "Minimum memory utilization as a percentage." 648 ::= { raqmonParticipantEntry 24 } 650 raqmonParticipantMemoryMax OBJECT-TYPE 651 SYNTAX INTEGER (0..100) 652 MAX-ACCESS read-only 653 STATUS current 654 DESCRIPTION 655 "Maximum memory utilization as a percentage." 656 ::= { raqmonParticipantEntry 25 } 658 raqmonParticipantRTTMean OBJECT-TYPE 659 SYNTAX Gauge32 660 MAX-ACCESS read-only 661 STATUS current 662 DESCRIPTION 663 "Mean round trip time (RTT) over the entire session." 664 ::= { raqmonParticipantEntry 26 } 666 raqmonParticipantRTTMin OBJECT-TYPE 667 SYNTAX Gauge32 668 MAX-ACCESS read-only 669 STATUS current 670 DESCRIPTION 671 "Minimum round trip time (RTT) over the entire session." 672 ::= { raqmonParticipantEntry 27 } 674 raqmonParticipantRTTMax OBJECT-TYPE 675 SYNTAX Gauge32 676 MAX-ACCESS read-only 677 STATUS current 678 DESCRIPTION 679 "Maximum round trip time (RTT) over the entire session." 680 ::= { raqmonParticipantEntry 28 } 682 raqmonParticipantJitterMean OBJECT-TYPE 683 SYNTAX Gauge32 684 MAX-ACCESS read-only 685 STATUS current 686 DESCRIPTION 687 "Mean jitter over the entire session." 688 ::= { raqmonParticipantEntry 29 } 690 raqmonParticipantJitterMin OBJECT-TYPE 691 SYNTAX Gauge32 692 MAX-ACCESS read-only 693 STATUS current 694 DESCRIPTION 695 "Minimum jitter over the entire session." 696 ::= { raqmonParticipantEntry 30 } 698 raqmonParticipantJitterMax OBJECT-TYPE 699 SYNTAX Gauge32 700 MAX-ACCESS read-only 701 STATUS current 702 DESCRIPTION 703 "Maximim jitter over the entire session." 704 ::= { raqmonParticipantEntry 31 } 706 raqmonParticipantPackets OBJECT-TYPE 707 SYNTAX Counter32 708 MAX-ACCESS read-only 709 STATUS current 710 DESCRIPTION 711 "Count of packets received for the entire session." 712 ::= { raqmonParticipantEntry 32 } 714 raqmonParticipantLostPackets OBJECT-TYPE 715 SYNTAX Counter32 716 MAX-ACCESS read-only 717 STATUS current 718 DESCRIPTION 719 "Count of packets lost by this 720 receiver for the entire session." 721 ::= { raqmonParticipantEntry 33 } 723 raqmonQosTable OBJECT-TYPE 724 SYNTAX SEQUENCE OF RaqmonQosEntry 725 MAX-ACCESS not-accessible 726 STATUS current 727 DESCRIPTION 728 "Table of historical information 729 about quality of service 730 data during sessions. 731 " 732 ::= { raqmonSession 2 } 734 raqmonQosEntry OBJECT-TYPE 735 SYNTAX RaqmonQosEntry 736 MAX-ACCESS not-accessible 737 STATUS current 738 DESCRIPTION 739 "Each entry contains information from 740 a single RAQMON packet. 741 Rows are removed for 742 inactive sessions when implementation 743 specific time or space limits are reached. 744 " 745 INDEX { raqmonParticipantStartDate, 746 raqmonParticipantIndex, raqmonQosTime } 748 ::= { raqmonQosTable 1 } 750 RaqmonQosEntry ::= 751 SEQUENCE { 752 raqmonQosTime 753 Duration, 754 raqmonQosRTT 755 Gauge32, 756 raqmonQosJitter 757 Gauge32, 758 raqmonQosRcvdPackets 759 Integer32, 760 raqmonQosRcvdOctets 761 Integer32, 762 raqmonQosSentPackets 763 Integer32, 764 raqmonQosSentOctets 765 Integer32, 766 raqmonQosLostPackets 767 Integer32, 768 raqmonQosRsvpStatus 769 INTEGER 770 } 772 raqmonQosTime OBJECT-TYPE 773 SYNTAX Duration 774 MAX-ACCESS read-only 775 STATUS current 776 DESCRIPTION 777 "Time of this entry measured 778 from the start of the corresponding 779 participant session." 780 ::= { raqmonQosEntry 1 } 782 raqmonQosRTT OBJECT-TYPE 783 SYNTAX Gauge32 784 MAX-ACCESS read-only 785 STATUS current 786 DESCRIPTION 787 "The round trip time. 788 Will contain the previous value if there was no report 789 for this time (or 2^32 - 1 if value never reported). 790 " 791 ::= { raqmonQosEntry 2 } 793 raqmonQosJitter OBJECT-TYPE 794 SYNTAX Gauge32 795 MAX-ACCESS read-only 796 STATUS current 797 DESCRIPTION 798 "An estimate of delay variation 799 as observed by this receiver. 800 Will contain the previous value if there was no report 801 for this time (or 2^32 - 1 if value never reported). 802 " 803 ::= { raqmonQosEntry 3 } 805 raqmonQosRcvdPackets OBJECT-TYPE 806 SYNTAX Integer32 807 MAX-ACCESS read-only 808 STATUS current 809 DESCRIPTION 810 "Count of packets received by this receiver 811 since the last entry containing a value for this field. 812 This is not a cumulative 813 value since the start of the session. 814 Set to -1 if value not reported for this time. 815 " 816 ::= { raqmonQosEntry 4 } 818 raqmonQosRcvdOctets OBJECT-TYPE 819 SYNTAX Integer32 820 MAX-ACCESS read-only 821 STATUS current 822 DESCRIPTION 823 "Count of octets received by this receiver 824 since the last entry containing a value for this field. 825 This is not a cumulative value 826 since the start of the session. 827 Set to -1 if value not reported for this time. 828 " 829 ::= { raqmonQosEntry 5 } 831 raqmonQosSentPackets OBJECT-TYPE 832 SYNTAX Integer32 833 MAX-ACCESS read-only 834 STATUS current 835 DESCRIPTION 836 "Count of packets sent since the last entry containing a 837 value for this field. 838 This is not a cumulative value since 839 the start of the session. 840 Set to -1 if value not reported for this time. 841 " 842 ::= { raqmonQosEntry 6 } 844 raqmonQosSentOctets OBJECT-TYPE 845 SYNTAX Integer32 846 MAX-ACCESS read-only 847 STATUS current 848 DESCRIPTION 849 "Count of octets sent since the last entry containing a 850 value for this field. 851 This is not a cumulative value 852 since the start of the session. 853 Set to -1 if value not reported for this time. 854 " 855 ::= { raqmonQosEntry 7 } 857 raqmonQosLostPackets OBJECT-TYPE 858 SYNTAX Integer32 859 MAX-ACCESS read-only 860 STATUS current 861 DESCRIPTION 862 "A count of packets lost as observed by this receiver 863 since the last entry containing a value for this field. 864 Set to -1 if value not reported for this time." 865 ::= { raqmonQosEntry 8 } 867 raqmonQosRsvpStatus OBJECT-TYPE 868 SYNTAX INTEGER 869 { 870 unknown(-1), 871 notInUse(0), 872 disabled(1), 873 reservationPending(2), 874 reservationFailed(3), 875 reservationSuccess(4) 876 } 877 MAX-ACCESS read-only 878 STATUS current 879 DESCRIPTION 880 "The RSVP status. 881 Will contain the previous value if there was no report 882 for this time (or if no 883 value was ever reported)." 884 ::= { raqmonQosEntry 9 } 886 raqmonParticipantAddrTable OBJECT-TYPE 887 SYNTAX SEQUENCE OF RaqmonParticipantAddrEntry 888 MAX-ACCESS not-accessible 889 STATUS current 890 DESCRIPTION 891 "Maps raqmonParticipantAddr to the index of the 892 raqmonParticipantTable. This table allows management 893 applications to find entries 894 sorted by raqmonParticipantAddr 895 rather than raqmonParticipantStartDate." 896 ::= { raqmonSession 3 } 898 raqmonParticipantAddrEntry OBJECT-TYPE 899 SYNTAX RaqmonParticipantAddrEntry 900 MAX-ACCESS not-accessible 901 STATUS current 902 DESCRIPTION 903 "Each entry corresponds to exactly one entry in the 904 raqmonParticipantEntry - the entry containing the 905 index pair rraqmonParticipantStartDate, 906 raqmonParticipantIndex." 907 INDEX { raqmonParticipantAddr, 908 raqmonParticipantStartDate, 909 raqmonParticipantIndex } 910 ::= { raqmonParticipantAddrTable 1 } 912 RaqmonParticipantAddrEntry ::= 913 SEQUENCE { 914 raqmonParticipantAddrEndDate 915 RaqmonDateAndTime 916 } 918 raqmonParticipantAddrEndDate OBJECT-TYPE 919 SYNTAX RaqmonDateAndTime 920 MAX-ACCESS read-only 921 STATUS current 922 DESCRIPTION 923 "The value of 924 raqmonParticipantEndDate for the corresponding 925 raqmonParticipantEntry." 926 ::= { raqmonParticipantAddrEntry 1 } 928 raqmonException OBJECT IDENTIFIER ::= { raqmonMIBObjects 2 } 930 raqmonSessionExceptionTable OBJECT-TYPE 931 SYNTAX SEQUENCE OF RaqmonSessionExceptionEntry 932 MAX-ACCESS not-accessible 933 STATUS current 934 DESCRIPTION 935 "This table creates filters so that a 936 management station can 937 get immediate notification of a 938 session that has had poor 939 quality of service." 940 ::= { raqmonException 2 } 942 raqmonSessionExceptionEntry OBJECT-TYPE 943 SYNTAX RaqmonSessionExceptionEntry 944 MAX-ACCESS not-accessible 945 STATUS current 946 DESCRIPTION 947 "A conceptual row in the raqmonSessionExceptionTable." 948 INDEX { raqmonSessionExceptionIndex } 949 ::= { raqmonSessionExceptionTable 1 } 951 RaqmonSessionExceptionEntry ::= 952 SEQUENCE { 953 raqmonSessionExceptionIndex 954 INTEGER, 955 raqmonSessionExceptionJitterThreshold 956 Unsigned32, 957 raqmonSessionExceptionRttThreshold 958 Unsigned32, 959 raqmonSessionExceptionLostPacketsThreshold 960 Integer32, 961 raqmonSessionExceptionRowStatus 962 RowStatus 963 } 965 raqmonSessionExceptionIndex OBJECT-TYPE 966 SYNTAX INTEGER (1..65535) 967 MAX-ACCESS not-accessible 968 STATUS current 969 DESCRIPTION 970 "An index that uniquely identifies an 971 entry in the raqmonSessionExceptionTable." 972 ::= { raqmonSessionExceptionEntry 2 } 974 raqmonSessionExceptionJitterThreshold OBJECT-TYPE 975 SYNTAX Unsigned32 976 MAX-ACCESS read-write 977 STATUS current 978 DESCRIPTION 979 "Threshold for jitter in units of milliseconds. 980 The value during a session must be greater than or 981 equal to this value for an exception to be created." 982 ::= { raqmonSessionExceptionEntry 3 } 984 raqmonSessionExceptionRttThreshold OBJECT-TYPE 985 SYNTAX Unsigned32 986 MAX-ACCESS read-write 987 STATUS current 988 DESCRIPTION 989 "Threshold for round trip time in units of milliseconds. 990 The value during a session must be greater than or 991 equal to this value for an exception to be created." 992 ::= { raqmonSessionExceptionEntry 4 } 994 raqmonSessionExceptionLostPacketsThreshold OBJECT-TYPE 995 SYNTAX Integer32 (0..1000) 996 MAX-ACCESS read-write 997 STATUS current 998 DESCRIPTION 999 "Threshold for lost packets in 1000 units of tenth of a percent. 1002 The value during a session must be greater than or 1003 equal to this value for an exception to be created." 1004 ::= { raqmonSessionExceptionEntry 5 } 1006 raqmonSessionExceptionRowStatus OBJECT-TYPE 1007 SYNTAX RowStatus 1008 MAX-ACCESS read-create 1009 STATUS current 1010 DESCRIPTION 1011 "Value of 'active' when exceptions 1012 are being monitored by the system. 1013 A newly-created conceptual row must have the all 1014 read-create objects initialized 1015 before becoming 'active'. 1016 A conceptual row that is in 1017 the 'notReady' or 'notInService' 1018 state MAY be removed after 5 minutes." 1019 ::= { raqmonSessionExceptionEntry 7 } 1021 raqmonConfig OBJECT IDENTIFIER ::= { raqmonMIBObjects 3 } 1023 raqmonConfigPort OBJECT-TYPE 1024 SYNTAX Unsigned32 (0..65535) 1025 MAX-ACCESS read-write 1026 STATUS current 1027 DESCRIPTION 1028 "The UDP port to listen on for RAQMON reports." 1029 ::= { raqmonConfig 1 } 1031 raqmonConfigPDUTransport OBJECT-TYPE 1032 SYNTAX INTEGER 1033 { 1034 other(0), 1035 rtcp(1), 1036 snmp(2) 1037 } 1038 MAX-ACCESS read-only 1039 STATUS current 1040 DESCRIPTION 1041 "The PDU transport used by this collector." 1042 ::= { raqmonConfig 2 } 1043 -- editor note: does this need to be read-write? Can a collector support 1044 -- multiple transports simultaneously? 1046 raqmonConfigRaqmonPDUs OBJECT-TYPE 1047 SYNTAX Counter32 1048 MAX-ACCESS read-only 1049 STATUS current 1050 DESCRIPTION 1051 "Count of RAQMON PDUs received by the Collector." 1052 ::= { raqmonConfig 3 } 1054 -- RAQMON PDU Definition 1056 raqmonPDU OBJECT IDENTIFIER ::= { raqmonMIBObjects 4 } 1058 raqmonPDUBasicPDU OBJECT-TYPE 1059 SYNTAX OCTET STRING 1060 MAX-ACCESS read-only 1061 STATUS current 1062 DESCRIPTION 1063 "A binary representationof the Basic RAQMON PDU," 1064 REFERENCE "[SIDDIQUI3 - Section 4.1]" 1065 ::= { raqmonPDU 1 } 1067 raqmonConformance OBJECT IDENTIFIER ::= { raqmon 2 } 1069 raqmonGroups OBJECT IDENTIFIER ::= { raqmonConformance 1 } 1071 raqmonCollectorGroup OBJECT-GROUP 1072 OBJECTS { 1073 raqmonParticipantStartDate, 1074 raqmonParticipantIndex, 1075 raqmonParticipantAddr, 1076 raqmonParticipantSendPort, 1077 raqmonParticipantRecvPort, 1078 raqmonParticipantSetupDelay, 1079 raqmonParticipantName, 1080 raqmonParticipantTool, 1081 raqmonParticipantQosCount, 1082 raqmonParticipantEndDate, 1083 raqmonParticipantRcvdPT, 1084 raqmonParticipantSentPT, 1085 raqmonParticipantActive, 1086 raqmonParticipantPeerIndex, 1087 raqmonParticipantPeerAddr, 1088 raqmonParticipantSrcLayer2, 1089 raqmonParticipantDestLayer2, 1090 raqmonParticipantSrcLayer3, 1091 raqmonParticipantDestLayer3, 1092 raqmonParticipantCPUMean, 1093 raqmonParticipantCPUMin, 1094 raqmonParticipantCPUMax, 1095 raqmonParticipantMemoryMean, 1096 raqmonParticipantMemoryMin, 1097 raqmonParticipantMemoryMax, 1098 raqmonParticipantRTTMean, 1099 raqmonParticipantRTTMin, 1100 raqmonParticipantRTTMax, 1101 raqmonParticipantJitterMean, 1102 raqmonParticipantJitterMin, 1103 raqmonParticipantJitterMax, 1104 raqmonParticipantPackets, 1105 raqmonParticipantLostPackets, 1106 raqmonQosTime,raqmonQosRTT, 1107 raqmonQosJitter, raqmonQosRcvdPackets, 1108 raqmonQosRcvdOctets, 1109 raqmonQosSentPackets, 1110 raqmonQosSentOctets, 1111 raqmonQosLostPackets, 1112 raqmonQosRsvpStatus, 1113 raqmonParticipantAddrEndDate, 1114 raqmonConfigPort,raqmonSessionExceptionIndex, 1115 raqmonSessionExceptionJitterThreshold, 1116 raqmonSessionExceptionRttThreshold, 1117 raqmonSessionExceptionLostPacketsThreshold, 1118 raqmonSessionExceptionRowStatus, raqmonConfigPDUTransport, 1119 raqmonConfigRaqmonPDUs } 1120 STATUS current 1121 DESCRIPTION 1122 "Objects used in RAQMON by a Collector" 1123 ::= { raqmonGroups 1 } 1125 raqmonCollectorNotifications NOTIFICATION-GROUP 1126 NOTIFICATIONS { raqmonSessionAlarm } 1127 STATUS current 1128 DESCRIPTION 1129 "Notifications sent by a RAQMON collector." 1130 ::= { raqmonGroups 2 } 1132 raqmonDeviceGroup OBJECT-GROUP 1133 OBJECTS { 1134 raqmonPDUBasicPDU } 1135 STATUS current 1136 DESCRIPTION 1137 "Objects by a device to generate Notifications, for 1138 RAQMON SNMP Transport." 1139 ::= { raqmonGroups 3 } 1141 raqmonDeviceNotifications NOTIFICATION-GROUP 1142 NOTIFICATIONS { raqmonSNMPTransportNotofication } 1143 STATUS current 1144 DESCRIPTION 1145 "Notifications send by a RAQMON device." 1146 ::= { raqmonGroups 4 } 1148 END 1150 6. References 1152 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 1153 for Describing SNMP Management Frameworks", RFC 2571, April 1154 1999. 1156 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1157 of Management Information for TCP/IP-based Internets", STD 1158 16, RFC 1155, May 1990. 1160 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 1161 16, RFC 1212, March 1991. 1163 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 1164 SNMP", RFC 1215, March 1991. 1166 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1167 Rose, M., and S. Waldbusser, "Structure of Management 1168 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1169 1999. 1171 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1172 Rose, M., and S. Waldbusser, "Textual Conventions for 1173 SMIv2", STD 58, RFC 2579, April 1999. 1175 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1176 Rose, M., and S. Waldbusser, "Conformance Statements for 1177 SMIv2", STD 58, RFC 2580, April 1999. 1179 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1180 Network Management Protocol", STD 15, RFC 1157, May 1990. 1182 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1183 "Introduction to Community-based SNMPv2", RFC 1901, January 1184 1996. 1186 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1187 "Transport Mappings for Version 2 of the Simple Network 1188 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1190 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1191 Processing and Dispatching for the Simple Network Management 1192 Protocol (SNMP)", RFC 2572, April 1999. 1194 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1195 (USM) for version 3 of the Simple Network Management 1196 Protocol (SNMPv3)", RFC 2574, April 1999. 1198 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1199 "Protocol Operations for Version 2 of the Simple Network 1200 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1202 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 1203 RFC 2573, April 1999. 1205 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1206 Access Control Model (VACM) for the Simple Network 1207 Management Protocol (SNMP)", RFC 2575, April 1999. 1209 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1210 "Introduction to Version 3 of the Internet-standard Network 1211 Management Framework", RFC 2570, April 1999. 1213 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1214 Requirement Levels", BCP 14, RFC 2119, March 1997. 1216 [RFC2819] Waldbusser, S., "Remote Network Monitoring Management 1217 Information Base", STD 59, RFC 2819, May 2000 1219 [SIDDIQUI1] A. Siddiqui, D.Romascanu, E. Golovinsky, and R. Smith, 1220 "Real-time Application Quality of Service Monitoring (RAQMON) MIB", 1221 Internet-Draft, draft-siddiqui-rmonmib-raqmon-mib-01.txt, February 1222 2002 1224 [SIDDIQUI2] A. Siddiqui, D.Romascanu, E. Golovinsky, and R. Smith, 1225 "Framework for Real-time Application Quality of Service 1226 Monitoring (RAQMON)", Internet-Draft, draft-siddiqui-raqmon- 1227 framework-00.txt, October 2002 1229 [SIDDIQUI3] A. Siddiqui, D.Romascanu, E. Golovinsky, and R. Smith, 1230 "Protocol Data Units for Real-time Application Quality of Service 1231 Monitoring (RAQMON)", Internet-Draft, draft-siddiqui-raqmon-pdu- 1232 00.txt, October 2002 1233 7. Intellectual Property 1235 The IETF takes no position regarding the validity or scope of any 1236 intellectual property or other rights that might be claimed to 1237 pertain to the implementation or use of the technology described in 1238 this document or the extent to which any license under such rights 1239 might or might not be available; neither does it represent that it 1240 has made any effort to identify any such rights. Information on the 1241 IETF's procedures with respect to rights in standards-track and 1242 standards-related documentation can be found in BCP-11. Copies of 1243 claims of rights made available for publication and any assurances of 1244 licenses to be made available, or the result of an attempt made to 1245 obtain a general license or permission for the use of such 1246 proprietary rights by implementors or users of this specification can 1247 be obtained from the IETF Secretariat. 1249 The IETF invites any interested party to bring to its attention any 1250 copyrights, patents or patent applications, or other proprietary 1251 rights which may cover technology that may be required to practice 1252 this standard. Please address the information to the IETF Executive 1253 Director. 1255 8. Security Considerations 1257 There are a number of management objects defined in this MIB 1258 that have a MAX-ACCESS clause of read-write and/or read-create. 1259 Such objects may be considered sensitive or vulnerable in some 1260 network environments. The support for SET operations in a 1261 non-secure environment without proper protection can have a 1262 negative effect on network operations. 1264 There are a number of managed objects in this MIB that may contain 1265 sensitive information. These are: 1267 raqmonParticipantAddr 1269 It is thus important to control even GET access to these objects 1270 and possibly to even encrypt the values of these object when 1271 sending them over the network via SNMP. Not all versions of 1272 SNMP provide features for such a secure environment. 1274 SNMPv1 by itself is not a secure environment. Even if the 1275 network itself is secure (for example by using IPSec), even then, 1276 there is no control as to who on the secure network is allowed 1277 to access and GET/SET (read/change/create/delete) the objects in 1278 this MIB. 1280 It is RECOMMENDED that the implementers consider the security 1281 features as provided by the SNMPv3 framework. Specifically, the 1282 use of the User-based Security Model [RFC2274] and the 1283 View-based Access Control Model [RFC2275] is RECOMMENDED. 1285 It is then a customer/user responsibility to ensure that the SNMP 1286 entity giving access to an instance of this MIB, is properly 1287 configured to give access to the objects only to those 1288 principals (users) that have legitimate rights to indeed GET or 1289 SET (change/create/delete) them. 1291 9. Authors' Addresses 1293 Anwar A. Siddiqui 1294 Avaya Labs 1295 307 Middletown Lincroft Road 1296 Lincroft, New Jersey 07738 1297 USA 1298 Tel: +1 732 852-3200 1299 Fax: +1 732 817-5922 1300 E-mail: anwars@avaya.com 1302 Dan Romascanu 1303 Avaya Inc. 1304 Atidim Technology Park, Bldg. #3 1305 Tel Aviv, 61131 1306 Israel 1307 Tel: +972-3-645-8414 1308 Email: dromasca@avaya.com 1310 Richard Smith 1311 Avaya Inc. 1312 123 Epping Rd 1313 North Ryde NSW 2113 1314 Australia 1315 Tel: +61 2 9886 8987 1316 Email: rsmith9@avaya.com 1318 Eugene Golovinsky 1319 BMC Software 1320 2101 CityWest Blvd. 1321 Houston, Texas 77042 1322 USA 1323 Tel: +1 713 918-1816 1324 Email: eugene_golovinsky@bmc.com 1326 A. Full Copyright Statement 1328 This document and translations of it may be copied and furnished to 1329 others, and derivative works that comment on or otherwise explain it 1330 or assist in its implementation may be prepared, copied, published 1331 and distributed, in whole or in part, without restriction of any 1332 kind, provided that the above copyright notice and this paragraph are 1333 included on all such copies and derivative works. However, this 1334 document itself may not be modified in any way, such as by removing 1335 the copyright notice or references to the Internet Society or other 1336 Internet organizations, except as needed for the purpose of 1337 developing Internet standards in which case the procedures for 1338 copyrights defined in the Internet Standards process must be 1339 followed, or as required to translate it into languages other than 1340 English. 1342 The limited permissions granted above are perpetual and will not be 1343 revoked by the Internet Society or its successors or assigns. 1345 This document and the information contained herein is provided on an 1346 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1347 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1348 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1349 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1350 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1352 B. Log of Changes 1354 (This section will be removed prior to publication as RFC) 1356 B1. Changes in draft-siddiqui-rmonmib-raqmon-mib-02.txt 1358 - changed OID of raqmonSessionAlarm 1359 - clarifications in DESCRIPTION clauses 1360 - changed raqmonParticpantActive SYNTAX to TruthValue 1361 - change range of raqmonParticipantSrcLayer2 and 1362 raqmonParticipantDestLayer2 to (0..7) 1363 - changed raqmonParticipantSrcLayer3 and 1364 raqmonParticipantDestLayer3 to Dscp 1365 - changed counters SYNTAX to Counter32 1366 - added raqmonConfigPDUTransport and raqmonConfigRaqmonPDUs 1367 - added raqmonPDUBasicPDU and raqmonSNMPTransportNotofication 1368 - changed raqmonConformace to reflect the different conformace requirements for 1369 collectors and RAQMON devices