draft-ietf-dime-diameter-cc-appl-mib-02.txt   draft-ietf-dime-diameter-cc-appl-mib-03.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: June 7, 2010 Cisco Systems Expires: July 19, 2010 Cisco Systems
December 4, 2009 January 15, 2010
Diameter Credit Control Application MIB Diameter Credit Control Application MIB
draft-ietf-dime-diameter-cc-appl-mib-02.txt draft-ietf-dime-diameter-cc-appl-mib-03.txt
Abstract Abstract
Along with providing support for certain basic authentication, Along with providing support for certain basic authentication,
authorization and accounting functions, the Diameter base protocol is authorization and accounting functions, the Diameter base protocol is
intended to provide a framework for AAA applications. intended to provide a framework for AAA applications.
This document defines the Management Information Base (MIB) module This document defines the Management Information Base (MIB) module
which describes the minimum set of objects needed to manage an which describes the minimum set of objects needed to manage an
implementation of the Diameter Credit Control application. implementation of the Diameter Credit Control application.
skipping to change at page 1, line 43 skipping to change at page 1, line 43
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 June 7, 2010. This Internet-Draft will expire on July 19, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2010 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 Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 13 skipping to change at page 3, line 13
than English. 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 . . . . . . . . . . . . . . . . . . . . . . . 19
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.1. Normative References . . . . . . . . . . . . . . . . . . . 19 8.1. Normative References . . . . . . . . . . . . . . . . . . . 19
8.2. Informative References . . . . . . . . . . . . . . . . . . 19 8.2. Informative References . . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20 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
skipping to change at page 5, line 21 skipping to change at page 5, line 21
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 "200912040000Z" -- 04 December 2009 LAST-UPDATED "201001150000Z" -- 15 January 2010
ORGANIZATION "IETF dime Working Group." ORGANIZATION "IETF dime Working Group."
CONTACT-INFO CONTACT-INFO
"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
Phone: +91 80 4103 6427 Phone: +91 80 4103 6427
Email: subashtc@cisco.com" 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 (2010). 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 "200912040000Z" -- 04 December 2009 REVISION "201001150000Z" -- 15 January 2010
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 XXX }
-- RFC Ed.: replace XXX with value assigned by IANA
-- and remove this note
-- Top-Level Components of this MIB. -- Top-Level Components of this MIB.
diameterCcAppMIB OBJECT IDENTIFIER ::= diameterCcAppMIB OBJECT IDENTIFIER ::=
{ diameterCCAMIB 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 ::= { diameterCcAppObjects 2 } dccaPeerCfgs OBJECT IDENTIFIER ::= { diameterCcAppObjects 2 }
dccaPeerStats OBJECT IDENTIFIER ::= { diameterCcAppObjects 3 } dccaPeerStats OBJECT IDENTIFIER ::= { diameterCcAppObjects 3 }
skipping to change at page 19, line 19 skipping to change at page 19, line 26
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
IANA is requested to assign an OID under mib-2. The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value
-------------- -----------------------
diameterCCAMIB { mib-2 XXX }
Editor's Note (to be removed prior to publication) The IANA is
requested to assign a value for "XXX" under the 'mib-2' subtree
and to record the assignment in the SMI Numbers registry. When
the assignment has been made, the RFC Editor is asked to replace
"XXX" (here and in the MIB module) with the assigned value and to
remove this note.
6. Security Considerations 6. Security Considerations
SNMPv1 by itself is not a secure environment. Even if the network SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSec), there is no control as itself is secure (for example by using IPSec), there is no control as
to who on the secure network is allowed to access and GET (read) the to who on the secure network is allowed to access and GET (read) the
objects in this MIB. objects in this MIB.
It is recommended that the implementers consider the security It is recommended that the implementers consider the security
features as provided by the SNMPv3 framework. Specifically, the use features as provided by the SNMPv3 framework. Specifically, the use
skipping to change at page 20, line 41 skipping to change at page 21, line 10
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] [I-D.ietf-dime-diameter-base-protocol-mib]
Zorn, G. and S. Comerica, "Diameter Base Protocol MIB", Zorn, G. and S. Comerica, "Diameter Base Protocol MIB",
draft-ietf-dime-diameter-base-protocol-mib-03 (work in draft-ietf-dime-diameter-base-protocol-mib-04 (work in
progress), November 2009. 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 1463 East Republican Street, #358
Seattle, Washington 98102 Seattle, Washington 98112
+1 (206) 931-0768 USA
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. 16 change blocks. 
17 lines changed or deleted 34 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/