Media Gateway Control (Megaco) Internet Draft Bala Pitchandi Document: draft-pitchandi-megaco-ringing-mib-00.txt UTStarcom Inc Expires: April 2003 October 2002 Megaco Ringing MIB Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026 [1]. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that 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." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for use by the MEGACO/H.248 Ringing Packages operating on Media Gateways. These objects can be used to manage the network containing Media Gateway(s). This is the initial version of this draft. This draft defines a MIB that contains the elements for defining ringing patterns [21]. Rules have been defined below which MUST be adhered to ensure a properly defined set of ringing patterns. Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119 [2]. Pitchandi Standards Track - Expires April 2003 [Page 1] Megaco Ringing MIB October 2002 1. Overview The MEGACO/H.248 protocol [3] [4] defines communication between the elements of a physically decomposed multimedia gateway. Those elements are the Media Gateway Controller (MGC) and the Media Gateway (MG). This MIB defines objects on these elements that are to be used to configure the different ringing patterns. This MIB is defined as per the concepts and specifications of the SNMP Management Framework, which consists of 5 parts as follows. . An overall architecture, described in RFC 2571 [5]. . Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and described in STD 16, RFC 1155 [6], STD 16, RFC 1212 [7] and RFC 1215 [8]. The second version, called SMIv2, is described in STD 58, RFC 2578 [9], STD 58, RFC 2579 [10] and STD 58, RFC 2580 [11]. . Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in STD 15, RFC 1157 [12]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [13] and RFC 1905 [14]. The third version of the message protocol is called SNMPv3 and described in RFC 2570 [15], RFC 2573 [16] and RFC 2575 [17]. . Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in STD 15, RFC 1157 [12]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [14]. . A set of fundamental applications described in RFC 2573 [16] and the view-based access control mechanism described in RFC 2575 [17]. A more detailed introduction to the current SNMP Management Framework can be found in RFC 2570 [15]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the mechanisms defined in the SMI. This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no translation is possible (use of Counter64). Some machine readable information in SMIv2 will be converted into Pitchandi Standards Track - Expires April 2003 [Page 2] Megaco Ringing MIB October 2002 textual descriptions in SMIv1 during the translation process. However, this loss of machine readable information is not considered to change the semantics of the MIB. 2. Ringing MIB Definition MEGACO-RINGING-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Integer32, OBJECT-IDENTITY, mib-2 FROM SNMPv2-SMI RowStatus, DisplayString, TestAndIncr FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP, FROM SNMOv2-CONF; NOTIFICATION-GROUP megacoRingingMIB MODULE-IDENTITY LAST-UPDATED "200210081200Z" -- 08 Oct 2002 ORGANIZATION "IETF" CONTACT-INFO " Postal: Bala Pitchandi UTStarcom Inc 33 Wood Avenue South Iselin, NJ 08830 Email: bs@utstar.com Phone: +1 (732)442-4457 " DESCRIPTION "The MEGACO RINGING MIB module." -- Revision History REVISION "200210081200Z" -- 08 Oct 2002 DESCRIPTION "This is the initial Draft version of this MIB." ::= { mib-2 xx } _ final assignment by IANA at publication time -- ***************************************************************** -- Pitchandi Standards Track - Expires April 2003 [Page 3] Megaco Ringing MIB October 2002 -- OID and Group Definitions -- -- ***************************************************************** -- OID for the MIB Objects... megacoRingingMIBObjects OBJECT IDENTIFIER::= {megacoRingingMIB 1} -- The Megaco Ringing MIB contains 2 (object) groups. mgcoRingingCapabilities OBJECT IDENTIFIER::= {megacoRingingMIBObjects 1} mgcoRingingProperties OBJECT IDENTIFIER::= {megacoRingingMIBObjects 2} -- ***************************************************************** -- -- Megaco Profile Property -- -- OIDs that define the Properties that a Termination can support. -- The MEGACO-MIB supports a Property Profile Table, in which -- a Manager defines a Property Profile by defining a list of properties -- that a termination supports. -- -- mgcoRingingProperty represents the OID for the Ringing Property -- --****************************************************************** mgcoRingingProperty OBJECT-IDENTITY STATUS current DESCRIPTION "Ringing Property Package" ::= { mgcoRingingProperties 1 } --****************************************************************** -- -- MEGACO RINGING MIB .... -- -- The MEGACO RINGING MIB module consists of two tables -- -- (1) mgcoRingingPatternTable -- Multiple Ringing patterns are represented through the -- mgcoRingingPatternTable. -- -- (2) mgcoRingingCadenceGroupTable -- Multiple cadences are represented through the -- mgcoRingingCadenceGroupTable. The ring patterns share the -- data contained in the megRingingPatternTable and -- megRingingCadenceGroupTable. -- --****************************************************************** Pitchandi Standards Track - Expires April 2003 [Page 4] Megaco Ringing MIB October 2002 --****************************************************************** -- -- The mgcoRingingPatternTable provides a list of the ringing patterns -- available on a Media Gateway. The mgcoRingingPatternTable consists of -- four objects -- -- mgcoRingingPatternId (index): -- A number indicating a unique pattern; this number represents a -- ringing pattern (for a given market) available on a Media Gateway. -- mgcoRingingCadenceGroupId -- A number indicating a unique Cadence Group Id value that is -- associated with a mgcoRingingPatternId. This number is also -- an index into the mgcoRingingCadenceGroupTable. -- mgcoRingingPatternName -- This is a character string indicating the ringing pattern name -- This pattern name could be represented by the text that would -- be passed in the Signal Descriptor (i.e., the packageId, the -- signalId and other possible parameters). -- mgcoRingingPatternRowStatus -- This is used to create new rows in this table, modify existing -- rows, and to delete existing rows. -- -- The rules that guide this table are -- -- (1) mgcoRingingPatternId represents the pattern id that would be -- sent as the parameter in the packages requesting to apply -- ringing (like alert/ri etc) -- (2) mgcoRingingPatternName represents the pattern name and it could -- represent the package/signal (like alert/ri) -- (3) mgcoRingingCadenceGroupId represents the cadence group that -- constitutes this ringing pattern -- --****************************************************************** mgcoRingingPatternTable OBJECT-TYPE SYNTAX SEQUENCE OF MgcoRingingPatternEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains a list of the various Ringing Pattern Ids available on a Media Gateway. Each row of the table contains a field to indicate the Ringing Pattern Id value, a field to indicate the Cadence Group Id associated with the Ringing Pattern Id, a field to hold a name for the pattern" ::= { mgcoRingingCapabilities 1 } mgcoRingingPatternEntry OBJECT-TYPE SYNTAX MgcoRingingPatternEntry Pitchandi Standards Track - Expires April 2003 [Page 5] Megaco Ringing MIB October 2002 MAX-ACCESS not-accessible STATUS current DESCRIPTION "This entry contains objects that indicate the pattern Id value, the Cadence Group Id value, the pattern Name, and the status of the row. The indices for an entry is the mgcoRingingPatternId and a manager creates a row in this table to define a Ringing pattern." INDEX { mgcoRingingPatternId } ::= { mgcoRingingPatternTable 1 } MgcoRingingPatternEntry ::= SEQUENCE { mgcoRingingPatternId INTEGER, -- na mgcoRingingCadenceGroupId INTEGER, -- rc mgcoRingingPatternName DisplayString, -- rc mgcoRingingPatternRowStatus RowStatus -- rc } mgcoRingingPatternId OBJECT-TYPE SYNTAX INTEGER (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "A value to indicate a unique ringing pattern identity." ::= { mgcoRingingPatternEntry 1 } mgcoRingingCadenceGroupId OBJECT-TYPE SYNTAX INTEGER (1..2147483647) MAX-ACCESS read-create STATUS current DESCRIPTION "A value to indicate the entry in the mgcoRingingCadenceGroupTable that defines this ringing pattern, it is an Index into that table" ::= { mgcoRingingPatternEntry 2 } mgcoRingingPatternName OBJECT-TYPE SYNTAX DisplayString (SIZE(0..255)) MAX-ACCESS read-create STATUS current DESCRIPTION "A string to indicate a unique ringing pattern identity." ::= { mgcoRingingPatternEntry 3 } mgcoRingingPatternRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This is used to create new rows in this table, modify existing rows, and to delete rows." Pitchandi Standards Track - Expires April 2003 [Page 6] Megaco Ringing MIB October 2002 ::= { mgcoRingingPatternEntry 4 } --****************************************************************** -- -- Next Cadence Group Id -- --****************************************************************** mgcoRingingCadenceNextGroupId OBJECT-TYPE SYNTAX TestAndIncr MAX-ACCESS read-write STATUS current DESCRIPTION "The Next Cadence Group Id value available for a Media Gateway. Assists the manager in selecting a value for mgcoRingingCadenceGroupTable. A manager will 'lock' this variable to ensure single access." ::= { mgcoRingingCapabilities 2 } --****************************************************************** -- -- mgcoRingingCadenceGroupTable -- -- The mgcoRingingCadenceGroupTable provides the components that comprise -- the various Group Ids. The mgcoRingingCadenceGroupTable is indexed by the -- mgcoRingingCadenceGroupId (from the mgcoRingingPatternTable) and the -- mgcoRingingCadenceGroupIndex. -- -- The objects of the mgcoRingingCadenceGroupTable are: -- mgcoRingingCadenceGroupId (index) -- A number indicating a unique Cadence Group Id value. This value is -- from the mgcoRingingPatternTable. -- mgcoRingingCadenceGroupIndex (index) -- A number indicating the component number of a cadence group. If the -- cadence group contains only one component then this value is 1; if -- ths cadence group contains multiple components then this value starts -- at 1 and increases by one sequentially for each component. The linkage -- if any, between components of the group is always sequential in time. -- mgcoRingingCadenceGroupName -- A decriptive name which identifies this component of the cadence -- group -- mgcoRingingCadenceGroupRef -- A number indicating an existing cadence group Id value. -- mgcoRingingCadenceGroupRingingMinDuration -- A number indicating the minimum durattion of the Ringing Cadence -- in milliseconds of a ringing cadence group; The range is decimal 0 to -- 5000. -- mgcoRingingCadenceGroupRingingNomDuration -- A number indicating the nominal durattion of the Ringing Cadence -- in milliseconds of a ringing cadence group; The range is decimal 0 to Pitchandi Standards Track - Expires April 2003 [Page 7] Megaco Ringing MIB October 2002 -- 5000. -- mgcoRingingCadenceGroupRingingMaxDuration -- A number indicating the minimum durattion of the Ringing Cadence -- in milliseconds of a ringing cadence group; The range is decimal 0 to -- 5000. -- mgcoRingingCadenceGroupSilentMinDuration -- A number indicating the minimum durattion of the Silence period -- in milliseconds of a ringing cadence group; The range is decimal 0 to -- 5000. -- mgcoRingingCadenceGroupSilentNomDuration -- A number indicating the nominal durattion of the Silence period -- in milliseconds of a ringing cadence group; The range is decimal 0 to -- 5000. -- mgcoRingingCadenceGroupSilentMaxDuration -- A number indicating the maximum durattion of the Silence period -- in milliseconds of a ringing cadence group; The range is decimal 0 to -- 5000. -- mgcoRingingCadenceGroupRowStatus -- This is used to create new rows in this table, modify existing rows, -- and to delete rows. -- -- Rules guiding this table are: -- -- (1) A mgcoRingingCadenceGroupId MUST NOT be deleted if it is referenced -- by another existing mgcoRingingCadenceGroupId. -- (2) A mgcoRingingCadenceGroupId value MUST NOT be the same value as a -- mgcoRingingCadenceGroupRef value for the same table row. -- (3) A mgcoRingingCadenceGroupRef value MUST be a previously defined -- mgcoRingingCadenceGroupId value. -- (4) A mgcoRingingCadenceGroupRingingMinDuration value REQUIRES a -- mgcoRingingCadenceGroupRingingNomDuration value and a -- mgcoRingingCadenceGroupRingingMaxDuration value. -- (5) A mgcoRingingCadenceGroupSilentMinDuration value REQUIRES a -- mgcoRingingCadenceGroupSilentNomDuration value and a -- mgcoRingingCadenceGroupSilentMaxDuration value. -- (6) MinDuration MUST be less than NomDuration which MUST be less than -- MaxDuration. This applies for both Ringing & Silent durations. -- (7) A cadence component could have just ringing duration values (Ring -- Burst) in which case, the Silent durtions would be all NULL (0). -- -- NOTE: An example of a Megaco/H.248 Ringing MIB tables is given -- at the end of the MEGACO RINGING MIB module -- specification. While the example complies with the above -- rules, other valid interpretations are possible. --****************************************************************** mgcoRingingCadenceGroupTable OBJECT-TYPE SYNTAX SEQUENCE OF MgcoRingingCadenceGroupEntry MAX-ACCESS not-accessible Pitchandi Standards Track - Expires April 2003 [Page 8] Megaco Ringing MIB October 2002 STATUS current DESCRIPTION "This table contains a list of the various cadence groups. This table is recursively accessed in order to completely define a cadence" ::= { mgcoRingingCapabilities 3 } mgcoRingingCadenceGroupEntry OBJECT-TYPE SYNTAX MgcoRingingCadenceGroupEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This entry contains objects that describe the cadence characteristics. The indices for an entry are the mgcoRingingCadenceGroupId and mgcoRingingCadenceGroupIndex. mgcoRingingCadenceGroupId is a field from the mgcoRingingPatternTable" INDEX { mgcoRingingCadenceGroupId, mgcoRingingCadenceGroupIndex } ::= { mgcoRingingCadenceGroupTable 1 } MgcoRingingCadenceGroupEntry ::= SEQUENCE { mgcoRingingCadenceGroupIndex INTEGER, mgcoRingingCadenceGroupName DisplayString, mgcoRingingCadenceGroupRef Integer32, mgcoRingingCadenceGroupRingingMinDuration Integer32, mgcoRingingCadenceGroupRingingNomDuration Integer32, mgcoRingingCadenceGroupRingingMaxDuration Integer32, mgcoRingingCadenceGroupSilentMinDuration Integer32, mgcoRingingCadenceGroupSilentNomDuration Integer32, mgcoRingingCadenceGroupSilentMaxDuration Integer32, mgcoRingingCadenceGroupRowStatus RowStatus } mgcoRingingCadenceGroupIndex OBJECT-TYPE SYNTAX INTEGER (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "A value used to access all the entries in the table that correspond to a particular Group Id. This value also serves to order the entries for the Group Index." ::= { mgcoRingingCadenceGroupEntry 1 } mgcoRingingCadenceGroupName OBJECT-TYPE SYNTAX DisplayString (SIZE(0..255)) MAX-ACCESS read-create STATUS current DESCRIPTION "A descriptive name which would identify this component of the cadence" ::= { mgcoRingingCadenceGroupEntry 2 } Pitchandi Standards Track - Expires April 2003 [Page 9] Megaco Ringing MIB October 2002 mgcoRingingCadenceGroupRef OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "A value used to recursively enter the mgcoRingingCadenceGroupTable. It indicates that this portion of the group is a reference to a different GroupId in the table." ::= { mgcoRingingCadenceGroupEntry 3 } mgcoRingingCadenceGroupRingingMinDuration OBJECT-TYPE SYNTAX Integer32(0..5000) MAX-ACCESS read-create STATUS current DESCRIPTION "A value to indicate the minimum duration of the ringing period of this cadence component. The possible values range from 0 to 5000" ::= { mgcoRingingCadenceGroupEntry 4 } mgcoRingingCadenceGroupRingingNomDuration OBJECT-TYPE SYNTAX Integer32(0..5000) MAX-ACCESS read-create STATUS current DESCRIPTION "A value to indicate the nominal duration of the ringing period of this cadence component. The possible values range from 0 to 5000. This value MUST be greater than RingingMinDuration" ::= { mgcoRingingCadenceGroupEntry 5 } mgcoRingingCadenceGroupRingingMaxDuration OBJECT-TYPE SYNTAX Integer32(0..5000) MAX-ACCESS read-create STATUS current DESCRIPTION "A value to indicate the maximum duration of the ringing period of this cadence component. The possible values range from 0 to 5000. This value MUST be greater than RingingNomDuration" ::= { mgcoRingingCadenceGroupEntry 6 } mgcoRingingCadenceGroupSilentMinDuration OBJECT-TYPE SYNTAX Integer32(0..5000) MAX-ACCESS read-create STATUS current DESCRIPTION "A value to indicate the minimum duration of the silent period of this cadence component. The possible values range from 0 to 5000" ::= { mgcoRingingCadenceGroupEntry 7 } Pitchandi Standards Track - Expires April 2003 [Page 10] Megaco Ringing MIB October 2002 mgcoRingingCadenceGroupSilentNomDuration OBJECT-TYPE SYNTAX Integer32(0..5000) MAX-ACCESS read-create STATUS current DESCRIPTION "A value to indicate the nominal duration of the silent period of this cadence component. The possible values range from 0 to 5000. This value MUST be greater than SilentMinDuration" ::= { mgcoRingingCadenceGroupEntry 8 } mgcoRingingCadenceGroupSilentMaxDuration OBJECT-TYPE SYNTAX Integer32(0..5000) MAX-ACCESS read-create STATUS current DESCRIPTION "A value to indicate the maximum duration of the silent period of this cadence component. The possible values range from 0 to 5000. This value MUST be greater than SilentNomDuration" ::= { mgcoRingingCadenceGroupEntry 9 } mgcoRingingCadenceGroupRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This is used to create new rows in this table, modify existing rows, and to delete rows." ::= { mgcoRingingCadenceGroupEntry 10 } -- ***************************************************************** -- -- Megaco-Ringing-MIB Notification Definitions -- -- There Are No Notifications at this time -- -- ***************************************************************** megacoRingingMIBNotifications OBJECT IDENTIFIER::= {megacoRingingMIB 2} mgcoRingingNotifPrefix OBJECT IDENTIFIER ::= { megacoRingingMIBNotifications 0 } mgcoRingingNotifObjects OBJECT IDENTIFIER ::= { megacoRingingMIBNotifications 1 } -- ***************************************************************** -- -- Conformance for the Megaco-Ringing-MIB Pitchandi Standards Track - Expires April 2003 [Page 11] Megaco Ringing MIB October 2002 -- -- ***************************************************************** megacoRingingConformance OBJECT IDENTIFIER ::= { megacoRingingMIB 3 } mgcoRingingCompliances OBJECT IDENTIFIER ::= { mgcoRingingConformance 1 } mgcoRingingConfGroups OBJECT IDENTIFIER ::= { mgcoRingingConformance 2 } -- Compliance mgcoRingingCompliances MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for entities which implement the Megaco Ringing Package MIB. " MODULE -- This module MANDATORY-GROUPS { mgcoRingingPatternSetGrp, mgcoRingingCadenceGroupGrp } ::= { mgcoRingingCompliances 1 } -- Units of Conformance mgcoRingingPatternSetGrp OBJECT-GROUP OBJECTS { mgcoRingingCadenceGroupId, mgcoRingingPatternName, mgcoRingingPatternRowStatus } STATUS current DESCRIPTION "Objects which implement Ringing Pattern Set Definition" ::= { mgcoRingingConfGroups 1 } mgcoRingingCadenceGroupGrp OBJECT-GROUP OBJECTS { mgcoRingingCadenceNextGroupId, mgcoRingingCadenceGroupName, mgcoRingingCadenceGroupRef, mgcoRingingCadenceGroupRingingMinDuration, Pitchandi Standards Track - Expires April 2003 [Page 12] Megaco Ringing MIB October 2002 mgcoRingingCadenceGroupRingingNomDuration, mgcoRingingCadenceGroupRingingMaxDuration, mgcoRingingCadenceGroupSilentMinDuration, mgcoRingingCadenceGroupSilentNomDuration, mgcoRingingCadenceGroupSilentMaxDuration, mgcoRingingCadenceGroupRowStatus } STATUS current DESCRIPTION "Objects which implement Ringing Cadence Group Characteristics Definition" ::= { mgcoRingingConfGroups 2 } END 3. Example Ringing MIB The MEGACO RINGING MIB Ringing parameters was designed based on the commonly accepted Bellcore Standard GR-506-CORE [20]. But the MIB can be used to represent other Ringing patterns as well. Examples of some ringing pattern are shown below (taken from [20]): +-----------+------------------------+ | Pattern | Cadence | +-----------+------------------------+ | 1 | 2 secs ON, 4 secs off | | 2 | Long - Long | | 3 | Short - Short - Long | | 4 | Short - Long - Short | | 5 | Short | +-----------+------------------------+ Example of MEGACO RINGING MIB populated with above ringing definitions is shown below: Note: The pattern names alert/ri, alert/cw and andisp/dwa is used in these examples. Other valid names may be used as required by the implementations. mgcoRingingPatternTable (Object names are abbreviated): +----------+----------------+---------------+-----------+ |PatternId | CadenceGroupId | PatternName | RowStatus | +----------+----------------+---------------+-----------+ | 1 | 2 | 'alert/ri' | 1(active) | | 2 | 5 | 'alert/cw' | 1(active) | | 3 | 6 | 'andisp/dwa' | 1(active) | +----------+----------------+---------------+-----------+ Pitchandi Standards Track - Expires April 2003 [Page 13] Megaco Ringing MIB October 2002 mgcoRingingCadenceGroupTable (Object names are abbreviated): +----+-----+-----+---+-------+-------+-------+-------+-------+-------+------+ |GrId|GrInd|Name |Ref|RgMnDur|RgNmDur|RgMxDur|SlMnDur|SlNmDur|SlMxDur|RwStat| +----+-----+-----+---+-------+-------+-------+-------+-------+-------+------+ | | | | | | | | | | | | | 1 | 1 | p1 | | 2000 | 2200 | 2400 | 3600 | 3800 | 4000 | 1 | | 2 | 1 |2son | | 1800 | 2000 | 2200 | 3600 | 4000 | 4400 | 1 | | 3 | 1 |ring1| | 200 | 400 | 600 | 140 | 180 | 200 | 1 | | 3 | 2 |ring2| | 530 | 700 | 925 | 215 | 300 | 425 | 1 | | 4 | 1 |pat3 | | 630 | 800 | 1025 | 315 | 400 | 525 | 1 | | 5 | 1 |long | 4 | | | | | | | 1 | | 5 | 2 |long | | 630 | 800 | 1025 | 3475 | 4000 | 4400 | 1 | | 6 | 1 |short| | 315 | 400 | 525 | 145 | 200 | 525 | 1 | | 6 | 2 |short| | 315 | 400 | 525 | 145 | 200 | 525 | 1 | | 6 | 3 |long | 5 | | | | | | | 1 | | 7 | 1 |burst| | 450 | 500 | 550 | | | | 1 | +----+-----+-----+---+-------+-------+-------+-------+-------+-------+------+ 4. Security Considerations In order to implement this MIB, a probe must capture all packets on the ocally-attached network, including packets between third parties. These packets are analyzed to collect network addresses, protocol usage information, and conversation statistics. Data of this nature may be considered sensitive in some environments. In such environments the administrator may wish to restrict SNMP access to the probe. This MIB also includes functions for returning the contents of captured packets, potentially including sensitive user data or passwords. It is recommended that SNMP access to these functions be restricted. There are a number of management objects defined in this MIB that have a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. SNMPv1 by itself is not a secure environment. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB. It is recommended that the implementors consider the security features as provided by the SNMPv3 framework. Specifically, the use of the User-based Pitchandi Standards Track - Expires April 2003 [Page 14] Megaco Ringing MIB October 2002 Security Model RFC 2574 [18] and the View- based Access Control Model RFC 2575 [17] is recommended. It is then a customer/user responsibility to ensure that the SNMP entity giving access to an instance of this MIB, is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET change/create/delete) them. References [2] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997 [3] Cuervo, F., Greene, N., Rayhan, A., Rosen, B., Segers, J., "Megaco Protocol Version 1.0", RFC 3015, November 2000 [4] ITU-T Recommendation H.248 (06/2000), "Gateway Control Protocol". [5] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999. [6] Rose, M. and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990. [7] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1212, March 1991. [8] Rose, M., "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991. [9] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [10] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [11] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [12] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, May 1990. [13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, [14] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol Operations Pitchandi Standards Track - Expires April 2003 [Page 15] Megaco Ringing MIB October 2002 for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996. [15] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction to Version 3 of the Internet-standard Network Management Framework", RFC 2570, April 1999. [16] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC 2573, April 1999. [17] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2575, April 1999. [18] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, April 1999. [19] Telcordia, "LSSGR: Voice Band Data Transmission", GR-30-CORE, Issue 2, December 1998 [20] Telcordia, "LSSGR: Signaling for Analog Interfaces", GR-506-CORE, Issue 1, June 1996 [21] Boyle et al, draft-boyle-megaco-alerting-03.txt, "Enhanced Alerting Packages for Megaco/H.248", March 2002 [22] ETSI, "Access and Terminals (AT); Analogue access to the Public Switched Telephone Network (PSTN); Subscriber line protocol over the local loop for display (and related) services; Part 1 : On- hook data transmission", EN 300 659-1, V1.3.1 (2000-09) Acknowledgments Several people from the Megaco Working group have contributed to the development of the Megaco Ringing MIB. Author's Addresses Bala Pitchandi UTStarcom Inc 33 Wood Avenue South Iselin, NJ USA 08830 Phone: (732) 452 4457 Email: bs@utstar.com Pitchandi Standards Track - Expires April 2003 [Page 16] Megaco Ringing MIB October 2002 Full Copyright Statement "Copyright (C) The Internet Society (2002). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." Pitchandi Standards Track - Expires April 2003 [Page 17]