idnits 2.17.1 draft-ietf-dime-diameter-cc-appl-mib-03.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 (January 15, 2010) is 5215 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-04 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: July 19, 2010 Cisco Systems 6 January 15, 2010 8 Diameter Credit Control Application MIB 9 draft-ietf-dime-diameter-cc-appl-mib-03.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 July 19, 2010. 44 Copyright Notice 46 Copyright (c) 2010 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 . . . . . . . . . . . . . . . . . . . . . . . 19 80 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 81 8.1. Normative References . . . . . . . . . . . . . . . . . . . 19 82 8.2. Informative References . . . . . . . . . . . . . . . . . . 20 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 "201001150000Z" -- 15 January 2010 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 (2010). 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." 168 -- RFC Ed.: replace yyyy with actual RFC number and remove this note 170 REVISION "201001150000Z" -- 15 January 2010 171 DESCRIPTION "Initial version as published in RFC yyyy" 173 -- RFC Ed.: replace yyyy with actual RFC number and remove this note 175 ::= { mib-2 XXX } 177 -- RFC Ed.: replace XXX with value assigned by IANA 178 -- and remove this note 180 -- Top-Level Components of this MIB. 181 diameterCcAppMIB OBJECT IDENTIFIER ::= 182 { diameterCCAMIB 2 } 183 diameterCcAppTraps OBJECT IDENTIFIER ::= 184 { diameterCcAppMIB 0 } 185 diameterCcAppObjects OBJECT IDENTIFIER ::= 186 { diameterCcAppMIB 1 } 187 diameterCcAppConform OBJECT IDENTIFIER ::= 188 { diameterCcAppMIB 2 } 190 dccaHostCfgs OBJECT IDENTIFIER ::= { diameterCcAppObjects 1 } 191 dccaPeerCfgs OBJECT IDENTIFIER ::= { diameterCcAppObjects 2 } 192 dccaPeerStats OBJECT IDENTIFIER ::= { diameterCcAppObjects 3 } 194 dccaHostID OBJECT-TYPE 195 SYNTAX SnmpAdminString 196 MAX-ACCESS read-only 197 STATUS current 198 DESCRIPTION 199 "The implementation identification string for 200 the Diameter software in use on the system, 201 for example; 'diameterd'" 202 ::= { dccaHostCfgs 1 } 204 dccaHostIpAddrTable OBJECT-TYPE 205 SYNTAX SEQUENCE OF DccaHostIpAddrEntry 206 MAX-ACCESS not-accessible 207 STATUS current 208 DESCRIPTION 209 "The table listing the Diameter 210 Credit Control host's IP Addresses." 211 ::= { dccaHostCfgs 2 } 213 dccaHostIpAddrEntry OBJECT-TYPE 214 SYNTAX DccaHostIpAddrEntry 215 MAX-ACCESS not-accessible 216 STATUS current 217 DESCRIPTION 218 "A row entry representing a Diameter 219 Credit Control host IP Address." 220 INDEX { dccaHostIpAddrIndex } 221 ::= { dccaHostIpAddrTable 1 } 223 DccaHostIpAddrEntry ::= SEQUENCE { 224 dccaHostIpAddrIndex Unsigned32, 225 dccaHostIpAddrType InetAddressType, 226 dccaHostIpAddress InetAddress 227 } 229 dccaHostIpAddrIndex OBJECT-TYPE 230 SYNTAX Unsigned32 (1..4294967295 ) 231 MAX-ACCESS not-accessible 232 STATUS current 233 DESCRIPTION 234 "A number uniquely identifying the number 235 of IP Addresses supported by this Diameter 236 Credit Control host." 237 ::= { dccaHostIpAddrEntry 1 } 239 dccaHostIpAddrType OBJECT-TYPE 240 SYNTAX InetAddressType 241 MAX-ACCESS read-only 242 STATUS current 243 DESCRIPTION 244 "The type of internet address stored 245 in dccaHostIpAddress." 246 ::= { dccaHostIpAddrEntry 2 } 248 dccaHostIpAddress OBJECT-TYPE 249 SYNTAX InetAddress 250 MAX-ACCESS read-only 251 STATUS current 252 DESCRIPTION 253 "The IP-Address of the host, which is of the 254 type specified in dccaHostIpAddrType." 255 ::= { dccaHostIpAddrEntry 3 } 257 dccaPeerTable OBJECT-TYPE 258 SYNTAX SEQUENCE OF DccaPeerEntry 259 MAX-ACCESS not-accessible 260 STATUS current 261 DESCRIPTION 262 "The table listing information regarding 263 the discovered or configured Diameter 264 Credit Control peers." 265 ::= { dccaPeerCfgs 1 } 267 dccaPeerEntry OBJECT-TYPE 268 SYNTAX DccaPeerEntry 269 MAX-ACCESS not-accessible 270 STATUS current 271 DESCRIPTION 272 "A row entry representing a discovered 273 or configured Diameter Credit Control 274 peer." 275 INDEX { dccaPeerIndex } 276 ::= { dccaPeerTable 1 } 278 DccaPeerEntry ::= SEQUENCE { 279 dccaPeerIndex Unsigned32, 280 dccaPeerId SnmpAdminString, 281 dccaPeerFirmwareRevision Unsigned32, 282 dccaPeerStorageType StorageType, 283 dccaPeerRowStatus RowStatus } 285 dccaPeerIndex OBJECT-TYPE 286 SYNTAX Unsigned32 (1..4294967295) 287 MAX-ACCESS not-accessible 288 STATUS current 289 DESCRIPTION 290 "A number uniquely identifying each Diameter 291 Credit Control peer with which this host 292 communicates." 293 ::= { dccaPeerEntry 1 } 295 dccaPeerId OBJECT-TYPE 296 SYNTAX SnmpAdminString 297 MAX-ACCESS read-create 298 STATUS current 299 DESCRIPTION 300 "The server identifier for the Diameter 301 Credit Control peer." 302 ::= { dccaPeerEntry 2 } 304 dccaPeerFirmwareRevision OBJECT-TYPE 305 SYNTAX Unsigned32 (1..4294967295) 306 MAX-ACCESS read-create 307 STATUS current 308 DESCRIPTION 309 "Firmware revision of peer. If no firmware 310 revision, the revision of the Diameter 311 Credit Control software 312 module may be reported instead." 313 ::= { dccaPeerEntry 3 } 315 dccaPeerStorageType OBJECT-TYPE 316 SYNTAX StorageType 317 MAX-ACCESS read-create 318 STATUS current 319 DESCRIPTION 320 "The storage type for this conceptual row. None 321 of the columnar objects is writable when the 322 conceptual row is permanent." 323 REFERENCE 324 "Textual Conventions for SMIv2, Section 2." 325 DEFVAL { nonVolatile } 326 ::= { dccaPeerEntry 4 } 328 dccaPeerRowStatus OBJECT-TYPE 329 SYNTAX RowStatus 330 MAX-ACCESS read-create 331 STATUS current 332 DESCRIPTION 333 "The status of this conceptual row. 334 To create a row in this table, a manager must 335 set this object to either createAndGo(4) or 336 createAndWait(5). 338 Until instances of all corresponding columns 339 are appropriately configured, the value of the 340 corresponding instance of the 341 dccaPeerRowStatus column is 'notReady'. 343 In particular, a newly created row cannot be 344 made active until the corresponding dccaPeerId 345 has been set. 347 dccaPeerId may not be modified while the 348 value of this object is active(1): 349 An attempt to set these objects while the value 350 of dccaPeerRowStatus is active(1) will result 351 in an inconsistentValue error. 353 Entries in this table with dccaPeerRowStatus 354 equal to active(1) remain in the table until 355 destroyed. 357 Entries in this table with dccaPeerRowStatus 358 equal to values other than active(1) will be 359 destroyed after timeout (5 minutes). 361 If a dccaPeerId being created via SNMP already 362 exists in another active dccaPeerEntry, then a 363 newly created row 364 cannot be made active until the original row 365 with the dccaPeerId value is destroyed. 367 Upon reload, dccaPeerIndex values may be 368 changed." 370 ::= { dccaPeerEntry 5 } 372 dccaPeerVendorTable OBJECT-TYPE 373 SYNTAX SEQUENCE OF DccaPeerVendorEntry 374 MAX-ACCESS not-accessible 375 STATUS current 376 DESCRIPTION 377 "The table listing the Vendor IDs 378 supported by the peer." 379 ::= { dccaPeerCfgs 2 } 381 dccaPeerVendorEntry OBJECT-TYPE 382 SYNTAX DccaPeerVendorEntry 383 MAX-ACCESS not-accessible 384 STATUS current 385 DESCRIPTION 386 "A row entry representing a 387 Vendor ID supported by the peer." 388 INDEX { 389 dccaPeerIndex, 390 dccaPeerVendorIndex 391 } 392 ::= { dccaPeerVendorTable 1 } 394 DccaPeerVendorEntry ::= SEQUENCE { 395 dccaPeerVendorIndex Unsigned32, 396 dccaPeerVendorId Unsigned32, 397 dccaPeerVendorStorageType StorageType, 398 dccaPeerVendorRowStatus RowStatus 399 } 401 dccaPeerVendorIndex OBJECT-TYPE 402 SYNTAX Unsigned32 (1..4294967295 ) 403 MAX-ACCESS not-accessible 404 STATUS current 405 DESCRIPTION 406 "A number uniquely identifying the Vendor 407 ID supported by the peer." 408 ::= { dccaPeerVendorEntry 1 } 410 dccaPeerVendorId OBJECT-TYPE 411 SYNTAX Unsigned32 412 MAX-ACCESS read-create 413 STATUS current 414 DESCRIPTION 415 "The active Vendor IDs used for peer 416 connections." 417 ::= { dccaPeerVendorEntry 2 } 419 dccaPeerVendorStorageType OBJECT-TYPE 420 SYNTAX StorageType 421 MAX-ACCESS read-create 422 STATUS current 423 DESCRIPTION 424 "The storage type for this conceptual row. An 425 agent implementing the table must allow adding 426 dccaPeerVendorId into the table. None of the 427 columnar objects is writable 428 when the conceptual row is permanent." 429 REFERENCE 430 "Textual Conventions for SMIv2, Section 2." 431 DEFVAL { nonVolatile } 432 ::= { dccaPeerVendorEntry 3 } 434 dccaPeerVendorRowStatus OBJECT-TYPE 435 SYNTAX RowStatus 436 MAX-ACCESS read-create 437 STATUS current 438 DESCRIPTION 439 "The status of this conceptual row. 441 To create a row in this table, a manager must 442 set this object to either createAndGo(4) or 443 createAndWait(5). 445 Until instances of all corresponding columns 446 are appropriately configured, the value of the 447 corresponding instance of the 448 dccaPeerVendorRowStatus column is 'notReady'. 450 In particular, a newly created row cannot be 451 made active until the corresponding 452 dccaPeerVendorId has been set. 454 dccaPeerVendorId may not be modified while the 455 value of this object is active(1): 456 An attempt to set these objects while the 457 value of dccaPeerVendorRowStatus is active(1) 458 will result in an inconsistentValue error. 460 Entries in this table with 461 dccaPeerVendorRowStatus equal to 462 active(1) remain in the table until destroyed. 464 Entries in this table with 465 dccaPeerVendorRowStatus equal to 466 values other than active(1) will be destroyed 467 after timeout (5 minutes). 469 If the peer vendor id being created via SNMP 470 already exists 471 in another active dccaPeerVendorEntry, 472 then a newly 473 created row cannot be made active until the 474 original row with the peer vendor id value is 475 destroyed. 477 Upon reload, dccaPeerVendorIndex values may be 478 changed." 479 ::= { dccaPeerVendorEntry 4 } 481 -- per-peer statistics 483 dccaPerPeerStatsTable OBJECT-TYPE 484 SYNTAX SEQUENCE OF DccaPerPeerStatsEntry 485 MAX-ACCESS not-accessible 486 STATUS current 487 DESCRIPTION 488 "The table listing the Diameter 489 Credit Control per-peer Statistics." 490 ::= { dccaPeerStats 1 } 492 dccaPerPeerStatsEntry OBJECT-TYPE 493 SYNTAX DccaPerPeerStatsEntry 494 MAX-ACCESS not-accessible 495 STATUS current 496 DESCRIPTION 497 "A row entry representing a Diameter 498 Credit Control Peer." 499 INDEX { dccaPeerIndex } 500 ::= { dccaPerPeerStatsTable 1 } 502 DccaPerPeerStatsEntry ::= SEQUENCE { 503 dccaPerPeerStatsCCRIn Counter32, 504 dccaPerPeerStatsCCROut Counter32, 505 dccaPerPeerStatsCCRDropped Counter32, 506 dccaPerPeerStatsCCAIn Counter32, 507 dccaPerPeerStatsCCAOut Counter32, 508 dccaPerPeerStatsCCADropped Counter32, 509 dccaPerPeerStatsRARIn Counter32, 510 dccaPerPeerStatsRARDropped Counter32, 511 dccaPerPeerStatsRAAOut Counter32, 512 dccaPerPeerStatsRAADropped Counter32, 513 dccaPerPeerStatsSTROut Counter32, 514 dccaPerPeerStatsSTRDropped Counter32, 515 dccaPerPeerStatsSTAIn Counter32, 516 dccaPerPeerStatsSTADropped Counter32, 517 dccaPerPeerStatsAAROut Counter32, 518 dccaPerPeerStatsAARDropped Counter32, 519 dccaPerPeerStatsAAAIn Counter32, 520 dccaPerPeerStatsAAADropped Counter32, 521 dccaPerPeerStatsASRIn Counter32, 522 dccaPerPeerStatsASRDropped Counter32, 523 dccaPerPeerStatsASAOut Counter32, 524 dccaPerPeerStatsASADropped Counter32 } 526 dccaPerPeerStatsCCRIn OBJECT-TYPE 527 SYNTAX Counter32 528 MAX-ACCESS read-only 529 STATUS current 530 DESCRIPTION 531 "Number of Diameter Credit-Control-Request 532 (CCR) messages received, per peer." 533 ::= { dccaPerPeerStatsEntry 2 } 535 dccaPerPeerStatsCCROut OBJECT-TYPE 536 SYNTAX Counter32 537 MAX-ACCESS read-only 538 STATUS current 539 DESCRIPTION 540 "Number of Diameter Credit-Control-Request (CCR) 541 messages sent, per peer." 542 ::= { dccaPerPeerStatsEntry 3 } 544 dccaPerPeerStatsCCRDropped OBJECT-TYPE 545 SYNTAX Counter32 546 MAX-ACCESS read-only 547 STATUS current 548 DESCRIPTION 549 "Number of Diameter Credit-Control-Request (CCR) 550 messages dropped, per peer." 551 ::= { dccaPerPeerStatsEntry 4 } 553 dccaPerPeerStatsCCAIn OBJECT-TYPE 554 SYNTAX Counter32 555 MAX-ACCESS read-only 556 STATUS current 557 DESCRIPTION 558 "Number of Diameter Credit-Control-Answer (CCA) 559 messages received, per peer." 560 ::= { dccaPerPeerStatsEntry 5 } 562 dccaPerPeerStatsCCAOut OBJECT-TYPE 563 SYNTAX Counter32 564 MAX-ACCESS read-only 565 STATUS current 566 DESCRIPTION 567 "Number of Diameter Credit-Control-Answer (CCA) 568 messages sent, per peer." 569 ::= { dccaPerPeerStatsEntry 6 } 571 dccaPerPeerStatsCCADropped OBJECT-TYPE 572 SYNTAX Counter32 573 MAX-ACCESS read-only 574 STATUS current 575 DESCRIPTION 576 "Number of Diameter Credit-Control-Answer (CCA) 577 messages dropped, per peer." 578 ::= { dccaPerPeerStatsEntry 7 } 580 dccaPerPeerStatsRARIn OBJECT-TYPE 581 SYNTAX Counter32 582 MAX-ACCESS read-only 583 STATUS current 584 DESCRIPTION 585 "Number of Diameter Re-Auth-Request (RAR) 586 messages received, per peer." 587 ::= { dccaPerPeerStatsEntry 8 } 589 dccaPerPeerStatsRARDropped OBJECT-TYPE 590 SYNTAX Counter32 591 MAX-ACCESS read-only 592 STATUS current 593 DESCRIPTION 594 "Number of Diameter Re-Auth-Request (RAR) 595 messages dropped, per peer." 596 ::= { dccaPerPeerStatsEntry 9 } 598 dccaPerPeerStatsRAAOut OBJECT-TYPE 599 SYNTAX Counter32 600 MAX-ACCESS read-only 601 STATUS current 602 DESCRIPTION 603 "Number of Diameter Re-Auth-Answer (RAA) 604 messages transmitted, per peer." 605 ::= { dccaPerPeerStatsEntry 10 } 607 dccaPerPeerStatsRAADropped OBJECT-TYPE 608 SYNTAX Counter32 609 MAX-ACCESS read-only 610 STATUS current 611 DESCRIPTION 612 "Number of Diameter Re-Auth-Answer (RAA) 613 messages dropped, per peer." 614 ::= { dccaPerPeerStatsEntry 11 } 616 dccaPerPeerStatsSTROut OBJECT-TYPE 617 SYNTAX Counter32 618 MAX-ACCESS read-only 619 STATUS current 620 DESCRIPTION 621 "Number of Diameter 622 Session-Termination-Request (STR) 623 messages transmitted, per peer." 624 ::= { dccaPerPeerStatsEntry 12 } 626 dccaPerPeerStatsSTRDropped OBJECT-TYPE 627 SYNTAX Counter32 628 MAX-ACCESS read-only 629 STATUS current 630 DESCRIPTION 631 "Number of Diameter 632 Session-Termination-Request (STR) 633 messages dropped, per peer." 634 ::= { dccaPerPeerStatsEntry 13 } 636 dccaPerPeerStatsSTAIn OBJECT-TYPE 637 SYNTAX Counter32 638 MAX-ACCESS read-only 639 STATUS current 640 DESCRIPTION 641 "Number of Diameter 642 Session-Termination-Answer (STA) 643 messages received, per peer." 644 ::= { dccaPerPeerStatsEntry 14 } 646 dccaPerPeerStatsSTADropped OBJECT-TYPE 647 SYNTAX Counter32 648 MAX-ACCESS read-only 649 STATUS current 650 DESCRIPTION 651 "Number of Diameter 652 Session-Termination-Answer (STA) 653 messages dropped, per peer." 654 ::= { dccaPerPeerStatsEntry 15 } 656 dccaPerPeerStatsAAROut OBJECT-TYPE 657 SYNTAX Counter32 658 MAX-ACCESS read-only 659 STATUS current 660 DESCRIPTION 661 "Number of Diameter AA-Request (AAR) 662 messages transmitted, per peer." 663 ::= { dccaPerPeerStatsEntry 16 } 665 dccaPerPeerStatsAARDropped OBJECT-TYPE 666 SYNTAX Counter32 667 MAX-ACCESS read-only 668 STATUS current 669 DESCRIPTION 670 "Number of Diameter AA-Request (AAR) 671 messages dropped, per peer." 672 ::= { dccaPerPeerStatsEntry 17 } 674 dccaPerPeerStatsAAAIn OBJECT-TYPE 675 SYNTAX Counter32 676 MAX-ACCESS read-only 677 STATUS current 678 DESCRIPTION 679 "Number of Diameter AA-Answer (AAA) 680 messages received, per peer." 681 ::= { dccaPerPeerStatsEntry 18 } 683 dccaPerPeerStatsAAADropped OBJECT-TYPE 684 SYNTAX Counter32 685 MAX-ACCESS read-only 686 STATUS current 687 DESCRIPTION 688 "Number of Diameter AA-Answer (AAA) 689 messages dropped, per peer." 690 ::= { dccaPerPeerStatsEntry 19 } 692 dccaPerPeerStatsASRIn OBJECT-TYPE 693 SYNTAX Counter32 694 MAX-ACCESS read-only 695 STATUS current 696 DESCRIPTION 697 "Number of Diameter Abort-Session-Request 698 (ASR) messages received, per peer." 699 ::= { dccaPerPeerStatsEntry 20 } 701 dccaPerPeerStatsASRDropped OBJECT-TYPE 702 SYNTAX Counter32 703 MAX-ACCESS read-only 704 STATUS current 705 DESCRIPTION 706 "Number of Diameter Abort-Session-Request 707 (ASR) messages dropped, per peer." 708 ::= { dccaPerPeerStatsEntry 21 } 710 dccaPerPeerStatsASAOut OBJECT-TYPE 711 SYNTAX Counter32 712 MAX-ACCESS read-only 713 STATUS current 714 DESCRIPTION 715 "Number of Diameter Abort-Session-Answer 716 (ASA) messages transmitted, per peer." 717 ::= { dccaPerPeerStatsEntry 22 } 719 dccaPerPeerStatsASADropped OBJECT-TYPE 720 SYNTAX Counter32 721 MAX-ACCESS read-only 722 STATUS current 723 DESCRIPTION 724 "Number of Diameter Abort-Session-Answer 725 (ASA) messages dropped, per peer." 726 ::= { dccaPerPeerStatsEntry 23 } 728 -- Conformance dccaMIBCompliances 730 dccaMIBCompliances 731 OBJECT IDENTIFIER ::= { diameterCcAppConform 1 } dccaMIBGroups 732 OBJECT IDENTIFIER ::= { diameterCcAppConform 2 } 734 -- Compliance Statements 736 dccaMIBCompliance MODULE-COMPLIANCE 737 STATUS current 738 DESCRIPTION 739 "The compliance statement for Diameter Credit 740 Control application entities." 741 MODULE -- this module 742 MANDATORY-GROUPS { dccaPeerStatsGroup } 744 GROUP 745 dccaHostCfgGroup 746 DESCRIPTION 747 "This group is only mandatory for a system that 748 supports Local DCCA Host configuration." 750 GROUP 751 dccaPeerCfgGroup 752 DESCRIPTION 753 "This group is only mandatory for a system that 754 supports DCCA Peer configuration." 756 ::= { dccaMIBCompliances 1 } 758 -- Units of Conformance 760 dccaHostCfgGroup OBJECT-GROUP 761 OBJECTS { 762 dccaHostIpAddrType, 763 dccaHostIpAddress, 764 dccaHostID 765 } 766 STATUS current 767 DESCRIPTION 768 "A collection of objects providing 769 configuration common to the server." 770 ::= { dccaMIBGroups 1 } 772 dccaPeerCfgGroup OBJECT-GROUP 773 OBJECTS { 774 dccaPeerId, 775 dccaPeerVendorId, 776 dccaPeerStorageType, 777 dccaPeerVendorStorageType, 778 dccaPeerFirmwareRevision, 779 dccaPeerRowStatus, 780 dccaPeerVendorRowStatus 781 } 782 STATUS current 783 DESCRIPTION 784 "A collection of objects providing peer 785 configuration common to the server." 786 ::= { dccaMIBGroups 2 } 788 dccaPeerStatsGroup OBJECT-GROUP 789 OBJECTS { 790 dccaPerPeerStatsCCRIn, 791 dccaPerPeerStatsCCROut, 792 dccaPerPeerStatsCCRDropped, 793 dccaPerPeerStatsCCAIn, 794 dccaPerPeerStatsCCAOut, 795 dccaPerPeerStatsCCADropped, 796 dccaPerPeerStatsRARIn, 797 dccaPerPeerStatsRARDropped, 798 dccaPerPeerStatsRAAOut, 799 dccaPerPeerStatsRAADropped, 800 dccaPerPeerStatsSTROut, 801 dccaPerPeerStatsSTRDropped, 802 dccaPerPeerStatsSTAIn, 803 dccaPerPeerStatsSTADropped, 804 dccaPerPeerStatsAAROut, 805 dccaPerPeerStatsAARDropped, 806 dccaPerPeerStatsAAAIn, 807 dccaPerPeerStatsAAADropped, 808 dccaPerPeerStatsASRIn, 809 dccaPerPeerStatsASRDropped, 810 dccaPerPeerStatsASAOut, 811 dccaPerPeerStatsASADropped 812 } 813 STATUS current 814 DESCRIPTION 815 "A collection of objects providing peer 816 statistics common to the server." 817 ::= { dccaMIBGroups 3 } 819 END 821 5. IANA Considerations 823 The MIB module in this document uses the following IANA-assigned 824 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 826 Descriptor OBJECT IDENTIFIER value 827 -------------- ----------------------- 828 diameterCCAMIB { mib-2 XXX } 830 Editor's Note (to be removed prior to publication) The IANA is 831 requested to assign a value for "XXX" under the 'mib-2' subtree 832 and to record the assignment in the SMI Numbers registry. When 833 the assignment has been made, the RFC Editor is asked to replace 834 "XXX" (here and in the MIB module) with the assigned value and to 835 remove this note. 837 6. Security Considerations 839 SNMPv1 by itself is not a secure environment. Even if the network 840 itself is secure (for example by using IPSec), there is no control as 841 to who on the secure network is allowed to access and GET (read) the 842 objects in this MIB. 844 It is recommended that the implementers consider the security 845 features as provided by the SNMPv3 framework. Specifically, the use 846 of the User-based Security Model [RFC3414] and the View-based Access 847 Control Model [RFC3415] is recommended. 849 It is then a customer/user responsibility to ensure that the SNMP 850 entity giving access to an instance of this MIB, is properly 851 configured to give access to the objects only to those principals 852 (users) that have legitimate rights to indeed GET or SET (change/ 853 create/delete) them. 855 7. Acknowledgements 857 Thanks to Sumanth Mithra and Biswaranjan Panda for helpful 858 suggestions and feedback. 860 8. References 862 8.1. Normative References 864 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 865 Requirement Levels", BCP 14, RFC 2119, March 1997. 867 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 868 Schoenwaelder, Ed., "Structure of Management Information 869 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 871 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 872 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 873 STD 58, RFC 2579, April 1999. 875 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 876 "Conformance Statements for SMIv2", STD 58, RFC 2580, 877 April 1999. 879 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 880 Architecture for Describing Simple Network Management 881 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 882 December 2002. 884 [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. 885 Arkko, "Diameter Base Protocol", RFC 3588, September 2003. 887 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 888 Schoenwaelder, "Textual Conventions for Internet Network 889 Addresses", RFC 4001, February 2005. 891 [RFC4006] Hakala, H., Mattila, L., Koskinen, J-P., Stura, M., and J. 892 Loughney, "Diameter Credit-Control Application", RFC 4006, 893 August 2005. 895 8.2. Informative References 897 [I-D.ietf-dime-diameter-base-protocol-mib] 898 Zorn, G. and S. Comerica, "Diameter Base Protocol MIB", 899 draft-ietf-dime-diameter-base-protocol-mib-04 (work in 900 progress), November 2009. 902 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 903 "Introduction and Applicability Statements for Internet- 904 Standard Management Framework", RFC 3410, December 2002. 906 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model 907 (USM) for version 3 of the Simple Network Management 908 Protocol (SNMPv3)", STD 62, RFC 3414, December 2002. 910 [RFC3415] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 911 Access Control Model (VACM) for the Simple Network 912 Management Protocol (SNMP)", STD 62, RFC 3415, 913 December 2002. 915 Authors' Addresses 917 Glen Zorn (editor) 918 Network Zen 919 1463 East Republican Street, #358 920 Seattle, Washington 98112 921 USA 923 Email: gwz@net-zen.net 925 Subash Comerica 926 Cisco Systems 927 Global Development Centre, Prestige Waterford 928 No. 9 Brunton Road 929 BGL3/MZ/ 930 Bangalore, Karnataka 560025 931 India 933 Phone: +91 80 4103 6427 934 Email: subashtc@cisco.com