draft-ietf-dime-diameter-base-protocol-mib-00.txt   draft-ietf-dime-diameter-base-protocol-mib-01.txt 
Network Working Group G. Zorn Network Working Group G. Zorn, Ed.
Internet-Draft Network Zen Internet-Draft Network Zen
Intended status: Informational S. Comerica Intended status: Informational S. Comerica
Expires: November 20, 2009 Cisco Systems Expires: January 2, 2010 Cisco Systems
May 19, 2009 July 1, 2009
Diameter Base Protocol MIB Diameter Base Protocol MIB
draft-ietf-dime-diameter-base-protocol-mib-00.txt draft-ietf-dime-diameter-base-protocol-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
skipping to change at page 2, line 21 skipping to change at page 2, line 27
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.
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 . . . . . . . . . . . . . . . . . . . . . 49 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 48
6. Security Considerations . . . . . . . . . . . . . . . . . . . 49 6. Security Considerations . . . . . . . . . . . . . . . . . . . 48
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 50 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 49
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 50 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 49
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 50 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 50
9.1. Normative References . . . . . . . . . . . . . . . . . . . 50 9.1. Normative References . . . . . . . . . . . . . . . . . . . 50
9.2. Informative References . . . . . . . . . . . . . . . . . . 50 9.2. Informative References . . . . . . . . . . . . . . . . . . 50
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 51 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 51
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 base Diameter protocol
managing the base Diameter protocol. [RFC3588].
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 [RFC1215]. 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
always extended for a particular application. Four standard Diameter
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
base protocol as described in [RFC3588]. Objects related to the base protocol as described in RFC 3588 [RFC3588]. Objects related to
applications mentioned above (and any additional applications created Diameter applications are defined in separate documents.
in the future) will be defined in separate documents.
4. Diameter Base Protocol MIB Definitions 4. Diameter Base Protocol MIB Definitions
DIAMETER-BASE-PROTOCOL-MIB DEFINITIONS ::= BEGIN DIAMETER-BASE-PROTOCOL-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
InetAddressType, InetAddressType,
InetAddress InetAddress
FROM INET-ADDRESS-MIB -- [RFC4001] FROM INET-ADDRESS-MIB -- [RFC4001]
MODULE-IDENTITY, MODULE-IDENTITY,
skipping to change at page 21, line 43 skipping to change at page 21, line 33
"A row entry representing a "A row entry representing a
Vendor ID supported by the peer." Vendor ID supported by the peer."
INDEX { INDEX {
dbpPeerIndex, dbpPeerIndex,
dbpPeerVendorIndex dbpPeerVendorIndex
} }
::= { dbpPeerVendorTable 1 } ::= { dbpPeerVendorTable 1 }
DbpPeerVendorEntry ::= SEQUENCE { DbpPeerVendorEntry ::= SEQUENCE {
dbpPeerVendorIndex Unsigned32, dbpPeerVendorIndex Unsigned32,
dbpPeerVendorId INTEGER , dbpPeerVendorId Unsigned32,
dbpPeerVendorStorageType StorageType, dbpPeerVendorStorageType StorageType,
dbpPeerVendorRowStatus RowStatus dbpPeerVendorRowStatus RowStatus
} }
dbpPeerVendorIndex OBJECT-TYPE dbpPeerVendorIndex 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 the Vendor "A number uniquely identifying the Vendor
ID supported by the peer. Upon reload, ID supported by the peer. Upon reload,
dbpPeerVendorIndex values may be changed." dbpPeerVendorIndex values may be changed."
::= { dbpPeerVendorEntry 1 } ::= { dbpPeerVendorEntry 1 }
dbpPeerVendorId OBJECT-TYPE dbpPeerVendorId OBJECT-TYPE
SYNTAX INTEGER { SYNTAX Unsigned32 (1..4294967295 )
diameterVendorIetf(0),
diameterVendorCisco(9),
diameterVendor3gpp(10415),
diameterVendorVodafone(12645)
}
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The active vendor ID used for peer connections. "The active vendor ID used for peer connections."
diameterVendorIetf(0) -- IETF
diameterVendor3gpp(10415) - 3GPP
DEFVAL { diameterVendorIetf }
::= { dbpPeerVendorEntry 2 } ::= { dbpPeerVendorEntry 2 }
dbpPeerVendorStorageType OBJECT-TYPE dbpPeerVendorStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row. "The storage type for this conceptual row.
None of the objects are writable when the None of the objects are writable when the
conceptual row is permanent." conceptual row is permanent."
skipping to change at page 50, line 14 skipping to change at page 49, line 48
7. Contributors 7. Contributors
This document is based upon and derived from work done by Jay This document is based upon and derived from work done by Jay
Koehler, Mark Eklund and Hai Li. Koehler, Mark Eklund and Hai Li.
8. Acknowledgements 8. Acknowledgements
Thanks to David Battle for his participation and suggestions in Thanks to David Battle for his participation and suggestions in
designing the table structures; Kevin Lingle, Sumanth Mithra, Tolga designing the table structures; Kevin Lingle, Sumanth Mithra, Tolga
Asveren and Biswaranjan Panda for reviewing the MIB and making Asveren, Tina Tsou, Mark Jone, John Loughney and Biswaranjan Panda
invaluable suggestions; and Greg Weber for his help in representing for reviewing the MIB and making useful suggestions; and Greg Weber
the MIB at IETF meetings. for his help in representing the MIB at IETF meetings.
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC1215] Rose, M., "Convention for defining traps for use with the [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
SNMP", RFC 1215, March 1991. 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
August 2005. Addresses", RFC 4001, February 2005.
9.2. Informative References 9.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
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. 21 change blocks. 
68 lines changed or deleted 45 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/