draft-ietf-dime-diameter-cc-appl-mib-00.txt   draft-ietf-dime-diameter-cc-appl-mib-01.txt 
Network Working Group G. Zorn 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: November 20, 2009 Cisco Systems Expires: January 2, 2010 Cisco Systems
May 19, 2009 July 1, 2009
Diameter Credit Control Application MIB Diameter Credit Control Application MIB
draft-ietf-dime-diameter-cc-appl-mib-00.txt draft-ietf-dime-diameter-cc-appl-mib-01.txt
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 not be modified, provisions of BCP 78 and BCP 79. This document may contain material
and derivative works of it may not be created, except to format it from IETF Documents or IETF Contributions published or made publicly
for publication as an RFC or to translate it into languages other available before November 10, 2008. The person(s) controlling the
than English. 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 November 20, 2009. This Internet-Draft will expire on January 2, 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 in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. and restrictions with respect to this document.
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.
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 . . . . . . . . . . . . . . . . . . . . . . . . . . 19 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18
8.1. Normative References . . . . . . . . . . . . . . . . . . . 19 8.1. Normative References . . . . . . . . . . . . . . . . . . . 18
8.2. Informative References . . . . . . . . . . . . . . . . . . 19 8.2. Informative References . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19
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
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 ([RFC2578], [RFC2579], [RFC2580]). In particular, it describes
[RFC2580]. In particular, it describes managed objects used for managed objects used for managing the Diameter Credit Control
managing the Diameter base protocol. Application [RFC4006].
Discussion of this draft may be directed to the authors. Discussion of this draft may be directed to the authors.
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 [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. Four standard Diameter always extended for a particular application.
applications have been defined to date: NASREQ [RFC4005], Mobile IP
[RFC4004] [RFC3141], Credit Control [RFC4006] and EAP [RFC4072];
others may be defined in the future.
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 [RFC4006]. The Credit Control Application protocol as described in RFC 4006
MIB specification for the Diameter base protocol [BASEMIB] SHOULD be [RFC4006]. The MIB specification for the Diameter base protocol
implemented prior to the implementation of this MIB. [I-D.ietf-dime-diameter-base-protocol-mib] SHOULD be implemented
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
skipping to change at page 18, line 41 skipping to change at page 18, line 35
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 and Biswaranjan Panda for helpful Thanks to Sumanth Mithra, Tina Tsou, John Loughney and Biswaranjan
suggestions and feedback. Panda for helpful suggestions and feedback.
8. References 8. References
8.1. Normative References 8.1. Normative References
[BASEMIB] Zorn, G. and S. Comerica, "Diameter Base Protocol MIB", [I-D.ietf-dime-diameter-base-protocol-mib]
draft-zorn-dime-diameter-base-protocol-mib-03.txt (work in Zorn, G. and S. Comerica, "Diameter Base Protocol MIB",
progress), February 2007. 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.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing Simple Network Management
Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
December 2002.
[RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.
Arkko, "Diameter Base Protocol", RFC 3588, September 2003. Arkko, "Diameter Base Protocol", RFC 3588, September 2003.
[RFC4004] Calhoun, P., Johansson, T., Perkins, C., Hiller, T., and [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
P. McCann, "Diameter Mobile IPv4 Application", RFC 4004, Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005.
[RFC4006] Hakala, H., Mattila, L., Koskinen, J-P., Stura, M., and J.
Loughney, "Diameter Credit-Control Application", RFC 4006,
August 2005. August 2005.
8.2. Informative References 8.2. Informative References
[RFC3141] Hiller, T., Walsh, P., Chen, X., Munson, M., Dommety, G.,
Sivalingham, S., Lim, B., McCann, P., Shiino, H.,
Hirschman, B., Manning, S., Hsu, R., Koo, H., Lipford, M.,
Calhoun, P., Lo, C., Jaques, E., Campbell, E., Y.Xu,
S.Baba, T.Ayaki, T.Seki, and A.Hameed, "CDMA2000 Wireless
Data Requirements for AAA", RFC 3141, June 2001.
[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.
[RFC4005] Calhoun, P., Zorn, G., Spence, D., and D. Mitton,
"Diameter Network Access Server Application", RFC 4005,
August 2005.
[RFC4006] Hakala, H., Mattila, L., Koskinen, J-P., Stura, M., and J.
Loughney, "Diameter Credit-Control Application", RFC 4006,
August 2005.
[RFC4072] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible
Authentication Protocol (EAP) Application", RFC 4072,
August 2005.
Authors' Addresses Authors' Addresses
Glen Zorn Glen Zorn (editor)
Network Zen Network Zen
1310 East Thomas Street 1310 East Thomas Street
#306 #306
Seattle, Washington 98102 Seattle, Washington 98102
USA USA
Phone: +1 (206) 377-9035 Phone: +1 (206) 377-9035
Email: gwz@net-zen.net Email: gwz@net-zen.net
Subash Comerica Subash Comerica
 End of changes. 19 change blocks. 
52 lines changed or deleted 48 lines changed or added

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