draft-ietf-dime-diameter-cc-appl-mib-01.txt   draft-ietf-dime-diameter-cc-appl-mib-02.txt 
Network Working Group G. Zorn, Ed. Network Working Group G. Zorn, Ed.
Internet-Draft Network Zen Internet-Draft Network Zen
Intended status: Standards Track S. Comerica Intended status: Standards Track S. Comerica
Expires: January 2, 2010 Cisco Systems Expires: June 7, 2010 Cisco Systems
July 1, 2009 December 4, 2009
Diameter Credit Control Application MIB Diameter Credit Control Application MIB
draft-ietf-dime-diameter-cc-appl-mib-01.txt draft-ietf-dime-diameter-cc-appl-mib-02.txt
Abstract
Along with providing support for certain basic authentication,
authorization and accounting functions, the Diameter base protocol is
intended to provide a framework for AAA applications.
This document defines the Management Information Base (MIB) module
which describes the minimum set of objects needed to manage an
implementation of the Diameter Credit Control application.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. This document may contain material provisions of BCP 78 and BCP 79.
from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from
the person(s) controlling the copyright in such materials, this
document may not be modified outside the IETF Standards Process, and
derivative works of it may not be created outside the IETF Standards
Process, except to format it for publication as an RFC or to
translate it into languages other than English.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 2, 2010. This Internet-Draft will expire on June 7, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Abstract include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
Along with providing support for certain basic authentication, described in the BSD License.
authorization and accounting functions, the Diameter base protocol is
intended to provide a framework for AAA applications.
This document defines the Management Information Base (MIB) module This document may contain material from IETF Documents or IETF
which describes the minimum set of objects needed to manage an Contributions published or made publicly available before November
implementation of the Diameter Credit Control Application. 10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents Table of Contents
1. The Internet-Standard Management Framework . . . . . . . . . . 3 1. The Internet-Standard Management Framework . . . . . . . . . . 3
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Diameter Credit Control Application MIB Definitions . . . . . 3 4. Diameter Credit Control Application MIB Definitions . . . . . 3
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
6. Security Considerations . . . . . . . . . . . . . . . . . . . 18 6. Security Considerations . . . . . . . . . . . . . . . . . . . 18
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.1. Normative References . . . . . . . . . . . . . . . . . . . 18 8.1. Normative References . . . . . . . . . . . . . . . . . . . 19
8.2. Informative References . . . . . . . . . . . . . . . . . . 19 8.2. Informative References . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20
1. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58 module that is compliant to the SMIv2, which is described in STD 58
([RFC2578], [RFC2579], [RFC2580]). In particular, it describes ([RFC2578], [RFC2579], [RFC2580]). In particular, it describes
managed objects used for managing the Diameter Credit Control managed objects used for managing the Diameter Credit Control
Application [RFC4006]. Application [RFC4006].
Discussion of this draft may be directed to the authors. Discussion of this draft may be directed to the dime Working Group of
the IETF (dime@ietf.org)..
2. Requirements Language 2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
3. Overview 3. Overview
The base Diameter protocol [RFC3588] is never used alone; it is The base Diameter protocol [RFC3588] is never used alone; it is
always extended for a particular application. always extended for a particular application.
This MIB defines objects supporting the management of the Diameter This MIB defines objects supporting the management of the Diameter
Credit Control Application protocol as described in RFC 4006 Credit Control Application protocol as described in [RFC4006]. The
[RFC4006]. The MIB specification for the Diameter base protocol MIB specification for the Diameter base protocol
[I-D.ietf-dime-diameter-base-protocol-mib] SHOULD be implemented [I-D.ietf-dime-diameter-base-protocol-mib] SHOULD be implemented
prior to the implementation of this MIB. prior to the implementation of this MIB.
4. Diameter Credit Control Application MIB Definitions 4. Diameter Credit Control Application MIB Definitions
DIAMETER-CC-APPLICATION-MIB DEFINITIONS ::= BEGIN DIAMETER-CC-APPLICATION-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
Unsigned32, Unsigned32,
Counter32 Counter32,
mib-2
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- [RFC2580]
StorageType, StorageType,
RowStatus RowStatus
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- [RFC2579]
InetAddressType, InetAddressType,
InetAddress InetAddress
FROM INET-ADDRESS-MIB -- [RFC4001] FROM INET-ADDRESS-MIB -- [RFC4001]
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB; -- [RFC3411] FROM SNMP-FRAMEWORK-MIB; -- [RFC3411]
diameterCCAMIB MODULE-IDENTITY diameterCCAMIB MODULE-IDENTITY
LAST-UPDATED "200903060000Z" -- 06 March 2009 LAST-UPDATED "200912040000Z" -- 04 December 2009
ORGANIZATION "IETF dime Working Group." ORGANIZATION "IETF dime Working Group."
CONTACT-INFO CONTACT-INFO
"Glen Zorn "Subash Comerica
Network Zen Cisco Systems
1310 East Thomas Street Global Development Centre, Prestige Waterford
Seattle, WA 98102 No. 9 Brunton Road
USA BGL3/MZ/
Phone: +1 (206) 377 9035 Bangalore, Karnataka 560025
Email: gwz@net-zen.net" India
Phone: +91 80 4103 6427
Email: subashtc@cisco.com"
DESCRIPTION DESCRIPTION
"The MIB module for entities implementing the "The MIB module for entities implementing the
Diameter Credit Control Application, RFC 4006. Diameter Credit Control Application, RFC 4006.
Copyright (C) The Internet Society (2009). This initial Copyright (C) The Internet Society (2009). This initial
version of this MIB module was published in RFC yyyy; version of this MIB module was published in RFC yyyy;
for full legal notices see the RFC itself. Supplementary for full legal notices see the RFC itself. Supplementary
information may be available on information may be available on
http://www.ietf.org/copyrights/ianamib.html." http://www.ietf.org/copyrights/ianamib.html."
-- RFC Ed.: replace yyyy with actual RFC number and remove this note -- RFC Ed.: replace yyyy with actual RFC number and remove this note
REVISION "200903060000Z" -- 06 March 2009 REVISION "200912040000Z" -- 04 December 2009
DESCRIPTION "Initial version as published in RFC yyyy" DESCRIPTION "Initial version as published in RFC yyyy"
-- RFC Ed.: replace yyyy with actual RFC number and remove this note -- RFC Ed.: replace yyyy with actual RFC number and remove this note
::= { mib-2 119 } -- Experimental value assigned by IANA. ::= { mib-2 119 } -- Experimental value assigned by IANA.
-- Top-Level Components of this MIB. -- Top-Level Components of this MIB.
diameterCcAppMIB OBJECT ::= diameterCcAppMIB OBJECT IDENTIFIER ::=
{ diameterMIB 2 } { diameterCCAMIB 2 }
diameterCcAppTraps OBJECT IDENTIFIER ::= diameterCcAppTraps OBJECT IDENTIFIER ::=
{ diameterCcAppMIB 0 } { diameterCcAppMIB 0 }
diameterCcAppObjects OBJECT IDENTIFIER ::= diameterCcAppObjects OBJECT IDENTIFIER ::=
{ diameterCcAppMIB 1 } { diameterCcAppMIB 1 }
diameterCcAppConform OBJECT IDENTIFIER ::= diameterCcAppConform OBJECT IDENTIFIER ::=
{ diameterCcAppMIB 2 } { diameterCcAppMIB 2 }
dccaHostCfgs OBJECT IDENTIFIER ::= { diameterCcAppObjects 1 } dccaHostCfgs OBJECT IDENTIFIER ::= { diameterCcAppObjects 1 }
dccaPeerCfgs OBJECT IDENTIFIER ::= { diameterCCAMIBObjects 2 } dccaPeerCfgs OBJECT IDENTIFIER ::= { diameterCcAppObjects 2 }
dccaPeerStats OBJECT IDENTIFIER ::= { diameterCcAppObjects 3 } dccaPeerStats OBJECT IDENTIFIER ::= { diameterCcAppObjects 3 }
dccaHostID OBJECT-TYPE dccaHostID OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The implementation identification string for "The implementation identification string for
the Diameter software in use on the system, the Diameter software in use on the system,
for example; 'diameterd'" for example; 'diameterd'"
skipping to change at page 6, line 24 skipping to change at page 7, line 31
dccaHostIpAddress OBJECT-TYPE dccaHostIpAddress OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP-Address of the host, which is of the "The IP-Address of the host, which is of the
type specified in dccaHostIpAddrType." type specified in dccaHostIpAddrType."
::= { dccaHostIpAddrEntry 3 } ::= { dccaHostIpAddrEntry 3 }
dccaPeerTable OBJECT-TYPE dccaPeerTable OBJECT-TYPE
SYNTAX SEQUENCE OF DcaPeerEntry SYNTAX SEQUENCE OF DccaPeerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table listing information regarding "The table listing information regarding
the discovered or configured Diameter the discovered or configured Diameter
Credit Control peers." Credit Control peers."
::= { dccaPeerCfgs 1 } ::= { dccaPeerCfgs 1 }
dccaPeerEntry OBJECT-TYPE dccaPeerEntry OBJECT-TYPE
SYNTAX DcaPeerEntry SYNTAX DccaPeerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row entry representing a discovered "A row entry representing a discovered
or configured Diameter Credit Control or configured Diameter Credit Control
peer." peer."
INDEX { dccaPeerIndex } INDEX { dccaPeerIndex }
::= { dccaPeerTable 1 } ::= { dccaPeerTable 1 }
DcaPeerEntry ::= SEQUENCE { DccaPeerEntry ::= SEQUENCE {
dccaPeerIndex Unsigned32, dccaPeerIndex Unsigned32,
dccaPeerId SnmpAdminString, dccaPeerId SnmpAdminString,
dccaPeerFirmwareRevision Unsigned32, dccaPeerFirmwareRevision Unsigned32,
dccaPeerStorageType StorageType, dccaPeerStorageType StorageType,
dccaPeerStatus RowStatus } dccaPeerRowStatus RowStatus }
dccaPeerIndex OBJECT-TYPE dccaPeerIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number uniquely identifying each Diameter "A number uniquely identifying each Diameter
Credit Control peer with which this host Credit Control peer with which this host
communicates." communicates."
::= { dccaPeerEntry 1 } ::= { dccaPeerEntry 1 }
skipping to change at page 7, line 45 skipping to change at page 9, line 5
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row. None "The storage type for this conceptual row. None
of the columnar objects is writable when the of the columnar objects is writable when the
conceptual row is permanent." conceptual row is permanent."
REFERENCE REFERENCE
"Textual Conventions for SMIv2, Section 2." "Textual Conventions for SMIv2, Section 2."
DEFVAL { nonVolatile } DEFVAL { nonVolatile }
::= { dccaPeerEntry 4 } ::= { dccaPeerEntry 4 }
dccaPeerStatus OBJECT-TYPE dccaPeerRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
DESCRIPTION
"The status of this conceptual row. "The status of this conceptual row.
To create a row in this table, a manager must To create a row in this table, a manager must
set this object to either createAndGo(4) or set this object to either createAndGo(4) or
createAndWait(5). createAndWait(5).
Until instances of all corresponding columns Until instances of all corresponding columns
are appropriately configured, the value of the are appropriately configured, the value of the
corresponding instance of the corresponding instance of the
dccaPeerRowStatus column is 'notReady'. dccaPeerRowStatus column is 'notReady'.
In particular, a newly created row cannot be In particular, a newly created row cannot be
skipping to change at page 11, line 4 skipping to change at page 12, line 10
If the peer vendor id being created via SNMP If the peer vendor id being created via SNMP
already exists already exists
in another active dccaPeerVendorEntry, in another active dccaPeerVendorEntry,
then a newly then a newly
created row cannot be made active until the created row cannot be made active until the
original row with the peer vendor id value is original row with the peer vendor id value is
destroyed. destroyed.
Upon reload, dccaPeerVendorIndex values may be Upon reload, dccaPeerVendorIndex values may be
changed." changed."
::= { dccaPeerVendorEntry 4 } ::= { dccaPeerVendorEntry 4 }
-- per-peer statistics -- per-peer statistics
dccaPerPeerStatsTable OBJECT-TYPE dccaPerPeerStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF dccaPerPeerStatsEntry SYNTAX SEQUENCE OF DccaPerPeerStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table listing the Diameter "The table listing the Diameter
Credit Control per-peer Statistics." Credit Control per-peer Statistics."
::= { dccaPeerStats 1 } ::= { dccaPeerStats 1 }
dccaPerPeerStatsEntry OBJECT-TYPE dccaPerPeerStatsEntry OBJECT-TYPE
SYNTAX dccaPerPeerStatsEntry SYNTAX DccaPerPeerStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row entry representing a Diameter "A row entry representing a Diameter
Credit Control Peer." Credit Control Peer."
INDEX { dccaPeerIndex } INDEX { dccaPeerIndex }
::= { dccaPerPeerStatsTable 1 } ::= { dccaPerPeerStatsTable 1 }
dccaPerPeerStatsEntry ::= SEQUENCE { DccaPerPeerStatsEntry ::= SEQUENCE {
dccaPerPeerStatsCCRIn Counter32, dccaPerPeerStatsCCRIn Counter32,
dccaPerPeerStatsCCROut Counter32, dccaPerPeerStatsCCROut Counter32,
dccaPerPeerStatsCCRDropped Counter32, dccaPerPeerStatsCCRDropped Counter32,
dccaPerPeerStatsCCAIn Counter32, dccaPerPeerStatsCCAIn Counter32,
dccaPerPeerStatsCCAOut Counter32, dccaPerPeerStatsCCAOut Counter32,
dccaPerPeerStatsCCADropped Counter32, dccaPerPeerStatsCCADropped Counter32,
dccaPerPeerStatsRARIn Counter32, dccaPerPeerStatsRARIn Counter32,
dccaPerPeerStatsRARDropped Counter32, dccaPerPeerStatsRARDropped Counter32,
dccaPerPeerStatsRAAOut Counter32, dccaPerPeerStatsRAAOut Counter32,
dccaPerPeerStatsRAADropped Counter32, dccaPerPeerStatsRAADropped Counter32,
skipping to change at page 16, line 14 skipping to change at page 17, line 19
dccaPerPeerStatsASADropped OBJECT-TYPE dccaPerPeerStatsASADropped OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of Diameter Abort-Session-Answer "Number of Diameter Abort-Session-Answer
(ASA) messages dropped, per peer." (ASA) messages dropped, per peer."
::= { dccaPerPeerStatsEntry 23 } ::= { dccaPerPeerStatsEntry 23 }
-- -- Conformance -- dccaMIBCompliances -- Conformance dccaMIBCompliances
dccaMIBCompliances dccaMIBCompliances
OBJECT IDENTIFIER ::= { diameterCcAppConform 1 } dccaMIBGroups OBJECT IDENTIFIER ::= { diameterCcAppConform 1 } dccaMIBGroups
OBJECT IDENTIFIER ::= { diameterCcAppConform 2 } OBJECT IDENTIFIER ::= { diameterCcAppConform 2 }
-- -- Compliance Statements -- -- Compliance Statements
dccaMIBCompliance MODULE-COMPLIANCE dccaMIBCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for Diameter Credit "The compliance statement for Diameter Credit
Control application entities." Control application entities."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { dccaPeerStatsGroup } MANDATORY-GROUPS { dccaPeerStatsGroup }
GROUP GROUP
skipping to change at page 16, line 44 skipping to change at page 17, line 49
supports Local DCCA Host configuration." supports Local DCCA Host configuration."
GROUP GROUP
dccaPeerCfgGroup dccaPeerCfgGroup
DESCRIPTION DESCRIPTION
"This group is only mandatory for a system that "This group is only mandatory for a system that
supports DCCA Peer configuration." supports DCCA Peer configuration."
::= { dccaMIBCompliances 1 } ::= { dccaMIBCompliances 1 }
-- -- Units of Conformance -- -- Units of Conformance
dccaHostCfgGroup OBJECT-GROUP dccaHostCfgGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dccaHostAddressType, dccaHostIpAddrType,
dccaHostAddress, dccaHostIpAddress,
dccaHostId dccaHostID
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing "A collection of objects providing
configuration common to the server." configuration common to the server."
::= { dccaMIBGroups 1 } ::= { dccaMIBGroups 1 }
dccaPeerCfgGroup OBJECT-GROUP dccaPeerCfgGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dccaPeerId, dccaPeerId,
skipping to change at page 17, line 28 skipping to change at page 18, line 34
dccaPeerVendorRowStatus dccaPeerVendorRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing peer "A collection of objects providing peer
configuration common to the server." configuration common to the server."
::= { dccaMIBGroups 2 } ::= { dccaMIBGroups 2 }
dccaPeerStatsGroup OBJECT-GROUP dccaPeerStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dccaPeerStatsCCRIn, dccaPerPeerStatsCCRIn,
dccaPeerStatsCCROut, dccaPerPeerStatsCCROut,
dccaPeerStatsCCRDropped, dccaPerPeerStatsCCRDropped,
dccaPeerStatsCCAIn, dccaPerPeerStatsCCAIn,
dccaPeerStatsCCAOut, dccaPerPeerStatsCCAOut,
dccaPeerStatsCCADropped, dccaPerPeerStatsCCADropped,
dccaPeerStatsRARIn, dccaPerPeerStatsRARIn,
dccaPeerStatsRARDropped, dccaPerPeerStatsRARDropped,
dccaPeerStatsRAAOut, dccaPerPeerStatsRAAOut,
dccaPeerStatsRAADropped, dccaPerPeerStatsRAADropped,
dccaPeerStatsSTROut, dccaPerPeerStatsSTROut,
dccaPeerStatsSTRDropped, dccaPerPeerStatsSTRDropped,
dccaPeerStatsSTAIn, dccaPerPeerStatsSTAIn,
dccaPeerStatsSTADropped, dccaPerPeerStatsSTADropped,
dccaPeerStatsAAROut, dccaPerPeerStatsAAROut,
dccaPeerStatsAARDropped, dccaPerPeerStatsAARDropped,
dccaPeerStatsAAAIn, dccaPerPeerStatsAAAIn,
dccaPeerStatsAAADropped, dccaPerPeerStatsAAADropped,
dccaPeerStatsASRIn, dccaPerPeerStatsASRIn,
dccaPeerStatsASRDropped, dccaPerPeerStatsASRDropped,
dccaPeerStatsASAOut, dccaPerPeerStatsASAOut,
dccaPeerStatsASADropped dccaPerPeerStatsASADropped
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing peer "A collection of objects providing peer
statistics common to the server." statistics common to the server."
::= { dccaMIBGroups 3 } ::= { dccaMIBGroups 3 }
END END
5. IANA Considerations 5. IANA Considerations
skipping to change at page 18, line 35 skipping to change at page 19, line 41
Control Model [RFC3415] is recommended. Control Model [RFC3415] is recommended.
It is then a customer/user responsibility to ensure that the SNMP It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly entity giving access to an instance of this MIB, is properly
configured to give access to the objects only to those principals configured to give access to the objects only to those principals
(users) that have legitimate rights to indeed GET or SET (change/ (users) that have legitimate rights to indeed GET or SET (change/
create/delete) them. create/delete) them.
7. Acknowledgements 7. Acknowledgements
Thanks to Sumanth Mithra, Tina Tsou, John Loughney and Biswaranjan Thanks to Sumanth Mithra and Biswaranjan Panda for helpful
Panda for helpful suggestions and feedback. suggestions and feedback.
8. References 8. References
8.1. Normative References 8.1. Normative References
[I-D.ietf-dime-diameter-base-protocol-mib]
Zorn, G. and S. Comerica, "Diameter Base Protocol MIB",
draft-ietf-dime-diameter-base-protocol-mib-00 (work in
progress), May 2009.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999. STD 58, RFC 2579, April 1999.
skipping to change at page 19, line 36 skipping to change at page 20, line 39
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005. Addresses", RFC 4001, February 2005.
[RFC4006] Hakala, H., Mattila, L., Koskinen, J-P., Stura, M., and J. [RFC4006] Hakala, H., Mattila, L., Koskinen, J-P., Stura, M., and J.
Loughney, "Diameter Credit-Control Application", RFC 4006, Loughney, "Diameter Credit-Control Application", RFC 4006,
August 2005. August 2005.
8.2. Informative References 8.2. Informative References
[I-D.ietf-dime-diameter-base-protocol-mib]
Zorn, G. and S. Comerica, "Diameter Base Protocol MIB",
draft-ietf-dime-diameter-base-protocol-mib-03 (work in
progress), November 2009.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management (USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", STD 62, RFC 3414, December 2002. Protocol (SNMPv3)", STD 62, RFC 3414, December 2002.
[RFC3415] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based [RFC3415] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", STD 62, RFC 3415, Management Protocol (SNMP)", STD 62, RFC 3415,
December 2002. December 2002.
Authors' Addresses Authors' Addresses
Glen Zorn (editor) Glen Zorn (editor)
Network Zen Network Zen
1310 East Thomas Street 1310 East Thomas Street
#306
Seattle, Washington 98102 Seattle, Washington 98102
USA +1 (206) 931-0768
Phone: +1 (206) 377-9035
Email: gwz@net-zen.net Email: gwz@net-zen.net
Subash Comerica Subash Comerica
Cisco Systems Cisco Systems
Global Development Centre, Prestige Waterford Global Development Centre, Prestige Waterford
No. 9 Brunton Road No. 9 Brunton Road
BGL3/MZ/ BGL3/MZ/
Bangalore, Karnataka 560025 Bangalore, Karnataka 560025
India India
 End of changes. 40 change blocks. 
99 lines changed or deleted 103 lines changed or added

This html diff was produced by rfcdiff 1.37b. The latest version is available from http://tools.ietf.org/tools/rfcdiff/