idnits 2.17.1 draft-ietf-dime-diameter-cc-appl-mib-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Sep 2009 rather than the newer Notice from 28 Dec 2009. (See https://trustee.ietf.org/license-info/) Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (December 4, 2009) is 5256 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) ** Obsolete normative reference: RFC 3588 (Obsoleted by RFC 6733) ** Obsolete normative reference: RFC 4006 (Obsoleted by RFC 8506) == Outdated reference: A later version (-06) exists of draft-ietf-dime-diameter-base-protocol-mib-03 Summary: 3 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group G. Zorn, Ed. 3 Internet-Draft Network Zen 4 Intended status: Standards Track S. Comerica 5 Expires: June 7, 2010 Cisco Systems 6 December 4, 2009 8 Diameter Credit Control Application MIB 9 draft-ietf-dime-diameter-cc-appl-mib-02.txt 11 Abstract 13 Along with providing support for certain basic authentication, 14 authorization and accounting functions, the Diameter base protocol is 15 intended to provide a framework for AAA applications. 17 This document defines the Management Information Base (MIB) module 18 which describes the minimum set of objects needed to manage an 19 implementation of the Diameter Credit Control application. 21 Status of this Memo 23 This Internet-Draft is submitted to IETF in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF), its areas, and its working groups. Note that 28 other groups may also distribute working documents as Internet- 29 Drafts. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 The list of current Internet-Drafts can be accessed at 37 http://www.ietf.org/ietf/1id-abstracts.txt. 39 The list of Internet-Draft Shadow Directories can be accessed at 40 http://www.ietf.org/shadow.html. 42 This Internet-Draft will expire on June 7, 2010. 44 Copyright Notice 46 Copyright (c) 2009 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (http://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the BSD License. 59 This document may contain material from IETF Documents or IETF 60 Contributions published or made publicly available before November 61 10, 2008. The person(s) controlling the copyright in some of this 62 material may not have granted the IETF Trust the right to allow 63 modifications of such material outside the IETF Standards Process. 64 Without obtaining an adequate license from the person(s) controlling 65 the copyright in such materials, this document may not be modified 66 outside the IETF Standards Process, and derivative works of it may 67 not be created outside the IETF Standards Process, except to format 68 it for publication as an RFC or to translate it into languages other 69 than English. 71 Table of Contents 73 1. The Internet-Standard Management Framework . . . . . . . . . . 3 74 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 75 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 76 4. Diameter Credit Control Application MIB Definitions . . . . . 3 77 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 78 6. Security Considerations . . . . . . . . . . . . . . . . . . . 18 79 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18 80 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 81 8.1. Normative References . . . . . . . . . . . . . . . . . . . 19 82 8.2. Informative References . . . . . . . . . . . . . . . . . . 19 83 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20 85 1. The Internet-Standard Management Framework 87 For a detailed overview of the documents that describe the current 88 Internet-Standard Management Framework, please refer to section 7 of 89 RFC 3410 [RFC3410]. 91 Managed objects are accessed via a virtual information store, termed 92 the Management Information Base or MIB. MIB objects are generally 93 accessed through the Simple Network Management Protocol (SNMP). 94 Objects in the MIB are defined using the mechanisms defined in the 95 Structure of Management Information (SMI). This memo specifies a MIB 96 module that is compliant to the SMIv2, which is described in STD 58 97 ([RFC2578], [RFC2579], [RFC2580]). In particular, it describes 98 managed objects used for managing the Diameter Credit Control 99 Application [RFC4006]. 101 Discussion of this draft may be directed to the dime Working Group of 102 the IETF (dime@ietf.org).. 104 2. Requirements Language 106 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 107 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 108 document are to be interpreted as described in RFC 2119 [RFC2119]. 110 3. Overview 112 The base Diameter protocol [RFC3588] is never used alone; it is 113 always extended for a particular application. 115 This MIB defines objects supporting the management of the Diameter 116 Credit Control Application protocol as described in [RFC4006]. The 117 MIB specification for the Diameter base protocol 118 [I-D.ietf-dime-diameter-base-protocol-mib] SHOULD be implemented 119 prior to the implementation of this MIB. 121 4. Diameter Credit Control Application MIB Definitions 123 DIAMETER-CC-APPLICATION-MIB DEFINITIONS ::= BEGIN 125 IMPORTS 126 MODULE-IDENTITY, 127 OBJECT-TYPE, 128 Unsigned32, 129 Counter32, 130 mib-2 131 FROM SNMPv2-SMI -- [RFC2578] 133 MODULE-COMPLIANCE, 134 OBJECT-GROUP 135 FROM SNMPv2-CONF -- [RFC2580] 136 StorageType, 137 RowStatus 138 FROM SNMPv2-TC -- [RFC2579] 139 InetAddressType, 140 InetAddress 141 FROM INET-ADDRESS-MIB -- [RFC4001] 142 SnmpAdminString 143 FROM SNMP-FRAMEWORK-MIB; -- [RFC3411] 145 diameterCCAMIB MODULE-IDENTITY 146 LAST-UPDATED "200912040000Z" -- 04 December 2009 147 ORGANIZATION "IETF dime Working Group." 148 CONTACT-INFO 149 "Subash Comerica 150 Cisco Systems 151 Global Development Centre, Prestige Waterford 152 No. 9 Brunton Road 153 BGL3/MZ/ 154 Bangalore, Karnataka 560025 155 India 156 Phone: +91 80 4103 6427 157 Email: subashtc@cisco.com" 158 DESCRIPTION 159 "The MIB module for entities implementing the 160 Diameter Credit Control Application, RFC 4006. 162 Copyright (C) The Internet Society (2009). This initial 163 version of this MIB module was published in RFC yyyy; 164 for full legal notices see the RFC itself. Supplementary 165 information may be available on 166 http://www.ietf.org/copyrights/ianamib.html." 167 -- RFC Ed.: replace yyyy with actual RFC number and remove this note 169 REVISION "200912040000Z" -- 04 December 2009 170 DESCRIPTION "Initial version as published in RFC yyyy" 171 -- RFC Ed.: replace yyyy with actual RFC number and remove this note 172 ::= { mib-2 119 } -- Experimental value assigned by IANA. 174 -- Top-Level Components of this MIB. 175 diameterCcAppMIB OBJECT IDENTIFIER ::= 176 { diameterCCAMIB 2 } 178 diameterCcAppTraps OBJECT IDENTIFIER ::= 179 { diameterCcAppMIB 0 } 180 diameterCcAppObjects OBJECT IDENTIFIER ::= 181 { diameterCcAppMIB 1 } 182 diameterCcAppConform OBJECT IDENTIFIER ::= 183 { diameterCcAppMIB 2 } 185 dccaHostCfgs OBJECT IDENTIFIER ::= { diameterCcAppObjects 1 } 186 dccaPeerCfgs OBJECT IDENTIFIER ::= { diameterCcAppObjects 2 } 187 dccaPeerStats OBJECT IDENTIFIER ::= { diameterCcAppObjects 3 } 189 dccaHostID OBJECT-TYPE 190 SYNTAX SnmpAdminString 191 MAX-ACCESS read-only 192 STATUS current 193 DESCRIPTION 194 "The implementation identification string for 195 the Diameter software in use on the system, 196 for example; 'diameterd'" 197 ::= { dccaHostCfgs 1 } 199 dccaHostIpAddrTable OBJECT-TYPE 200 SYNTAX SEQUENCE OF DccaHostIpAddrEntry 201 MAX-ACCESS not-accessible 202 STATUS current 203 DESCRIPTION 204 "The table listing the Diameter 205 Credit Control host's IP Addresses." 206 ::= { dccaHostCfgs 2 } 208 dccaHostIpAddrEntry OBJECT-TYPE 209 SYNTAX DccaHostIpAddrEntry 210 MAX-ACCESS not-accessible 211 STATUS current 212 DESCRIPTION 213 "A row entry representing a Diameter 214 Credit Control host IP Address." 215 INDEX { dccaHostIpAddrIndex } 216 ::= { dccaHostIpAddrTable 1 } 218 DccaHostIpAddrEntry ::= SEQUENCE { 219 dccaHostIpAddrIndex Unsigned32, 220 dccaHostIpAddrType InetAddressType, 221 dccaHostIpAddress InetAddress 222 } 224 dccaHostIpAddrIndex OBJECT-TYPE 225 SYNTAX Unsigned32 (1..4294967295 ) 226 MAX-ACCESS not-accessible 227 STATUS current 228 DESCRIPTION 229 "A number uniquely identifying the number 230 of IP Addresses supported by this Diameter 231 Credit Control host." 232 ::= { dccaHostIpAddrEntry 1 } 234 dccaHostIpAddrType OBJECT-TYPE 235 SYNTAX InetAddressType 236 MAX-ACCESS read-only 237 STATUS current 238 DESCRIPTION 239 "The type of internet address stored 240 in dccaHostIpAddress." 241 ::= { dccaHostIpAddrEntry 2 } 243 dccaHostIpAddress OBJECT-TYPE 244 SYNTAX InetAddress 245 MAX-ACCESS read-only 246 STATUS current 247 DESCRIPTION 248 "The IP-Address of the host, which is of the 249 type specified in dccaHostIpAddrType." 250 ::= { dccaHostIpAddrEntry 3 } 252 dccaPeerTable OBJECT-TYPE 253 SYNTAX SEQUENCE OF DccaPeerEntry 254 MAX-ACCESS not-accessible 255 STATUS current 256 DESCRIPTION 257 "The table listing information regarding 258 the discovered or configured Diameter 259 Credit Control peers." 260 ::= { dccaPeerCfgs 1 } 262 dccaPeerEntry OBJECT-TYPE 263 SYNTAX DccaPeerEntry 264 MAX-ACCESS not-accessible 265 STATUS current 266 DESCRIPTION 267 "A row entry representing a discovered 268 or configured Diameter Credit Control 269 peer." 270 INDEX { dccaPeerIndex } 271 ::= { dccaPeerTable 1 } 273 DccaPeerEntry ::= SEQUENCE { 274 dccaPeerIndex Unsigned32, 275 dccaPeerId SnmpAdminString, 276 dccaPeerFirmwareRevision Unsigned32, 277 dccaPeerStorageType StorageType, 278 dccaPeerRowStatus RowStatus } 280 dccaPeerIndex OBJECT-TYPE 281 SYNTAX Unsigned32 (1..4294967295) 282 MAX-ACCESS not-accessible 283 STATUS current 284 DESCRIPTION 285 "A number uniquely identifying each Diameter 286 Credit Control peer with which this host 287 communicates." 288 ::= { dccaPeerEntry 1 } 290 dccaPeerId OBJECT-TYPE 291 SYNTAX SnmpAdminString 292 MAX-ACCESS read-create 293 STATUS current 294 DESCRIPTION 295 "The server identifier for the Diameter 296 Credit Control peer." 297 ::= { dccaPeerEntry 2 } 299 dccaPeerFirmwareRevision OBJECT-TYPE 300 SYNTAX Unsigned32 (1..4294967295) 301 MAX-ACCESS read-create 302 STATUS current 303 DESCRIPTION 304 "Firmware revision of peer. If no firmware 305 revision, the revision of the Diameter 306 Credit Control software 307 module may be reported instead." 308 ::= { dccaPeerEntry 3 } 310 dccaPeerStorageType OBJECT-TYPE 311 SYNTAX StorageType 312 MAX-ACCESS read-create 313 STATUS current 314 DESCRIPTION 315 "The storage type for this conceptual row. None 316 of the columnar objects is writable when the 317 conceptual row is permanent." 318 REFERENCE 319 "Textual Conventions for SMIv2, Section 2." 320 DEFVAL { nonVolatile } 321 ::= { dccaPeerEntry 4 } 323 dccaPeerRowStatus OBJECT-TYPE 324 SYNTAX RowStatus 325 MAX-ACCESS read-create 326 STATUS current 327 DESCRIPTION 328 "The status of this conceptual row. 329 To create a row in this table, a manager must 330 set this object to either createAndGo(4) or 331 createAndWait(5). 333 Until instances of all corresponding columns 334 are appropriately configured, the value of the 335 corresponding instance of the 336 dccaPeerRowStatus column is 'notReady'. 338 In particular, a newly created row cannot be 339 made active until the corresponding dccaPeerId 340 has been set. 342 dccaPeerId may not be modified while the 343 value of this object is active(1): 344 An attempt to set these objects while the value 345 of dccaPeerRowStatus is active(1) will result 346 in an inconsistentValue error. 348 Entries in this table with dccaPeerRowStatus 349 equal to active(1) remain in the table until 350 destroyed. 352 Entries in this table with dccaPeerRowStatus 353 equal to values other than active(1) will be 354 destroyed after timeout (5 minutes). 356 If a dccaPeerId being created via SNMP already 357 exists in another active dccaPeerEntry, then a 358 newly created row 359 cannot be made active until the original row 360 with the dccaPeerId value is destroyed. 362 Upon reload, dccaPeerIndex values may be 363 changed." 364 ::= { dccaPeerEntry 5 } 366 dccaPeerVendorTable OBJECT-TYPE 367 SYNTAX SEQUENCE OF DccaPeerVendorEntry 368 MAX-ACCESS not-accessible 369 STATUS current 370 DESCRIPTION 371 "The table listing the Vendor IDs 372 supported by the peer." 373 ::= { dccaPeerCfgs 2 } 375 dccaPeerVendorEntry OBJECT-TYPE 376 SYNTAX DccaPeerVendorEntry 377 MAX-ACCESS not-accessible 378 STATUS current 379 DESCRIPTION 380 "A row entry representing a 381 Vendor ID supported by the peer." 382 INDEX { 383 dccaPeerIndex, 384 dccaPeerVendorIndex 385 } 386 ::= { dccaPeerVendorTable 1 } 388 DccaPeerVendorEntry ::= SEQUENCE { 389 dccaPeerVendorIndex Unsigned32, 390 dccaPeerVendorId Unsigned32, 391 dccaPeerVendorStorageType StorageType, 392 dccaPeerVendorRowStatus RowStatus 393 } 395 dccaPeerVendorIndex OBJECT-TYPE 396 SYNTAX Unsigned32 (1..4294967295 ) 397 MAX-ACCESS not-accessible 398 STATUS current 399 DESCRIPTION 400 "A number uniquely identifying the Vendor 401 ID supported by the peer." 402 ::= { dccaPeerVendorEntry 1 } 404 dccaPeerVendorId OBJECT-TYPE 405 SYNTAX Unsigned32 406 MAX-ACCESS read-create 407 STATUS current 408 DESCRIPTION 409 "The active Vendor IDs used for peer 410 connections." 411 ::= { dccaPeerVendorEntry 2 } 413 dccaPeerVendorStorageType OBJECT-TYPE 414 SYNTAX StorageType 415 MAX-ACCESS read-create 416 STATUS current 417 DESCRIPTION 418 "The storage type for this conceptual row. An 419 agent implementing the table must allow adding 420 dccaPeerVendorId into the table. None of the 421 columnar objects is writable 422 when the conceptual row is permanent." 423 REFERENCE 424 "Textual Conventions for SMIv2, Section 2." 425 DEFVAL { nonVolatile } 426 ::= { dccaPeerVendorEntry 3 } 428 dccaPeerVendorRowStatus OBJECT-TYPE 429 SYNTAX RowStatus 430 MAX-ACCESS read-create 431 STATUS current 432 DESCRIPTION 433 "The status of this conceptual row. 435 To create a row in this table, a manager must 436 set this object to either createAndGo(4) or 437 createAndWait(5). 439 Until instances of all corresponding columns 440 are appropriately configured, the value of the 441 corresponding instance of the 442 dccaPeerVendorRowStatus column is 'notReady'. 444 In particular, a newly created row cannot be 445 made active until the corresponding 446 dccaPeerVendorId has been set. 448 dccaPeerVendorId may not be modified while the 449 value of this object is active(1): 450 An attempt to set these objects while the 451 value of dccaPeerVendorRowStatus is active(1) 452 will result in an inconsistentValue error. 454 Entries in this table with 455 dccaPeerVendorRowStatus equal to 456 active(1) remain in the table until destroyed. 458 Entries in this table with 459 dccaPeerVendorRowStatus equal to 460 values other than active(1) will be destroyed 461 after timeout (5 minutes). 463 If the peer vendor id being created via SNMP 464 already exists 465 in another active dccaPeerVendorEntry, 466 then a newly 467 created row cannot be made active until the 468 original row with the peer vendor id value is 469 destroyed. 471 Upon reload, dccaPeerVendorIndex values may be 472 changed." 473 ::= { dccaPeerVendorEntry 4 } 475 -- per-peer statistics 477 dccaPerPeerStatsTable OBJECT-TYPE 478 SYNTAX SEQUENCE OF DccaPerPeerStatsEntry 479 MAX-ACCESS not-accessible 480 STATUS current 481 DESCRIPTION 482 "The table listing the Diameter 483 Credit Control per-peer Statistics." 484 ::= { dccaPeerStats 1 } 486 dccaPerPeerStatsEntry OBJECT-TYPE 487 SYNTAX DccaPerPeerStatsEntry 488 MAX-ACCESS not-accessible 489 STATUS current 490 DESCRIPTION 491 "A row entry representing a Diameter 492 Credit Control Peer." 493 INDEX { dccaPeerIndex } 494 ::= { dccaPerPeerStatsTable 1 } 496 DccaPerPeerStatsEntry ::= SEQUENCE { 497 dccaPerPeerStatsCCRIn Counter32, 498 dccaPerPeerStatsCCROut Counter32, 499 dccaPerPeerStatsCCRDropped Counter32, 500 dccaPerPeerStatsCCAIn Counter32, 501 dccaPerPeerStatsCCAOut Counter32, 502 dccaPerPeerStatsCCADropped Counter32, 503 dccaPerPeerStatsRARIn Counter32, 504 dccaPerPeerStatsRARDropped Counter32, 505 dccaPerPeerStatsRAAOut Counter32, 506 dccaPerPeerStatsRAADropped Counter32, 507 dccaPerPeerStatsSTROut Counter32, 508 dccaPerPeerStatsSTRDropped Counter32, 509 dccaPerPeerStatsSTAIn Counter32, 510 dccaPerPeerStatsSTADropped Counter32, 511 dccaPerPeerStatsAAROut Counter32, 512 dccaPerPeerStatsAARDropped Counter32, 513 dccaPerPeerStatsAAAIn Counter32, 514 dccaPerPeerStatsAAADropped Counter32, 515 dccaPerPeerStatsASRIn Counter32, 516 dccaPerPeerStatsASRDropped Counter32, 517 dccaPerPeerStatsASAOut Counter32, 518 dccaPerPeerStatsASADropped Counter32 } 520 dccaPerPeerStatsCCRIn OBJECT-TYPE 521 SYNTAX Counter32 522 MAX-ACCESS read-only 523 STATUS current 524 DESCRIPTION 525 "Number of Diameter Credit-Control-Request 526 (CCR) messages received, per peer." 527 ::= { dccaPerPeerStatsEntry 2 } 529 dccaPerPeerStatsCCROut OBJECT-TYPE 530 SYNTAX Counter32 531 MAX-ACCESS read-only 532 STATUS current 533 DESCRIPTION 534 "Number of Diameter Credit-Control-Request (CCR) 535 messages sent, per peer." 536 ::= { dccaPerPeerStatsEntry 3 } 538 dccaPerPeerStatsCCRDropped OBJECT-TYPE 539 SYNTAX Counter32 540 MAX-ACCESS read-only 541 STATUS current 542 DESCRIPTION 543 "Number of Diameter Credit-Control-Request (CCR) 544 messages dropped, per peer." 545 ::= { dccaPerPeerStatsEntry 4 } 547 dccaPerPeerStatsCCAIn OBJECT-TYPE 548 SYNTAX Counter32 549 MAX-ACCESS read-only 550 STATUS current 551 DESCRIPTION 552 "Number of Diameter Credit-Control-Answer (CCA) 553 messages received, per peer." 554 ::= { dccaPerPeerStatsEntry 5 } 556 dccaPerPeerStatsCCAOut OBJECT-TYPE 557 SYNTAX Counter32 558 MAX-ACCESS read-only 559 STATUS current 560 DESCRIPTION 561 "Number of Diameter Credit-Control-Answer (CCA) 562 messages sent, per peer." 563 ::= { dccaPerPeerStatsEntry 6 } 565 dccaPerPeerStatsCCADropped OBJECT-TYPE 566 SYNTAX Counter32 567 MAX-ACCESS read-only 568 STATUS current 569 DESCRIPTION 570 "Number of Diameter Credit-Control-Answer (CCA) 571 messages dropped, per peer." 572 ::= { dccaPerPeerStatsEntry 7 } 574 dccaPerPeerStatsRARIn OBJECT-TYPE 575 SYNTAX Counter32 576 MAX-ACCESS read-only 577 STATUS current 578 DESCRIPTION 579 "Number of Diameter Re-Auth-Request (RAR) 580 messages received, per peer." 581 ::= { dccaPerPeerStatsEntry 8 } 583 dccaPerPeerStatsRARDropped OBJECT-TYPE 584 SYNTAX Counter32 585 MAX-ACCESS read-only 586 STATUS current 587 DESCRIPTION 588 "Number of Diameter Re-Auth-Request (RAR) 589 messages dropped, per peer." 590 ::= { dccaPerPeerStatsEntry 9 } 592 dccaPerPeerStatsRAAOut OBJECT-TYPE 593 SYNTAX Counter32 594 MAX-ACCESS read-only 595 STATUS current 596 DESCRIPTION 597 "Number of Diameter Re-Auth-Answer (RAA) 598 messages transmitted, per peer." 599 ::= { dccaPerPeerStatsEntry 10 } 601 dccaPerPeerStatsRAADropped OBJECT-TYPE 602 SYNTAX Counter32 603 MAX-ACCESS read-only 604 STATUS current 605 DESCRIPTION 606 "Number of Diameter Re-Auth-Answer (RAA) 607 messages dropped, per peer." 608 ::= { dccaPerPeerStatsEntry 11 } 610 dccaPerPeerStatsSTROut OBJECT-TYPE 611 SYNTAX Counter32 612 MAX-ACCESS read-only 613 STATUS current 614 DESCRIPTION 615 "Number of Diameter 616 Session-Termination-Request (STR) 617 messages transmitted, per peer." 618 ::= { dccaPerPeerStatsEntry 12 } 620 dccaPerPeerStatsSTRDropped OBJECT-TYPE 621 SYNTAX Counter32 622 MAX-ACCESS read-only 623 STATUS current 624 DESCRIPTION 625 "Number of Diameter 626 Session-Termination-Request (STR) 627 messages dropped, per peer." 628 ::= { dccaPerPeerStatsEntry 13 } 630 dccaPerPeerStatsSTAIn OBJECT-TYPE 631 SYNTAX Counter32 632 MAX-ACCESS read-only 633 STATUS current 634 DESCRIPTION 635 "Number of Diameter 636 Session-Termination-Answer (STA) 637 messages received, per peer." 638 ::= { dccaPerPeerStatsEntry 14 } 640 dccaPerPeerStatsSTADropped OBJECT-TYPE 641 SYNTAX Counter32 642 MAX-ACCESS read-only 643 STATUS current 644 DESCRIPTION 645 "Number of Diameter 646 Session-Termination-Answer (STA) 647 messages dropped, per peer." 648 ::= { dccaPerPeerStatsEntry 15 } 650 dccaPerPeerStatsAAROut OBJECT-TYPE 651 SYNTAX Counter32 652 MAX-ACCESS read-only 653 STATUS current 654 DESCRIPTION 655 "Number of Diameter AA-Request (AAR) 656 messages transmitted, per peer." 657 ::= { dccaPerPeerStatsEntry 16 } 659 dccaPerPeerStatsAARDropped OBJECT-TYPE 660 SYNTAX Counter32 661 MAX-ACCESS read-only 662 STATUS current 663 DESCRIPTION 664 "Number of Diameter AA-Request (AAR) 665 messages dropped, per peer." 666 ::= { dccaPerPeerStatsEntry 17 } 668 dccaPerPeerStatsAAAIn OBJECT-TYPE 669 SYNTAX Counter32 670 MAX-ACCESS read-only 671 STATUS current 672 DESCRIPTION 673 "Number of Diameter AA-Answer (AAA) 674 messages received, per peer." 675 ::= { dccaPerPeerStatsEntry 18 } 677 dccaPerPeerStatsAAADropped OBJECT-TYPE 678 SYNTAX Counter32 679 MAX-ACCESS read-only 680 STATUS current 681 DESCRIPTION 682 "Number of Diameter AA-Answer (AAA) 683 messages dropped, per peer." 684 ::= { dccaPerPeerStatsEntry 19 } 686 dccaPerPeerStatsASRIn OBJECT-TYPE 687 SYNTAX Counter32 688 MAX-ACCESS read-only 689 STATUS current 690 DESCRIPTION 691 "Number of Diameter Abort-Session-Request 692 (ASR) messages received, per peer." 693 ::= { dccaPerPeerStatsEntry 20 } 695 dccaPerPeerStatsASRDropped OBJECT-TYPE 696 SYNTAX Counter32 697 MAX-ACCESS read-only 698 STATUS current 699 DESCRIPTION 700 "Number of Diameter Abort-Session-Request 701 (ASR) messages dropped, per peer." 702 ::= { dccaPerPeerStatsEntry 21 } 704 dccaPerPeerStatsASAOut OBJECT-TYPE 705 SYNTAX Counter32 706 MAX-ACCESS read-only 707 STATUS current 708 DESCRIPTION 709 "Number of Diameter Abort-Session-Answer 710 (ASA) messages transmitted, per peer." 711 ::= { dccaPerPeerStatsEntry 22 } 713 dccaPerPeerStatsASADropped OBJECT-TYPE 714 SYNTAX Counter32 715 MAX-ACCESS read-only 716 STATUS current 717 DESCRIPTION 718 "Number of Diameter Abort-Session-Answer 719 (ASA) messages dropped, per peer." 720 ::= { dccaPerPeerStatsEntry 23 } 722 -- Conformance dccaMIBCompliances 724 dccaMIBCompliances 725 OBJECT IDENTIFIER ::= { diameterCcAppConform 1 } dccaMIBGroups 726 OBJECT IDENTIFIER ::= { diameterCcAppConform 2 } 728 -- Compliance Statements 730 dccaMIBCompliance MODULE-COMPLIANCE 731 STATUS current 732 DESCRIPTION 733 "The compliance statement for Diameter Credit 734 Control application entities." 735 MODULE -- this module 736 MANDATORY-GROUPS { dccaPeerStatsGroup } 738 GROUP 739 dccaHostCfgGroup 740 DESCRIPTION 741 "This group is only mandatory for a system that 742 supports Local DCCA Host configuration." 744 GROUP 745 dccaPeerCfgGroup 746 DESCRIPTION 747 "This group is only mandatory for a system that 748 supports DCCA Peer configuration." 750 ::= { dccaMIBCompliances 1 } 752 -- Units of Conformance 753 dccaHostCfgGroup OBJECT-GROUP 754 OBJECTS { 755 dccaHostIpAddrType, 756 dccaHostIpAddress, 757 dccaHostID 758 } 759 STATUS current 760 DESCRIPTION 761 "A collection of objects providing 762 configuration common to the server." 763 ::= { dccaMIBGroups 1 } 765 dccaPeerCfgGroup OBJECT-GROUP 766 OBJECTS { 767 dccaPeerId, 768 dccaPeerVendorId, 769 dccaPeerStorageType, 770 dccaPeerVendorStorageType, 771 dccaPeerFirmwareRevision, 772 dccaPeerRowStatus, 773 dccaPeerVendorRowStatus 774 } 775 STATUS current 776 DESCRIPTION 777 "A collection of objects providing peer 778 configuration common to the server." 779 ::= { dccaMIBGroups 2 } 781 dccaPeerStatsGroup OBJECT-GROUP 782 OBJECTS { 783 dccaPerPeerStatsCCRIn, 784 dccaPerPeerStatsCCROut, 785 dccaPerPeerStatsCCRDropped, 786 dccaPerPeerStatsCCAIn, 787 dccaPerPeerStatsCCAOut, 788 dccaPerPeerStatsCCADropped, 789 dccaPerPeerStatsRARIn, 790 dccaPerPeerStatsRARDropped, 791 dccaPerPeerStatsRAAOut, 792 dccaPerPeerStatsRAADropped, 793 dccaPerPeerStatsSTROut, 794 dccaPerPeerStatsSTRDropped, 795 dccaPerPeerStatsSTAIn, 796 dccaPerPeerStatsSTADropped, 797 dccaPerPeerStatsAAROut, 798 dccaPerPeerStatsAARDropped, 799 dccaPerPeerStatsAAAIn, 800 dccaPerPeerStatsAAADropped, 801 dccaPerPeerStatsASRIn, 802 dccaPerPeerStatsASRDropped, 803 dccaPerPeerStatsASAOut, 804 dccaPerPeerStatsASADropped 805 } 806 STATUS current 807 DESCRIPTION 808 "A collection of objects providing peer 809 statistics common to the server." 810 ::= { dccaMIBGroups 3 } 812 END 814 5. IANA Considerations 816 IANA is requested to assign an OID under mib-2. 818 6. Security Considerations 820 SNMPv1 by itself is not a secure environment. Even if the network 821 itself is secure (for example by using IPSec), there is no control as 822 to who on the secure network is allowed to access and GET (read) the 823 objects in this MIB. 825 It is recommended that the implementers consider the security 826 features as provided by the SNMPv3 framework. Specifically, the use 827 of the User-based Security Model [RFC3414] and the View-based Access 828 Control Model [RFC3415] is recommended. 830 It is then a customer/user responsibility to ensure that the SNMP 831 entity giving access to an instance of this MIB, is properly 832 configured to give access to the objects only to those principals 833 (users) that have legitimate rights to indeed GET or SET (change/ 834 create/delete) them. 836 7. Acknowledgements 838 Thanks to Sumanth Mithra and Biswaranjan Panda for helpful 839 suggestions and feedback. 841 8. References 842 8.1. Normative References 844 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 845 Requirement Levels", BCP 14, RFC 2119, March 1997. 847 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 848 Schoenwaelder, Ed., "Structure of Management Information 849 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 851 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 852 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 853 STD 58, RFC 2579, April 1999. 855 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 856 "Conformance Statements for SMIv2", STD 58, RFC 2580, 857 April 1999. 859 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 860 Architecture for Describing Simple Network Management 861 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 862 December 2002. 864 [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. 865 Arkko, "Diameter Base Protocol", RFC 3588, September 2003. 867 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 868 Schoenwaelder, "Textual Conventions for Internet Network 869 Addresses", RFC 4001, February 2005. 871 [RFC4006] Hakala, H., Mattila, L., Koskinen, J-P., Stura, M., and J. 872 Loughney, "Diameter Credit-Control Application", RFC 4006, 873 August 2005. 875 8.2. Informative References 877 [I-D.ietf-dime-diameter-base-protocol-mib] 878 Zorn, G. and S. Comerica, "Diameter Base Protocol MIB", 879 draft-ietf-dime-diameter-base-protocol-mib-03 (work in 880 progress), November 2009. 882 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 883 "Introduction and Applicability Statements for Internet- 884 Standard Management Framework", RFC 3410, December 2002. 886 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model 887 (USM) for version 3 of the Simple Network Management 888 Protocol (SNMPv3)", STD 62, RFC 3414, December 2002. 890 [RFC3415] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 891 Access Control Model (VACM) for the Simple Network 892 Management Protocol (SNMP)", STD 62, RFC 3415, 893 December 2002. 895 Authors' Addresses 897 Glen Zorn (editor) 898 Network Zen 899 1310 East Thomas Street 900 Seattle, Washington 98102 901 +1 (206) 931-0768 903 Email: gwz@net-zen.net 905 Subash Comerica 906 Cisco Systems 907 Global Development Centre, Prestige Waterford 908 No. 9 Brunton Road 909 BGL3/MZ/ 910 Bangalore, Karnataka 560025 911 India 913 Phone: +91 80 4103 6427 914 Email: subashtc@cisco.com