idnits 2.17.1 draft-zorn-dime-diameter-cc-appl-mib-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.ii or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. See https://trustee.ietf.org/license-info/.) -- The document has an IETF Trust Provisions (28 Dec 2009) Section 6.c(i) Publication Limitation clause. 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 date (March 6, 2009) is 5501 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. 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: 'RFC4001' is mentioned on line 127, but not defined == Missing Reference: 'RFC3411' is mentioned on line 129, but not defined == Outdated reference: A later version (-05) exists of draft-zorn-dime-diameter-base-protocol-mib-03 ** Downref: Normative reference to an Informational draft: draft-zorn-dime-diameter-base-protocol-mib (ref. 'BASEMIB') ** Obsolete normative reference: RFC 3588 (Obsoleted by RFC 6733) -- Obsolete informational reference (is this intentional?): RFC 4005 (Obsoleted by RFC 7155) -- Obsolete informational reference (is this intentional?): RFC 4006 (Obsoleted by RFC 8506) Summary: 3 errors (**), 0 flaws (~~), 4 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group G. Zorn 3 Internet-Draft Network Zen 4 Intended status: Standards Track S. Comerica 5 Expires: September 7, 2009 Cisco Systems 6 March 6, 2009 8 Diameter Credit Control Application MIB 9 draft-zorn-dime-diameter-cc-appl-mib-05.txt 11 Status of this Memo 13 This Internet-Draft is submitted to IETF in full conformance with the 14 provisions of BCP 78 and BCP 79. This document may not be modified, 15 and derivative works of it may not be created, except to format it 16 for publication as an RFC or to translate it into languages other 17 than English. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that 21 other groups may also distribute working documents as Internet- 22 Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/ietf/1id-abstracts.txt. 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html. 35 This Internet-Draft will expire on September 7, 2009. 37 Copyright Notice 39 Copyright (c) 2009 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents in effect on the date of 44 publication of this document (http://trustee.ietf.org/license-info). 45 Please review these documents carefully, as they describe your rights 46 and restrictions with respect to this document. 48 Abstract 50 Along with providing support for certain basic authentication, 51 authorization and accounting functions, the Diameter base protocol is 52 intended to provide a framework for AAA applications. 54 This document defines the Management Information Base (MIB) module 55 which describes the minimum set of objects needed to manage an 56 implementation of the Diameter Credit Control application. 58 Table of Contents 60 1. The Internet-Standard Management Framework . . . . . . . . . . 3 61 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 62 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 63 4. Diameter Credit Control Application MIB Definitions . . . . . 3 64 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 65 6. Security Considerations . . . . . . . . . . . . . . . . . . . 18 66 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18 67 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 68 8.1. Normative References . . . . . . . . . . . . . . . . . . . 19 69 8.2. Informative References . . . . . . . . . . . . . . . . . . 19 70 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20 72 1. The Internet-Standard Management Framework 74 For a detailed overview of the documents that describe the current 75 Internet-Standard Management Framework, please refer to section 7 of 76 RFC 3410 [RFC3410]. 78 Managed objects are accessed via a virtual information store, termed 79 the Management Information Base or MIB. MIB objects are generally 80 accessed through the Simple Network Management Protocol (SNMP). 81 Objects in the MIB are defined using the mechanisms defined in the 82 Structure of Management Information (SMI). This memo specifies a MIB 83 module that is compliant to the SMIv2, which is described in STD 58, 84 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 85 [RFC2580]. In particular, it describes managed objects used for 86 managing the Diameter base protocol. 88 Discussion of this draft may be directed to the authors. 90 2. Requirements Language 92 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 93 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 94 document are to be interpreted as described in [RFC2119]. 96 3. Overview 98 The base Diameter protocol [RFC3588] is never used alone; it is 99 always extended for a particular application. Four standard Diameter 100 applications have been defined to date: NASREQ [RFC4005], Mobile IP 101 [RFC4004] [RFC3141], Credit Control [RFC4006] and EAP [RFC4072]; 102 others may be defined in the future. 104 This MIB defines objects supporting the management of the Diameter 105 Credit Control Application protocol as described in [RFC4006]. The 106 MIB specification for the Diameter base protocol [BASEMIB] SHOULD be 107 implemented prior to the implementation of this MIB. 109 4. Diameter Credit Control Application MIB Definitions 111 DIAMETER-CC-APPLICATION-MIB DEFINITIONS ::= BEGIN 113 IMPORTS 114 MODULE-IDENTITY, 115 OBJECT-TYPE, 116 Unsigned32, 117 Counter32 118 FROM SNMPv2-SMI -- [RFC2578] 119 MODULE-COMPLIANCE, 120 OBJECT-GROUP 121 FROM SNMPv2-CONF -- [RFC2580] 122 StorageType, 123 RowStatus 124 FROM SNMPv2-TC -- [RFC2579] 125 InetAddressType, 126 InetAddress 127 FROM INET-ADDRESS-MIB -- [RFC4001] 128 SnmpAdminString 129 FROM SNMP-FRAMEWORK-MIB; -- [RFC3411] 131 diameterCCAMIB MODULE-IDENTITY 132 LAST-UPDATED "200903060000Z" -- 06 March 2009 133 ORGANIZATION "IETF dime Working Group." 134 CONTACT-INFO 135 "Glen Zorn 136 Network Zen 137 1310 East Thomas Street 138 Seattle, WA 98102 139 USA 140 Phone: +1 (206) 377 9035 141 Email: gwz@net-zen.net" 142 DESCRIPTION 143 "The MIB module for entities implementing the 144 Diameter Credit Control Application, RFC 4006. 146 Copyright (C) The Internet Society (2009). This initial 147 version of this MIB module was published in RFC yyyy; 148 for full legal notices see the RFC itself. Supplementary 149 information may be available on 150 http://www.ietf.org/copyrights/ianamib.html." 151 -- RFC Ed.: replace yyyy with actual RFC number and remove this note 153 REVISION "200903060000Z" -- 06 March 2009 154 DESCRIPTION "Initial version as published in RFC yyyy" 155 -- RFC Ed.: replace yyyy with actual RFC number and remove this note 156 ::= { mib-2 119 } -- Experimental value assigned by IANA. 158 -- Top-Level Components of this MIB. 159 diameterCcAppMIB OBJECT ::= 160 { diameterMIB 2 } 161 diameterCcAppTraps OBJECT IDENTIFIER ::= 162 { diameterCcAppMIB 0 } 163 diameterCcAppObjects OBJECT IDENTIFIER ::= 164 { diameterCcAppMIB 1 } 166 diameterCcAppConform OBJECT IDENTIFIER ::= 167 { diameterCcAppMIB 2 } 169 dccaHostCfgs OBJECT IDENTIFIER ::= { diameterCcAppObjects 1 } 170 dccaPeerCfgs OBJECT IDENTIFIER ::= { diameterCCAMIBObjects 2 } 171 dccaPeerStats OBJECT IDENTIFIER ::= { diameterCcAppObjects 3 } 173 dccaHostID OBJECT-TYPE 174 SYNTAX SnmpAdminString 175 MAX-ACCESS read-only 176 STATUS current 177 DESCRIPTION 178 "The implementation identification string for 179 the Diameter software in use on the system, 180 for example; 'diameterd'" 181 ::= { dccaHostCfgs 1 } 183 dccaHostIpAddrTable OBJECT-TYPE 184 SYNTAX SEQUENCE OF DccaHostIpAddrEntry 185 MAX-ACCESS not-accessible 186 STATUS current 187 DESCRIPTION 188 "The table listing the Diameter 189 Credit Control host's IP Addresses." 190 ::= { dccaHostCfgs 2 } 192 dccaHostIpAddrEntry OBJECT-TYPE 193 SYNTAX DccaHostIpAddrEntry 194 MAX-ACCESS not-accessible 195 STATUS current 196 DESCRIPTION 197 "A row entry representing a Diameter 198 Credit Control host IP Address." 199 INDEX { dccaHostIpAddrIndex } 200 ::= { dccaHostIpAddrTable 1 } 202 DccaHostIpAddrEntry ::= SEQUENCE { 203 dccaHostIpAddrIndex Unsigned32, 204 dccaHostIpAddrType InetAddressType, 205 dccaHostIpAddress InetAddress 206 } 208 dccaHostIpAddrIndex OBJECT-TYPE 209 SYNTAX Unsigned32 (1..4294967295 ) 210 MAX-ACCESS not-accessible 211 STATUS current 212 DESCRIPTION 213 "A number uniquely identifying the number 214 of IP Addresses supported by this Diameter 215 Credit Control host." 216 ::= { dccaHostIpAddrEntry 1 } 218 dccaHostIpAddrType OBJECT-TYPE 219 SYNTAX InetAddressType 220 MAX-ACCESS read-only 221 STATUS current 222 DESCRIPTION 223 "The type of internet address stored 224 in dccaHostIpAddress." 225 ::= { dccaHostIpAddrEntry 2 } 227 dccaHostIpAddress OBJECT-TYPE 228 SYNTAX InetAddress 229 MAX-ACCESS read-only 230 STATUS current 231 DESCRIPTION 232 "The IP-Address of the host, which is of the 233 type specified in dccaHostIpAddrType." 234 ::= { dccaHostIpAddrEntry 3 } 236 dccaPeerTable OBJECT-TYPE 237 SYNTAX SEQUENCE OF DcaPeerEntry 238 MAX-ACCESS not-accessible 239 STATUS current 240 DESCRIPTION 241 "The table listing information regarding 242 the discovered or configured Diameter 243 Credit Control peers." 244 ::= { dccaPeerCfgs 1 } 246 dccaPeerEntry OBJECT-TYPE 247 SYNTAX DcaPeerEntry 248 MAX-ACCESS not-accessible 249 STATUS current 250 DESCRIPTION 251 "A row entry representing a discovered 252 or configured Diameter Credit Control 253 peer." 254 INDEX { dccaPeerIndex } 255 ::= { dccaPeerTable 1 } 257 DcaPeerEntry ::= SEQUENCE { 258 dccaPeerIndex Unsigned32, 259 dccaPeerId SnmpAdminString, 260 dccaPeerFirmwareRevision Unsigned32, 261 dccaPeerStorageType StorageType, 262 dccaPeerStatus RowStatus } 264 dccaPeerIndex OBJECT-TYPE 265 SYNTAX Unsigned32 (1..4294967295) 266 MAX-ACCESS not-accessible 267 STATUS current 268 DESCRIPTION 269 "A number uniquely identifying each Diameter 270 Credit Control peer with which this host 271 communicates." 272 ::= { dccaPeerEntry 1 } 274 dccaPeerId OBJECT-TYPE 275 SYNTAX SnmpAdminString 276 MAX-ACCESS read-create 277 STATUS current 278 DESCRIPTION 279 "The server identifier for the Diameter 280 Credit Control peer." 281 ::= { dccaPeerEntry 2 } 283 dccaPeerFirmwareRevision OBJECT-TYPE 284 SYNTAX Unsigned32 (1..4294967295) 285 MAX-ACCESS read-create 286 STATUS current 287 DESCRIPTION 288 "Firmware revision of peer. If no firmware 289 revision, the revision of the Diameter 290 Credit Control software 291 module may be reported instead." 292 ::= { dccaPeerEntry 3 } 294 dccaPeerStorageType OBJECT-TYPE 295 SYNTAX StorageType 296 MAX-ACCESS read-create 297 STATUS current 298 DESCRIPTION 299 "The storage type for this conceptual row. None 300 of the columnar objects is writable when the 301 conceptual row is permanent." 302 REFERENCE 303 "Textual Conventions for SMIv2, Section 2." 304 DEFVAL { nonVolatile } 305 ::= { dccaPeerEntry 4 } 307 dccaPeerStatus OBJECT-TYPE 308 SYNTAX RowStatus 309 MAX-ACCESS read-create 310 STATUS current 311 DESCRIPTION 312 DESCRIPTION 313 "The status of this conceptual row. 315 To create a row in this table, a manager must 316 set this object to either createAndGo(4) or 317 createAndWait(5). 319 Until instances of all corresponding columns 320 are appropriately configured, the value of the 321 corresponding instance of the 322 dccaPeerRowStatus column is 'notReady'. 324 In particular, a newly created row cannot be 325 made active until the corresponding dccaPeerId 326 has been set. 328 dccaPeerId may not be modified while the 329 value of this object is active(1): 330 An attempt to set these objects while the value 331 of dccaPeerRowStatus is active(1) will result 332 in an inconsistentValue error. 334 Entries in this table with dccaPeerRowStatus 335 equal to active(1) remain in the table until 336 destroyed. 338 Entries in this table with dccaPeerRowStatus 339 equal to values other than active(1) will be 340 destroyed after timeout (5 minutes). 342 If a dccaPeerId being created via SNMP already 343 exists in another active dccaPeerEntry, then a 344 newly created row 345 cannot be made active until the original row 346 with the dccaPeerId value is destroyed. 348 Upon reload, dccaPeerIndex values may be 349 changed." 350 ::= { dccaPeerEntry 5 } 352 dccaPeerVendorTable OBJECT-TYPE 353 SYNTAX SEQUENCE OF DccaPeerVendorEntry 354 MAX-ACCESS not-accessible 355 STATUS current 356 DESCRIPTION 357 "The table listing the Vendor IDs 358 supported by the peer." 359 ::= { dccaPeerCfgs 2 } 361 dccaPeerVendorEntry OBJECT-TYPE 362 SYNTAX DccaPeerVendorEntry 363 MAX-ACCESS not-accessible 364 STATUS current 365 DESCRIPTION 366 "A row entry representing a 367 Vendor ID supported by the peer." 368 INDEX { 369 dccaPeerIndex, 370 dccaPeerVendorIndex 371 } 372 ::= { dccaPeerVendorTable 1 } 374 DccaPeerVendorEntry ::= SEQUENCE { 375 dccaPeerVendorIndex Unsigned32, 376 dccaPeerVendorId Unsigned32, 377 dccaPeerVendorStorageType StorageType, 378 dccaPeerVendorRowStatus RowStatus 379 } 381 dccaPeerVendorIndex OBJECT-TYPE 382 SYNTAX Unsigned32 (1..4294967295 ) 383 MAX-ACCESS not-accessible 384 STATUS current 385 DESCRIPTION 386 "A number uniquely identifying the Vendor 387 ID supported by the peer." 388 ::= { dccaPeerVendorEntry 1 } 390 dccaPeerVendorId OBJECT-TYPE 391 SYNTAX Unsigned32 392 MAX-ACCESS read-create 393 STATUS current 394 DESCRIPTION 395 "The active Vendor IDs used for peer 396 connections." 397 ::= { dccaPeerVendorEntry 2 } 399 dccaPeerVendorStorageType OBJECT-TYPE 400 SYNTAX StorageType 401 MAX-ACCESS read-create 402 STATUS current 403 DESCRIPTION 404 "The storage type for this conceptual row. An 405 agent implementing the table must allow adding 406 dccaPeerVendorId into the table. None of the 407 columnar objects is writable 408 when the conceptual row is permanent." 409 REFERENCE 410 "Textual Conventions for SMIv2, Section 2." 411 DEFVAL { nonVolatile } 412 ::= { dccaPeerVendorEntry 3 } 414 dccaPeerVendorRowStatus OBJECT-TYPE 415 SYNTAX RowStatus 416 MAX-ACCESS read-create 417 STATUS current 418 DESCRIPTION 419 "The status of this conceptual row. 421 To create a row in this table, a manager must 422 set this object to either createAndGo(4) or 423 createAndWait(5). 425 Until instances of all corresponding columns 426 are appropriately configured, the value of the 427 corresponding instance of the 428 dccaPeerVendorRowStatus column is 'notReady'. 430 In particular, a newly created row cannot be 431 made active until the corresponding 432 dccaPeerVendorId has been set. 434 dccaPeerVendorId may not be modified while the 435 value of this object is active(1): 436 An attempt to set these objects while the 437 value of dccaPeerVendorRowStatus is active(1) 438 will result in an inconsistentValue error. 440 Entries in this table with 441 dccaPeerVendorRowStatus equal to 442 active(1) remain in the table until destroyed. 444 Entries in this table with 445 dccaPeerVendorRowStatus equal to 446 values other than active(1) will be destroyed 447 after timeout (5 minutes). 449 If the peer vendor id being created via SNMP 450 already exists 451 in another active dccaPeerVendorEntry, 452 then a newly 453 created row cannot be made active until the 454 original row with the peer vendor id value is 455 destroyed. 457 Upon reload, dccaPeerVendorIndex values may be 458 changed." 459 ::= { dccaPeerVendorEntry 4 } 461 -- per-peer statistics 463 dccaPerPeerStatsTable OBJECT-TYPE 464 SYNTAX SEQUENCE OF dccaPerPeerStatsEntry 465 MAX-ACCESS not-accessible 466 STATUS current 467 DESCRIPTION 468 "The table listing the Diameter 469 Credit Control per-peer Statistics." 470 ::= { dccaPeerStats 1 } 472 dccaPerPeerStatsEntry OBJECT-TYPE 473 SYNTAX dccaPerPeerStatsEntry 474 MAX-ACCESS not-accessible 475 STATUS current 476 DESCRIPTION 477 "A row entry representing a Diameter 478 Credit Control Peer." 479 INDEX { dccaPeerIndex } 480 ::= { dccaPerPeerStatsTable 1 } 482 dccaPerPeerStatsEntry ::= SEQUENCE { 483 dccaPerPeerStatsCCRIn Counter32, 484 dccaPerPeerStatsCCROut Counter32, 485 dccaPerPeerStatsCCRDropped Counter32, 486 dccaPerPeerStatsCCAIn Counter32, 487 dccaPerPeerStatsCCAOut Counter32, 488 dccaPerPeerStatsCCADropped Counter32, 489 dccaPerPeerStatsRARIn Counter32, 490 dccaPerPeerStatsRARDropped Counter32, 491 dccaPerPeerStatsRAAOut Counter32, 492 dccaPerPeerStatsRAADropped Counter32, 493 dccaPerPeerStatsSTROut Counter32, 494 dccaPerPeerStatsSTRDropped Counter32, 495 dccaPerPeerStatsSTAIn Counter32, 496 dccaPerPeerStatsSTADropped Counter32, 497 dccaPerPeerStatsAAROut Counter32, 498 dccaPerPeerStatsAARDropped Counter32, 499 dccaPerPeerStatsAAAIn Counter32, 500 dccaPerPeerStatsAAADropped Counter32, 501 dccaPerPeerStatsASRIn Counter32, 502 dccaPerPeerStatsASRDropped Counter32, 503 dccaPerPeerStatsASAOut Counter32, 504 dccaPerPeerStatsASADropped Counter32 } 506 dccaPerPeerStatsCCRIn OBJECT-TYPE 507 SYNTAX Counter32 508 MAX-ACCESS read-only 509 STATUS current 510 DESCRIPTION 511 "Number of Diameter Credit-Control-Request 512 (CCR) messages received, per peer." 513 ::= { dccaPerPeerStatsEntry 2 } 515 dccaPerPeerStatsCCROut OBJECT-TYPE 516 SYNTAX Counter32 517 MAX-ACCESS read-only 518 STATUS current 519 DESCRIPTION 520 "Number of Diameter Credit-Control-Request (CCR) 521 messages sent, per peer." 522 ::= { dccaPerPeerStatsEntry 3 } 524 dccaPerPeerStatsCCRDropped OBJECT-TYPE 525 SYNTAX Counter32 526 MAX-ACCESS read-only 527 STATUS current 528 DESCRIPTION 529 "Number of Diameter Credit-Control-Request (CCR) 530 messages dropped, per peer." 531 ::= { dccaPerPeerStatsEntry 4 } 533 dccaPerPeerStatsCCAIn OBJECT-TYPE 534 SYNTAX Counter32 535 MAX-ACCESS read-only 536 STATUS current 537 DESCRIPTION 538 "Number of Diameter Credit-Control-Answer (CCA) 539 messages received, per peer." 540 ::= { dccaPerPeerStatsEntry 5 } 542 dccaPerPeerStatsCCAOut OBJECT-TYPE 543 SYNTAX Counter32 544 MAX-ACCESS read-only 545 STATUS current 546 DESCRIPTION 547 "Number of Diameter Credit-Control-Answer (CCA) 548 messages sent, per peer." 549 ::= { dccaPerPeerStatsEntry 6 } 551 dccaPerPeerStatsCCADropped OBJECT-TYPE 552 SYNTAX Counter32 553 MAX-ACCESS read-only 554 STATUS current 555 DESCRIPTION 556 "Number of Diameter Credit-Control-Answer (CCA) 557 messages dropped, per peer." 558 ::= { dccaPerPeerStatsEntry 7 } 560 dccaPerPeerStatsRARIn OBJECT-TYPE 561 SYNTAX Counter32 562 MAX-ACCESS read-only 563 STATUS current 564 DESCRIPTION 565 "Number of Diameter Re-Auth-Request (RAR) 566 messages received, per peer." 567 ::= { dccaPerPeerStatsEntry 8 } 569 dccaPerPeerStatsRARDropped OBJECT-TYPE 570 SYNTAX Counter32 571 MAX-ACCESS read-only 572 STATUS current 573 DESCRIPTION 574 "Number of Diameter Re-Auth-Request (RAR) 575 messages dropped, per peer." 576 ::= { dccaPerPeerStatsEntry 9 } 578 dccaPerPeerStatsRAAOut OBJECT-TYPE 579 SYNTAX Counter32 580 MAX-ACCESS read-only 581 STATUS current 582 DESCRIPTION 583 "Number of Diameter Re-Auth-Answer (RAA) 584 messages transmitted, per peer." 585 ::= { dccaPerPeerStatsEntry 10 } 587 dccaPerPeerStatsRAADropped OBJECT-TYPE 588 SYNTAX Counter32 589 MAX-ACCESS read-only 590 STATUS current 591 DESCRIPTION 592 "Number of Diameter Re-Auth-Answer (RAA) 593 messages dropped, per peer." 594 ::= { dccaPerPeerStatsEntry 11 } 596 dccaPerPeerStatsSTROut OBJECT-TYPE 597 SYNTAX Counter32 598 MAX-ACCESS read-only 599 STATUS current 600 DESCRIPTION 601 "Number of Diameter 602 Session-Termination-Request (STR) 603 messages transmitted, per peer." 604 ::= { dccaPerPeerStatsEntry 12 } 606 dccaPerPeerStatsSTRDropped OBJECT-TYPE 607 SYNTAX Counter32 608 MAX-ACCESS read-only 609 STATUS current 610 DESCRIPTION 611 "Number of Diameter 612 Session-Termination-Request (STR) 613 messages dropped, per peer." 614 ::= { dccaPerPeerStatsEntry 13 } 616 dccaPerPeerStatsSTAIn OBJECT-TYPE 617 SYNTAX Counter32 618 MAX-ACCESS read-only 619 STATUS current 620 DESCRIPTION 621 "Number of Diameter 622 Session-Termination-Answer (STA) 623 messages received, per peer." 624 ::= { dccaPerPeerStatsEntry 14 } 626 dccaPerPeerStatsSTADropped OBJECT-TYPE 627 SYNTAX Counter32 628 MAX-ACCESS read-only 629 STATUS current 630 DESCRIPTION 631 "Number of Diameter 632 Session-Termination-Answer (STA) 633 messages dropped, per peer." 634 ::= { dccaPerPeerStatsEntry 15 } 636 dccaPerPeerStatsAAROut OBJECT-TYPE 637 SYNTAX Counter32 638 MAX-ACCESS read-only 639 STATUS current 640 DESCRIPTION 641 "Number of Diameter AA-Request (AAR) 642 messages transmitted, per peer." 643 ::= { dccaPerPeerStatsEntry 16 } 645 dccaPerPeerStatsAARDropped OBJECT-TYPE 646 SYNTAX Counter32 647 MAX-ACCESS read-only 648 STATUS current 649 DESCRIPTION 650 "Number of Diameter AA-Request (AAR) 651 messages dropped, per peer." 652 ::= { dccaPerPeerStatsEntry 17 } 654 dccaPerPeerStatsAAAIn OBJECT-TYPE 655 SYNTAX Counter32 656 MAX-ACCESS read-only 657 STATUS current 658 DESCRIPTION 659 "Number of Diameter AA-Answer (AAA) 660 messages received, per peer." 661 ::= { dccaPerPeerStatsEntry 18 } 663 dccaPerPeerStatsAAADropped OBJECT-TYPE 664 SYNTAX Counter32 665 MAX-ACCESS read-only 666 STATUS current 667 DESCRIPTION 668 "Number of Diameter AA-Answer (AAA) 669 messages dropped, per peer." 670 ::= { dccaPerPeerStatsEntry 19 } 672 dccaPerPeerStatsASRIn OBJECT-TYPE 673 SYNTAX Counter32 674 MAX-ACCESS read-only 675 STATUS current 676 DESCRIPTION 677 "Number of Diameter Abort-Session-Request 678 (ASR) messages received, per peer." 679 ::= { dccaPerPeerStatsEntry 20 } 681 dccaPerPeerStatsASRDropped OBJECT-TYPE 682 SYNTAX Counter32 683 MAX-ACCESS read-only 684 STATUS current 685 DESCRIPTION 686 "Number of Diameter Abort-Session-Request 687 (ASR) messages dropped, per peer." 688 ::= { dccaPerPeerStatsEntry 21 } 690 dccaPerPeerStatsASAOut OBJECT-TYPE 691 SYNTAX Counter32 692 MAX-ACCESS read-only 693 STATUS current 694 DESCRIPTION 695 "Number of Diameter Abort-Session-Answer 696 (ASA) messages transmitted, per peer." 697 ::= { dccaPerPeerStatsEntry 22 } 699 dccaPerPeerStatsASADropped OBJECT-TYPE 700 SYNTAX Counter32 701 MAX-ACCESS read-only 702 STATUS current 703 DESCRIPTION 704 "Number of Diameter Abort-Session-Answer 705 (ASA) messages dropped, per peer." 706 ::= { dccaPerPeerStatsEntry 23 } 708 -- -- Conformance -- dccaMIBCompliances 710 dccaMIBCompliances 711 OBJECT IDENTIFIER ::= { diameterCcAppConform 1 } dccaMIBGroups 712 OBJECT IDENTIFIER ::= { diameterCcAppConform 2 } 714 -- -- Compliance Statements -- 716 dccaMIBCompliance MODULE-COMPLIANCE 717 STATUS current 718 DESCRIPTION 719 "The compliance statement for Diameter Credit 720 Control application entities." 721 MODULE -- this module 722 MANDATORY-GROUPS { dccaPeerStatsGroup } 724 GROUP 725 dccaHostCfgGroup 726 DESCRIPTION 727 "This group is only mandatory for a system that 728 supports Local DCCA Host configuration." 730 GROUP 731 dccaPeerCfgGroup 732 DESCRIPTION 733 "This group is only mandatory for a system that 734 supports DCCA Peer configuration." 736 ::= { dccaMIBCompliances 1 } 738 -- -- Units of Conformance -- 739 dccaHostCfgGroup OBJECT-GROUP 740 OBJECTS { 741 dccaHostAddressType, 742 dccaHostAddress, 743 dccaHostId 744 } 745 STATUS current 746 DESCRIPTION 747 "A collection of objects providing 748 configuration common to the server." 749 ::= { dccaMIBGroups 1 } 751 dccaPeerCfgGroup OBJECT-GROUP 752 OBJECTS { 753 dccaPeerId, 754 dccaPeerVendorId, 755 dccaPeerStorageType, 756 dccaPeerVendorStorageType, 757 dccaPeerFirmwareRevision, 758 dccaPeerRowStatus, 759 dccaPeerVendorRowStatus 760 } 761 STATUS current 762 DESCRIPTION 763 "A collection of objects providing peer 764 configuration common to the server." 765 ::= { dccaMIBGroups 2 } 767 dccaPeerStatsGroup OBJECT-GROUP 768 OBJECTS { 769 dccaPeerStatsCCRIn, 770 dccaPeerStatsCCROut, 771 dccaPeerStatsCCRDropped, 772 dccaPeerStatsCCAIn, 773 dccaPeerStatsCCAOut, 774 dccaPeerStatsCCADropped, 775 dccaPeerStatsRARIn, 776 dccaPeerStatsRARDropped, 777 dccaPeerStatsRAAOut, 778 dccaPeerStatsRAADropped, 779 dccaPeerStatsSTROut, 780 dccaPeerStatsSTRDropped, 781 dccaPeerStatsSTAIn, 782 dccaPeerStatsSTADropped, 783 dccaPeerStatsAAROut, 784 dccaPeerStatsAARDropped, 785 dccaPeerStatsAAAIn, 786 dccaPeerStatsAAADropped, 787 dccaPeerStatsASRIn, 788 dccaPeerStatsASRDropped, 789 dccaPeerStatsASAOut, 790 dccaPeerStatsASADropped 791 } 792 STATUS current 793 DESCRIPTION 794 "A collection of objects providing peer 795 statistics common to the server." 796 ::= { dccaMIBGroups 3 } 798 END 800 5. IANA Considerations 802 IANA is requested to assign an OID under mib-2. 804 6. Security Considerations 806 SNMPv1 by itself is not a secure environment. Even if the network 807 itself is secure (for example by using IPSec), there is no control as 808 to who on the secure network is allowed to access and GET (read) the 809 objects in this MIB. 811 It is recommended that the implementers consider the security 812 features as provided by the SNMPv3 framework. Specifically, the use 813 of the User-based Security Model [RFC3414] and the View-based Access 814 Control Model [RFC3415] is recommended. 816 It is then a customer/user responsibility to ensure that the SNMP 817 entity giving access to an instance of this MIB, is properly 818 configured to give access to the objects only to those principals 819 (users) that have legitimate rights to indeed GET or SET (change/ 820 create/delete) them. 822 7. Acknowledgements 824 Thanks to Sumanth Mithra and Biswaranjan Panda for helpful 825 suggestions and feedback. 827 8. References 828 8.1. Normative References 830 [BASEMIB] Zorn, G. and S. Comerica, "Diameter Base Protocol MIB", 831 draft-zorn-dime-diameter-base-protocol-mib-03.txt (work in 832 progress), February 2007. 834 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 835 Requirement Levels", BCP 14, RFC 2119, March 1997. 837 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 838 Schoenwaelder, Ed., "Structure of Management Information 839 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 841 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 842 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 843 STD 58, RFC 2579, April 1999. 845 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 846 "Conformance Statements for SMIv2", STD 58, RFC 2580, 847 April 1999. 849 [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. 850 Arkko, "Diameter Base Protocol", RFC 3588, September 2003. 852 [RFC4004] Calhoun, P., Johansson, T., Perkins, C., Hiller, T., and 853 P. McCann, "Diameter Mobile IPv4 Application", RFC 4004, 854 August 2005. 856 8.2. Informative References 858 [RFC3141] Hiller, T., Walsh, P., Chen, X., Munson, M., Dommety, G., 859 Sivalingham, S., Lim, B., McCann, P., Shiino, H., 860 Hirschman, B., Manning, S., Hsu, R., Koo, H., Lipford, M., 861 Calhoun, P., Lo, C., Jaques, E., Campbell, E., Y.Xu, 862 S.Baba, T.Ayaki, T.Seki, and A.Hameed, "CDMA2000 Wireless 863 Data Requirements for AAA", RFC 3141, June 2001. 865 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 866 "Introduction and Applicability Statements for Internet- 867 Standard Management Framework", RFC 3410, December 2002. 869 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model 870 (USM) for version 3 of the Simple Network Management 871 Protocol (SNMPv3)", STD 62, RFC 3414, December 2002. 873 [RFC3415] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 874 Access Control Model (VACM) for the Simple Network 875 Management Protocol (SNMP)", STD 62, RFC 3415, 876 December 2002. 878 [RFC4005] Calhoun, P., Zorn, G., Spence, D., and D. Mitton, 879 "Diameter Network Access Server Application", RFC 4005, 880 August 2005. 882 [RFC4006] Hakala, H., Mattila, L., Koskinen, J-P., Stura, M., and J. 883 Loughney, "Diameter Credit-Control Application", RFC 4006, 884 August 2005. 886 [RFC4072] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible 887 Authentication Protocol (EAP) Application", RFC 4072, 888 August 2005. 890 Authors' Addresses 892 Glen Zorn 893 Network Zen 894 1310 East Thomas Street 895 #306 896 Seattle, Washington 98102 897 USA 899 Phone: +1 (206) 377-9035 900 Email: gwz@net-zen.net 902 Subash Comerica 903 Cisco Systems 904 Global Development Centre, Prestige Waterford 905 No. 9 Brunton Road 906 BGL3/MZ/ 907 Bangalore, Karnataka 560025 908 India 910 Phone: +91 80 4103 6427 911 Email: subashtc@cisco.com