INTERNET-DRAFT Dinh Nguyen - Cisco Systems Rick Chen - Cisco Systems January 15, 1998 External Media Gateway Control Protocol MIB XGCP-MIB Status of this memo: This document is an Internet-Draft. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. The other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as ``work in progress''. To learn the current status of any Internet-Draft, please check the ``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). This document specifies the MIB proposal for External Media Gateway Control Protocols (SGCP/MGCP). External Media Gateway Control Protocol such as SGCP/MGCP is a solution for controlling VoIP Gateways from external control elements called External Media Gateway Controllers. Copyright Notice: Copyright (C) The Internet Society (1998-1999). All Rights Reserved. Abstract This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, this proposal specifies a new XGCP-MIB module in a manner that is compliant to the SNMP SMI. The set of its objects is consistent with the SNMP framework and other existing SNMP standards. Table of Contents Abstract ..............................................................1 1.0 Introduction ......................................................2 2.0 Revision History ..................................................2 3.0 The SNMP Network Management Framework..............................2 3.1 Object Definitions ................................................3 4.0 Overview ..........................................................3 4.1 Tables ............................................................3 Expires JULY 1999 [Page 1] INTERNET-DRAFT XGCP-MIB JANUARY 15,1999 4.2 Objects ...........................................................3 5.0 Definitions .......................................................4 6.0 Acknowledgments ..................................................18 7.0 Security Considerations ..........................................18 8.0 References .......................................................19 9.0 Editor's Address .................................................20 1.0 Introduction A management system contains: several (potentially many) nodes, each with a processing entity, termed the agent, which has access to management instrumentation; at least one management station; and, a management protocol, used to convey management information between the agents and management stations. Operations of the protocol are carried out under an administrative framework which define authentication, authorization, access control, and privacy policies. Management stations execute management applications which monitor and control managed elements. Managed elements are devices such as hosts, routers, terminal servers, etc., which are monitored and controlled via access to their management information. Management information is viewed as a collection of managed objects, residing in a virtual information store, termed the Management Information Base (MIB). Collections of related objects are defined in MIB modules. These modules are written using a subset of OSI's Abstract Syntax Notation One (ASN.1) [1], termed the Structure of Management Information (SMI) [2]. This document is the MIB module which defines managed objects for managing implementations of the External Media Gateway Control Protocol such as SGCP [3] and MGCP [4]. SGCP/MGCP is a protocol used between a Media Gateway Controller and a Media Gateway in a VoIP network, where the Media Gateway Controller uses SGCP/MGCP to control the media gateway connected through an IP network. In the SGCP/MGCP model, call control intelligence resides in the Media Gateway Controller and outside of the media gateway. 2.0 Revision History 0.01 January 15, 1999 - Initial version 3.0 The SNMP Network Management Framework The SNMP Network Management Framework consists of three major components. They are: 1. STD 16/RFC 1155 [5] which defines the SMI, the mechanism used for describing and naming objects for the purpose of management. STD 16/RFC 1212 [8] defines a more concise description mechanism, Expires JULY 1999 [Page 2] INTERNET-DRAFT XGCP-MIB JANUARY 15,1999 which is wholly consistent with the SMI. 2. RFC 1156 [6] which defines MIB-I, the core set of managed objects for the Internet suite of protocols. STD 17/RFC 1213 [9] defines MIB-II, an evolution of MIB-I based on implementation experience and new operational requirements. 3. STD 15/RFC 1157 [7] which defines the SNMP, the protocol used for network access to managed objects. The Framework permits new objects to be defined for the purpose of experimentation and evaluation. 3.1 Object Definitions Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the subset of Abstract Syntax Notation One (ASN.1) defined in the SMI. In particular, each object type is named by an OBJECT IDENTIFIER, an administratively assigned name. The object type together with an object instance serves to uniquely identify a specific instantiation of the object. For human convenience, we often use a textual string, termed the descriptor, to refer to the object type. 4.0 Overview 4.1 Tables 4.1.1 Message Statistics Table The message statistics information table - This table is used for SGCP/MGCP message statistics since reset. The IP Address will be used as an index for this table. Message statistics entry in the table is per IP Address. 4.1.2 Capability Package Table The Capability Package table - This table is used to specify the availability of the packages. The Capabality Package Name is used as the index for the table. 4.2 Objects This MIB module contains new objects for managing timeout values, maximum waiting delay, restart timer for restart process, request retry counter, package capability, IP Address and Domain Name of the default MGC, packet loss threshold, quality alert thresholds. Trap for protocol shutdown or bring-up is provided. 5.0 Definitions Expires JULY 1999 [Page 3] INTERNET-DRAFT XGCP-MIB JANUARY 15,1999 XGCP-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Integer32, Counter32, IpAddress, NOTIFICATION-TYPE FROM SNMPv2-SMI TEXTUAL-CONVENTION, TruthValue, DisplayString FROM SNMPv2-TC ciscoExperiment FROM CISCO-SMI MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; xgcpMIB MODULE-IDENTITY LAST-UPDATED "9901150000Z" ORGANIZATION "Will submit this new XGCP-MIB to IETF-DRAFT" CONTACT-INFO " Dinh D. Nguyen Postal: Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 US Phone: +1 408 525 1624 Email: dinhn@cisco.com Rick N. Chen Postal: Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 US Phone: +1 408 525 6367 Email: richen@cisco.com" DESCRIPTION "The MIB module for managing XGCP implementations." REVISION "9901500000Z" DESCRIPTION "This is initial version of XGCP MIB." ::= { experimental xxxx } Expires JULY 1999 [Page 4] INTERNET-DRAFT XGCP-MIB JANUARY 15,1999 CapabilityPackageName ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "An identification for a XGCP Capability Package. A CapabilityPackageName corresponds one-to-one to a xgcpCapabilityPackageName index. " SYNTAX DisplayString (SIZE (1..64)) xgcpObjects OBJECT IDENTIFIER ::= { xgcpMIB 1 } xgcpCoreGrpObjects OBJECT IDENTIFIER ::= { xgcpObjects 1 } xgcpExtentionGrpObjects OBJECT IDENTIFIER ::= { xgcpObjects 2 } xgcpPackageGrpObjects OBJECT IDENTIFIER ::= { xgcpObjects 3 } xgcpVoiceQualityGrpObjects OBJECT IDENTIFIER ::= { xgcpObjects 4 } -- ********************************************************************* -- The XGCP Core Group -- ********************************************************************* xgcpInBadVersionCount OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of incoming messages which were delivered to the protocol entity and were for an unsupported protocol version. " ::= { xgcpCoreGrpObjects 1 } xgcpRequestTimeOut OBJECT-TYPE SYNTAX Integer32 (1..100000) UNITS "milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION "The request timeout is used to determine the timeout value used for retransmitting unacknowledged message. It is the responsibility of the requesting entity to provide suitable timeouts for all outstanding commands, and to retry commands when timeouts exceeded. The default value of this object is 500 milliseconds. " ::= { xgcpCoreGrpObjects 2 } xgcpRequestRetryCount OBJECT-TYPE SYNTAX Integer32 (0..10) MAX-ACCESS read-write STATUS current DESCRIPTION Expires JULY 1999 [Page 5] INTERNET-DRAFT XGCP-MIB JANUARY 15,1999 "This object specifies the number of retries for a request that exceeds timeout. It is the responsibility of the requesting entity to provide suitable timeouts for all outstanding commands, and to retry when times out. The range for this object is from 0 to 10. The default value of this object is 3. " ::= { xgcpCoreGrpObjects 3 } xgcpAdminStatus OBJECT-TYPE SYNTAX INTEGER { adminStatusUp (1), adminStatusDown (2), adminStatusGracefulDown (3) } MAX-ACCESS read-write STATUS current DESCRIPTION "This object is used for the Admin Status of the protocol entity. The possible admin status are: up - up protocol entity administratively down - down protocol entity adiministratively graceful-shutdown - gracefully shut down protocol entity administratively. A graceful shutdown indicates that the protocol will be taken out of service after the restart delay timer timeouts or all connections are torn down. When in adminStatusGracefulDown, the xgcpOperStatus goes from operStatusUp to operStatusDown via operStatusShutDownInProgress. If there is no connection or restart delay timer timeouts then xgcpOperStatus moves from operStatusShutDownInProgress to operStatusDown. " DEFVAL { adminStatusDown } ::= { xgcpCoreGrpObjects 4 } xgcpOperStatus OBJECT-TYPE SYNTAX INTEGER { operStatusUp (1), operStatusDown (2), operStatusShutDownInProgress (3) } MAX-ACCESS read-only STATUS current DESCRIPTION Expires JULY 1999 [Page 6] INTERNET-DRAFT XGCP-MIB JANUARY 15,1999 "This object is used for the Operating Status of the protocol entity. The possible operating status are: up - protocol up down - protocol down shutdown-in-progress - Shut down in progress. Shutdown in progress state indicates that the Media Gateway is in a transition state from up to down. This state happens when resources are in the process of being cleaned up and new resource can't be allocated. " ::= { xgcpCoreGrpObjects 5 } xgcpUnRecognizedPacketCount OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION " This refers to the count of unrecognized packets since reset. " ::= { xgcpCoreGrpObjects 6 } -- ***************************************************************** -- -- The XGCP Statistics table -- -- ***************************************************************** -- -- XGCP statistics are kept in this table, with each -- table entry containing the statistics of XGCP that -- communicates with a Media Gateway Controller (MGC) at -- a specific IP address of the MGC. -- -- Each table entry is composed of the following information: -- -- 1) Total messages received/transmitted per IP device -- 2) Messages successfully received/transmitted per IP device -- -- Successful messages apply to both transmit and -- receive messages. -- Transmit: Positive ACK is received from the Media -- Gateway Controller -- Receive: Positive ACK is sent to the Media Gateway -- Controller. This implies that the format -- of the message is correct and the request -- can be fulfilled. -- -- Failed messages apply to both transmit and receive Expires JULY 1999 [Page 7] INTERNET-DRAFT XGCP-MIB JANUARY 15,1999 -- messages. -- Transmit: Either NAK is received from the MGC or message -- times out waiting for ACK. -- Receive: Format of the received message is bad or -- the request can not be fulfilled. xgcpMsgStatTable OBJECT-TYPE SYNTAX SEQUENCE OF XgcpMsgStatEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains XGCP statistics information since reset. " ::= { xgcpCoreGrpObjects 7 } xgcpMsgStatEntry OBJECT-TYPE SYNTAX XgcpMsgStatEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The row of the xgcpMsgStatTable contains information about XGCP message statistics per IP address of the Media Gateway Controller. LRU (Least Recently Used) is used to maintain the entry of this table. " INDEX { xgcpIPAddress } ::= { xgcpMsgStatTable 1 } XgcpMsgStatEntry ::= SEQUENCE { xgcpIPAddress IpAddress, xgcpTotalMessageCount Counter32, xgcpMessageSuccessCount Counter32, xgcpMessageFailCount Counter32 } xgcpIPAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION " This object specifies the IP address of the Media Gateway Controller. " ::= { xgcpMsgStatEntry 1 } xgcpTotalMessageCount OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION " This object specifies the total count of messages Expires JULY 1999 [Page 8] INTERNET-DRAFT XGCP-MIB JANUARY 15,1999 (transmitted and received) that communicate with the Media Gateway Controller on that IP address. " ::= { xgcpMsgStatEntry 2 } xgcpMessageSuccessCount OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object specifies the count of successful messages that communicate with the Media Gateway Controller on that IP address. Successful messages: Transmit: Positive ACK is received from the Media Gateway Controller Receive: Positive ACK is sent to the Media Gateway Controller " ::= { xgcpMsgStatEntry 3 } xgcpMessageFailCount OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object specifies the count of failed messages that communicate with the Media Gateway Controller on that IP address. Failed messages apply to both transmit and receive messages. Transmit: Either NAK is received from the Media Gateway Controller or message times out waiting for an ACK. Receive: Either Format of the received message is bad or the request can not be fulfilled. " ::= { xgcpMsgStatEntry 4 } -- ***************************************************************** -- The XGCP Extention Group -- ***************************************************************** xgcpMaxWaitingDelayTimeOut OBJECT-TYPE SYNTAX Integer32 (0..300000) UNITS "milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION Expires JULY 1999 [Page 9] INTERNET-DRAFT XGCP-MIB JANUARY 15,1999 "The maximum waiting delay (MWD) timeout value is used for the Media Gateway to send the Restart In Progress to the Media Gateway Controller. The default value of this object is chosen in an implementation-dependent manner by the MGCP functionality based on the call volume of the system. " REFERENCE " Media Gateway Control Protocol (MGCP), version 0.1 draft, Nov 9, 1998 : Section 2.4.4 " ::= { xgcpExtentionGrpObjects 1 } xgcpRestartDelayTimeOut OBJECT-TYPE SYNTAX Integer32 (-1..30) UNITS "seconds" MAX-ACCESS read-write STATUS current DESCRIPTION "This object specifies the Restart Delay Timeout for the restart process. The purpose of setting the restart timer before sending the Restart In Progress notification to the media gateway controller is to avoid the network congestion during the critical period of service restoration. -1: infinity which indicates no timeout. 0: immediate timeout which indicates immediate shutdown. The default value of this object is -1. " REFERENCE " Media Gateway Control Protocol (MGCP), version 0.1 draft, Nov 9, 1998 : Section 2.4.4 " ::= { xgcpExtentionGrpObjects 2 } xgcpMGCCfgIPAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-write STATUS current DESCRIPTION "This object is used for the IP Address of the Default Media Gateway Controller. " ::= { xgcpExtentionGrpObjects 3 } xgcpMGCCfgDomainName OBJECT-TYPE SYNTAX DisplayString (SIZE (1..64)) MAX-ACCESS read-write Expires JULY 1999 [Page 10] INTERNET-DRAFT XGCP-MIB JANUARY 15,1999 STATUS current DESCRIPTION "This object is used to configure the domain name of the Default Media Gateway Controller. " ::= { xgcpExtentionGrpObjects 4 } -- ***************************************************************** -- The XGCP Package Group -- ***************************************************************** -- ***************************************************************** -- The XGCP Capability Package table -- ***************************************************************** -- -- The Capability Package table - This table is used to specify -- the availability of the packages. -- -- The Capabality Package Name is used as the index for the table. -- -- Each entry contains a CapabilityPackageEnable object. It is -- used to enable/disable a package on the Media Gateway. -- The default value of this object is "true". A user can -- de-activate the package by setting this variable to "false" -- xgcpCapabilityPackageTable OBJECT-TYPE SYNTAX SEQUENCE OF XgcpCapabilityPackageEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains XGCP capability packages. " ::= { xgcpPackageGrpObjects 1 } xgcpCapabilityPackageEntry OBJECT-TYPE SYNTAX XgcpCapabilityPackageEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The entry specifies the availability of the XGCP package. Each entry is created when the MGCP software detects a new package. New package is added in the system. " INDEX { IMPLIED xgcpCapabilityPackageName } ::= { xgcpCapabilityPackageTable 1 } XgcpCapabilityPackageEntry ::= SEQUENCE { xgcpCapabilityPackageName CapabilityPackageName, xgcpCapabilityPackageEnable TruthValue, Expires JULY 1999 [Page 11] INTERNET-DRAFT XGCP-MIB JANUARY 15,1999 xgcpDefaultPackage TruthValue } xgcpCapabilityPackageName OBJECT-TYPE SYNTAX CapabilityPackageName MAX-ACCESS not-accessible STATUS current DESCRIPTION " This object specifies the Name of the Capability Package. The list of basic packages includes the following: _________________________________________ | Package | name | |______________________________|_________| | Generic Media Package | G | | DTMF package | D | | MF Package | M | | Trunk Package | T | | Line Package | L | | Handset Package | H | | RTP Package | R | | Netwark Access Server Package| N | | Announcement Server Package | A | | Script Package | Script| |______________________________|_________| " REFERENCE " Media Gateway Control Protocol (MGCP), version 0.1 draft, Nov 9, 1998 : Section 5.1 " ::= { xgcpCapabilityPackageEntry 1 } xgcpCapabilityPackageEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION " This object eables/disables the Package Capability " DEFVAL { true } ::= { xgcpCapabilityPackageEntry 2 } xgcpDefaultPackage OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION " This object specifies the default package. The default package is assumed when no package is Expires JULY 1999 [Page 12] INTERNET-DRAFT XGCP-MIB JANUARY 15,1999 specified in the request message. " REFERENCE " Media Gateway Control Protocol (MGCP), version 0.1 draft, Nov 9, 1998 : Section 2.1.6 " DEFVAL { true } ::= { xgcpCapabilityPackageEntry 3 } -- ***************************************************************** -- The XGCP Voice Quality Group -- ***************************************************************** xgcpLowWaterMarkForPacketLoss OBJECT-TYPE SYNTAX Integer32 (1..3000) MAX-ACCESS read-write STATUS current DESCRIPTION "This object specifies the low water mark for voice quality packet loss per 100,000 packets. Voice quality packet loss may happen due to network congestion or due to network overload. The damping happens between the low water mark and high water mark of packet loss. Whenever the damping hits high water mark preceded by hitting low water mark, a notify is sent to the Media Gateway Controller. The range of this object is from 1 to 3000. The default value of this object is 1000. " ::= { xgcpVoiceQualityGrpObjects 1 } xgcpHighWaterMarkForPacketLoss OBJECT-TYPE SYNTAX Integer32 (5000..25000) MAX-ACCESS read-write STATUS current DESCRIPTION "This object specifies the high water mark for voice quality packet loss per 100,000 packets. Voice quality packet loss may happen due to network congestion or due to network overload. The damping happens between the low water mark and high water mark of packet loss. The first hit of the high water mark results in a notify being sent to the Media Gateway Controller. Subsequent hits of the high water mark results in a notify being sent to the Media Gateway Controller only after the low water mark is hit. Expires JULY 1999 [Page 13] INTERNET-DRAFT XGCP-MIB JANUARY 15,1999 The range of this object is from 5000 to 25000. The default value of this object is 10,000. " ::= { xgcpVoiceQualityGrpObjects 2 } xgcpLowWaterMarkForJitter OBJECT-TYPE SYNTAX Integer32 (4..60) UNITS "milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION " This object is the low water mark for Quality Alert for Jitter. Jitter is an estimate of the statistical variance of the RTP data packet interval-rival time measured in milliseconds and expressed as an unsigned integer. The damping happens between the low water mark and high water mark. Whenever the damping hits high water mark preceded by hitting low water mark, a notify is sent to the Media Gateway Controller. The range of this object is from 4 to 60. The default value of this object is 30. " ::= { xgcpVoiceQualityGrpObjects 3 } xgcpHighWaterMarkForJitter OBJECT-TYPE SYNTAX Integer32 (100..200) UNITS "milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION " This object is the high water mark for Quality Alert for Jitter. Jitter is an estimate of the statistical variance of the RTP data packet interval-rival time measured in milliseconds and expressed as an unsigned integer. The damping happens between the low water mark and high water mark. The first hit of the high water mark results in notify sent to the Media Gateway Controller. Subsequent hits of the high water mark results in a notify being sent to the Media Gateway Controller only after the low water mark is hit. The range of this object is from 100 to 200. The default value of this object is 150. " ::= { xgcpVoiceQualityGrpObjects 4 } Expires JULY 1999 [Page 14] INTERNET-DRAFT XGCP-MIB JANUARY 15,1999 xgcpLowWaterMarkForLatency OBJECT-TYPE SYNTAX Integer32 (125..200) UNITS "milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION " This object is the high water mark for Quality Alert for latency. QA latency is an estimate of the network delay, expressed in milliseconds. This is the average value of the difference between the Network Time Protocol (NTP) timestamp indicated by the senders of the RTCP messages and the NTP timestamp of the receivers, measured when these messages are received. The damping happens between the low water mark and high water mark. Whenever the damping hits high water mark preceded by hitting low water mark, a notify is sent to the Media Gateway Controller. The range of this object is from 125 to 200. The default value of this object is 150. " ::= { xgcpVoiceQualityGrpObjects 5 } xgcpHighWaterMarkForLatency OBJECT-TYPE SYNTAX Integer32 (250..400) UNITS "milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION " This object is the high water mark for Quality Alert for latency. QA latency is an estimate of the network delay, expressed in milliseconds. This is the average value of the difference between the NTP timestamp indicated by the senders of the RTCP messages and the NTP timestamp of the receivers, measured when these messages are received. The damping happens between the low water mark and high water mark. The first hit of the high water mark results in a notify being sent to the Media Gateway Controller. Subsequent hits of the high water mark results in a notify being sent to the Media Gateway Controller only after the low water mark is hit. The range of this object is from 250 to 400. The default value of this object is 300. " Expires JULY 1999 [Page 15] INTERNET-DRAFT XGCP-MIB JANUARY 15,1999 ::= { xgcpVoiceQualityGrpObjects 6 } -- ********************************************************************* -- Media gateway control notification -- ********************************************************************* xgcpNotificationPrefix OBJECT IDENTIFIER ::= { xgcpMIB 2 } xgcpNotifications OBJECT IDENTIFIER ::= { xgcpNotificationPrefix 0 } xgcpUpDownNotification NOTIFICATION-TYPE STATUS current DESCRIPTION "This notification is sent when the protocol status changes between up and down. " ::= { xgcpNotifications 1 } --********************************************************************** -- Conformance --********************************************************************** -- -- conformance information -- xgcpMIBConformance OBJECT IDENTIFIER ::= { xgcpMIB 3 } xgcpMIBCompliances OBJECT IDENTIFIER ::= { xgcpMIBConformance 1 } xgcpMIBGroups OBJECT IDENTIFIER ::= { xgcpMIBConformance 2 } -- -- Conformance and compliance statements statements -- xgcpMIBCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for the SNMPv2 entities which implement XGCP." MODULE -- this module MANDATORY-GROUPS { xgcpCoreGroup } GROUP xgcpExtensionGroup DESCRIPTION "The xgcp Extension Group is mandatory for MGCP on the Media Gateway. " GROUP xgcpPackageGroup Expires JULY 1999 [Page 16] INTERNET-DRAFT XGCP-MIB JANUARY 15,1999 DESCRIPTION "The xgcp Package Group is mandatory for MGCP on the Media Gateway Controller and the Media Gateway. " GROUP xgcpVoiceQualityGroup DESCRIPTION "The xgcp Voice Quality Group is mandatory for MGCP on the Media Gateway. " ::= { xgcpMIBCompliances 1 } -- -- units of conformance -- -- MIB Groups -- xgcpCoreGroup OBJECT-GROUP OBJECTS { xgcpInBadVersionCount, xgcpRequestTimeOut, xgcpRequestRetryCount, xgcpAdminStatus, xgcpOperStatus, xgcpUnRecognizedPacketCount, xgcpTotalMessageCount, xgcpMessageSuccessCount, xgcpMessageFailCount } STATUS current DESCRIPTION "This group contains core objects for SGCP/MGCP on the Media Gateway Controller and the Media Gateway. " ::= { xgcpMIBGroups 1 } xgcpExtensionGroup OBJECT-GROUP OBJECTS { xgcpMaxWaitingDelayTimeOut, xgcpRestartDelayTimeOut, xgcpMGCCfgIPAddress, xgcpMGCCfgDomainName } STATUS current DESCRIPTION "This group contains extension objects for MGCP on the Media Gateway. " ::= { xgcpMIBGroups 2 } Expires JULY 1999 [Page 17] INTERNET-DRAFT XGCP-MIB JANUARY 15,1999 xgcpPackageGroup OBJECT-GROUP OBJECTS { xgcpCapabilityPackageEnable, xgcpDefaultPackage } STATUS current DESCRIPTION "This group contains package objects for MGCP on the Media Gateway or the Media Gateway Controller. " ::= { xgcpMIBGroups 3 } xgcpVoiceQualityGroup OBJECT-GROUP OBJECTS { xgcpLowWaterMarkForPacketLoss, xgcpHighWaterMarkForPacketLoss, xgcpLowWaterMarkForJitter, xgcpHighWaterMarkForJitter, xgcpLowWaterMarkForLatency, xgcpHighWaterMarkForLatency } STATUS current DESCRIPTION "This group contains voice quality objects for the Media Gateway ." ::= { xgcpMIBGroups 4 } END 6.0 Acknowledgments Thanks to David Oran, Bob Stewart, Hongchi Shih, Bill Foster, Alex Clemm, Dan Lai, Eliza Duerme, Thao Tran, and Mike Hubenthal- Cisco Systems, for helping and reviewing this first draft version. 7.0 Security Considerations This MIB contains readable objects whose values provide information related to External Media Gateway Control (SGCP/MGCP). There are also objects that have a MAX-ACCESS clause of read-write and/or read-create, such as those which allow an administrator to dynamically configure protocol information. While unauthorized access to the readable objects is relatively innocuous, unauthorized access to the write-able objects can cause a denial of service, or can cause unauthorized creation and/or manipulation of the protocols. Hence, the support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. It is recommended that the designers consider the security features as provided by the SNMPv3 framework. Specifically, the use of the Expires JULY 1999 [Page 18] INTERNET-DRAFT XGCP-MIB JANUARY 15,1999 User-based Security Model RFC 2274 [17] and the View-based Access Control Model RFC 2275 [16] is recommended. It is then a customer/user responsibility to ensure that the SNMP entity giving access to this MIB, is properly configured to give access to those objects only to those principals (users) that have legitimate rights to access them. 8.0 References [1] Information processing systems - Open Systems Interconnection Specification of Abstract Syntax Notation One (ASN.1), International Organization for Standardization. International Standard 8824, (December, 1987). [2] McCloghrie, K., Editor, "Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, Cisco Systems, January 1996. [3] Maurico Arango et al, Simple Gateway Control Protocol, Version 1.1 June 26, 1998 [4] Maurico Arango et al, Media Gateway Control Protocol, Version 0.1 draft, November 9, 1998 [5] Rose, M., and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", RFC 1155, Performance Systems International, Hughes LAN Systems, May 1990. [6] Rose, M., and K. McCloghrie, "Management Information Base for Network Management", RFC 1156, Performance Systems International, Hughes LAN Systems, May 1990. [7] J. Case, M. Fedor, M. Schoffstall, J. Davin, "Simple Network Management Protocol (SNMP)", RFC 1157, May 1990. [8] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, Performance Systems International, Hughes LAN Systems, March 1991. [9] Rose, M., and K. McCloghrie, "Management Information Base for Network Management of TCP/IP-based internets: MIB-II", RFC 1213 Performance Systems International, Hughes LAN Systems, May 1990. [10] M. Rose,"A Convention for Defining Traps for use with the SNMP, RFC 1215, Performance Systems International, March 1991. [11] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2271, Cabletron Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998. [12] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, SNMP Research,Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., International Network Services, January 1996. [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., International Network Services, January 1996. [14] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, SNMP Expires JULY 1999 [Page 19] INTERNET-DRAFT XGCP-MIB JANUARY 15,1999 Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., International Network Services, January 1996. [15] R. Atkinson. "Security architecture for the internet protocol" RFC 1825, August 1995. [16] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc., Cisco Systems, Inc., January 1998. [17] Blumenthal, U., and B. Wijnen, "User-based Security Model(USM) for version 3 of the Simple Network Management Protocol (SNMPv3)" RFC 2274, IBM T. J. Watson Research, January 1998. [18] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB using SMIv2", RFC 2233, Cisco Systems, FTP Software, November 1997. 9.0 Editor's Address Dinh D. Nguyen Cisco Systems 170 West Tasman Drive San Jose, CA 95134-1706 Phone: +1 408 525 1624 Email: dinhn@cisco.com Rick Chen Cisco Systems 170 West Tasman Drive San Jose, CA 95134-1706 Phone: +1 408 525 6367 Email: richen@cisco.com Expires JULY 1999 [Page 20]