draft-ietf-dime-diameter-base-protocol-mib-03.txt   draft-ietf-dime-diameter-base-protocol-mib-04.txt 
Network Working Group G. Zorn Network Working Group G. Zorn
Internet-Draft Network Zen Internet-Draft Network Zen
Intended status: Standards Track S. Comerica Intended status: Standards Track S. Comerica
Expires: May 13, 2010 Cisco Systems Expires: July 19, 2010 Cisco Systems
November 9, 2009 January 15, 2010
Diameter Base Protocol MIB Diameter Base Protocol MIB
draft-ietf-dime-diameter-base-protocol-mib-03.txt draft-ietf-dime-diameter-base-protocol-mib-04.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 protocol is authorization and accounting functions, the Diameter protocol is
designed to provide a framework for AAA applications. designed 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 protocol. implementation of the Diameter protocol.
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 May 13, 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 15 skipping to change at page 3, line 15
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 Base Protocol MIB Definitions . . . . . . . . . . . . 3 4. Diameter Base Protocol MIB Definitions . . . . . . . . . . . . 3
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 47 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 47
6. Security Considerations . . . . . . . . . . . . . . . . . . . 47 6. Security Considerations . . . . . . . . . . . . . . . . . . . 47
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 48 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 48
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 48 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 48
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 48 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 49
9.1. Normative References . . . . . . . . . . . . . . . . . . . 48 9.1. Normative References . . . . . . . . . . . . . . . . . . . 49
9.2. Informative References . . . . . . . . . . . . . . . . . . 49 9.2. Informative References . . . . . . . . . . . . . . . . . . 49
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 49 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 50
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).
skipping to change at page 5, line 17 skipping to change at page 5, line 17
NOTIFICATION-GROUP, NOTIFICATION-GROUP,
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- [RFC2580]
RowStatus, RowStatus,
TruthValue, TruthValue,
StorageType StorageType
FROM SNMPv2-TC; -- [RFC2579] FROM SNMPv2-TC; -- [RFC2579]
diameterBaseProtocolMIB MODULE-IDENTITY diameterBaseProtocolMIB MODULE-IDENTITY
LAST-UPDATED "200802100000Z" -- 10 February 2008 LAST-UPDATED "201001150000Z" -- 15 January 2010
ORGANIZATION "IETF dime Working Group." ORGANIZATION "IETF dime Working Group."
CONTACT-INFO CONTACT-INFO
"Glen Zorn "Glen Zorn
Network Zen Network Zen
1310 East Thomas Street 1463 East Republican Street, #358
Seattle, WA 98102 Seattle, WA 98112
USA USA
Email: gwz@net-zen.net" Email: gwz@net-zen.net"
DESCRIPTION DESCRIPTION
"The MIB module for entities implementing the "The MIB module for entities implementing the
Diameter Base Protocol. Diameter Base Protocol.
Copyright (C) The IETF Trust (2008). This initial Copyright (C) The IETF Trust (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 "200802100000Z" -- 10 February 2008 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.
diameterBaseNotifications OBJECT IDENTIFIER ::= diameterBaseNotifications OBJECT IDENTIFIER ::=
{ diameterBaseProtocolMIB 0 } { diameterBaseProtocolMIB 0 }
diameterBaseObjects OBJECT IDENTIFIER ::= diameterBaseObjects OBJECT IDENTIFIER ::=
{ diameterBaseProtocolMIB 1 } { diameterBaseProtocolMIB 1 }
diameterBaseConform OBJECT IDENTIFIER ::= diameterBaseConform OBJECT IDENTIFIER ::=
{ diameterBaseProtocolMIB 2 } { diameterBaseProtocolMIB 2 }
dbpLocalCfgs OBJECT IDENTIFIER ::= { diameterBaseObjects 1 } dbpLocalCfgs OBJECT IDENTIFIER ::= { diameterBaseObjects 1 }
dbpLocalStats OBJECT IDENTIFIER ::= { diameterBaseObjects 2 } dbpLocalStats OBJECT IDENTIFIER ::= { diameterBaseObjects 2 }
dbpPeerCfgs OBJECT IDENTIFIER ::= { diameterBaseObjects 3 } dbpPeerCfgs OBJECT IDENTIFIER ::= { diameterBaseObjects 3 }
dbpPeerStats OBJECT IDENTIFIER ::= { diameterBaseObjects 4 } dbpPeerStats OBJECT IDENTIFIER ::= { diameterBaseObjects 4 }
dbpRealmCfgs OBJECT IDENTIFIER ::= { diameterBaseObjects 5 } dbpRealmCfgs OBJECT IDENTIFIER ::= { diameterBaseObjects 5 }
dbpRealmStats OBJECT IDENTIFIER ::= { diameterBaseObjects 6 } dbpRealmStats OBJECT IDENTIFIER ::= { diameterBaseObjects 6 }
skipping to change at page 48, line 24 skipping to change at page 48, line 28
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing statistics "A collection of objects providing statistics
of realm message routing." of realm message routing."
::= { diameterBaseProtocolMIBGroups 7 } ::= { diameterBaseProtocolMIBGroups 7 }
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
----------------------- -----------------------
diameterBaseProtocolMIB { 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
There are managed objects defined in this MIB that have a MAX-ACCESS There are managed objects defined in this MIB that have a MAX-ACCESS
clause of read-write and/or read-create. Such objects may be clause of read-write and/or read-create. Such objects may be
considered sensitive or vulnerable in some network environments. The considered sensitive or vulnerable in some network environments. The
support for SET operations in a non-secure environment without proper support for SET operations in a non-secure environment without proper
protection can have a negative effect on network operations. protection can have a negative effect on network operations.
There are several of managed objects in this MIB that may contain There are several of managed objects in this MIB that may contain
skipping to change at page 50, line 40 skipping to change at page 51, line 9
[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 Glen Zorn
Network Zen Network Zen
1310 E. Thomas Street 1463 East Republican Street, #358
Seattle, WA 98102 Seattle, WA 98112
USA 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
Phone: +91 80 4103 6427 Phone: +91 80 4103 6427
Email: subashtc@cisco.com Email: subashtc@cisco.com
 End of changes. 16 change blocks. 
17 lines changed or deleted 37 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/