[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 03 04 05 06 07 08 09 10 11 12 RFC 4780

SIP WG                                                         K. Lingle
Internet-Draft                                       Cisco Systems, Inc.
Expires: December 30, 2003                                      J. Maeng
                                                          ipDialog, Inc.
                                                               J-F. Mule
                                                               CableLabs
                                                               D. Walker
                                                      SS8 Networks, Inc.
                                                               July 2003


   Management Information Base for Session Initiation Protocol (SIP)
                       draft-ietf-sip-mib-07.txt

Status of this Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026.

   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.

   This Internet-Draft will expire on December 30, 2003.

Copyright Notice

   Copyright (C) The Internet Society (2003). All Rights Reserved.

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 describes a set of managed objects that are used to
   manage Session Initiation Protocol (SIP) entities, which include User
   Agents, Proxy servers, Redirect servers and Registrars.





Lingle, et al.         Expires December 30, 2003                [Page 1]

Internet-Draft              SIP MIB Modules                    July 2003


Table of Contents

   1.  Conventions  . . . . . . . . . . . . . . . . . . . . . . . .    3
   2.  Introduction . . . . . . . . . . . . . . . . . . . . . . . .    3
   3.  The Internet-Standard Management Framework . . . . . . . . .    3
   4.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . .    3
   5.  Structure of SIP MIB . . . . . . . . . . . . . . . . . . . .    3
   5.1 Textual Conventions  . . . . . . . . . . . . . . . . . . . .    6
   5.2 Relationship to the Network Services MIB . . . . . . . . . .    6
   6.  Accommodating SIP Extension Methods  . . . . . . . . . . . .   10
   7.  Definitions  . . . . . . . . . . . . . . . . . . . . . . . .   10
   7.1 SIP Textual Conventions  . . . . . . . . . . . . . . . . . .   10
   7.2 SIP Common MIB Module  . . . . . . . . . . . . . . . . . . .   12
   7.3 SIP User Agent MIB Module  . . . . . . . . . . . . . . . . .   73
   7.4 SIP Server (Registrar, Redirect & Proxy Server) MIB Module .   78
   8.  Changes from Previous Draft Revisions  . . . . . . . . . . .   98
   9.  Security Considerations  . . . . . . . . . . . . . . . . . .  108
   10. Contributor Acknowledgments  . . . . . . . . . . . . . . . .  112
       Normative References . . . . . . . . . . . . . . . . . . . .  112
       Informational References . . . . . . . . . . . . . . . . . .  113
       Authors' Addresses . . . . . . . . . . . . . . . . . . . . .  113
       Intellectual Property and Copyright Statements . . . . . . .  115





























Lingle, et al.         Expires December 30, 2003                [Page 2]

Internet-Draft              SIP MIB Modules                    July 2003


1. Conventions

   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 [1].

2. Introduction

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it describes a set of managed objects that are used to
   manage Session Initiation Protocol (SIP) entities, which include User
   Agents, Proxy servers, Redirect servers and Registrars.

3. The Internet-Standard Management Framework

   For a detailed overview of the documents that describe the current
   Internet-Standard Management Framework, please refer to section 7 of
   RFC 3410 [2]. Managed objects are accessed via a virtual information
   store, termed the Management Information Base or MIB.  MIB objects
   are generally accessed through the Simple Network Management Protocol
   (SNMP). Objects in the MIB are defined using the mechanisms defined
   in the Structure of Management Information (SMI).  This memo
   specifies a MIB module that is compliant to the SMIv2, which is
   described in STD 58, RFC 2578 [3], STD 58, RFC 2579 [4] and STD 58,
   RFC 2580 [5].

4. Overview

   The Session Initiation Protocol (SIP) RFC 3261 [7] is an application-
   layer control (signaling) protocol for creating, modifying, and
   terminating sessions with one or more participants. These sessions
   include Internet telephone calls, multimedia distribution, and
   multimedia conferences. This MIB provides some managed objects for
   SIP entities defined in RFC 3261 - User Agent, Proxy Server, Redirect
   Server and Registrar. It is provided as a base for the work within
   the working group to define a MIB. This MIB is intended to provide
   management of the basic SIP entities. It provides for monitoring of
   status and protocol statistics, as well as for configuration of SIP
   entities.

5. Structure of SIP MIB

   This memo specifies four MIB modules.  They are SIP-COMMON-MIB, SIP-
   SERVER-MIB, SIP-UA-MIB and SIP-TC.  SIP-COMMON-MIB contains common
   objects used in all the SIP entities. SIP-SERVER-MIB contains objects
   specific to Registrars, Proxies and Redirect Servers, and SIP-UA-MIB
   includes objects specific to User Agents.  SIP-TC defines the textual



Lingle, et al.         Expires December 30, 2003                [Page 3]

Internet-Draft              SIP MIB Modules                    July 2003


   conventions used throughout MIB modules. The MIB Modules contain
   following groups of objects:

   SIP-COMMON-MIB: Common to all the SIP entities

   o  sipCommonMIBObjects

      *  sipCommonCfgBase: This object group defines configuration
         objects common to all SIP entities including SIP protocol
         version, operational and administrative status, SIP
         organization name, max number of SIP sessions an entity can
         manage, etc.

      *  sipCommonCfgTimer: This object group defines timer
         configuration objects applicable to SIP user agent and SIP
         stateful proxy entities.

      *  sipCommonCfgRetry: This object group defines retry counter
         configuration objects applicable to SIP user agent and SIP
         stateful proxy entities.

      *  sipCommonCfgExpires: This object group defines Expires header
         value configuration objects applicable to SIP user agent and
         SIP stateful proxies

      *  sipCommonStatsSummary: This object group defines a table
         containing the summary statistics objects applicable to all SIP
         entities, including the total number of SIP requests &
         responses in/out, total number of transactions, etc.

      *  sipCommonStatsMethod: This object group defines a table
         containing the per method statistics objects applicable to all
         SIP entities, including the total number of SIP requests for
         the Invite, Ack, Bye, Cancel, Options and /Register methods.

      *  sipCommonStatusCode: This object group defines a table
         indicating the number of SIP responses in/out per class of
         response (1xx, 2xx, etc.)

      *  sipCommonStatsTrans: This object group defines a table
         containing a gauge reflecting the number of transactions
         currently awaiting definitive responses by the managed SIP
         entity.

      *  sipCommonStatsRetry: This object group defines statistic
         objects indicating the number of retries sent on a per method
         basis.




Lingle, et al.         Expires December 30, 2003                [Page 4]

Internet-Draft              SIP MIB Modules                    July 2003


      *  sipCommonStatsOther: This object group defines additional
         statistic objects including a counter of the number of SIP
         requests received with unsupported URIs.

      *  sipCommonNotifObjects: This object group defines
         accessible-for-notify objects that are relate to the SNMP
         notifications defined in this MIB module.

   The SIP-COMMON-MIB also contains notifications, including:

   o  sipStatusCodeNotif: indicates that a specific status code has been
      sent or received by the system.

   o  sipStatusCodeThreshExceededNotif: indicates that a specific status
      code has been sent or received by the system enough to exceed the
      configured threshold.

   SIP-SERVER-MIB: Groups of objects for Registrars, Proxy and Redirect
   Servers

   o  sipServerMIBObjects

      *  sipServerCfg: This object group defines common server
         configuration objects including the SIP server host address.

      *  sipServerStats: This object group is currently empty and is
         created for future extensions of the SIP MIB.

      *  sipProxyCfg: This object group defines Proxy Server
         configuration objects including the maximum duration in the
         Expires header, the proxy mode of operation (stateless,
         stateful, call stateful), the cancellation of outstanding
         branch requests

      *  sipProxyStats: This object group defines a table containing the
         statistics objects applicable to all SIP Proxy Servers.  It
         includes the number of occurrences of unsupported options being
         specified in received Proxy-Require headers.

      *  sipRedirCfg: This object group is currently empty and is
         created for future extensions of the SIP MIB.

      *  sipRedirStats: This object group is currently empty and is
         created for future extensions of the SIP MIB.

      *  sipRegCfg: This object group is currently empty and is created
         for future extensions of the SIP MIB.




Lingle, et al.         Expires December 30, 2003                [Page 5]

Internet-Draft              SIP MIB Modules                    July 2003


      *  sipRegStats: This object group is currently empty and is
         created for future extensions of the SIP MIB.

   SIP-UA-MIB: Group of objects for User Agents.

   o  sipUAMIBObjects

      *  sipUACfgSipServer: This group specifies SIP server
         configuration objects applicable to SIP user agents including
         the Internet address of the SIP Server to use to proxy or
         redirect calls.

   To conform with this specification, an SNMP agent MUST implement
   SIP-TC, plus the SIP-COMMON-MIB and one of the SIP entity-type-
   specific MIB modules (SIP-SERVER-MIB or SIP-UA-MIB) as applicable for
   each instance of a SIP entity being managed.  If a device has more
   than one SIP entity or multiple instances of the same entity, type it
   MUST implement multiple SIP modules. Section 4.2 describes handling
   of multiple instances in detail.

5.1 Textual Conventions

   The data type SipTransportProtocol is used as Textual Conventions in
   this document.  These Textual Conventions have NO effect on either
   the syntax or the semantics of any managed object.  Objects defined
   using these conventions are always encoded by means of the rules that
   define their primitive type.  Hence, no changes to the SMI or the
   SNMP are necessary to accommodate these Textual Conventions. They are
   adopted merely for the convenience of readers.

5.2 Relationship to the Network Services MIB

   There is a requirement to be able to support multiple instances of
   various SIP MIB modules in the context of a single system having a
   single SNMP agent.

   This requirement is solved by using the framework provided by the
   NETWORK-SERVICES-MIB, RFC 2788 [6]. A device implementing the SIP MIB
   MUST support the NETWORK-SERVICES-MIB and, at a minimum, it MUST
   support the applIndex and applName objects in applTable.  The
   following applName conventions will be adopted:

   o  for a SIP Proxy entity, applName MUST be equal to "sip_proxy"

   o  for a SIP Redirect entity, applName MUST be equal to
      "sip_redirect"

   o  for a SIP Registrar entity, applName MUST be equal to



Lingle, et al.         Expires December 30, 2003                [Page 6]

Internet-Draft              SIP MIB Modules                    July 2003


      "sip_registrar"

   o  for a SIP User Agent entity, applName MUST be equal to "sip_ua"

   o  for any combination of Proxy, Registrar, or Redirect Server being
      managed as a single aggregate entity, the applName for the
      combined server entity MUST reflect the appropriate combination.
      For example, "sip_proxy_redirect" or "sip_proxy_registrar".

   The SNMP agent MAY support any combination of the other attributes in
   applTable.  If the following objects are supported, the object values
   SHOULD be populated as follows:

   o  applVersion: version of the SIP application.

   o  applUptime: value MUST be identical to sipServiceStartTime defined
      in the SIP-COMMON-MIB module,

   o  applOperStatus: value SHOULD reflect the operational status
      defined in sipServiceOperStatus, at least by means of a mapping,

   o  applLastChange: value MUST be identical to sipServiceLastChange
      defined in the SIP-COMMON module.

   Note: There are a number of other objects in the applTable.  They are
   not included for the sake of brevity and for the fact that they do
   not enhance the concept being presented.

   Example 1:

   The tables below illustrate how a system acting as both Proxy and
   Registrar server might be configured to maintain separate SIP-
   COMMON-MIB instances.

   The NETWORK-SERVICES-MIB applTable might be populated as follows:

         +-----------+-----------------+----------------------+
         | applIndex |     applName    |    applDescription   |
         +-----------+-----------------+----------------------+
         |     1     |   "sip_proxy"   |   "ACME SIP Proxy"   |
         |     2     | "sip_registrar" | "ACME SIP Registrar" |
         +-----------+-----------------+----------------------+

   The SIP-COMMON-MIB sipCommonCfgTable would have two rows: one for the
   proxy (applIndex=1) and one for the registrar (applIndex=2). The
   SIP-SERVER-MIB tables would, however, only be populated with one row
   indexed by applIndex=1 and applIndex=2 respectively if the server
   provides either proxy or registrar.



Lingle, et al.         Expires December 30, 2003                [Page 7]

Internet-Draft              SIP MIB Modules                    July 2003


   SIP-COMMON-MIB sipCommonCfgTable might be populated as:

    +-----------+---------------------+----------------------+-----+
    | applIndex | sipProtocolVerfsion | sipServiceOperStatus | ... |
    +-----------+---------------------+----------------------+-----+
    |     1     |      "SIP/2.0"      |         up(1)        |     |
    |     2     |      "SIP/2.0"      |     restarting(4)    |     |
    +-----------+---------------------+----------------------+-----+

   while sipProxyCfgTable in SIP-SERVER-MIB might be populated as:

   +-----------+----------------------+----------------------+-----+
   | applIndex | sipRequestMaxExpires | sipProxyStatefulness | ... |
   +-----------+----------------------+----------------------+-----+
   |     1     |         3600         |     stateless(1)     |     |
   +-----------+----------------------+----------------------+-----+

   and sipRegUserTable in SIP-SERVER-MIB might be populated as:

        +-----------+--------------+---------------------+-----+
        | applIndex | sipUserIndex |      sipUserUri     | ... |
        +-----------+--------------+---------------------+-----+
        |     2     |       1      |   drwalker@ss8.com  |     |
        |     2     |       2      | jmaeng@ipdialog.com |     |
        |     2     |       3      |  klingle@cisco.com  |     |
        |     2     |       4      |  jfm@cablelabs.com  |     |
        +-----------+--------------+---------------------+-----+

   Example 2:

   This example illustrates how to represent a system acting as both
   Proxy and Registrar server, where the two entities share a single
   instance of SIP-COMMON-MIB.

   The NETWORK-SERVICES-MIB applTable might be populated as follows:

  +-----------+-----------------------+------------------------------+
  | applIndex |        applName       |        applDescription       |
  +-----------+-----------------------+------------------------------+
  |     1     | "sip_proxy_registrar" | "ACME SIP Proxy & Registrar" |
  +-----------+-----------------------+------------------------------+

   The SIP-COMMON-MIB sipCommonCfgTable would have only one row to cover
   both the proxy and the registrar.







Lingle, et al.         Expires December 30, 2003                [Page 8]

Internet-Draft              SIP MIB Modules                    July 2003


   SIP-COMMON-MIB sipCommonCfgTable might be populated as:

       +-----------+--------------------+----------------------+
       | applIndex | sipProtocolVersion | sipServiceOperStatus |
       +-----------+--------------------+----------------------+
       |     1     |      "SIP/2.0"     |         up(1)        |
       +-----------+--------------------+----------------------+

   while sipProxyCfgTable in SIP-SERVER-MIB is populated as:

      +-----------+----------------------+----------------------+
      | applIndex | sipMaxRequestExpires | sipProxyStatefulness |
      +-----------+----------------------+----------------------+
      |     1     |         3600         |     stateless(1)     |
      +-----------+----------------------+----------------------+

   and sipRegUserTable in SIP-SERVER-MIB might be populated as:

        +-----------+--------------+---------------------+-----+
        | applIndex | sipUserIndex |      sipUserUri     | ... |
        +-----------+--------------+---------------------+-----+
        |     2     |       1      |   drwalker@ss8.com  |     |
        |     2     |       2      | jmaeng@ipdialog.com |     |
        |     2     |       3      |  klingle@cisco.com  |     |
        |     2     |       4      |  jfm@cablelabs.com  |     |
        +-----------+--------------+---------------------+-----+

   The NETWORK-SERVICES-MIB assocTable is not considered a requirement
   for SIP systems.  It is not a mandatory group for NETWORK-SERVICES-
   MIB compliance.

   The relationship between the value of applOperStatus and
   sipServiceOperStatus is as follows:

  +----------------------+-----------------------+-------------------+
  | sipServiceOperStatus | -- corresponds to --> |   applOperstatus  |
  +----------------------+-----------------------+-------------------+
  |          up          |          -->          |         up        |
  |         down         |          -->          |        down       |
  |       congested      |          -->          |     congested     |
  |      restarting      |          -->          |     restarting    |
  |       quiescing      |          -->          |     quiescing     |
  |        testing       |          -->          |         up        |
  |        unknown       |          -->          | --indeterminate-- |
  +----------------------+-----------------------+-------------------+

   If the sipOperStatus is 'unknown' there is no corresponding value of
   applOperStatus.  Therefore, the last known value of applOperStatus



Lingle, et al.         Expires December 30, 2003                [Page 9]

Internet-Draft              SIP MIB Modules                    July 2003


   SHOULD be maintained until the sipOperStatus transitions to a value
   that can be mapped appropriately.

6. Accommodating SIP Extension Methods

   The core set of SIP methods is defined in RFC 3261 [7].  Other
   Internet- Draft documents and RFCs define additional methods.  In the
   future more methods may be defined.  In order to avoid having to
   update the SIP-COMMON-MIB module to accommodate these extension
   methods, there are various extension method tables throughout the MIB
   module. There are no per method objects defined in the other MIB
   modules.

   The sipExtMethodSupportedTable is the main table for listing all of
   the extension methods supported by a system.  The table is
   informational in nature and populated by the system.  Entries cannot
   be added or deleted by a SNMP manager.  The other extension method
   tables in the MIB are augmentations of this table.

   The other extension method tables defined in the SIP-COMMON-MIB are:
   sipCommonCfgTimerExtMethodTable, sipCommonCfgRetryExtMethodTable,
   sipStatsExtMethodTable, and sipCommonStatsRetryExtMethodTable.

7. Definitions

7.1 SIP Textual Conventions

      SIP-TC DEFINITIONS ::= BEGIN

      IMPORTS
           MODULE-IDENTITY,
           mib-2
                FROM SNMPv2-SMI

           TEXTUAL-CONVENTION
                FROM SNMPv2-TC;

      sipTC MODULE-IDENTITY
           LAST-UPDATED   "200307300000Z"
           ORGANIZATION   "IETF SIP Working Group, SIP MIB Team"
           CONTACT-INFO
                   "SIP WG email: sip@ietf.org

                    Co-editor  Kevin Lingle
                               Cisco Systems, Inc.
                    postal:    7025 Kit Creek Road
                               P.O. Box 14987
                               Research Triangle Park, NC 27709



Lingle, et al.         Expires December 30, 2003               [Page 10]

Internet-Draft              SIP MIB Modules                    July 2003


                               USA
                    email:     klingle@cisco.com
                    phone:     +1 919 392 2029

                    Co-editor  Joon Maeng
                               ipDialog, Inc.
                    postal:    7701 N. Lamar Blvd., Suite 304
                               Austin, TX 78752-1023
                               USA
                    email:     jmaeng@ipdialog.com
                    phone:     +1 512 371 1770

                    Co-editor  Dave Walker
                               SS8 Networks, Inc.
                    postal:    495 March Road
                               Kanata, ON K2K 3G1
                               Canada
                    email:     drwalker@ss8.com
                    phone:     +1 613 592 2100

                    Co-editor  Jean-Francois Mule
                               CableLabs
                    postal:    400 Centennial Parkway
                               Louisville, CO 80027
                               USA
                    email:     jf.mule@cablelabs.com
                    phone:     +1 303 661 3708  "
           DESCRIPTION
                "Session Initiation Protocol (SIP) MIB Textual
                 Conventions module used by other SIP-related
                 MIB Modules.

                 Copyright (C) The Internet Society (2003). This version
                 of this MIB module is part of RFC XXXX; see the RFC
                 itself for full legal notices."
   -- RFC Ed: replace XXXX with actual RFC number and remove this note
           REVISION        "200307300000Z"
           DESCRIPTION
                "Initial version of the IETF SIP-TC module.
                 This version published as part of RFC XXXX."
   -- RFC Ed: replace XXXX with actual RFC number and remove this note
           ::= { mib-2 xx }
   -- RFC Ed: replace xx with actual IANA assigned number and remove this note

      --
      -- Textual Conventions
      --




Lingle, et al.         Expires December 30, 2003               [Page 11]

Internet-Draft              SIP MIB Modules                    July 2003


      SipTransportProtocol ::= TEXTUAL-CONVENTION
              STATUS current
              DESCRIPTION
                   "This convention is a bit map.  Each bit represents a
                    transport protocol.  If a bit has value 1, then that
                    selected transport protocol is in some way dependent
                    on the context of the object using this convention.
                    If a bit has value 0, then that transport protocol
                    is not selected.  Combinations of bits can be
                    set when multiple transport protocols are selected.

                    bit 0   : a protocol other than those defined here.
                    bit 1   : User Datagram Protocol.
                    bit 2   : Transmission Control Protocol.
                    bit 3   : Stream Control Transmission Protocol.
                    bit 4   : Transport Layer Security Protocol."
              SYNTAX     BITS {
                               other(0),  -- none of the following
                               udp(1),
                               tcp(2),
                               sctp(3),
                               tls(4)
              }
   --         REFERENCE "RFC 3261, Section 18"
      END


7.2 SIP Common MIB Module

     SIP-COMMON-MIB DEFINITIONS ::= BEGIN

      IMPORTS
           MODULE-IDENTITY,
           OBJECT-TYPE,
           NOTIFICATION-TYPE,
           Counter32,
           Gauge32,
           TimeTicks,
           Unsigned32,
           mib-2
                FROM SNMPv2-SMI

           RowStatus,
           TruthValue
                FROM SNMPv2-TC
           MODULE-COMPLIANCE,

           OBJECT-GROUP,



Lingle, et al.         Expires December 30, 2003               [Page 12]

Internet-Draft              SIP MIB Modules                    July 2003


           NOTIFICATION-GROUP
                FROM SNMPv2-CONF

           SnmpAdminString
                FROM SNMP-FRAMEWORK-MIB

           SipTransportProtocol
                FROM SIP-TC

           applIndex
                FROM NETWORK-SERVICES-MIB

           InetPortNumber
                FROM INET-ADDRESS-MIB;

      sipCommonMIB MODULE-IDENTITY
           LAST-UPDATED   "200307300000Z"
           ORGANIZATION   "IETF SIP Working Group, SIP MIB Team"
           CONTACT-INFO
                   "SIP WG email: sip@ietf.org

                    Co-editor  Kevin Lingle
                               Cisco Systems, Inc.
                    postal:    7025 Kit Creek Road
                               P.O. Box 14987
                               Research Triangle Park, NC 27709
                               USA
                    email:     klingle@cisco.com
                    phone:     +1 919 392 2029

                    Co-editor  Joon Maeng
                               ipDialog, Inc.
                    postal:    7701 N. Lamar Blvd., Suite 304
                               Austin, TX 78752-1023
                               USA
                    email:     jmaeng@ipdialog.com
                    phone:     +1 512 371 1770

                    Co-editor  Dave Walker
                               SS8 Networks, Inc.
                    postal:    495 March Road
                               Kanata, ON K2K 3G1
                               Canada
                    email:     drwalker@ss8.com
                    phone:     +1 613 592 2100

                    Co-editor  Jean-Francois Mule
                               CableLabs



Lingle, et al.         Expires December 30, 2003               [Page 13]

Internet-Draft              SIP MIB Modules                    July 2003


                    postal:    400 Centennial Parkway
                               Louisville, CO 80027
                               USA
                    email:     jf.mule@cablelabs.com
                    phone:     +1 303 661 3708  "
           DESCRIPTION
                "Session Initiation Protocol (SIP) Common MIB module.
                 This module defines objects which MAY be common to all
                 SIP entities.

                 SIP is an application-layer signalling protocol for
                 creating, modifying and terminating multimedia
                 sessions with one or more participants. These sessions
                 include Internet multimedia conferences and Internet
                 telephone calls.  SIP is defined in RFC 3261 (June
                 2002).

                 This MIB is defined for managing objects which are
                 common to SIP User Agents (UAs), Proxy and Redirect
                 Servers, and Registrars.  Objects specific to each of
                 these entities MAY be managed using entity specific
                 MIBs defined in other modules.

                 A User Agent is an application that contains both a
                 User Agent Client (UAC) and a User Agent Server (UAS).
                 A UAC is an application that initiates a SIP request.
                 A UAS is an application that contacts the user when a
                 SIP request is received and that returns a response on
                 behalf of the user.  The response accepts, rejects, or
                 redirects the request.

                 A Proxy Server acts as both a client and a server.
                 It accepts requests from other clients, either
                 responding to them or passing them on to other
                 servers, possibly after modification.

                 A Redirect Server accepts requests from clients and
                 returns zero or more addresses to that client. Unlike
                 a Proxy Server it does not initiate requests.  Unlike
                 a User Agent Server it does not accept calls.

                 A Registrar Server accepts REGISTER requests.
                 A Registrar Server is typically co-located with a
                 Proxy or Redirect Server.

                 Copyright (C) The Internet Society (2003). This version
                 of this MIB module is part of RFC XXXX; see the RFC
                 itself for full legal notices."



Lingle, et al.         Expires December 30, 2003               [Page 14]

Internet-Draft              SIP MIB Modules                    July 2003


   -- RFC Ed: replace XXXX with actual RFC number and remove this note
           REVISION        "200307300000Z"
           DESCRIPTION
                "Initial version of the IETF SIP-COMMON-MIB module.
                 This version published as part of RFC XXXX."
   -- RFC Ed: replace XXXX with actual RFC number and remove this note
           ::= { mib-2 xx  }
   -- RFC Ed: replace xx with actual IANA assigned number and remove this note

      -- Top-Level Components of this MIB.
      sipCommonMIBNotifs     OBJECT IDENTIFIER ::= { sipCommonMIB 0 }
      sipCommonMIBObjects    OBJECT IDENTIFIER ::= { sipCommonMIB 1 }
      sipCommonMIBConform    OBJECT IDENTIFIER ::= { sipCommonMIB 2 }

      --
      -- This MIB contains objects that are common to all SIP entities.
      --

      -- Common basic configuration
      sipCommonCfgBase       OBJECT IDENTIFIER ::= { sipCommonMIBObjects 1 }
      -- Protocol timer configuration
      sipCommonCfgTimer      OBJECT IDENTIFIER ::= { sipCommonMIBObjects 2 }
      -- Method retry configuration
      sipCommonCfgRetry      OBJECT IDENTIFIER ::= { sipCommonMIBObjects 3 }
      -- Expires header configuration
      sipCommonCfgExpires    OBJECT IDENTIFIER ::= { sipCommonMIBObjects 4 }
      -- SIP message summary statistics
      sipCommonStatsSummary  OBJECT IDENTIFIER ::= { sipCommonMIBObjects 5 }
      -- Per method statistics
      sipCommonStatsMethod   OBJECT IDENTIFIER ::= { sipCommonMIBObjects 6 }
      -- Per Status code or status code class statistics
      sipCommonStatusCode    OBJECT IDENTIFIER ::= { sipCommonMIBObjects 7 }
      -- Transaction statistics
      sipCommonStatsTrans    OBJECT IDENTIFIER ::= { sipCommonMIBObjects 8 }
      -- Method retry statistics
      sipCommonStatsRetry    OBJECT IDENTIFIER ::= { sipCommonMIBObjects 9 }
      -- Other statistics
      sipCommonStatsOther    OBJECT IDENTIFIER ::= { sipCommonMIBObjects 10 }
      -- Accessible-for-notify objects
      sipCommonNotifObjects  OBJECT IDENTIFIER ::= { sipCommonMIBObjects 11 }

      --
      -- Common Configuration Objects
      --
      sipCommonCfgTable OBJECT-TYPE
          SYNTAX     SEQUENCE OF SipCommonCfgEntry
          MAX-ACCESS not-accessible
          STATUS     current



Lingle, et al.         Expires December 30, 2003               [Page 15]

Internet-Draft              SIP MIB Modules                    July 2003


          DESCRIPTION
               "This table contains the common configuration objects
                applicable to all SIP entities."
          ::= { sipCommonCfgBase 1 }

      sipCommonCfgEntry OBJECT-TYPE
          SYNTAX     SipCommonCfgEntry
          MAX-ACCESS not-accessible
          STATUS     current
          DESCRIPTION
               "A row of common configuration.

                Each row represents objects for a particular SIP
                entity instance present in this system.  applIndex
                is used to uniquely identify these instances of SIP
                entities and correlate them through the common
                framework of the NETWORK-SERVICES-MIB (RFC 2788)."
          INDEX { applIndex }
          ::= { sipCommonCfgTable 1 }

      SipCommonCfgEntry ::=
          SEQUENCE {
                   sipProtocolVersion        SnmpAdminString,
                   sipServiceOperStatus      INTEGER,
                   sipServiceAdminStatus     INTEGER,
                   sipServiceStartTime       TimeTicks,
                   sipServiceLastChange      TimeTicks,
                   sipOrganization           SnmpAdminString,
                   sipMaxSessions            Unsigned32,
                   sipRequestUriHostMatching TruthValue,
                   sipServiceNotifEnable     BITS,
                   sipEntityType             INTEGER
          }

      sipProtocolVersion OBJECT-TYPE
          SYNTAX      SnmpAdminString
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object will reflect the version of SIP supported by
                this SIP entity.  It will follow the same format as SIP
                version information contained in the SIP messages
                generated by this SIP entity.  For example, entities
                supporting SIP version 2 will return 'SIP/2.0' as dictated
                by the standard."
          REFERENCE
                "RFC 3261, Section 7.1"
          ::= { sipCommonCfgEntry 1 }



Lingle, et al.         Expires December 30, 2003               [Page 16]

Internet-Draft              SIP MIB Modules                    July 2003


     sipServiceOperStatus OBJECT-TYPE
          SYNTAX     INTEGER {
                             unknown(1),
                             up(2),
                             down(3),
                             congested(4),
                             restarting(5),
                             quiescing(6),
                             testing(7)
                     }
          MAX-ACCESS read-only
          STATUS     current
          DESCRIPTION
               "This object contains the current operational state of the
                SIP application.

                unknown    : The operational status cannot be determined
                             for some reason.
                up         : The application is operating normally, and
                             is processing (receiving and possibly
                             issuing) SIP requests and responses.
                down       : The application is currently unable to
                             process SIP messages.
                congested  : The application is operational but no
                             additional inbound transactions can be
                             accommodated at the moment.
                restarting : The application is currently unavailable
                             but it is in the process of restarting and
                             will, presumably, soon be able to process
                             SIP messages.
                quiescing  : The application is currently operational
                             but has been administratively put into
                             quiesce mode.  Additional inbound transactions
                             MAY be rejected.
                testing    : The application is currently in test mode
                             and MAY not be able to process SIP messages.

                The operational status values defined for this object are
                not based on any specific information contained in the SIP
                standard."
          ::= { sipCommonCfgEntry 2 }

      sipServiceAdminStatus OBJECT-TYPE
          SYNTAX     INTEGER {
                             noop(1),
                             up(2),
                             down(3),
                             reset(4),



Lingle, et al.         Expires December 30, 2003               [Page 17]

Internet-Draft              SIP MIB Modules                    July 2003


                             quiesceSessions(5),
                             quiesceApplication(6)
                     }
          MAX-ACCESS read-write
          STATUS     current
          DESCRIPTION
               "This object is used to affect the overall operational
                state of the SIP application.  When read, this object
                always return a value of noop(1) since sipServiceOperStatus
                reflects the actual operational status.

                noop               : Setting this object to a noop value
                                     has no effect; when read, this value
                                     is always returned.
                up                 : Enable the application.
                down               : Abrupt shutdown. Immediately terminate.
                reset              : Restart application, reinitialize data.
                quiesceSessions    : Enable quiescence mode.  Stop accepting
                                     any new SIP sessions. Stop processing
                                     new transactions except for transactions
                                     associated with an existing session or
                                     call.
                quiesceApplications : Enable quiescence mode. Stop processing
                                     new SIP transactions except for
                                     transactions associated with existing
                                     applications. The exact application
                                     behavior SHOULD be specified by the
                                     implementation."
          ::= { sipCommonCfgEntry 3 }

      sipServiceStartTime OBJECT-TYPE
          SYNTAX     TimeTicks
          MAX-ACCESS read-only
          STATUS     current
          DESCRIPTION
               "The value of sysUpTime at the time the SIP entity was last
                started. If started prior to the last re-initialization of
                the local network management subsystem, then this object
                contains a zero value."
          ::= { sipCommonCfgEntry 4 }

      sipServiceLastChange OBJECT-TYPE
          SYNTAX     TimeTicks
          MAX-ACCESS read-only
          STATUS     current
          DESCRIPTION
               "The value of sysUpTime at the time the SIP entity entered
                its current operational state.  If the current state was



Lingle, et al.         Expires December 30, 2003               [Page 18]

Internet-Draft              SIP MIB Modules                    July 2003


                entered prior to the last re-initialization of the local
                network management subsystem, then this object contains a
                zero value."
          ::= { sipCommonCfgEntry 5 }

      sipOrganization OBJECT-TYPE
          SYNTAX     SnmpAdminString
          MAX-ACCESS read-write
          STATUS     current
          DESCRIPTION
               "This object contains the organization name which the SIP
                entity inserts into Organization headers of SIP messages
                processed by this system.  If the string is empty, no
                Organization header is to be generated."
          REFERENCE
                "RFC 3261, Section 20.25"
          ::= { sipCommonCfgEntry 6 }

      sipMaxSessions OBJECT-TYPE
          SYNTAX     Unsigned32 (1..4294967295)
          MAX-ACCESS read-only
          STATUS     current
          DESCRIPTION
               "This object indicates the maximum number of simultaneous
                sessions that the SIP entity can manage."
          ::= { sipCommonCfgEntry 7 }

      sipRequestUriHostMatching OBJECT-TYPE
          SYNTAX     TruthValue
          MAX-ACCESS read-write
          STATUS     current
          DESCRIPTION
               "This object specifies whether or not the host in
                RequestURI MUST match server's host name.

                If the value of this object is 'true', then the server
                requires a match, and if the RequestURI doesn't match the
                server's host name, a Location Service MAY be used to
                obtain information about a callee's possible location(s)
                or a 404 Not Found status code is returned by the server.
                If the value is 'false', then no match is required."
          REFERENCE
               "RFC 3261, Section 8.1.1.1"
          ::= { sipCommonCfgEntry 8 }

      sipServiceNotifEnable OBJECT-TYPE
          SYNTAX     BITS {
                           sipServiceColdStart(0),



Lingle, et al.         Expires December 30, 2003               [Page 19]

Internet-Draft              SIP MIB Modules                    July 2003


                           sipServiceWarmStart(1),
                           sipServiceStatusChanged(2)
          }
          MAX-ACCESS read-write
          STATUS     current
          DESCRIPTION
               "This object specifies which SIP service related
                notifications are enabled.   Each bit represents
                a specific notification.  If a bit has a value 1,
                the associated notification is enabled and will
                be generated by the SIP entity at the approriate
                time.  The notifications are OPTIONAL, and if they
                are not implemented this object's value has no
                meaning and MUST be 0.  Setting this object in that
                circumstance SHOULD result in a badValue error.
                If notifications are supported, this object's default
                value SHOULD reflect sipServiceColdStart and
                sipServiceWarmStart enabled and sipServiceStatusChanged
                disabled."
          ::= { sipCommonCfgEntry 9 }

       sipEntityType OBJECT-TYPE
          SYNTAX     INTEGER {
                              unknown(1),
                              userAgent(2),
                              proxyServer(3),
                              redirectServer(4),
                              proxyRedirectServer(5),
                              registrar(6)
          }
          MAX-ACCESS read-only
          STATUS     current
          DESCRIPTION
               "This object reflects the type of SIP entity
                this row if related to."
          ::= { sipCommonCfgEntry 10 }


      --
      -- Support for multiple ports
      --
      sipPortTable OBJECT-TYPE
          SYNTAX     SEQUENCE OF SipPortEntry
          MAX-ACCESS not-accessible
          STATUS     current


          DESCRIPTION



Lingle, et al.         Expires December 30, 2003               [Page 20]

Internet-Draft              SIP MIB Modules                    July 2003


               "This table contains the list of ports that each SIP entity
                in this system is allowed to use.  These ports can be
                advertised using the Contact header in a REGISTER request
                or response."
          ::= { sipCommonCfgBase 2 }

      sipPortEntry OBJECT-TYPE
          SYNTAX     SipPortEntry
          MAX-ACCESS not-accessible
          STATUS     current
          DESCRIPTION
               "Specification of a particular port.

                Each row represents those objects for a particular SIP
                entity present in this system.  applIndex is used to
                uniquely identify these instances of SIP entities and
                correlate them through the common framework of the
                NETWORK-SERVICES-MIB (RFC 2788)."
          INDEX { applIndex, sipPort }
          ::= { sipPortTable 1 }

      SipPortEntry ::=
          SEQUENCE {
                   sipPort                 InetPortNumber,
                   sipTransportRcv         SipTransportProtocol,
                   sipTransportSnd         SipTransportProtocol,
                   sipPortStatus           RowStatus
          }

      sipPort OBJECT-TYPE
          SYNTAX     InetPortNumber
          MAX-ACCESS not-accessible
          STATUS     current
          DESCRIPTION
               "This object reflects a particular port that can be used by
                the SIP application."
          ::= { sipPortEntry 1 }

      sipTransportRcv OBJECT-TYPE
          SYNTAX     SipTransportProtocol
          MAX-ACCESS read-create
          STATUS     current
          DESCRIPTION
               "This object will specify the transport protocol the SIP
                entity will use to receive SIP messages.

                This object is a bit map.  Each bit represents a transport
                protocol.  If a bit has value 1, then that transport protocol



Lingle, et al.         Expires December 30, 2003               [Page 21]

Internet-Draft              SIP MIB Modules                    July 2003


                is currently being used.  If a bit has value 0, then that
                transport protocol is currently not being used."
          ::= { sipPortEntry 2 }

      sipTransportSnd OBJECT-TYPE
          SYNTAX     SipTransportProtocol
          MAX-ACCESS read-create
          STATUS     current


          DESCRIPTION
               "This object will specify the transport protocol the SIP
                entity will use to send SIP messages.

                This object is a bit map.  Each bit represents a transport
                protocol.  If a bit has value 1, then that transport protocol
                is currently being used.  If a bit has value 0, then that
                transport protocol is currently not being used."
          ::= { sipPortEntry 3 }

      sipPortStatus OBJECT-TYPE
          SYNTAX     RowStatus
          MAX-ACCESS read-create
          STATUS     current
          DESCRIPTION
               "The row status of the entry. This object is REQUIRED to
                create or delete rows by a manager.  The row
                associated with port 5060 need not be created and cannot
                be deleted.  It is always present in the table.  It is
                implementation specific as to whether objects in this table
                can be set while a row is 'active'."
          ::= { sipPortEntry 4 }


      --
      -- Support for multiple non-SIP URI schemes
      --
      sipUriSupportedTable OBJECT-TYPE
          SYNTAX     SEQUENCE OF SipUriSupportedEntry
          MAX-ACCESS not-accessible
          STATUS     current
          DESCRIPTION
               "This table contains a list of URI schemes supported by each
                SIP entity in this system. These are in addition to the SIP
                URI which MUST necessarily be supported.  Normally the
                list of URI schemes supported by an entity is static
                (i.e. will not change over time).




Lingle, et al.         Expires December 30, 2003               [Page 22]

Internet-Draft              SIP MIB Modules                    July 2003


                A URI is a Uniform Resource Identifier (as defined in RFC
                2396).

                URI schemes could, for example, contain URLs for phones, fax,
                or irc (if they were defined) or a mailto: (RFC 2368) URL."
          REFERENCE
                "RFC 3261, Section 20.10"
          ::= { sipCommonCfgBase 3 }

      sipUriSupportedEntry OBJECT-TYPE
          SYNTAX     SipUriSupportedEntry
          MAX-ACCESS not-accessible
          STATUS     current
          DESCRIPTION
               "A particular non-SIP URI supported by the SIP entity.

                Each row represents those objects for a particular SIP
                entity present in this system.  applIndex is used to
                uniquely identify these instances of SIP entities and
                correlate them through the common framework of the
                NETWORK-SERVICES-MIB (RFC 2788).
                The objects in this table entry SHOULD be non-volatile
                and their value SHOULD be kept at reboot."
          INDEX { applIndex, sipUriSupportedIndex }
          ::= { sipUriSupportedTable 1 }

      SipUriSupportedEntry ::=
          SEQUENCE {
                   sipUriSupportedIndex           Unsigned32,
                   sipUriSupported                SnmpAdminString
          }

      sipUriSupportedIndex OBJECT-TYPE
          SYNTAX     Unsigned32 (1..4294967295)
          MAX-ACCESS not-accessible
          STATUS     current
          DESCRIPTION
               "This object uniquely identifies a conceptual row
                in the table."
          ::= { sipUriSupportedEntry 1 }

      sipUriSupported OBJECT-TYPE
          SYNTAX SnmpAdminString
          MAX-ACCESS read-only
          STATUS current
          DESCRIPTION
               "This object indicates a particular non-SIP URI scheme
                supported by the SIP entity.  Only the scheme itself



Lingle, et al.         Expires December 30, 2003               [Page 23]

Internet-Draft              SIP MIB Modules                    July 2003


                (as described in RFC 2396) is indicated.  For example,
                if the mailto: URLs are supported, then the table entry
                contains 'mailto' without the colon."
          REFERENCE
                "RFC 2396 section 3"
          ::= { sipUriSupportedEntry 2 }


      --
      -- Support for features which MAY be requested in Proxy-Require
      -- and Require headers
      --
      sipFtrSupportedTable OBJECT-TYPE
          SYNTAX     SEQUENCE OF SipFtrSupportedEntry
          MAX-ACCESS not-accessible
          STATUS     current
          DESCRIPTION
               "This table contains a list of the features
                supported by each SIP entity in this system, and which
                MAY be REQUIRED by a peer. Definition of non-standard
                features is outside the scope of SIP, which only provides
                mechanisms whereby support for specific features MAY be
                signalled or requested.

                As and example of a non-standard feature, a user agent
                client MAY require that a server support the
                'com.example.billing' feature, which it would
                indicate in a Require header.  Such a client would have
                a row in its sipFtrSupportedTable containing the string
                'com.example.billing'.  Similarly, a server which is
                capable of handling requests for such features would list
                the string in its sipFtrSupportedTable.

                If a server does not support the required feature
                (indicated in a Require header to a UAS, or in a Proxy-
                Require to a Proxy Server), the server returns a 420 Bad
                Extension listing the feature in an Unsupported header.

                Normally the list of such features supported by an entity
                is static (i.e. will not change over time)."
          REFERENCE
               "RFC 3261, Section 19.2"
          ::= { sipCommonCfgBase 4 }

      sipFtrSupportedEntry OBJECT-TYPE
          SYNTAX SipFtrSupportedEntry
          MAX-ACCESS not-accessible
          STATUS current



Lingle, et al.         Expires December 30, 2003               [Page 24]

Internet-Draft              SIP MIB Modules                    July 2003


          DESCRIPTION
               "A particular feature supported by the SIP
                entity, and which MAY be REQUIRED by a peer.

                Each row represents those objects for a particular SIP
                entity present in this system.  applIndex is used to
                uniquely identify these instances of SIP entities and
                correlate them through the common framework of the
                NETWORK-SERVICES-MIB (RFC 2788).
                The objects in this table entry SHOULD be non-volatile
                and their value SHOULD be kept at reboot."
          INDEX { applIndex, sipFtrSupportedIndex }
          ::= { sipFtrSupportedTable 1 }

      SipFtrSupportedEntry ::=
          SEQUENCE {
                   sipFtrSupportedIndex           Unsigned32,
                   sipFtrSupported                SnmpAdminString
          }

      sipFtrSupportedIndex OBJECT-TYPE
          SYNTAX     Unsigned32 (1..4294967295)
          MAX-ACCESS not-accessible
          STATUS     current
          DESCRIPTION
               "This object uniquely identifies a conceptual row in the
                table."
          ::= { sipFtrSupportedEntry 1 }

      sipFtrSupported OBJECT-TYPE
          SYNTAX     SnmpAdminString
          MAX-ACCESS read-only
          STATUS     current
          DESCRIPTION
               "This object indicates a particular feature
                which is supported by the SIP entity."
          ::= { sipFtrSupportedEntry 2 }


      --
      -- Support for extension methods
      --
      sipExtMethodSupportedTable OBJECT-TYPE
          SYNTAX     SEQUENCE OF SipExtMethodSupportedEntry
          MAX-ACCESS not-accessible
          STATUS     current
          DESCRIPTION
               "This table contains a list of extension methods supported



Lingle, et al.         Expires December 30, 2003               [Page 25]

Internet-Draft              SIP MIB Modules                    July 2003


                by each SIP entity in this system. These are in addition
                to the standard set of SIP methods discussed in Section
                7.1 of RFC 3261.  Any additional methods that MAY be
                incorporated into the SIP protocol SHOULD be represented
                by this table without any requirement to update this MIB.
                The table is informational in nature; conveying to the NMS
                capabilities of the managed system."
          ::= { sipCommonCfgBase 5 }

      sipExtMethodSupportedEntry OBJECT-TYPE
          SYNTAX     SipExtMethodSupportedEntry
          MAX-ACCESS not-accessible
          STATUS     current
          DESCRIPTION
               "A particular extension method supported by the SIP entity.

                Each row represents those objects for a particular SIP
                entity present in this system.  applIndex is used to
                uniquely identify these instances of SIP entities and
                correlate them through the common framework of the
                NETWORK-SERVICES-MIB (RFC 2788).
                The objects in this table entry SHOULD be non-volatile
                and their value SHOULD be kept at reboot."
          INDEX { applIndex, sipExtMethodSupportedIndex }
          ::= { sipExtMethodSupportedTable 1 }

      SipExtMethodSupportedEntry ::=
          SEQUENCE {
                   sipExtMethodSupportedIndex     Unsigned32,
                   sipExtMethodName               SnmpAdminString
          }

      sipExtMethodSupportedIndex OBJECT-TYPE
          SYNTAX     Unsigned32 (1..4294967295)
          MAX-ACCESS not-accessible
          STATUS     current
          DESCRIPTION
               "This object uniquely identifies a conceptual row
                in the table."
          ::= { sipExtMethodSupportedEntry 1 }

      sipExtMethodName OBJECT-TYPE
          SYNTAX SnmpAdminString
          MAX-ACCESS read-only
          STATUS current
          DESCRIPTION
               "This object reflects the supported extension method's name.
                The method name MUST be all upper case (eg, 'FOO')."



Lingle, et al.         Expires December 30, 2003               [Page 26]

Internet-Draft              SIP MIB Modules                    July 2003


          ::= { sipExtMethodSupportedEntry 2 }


      --
      -- SIP Timer Configuration
      --
      sipCommonCfgTimerTable OBJECT-TYPE
          SYNTAX      SEQUENCE OF SipCommonCfgTimerEntry
          MAX-ACCESS not-accessible
          STATUS     current
          DESCRIPTION
               "This table contains timer configuration objects applicable
                to SIP user agent and SIP stateful Proxy Server entities."
          ::= { sipCommonCfgTimer 1 }

      sipCommonCfgTimerEntry OBJECT-TYPE
          SYNTAX     SipCommonCfgTimerEntry
          MAX-ACCESS not-accessible
          STATUS     current
          DESCRIPTION
               "A row of timer configuration.

                Each row represents those objects for a particular SIP
                entity present in this system.  applIndex is used to
                uniquely identify these instances of SIP entities and
                correlate them through the common framework of the
                NETWORK-SERVICES-MIB (RFC 2788).
                The objects in this table entry SHOULD be non-volatile
                and their value SHOULD be kept at reboot."
          INDEX { applIndex }
          ::= { sipCommonCfgTimerTable 1 }

      SipCommonCfgTimerEntry ::=
          SEQUENCE {
                   sipCfgTimerA               Unsigned32,
                   sipCfgTimerB               Unsigned32,
                   sipCfgTimerC               Unsigned32,
                   sipCfgTimerD               Unsigned32,
                   sipCfgTimerE               Unsigned32,
                   sipCfgTimerF               Unsigned32,
                   sipCfgTimerG               Unsigned32,
                   sipCfgTimerH               Unsigned32,
                   sipCfgTimerI               Unsigned32,
                   sipCfgTimerJ               Unsigned32,
                   sipCfgTimerK               Unsigned32,
                   sipCfgTimerT1              Unsigned32,
                   sipCfgTimerT2              Unsigned32,
                   sipCfgTimerT4              Unsigned32



Lingle, et al.         Expires December 30, 2003               [Page 27]

Internet-Draft              SIP MIB Modules                    July 2003


          }

      sipCfgTimerA OBJECT-TYPE
          SYNTAX      Unsigned32 (100..1000)
          UNITS       "milliseconds"
          MAX-ACCESS  read-write
          STATUS      current
          DESCRIPTION
               "This object specifies the initial value for the retransmit
               timer for the INVITE method.  The retransmit timer doubles
               after each retransmission, ensuring an exponential backoff
               in network traffic. This object represents the initial time
               a SIP entity will wait to receive a provisional response to
               an INVITE before resending the INVITE request."
          REFERENCE
                "RFC 3261, Section 17.1.1.2"
          DEFVAL { 500 }
          ::= { sipCommonCfgTimerEntry 1 }

      sipCfgTimerB OBJECT-TYPE
          SYNTAX      Unsigned32 (32000..300000)
          UNITS       "milliseconds"
          MAX-ACCESS  read-write
          STATUS      current
          DESCRIPTION
              "This object specifies the maximum time a SIP entity will
               wait to receive a final response to an INVITE.  The
               timer is started upon transmission of the initial INVITE
               request."
          REFERENCE
                "RFC 3261, Section 17.1.1.2"
          DEFVAL { 32000 }
      ::= { sipCommonCfgTimerEntry 2 }

      sipCfgTimerC OBJECT-TYPE
          SYNTAX      Unsigned32 (180000..300000)
          UNITS       "milliseconds"
          MAX-ACCESS  read-write
          STATUS      current
          DESCRIPTION
               "This object specifies the maximum time a SIP Proxy Server
                will wait to receive a provisional response to an INVITE.
                The Timer C MUST be set for each client transaction when
                an INVITE request is proxied."
          REFERENCE
                "RFC 3261, Section 16.6"
          DEFVAL { 180000 }
          ::= { sipCommonCfgTimerEntry 3 }



Lingle, et al.         Expires December 30, 2003               [Page 28]

Internet-Draft              SIP MIB Modules                    July 2003


      sipCfgTimerD OBJECT-TYPE
          SYNTAX      Unsigned32 (0..300000)
          UNITS       "milliseconds"
          MAX-ACCESS  read-write
          STATUS      current
          DESCRIPTION
               "This object specifies the amount of time that the server
                transaction can remain in the 'Completed' state when
                unreliable transports are used. The default value MUST be
                greater than 32000 for UDP transport and its value MUST
                be 0 for TCP/SCTP transport."
          REFERENCE
                "RFC 3261, Section 17.1.1.2"
              DEFVAL { 32000 }
          ::= { sipCommonCfgTimerEntry 4 }

      sipCfgTimerE OBJECT-TYPE
          SYNTAX      Unsigned32 (100..1000)
          UNITS       "milliseconds"
          MAX-ACCESS  read-write
          STATUS      current
          DESCRIPTION
              "This object specifies the initial value for the retransmit
               timer for a non-INVITE method while in 'Trying State'.
               The retransmit timer doubles after each retransmission
               until it reaches T2 to ensure an exponential backoff
               in network traffic. This object represents the initial time
               a SIP entity will wait to receive a provisional response to
               the request before resending the non-INVITE request."
          REFERENCE
                "RFC 3261, Section 17.1.2.2"
          DEFVAL { 500 }
          ::= { sipCommonCfgTimerEntry 5 }

      sipCfgTimerF  OBJECT-TYPE
          SYNTAX      Unsigned32 (32000..300000)
          UNITS       "milliseconds"
          MAX-ACCESS  read-write
          STATUS      current
          DESCRIPTION
              "This object specifies the maximum time a SIP entity will
               wait to receive a final response to a non-INVITE request.
               The timer is started upon transmission of the
               initial request."
          REFERENCE
                "RFC 3261, Section 17.1.2.2"
          DEFVAL { 32000 }
          ::= { sipCommonCfgTimerEntry 6 }



Lingle, et al.         Expires December 30, 2003               [Page 29]

Internet-Draft              SIP MIB Modules                    July 2003


      sipCfgTimerG  OBJECT-TYPE
          SYNTAX      Unsigned32 (0..1000)
          UNITS       "milliseconds"
          MAX-ACCESS  read-write
          STATUS      current
          DESCRIPTION
               "This object specifies the initial value for the retransmit
               timer for final responses to INVITE requests.
               If timer G fires, the response is passed to the transport
               layer once more for retransmission, and timer G is set
               to fire in MIN(2*T1, T2) seconds.  From then on, when
               timer G fires, the response is passed to the transport
               again for transmission, and timer G is reset with a value
               that doubles, unless that value exceeds T2, in which case
               it is reset with the value of T2.
               The default value MUST be T1 for UDP transport and its value
               MUST be 0 for reliable transport like TCP/SCTP."
          REFERENCE
                "RFC 3261, Section 17.2.1"
          DEFVAL { 500 }
          ::= { sipCommonCfgTimerEntry 7 }

      sipCfgTimerH  OBJECT-TYPE
          SYNTAX      Unsigned32 (32000..300000)
          UNITS       "milliseconds"
          MAX-ACCESS  read-write
          STATUS      current
          DESCRIPTION
               "This object specifies the maximum time a server will wait
               to receive an ACK before it abandons retransmitting the
               response. The timer is started upon entering the
               'Completed' state."
          REFERENCE
                "RFC 3261, Section 17.2.1"
          DEFVAL { 32000 }
          ::= { sipCommonCfgTimerEntry 8 }

         sipCfgTimerI  OBJECT-TYPE
          SYNTAX      Unsigned32 (0..10000)
          UNITS       "milliseconds"
          MAX-ACCESS  read-write
          STATUS      current
          DESCRIPTION
               "This object specifies the maximum time a SIP entity will
               wait to receive additional ACK message retransmissions.
               The timer is started upon entering the 'Confirmed' state.
               The default value MUST be T4 for UDP transport and its value
               MUST be 0 for reliable transport like TCP/SCTP."



Lingle, et al.         Expires December 30, 2003               [Page 30]

Internet-Draft              SIP MIB Modules                    July 2003


          REFERENCE
                "RFC 3261, Section 17.2.1"
          DEFVAL { 5000 }
          ::= { sipCommonCfgTimerEntry 9 }

         sipCfgTimerJ  OBJECT-TYPE
          SYNTAX      Unsigned32 (32000..300000)
          UNITS       "milliseconds"
          MAX-ACCESS  read-write
          STATUS      current
          DESCRIPTION
               "This object specifies the maximum time a SIP server will
               wait to receive retransmissions of non-INVITE request.
               The timer is started upon entering the 'Completed' state
               for non-INVITE transactions. When timer J fires, the server
               MUST transition to the 'Terminated' state."
          REFERENCE "RFC 3261, Section 17.2.2"
          DEFVAL { 32000 }
          ::= { sipCommonCfgTimerEntry 10 }

         sipCfgTimerK  OBJECT-TYPE
          SYNTAX      Unsigned32 (0..10000)
          UNITS       "milliseconds"
          MAX-ACCESS  read-write
          STATUS      current
          DESCRIPTION
               "This object specifies the maximum time a SIP client will
               wait to receive retransmissions of responses to non-INVITE
               requests.
               The timer is started upon entering the 'Completed' state
               for non-INVITE transactions. When timer K fires, the server
               MUST transition to the 'Terminated' state.
               The default value MUST be T4 for UDP transport and its value
               MUST be 0 for reliable transport like TCP/SCTP."
          REFERENCE
                "RFC 3261, Section 17.1.2.2"
          DEFVAL { 5000 }
          ::= { sipCommonCfgTimerEntry 11 }

      sipCfgTimerT1  OBJECT-TYPE
          SYNTAX      Unsigned32 (200..10000)
          UNITS       "milliseconds"
          MAX-ACCESS  read-write
          STATUS      current
          DESCRIPTION
               "This object specifies the T1 timer for a SIP entity. T1
               is an estimate of the round-trip time (RTT) between the
               client and server transactions."



Lingle, et al.         Expires December 30, 2003               [Page 31]

Internet-Draft              SIP MIB Modules                    July 2003


          REFERENCE
               "RFC 3261, Section 17"
          DEFVAL { 500 }
          ::= { sipCommonCfgTimerEntry 12 }

      sipCfgTimerT2  OBJECT-TYPE
          SYNTAX      Unsigned32 (200..10000)
          UNITS       "milliseconds"
          MAX-ACCESS  read-write
          STATUS      current
          DESCRIPTION
               "This object specifies the T2 timer for a SIP entity.
                T2 is the maximum retransmit interval for non-INVITE
                requests and INVITE responses.  It's used in various
                parts of the protocol to reset other Timer* objects
                to this value."
          REFERENCE
                "RFC 3261, Section 17"
          DEFVAL { 4000 }
          ::= { sipCommonCfgTimerEntry 13 }

      sipCfgTimerT4  OBJECT-TYPE
          SYNTAX      Unsigned32 (200..10000)
          UNITS       "milliseconds"
          MAX-ACCESS  read-write
          STATUS      current
          DESCRIPTION
               "This object specifies the T4 timer for a SIP entity.
                T4 is the maximum duration a message will remain in
                the network. It represents the amount of time the
                network will take to clear messages between client
                and server transactions.  It's used in various parts
                of the protocol to reset other Timer* objects to this
                value."
          REFERENCE
                "RFC 3261, Section 17"
          DEFVAL { 5000 }
          ::= { sipCommonCfgTimerEntry 14 }


      --
      -- Initial Timers Extensions: support for extension methods
      --
      sipCommonCfgTimerExtMethodTable OBJECT-TYPE
          SYNTAX      SEQUENCE OF SipCommonCfgTimerExtMethodEntry
          MAX-ACCESS  not-accessible
          STATUS      current
          DESCRIPTION



Lingle, et al.         Expires December 30, 2003               [Page 32]

Internet-Draft              SIP MIB Modules                    July 2003


               "This table contains retransmit timers for each SIP
                extension method this entity supports.

                The applicable T2 timer value for timers configured
                in this table is that of the sipCfgTimerT2 object
                with the same applIndex value."
          ::= { sipCommonCfgTimer 2 }

      sipCommonCfgTimerExtMethodEntry  OBJECT-TYPE
          SYNTAX      SipCommonCfgTimerExtMethodEntry
          MAX-ACCESS  not-accessible
          STATUS      current
          DESCRIPTION
               "This row contains timer value information for
                a particular extension method.

                Each row represents those objects for a particular SIP
                entity present in this system.  applIndex is used to
                uniquely identify these instances of SIP entities and
                correlate them through the common framework of the
                NETWORK-SERVICES-MIB (RFC 2788).
                The objects in this table entry SHOULD be non-volatile
                and their value SHOULD be kept at reboot."
          AUGMENTS { sipExtMethodSupportedEntry }
          ::= { sipCommonCfgTimerExtMethodTable 1 }

      SipCommonCfgTimerExtMethodEntry ::=
          SEQUENCE {
             sipCfgTimerExtMethodTimer      Unsigned32
          }

      sipCfgTimerExtMethodTimer OBJECT-TYPE
          SYNTAX      Unsigned32
          UNITS       "milliseconds"
          MAX-ACCESS  read-create
          STATUS      current
          DESCRIPTION
               "This object specifies the time a SIP entity will wait
                for a response to the extension method request before
                retransmitting.  The retransmit timer doubles after
                each retransmission, ensuring an exponential backoff
                in network traffic."
          ::= { sipCommonCfgTimerExtMethodEntry 1 }


      --
      -- SIP Retry Configuration
      --



Lingle, et al.         Expires December 30, 2003               [Page 33]

Internet-Draft              SIP MIB Modules                    July 2003


      sipCommonCfgRetryTable OBJECT-TYPE
          SYNTAX      SEQUENCE OF SipCommonCfgRetryEntry
          MAX-ACCESS not-accessible
          STATUS     current
          DESCRIPTION
               "This table contains retry configuration objects applicable
                to SIP user agent and SIP proxies."
          ::= { sipCommonCfgRetry 1 }

      sipCommonCfgRetryEntry OBJECT-TYPE
          SYNTAX     SipCommonCfgRetryEntry
          MAX-ACCESS not-accessible
          STATUS     current
          DESCRIPTION
               "A row of retry configuration.

                Each row represents those objects for a particular SIP
                entity present in this system.  applIndex is used to
                uniquely identify these instances of SIP entities and
                correlate them through the common framework of the
                NETWORK-SERVICES-MIB (RFC 2788).
                The objects in this table entry SHOULD be non-volatile
                and their value SHOULD be kept at reboot."
          INDEX { applIndex }
          ::= { sipCommonCfgRetryTable 1 }

      SipCommonCfgRetryEntry ::=
          SEQUENCE {
                   sipCfgRetryInvite            Unsigned32,
                   sipCfgRetryBye               Unsigned32,
                   sipCfgRetryCancel            Unsigned32,
                   sipCfgRetryRegister          Unsigned32,
                   sipCfgRetryOptions           Unsigned32,
                   sipCfgRetryFinalResponse     Unsigned32,
                   sipCfgRetryNonFinalResponse  Unsigned32
          }

      sipCfgRetryInvite OBJECT-TYPE
          SYNTAX      Unsigned32 (1..10)
          MAX-ACCESS  read-write
          STATUS      current
          DESCRIPTION
               "This object will specify the number of times a SIP entity
                will retry sending an INVITE request."
          DEFVAL { 6 }
          ::= { sipCommonCfgRetryEntry 1 }

      sipCfgRetryBye OBJECT-TYPE



Lingle, et al.         Expires December 30, 2003               [Page 34]

Internet-Draft              SIP MIB Modules                    July 2003


          SYNTAX      Unsigned32 (1..10)
          MAX-ACCESS  read-write
          STATUS      current
          DESCRIPTION
               "This object will specify the number of times a SIP entity
                will retry sending a BYE request."
          DEFVAL { 6 }
          ::= { sipCommonCfgRetryEntry 2 }

      sipCfgRetryCancel OBJECT-TYPE
          SYNTAX      Unsigned32 (1..10)
          MAX-ACCESS  read-write
          STATUS      current
          DESCRIPTION
               "This object will specify the number of times a SIP entity
                will retry sending a CANCEL request."
          DEFVAL { 6 }
          ::= { sipCommonCfgRetryEntry 3 }

      sipCfgRetryRegister OBJECT-TYPE
          SYNTAX      Unsigned32 (1..10)
          MAX-ACCESS  read-write
          STATUS      current
          DESCRIPTION
               "This object will specify the number of times a SIP entity
                will retry sending a REGISTER request."
          DEFVAL { 6 }
          ::= { sipCommonCfgRetryEntry 4 }

      sipCfgRetryOptions OBJECT-TYPE
          SYNTAX      Unsigned32 (1..10)
          MAX-ACCESS  read-write
          STATUS      current
          DESCRIPTION
               "This object will specify the number of times a SIP entity
                will retry sending an OPTIONS request."
          DEFVAL { 6 }
          ::= { sipCommonCfgRetryEntry 5 }

      sipCfgRetryFinalResponse OBJECT-TYPE
          SYNTAX      Unsigned32 (1..10)
          MAX-ACCESS  read-write
          STATUS      current
          DESCRIPTION
               "This object will specify the number of times a SIP entity
                will retry sending a final response and expecting an ACK."
          DEFVAL { 6 }
          ::= { sipCommonCfgRetryEntry 6 }



Lingle, et al.         Expires December 30, 2003               [Page 35]

Internet-Draft              SIP MIB Modules                    July 2003


      sipCfgRetryNonFinalResponse OBJECT-TYPE
          SYNTAX      Unsigned32 (1..10)
          MAX-ACCESS  read-write
          STATUS      current
          DESCRIPTION
               "This object will specify the number of times a SIP entity
                will retry sending a non-final response."
          DEFVAL { 6 }
          ::= { sipCommonCfgRetryEntry 7 }


      --
      -- Retry Extensions: support for extension methods
      --
      sipCommonCfgRetryExtMethodTable OBJECT-TYPE
          SYNTAX      SEQUENCE OF SipCommonCfgRetryExtMethodEntry
          MAX-ACCESS  not-accessible
          STATUS      current
          DESCRIPTION
               "This table contains retry configuration for each SIP
                extension method this entity supports."
          ::= { sipCommonCfgRetry 2 }

      sipCommonCfgRetryExtMethodEntry  OBJECT-TYPE
          SYNTAX      SipCommonCfgRetryExtMethodEntry
          MAX-ACCESS  not-accessible
          STATUS      current
          DESCRIPTION
               "This row contains retry configuration information for
                a particular extension method.

                Each row represents those objects for a particular SIP
                entity present in this system.  applIndex is used to
                uniquely identify these instances of SIP entities and
                correlate them through the common framework of the
                NETWORK-SERVICES-MIB (RFC 2788).
                The objects in this table entry SHOULD be non-volatile
                and their value SHOULD be kept at reboot."
          AUGMENTS { sipExtMethodSupportedEntry }
          ::= { sipCommonCfgRetryExtMethodTable 1 }

      SipCommonCfgRetryExtMethodEntry ::=
          SEQUENCE {
             sipCfgRetryExtMethodRetry      Unsigned32
          }

      sipCfgRetryExtMethodRetry OBJECT-TYPE
          SYNTAX      Unsigned32



Lingle, et al.         Expires December 30, 2003               [Page 36]

Internet-Draft              SIP MIB Modules                    July 2003


          MAX-ACCESS  read-create
          STATUS      current
          DESCRIPTION
               "This object specifies the number of times a SIP entity
                will retry sending its request for this particular
                extension method."
          ::= { sipCommonCfgRetryExtMethodEntry 1 }


      --
      -- Per Method Expires Configuration
      --
      sipCommonCfgExpiresMethodTable OBJECT-TYPE
          SYNTAX     SEQUENCE OF SipCommonCfgExpiresMethodEntry
          MAX-ACCESS not-accessible
          STATUS     current
          DESCRIPTION
               "This table contains Expires header value configuration
                objects applicable to SIP user agent and SIP stateful
                Proxy Server entities."
          ::= { sipCommonCfgExpires 1 }

      sipCommonCfgExpiresMethodEntry OBJECT-TYPE
          SYNTAX     SipCommonCfgExpiresMethodEntry
          MAX-ACCESS not-accessible
          STATUS     current
          DESCRIPTION
               "A row of Expires header configuration for SIP Methods.

                Each row represents those objects for a particular SIP
                entity present in this system.  applIndex is used to
                uniquely identify these instances of SIP entities and
                correlate them through the common framework of the
                NETWORK-SERVICES-MIB (RFC 2788).
                The objects in this table entry SHOULD be non-volatile
                and their value SHOULD be kept at reboot."
          INDEX { applIndex }
          ::= { sipCommonCfgExpiresMethodTable 1 }

      SipCommonCfgExpiresMethodEntry ::=
          SEQUENCE {
                   sipCfgExpiresInvite       Unsigned32,
                   sipCfgExpiresRegister     Unsigned32,
                   sipCfgExpiresHeaderMethod BITS
          }

      sipCfgExpiresInvite OBJECT-TYPE
          SYNTAX     Unsigned32 (0..4294967295)



Lingle, et al.         Expires December 30, 2003               [Page 37]

Internet-Draft              SIP MIB Modules                    July 2003


          UNITS      "seconds"
          MAX-ACCESS read-write
          STATUS     current
          DESCRIPTION
               "For user agent clients, this value is inserted into the
                Expires header.
                For Proxy Servers, if a received request contained an
                Expires header, then the value in the header takes
                precedence."
          ::= { sipCommonCfgExpiresMethodEntry 1 }

      sipCfgExpiresRegister OBJECT-TYPE
          SYNTAX     Unsigned32 (0..4294967295)
          UNITS      "seconds"
          MAX-ACCESS read-write
          STATUS     current
          DESCRIPTION
               "For user agent clients, this value is inserted into the
                Expires header.
                For Registrar Servers, if a received request contained an
                Expires header, then the value in the header takes
                precedence."
          ::= { sipCommonCfgExpiresMethodEntry 2 }

      sipCfgExpiresHeaderMethod OBJECT-TYPE
          SYNTAX     BITS {
                           invite(0),
                           register(1)
          }
          MAX-ACCESS read-write
          STATUS current
          DESCRIPTION
               "This convention is a bit map. Each bit represents a
                SIP method where the Expires header SHOULD be included.
                If a bit has value 1, then the requests corresponding
                to that SIP method MUST include an Expires header line.
                If a bit has value 0, then the Expires header line will
                not be added.

                Combinations of bits can be set when the Expires header
                line is REQUIRED in multiple SIP methods.

                     bit 0   : INVITE method.
                     bit 1   : REGISTER Method."
          ::= { sipCommonCfgExpiresMethodEntry 3 }

      sipCommonCfgExpiresStatusCodeTable OBJECT-TYPE
          SYNTAX     SEQUENCE OF SipCommonCfgExpiresStatusCodeEntry



Lingle, et al.         Expires December 30, 2003               [Page 38]

Internet-Draft              SIP MIB Modules                    July 2003


          MAX-ACCESS not-accessible
          STATUS     current
          DESCRIPTION
               "This table contains the Expires header configuration
                objects for the SIP responses."
          ::= { sipCommonCfgExpires 2 }

      sipCommonCfgExpiresStatusCodeEntry OBJECT-TYPE
          SYNTAX      SipCommonCfgExpiresStatusCodeEntry
          MAX-ACCESS  not-accessible
          STATUS      current
          DESCRIPTION
               "This row contains information on the configuration of
                the Expires header value for a particular SIP status
                code. Examples of SIP responses that MAY include an
                Expires header are 302 and 504.

                Each row represents those objects for a particular SIP
                entity present in this system.  applIndex is used to
                uniquely identify these instances of SIP entities and
                correlate them through the common framework of the
                NETWORK-SERVICES-MIB (RFC 2788).
                The objects in this table entry SHOULD be non-volatile
                and their value SHOULD be kept at reboot."
          INDEX { applIndex, sipCfgExpiresStatusCodeValue }
          ::= { sipCommonCfgExpiresStatusCodeTable 1 }

      SipCommonCfgExpiresStatusCodeEntry ::=
          SEQUENCE {
                   sipCfgExpiresStatusCodeValue   Unsigned32,
                   sipCfgExpiresHeaderValue       Unsigned32,
                   sipCfgExpiresStatusCodeStatus  RowStatus
           }

      sipCfgExpiresStatusCodeValue OBJECT-TYPE
          SYNTAX      Unsigned32 (100..999)
          MAX-ACCESS  not-accessible
          STATUS      current
          DESCRIPTION
               "This object contains a SIP status code value for which
                the Expires header value is configured. All of the other
                information in the row is related to this value."
          ::= { sipCommonCfgExpiresStatusCodeEntry 1 }

      sipCfgExpiresHeaderValue OBJECT-TYPE
          SYNTAX     Unsigned32 (0..4294967295)
          UNITS      "seconds"
          MAX-ACCESS read-create



Lingle, et al.         Expires December 30, 2003               [Page 39]

Internet-Draft              SIP MIB Modules                    July 2003


          STATUS     current
          DESCRIPTION
               "This value is inserted into the Expires header for the
                specific status code."
          ::= { sipCommonCfgExpiresStatusCodeEntry 2 }

      sipCfgExpiresStatusCodeStatus OBJECT-TYPE
          SYNTAX      RowStatus
          MAX-ACCESS  read-create
          STATUS      current
          DESCRIPTION
               "This object is REQUIRED to create or delete rows
                by a manager.

                A value for sipCfgExpiresHeaderValue MUST be specified when
                creating rows by setting this row status to 'createAndGo'.
                The row will automatically transition to 'active'.

                The configuration specified by an entry will be made
                active when this object is set to 'active'."
          ::= { sipCommonCfgExpiresStatusCodeEntry 3 }


      --
      -- Common Statistics Objects
      --

      --
      -- Summary Statistics
      --
      sipSummaryStatsTable OBJECT-TYPE
          SYNTAX     SEQUENCE OF SipSummaryStatsEntry
          MAX-ACCESS not-accessible
          STATUS     current
          DESCRIPTION
               "This table contains the summary statistics objects
                applicable to all SIP entities.  Each row represents
                those objects for a particular SIP entity present in
                this system."
          ::= { sipCommonStatsSummary 1 }

      sipSummaryStatsEntry OBJECT-TYPE
          SYNTAX     SipSummaryStatsEntry
          MAX-ACCESS not-accessible
          STATUS     current


          DESCRIPTION



Lingle, et al.         Expires December 30, 2003               [Page 40]

Internet-Draft              SIP MIB Modules                    July 2003


               "A row of summary statistics.

                Each row represents those objects for a particular SIP
                entity present in this system.  applIndex is used to
                uniquely identify these instances of SIP entities and
                correlate them through the common framework of the
                NETWORK-SERVICES-MIB (RFC 2788)."
          INDEX { applIndex }
          ::= { sipSummaryStatsTable 1 }

      SipSummaryStatsEntry ::=
          SEQUENCE {
                   sipSummaryInRequests         Counter32,
                   sipSummaryOutRequests        Counter32,
                   sipSummaryInResponses        Counter32,
                   sipSummaryOutResponses       Counter32,
                   sipSummaryTotalTransactions  Counter32
          }

      sipSummaryInRequests OBJECT-TYPE
          SYNTAX     Counter32
          MAX-ACCESS read-only
          STATUS     current
          DESCRIPTION
               "This object indicates the total number of SIP request
                messages received by the SIP entity including
                retransmissions."
          ::= { sipSummaryStatsEntry 1 }

      sipSummaryOutRequests OBJECT-TYPE
          SYNTAX     Counter32
          MAX-ACCESS read-only
          STATUS     current
          DESCRIPTION
               "This object contains the total number of SIP request
                messages sent out (originated and relayed) by the SIP
                entity.  Where a particular message is sent more than
                once, for example as a retransmission, or as a result of
                forking, each transmission is counted separately."
          ::= { sipSummaryStatsEntry 2 }

      sipSummaryInResponses OBJECT-TYPE
          SYNTAX     Counter32
          MAX-ACCESS read-only
          STATUS     current
          DESCRIPTION
               "This object contains the total number of SIP response
                messages received by the SIP entity including



Lingle, et al.         Expires December 30, 2003               [Page 41]

Internet-Draft              SIP MIB Modules                    July 2003


                retransmissions."
          ::= { sipSummaryStatsEntry 3 }

      sipSummaryOutResponses OBJECT-TYPE
          SYNTAX     Counter32
          MAX-ACCESS read-only
          STATUS     current
          DESCRIPTION


               "This object contains the total number of SIP response
                messages sent (originated and relayed) by the SIP entity
                including retransmissions."
          ::= { sipSummaryStatsEntry 4 }

      sipSummaryTotalTransactions OBJECT-TYPE
          SYNTAX Counter32
          MAX-ACCESS read-only
          STATUS current
          DESCRIPTION
               "This object contains a count of the number of transactions
                that are in progress and transactions that have reached the
                terminated state.  It is not applicable to stateless
                SIP Proxy Servers.

                A SIP transaction occurs between a client and a server and
                comprises all messages from the first request sent from
                the client to the server up to a final (non-1xx) response
                sent from the server to the client.

                If the request is INVITE and the final response is a non-2xx,
                the transaction also include an ACK to the response.  The ACK
                for a 2xx response to an INVITE request is a separate
                transaction.

                The branch ID parameter in the Via header field values
                serves as a transaction identifier.

                A transaction is identified by the CSeq sequence number
                within a single call leg.  The ACK request has the same
                CSeq number as the corresponding INVITE request, but
                comprises a transaction of its own.

                In the case of a forked request, all branches count as a
                single transaction.

                For a transaction stateless Proxy Server, this counter
                is always 0."



Lingle, et al.         Expires December 30, 2003               [Page 42]

Internet-Draft              SIP MIB Modules                    July 2003


          ::= { sipSummaryStatsEntry 5 }


      --
      -- SIP Method Statistics
      -- Total counts for each SIP method.
      --
      sipMethodStatsTable OBJECT-TYPE
          SYNTAX     SEQUENCE OF SipMethodStatsEntry
          MAX-ACCESS not-accessible
          STATUS     current
          DESCRIPTION
               "This table contains the method statistics objects
                for SIP entities.  Each row represents those objects
                for a particular SIP entity present in this system."
          ::= { sipCommonStatsMethod 1 }

      sipMethodStatsEntry OBJECT-TYPE
          SYNTAX     SipMethodStatsEntry
          MAX-ACCESS not-accessible
          STATUS     current
          DESCRIPTION
               "A row of per entity method statistics.

                Each row represents those objects for a particular SIP
                entity present in this system.  applIndex is used to
                uniquely identify these instances of SIP entities and
                correlate them through the common framework of the
                NETWORK-SERVICES-MIB (RFC 2788)."
          INDEX { applIndex }
          ::= { sipMethodStatsTable 1 }

      SipMethodStatsEntry ::=
          SEQUENCE {
                   sipStatsInviteIns          Counter32,
                   sipStatsInviteOuts         Counter32,
                   sipStatsAckIns             Counter32,
                   sipStatsAckOuts            Counter32,
                   sipStatsByeIns             Counter32,
                   sipStatsByeOuts            Counter32,
                   sipStatsCancelIns          Counter32,
                   sipStatsCancelOuts         Counter32,
                   sipStatsOptionsIns         Counter32,
                   sipStatsOptionsOuts        Counter32,
                   sipStatsRegisterIns        Counter32,
                   sipStatsRegisterOuts       Counter32
          }




Lingle, et al.         Expires December 30, 2003               [Page 43]

Internet-Draft              SIP MIB Modules                    July 2003


      sipStatsInviteIns OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the total number of INVITE requests
                received by the SIP entity including retransmissions."
          REFERENCE
               "RFC 3261, Section 7.1"
          ::= { sipMethodStatsEntry 1 }

      sipStatsInviteOuts OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current

          DESCRIPTION
               "This object reflects the total number of INVITE requests
                sent by the SIP entity including retransmissions."
          REFERENCE
               "RFC 3261, Section 7.1"
          ::= { sipMethodStatsEntry 2 }

      sipStatsAckIns OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the total number of ACK requests
                received by the SIP entity."
          REFERENCE
               "RFC 3261, Section 7.1"
          ::= { sipMethodStatsEntry 3 }

      sipStatsAckOuts OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the total number of ACK requests sent
                by the SIP entity."
          REFERENCE
               "RFC 3261, Section 7.1"
          ::= { sipMethodStatsEntry 4 }

      sipStatsByeIns OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only



Lingle, et al.         Expires December 30, 2003               [Page 44]

Internet-Draft              SIP MIB Modules                    July 2003


          STATUS      current
          DESCRIPTION
               "This object reflects the total number of BYE requests
                received by the SIP entity including retransmissions."
          REFERENCE
               "RFC 3261, Section 7.1"
          ::= { sipMethodStatsEntry 5 }

      sipStatsByeOuts OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the total number of BYE requests sent
                by the SIP entity including retransmissions."
          REFERENCE
               "RFC 3261, Section 7.1"
          ::= { sipMethodStatsEntry 6 }

      sipStatsCancelIns OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the total number of CANCEL requests
                received by the SIP entity including retransmissions."
          REFERENCE
               "RFC 3261, Section 7.1"
          ::= { sipMethodStatsEntry 7 }

      sipStatsCancelOuts OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the total number of CANCEL requests
                sent by the SIP entity including retransmissions."
          REFERENCE
               "RFC 3261, Section 7.1"
          ::= { sipMethodStatsEntry 8 }

      sipStatsOptionsIns OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the total number of OPTIONS requests
                received by the SIP entity including retransmissions."



Lingle, et al.         Expires December 30, 2003               [Page 45]

Internet-Draft              SIP MIB Modules                    July 2003


          REFERENCE
               "RFC 3261, Section 7.1"
          ::= { sipMethodStatsEntry 9 }

      sipStatsOptionsOuts OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the total number of OPTIONS requests
                sent by the SIP entity including retransmissions."
          REFERENCE
               "RFC 3261, Section 7.1"
          ::= { sipMethodStatsEntry 10 }

      sipStatsRegisterIns OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the total number of REGISTER requests
                received by the SIP entity including retransmissions."
          REFERENCE
               "RFC 3261, Section 7.1"
          ::= { sipMethodStatsEntry 11 }

      sipStatsRegisterOuts OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the total number of REGISTER requests
                sent by the SIP entity including retransmissions."
          REFERENCE
               "RFC 3261, Section 7.1"
          ::= { sipMethodStatsEntry 12 }


      --
      -- support for extension methods
      --

      sipStatsExtMethodTable OBJECT-TYPE
          SYNTAX      SEQUENCE OF SipStatsExtMethodEntry
          MAX-ACCESS  not-accessible
          STATUS      current
          DESCRIPTION
               "This table contains the list of extension methods which



Lingle, et al.         Expires December 30, 2003               [Page 46]

Internet-Draft              SIP MIB Modules                    July 2003


                each SIP entity in this system has been requested to
                monitor."
          ::= { sipCommonStatsMethod 2 }

      sipStatsExtMethodEntry OBJECT-TYPE
          SYNTAX      SipStatsExtMethodEntry
          MAX-ACCESS  not-accessible
          STATUS      current
          DESCRIPTION
               "This row contains information on a particular extension
                method that the SIP entity has been requested to monitor.

                Each row represents those objects for a particular SIP
                entity present in this system.  applIndex is used to
                uniquely identify these instances of SIP entities and
                correlate them through the common framework of the
                NETWORK-SERVICES-MIB (RFC 2788)."
          AUGMENTS { sipExtMethodSupportedEntry }
          ::= { sipStatsExtMethodTable 1 }

      SipStatsExtMethodEntry ::=
          SEQUENCE {
                   sipStatsExtMethodIns        Counter32,
                   sipStatsExtMethodOuts       Counter32
          }

      sipStatsExtMethodIns OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the total number of requests received
                by the SIP entity which requested the method contained in
                the sipStatsExtMethodName column including retransmissions
                if appropriate for the method."
          ::= { sipStatsExtMethodEntry 1 }

      sipStatsExtMethodOuts OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the total number of requests sent
                by the SIP entity which requested the method contained in
                the sipStatsExtMethodName column including retransmissions
                if appropriate for the method."
          ::= { sipStatsExtMethodEntry 2 }




Lingle, et al.         Expires December 30, 2003               [Page 47]

Internet-Draft              SIP MIB Modules                    July 2003


      --
      -- SIP Response Status Codes
      --
      sipStatusCodeClassesTable OBJECT-TYPE
          SYNTAX      SEQUENCE OF SipStatusCodeClassesEntry
          MAX-ACCESS  not-accessible
          STATUS      current
          DESCRIPTION
               "This table contains statistics on response status code
                classes for each SIP entity in this system."
          ::= { sipCommonStatusCode 1 }

      sipStatusCodeClassesEntry OBJECT-TYPE
          SYNTAX      SipStatusCodeClassesEntry
          MAX-ACCESS  not-accessible
          STATUS      current
          DESCRIPTION
               "This row contains statistics on response status codes.

                Each row represents those objects for a particular SIP
                entity present in this system.  applIndex is used to
                uniquely identify these instances of SIP entities and
                correlate them through the common framework of the
                NETWORK-SERVICES-MIB (RFC 2788)."
          INDEX { applIndex }
          ::= { sipStatusCodeClassesTable 1 }

      SipStatusCodeClassesEntry ::=
          SEQUENCE {
                   sipStatsInfoClassIns          Counter32,
                   sipStatsInfoClassOuts         Counter32,
                   sipStatsSuccessClassIns       Counter32,
                   sipStatsSuccessClassOuts      Counter32,
                   sipStatsRedirClassIns         Counter32,
                   sipStatsRedirClassOuts        Counter32,
                   sipStatsReqFailClassIns       Counter32,
                   sipStatsReqFailClassOuts      Counter32,
                   sipStatsServerFailClassIns    Counter32,
                   sipStatsServerFailClassOuts   Counter32,
                   sipStatsGlobalFailClassIns    Counter32,
                   sipStatsGlobalFailClassOuts   Counter32,
                   sipStatsOtherClassesIns       Counter32,
                   sipStatsOtherClassesOuts      Counter32
          }

      sipStatsInfoClassIns OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only



Lingle, et al.         Expires December 30, 2003               [Page 48]

Internet-Draft              SIP MIB Modules                    July 2003


          STATUS      current
          DESCRIPTION
               "This object reflects the number of 1xx class
                SIP responses received by the SIP entity.
                This class of responses relates to providing some
                information concerning the progress of processing
                a SIP request."
          REFERENCE
               "RFC 3261, Section 21.1"
          ::= { sipStatusCodeClassesEntry 1 }

      sipStatsInfoClassOuts OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the number of 1xx class
                SIP responses sent by the SIP entity.
                This class of responses relates to providing some
                information concerning the progress of processing
                a SIP request."
          REFERENCE
               "RFC 3261, Section 21.1"
          ::= { sipStatusCodeClassesEntry 2 }

      sipStatsSuccessClassIns OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the number of 2xx class SIP
                responses received by the SIP entity. This class of
                responses relate to successful completion of a SIP
                request."
          REFERENCE
               "RFC 3261, Section 21.2"
          ::= { sipStatusCodeClassesEntry 3 }

      sipStatsSuccessClassOuts OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the number of 2xx class SIP
                responses sent by the SIP entity. This class of
                responses relate to successful completion of a SIP
                request."
          REFERENCE



Lingle, et al.         Expires December 30, 2003               [Page 49]

Internet-Draft              SIP MIB Modules                    July 2003


               "RFC 3261, Section 21.2"
          ::= { sipStatusCodeClassesEntry 4 }

      sipStatsRedirClassIns OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the number of 3xx class SIP
                responses received by the SIP entity.  This class
                of responses relate to redirections to addresses
                where the callee might be reachable."
          REFERENCE
               "RFC 3261, Section 21.3"
          ::= { sipStatusCodeClassesEntry 5 }

      sipStatsRedirClassOuts OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the number of 3xx class SIP
                responses sent by the SIP entity.  This class
                of responses relate to redirections to addresses
                where the callee might be reachable."
          REFERENCE
               "RFC 3261, Section 21.3"
          ::= { sipStatusCodeClassesEntry 6 }

      sipStatsReqFailClassIns OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the number of 4xx class SIP
                responses received by the SIP entity. This class of
                responses reflect request failure by a SIP entity
                providing a client function."
          REFERENCE
               "RFC 3261, Section 21.4"
          ::= { sipStatusCodeClassesEntry 7 }

      sipStatsReqFailClassOuts OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the number of 4xx class SIP



Lingle, et al.         Expires December 30, 2003               [Page 50]

Internet-Draft              SIP MIB Modules                    July 2003


                responses sent by the SIP entity. This class of
                responses reflect request failure by a SIP entity
                providing a server function."
          REFERENCE
               "RFC 3261, Section 21.4"
          ::= { sipStatusCodeClassesEntry 8 }

      sipStatsServerFailClassIns OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the number of 5xx class SIP
                responses received by the SIP entity. This class of
                responses reflect failure responses received by a
                SIP entity providing a client function."
          REFERENCE
               "RFC 3261, Section 21.5"
          ::= { sipStatusCodeClassesEntry 9 }

      sipStatsServerFailClassOuts OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the number of 5xx class SIP
                responses sent by the SIP entity. This class of
                responses reflect failure responses sent by a SIP
                entity providing a server function."
          REFERENCE
               "RFC 3261, Section 21.5"
          ::= { sipStatusCodeClassesEntry 10 }

      sipStatsGlobalFailClassIns OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the number of 6xx class SIP
                responses received by the SIP entity. This class of
                responses reflect failure responses received by a
                SIP entity providing a client function.

                The responses generally indicate that a server has
                definitive information about a particular called party,
                not just the particular instance indicated in the
                Request-URI."
          REFERENCE



Lingle, et al.         Expires December 30, 2003               [Page 51]

Internet-Draft              SIP MIB Modules                    July 2003


               "RFC 3261, Section 21.6"
          ::= { sipStatusCodeClassesEntry 11 }

      sipStatsGlobalFailClassOuts OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the number of 6xx class SIP
                responses sent by the SIP entity. This class of
                responses reflect failure responses sent by a SIP
                entity providing a server function.

                The responses generally indicate that a server has
                definitive information about a particular called party,
                not just the particular instance indicated in the
                Request-URI."
          REFERENCE
               "RFC 3261, Section 21.6"
          ::= { sipStatusCodeClassesEntry 12 }

      sipStatsOtherClassesIns OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the number of SIP responses
                received by the SIP entity for status code response
                classes other than 1xx, 2xx, 3xx, 4xx, 5xx, or 6xx."
          ::= { sipStatusCodeClassesEntry 13 }

      sipStatsOtherClassesOuts OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the number of SIP responses
                sent by the SIP entity for status code response
                classes other than 1xx, 2xx, 3xx, 4xx, 5xx, or 6xx."
          ::= { sipStatusCodeClassesEntry 14 }



      --
      -- Support for specific status codes
      --
      sipStatusCodesTable OBJECT-TYPE
          SYNTAX      SEQUENCE OF SipStatusCodesEntry



Lingle, et al.         Expires December 30, 2003               [Page 52]

Internet-Draft              SIP MIB Modules                    July 2003


          MAX-ACCESS  not-accessible
          STATUS      current
          DESCRIPTION
               "This table contains the list of SIP status codes which
                each SIP entity in this system has been requested to
                monitor. It is the mechanism by which specific status
                codes are monitored."
          ::= { sipCommonStatusCode 2 }

      sipStatusCodesEntry OBJECT-TYPE
          SYNTAX      SipStatusCodesEntry
          MAX-ACCESS  not-accessible
          STATUS      current
          DESCRIPTION
               "This row contains information on a particular SIP status
                code that the SIP entity has been requested to monitor.

                Each row represents those objects for a particular SIP
                entity present in this system.  applIndex is used to
                uniquely identify these instances of SIP entities and
                correlate them through the common framework of the
                NETWORK-SERVICES-MIB (RFC 2788)."
          INDEX { applIndex, sipStatusCodeValue }
          ::= { sipStatusCodesTable 1 }

      SipStatusCodesEntry ::=
          SEQUENCE {
             sipStatusCodeValue      Unsigned32,
             sipStatusCodeIns        Counter32,
             sipStatusCodeOuts       Counter32,
             sipStatusCodeRowStatus  RowStatus
          }

      sipStatusCodeValue OBJECT-TYPE
          SYNTAX      Unsigned32 (100..999)
          MAX-ACCESS  not-accessible
          STATUS      current
          DESCRIPTION
               "This object contains a SIP status code value that the SIP
                entity has been requested to monitor.  All of the other
                information in the row is related to this value."
          ::= { sipStatusCodesEntry 1 }

      sipStatusCodeIns OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION



Lingle, et al.         Expires December 30, 2003               [Page 53]

Internet-Draft              SIP MIB Modules                    July 2003


               "This object reflects the total number of response messages
                received by the SIP entity with the status code value
                contained in the sipStatusCodeValue column."
          ::= { sipStatusCodesEntry 2 }

      sipStatusCodeOuts OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the total number of response messages
                sent by the SIP entity with the status code value
                contained in the sipStatusCodeValue column."
          ::= { sipStatusCodesEntry 3 }

      sipStatusCodeRowStatus OBJECT-TYPE
          SYNTAX      RowStatus
          MAX-ACCESS  read-create
          STATUS      current
          DESCRIPTION
               "The row augmentation in sipStatusCodeNotifTable
                will be governed by the value of this RowStatus.

                This object is REQUIRED to create or delete rows
                by a manager.

                The values 'createAndGo' and 'destroy' are the
                only valid values allowed for this object.
                If a row exists, it will reflect a status of
                'active' when queried."
          ::= { sipStatusCodesEntry 4 }


      --
      -- support for specific status code notifications
      --
      sipStatusCodeNotifTable OBJECT-TYPE
          SYNTAX      SEQUENCE OF SipStatusCodeNotifEntry
          MAX-ACCESS  not-accessible
          STATUS      current
          DESCRIPTION
               "This table contains objects to control notifications
                related to particular status codes each SIP entity in
                this system has been requested to monitor.

                There is an entry in this table corresponding to each
                entry in sipStatusCodesTable.  Therefore, this
                table augments that table and utilizes the same index



Lingle, et al.         Expires December 30, 2003               [Page 54]

Internet-Draft              SIP MIB Modules                    July 2003


                methodology.

                The objects in this table are not included directly
                in the sipStatusCodesTable simply to keep the
                status code notification control objects seperate from
                the actual status code statistics."
          ::= { sipCommonStatusCode 3 }

      sipStatusCodeNotifEntry OBJECT-TYPE
          SYNTAX      SipStatusCodeNotifEntry
          MAX-ACCESS  not-accessible
          STATUS      current
          DESCRIPTION
               "This row contains information controlling notifications
                for a particular SIP status code that the SIP entity has
                been requested to monitor."
          AUGMENTS { sipStatusCodesEntry }
          ::= { sipStatusCodeNotifTable 1 }

      SipStatusCodeNotifEntry ::=
          SEQUENCE {
             sipStatusCodeNotifSend         TruthValue,
             sipStatusCodeNotifEmitMode     INTEGER,
             sipStatusCodeNotifThresh       Unsigned32,
             sipStatusCodeNotifInterval     Unsigned32
          }

      sipStatusCodeNotifSend OBJECT-TYPE
          SYNTAX      TruthValue
          MAX-ACCESS  read-write
          STATUS      current
          DESCRIPTION
               "This object controls whether a sipStatusCodeNotif
                is emitted when the status code value specified in
                by sipStatusCodeValue is sent or received.
                If the value of this object is 'true', then a notification
                is sent.  If it is 'false', no notification is sent.
                Note well, that a notification MAY be emitted for
                every message sent or received that contains the particular
                status code.  Depending on the status code involved,
                this can cause a significant number of notification
                emissions that could be detrimental to network performance.
                Managers are forewarned to be prudent in the use of
                this object to enable notifications.  Look to
                sipStatusCodeNotifEmitMode for alternative
                controls for sipStatusCodeNotif emissions."
          DEFVAL { false }
          ::= { sipStatusCodeNotifEntry 1 }



Lingle, et al.         Expires December 30, 2003               [Page 55]

Internet-Draft              SIP MIB Modules                    July 2003


      sipStatusCodeNotifEmitMode OBJECT-TYPE
          SYNTAX      INTEGER {
                              normal(1),
                              oneShot(2),
                              triggered(3)  -- read-only
                      }
          MAX-ACCESS  read-write
          STATUS      current
          DESCRIPTION
               "The object sipStatusCodeNotifSend MUST be set
                to 'true' for the values of this object to have any
                effect.  It is RECOMMENDED that the desired emit mode
                be established by this object prior to setting
                sipStatusCodeNotifSend to 'true'.  This object and
                the sipStatusCodeNotifSend object can obviously be
                set independently, but their respective values will
                have a dependency on each other and the resulting
                notifications.

                This object specifies the mode for emissions of
                sipStatusCodeNotif notifications.

                normal    : sipStatusCodeNotif notifications will
                            be emitted by the system for each
                            SIP response messages sent or received
                            that contains the desired status code.

                oneShot   : Only one sipStatusCodeNotif notification
                            will be emitted.  It will be the next
                            SIP response messages sent or received
                            that contains the desired status code.

                            No more notifications are emitted until this
                            object is set to either 'oneShot' again
                            or 'normal'.  This option is provided
                            as a means of quelling the potential
                            promiscuous behavior that can be associated
                            with the sipStatusCodeNotif.

                triggered : This value is only readable and cannot be
                            set.  It reflects the default value of the
                            object or that the 'oneShot' case has
                            occurred and indicates the mode needs to
                            be reset to get further notifications.
                            The mode is reset by setting this object
                            to 'oneShot' or 'normal'."
          DEFVAL { triggered }
          ::= { sipStatusCodeNotifEntry 2 }



Lingle, et al.         Expires December 30, 2003               [Page 56]

Internet-Draft              SIP MIB Modules                    July 2003


      sipStatusCodeNotifThresh OBJECT-TYPE
          SYNTAX      Unsigned32
          MAX-ACCESS  read-write
          STATUS      current
          DESCRIPTION
               "This object specifies the number of response messages
                sent or received by this system that are considered
                excessive.  Based on crossing that threshold, a
                sipStatusCodeThreshExceededInNotif notification or a
                sipStatusCodeThreshExceededOutNotif will be sent.
                The sipStatusCodeThreshExceededIn/OutNotif can be
                used as an early warning mechanism in lieu of using
                sipStatusCodeNotif.

                Note that the configuration applied by this object
                will be applied equally to inbound and outbound
                response messages."
          DEFVAL { 500 }
          ::= { sipStatusCodeNotifEntry 3 }

      sipStatusCodeNotifInterval OBJECT-TYPE
          SYNTAX      Unsigned32
          UNITS       "seconds"
          MAX-ACCESS  read-write
          STATUS      current
          DESCRIPTION
               "This object specifies the time interval over which
                if sipCommonStatusCodeThresh is exceeded, with
                respect to sent or received messages, a
                sipStatusCodeThreshExceededIn/Out notification will
                be sent.

                Note that the configuration applied by this object
                will be applied equally to inbound and outbound
                response messages."
          DEFVAL { 60 }
          ::= { sipStatusCodeNotifEntry 4 }


      --
      -- Transaction Statistics
      --
      sipCurrentTransTable OBJECT-TYPE
          SYNTAX     SEQUENCE OF SipCurrentTransEntry
          MAX-ACCESS not-accessible
          STATUS     current
          DESCRIPTION
               "This table contains information on the transactions



Lingle, et al.         Expires December 30, 2003               [Page 57]

Internet-Draft              SIP MIB Modules                    July 2003


                currently awaiting definitive responses by each SIP
                entity in this system.

                This table does not apply to transaction stateless
                Proxy Servers."
          ::= { sipCommonStatsTrans 1 }

      sipCurrentTransEntry OBJECT-TYPE
          SYNTAX     SipCurrentTransEntry
          MAX-ACCESS not-accessible
          STATUS     current
          DESCRIPTION
               "Information on a particular SIP entity's current
                transactions.

                Each row represents those objects for a particular SIP
                entity present in this system.  applIndex is used to
                uniquely identify these instances of SIP entities and
                correlate them through the common framework of the
                NETWORK-SERVICES-MIB (RFC 2788)."
          INDEX { applIndex }
          ::= { sipCurrentTransTable 1 }

      SipCurrentTransEntry ::=
          SEQUENCE {
                   sipCurrentTransactions  Gauge32
          }

      sipCurrentTransactions OBJECT-TYPE
          SYNTAX     Gauge32 (0..4294967295)
          MAX-ACCESS read-only
          STATUS     current
          DESCRIPTION
               "This object contains the number of transactions awaiting
                definitive (non-1xx) response.  In the case of a forked
                request, all branches count as a single transaction
                corresponding to the entity identified by applIndex."
      ::= { sipCurrentTransEntry 1 }


      --
      -- SIP Retry Statistics
      --
      -- The counter objects in this group correspond directly to the
      -- retry timers supported in sipCommonCfgRetry group.  applIndex can
      -- be used to correlate the two groups.
      --
      sipCommonStatsRetryTable OBJECT-TYPE



Lingle, et al.         Expires December 30, 2003               [Page 58]

Internet-Draft              SIP MIB Modules                    July 2003


          SYNTAX     SEQUENCE OF SipCommonStatsRetryEntry
          MAX-ACCESS not-accessible
          STATUS     current
          DESCRIPTION
               "This table contains retry statistics objects applicable
                to each SIP entity in this system."
          ::= { sipCommonStatsRetry 1 }

      sipCommonStatsRetryEntry OBJECT-TYPE
          SYNTAX     SipCommonStatsRetryEntry
          MAX-ACCESS not-accessible
          STATUS     current
          DESCRIPTION
               "A row of retry statistics.

                Each row represents those objects for a particular SIP
                entity present in this system.  applIndex is used to
                uniquely identify these instances of SIP entities and
                correlate them through the common framework of the
                NETWORK-SERVICES-MIB (RFC 2788)."
          INDEX { applIndex }
          ::= { sipCommonStatsRetryTable 1 }

      SipCommonStatsRetryEntry ::=
          SEQUENCE {
                   sipStatsRetryInvites           Counter32,
                   sipStatsRetryByes              Counter32,
                   sipStatsRetryCancels           Counter32,
                   sipStatsRetryRegisters         Counter32,
                   sipStatsRetryOptions           Counter32,
                   sipStatsRetryFinalResponses    Counter32,
                   sipStatsRetryNonFinalResponses Counter32
          }

      sipStatsRetryInvites OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the total number of INVITE retries
                that have been sent by the SIP entity.   If the number of
                'first attempt' INVITES is of interest, subtract the value
                of this object from sipStatsInviteOuts."
          ::= { sipCommonStatsRetryEntry 1 }



      sipStatsRetryByes OBJECT-TYPE



Lingle, et al.         Expires December 30, 2003               [Page 59]

Internet-Draft              SIP MIB Modules                    July 2003


          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the total number of BYE retries that
                have been sent by the SIP entity. If the number of
                'first attempt' BYEs is of interest, subtract the value
                of this object from sipStatsByeOuts."
          ::= { sipCommonStatsRetryEntry 2 }

      sipStatsRetryCancels OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the total number of CANCEL retries
                that have been sent by the SIP entity. If the number of
                'first attempt' CANCELs is of interest, subtract the value
                of this object from sipStatsCancelOuts."
          ::= { sipCommonStatsRetryEntry 3 }

      sipStatsRetryRegisters OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the total number of REGISTER retries
                that have been sent by the SIP entity.  If the number of
                'first attempt' REGISTERSs is of interest, subtract the value
                of this object from sipStatsRegisterOuts."
          ::= { sipCommonStatsRetryEntry 4 }

      sipStatsRetryOptions OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the total number of OPTIONS retries
                that have been sent by the SIP entity.   If the number of
                'first attempt' OPTIONS is of interest, subtract the value
                of this object from sipStatsOptionsOuts."
          ::= { sipCommonStatsRetryEntry 5 }

      sipStatsRetryFinalResponses OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION



Lingle, et al.         Expires December 30, 2003               [Page 60]

Internet-Draft              SIP MIB Modules                    July 2003


               "This object reflects the total number of Final Response
                retries that have been sent by the SIP entity."
          ::= { sipCommonStatsRetryEntry 6 }

      sipStatsRetryNonFinalResponses OBJECT-TYPE
          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the total number of non-Final Response
                retries that have been sent by the SIP entity."
          ::= { sipCommonStatsRetryEntry 7 }


      --
      -- Retry Extensions Stats: support for extension methods
      --
      sipCommonStatsRetryExtMethodTable OBJECT-TYPE
          SYNTAX      SEQUENCE OF SipCommonStatsRetryExtMethodEntry
          MAX-ACCESS  not-accessible
          STATUS      current
          DESCRIPTION
               "This table contains retry statistics for each SIP
                extension method this entity supports."
          ::= { sipCommonStatsRetry 2 }

      sipCommonStatsRetryExtMethodEntry  OBJECT-TYPE
          SYNTAX      SipCommonStatsRetryExtMethodEntry
          MAX-ACCESS  not-accessible
          STATUS      current
          DESCRIPTION
               "This row contains retry statistics for
                a particular extension method.

                Each row represents those objects for a particular SIP
                entity present in this system.  applIndex is used to
                uniquely identify these instances of SIP entities and
                correlate them through the common framework of the
                NETWORK-SERVICES-MIB (RFC 2788)."
          AUGMENTS { sipExtMethodSupportedEntry }
          ::= { sipCommonStatsRetryExtMethodTable 1 }

      SipCommonStatsRetryExtMethodEntry ::=
          SEQUENCE {
             sipStatsRetryExtMethodRetries    Counter32
          }

      sipStatsRetryExtMethodRetries OBJECT-TYPE



Lingle, et al.         Expires December 30, 2003               [Page 61]

Internet-Draft              SIP MIB Modules                    July 2003


          SYNTAX      Counter32
          MAX-ACCESS  read-only
          STATUS      current
          DESCRIPTION
               "This object reflects the total number of retries
                sent by the SIP entity for a given extension method."
          ::= { sipCommonStatsRetryExtMethodEntry 1 }


      --
      -- Other Common Statistics
      --
      sipOtherStatsTable OBJECT-TYPE
          SYNTAX     SEQUENCE OF SipOtherStatsEntry
          MAX-ACCESS not-accessible
          STATUS     current
          DESCRIPTION
               "This table contains other common statistics supported by
                each SIP entity in this system."
          ::= { sipCommonStatsOther 1 }

      sipOtherStatsEntry OBJECT-TYPE
          SYNTAX     SipOtherStatsEntry
          MAX-ACCESS not-accessible
          STATUS     current


          DESCRIPTION
               "Information on a particular SIP entity's other common
                statistics.

                Each row represents those objects for a particular SIP
                entity present in this system.  applIndex is used to
                uniquely identify these instances of SIP entities and
                correlate them through the common framework of the
                NETWORK-SERVICES-MIB (RFC 2788)."
          INDEX { applIndex }
          ::= { sipOtherStatsTable 1 }

      SipOtherStatsEntry ::=
          SEQUENCE {
                   sipNumUnsupportedUris  Counter32
          }

      sipNumUnsupportedUris OBJECT-TYPE
          SYNTAX     Counter32
          MAX-ACCESS read-only
          STATUS     current



Lingle, et al.         Expires December 30, 2003               [Page 62]

Internet-Draft              SIP MIB Modules                    July 2003


          DESCRIPTION
               "Number of RequestURIs received with unsupported scheme.
                A server normally responds to such requests with a 400 Bad
                Request status code."
          ::= { sipOtherStatsEntry 1 }

      --
      -- Notification related objects
      --

      --
      -- Status code related notification objects.
      --
      sipStatusCodeNotifTo       OBJECT-TYPE
          SYNTAX     SnmpAdminString
          MAX-ACCESS accessible-for-notify
          STATUS     current
          DESCRIPTION
               "This object contains the value of the To header in the
                message containing the status code that caused the
                notification.  The header name will be part of
                this object value.
                For example, 'To: Watson ."
          ::= { sipCommonNotifObjects 1 }

      sipStatusCodeNotifFrom     OBJECT-TYPE
          SYNTAX     SnmpAdminString
          MAX-ACCESS accessible-for-notify
          STATUS     current
          DESCRIPTION
               "This object contains the value of the From header in the
                message containing the status code that caused the
                notification.  The header name will be part of
                this object value.
                For example, 'From: Watson '."
          ::= { sipCommonNotifObjects 2 }

      sipStatusCodeNotifCallId   OBJECT-TYPE
          SYNTAX     SnmpAdminString
          MAX-ACCESS accessible-for-notify
          STATUS     current
          DESCRIPTION
               "This object contains the value of the CallId in the
                message containing the status code that caused the
                notification.  The header name will be part of
                this object value.
                For example, 'Call-ID: 5551212@information.com'."
          ::= { sipCommonNotifObjects 3 }



Lingle, et al.         Expires December 30, 2003               [Page 63]

Internet-Draft              SIP MIB Modules                    July 2003


      sipStatusCodeNotifCSeq     OBJECT-TYPE
          SYNTAX     Unsigned32
          MAX-ACCESS accessible-for-notify
          STATUS     current
          DESCRIPTION
               "This object contains the CSeq value in the message
                containing the status code that caused the notification.
                The header name will be part of this object value.
                For example, 'CSeq: 1722 INVITE'."
          ::= { sipCommonNotifObjects 4 }

      --
      -- General notification related objects.
      --
      sipNotifApplIndex    OBJECT-TYPE
          SYNTAX     Unsigned32 (1..2147483647)
          MAX-ACCESS accessible-for-notify
          STATUS     current
          DESCRIPTION
               "This object contains the applIndex as described
               in RFC 2788. This object is created in order to
               allow a variable binding containing a value of
               applIndex in a notification."
          ::= { sipCommonNotifObjects 5 }

      sipNotifSequenceNumber OBJECT-TYPE
          SYNTAX     Unsigned32 (1..2147483647)
          MAX-ACCESS accessible-for-notify
          STATUS     current
          DESCRIPTION
               "This object contains a sequence number for each
                notification generated by this SIP entity.  Each
                notification SHOULD have a unique sequence number.
                A network manager can use this information to
                determine whether notifications from a particular
                SIP entity have been missed.  The value of this
                object MUST start at 1 and increase by one with
                each generated notification.  If a system restarts,
                the sequence number MAY start again from 1."
          ::= { sipCommonNotifObjects 6 }


      --
      -- Notifications
      --
      sipStatusCodeNotif         NOTIFICATION-TYPE
          OBJECTS {
                  sipNotifSequenceNumber,



Lingle, et al.         Expires December 30, 2003               [Page 64]

Internet-Draft              SIP MIB Modules                    July 2003


                  sipNotifApplIndex,
                  sipStatusCodeNotifTo,
                  sipStatusCodeNotifFrom,
                  sipStatusCodeNotifCallId,
                  sipStatusCodeNotifCSeq,
                  sipStatusCodeIns,
                  sipStatusCodeOuts
          }
          STATUS  current
          DESCRIPTION
               "Signifies that a specific status code has been sent
                or received by the system."
          ::= { sipCommonMIBNotifs 1 }

      sipStatusCodeThreshExceededInNotif NOTIFICATION-TYPE
          OBJECTS {
                  sipNotifSequenceNumber,
                  sipNotifApplIndex,
                  sipStatusCodeIns
          }
          STATUS  current
          DESCRIPTION
               "Signifies that a specific status code was found to
                have been received by the system enough to
                exceed the configured threshold.  This notification
                can be used as an early warning mechanism in lieu
                of using sipStatusCodeNotif."
          ::= { sipCommonMIBNotifs 2 }

      sipStatusCodeThreshExceededOutNotif NOTIFICATION-TYPE
          OBJECTS {
                  sipNotifSequenceNumber,
                  sipNotifApplIndex,
                  sipStatusCodeOuts
          }
          STATUS  current
          DESCRIPTION
               "Signifies that a specific status code was found to
                have been sent by the system enough to
                exceed the configured threshold.  This notification
                can be used as an early warning mechanism in lieu
                of using sipStatusCodeNotif."
          ::= { sipCommonMIBNotifs 3 }

      sipServiceColdStart NOTIFICATION-TYPE
          OBJECTS {
                  sipNotifSequenceNumber,
                  sipNotifApplIndex,



Lingle, et al.         Expires December 30, 2003               [Page 65]

Internet-Draft              SIP MIB Modules                    July 2003


                  sipServiceStartTime
          }
          STATUS  current
          DESCRIPTION
               "Signifies that the SIP service has reinitialized
                itself or started for the first time.  This SHOULD
                result from a hard 'down' to 'up' administrative
                status change.
                The configuration or behavior of the service
                MAY be altered."
          ::= { sipCommonMIBNotifs 4 }

      sipServiceWarmStart NOTIFICATION-TYPE
          OBJECTS {
                  sipNotifSequenceNumber,
                  sipNotifApplIndex,
                  sipServiceLastChange
          }
          STATUS  current
          DESCRIPTION
               "Signifies that the SIP service has reinitialized
                itself and is restarting after an adminstrative
                'reset'.  The configuration or behavior of the service
                MAY be altered."
          ::= { sipCommonMIBNotifs 5 }

      sipServiceStatusChanged NOTIFICATION-TYPE
          OBJECTS {
                  sipNotifSequenceNumber,
                  sipNotifApplIndex,
                  sipServiceLastChange,
                  sipServiceOperStatus
          }
          STATUS  current
          DESCRIPTION
               "Signifies that the SIP service operational status
                has changed."
          ::= { sipCommonMIBNotifs 6 }




      --
      -- Conformance
      --
      sipCommonMIBCompliances
        OBJECT IDENTIFIER ::= { sipCommonMIBConform 1 }
      sipCommonMIBGroups



Lingle, et al.         Expires December 30, 2003               [Page 66]

Internet-Draft              SIP MIB Modules                    July 2003


        OBJECT IDENTIFIER ::= { sipCommonMIBConform 2 }

      --
      -- Compliance Statements
      --
      sipCommonCompliance MODULE-COMPLIANCE
          STATUS     current
          DESCRIPTION
               "The compliance statement for SIP entities."

          MODULE -- this module
               MANDATORY-GROUPS { sipCommonConfigGroup,
                                  sipCommonStatsGroup }

          GROUP sipCommonConfigTimerGroup
          DESCRIPTION
               "This group is OPTIONAL.  A SIP entity can elect to
                not provide any timer configuration."

          GROUP sipCommonConfigTimerExtMethodGroup
          DESCRIPTION
               "This group is OPTIONAL.  A SIP entity can elect to
                not provide any extension method timer configuration.
                If implemented, the sipCommonConfigTimerGroup MUST also
                be implemented because of a dependency on sipCfgTimerT2."

          GROUP sipCommonConfigRetryGroup
          DESCRIPTION
               "This group is OPTIONAL.  A SIP entity can elect to
                not provide any retry configuration."

          GROUP sipCommonConfigRetryExtMethodGroup
          DESCRIPTION
               "This group is OPTIONAL.  A SIP entity can elect to
                not provide any extension method retry configuration."

          GROUP sipCommonStatsRetryGroup
          DESCRIPTION
               "This group is OPTIONAL.  A SIP entity can elect to
                not provide any retry statistics.  If implemented,
                the sipCommonConfigRetryGroup  MUST also be implemented."

          GROUP sipCommonStatsRetryExtMethodsGroup
          DESCRIPTION
               "This group is OPTIONAL.  A SIP entity can elect to
                not provide any extension method retry statistics.
                If implemented, the sipCommonConfigRetryExtMethodGroup
                MUST also be implemented."



Lingle, et al.         Expires December 30, 2003               [Page 67]

Internet-Draft              SIP MIB Modules                    July 2003


          GROUP sipCommonNotifGroup
          DESCRIPTION
               "This group is OPTIONAL.  A SIP entity can elect to
                not provide any notifications.  If implemented, the
                sipCommonStatusCodeNotifGroup and
                sipCommonNotifObjectsGroup MUST also be implemented."

          GROUP sipCommonStatusCodeNotifGroup
          DESCRIPTION
               "This group is OPTIONAL.  A SIP entity can elect to
                not provide any notifications.  If implemented, the
                sipCommonNotifGroup and sipCommonNotifObjectsGroup
                MUST also be implemented."

          GROUP sipCommonConfigExpiresGroup
          DESCRIPTION
               "This group is OPTIONAL.  A SIP entity can elect to
                not provide any Expires header configuration."

          GROUP sipCommonNotifObjectsGroup
          DESCRIPTION
               "This group is OPTIONAL.  A SIP entity can elect to
                not provide any notifications.  If implemented, the
                sipCommonStatusCodeNotifGroup and
                sipCommonNotifGroup MUST also be implemented."

          ::= { sipCommonMIBCompliances 1 }

      --
      -- Units of Conformance
      --
      sipCommonConfigGroup OBJECT-GROUP
          OBJECTS {
                  sipProtocolVersion,
                  sipServiceOperStatus,
                  sipServiceAdminStatus,
                  sipServiceStartTime,
                  sipServiceLastChange,
                  sipTransportRcv,
                  sipTransportSnd,
                  sipPortStatus,
                  sipUriSupported,
                  sipFtrSupported,
                  sipExtMethodName,
                  sipOrganization,
                  sipMaxSessions,
                  sipRequestUriHostMatching,
                  sipServiceNotifEnable,



Lingle, et al.         Expires December 30, 2003               [Page 68]

Internet-Draft              SIP MIB Modules                    July 2003


                  sipEntityType
          }
          STATUS  current
          DESCRIPTION
               "A collection of objects providing configuration common
                to all SIP enities."
          ::= { sipCommonMIBGroups 1 }

      sipCommonConfigTimerGroup OBJECT-GROUP
          OBJECTS {
                  sipCfgTimerA,
                  sipCfgTimerB,
                  sipCfgTimerC,
                  sipCfgTimerD,
                  sipCfgTimerE,
                  sipCfgTimerF,
                  sipCfgTimerG,
                  sipCfgTimerH,
                  sipCfgTimerI,
                  sipCfgTimerJ,
                  sipCfgTimerK,
                  sipCfgTimerT1,
                  sipCfgTimerT2,
                  sipCfgTimerT4
          }
          STATUS  current
          DESCRIPTION
               "A collection of objects providing timer configuration
                common to all SIP enities."
          ::= { sipCommonMIBGroups 2 }

      sipCommonConfigTimerExtMethodGroup OBJECT-GROUP
          OBJECTS {
                  sipCfgTimerExtMethodTimer
          }
          STATUS  current
          DESCRIPTION
               "A collection of objects providing extension method timer
                configuration."
          ::= { sipCommonMIBGroups 3 }

      sipCommonConfigRetryGroup OBJECT-GROUP
          OBJECTS {
                  sipCfgRetryInvite,
                  sipCfgRetryBye,
                  sipCfgRetryCancel,
                  sipCfgRetryRegister,
                  sipCfgRetryOptions,



Lingle, et al.         Expires December 30, 2003               [Page 69]

Internet-Draft              SIP MIB Modules                    July 2003


                  sipCfgRetryFinalResponse,
                  sipCfgRetryNonFinalResponse
          }
          STATUS  current
          DESCRIPTION
               "A collection of objects providing retry configuration
                common to all SIP enities."
          ::= { sipCommonMIBGroups 4 }

      sipCommonConfigRetryExtMethodGroup OBJECT-GROUP
          OBJECTS {
                  sipCfgRetryExtMethodRetry
          }
          STATUS  current
          DESCRIPTION
               "A collection of objects providing extension method retry
                configuration."
          ::= { sipCommonMIBGroups 5 }

      sipCommonStatsGroup OBJECT-GROUP
          OBJECTS {
                  sipSummaryInRequests,
                  sipSummaryOutRequests,
                  sipSummaryInResponses,
                  sipSummaryOutResponses,
                  sipSummaryTotalTransactions,
                  sipStatsInviteIns,
                  sipStatsInviteOuts,
                  sipStatsAckIns,
                  sipStatsAckOuts,
                  sipStatsByeIns,
                  sipStatsByeOuts,
                  sipStatsCancelIns,
                  sipStatsCancelOuts,
                  sipStatsOptionsIns,
                  sipStatsOptionsOuts,
                  sipStatsRegisterIns,
                  sipStatsRegisterOuts,
                  sipStatsExtMethodIns,
                  sipStatsExtMethodOuts,
                  sipStatsInfoClassIns,
                  sipStatsInfoClassOuts,
                  sipStatsSuccessClassIns,
                  sipStatsSuccessClassOuts,
                  sipStatsRedirClassIns,
                  sipStatsRedirClassOuts,
                  sipStatsReqFailClassIns,
                  sipStatsReqFailClassOuts,



Lingle, et al.         Expires December 30, 2003               [Page 70]

Internet-Draft              SIP MIB Modules                    July 2003


                  sipStatsServerFailClassIns,
                  sipStatsServerFailClassOuts,
                  sipStatsGlobalFailClassIns,
                  sipStatsGlobalFailClassOuts,
                  sipStatsOtherClassesIns,
                  sipStatsOtherClassesOuts,
                  sipStatusCodeIns,
                  sipStatusCodeOuts,
                  sipStatusCodeRowStatus,
                  sipCurrentTransactions,
                  sipNumUnsupportedUris
          }
          STATUS  current
          DESCRIPTION
               "A collection of objects providing statistics common
                to all SIP entities."
          ::= { sipCommonMIBGroups 6 }

      sipCommonStatsRetryGroup OBJECT-GROUP
          OBJECTS {
                   sipStatsRetryInvites,
                   sipStatsRetryByes,
                   sipStatsRetryCancels,
                   sipStatsRetryRegisters,
                   sipStatsRetryOptions,
                   sipStatsRetryFinalResponses,
                   sipStatsRetryNonFinalResponses
          }
          STATUS  current
          DESCRIPTION
               "A collection of objects providing retry statistics."
          ::= { sipCommonMIBGroups 7 }

      sipCommonStatsRetryExtMethodsGroup OBJECT-GROUP
          OBJECTS {
                  sipStatsRetryExtMethodRetries
          }
          STATUS  current
          DESCRIPTION
               "A collection of objects providing extension method retry
                statistics."
          ::= { sipCommonMIBGroups 8 }

      sipCommonNotifGroup NOTIFICATION-GROUP
          NOTIFICATIONS {
                  sipStatusCodeNotif,
                  sipStatusCodeThreshExceededInNotif,
                  sipStatusCodeThreshExceededOutNotif,



Lingle, et al.         Expires December 30, 2003               [Page 71]

Internet-Draft              SIP MIB Modules                    July 2003


                  sipServiceColdStart,
                  sipServiceWarmStart,
                  sipServiceStatusChanged
          }
          STATUS  current
          DESCRIPTION
               "A collection of notifications common to all SIP entities."
          ::= { sipCommonMIBGroups 9 }

      sipCommonStatusCodeNotifGroup OBJECT-GROUP
          OBJECTS {
                  sipStatusCodeNotifSend,
                  sipStatusCodeNotifEmitMode,
                  sipStatusCodeNotifThresh,
                  sipStatusCodeNotifInterval
         }
          STATUS  current
          DESCRIPTION
               "A collection of objects related to controlling and attribution
                of notifications common to all SIP entities."
          ::= { sipCommonMIBGroups 10 }

      sipCommonConfigExpiresGroup OBJECT-GROUP
          OBJECTS {
                   sipCfgExpiresInvite,
                   sipCfgExpiresRegister,
                   sipCfgExpiresHeaderMethod,
                   sipCfgExpiresHeaderValue,
                   sipCfgExpiresStatusCodeStatus
          }
          STATUS  current
          DESCRIPTION
               "A collection of objects providing configuration
                related to Expires header."
          ::= { sipCommonMIBGroups 11 }

      sipCommonNotifObjectsGroup OBJECT-GROUP
          OBJECTS {
                  sipStatusCodeNotifTo,
                  sipStatusCodeNotifFrom,
                  sipStatusCodeNotifCallId,
                  sipStatusCodeNotifCSeq,
                  sipNotifApplIndex,
                  sipNotifSequenceNumber
          }
          STATUS current
          DESCRIPTION
               "A collection of accessible-for-notify objects



Lingle, et al.         Expires December 30, 2003               [Page 72]

Internet-Draft              SIP MIB Modules                    July 2003


                related to the notification defined in this
                MIB module."
          ::= { sipCommonMIBGroups 12 }

      END


7.3 SIP User Agent MIB Module

      SIP-UA-MIB DEFINITIONS ::= BEGIN

      IMPORTS
           MODULE-IDENTITY,
           OBJECT-TYPE,
           Unsigned32,
           mib-2
                FROM SNMPv2-SMI

           MODULE-COMPLIANCE,
           OBJECT-GROUP
                FROM SNMPv2-CONF

           RowStatus
                FROM SNMPv2-TC

           applIndex
                FROM NETWORK-SERVICES-MIB

           InetAddressType,
           InetAddress
                FROM INET-ADDRESS-MIB;


      sipUAMIB MODULE-IDENTITY
           LAST-UPDATED   "200307300000Z"
           ORGANIZATION   "IETF SIP Working Group, SIP MIB Team"
           CONTACT-INFO
                   "SIP WG email: sip@ietf.org

                    Co-editor  Kevin Lingle
                               Cisco Systems, Inc.
                    postal:    7025 Kit Creek Road
                               P.O. Box 14987
                               Research Triangle Park, NC 27709
                               USA
                    email:     klingle@cisco.com
                    phone:     +1 919 392 2029




Lingle, et al.         Expires December 30, 2003               [Page 73]

Internet-Draft              SIP MIB Modules                    July 2003


                    Co-editor  Joon Maeng
                               ipDialog, Inc.
                    postal:    7701 N. Lamar Blvd., Suite 304
                               Austin, TX 78752-1023
                               USA
                    email:     jmaeng@ipdialog.com
                    phone:     +1 512 371 1770

                    Co-editor  Dave Walker
                               SS8 Networks, Inc.
                    postal:    495 March Road
                               Kanata, ON K2K 3G1
                               Canada
                    email:     drwalker@ss8.com
                    phone:     +1 613 592 2100

                    Co-editor  Jean-Francois Mule
                               CableLabs
                    postal:    400 Centennial Parkway
                               Louisville, CO 80027
                               USA
                    email:     jf.mule@cablelabs.com
                    phone:     +1 303 661 3708  "
           DESCRIPTION
                "Session Initiation Protocol (SIP) User Agent (UA)
                 MIB module.

                 SIP is an application-layer signalling protocol for
                 creating, modifying and terminating multimedia
                 sessions with one or more participants. These sessions
                 include Internet multimedia conferences and Internet
                 telephone calls.  SIP is defined in RFC 3261 (June
                 2002).

                 A User Agent is an application that contains both a
                 User Agent Client (UAC) and a User Agent Server (UAS).
                 A UAC is an application that initiates a SIP request.
                 A UAS is an application that contacts the user when a
                 SIP request is received and that returns a response on
                 behalf of the user.  The response accepts, rejects, or
                 redirects the request.

                 Copyright (C) The Internet Society (2003). This version
                 of this MIB module is part of RFC XXXX; see the RFC
                 itself for full legal notices."
   -- RFC Ed: replace XXXX with actual RFC number and remove this note
           REVISION        "200307300000Z"
           DESCRIPTION



Lingle, et al.         Expires December 30, 2003               [Page 74]

Internet-Draft              SIP MIB Modules                    July 2003


                "Initial version of the IETF SIP-UA-MIB module.
                 This version published as part of RFC XXXX."
   -- RFC Ed: replace XXXX with actual RFC number and remove this note
           ::= { mib-2 xx }
   -- RFC Ed: replace xx with actual IANA assigned number
   -- RFC Ed: and remove these notes

      -- Top-Level Components of this MIB.
      sipUAMIBObjects       OBJECT IDENTIFIER ::= { sipUAMIB 1 }
      sipUAMIBConform       OBJECT IDENTIFIER ::= { sipUAMIB 2 }

      --
      -- This MIB contains objects related to SIP User Agents.
      --
      sipUACfgSipServer     OBJECT IDENTIFIER ::= { sipUAMIBObjects 1 }

      --
      -- SIP Server Configuration
      --
      sipUACfgSipServerTable OBJECT-TYPE
          SYNTAX      SEQUENCE OF SipUACfgSipServerEntry
          MAX-ACCESS not-accessible
          STATUS     current
          DESCRIPTION
               "This table contains SIP server configuration objects
                applicable to each SIP user agent in this system."
          ::= { sipUACfgSipServer 1 }

      sipUACfgSipServerEntry OBJECT-TYPE
          SYNTAX     SipUACfgSipServerEntry
          MAX-ACCESS not-accessible
          STATUS     current
          DESCRIPTION
               "A row of server configuration.

                Each row represents those objects for a particular SIP
                user agent present in this system.  applIndex is used to
                uniquely identify these instances of SIP user agents and
                correlate them through the common framework of the
                NETWORK-SERVICES-MIB (RFC 2788). The same value of
                applIndex used in the corresponding SIP-COMMON-MIB is
                used here.
                The objects in this table entry SHOULD be non-volatile
                and their value SHOULD be kept at reboot."
          INDEX { applIndex, sipUACfgSipServerIndex }
          ::= { sipUACfgSipServerTable 1 }

      SipUACfgSipServerEntry ::=



Lingle, et al.         Expires December 30, 2003               [Page 75]

Internet-Draft              SIP MIB Modules                    July 2003


          SEQUENCE {
                   sipUACfgSipServerIndex       Unsigned32,
                   sipUACfgSipServerAddrType    InetAddressType,
                   sipUACfgSipServerAddr        InetAddress,
                   sipUACfgSipServerStatus      RowStatus
          }

      sipUACfgSipServerIndex OBJECT-TYPE
          SYNTAX     Unsigned32
          MAX-ACCESS not-accessible
          STATUS     current
          DESCRIPTION
               "A unique identifier of a server address when
                multiple addresses are configured by the SIP entity.
                If one address isn't reachable, then another can
                be tried."
          ::= { sipUACfgSipServerEntry 1 }

      sipUACfgSipServerAddrType OBJECT-TYPE
          SYNTAX     InetAddressType
          MAX-ACCESS read-create
          STATUS     current
          DESCRIPTION
               "This object specifies the type of address contained
                in the associated instance of sipUACfgSipServerAddr."
          REFERENCE "INET-ADDRESS-MIB (RFC 3291)"
          DEFVAL { ipv4 }
          ::= { sipUACfgSipServerEntry 2 }

      sipUACfgSipServerAddr OBJECT-TYPE
          SYNTAX     InetAddress
          MAX-ACCESS read-create
          STATUS     current
          DESCRIPTION
               "This object specifies the address of a SIP server
                this user agent will use to proxy/redirect calls."
          REFERENCE "INET-ADDRESS-MIB (RFC 3291)"
          ::= { sipUACfgSipServerEntry 3 }

      sipUACfgSipServerStatus OBJECT-TYPE
          SYNTAX     RowStatus
          MAX-ACCESS read-create
          STATUS     current
          DESCRIPTION
               "This object is used to control rows in this table.

                'active'        : the row's information is completely
                                  populated and that information is



Lingle, et al.         Expires December 30, 2003               [Page 76]

Internet-Draft              SIP MIB Modules                    July 2003


                                  being used by the user agent.

                'notInService'  : the row's address is not being used
                                  by the user agent, but will remain in
                                  the table.

                'notReady'      : key information is missing thus,
                                  preventing the row from being made
                                  'active' (eg, no address specified).

                'createAndGo'   : only allowed if the manager also
                                  provides a varbind for
                                  sipUACfgSipServerAddr object in the
                                  same set operation.

                'createAndWait' : not applicable.

                'destroy'       : the row's address will no longer be used
                                  by the user agent and the row will be
                                  removed from the table."
          ::= { sipUACfgSipServerEntry 4 }

      --
      -- Conformance
      --
      sipUAMIBCompliances
        OBJECT IDENTIFIER ::= { sipUAMIBConform 1 }
      sipUAMIBGroups
        OBJECT IDENTIFIER ::= { sipUAMIBConform 2 }

      --
      -- Compliance Statements
      --
      sipUACompliance MODULE-COMPLIANCE
          STATUS     current
          DESCRIPTION
               "The compliance statement for SIP entities."
          MODULE -- this module
               MANDATORY-GROUPS { sipUAConfigGroup }

          ::= { sipUAMIBCompliances 1 }

      --
      -- Units of Conformance
      --
      sipUAConfigGroup OBJECT-GROUP
          OBJECTS {
                  sipUACfgSipServerAddrType,



Lingle, et al.         Expires December 30, 2003               [Page 77]

Internet-Draft              SIP MIB Modules                    July 2003


                  sipUACfgSipServerAddr,
                  sipUACfgSipServerStatus
          }
          STATUS  current
          DESCRIPTION
               "A collection of objects providing configuration for
                SIP User Agents."
          ::= { sipUAMIBGroups 1 }

      END


7.4 SIP Server (Registrar, Redirect & Proxy Server) MIB Module

         SIP-SERVER-MIB DEFINITIONS ::= BEGIN

         IMPORTS
              MODULE-IDENTITY,
              OBJECT-TYPE,
              Counter32,
              Unsigned32,
              Gauge32,
              mib-2
                   FROM SNMPv2-SMI

              RowStatus,
              TruthValue,
              TimeStamp, DateAndTime
                   FROM SNMPv2-TC

              MODULE-COMPLIANCE,
              OBJECT-GROUP
                   FROM SNMPv2-CONF

              SnmpAdminString
                   FROM SNMP-FRAMEWORK-MIB

              applIndex
                   FROM NETWORK-SERVICES-MIB

              InetAddressType,
              InetAddress
                   FROM INET-ADDRESS-MIB;

         sipServerMIB MODULE-IDENTITY
              LAST-UPDATED   "200307300000Z"
              ORGANIZATION   "IETF SIP Working Group, SIP MIB Team"
              CONTACT-INFO



Lingle, et al.         Expires December 30, 2003               [Page 78]

Internet-Draft              SIP MIB Modules                    July 2003


                      "SIP WG email: sip@ietf.org

                       Co-editor  Kevin Lingle
                                  Cisco Systems, Inc.
                       postal:    7025 Kit Creek Road
                                  P.O. Box 14987
                                  Research Triangle Park, NC 27709
                                  USA
                       email:     klingle@cisco.com
                       phone:     +1 919 392 2029

                       Co-editor  Joon Maeng
                                  ipDialog, Inc.
                       postal:    7701 N. Lamar Blvd., Suite 304
                                  Austin, TX 78752-1023
                                  USA
                       email:     jmaeng@ipdialog.com
                       phone:     +1 512 371 1770

                       Co-editor  Dave Walker
                                  SS8 Networks, Inc.
                       postal:    495 March Road
                                  Kanata, ON K2K 3G1
                                  Canada
                       email:     drwalker@ss8.com
                       phone:     +1 613 592 2100

                       Co-editor  Jean-Francois Mule
                                  CableLabs
                       postal:    400 Centennial Parkway
                                  Louisville, CO 80027
                                  USA
                       email:     jf.mule@cablelabs.com
                       phone:     +1 303 661 3708  "
              DESCRIPTION
                   "Session Initiation Protocol (SIP) Server MIB module.

                    SIP is an application-layer signaling protocol for
                    creating, modifying and terminating multimedia
                    sessions with one or more participants. These sessions
                    include Internet multimedia conferences and Internet
                    telephone calls.  SIP is defined in RFC 3261 (June
                    2002).

                    This MIB is defined for the management of SIP Proxy,
                    Redirect, and Registrar Servers.

                    A Proxy Server acts as both a client and a server.



Lingle, et al.         Expires December 30, 2003               [Page 79]

Internet-Draft              SIP MIB Modules                    July 2003


                    It accepts requests from other clients, either
                    responding to them or passing them on to other
                    servers, possibly after modification.

                    A Redirect Server accepts requests from clients and
                    returns zero or more addresses to that client.
                    Unlike a User Agent Server it does not accept calls.

                    A Registrar is a server that accepts REGISTER
                    requests.  A Registrar is typically co-located with a
                    Proxy or Redirect Server.

                    Copyright (C) The Internet Society (2003).
                    This version of this MIB module is part of RFC XXXX;
                    see the RFC itself for full legal notices."
   -- RFC Ed: replace XXXX with actual RFC number and remove this note
              REVISION        "200307300000Z"
              DESCRIPTION
                   "Initial version of the IETF SIP-SERVER-MIB module.
                    This version published as part of RFC XXXX."
   -- RFC Ed: replace XXXX with actual RFC number and remove this note
           ::= { mib-2 yy }
   -- RFC Ed: replace yy with actual IANA assigned number and remove this note

         -- Top-Level Components of this MIB.
         sipServerMIBObjects  OBJECT IDENTIFIER ::= { sipServerMIB 1 }
         sipServerMIBConform  OBJECT IDENTIFIER ::= { sipServerMIB 2 }

         --
         -- These groups contain objects common to all SIP servers.
         --
         sipServerCfg   OBJECT IDENTIFIER ::= { sipServerMIBObjects 1 }
         sipServerStats OBJECT IDENTIFIER ::= { sipServerMIBObjects 2 }

         --
         -- Common Server Configuration Objects
         --
         sipServerCfgTable OBJECT-TYPE
             SYNTAX     SEQUENCE OF SipServerCfgEntry
             MAX-ACCESS not-accessible
             STATUS     current
             DESCRIPTION
                  "This table contains configuration objects applicable
                   to SIP Redirect and Proxy Servers."
             ::= { sipServerCfg 1 }

         sipServerCfgEntry OBJECT-TYPE
             SYNTAX     SipServerCfgEntry



Lingle, et al.         Expires December 30, 2003               [Page 80]

Internet-Draft              SIP MIB Modules                    July 2003


             MAX-ACCESS not-accessible
             STATUS     current
             DESCRIPTION
                  "A row of common configuration.

                   Each row represents those objects for a particular SIP
                   server present in this system.  applIndex is used to
                   uniquely identify these instances of SIP servers and
                   correlate them through the common framework of the
                   NETWORK-SERVICES-MIB (RFC 2788). The same value of
                   applIndex used in the corresponding SIP-COMMON-MIB
                   is used here.
                   The objects in this table entry SHOULD be non-volatile
                   and their value SHOULD be kept at reboot."
             INDEX { applIndex }
             ::= { sipServerCfgTable 1 }

         SipServerCfgEntry ::=
             SEQUENCE {
                      sipServerHostAddrType           InetAddressType,
                      sipServerHostAddr               InetAddress
             }

         sipServerHostAddrType OBJECT-TYPE
             SYNTAX     InetAddressType
             MAX-ACCESS read-write
             STATUS     current
             DESCRIPTION
                  "The type of Internet address by which the SIP server
                   is reachable."
             REFERENCE
                   "RFC 3261, Section 19.1.1"
             ::= { sipServerCfgEntry 1 }

         sipServerHostAddr OBJECT-TYPE
             SYNTAX     InetAddress
             MAX-ACCESS read-write
             STATUS     current
             DESCRIPTION
                  "This is the host portion of a SIP URI that is assigned
                   to the SIP server.  It MAY contain a fully qualified
                   domain name, or an IP address.  The length of the value
                   will depend on the type of address specified.
                   sipServerHostAddrType formalizes the type of address
                   given by this object.  It is the users responsibility
                   to maintain consistency between this object and the
                   type specified by sipServerHostAddrType."
             REFERENCE



Lingle, et al.         Expires December 30, 2003               [Page 81]

Internet-Draft              SIP MIB Modules                    July 2003


                   "RFC 3261, Section 19.1.1"
             ::= { sipServerCfgEntry 2 }

         --
         -- This group contains MIB objects related to SIP Proxy Servers.
         --
         sipProxyCfg      OBJECT IDENTIFIER ::= { sipServerMIBObjects 3 }
         sipProxyStats    OBJECT IDENTIFIER ::= { sipServerMIBObjects 4 }

         --
         -- Proxy Server Configuration
         --
         sipProxyCfgTable OBJECT-TYPE
             SYNTAX     SEQUENCE OF SipProxyCfgEntry
             MAX-ACCESS not-accessible
             STATUS     current
             DESCRIPTION
                  "This table contains configuration objects applicable
                   to SIP Proxy Servers."
             ::= { sipProxyCfg 1 }

         sipProxyCfgEntry OBJECT-TYPE
             SYNTAX     SipProxyCfgEntry
             MAX-ACCESS not-accessible
             STATUS     current
             DESCRIPTION
                  "A row of common proxy configuration.

                   Each row represents those objects for a particular SIP
                   server present in this system.  applIndex is used to
                   uniquely identify these instances of SIP servers and
                   correlate them through the common framework of the
                   NETWORK-SERVICES-MIB (RFC 2788).  The same value of
                   applIndex used in the corresponding SIP-COMMON-MIB
                   is used here.
                   The objects in this table entry SHOULD be non-volatile
                   and their value SHOULD be kept at reboot."
             INDEX { applIndex }
             ::= { sipProxyCfgTable 1 }

         SipProxyCfgEntry ::=
             SEQUENCE {
                      sipRequestMaxExpires         Unsigned32,
                      sipProxyStatefulness         INTEGER,
                      sipProxySendsCancel          TruthValue,
                      sipProxyForwardAll1xx        TruthValue,
                      sipProxyRecursion            TruthValue,
                      sipProxyProvideAlternatives  TruthValue,



Lingle, et al.         Expires December 30, 2003               [Page 82]

Internet-Draft              SIP MIB Modules                    July 2003


                      sipProxyRecordRoute          TruthValue,
                      sipProxyAuthMethod           BITS,
                      sipProxyAuthRealm            SnmpAdminString,
                      sipProxyNonceLifeTime        Unsigned32
             }

         sipRequestMaxExpires OBJECT-TYPE
             SYNTAX     Unsigned32 (0..4294967295)
             UNITS      "seconds"
             MAX-ACCESS read-write
             STATUS     current
             DESCRIPTION
                  "This object specifies the maximum duration that a SIP
                   server will accept from a client in the Expires
                   header."
             REFERENCE
                 "RFC 3261 Section 20.19"
             ::= { sipProxyCfgEntry 1 }

         sipProxyStatefulness OBJECT-TYPE
             SYNTAX     INTEGER {
                                 stateless(1),
                                 transactionStateful(2),
                                 callStateful(3)
                         }
             MAX-ACCESS read-write
             STATUS     current
             DESCRIPTION
                  "This object specifies the default mode of operation for
                   the Proxy Server entity.

                   A stateless proxy is a logical entity that does not
                   maintain the client or server transaction state machines
                   when it processes requests. A stateless proxy forwards
                   every request it receives downstream and every response
                   it receives upstream. If the value of this object is
                   stateless(1), the proxy defaults to stateless
                   operations.

                   A transaction stateful proxy, or simply a 'stateful
                   proxy', is a logical entity that maintains the client
                   and server transaction state machines during the
                   processing of a request. A (transaction) stateful proxy
                   is not the same as a call stateful proxy. If the value
                   if this object is transactionStateful(2), the proxy is
                   stateful on a transaction basis.

                   A call stateful proxy is a logical entity if it retains



Lingle, et al.         Expires December 30, 2003               [Page 83]

Internet-Draft              SIP MIB Modules                    July 2003


                   state for a dialog from the initiating INVITE to the
                   terminating BYE request.  A call stateful proxy is
                   always transaction stateful, but the converse is not
                   necessarily true. If the value of this object is
                   callStateful(3), the proxy is call stateful."
             REFERENCE
                   "RFC 3261, Section 16"
             ::= { sipProxyCfgEntry 2 }

         sipProxySendsCancel OBJECT-TYPE
             SYNTAX     TruthValue
             MAX-ACCESS read-write
             STATUS     current
             DESCRIPTION
                  "This object specifies whether or not a forking proxy sends
                   CANCEL on outstanding branch requests after receiving a
                   2xx or 6xx, or after the request times-out.

                   If the value of this object is 'true', the server sends
                   a CANCELs on branches where no definitive response has been
                   received.  If 'false', the proxy does not send CANCELs."
             REFERENCE
                   "RFC 3261, Section 10"
             ::= { sipProxyCfgEntry 3 }


         sipProxyForwardAll1xx OBJECT-TYPE
             SYNTAX     TruthValue
             MAX-ACCESS read-write
             STATUS     current
             DESCRIPTION
                  "This object specifies whether or not the proxy forwards
                   all 1xx responses, except the 100 Trying response,
                   upstream towards the source of the request.

                   If the value of this object is 'true', the 1xx responses
                   are sent.  If the value is 'false', duplicate 1xx
                   responses are not sent upstream."
             ::= { sipProxyCfgEntry 4 }

         sipProxyRecursion OBJECT-TYPE
             SYNTAX     TruthValue
             MAX-ACCESS read-write
             STATUS     current
             DESCRIPTION
                  "This object specifies whether or not the Proxy performs
                   recursive search on the Contacts provided in 3xx
                   redirects.



Lingle, et al.         Expires December 30, 2003               [Page 84]

Internet-Draft              SIP MIB Modules                    July 2003


                   If the value of this object is 'true', a recursive search
                   is performed.  If the value is 'false', no search is
                   performed, the 3xx response is sent upstream towards the
                   source of the request."
             REFERENCE
                 "RFC 3261 Sections 16.5 and 16.6"
             ::= { sipProxyCfgEntry 5 }

         sipProxyProvideAlternatives OBJECT-TYPE
             SYNTAX     TruthValue
             MAX-ACCESS read-write
             STATUS     current
             DESCRIPTION
                  "The object specifies whether or not the Server provides
                   alternative Contacts in 3xx and 485 responses.

                   If the value of this object is 'true', the server inserts a
                   list of alternative URIs into a Contact header where the
                   request Originator may possibly find the desired called
                   party.  If the value is 'false', the server doesn't add
                   Contact information to 3xx and 485 responses.

                   Note that the policies of a server MAY limit the
                   particular alternatives that are returned when this object
                   is set to 'true'."
             REFERENCE
                   "RFC 3261, Sections 13.2.2.2 and 16.5"
             DEFVAL { true }
             ::= { sipProxyCfgEntry 6 }

         sipProxyRecordRoute OBJECT-TYPE
             SYNTAX     TruthValue
             MAX-ACCESS read-write
             STATUS     current
             DESCRIPTION
                  "This object specifies whether or not the proxy adds itself
                   to the Record-Route header as a default action.  This
                   header is used to list the proxies that insist on being in
                   the signaling path for subsequent requests related to the
                   call-leg.

                   If the value of this object is 'true', the proxy adds itself
                   to the end of the Record-Route header, creating the header
                   if required.  If the value is 'false', the proxy does
                   not add itself to the Record-Route header."
             REFERENCE
                   "RFC 3261, Section 20.30"
             ::= { sipProxyCfgEntry 7 }



Lingle, et al.         Expires December 30, 2003               [Page 85]

Internet-Draft              SIP MIB Modules                    July 2003


         --
         -- Security
         --
         sipProxyAuthMethod OBJECT-TYPE
             SYNTAX     BITS {
                                none(0),
                                tls(1),
                                digest(2),
                                smime(3)
                        }
             MAX-ACCESS read-write
             STATUS     current
             DESCRIPTION
                  "This object specifies the authentication methods that
                   MAY be used to authenticate request originators.

                   bit 0  no authentication is performed
                   bit 1  TLS is used
                   bit 2  HTTP Digest is used
                   bit 3  S/MIME is used."
             REFERENCE
                 "RFC 3261 Sections 22, 23, 26, 26.2.3"
             ::= { sipProxyCfgEntry 8 }

         sipProxyAuthRealm OBJECT-TYPE
             SYNTAX     SnmpAdminString
             MAX-ACCESS read-write
             STATUS     current
             DESCRIPTION
                  "This object specifies the realm used in Proxy-Authenticate
                   headers.  Note that this MAY need to be stored per user."
             REFERENCE
                  "RFC 3261, Section 22.1"
             ::= { sipProxyCfgEntry 9 }

         sipProxyNonceLifeTime OBJECT-TYPE
             SYNTAX Unsigned32 (0..65535)
             UNITS "milliseconds"
             MAX-ACCESS read-write
             STATUS current
             DESCRIPTION
                  "This object specifies the lifetime of a given nonce. A
                   nonce is a server specified value whose contents are
                   opaque to the entity being authenticated and which is used
                   in calculating authentication data.  If this object has a
                   value of zero, then nonces are not reused."
             ::= { sipProxyCfgEntry 10 }




Lingle, et al.         Expires December 30, 2003               [Page 86]

Internet-Draft              SIP MIB Modules                    July 2003


         --
         -- Proxy Server Statistics
         --
         sipProxyStatsTable OBJECT-TYPE
             SYNTAX     SEQUENCE OF SipProxyStatsEntry
             MAX-ACCESS not-accessible
             STATUS     current
             DESCRIPTION
                  "This table contains the statistics objects applicable
                   to all SIP Proxy Servers in this system."
             ::= { sipProxyStats 1 }

         sipProxyStatsEntry OBJECT-TYPE
             SYNTAX     SipProxyStatsEntry
             MAX-ACCESS not-accessible
             STATUS     current
             DESCRIPTION
                  "A row of summary statistics.

                   Each row represents those objects for a particular SIP
                   server present in this system.  applIndex is used to
                   uniquely identify these instances of SIP servers and
                   correlate them through the common framework of the
                   NETWORK-SERVICES-MIB (RFC 2788).  The same value of
                   applIndex used in the corresponding SIP-COMMON-MIB
                   is used here."
             INDEX { applIndex }
             ::= { sipProxyStatsTable 1 }

         SipProxyStatsEntry ::=
             SEQUENCE {
                      sipNumProxyRequireFailures Counter32
             }

         sipNumProxyRequireFailures OBJECT-TYPE
             SYNTAX     Counter32
             MAX-ACCESS read-only
             STATUS     current
             DESCRIPTION
                  "This object contains the number of occurrences of
                   unsupported options being specified in received Proxy-
                   Require headers.  Such occurrences result in a 420 Bad
                   Extension status code being
                   returned."
             ::= { sipProxyStatsEntry 1 }

         --
         -- This group contains MIB objects related to SIP Registrars.



Lingle, et al.         Expires December 30, 2003               [Page 87]

Internet-Draft              SIP MIB Modules                    July 2003


         --
         sipRegCfg         OBJECT IDENTIFIER ::= { sipServerMIBObjects 5 }
         sipRegStats       OBJECT IDENTIFIER ::= { sipServerMIBObjects 6 }

         --
         -- Registrar Configuration
         --
         sipRegCfgTable OBJECT-TYPE
             SYNTAX     SEQUENCE OF SipRegCfgEntry
             MAX-ACCESS not-accessible
             STATUS     current
             DESCRIPTION
                  "This table contains configuration objects applicable
                   SIP Registrars."
             ::= { sipRegCfg 1 }

         sipRegCfgEntry OBJECT-TYPE
             SYNTAX     SipRegCfgEntry
             MAX-ACCESS not-accessible
             STATUS     current
             DESCRIPTION
                  "A row of common Registrar configuration.

                   Each row represents those objects for a particular SIP
                   server present in this system.  applIndex is used to
                   uniquely identify these instances of SIP servers and
                   correlate them through the common framework of the
                   NETWORK-SERVICES-MIB (RFC 2788). The same value of
                   applIndex used in the corresponding SIP-COMMON-MIB
                   is used here."
             INDEX { applIndex }
             ::= { sipRegCfgTable 1 }

         SipRegCfgEntry ::=
             SEQUENCE {
                      sipRegAllowThirdParty           TruthValue,
                      sipRegMaxContactExpiryDuration  Unsigned32,
                      sipRegMaxUsers                  Unsigned32,
                      sipRegCurrentUsers              Gauge32,
                      sipRegDfltRegActiveInterval     Unsigned32
             }

         sipRegAllowThirdParty OBJECT-TYPE
             SYNTAX     TruthValue
             MAX-ACCESS read-write
             STATUS     current
             DESCRIPTION
                  "This object specifies whether or not the Registrar SHOULD



Lingle, et al.         Expires December 30, 2003               [Page 88]

Internet-Draft              SIP MIB Modules                    July 2003


                   allow third party registrations. In third-party
                   registration, the entity issuing the request (in the
                   From header) is different from the entity being registered
                   (in the To header) to whom the provided Contact information
                   applies.

                   If the value of thsipRegAllowThirdPartyis object is 'true',
                   the Registrar allows third-party registrations.  If the
                   value is 'false', third-party registrations are rejected:
                   a 403 (Forbidden) status code is returned to the requester.
                   This object SHOULD be non-volatile and its value SHOULD
                   be kept at reboot."
             REFERENCE
                  "RFC 3261, Section 10.2"
             ::= { sipRegCfgEntry 1 }

         sipRegMaxContactExpiryDuration OBJECT-TYPE
             SYNTAX     Unsigned32 (0..4294967295)
             UNITS      "seconds"
             MAX-ACCESS read-write
             STATUS     current
             DESCRIPTION
                  "This object specifies the maximum expiry that may be
                   requested by a User Agent for a particular Contact.
                   User Agents can specify expiry using either an Expiry
                   header in a REGISTER request, or using an Expires parameter
                   in a Contact header in a REGISTER request.  If the value
                   requested by the User Agent is greater than the value
                   of this object, then the contact information is given the
                   duration specified by this object, and that duration
                   is indicated to the User Agent in the response."
             DEFVAL { 4294967295 }
             ::= { sipRegCfgEntry 2 }

         sipRegMaxUsers OBJECT-TYPE
             SYNTAX     Unsigned32 (1..4294967295)
             MAX-ACCESS read-only
             STATUS     current
             DESCRIPTION
                  "This object specifies the maximum number of users that
                   the Registrar supports.  The current number of users is
                   reflected by sipRegCurrentUsers."
             ::= { sipRegCfgEntry 3 }

         sipRegCurrentUsers OBJECT-TYPE
             SYNTAX     Gauge32 (0..4294967295)
             MAX-ACCESS read-only
             STATUS     current



Lingle, et al.         Expires December 30, 2003               [Page 89]

Internet-Draft              SIP MIB Modules                    July 2003


             DESCRIPTION
                  "This object specifies the number of users currently
                   configured on the Registrar."
             ::= { sipRegCfgEntry 4 }

         sipRegDfltRegActiveInterval OBJECT-TYPE
             SYNTAX     Unsigned32 (1..4294967295)
             UNITS      "seconds"
             MAX-ACCESS read-write
             STATUS     current
             DESCRIPTION
                  "This object specifies the default time interval the
                   Registrar considers registrations to be active.  The
                   value is used to compute the Expires header in the
                   REGISTER response.  If a user agent requests a time
                   interval shorter than specified by this object, the
                   Registrar SHOULD honor that request.  If a Contact
                   entry does not have an 'expires' parameter, the value
                   of the Expires header field is used instead. If a
                   Contact entry has no 'expires' parameter and no the
                   Expires header field is present, the value of this
                   object is used as the default value.
                   This object SHOULD be non-volatile and its value SHOULD
                   be kept at reboot."
             REFERENCE "RFC 3261, Section 10.2"
             ::= { sipRegCfgEntry 5 }


         --
         -- Per User Information
         --
         sipRegUserTable OBJECT-TYPE
             SYNTAX     SEQUENCE OF SipRegUserEntry
             MAX-ACCESS not-accessible
             STATUS     current
             DESCRIPTION
                  "This table contains information on all users registered
                   to each Registrar in this system."
             ::= { sipRegCfg 2 }

         sipRegUserEntry OBJECT-TYPE
             SYNTAX     SipRegUserEntry
             MAX-ACCESS not-accessible
             STATUS     current
             DESCRIPTION
                  "This entry contains information for a single user
                   registered to this Registrar.




Lingle, et al.         Expires December 30, 2003               [Page 90]

Internet-Draft              SIP MIB Modules                    July 2003


                   Each row represents those objects for a particular SIP
                   server present in this system.  applIndex is used to
                   uniquely identify these instances of SIP servers and
                   correlate them through the common framework of the
                   NETWORK-SERVICES-MIB (RFC 2788).  The same value of
                   applIndex used in the corresponding SIP-COMMON-MIB
                   is used here."
             INDEX { applIndex, sipUserIndex }
             ::= { sipRegUserTable 1 }

         SipRegUserEntry ::=
             SEQUENCE {
                      sipUserIndex                     Unsigned32,
                      sipUserUri                       SnmpAdminString,
                      sipUserAuthenticationFailures    Counter32,
                      sipUserTableRowStatus            RowStatus
             }

         sipUserIndex OBJECT-TYPE
             SYNTAX     Unsigned32 (1..4294967295)
             MAX-ACCESS not-accessible
             STATUS     current
             DESCRIPTION
                  "This object uniquely identifies a conceptual row in the
                   table."
             ::= { sipRegUserEntry 1 }

         sipUserUri OBJECT-TYPE
             SYNTAX     SnmpAdminString
             MAX-ACCESS read-create
             STATUS     current
             DESCRIPTION
                  "This object contains the user's address-of-record.  It
                   is the main form by which the Registrar knows the user.
                   The format is typically 'user@domain'.  It is contained
                   in the To header for all REGISTER requests."
             ::= { sipRegUserEntry 2 }

         sipUserAuthenticationFailures OBJECT-TYPE
             SYNTAX     Counter32
             MAX-ACCESS read-only
             STATUS     current
             DESCRIPTION
                  "This object contains a count of the number of times the
                   user has failed authentication."
             ::= { sipRegUserEntry 3 }

         sipUserTableRowStatus OBJECT-TYPE



Lingle, et al.         Expires December 30, 2003               [Page 91]

Internet-Draft              SIP MIB Modules                    July 2003


             SYNTAX     RowStatus
             MAX-ACCESS read-create
             STATUS     current
             DESCRIPTION
                  "The row status of the entry. This object is required
                   to create or delete rows remotely by a manager."
             ::= { sipRegUserEntry 4 }

         --
         -- Per Contact Information
         --
         sipContactTable OBJECT-TYPE
             SYNTAX     SEQUENCE OF SipContactEntry
             MAX-ACCESS not-accessible
             STATUS     current
             DESCRIPTION
                  "This table contains information on every location where
                   a registered user (specified by sipUserIndex) wishes to
                   be found (i.e. the user has provided Contact information
                   to each SIP Registrar in this system)."
             ::= { sipRegCfg 3 }

         sipContactEntry OBJECT-TYPE
             SYNTAX     SipContactEntry
             MAX-ACCESS not-accessible
             STATUS     current
             DESCRIPTION
                  "This entry contains information for a single Contact.
                   Multiple contacts may exist for a single user.

                   Each row represents those objects for a particular SIP
                   server present in this system.  applIndex is used to
                   uniquely identify these instances of SIP servers and
                   correlate them through the common framework of the
                   NETWORK-SERVICES-MIB (RFC 2788).  The same value of
                   applIndex used in the corresponding SIP-COMMON-MIB
                   is used here."
             INDEX { applIndex, sipUserIndex, sipContactIndex }
             ::= { sipContactTable 1 }

         SipContactEntry ::=
             SEQUENCE {
                      sipContactIndex                Unsigned32,
                      sipContactDisplayName          SnmpAdminString,
                      sipContactURI                  SnmpAdminString,
                      sipContactLastUpdated          TimeStamp,
                      sipContactExpiry               DateAndTime,
                      sipContactPreference           SnmpAdminString,



Lingle, et al.         Expires December 30, 2003               [Page 92]

Internet-Draft              SIP MIB Modules                    July 2003


                      sipContactRetryAfter           DateAndTime
             }

         sipContactIndex OBJECT-TYPE
             SYNTAX     Unsigned32 (1..4294967295)
             MAX-ACCESS not-accessible
             STATUS     current
             DESCRIPTION
                  "Along with the sipUserIndex, this object uniquely
                   identifies a conceptual row in the table."
             ::= { sipContactEntry 1 }

         sipContactDisplayName OBJECT-TYPE
             SYNTAX     SnmpAdminString
             MAX-ACCESS read-only
             STATUS     current
             DESCRIPTION
                  "This object contains the display name for the Contact.
                   For example, 'Santa at Home', or 'Santa on his Sled',
                   corresponding to contact URIs of
                   sip:BigGuy@sip.northpole.ca or
                   sip:sclaus817@sip.mobile.com, respectively."
             ::= { sipContactEntry 2 }

         sipContactURI OBJECT-TYPE
             SYNTAX     SnmpAdminString
             MAX-ACCESS read-only
             STATUS     current
             DESCRIPTION
                  "This object contains either a SIP URI where
                   the user can be contacted.  This URI is normally returned
                   to a client from a Redirect Server, or is used as the
                   RequestURI in a SIP request line for requests forwarded
                   by a proxy."
             ::= { sipContactEntry 3 }

         sipContactLastUpdated OBJECT-TYPE
             SYNTAX     TimeStamp
             MAX-ACCESS read-only
             STATUS     current
             DESCRIPTION
                  "This object indicates the time when this contact
                   information was accepted.  If the contact information
                   is updated via a subsequent REGISTER of the same
                   information, this object is also updated."
             ::= { sipContactEntry 4 }

         sipContactExpiry OBJECT-TYPE



Lingle, et al.         Expires December 30, 2003               [Page 93]

Internet-Draft              SIP MIB Modules                    July 2003


             SYNTAX     DateAndTime
             MAX-ACCESS read-only
             STATUS     current
             DESCRIPTION
                  "This object contains the date and time when the contact
                   information will no longer be valid.  Such times may be
                   specified by the user at registration (Expires header
                   or expiry parameter in the Contact information), or a
                   system default can be applied."
             ::= { sipContactEntry 5 }

         sipContactPreference OBJECT-TYPE
             SYNTAX     SnmpAdminString
             MAX-ACCESS read-only
             STATUS     current
             DESCRIPTION
                  "This object indicates a relative preference for the
                   particular Contact header field value compared to other
                   bindings for this address-of-record. A registering user
                   may provide this preference as a 'qvalue'parameter in
                   the Contact header.

                   The format of this item is a decimal number between 0
                   and 1 (for example 0.9).  Higher values indicate
                   locations preferred by the user."
             REFERENCE
                  "RFC 3261, Section 10.2.1.2, 16.6 and 20.10"
             ::= { sipContactEntry 6 }

         sipContactRetryAfter OBJECT-TYPE
             SYNTAX     DateAndTime
             MAX-ACCESS read-only
             STATUS     current
             DESCRIPTION
                  "This object indicates that the contact information is
                   currently inactive, and that it SHOULD only be
                   activated after the date and time specified by the object.
                   This value is provided by a user when deleting contact
                   information using a REGISTER request containing a
                   Retry-After header."
             REFERENCE
                  "RFC 3261, Section 20.33"
             ::= { sipContactEntry 7 }


         --
         -- Registrar Statistics
         --



Lingle, et al.         Expires December 30, 2003               [Page 94]

Internet-Draft              SIP MIB Modules                    July 2003


         sipRegStatsTable OBJECT-TYPE
             SYNTAX     SEQUENCE OF SipRegStatsEntry
             MAX-ACCESS not-accessible
             STATUS     current
             DESCRIPTION
                  "This table contains the summary statistics objects
                   applicable to all SIP Registrars in this system."
             ::= { sipRegStats 1 }

         sipRegStatsEntry OBJECT-TYPE
             SYNTAX     SipRegStatsEntry
             MAX-ACCESS not-accessible
             STATUS     current
             DESCRIPTION
                  "A row of summary statistics.

                   Each row represents those objects for a particular SIP
                   server present in this system.  applIndex is used to
                   uniquely identify these instances of SIP servers and
                   correlate them through the common framework of the
                   NETWORK-SERVICES-MIB (RFC 2788).  The same value of
                   applIndex used in the corresponding SIP-COMMON-MIB
                   is used here."
             INDEX { applIndex }
             ::= { sipRegStatsTable 1 }

         SipRegStatsEntry ::=
             SEQUENCE {
                      sipRegAcceptedRegistrations Counter32,
                      sipRegRejectedRegistrations Counter32
             }

         sipRegAcceptedRegistrations OBJECT-TYPE
             SYNTAX     Counter32
             MAX-ACCESS read-only
             STATUS     current
             DESCRIPTION
                  "This object contains a count of the number of REGISTER
                   requests that have been accepted (status code 200) by
                   the Registrar.  This includes additions of new contact
                   information, refreshing contact information, as well as
                   requests for deletion of contact information."
             ::= { sipRegStatsEntry 1 }

         sipRegRejectedRegistrations OBJECT-TYPE
             SYNTAX     Counter32
             MAX-ACCESS read-only
             STATUS     current



Lingle, et al.         Expires December 30, 2003               [Page 95]

Internet-Draft              SIP MIB Modules                    July 2003


             DESCRIPTION
                  "This object contains a count of the number REGISTER
                   requests that have been rejected by the Registrar."
             ::= { sipRegStatsEntry 2 }


         --
         -- Conformance
         --
         sipServerMIBCompliances
           OBJECT IDENTIFIER ::= { sipServerMIBConform 1 }
         sipServerMIBGroups
           OBJECT IDENTIFIER ::= { sipServerMIBConform 2 }

         --
         -- Compliance Statements
         --
         sipProxyServerCompliance MODULE-COMPLIANCE
             STATUS     current
             DESCRIPTION
                  "The compliance statement for SIP entities acting
                   as Proxy Servers."
             MODULE -- this module
                  MANDATORY-GROUPS { sipServerConfigGroup,
                                     sipProxyConfigGroup,
                                     sipProxyStatsGroup }
             ::= { sipServerMIBCompliances 1 }

         sipRedirectServerCompliance MODULE-COMPLIANCE
             STATUS     current
             DESCRIPTION
                  "The compliance statement for SIP entities acting
                   as Redirect Servers."
             MODULE -- this module
                  MANDATORY-GROUPS { sipServerConfigGroup }
             ::= { sipServerMIBCompliances 2 }

         sipRegistrarServerCompliance MODULE-COMPLIANCE
             STATUS     current
             DESCRIPTION
                  "The compliance statement for SIP entities acting
                   as Registrars."
             MODULE -- this module
                  MANDATORY-GROUPS { sipServerConfigGroup,
                                     sipRegistrarConfigGroup,
                                     sipRegistrarStatsGroup }
             ::= { sipServerMIBCompliances 3 }




Lingle, et al.         Expires December 30, 2003               [Page 96]

Internet-Draft              SIP MIB Modules                    July 2003


         --
         -- Units of Conformance
         --
         sipServerConfigGroup OBJECT-GROUP
             OBJECTS {
                     sipServerHostAddrType,
                     sipServerHostAddr
             }
             STATUS  current
             DESCRIPTION
                  "A collection of objects providing configuration common
                   to SIP Proxy and Redirect servers."
             ::= { sipServerMIBGroups 1 }

         sipProxyConfigGroup OBJECT-GROUP
             OBJECTS {
                     sipRequestMaxExpires,
                     sipProxyStatefulness,
                     sipProxySendsCancel,
                     sipProxyForwardAll1xx,
                     sipProxyRecursion,
                     sipProxyProvideAlternatives,
                     sipProxyRecordRoute,
                     sipProxyAuthMethod,
                     sipProxyAuthRealm,
                     sipProxyNonceLifeTime
             }
             STATUS  current
             DESCRIPTION
                  "A collection of objects providing configuration for
                   SIP Proxy servers."
             ::= { sipServerMIBGroups 2 }

         sipProxyStatsGroup OBJECT-GROUP
             OBJECTS {
                     sipNumProxyRequireFailures
             }
             STATUS  current
             DESCRIPTION
                  "A collection of objects providing statistics for
                   SIP Proxy servers."
             ::= { sipServerMIBGroups 3 }

         sipRegistrarConfigGroup OBJECT-GROUP
             OBJECTS {
                     sipRegAllowThirdParty,
                     sipRegMaxContactExpiryDuration,
                     sipRegMaxUsers,



Lingle, et al.         Expires December 30, 2003               [Page 97]

Internet-Draft              SIP MIB Modules                    July 2003


                     sipRegCurrentUsers,
                     sipRegDfltRegActiveInterval,
                     sipUserUri,
                     sipUserAuthenticationFailures,
                     sipUserTableRowStatus,
                     sipContactDisplayName,
                     sipContactURI,
                     sipContactLastUpdated,
                     sipContactExpiry,
                     sipContactPreference,
                     sipContactRetryAfter
             }
             STATUS  current
             DESCRIPTION
                  "A collection of objects providing configuration for
                   SIP Registrars."
             ::= { sipServerMIBGroups 4 }

         sipRegistrarStatsGroup OBJECT-GROUP
             OBJECTS {
                     sipRegAcceptedRegistrations,
                     sipRegRejectedRegistrations
             }
             STATUS  current
             DESCRIPTION
                  "A collection of objects providing statistics for
                   SIP Registrars."
             ::= { sipServerMIBGroups 5 }

         END


8. Changes from Previous Draft Revisions

   Changes from draft-ietf-sip-mib-06

   o  General

      *  Minor editorial changes in the Textual Conventions section.

   o  SIP-COMMON-MIB

      *  sipStatusCodeValue SYNTAX changed from INTEGER to Unsigned32.

      *  Optional sipCommonNotifObjectsGroup explicitly added to
         MODULE-COMPLIANCE.

      *  Removed OBJECT refinement for sipStatusCodeRowStatus added to



Lingle, et al.         Expires December 30, 2003               [Page 98]

Internet-Draft              SIP MIB Modules                    July 2003


         compliance in previous revision.  SMIC MIB compiler issues
         required it to be commented out. Instead, simply removed it.

   o  SIP-SERVER-MIB

      *  Removed OID placeholders: sipRedirCfg, sipRedirStats.
         sipRegCfg and sipRegStats OID values subsequently changed as a
         result.

   o  SIP-UA-MIB

      *  Removed OBJECT refinement for sipUACfgSipServerStatus added to
         compliance in previous revision.  SMIC MIB compiler issues
         required it to be commented out. Instead, simply removed it.

   Changes from draft-ietf-sip-mib-05

   o  Front paper/Back paper and General changes

      *  Removed all references and special handling of SIP INFO method
         Removed references and objects specific to RFC 2976: INFO will
         be treated as any SIP extension method.

      *  Changed requirements verbs from lowercase to uppercase wherever
         appropriate.

      *  Added RFC Editor notes.

      *  Updated all REFERENCE clauses and DESCRIPTIONS from RFC 2543 to
         RFC 3261.

      *  Explained the approach taken for extension methods that might
         be defined in the future.

      *  Defined a mapping of sipServiceOperStatus to applOperStatus.

      *  Enhanced Security section with details on various objects.

      *  Added descriptive language to various Entry objects regarding
         the expected persistence of data across system restarts.

   o  SIP-COMMON-MIB

      *  Removed sipTransactionTable after input from SIP community.

      *  Made all extension method tables augmentations of
         sipExtMethodSupportedTable.  This resulted in the removal of
         the following objects: sipCfgTimerExtMethodName,



Lingle, et al.         Expires December 30, 2003               [Page 99]

Internet-Draft              SIP MIB Modules                    July 2003


         sipCfgRetryExtMethodName, sipStatsExtMethodName,
         sipStatsRetryExtMethodName.

      *  sipCommonStatusCodeNotifEmitMode default value changed to
         'triggered'.

      *  sipStatusCodeThreshExceededNotif was replaced by two
         notifications: sipStatusCodeThreshExceededOutNotif &
         sipStatusCodeThreshExceededInNotif.

      *  Re-arranged the enumerated value of sipServiceOperStatus;
         making 'unknown' the first value.   Added some words to the
         DESCRIPTION of that object stating the values are not based on
         anything in the SIP standard.

      *  Clarified rules for capitalization of sipExtMethodName.

      *  All counters in the MIB are consistent with respect to
         resetting to zero.  No counters can be reset to zero. Entries
         in sipStatusCodesTable can simply be created or destroyed - no
         ability to set to 'notInService' where there was the question/
         possibility of resetting the counters to zero.
         sipStatsExtMethodTable no longer has itÈËs own RowStatus
         object, so it too can no longer be set to 'notInServiceË where
         there was the question/possibility of resetting the counters to
         zero. sipStatsExtMethodTable rows are augmentations of
         sipExtMethodSupportedEntry.

      *  OBJECT refinement for sipStatusCodeRowStatus added to
         compliance.

      *  Clarified the relationship between
         sipCommonStatusCodeNotifEmitMode and
         sipCommonStatusCodeNotifSend.

      *  Explained the existence of sipNotifApplIndex object better.

      *  sipCfgExpiresStatusCodeValue syntax changed from INTEGER to
         Unsigned32.

      *  sipEntityType object added to sipCommonCfgTable.

      *  All accessible-for-notify objects are moved into
         sipCommonNotifObjects group.  OIDs for actual notifications are
         re-assigned as a result.

      *  sipNotifSequenceNumber accessible-for-notify object added as a
         way for managers to gain insight into possible missed



Lingle, et al.         Expires December 30, 2003              [Page 100]

Internet-Draft              SIP MIB Modules                    July 2003


         notifications.  It is bound to each notification defined in the
         MIB.

      *  New notifications related to SIP service operational status are
         added: sipServiceColdStart, sipServiceWarmStart, &
         sipServiceLastChanged.

      *  New object sipServiceNotifEnable added to control the new SIP
         related notifications.

      *  Minor object descriptor changes: sipStatusCodesTable renamed to
         sipStatusCodeClassesTable SipStatusCodesEntry renamed to
         SipStatusCodeClassesEntry sipStatusCodesEntry renamed to
         sipStatusCodeClassesEntry sipCommonStatusCodeTable renamed to
         sipStatusCodesTable SipCommonStatusCodeEntry renamed to
         SipStatusCodesEntry sipCommonStatusCodeEntry renamed to
         sipStatusCodesEntry sipCommonStatusCodeValue renamed to
         sipStatusCodeValue sipCommonStatusCodeIns   renamed to
         sipStatusCodeIns sipCommonStatusCodeOuts  renamed to
         sipStatusCodeOuts sipCommonStatusCodeStatus renamed to
         sipStatusCodeRowStatus sipCommonStatusCodeNotifTable renaemd to
         sipStatusCodeNotifTable SipCommonStatusCodeNotifEntry renamed
         to SipStatusCodeNotifEntry sipCommonStatusCodeNotifEntry
         renamed to sipStatusCodeNotifEntry sipCommonStatusCodeNotifSend
         renamed to sipStatusCodeNotifSend
         sipCommonStatusCodeNotifEmitMode renamed to
         sipStatusCodeNotifEmitMode sipCommonStatusCodeNotifThresh
         renamed to sipStatusCodeNotifThresh
         sipCommonStatusCodeNotifInterval renamed to
         sipStatusCodeNotifInterval

      *  Removed all INFO method specific objects: sipCfgRetryInfo,
         sipStatsInfoIns, sipStatsInfoOuts, & sipStatsRetryInfos

      *  Clarifying words added to sipStatusCodeNotifTable DESCRIPTION
         to explain why it's a seperate table from sipStatusCodesTable.

   o  SIP-SERVER-MIB

      *  Deleted objects related to 'action' parameter. RFC 3261 section 
         10.2 deprecates the 'action' parameter deleted 3 objects:
         sipServerContactDfltAction, sipServerRespectUAAction,
         sipContactAction.

      *  Deleted pgp-related objects. RFC 3261 section 23 deprecates use
         of pgp deleted 3 objects: sipProxyAuthPgpAlgorithm,
         sipPgpPrivateKey, sipPgpVersion.




Lingle, et al.         Expires December 30, 2003              [Page 101]

Internet-Draft              SIP MIB Modules                    July 2003


      *  Removed sipProxyStateTimeout object. Timers G and timer H have
         been introduced in RFC 3261 for this purpose (see RFC 3261
         section 17.2.1).

      *  Updated description clause of sipProxyStatefulness. The 3
         definitions of stateless/statefulness now match the text in RFC
         3261.

      *  Changed DEFVAL for object sipProxyProvideAlternatives. Changed
         DEFVAL to true to align with RFC 3261 that states that 485
         responses SHOULD contain a contact header & 303 MAY... and
         updated REFERENCE clause to "RFC 3261 Sections 13.2.2.2 and
         16.5".

      *  Removed basic authentication value from sipProxyAuthMethod
         object Per section 22 of rfc 3261, deprecated.

      *  Changed SYNTAX of sipProxyNonceLifeTime from Integer32 to
         Unsigned32.

      *  Updated description clause of sipRegDfltRegActiveInterval Per
         RFC 3261 Section 10.2.

   o  SIP-UA-MIB

      *  OBJECT refinement for sipUACfgSipServerStatus added to
         compliance.

      *  Changed the object descriptors of sipUACfgSipServerAddrIndex to
         sipUACfgSipServerIndex, and sipUACfgSipServerAddrStatus to
         sipUACfgSipServerStatus.

   Changes from draft-ietf-sip-mib-04

   o  Started realignment with SIP RFC3261.

   Changes from draft-ietf-sip-mib-03

   o  Front paper/Back paper and General changes

      *  Rewrote section on Network Services MIB

      *  Fixed minor editorial nits

   o  SIP-COMMON-MIB

      *  CONTACT-INFO "SIP MIB email" changed to sip@ietf.org




Lingle, et al.         Expires December 30, 2003              [Page 102]

Internet-Draft              SIP MIB Modules                    July 2003


      *  sipInviteTimeout was removed from the MIB.  See below regarding
         new sipCommonCfgExpires objects.  They provide equivalent
         functionality with extensibility beyond INVITE.

      *  sipCommonCfgExpires OID subtree added.  Per method Expires
         configuration objects were added there. This new high-level OID
         was placed under the existing sipCommonCfgRetry OID and
         therefore, caused the OIDs for the subsequent groups to change
         (incrementing by one).

      *  Objects from tables under sipCommonCfgExpires were added to a
         new OBJECT-GROUP sipCommonConfigExpiresGroup, and that group
         was listed as optional in sipCommonCompliance.

      *  Minor DESCRIPTION change for sipCommonCfgEntry.  No behavior
         change.

      *  sipServiceOperStatus SYNTAX changed. New values added:
         congested & quiescing Old values removed: halted The order of
         the enumeration was altered as well.

      *  sipServiceAdminStatus SYNTAX changed. New values added: noop,
         up, down, quieseSessions, and quieseApplications Old values
         removed: shutdown, restart, stop, rts. These changes were made
         based on comments from last call reviewer and general known
         ambiguities in the previous design of the object.

      *  Clarifying changes to the DESCRIPTION of sipServiceStartTime.

      *  Clarifying changes to the DESCRIPTION of sipServiceStartTime.

      *  Clarification of behavior for sipPortStatus while row is
         'active'

      *  Clarifying changes to the DESCRIPTION of sipUriSupportedTable.

      *  Clarifying changes to the DESCRIPTIONs of sipFtrSupportedTable,
         sipFtrSupportedEntry, and sipFtrSupported. Specifically, IETF
         standard features and non-standard features are now represented
         by this table.  Only non-standard features were mentioned in
         prior revisions of the draft.

      *  Reference to usage of RFC 2788 applIndex moved from
         sipCommonCfgTimerExtMethodTable to
         sipCommonCfgTimerExtMethodEntry. This was the convention for
         other table/entry definitions in the MIB, so these objects were
         previously unconventional.




Lingle, et al.         Expires December 30, 2003              [Page 103]

Internet-Draft              SIP MIB Modules                    July 2003


      *  DEFVAL removed from sipCfgTimerExtMethodTimer.  The generic
         nature of the "extension" object does not lend itself to being
         able to specify a particular default value.

      *  Since the removal of the DEFVAL clause from
         sipCfgTimerExtMethodTimer, a value for that object must be
         specified when creating a sipCommonCfgTimerExtMethodEntry.  The
         description of sipCfgTimerExtMethodStatus was updated to
         reflect this.

      *  sipCommonCfgRetryExtMethodTable is now properly defined under
         sipCommonCfgRetry OID space instead of under sipCommonCfgTimer
         OID space.

      *  DEFVAL removed from sipCfgRetryExtMethodRetry.  The generic
         nature of the "extension" object does not lend itself to being
         able to specify a particular default value.

      *  Since the removal of the DEFVAL clause from
         sipCfgRetryExtMethodRetry, a value for that object must be
         specified when creating a sipCommonCfgRetryExtMethodEntry.  The
         description of sipCfgRetryExtMethodStatus was updated to
         reflect this.

      *  Clarifying changes to the DESCRIPTION of
         sipSummaryTotalTransactions. Specifically, the object is not
         applicable to stateless SIP proxy servers and the object should
         always return a value of 0 if implemented by a stateless proxy.

      *  Clarifying changes to the DESCRIPTION of
         sipStatsExtMethodStatus.

      *  sipStatsOtherClassesIns and sipStatsOtherClassesOuts counter
         objects were added to sipStatusCodesTable to handle possible
         future classes of response status codes.

      *  Text referring specifically to Redirect Server in
         sipStatsRedirClassIns and sipStatsRedirClassOuts was removed.

      *  Text defining protocol behavior in sipStatsServerFailClassIns,
         sipStatsServerFailClassOuts, sipStatsGlobalFailClassIns, and
         sipStatsGlobalFailClassOuts was removed.

      *  sipCommonStatusCodeNotifInterval SYNTAX changed from TimeTicks
         to Unsigned32 w/ a UNITS of "seconds" added to the definition.
         DEFVAL clause changed accordingly.

      *  sipStatusCodeNotifTo, sipStatusCodeNotifFrom,



Lingle, et al.         Expires December 30, 2003              [Page 104]

Internet-Draft              SIP MIB Modules                    July 2003


         sipStatusCodeNotifCallId, and sipStatusCodeNotifCSeq all had
         clarifying changes to their DESCRIPTIONs.  Specifically, the
         header name will be part of the object value and example values
         were given.

      *  Clarifying changes to the DESCRIPTION of sipCurrentTransTable
         and sipTransactionTable.  Specifically, these tables are not
         applicable to transaction stateless SIP Proxy Servers.

      *  Minor gramatical change to the DESCRIPTION of
         sipCurrentTransEntry.

      *  sipTransMethod and sipTransActivityInfo objects were added to
         sipTransactionTable while sipTransCallingPartyContentType and
         sipTransCalledPartyContentType were removed.

      *  Clarifying changes to the DESCRIPTION of sipTransState.
         Specifically, noting that not all values of the object are
         applicable to all transaction types.

      *  sipTransTo, sipTransFrom, sipTransCallId, and sipTransCSeq all
         had clarifying changes to their DESCRIPTIONs. Specifically, the
         header name will be part of the object value and example values
         were given.

      *  Minor gramatical change to the DESCRIPTION of
         sipOtherStatsEntry.

      *  sipCommonStatusCodeIns and sipCommonStatusCodeOuts objects were
         added to the varbind of sipStatusCodeNotif.

      *  Appropriate changes were made to sipCommonStatsGroup
         OBJECT-GROUP based on objects being added and/or removed from
         the MIB.

   o  SIP-SERVER-MIB

      *  CONTACT-INFO "SIP MIB email" changed to sip@ietf.org

      *  The statement "Unlike a Proxy server it does not initiate
         requests." was removed from where a Redirect Server is defined
         in the MIB's DESCRIPTION.

      *  sipServerMIBNotifs OID removed. No notifications were ever
         defined under this subtree.

      *  Clarifying text added to all of the Table DESCRIPTIONS stating
         that the value of applIndex used in this MIB corresponds to the



Lingle, et al.         Expires December 30, 2003              [Page 105]

Internet-Draft              SIP MIB Modules                    July 2003


         value of applIndex used in the SIP-COMMON-MIB.

      *  Clarifying changes to the DESCRIPTION of sipProxyStatefulness.

      *  sipContactPreference SYNTAX changed from OCTET STRING to
         SnmpAdminString.

   o  SIP-UA-MIB

      *  CONTACT-INFO "SIP MIB email" changed to sip@ietf.org

      *  sipUAMIBNotifs OID removed. No notifications were ever defined
         under this subtree.

      *  sipUAStats OID removed. No notifications were ever defined
         under this subtree.

      *  Clarifying text added to all of the Table DESCRIPTIONS stating
         that the value of applIndex used in this MIB corresponds to the
         value of applIndex used in the SIP-COMMON-MIB.

   o  SIP-TC

      *  CONTACT-INFO "SIP MIB email" changed to sip@ietf.org

   Changes from draft-ietf-sip-mib-02

   o  General

      *  Eliminated the SIP-MIB-SMI modules.  Each MIB module will now
         get it's own IANA OID.

      *  Top-level OID subtrees restructured in each MIB.

      *  General cleanup/removal of "placeholder" OID subtrees for
         object groups and notifications that never materialized.

   o  SIP-COMMON-MIB

      *  Removed sipCfgInitialTimerAck.

      *  Removed sipCfgRetryAck.

      *  Removed sipStatsRetryAcks.

      *  sipCommonStatsRetryExtMethodEntry was missing its INDEX clause.

      *  sipNumUnsupportedUris OID was "5" when it was the only object



Lingle, et al.         Expires December 30, 2003              [Page 106]

Internet-Draft              SIP MIB Modules                    July 2003


         in the table.  OID is now "1".

      *  High-level OID structure of the MIB is now sequential.

      *  Incorrect object descriptor for sipCfgInitialTimerRsp
         inconsistent with reference in compliance section.

      *  Inconsistencies between sipCommonStatsRetryGroup definition and
         SipCommonStatsRetryEntry OBJECT-TYPE corrected.

      *  sipNotifApplIndex was not in any object group in the
         conformance section.

   o  SIP-SERVER-MIB

      *  Removed sipInformationTryingInterval.

      *  Removed sipRxProxyAuthTable.

      *  Removed sipRegRespHasContacts.

      *  Removed sipRegContactDfltExpiryDate.

      *  Removed sipRegContactDfltExpiryDuration.

      *  Removed sipUserPassword.

      *  sipRequestMaxExpires DESCRIPTION changed to no longer
         specifically mention 400 response.

      *  sipProxyStateful object descriptor changed to
         sipProxyStatefullness and the SYNTAX changed from TruthValue to
         an enumerated INTEGER.

      *  sipProxyStateTimeout DESCRIPTION changed to now reflect only
         INVITE.

      *  Gauge32 was not being IMPORTed.

      *  sipServerContactDfltAction showed up in conformance and other
         object descriptions in an older form.

      *  sipServerHost replaced with InetAddressType/InetAddress object
         pair (sipServerHostAddrType & sipServerHostAddr).

   o  SIP-UA-MIB

      *  IMPORTed Unsigned32 to support sipUACfgSipServerAddrIndex.



Lingle, et al.         Expires December 30, 2003              [Page 107]

Internet-Draft              SIP MIB Modules                    July 2003


      *  sipUACfgSipServerEntry was referencing the wrong auxilliary
         object and listing that object in the conformance section.

      *  sipUACfgSipServerEntry listed sipUACfgSipServerStatus when it
         should have been listing sipUACfgSipServerAddrStatus.

      *  SIP-UA-MIB IMPORTed Counter32, but never used it. Removed the
         IMPORT of Counter32.


9. Security Considerations

   There are a number of management objects defined in this MIB module
   with 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.

   These are the tables and objects and their sensitivity/vulnerability:

   o  SIP-COMMON-MIB

         The following read-write object is used to control the overall
         SIP service in any SIP entity:

            sipServiceAdminStatus

         If this object is SET maliciously, it may result in unwanted
         operational status, or a failure to obtain SIP services.

         The following read-write and read-create objects are used to
         control the behavior of the SIP protocol as exhibited by a SIP
         entity:

            sipOrganization, sipRequestUriHostMatching, sipCfgTimerA,
            sipCfgTimerB, sipCfgTimerC, sipCfgTimerD, sipCfgTimerE,
            sipCfgTimerF, sipCfgTimerG, sipCfgTimerH, sipCfgTimerI,
            sipCfgTimerJ, sipCfgTimerK, sipCfgTimerT1, sipCfgTimerT2,
            sipCfgTimerT4, sipCfgTimerExtMethodTimer, sipCfgRetryInvite,
            sipCfgRetryBye, sipCfgRetryCancel, sipCfgRetryRegister,
            sipCfgRetryOptions, sipCfgRetryFinalResponse,
            sipCfgRetryNonFinalResponse, sipCfgRetryExtMethodRetry,
            sipCfgExpiresInvite, sipCfgExpiresRegister,
            sipCfgExpiresHeaderMethod, sipCfgExpiresHeaderValue,
            sipCfgExpiresStatusCodeStatus





Lingle, et al.         Expires December 30, 2003              [Page 108]

Internet-Draft              SIP MIB Modules                    July 2003


         If these objects are SET maliciously, it may result in
         incorrect or unwanted protocol operation.

         The following read-create object is used to configure the
         status code statistics that will be monitored by the SIP
         entity:

            sipStatusCodeRowStatus

         If this object is SET maliciously, it may result in an over
         allocation of resources in a system for the purpose of
         accumulating and maintaining statistics.

         The following read-write objects are used to configure the
         behavior of certain SNMP notifications potentially generated by
         a SIP entity:

            sipStatusCodeNotifSend, sipStatusCodeNotifEmitMode,
            sipStatusCodeNotifThresh, sipStatusCodeNotifInterval,
            sipServiceNotifEnable

         If these objects are SET maliciously, it may result in a system
         and/or network performance impact due to the generation of SNMP
         notifications.

   o  SIP-UA-MIB

         The following read-create objects are used to configure the
         Internet address of SIP servers a SIP User Agent will use to
         proxy/redirect SIP calls:

            sipUACfgSipServerAddrType, sipUACfgSipServerAddr,
            sipUACfgSipServerStatus.

         If these objects are SET maliciously, it may result in unwanted
         operation, or a failure to obtain SIP services from the user
         agent prospective or even theft of service. In particular,
         setting the SipUACfgSipServerStatus object instance to the
         'destroy' value may result in service disruption.

   o  SIP-SERVER-MIB

         The following read-create objects are managed by Registrar
         Servers and contain sensitive or private information about the
         address of record of registered users.

            sipUserUri & sipUserTableRowStatus




Lingle, et al.         Expires December 30, 2003              [Page 109]

Internet-Draft              SIP MIB Modules                    July 2003


         The sensitivity of these objects depends on the role that
         Registrar Servers play in the SIP service. In some cases, these
         objects, if SET maliciously, may allow unregistered users to
         steal service, or may prevent registered users from accessing
         the SIP service.

         The following read-write objects, if SET maliciously will have
         an immediate serious impact on the service:

            sipServerHostAddrType & sipServerHostAddr

         These objects specify the host part of the URI for the server
         providing the SIP resource and it is widely used by SIP servers
         in numerous header lines and field. For e.g., the host address
         may be used with the Request-URI to check if the server is the
         one resolved by the Request-URI, therefore determining whether
         to process or forward the request in the case of outbound
         proxies, or, as an another common example, it is used by Proxy
         Servers acting as strict routers to rewrite the Request-URI.
         Setting these objects with improper values may result in
         serious service interference or failure.

         sipRequestMaxExpires and sipRegMaxContactExpiryDuration: if set
         to a zero value and either SIP requests contain an Expires
         header or Contact header contain an expires parameter, may
         cause the server to never create bindings associated with an
         address of record (case of REGISTER request) or may cause
         server to expire and cancel invitations (case of INVITE
         request).

         sipProxyStatefulness: changing the value of this object affects
         how transaction states are being handled the Proxy Server and
         may result in call feature or service changes.

         sipProxyAuthMethod: this object specifies at a maximum what the
         authentication methods that may be used by a server. If this
         object is SET maliciously, it may alter how the level of
         security used by the server to generate requests and may
         compromise the network security policies.

         sipRegAllowThirdParty: depending on the authentication policy
         associated with registration services, setting this object
         maliciously to 'true' may allow theft of identity or service.

         sipProxyAuthRealm: if this object is SET improperly, and if the
         HTTP Digest authentication method is used, it may result in
         clients being unable to authenticate and ultimately, in the
         server denying service.



Lingle, et al.         Expires December 30, 2003              [Page 110]

Internet-Draft              SIP MIB Modules                    July 2003


         The remaining read-write objects, if SET maliciously may have
         some effect on the service:

         SipProxySendsCancel: this is a configuration object defining
         how a certain class of proxy servers (forking proxies) handle
         cancellation of outstanding branch requests. If this object was
         set to true and is maliciously changed to false, the impact is
         considered moderate: the forking proxy may simply terminate the
         outstanding branches at a later phase, either when a
         transaction timer expires or when subsequent messages arrive
         from the outstanding branches.

         sipProxyRecordRoute: setting this object to true may cause
         additional SIP traffic to cross the proxy server and may result
         in message avalanches.

         The threats posed by the following read-write objects can
         either be mitigated by other configuration settings like
         read-only objects or they are considered to cause additional
         server operations without immediate impact on the server like
         additional location look-ups (sipProxyProvideAlternatives),
         additional traffic due to expiration of nonce
         (sipProxyNonceLifeTime).

            sipProxyForwardAll1xx, sipProxyRecursion,
            sipProxyProvideAlternatives sipProxyNonceLifeTime, and
            sipRegDfltRegActiveInterval

         Some of the readable objects in the MIB modules (i.e., objects
         with a MAX-ACCESS other than not-accessible) may be considered
         sensitive or vulnerable in some network environments.  It is
         thus important to control even GET and/or NOTIFY access to
         these objects and possibly to even encrypt the values of these
         objects when sending them over the network via SNMP.

         The following object values may contain private or confidential
         customer information like first name, last name, customer
         identification, location, company affiliation, the time the
         information was updated, etc.

            SipContactDisplayName, SipContactURI, and
            SipContactLastUpdated.

   SNMP versions prior to SNMPv3 did not include adequate security. 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 module.



Lingle, et al.         Expires December 30, 2003              [Page 111]

Internet-Draft              SIP MIB Modules                    July 2003


   It is RECOMMENDED that implementers consider the security features as
   provided by the SNMPv3 framework (see [RFC3410], section 8),
   including full support for the SNMPv3 cryptographic mechanisms (for
   authentication and privacy).

   Further, deployment of SNMP versions prior to SNMPv3 is NOT
   RECOMMENDED.  Instead, it is RECOMMENDED to deploy SNMPv3 and to
   enable cryptographic security.  It is then a customer/operator
   responsibility to ensure that the SNMP entity giving access to an
   instance of this MIB module 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.

10. Contributor Acknowledgments

   We wish to thank the members of the IETF SIP & SIPPING working groups
   & the SIP-MIB Design team for their comments and suggestions.
   Detailed comments were provided by Tom Taylor, Kavitha Patchayappan
   and Dan Romascanu.

Normative References

   [1]  Bradner, S., "Key words for use in RFCs to Indicate Requirement
        Levels", BCP 14, RFC 2119, March 1997.

   [2]  Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction
        and Applicability Statements for Internet-Standard Management
        Framework", RFC 3410, December 2002.

   [3]  McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
        McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of
        Management Information Version 2 (SMIv2)", STD 58, RFC 2578,
        April 1999.

   [4]  McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
        McCloghrie, K., Rose, M. and S. Waldbusser, "Textual Conventions
        for SMIv2", STD 58, RFC 2579, April 1999.

   [5]  McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Conformance
        Statements for SMIv2", STD 58, RFC 2580, April 1999.

   [6]  Freed, N. and S. Kille, "Network Services Monitoring MIB", RFC
        2788, March 2000.

   [7]  Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A.,
        Peterson, J., Sparks, R., Handley, M. and E. Schooler, "SIP:
        Session Initiation Protocol", RFC 3261, June 2002.




Lingle, et al.         Expires December 30, 2003              [Page 112]

Internet-Draft              SIP MIB Modules                    July 2003


   [8]  Daniele, M., Haberman, B., Routhier, S. and J. Schoenwaelder,
        "Textual Conventions for Internet Network Addresses", RFC 3291,
        May 2002.

Informational References

   [9]   Hoffman, P., Masinter, L. and J. Zawinski, "The mailto URL
         scheme", RFC 2368, July 1998.

   [10]  Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform
         Resource Identifiers (URI): Generic Syntax", RFC 2396, August
         1998.


Authors' Addresses

   Kevin Lingle
   Cisco Systems, Inc.
   7025 Kit Creek Road
   P.O. Box 14987
   Research Triangle Park, NC  27709
   US

   Phone: +1 919 392 2029
   EMail: klingle@cisco.com


   Joon Maeng
   ipDialog, Inc.
   7701 N. Lamar Blvd., Suite 304
   Austin, TX  78752-1023
   US

   Phone: +1 512 371 1770
   EMail: jmaeng@ipdialog.com


   Jean-Francois Mule
   CableLabs
   400 Centennial Parkway
   Louisville, CO  80027
   US

   Phone: +1 303 661 9100
   EMail: jfm@cablelabs.com






Lingle, et al.         Expires December 30, 2003              [Page 113]

Internet-Draft              SIP MIB Modules                    July 2003


   Dave Walker
   SS8 Networks, Inc.
   495 March Road
   Kanata, ON  K2K 3G1
   CA

   Phone: +1 613 592 2100
   EMail: drwalker@ss8.com











































Lingle, et al.         Expires December 30, 2003              [Page 114]

Internet-Draft              SIP MIB Modules                    July 2003


Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   intellectual property or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; neither does it represent that it
   has made any effort to identify any such rights. Information on the
   IETF's procedures with respect to rights in standards-track and
   standards-related documentation can be found in BCP-11. Copies of
   claims of rights made available for publication and any assurances of
   licenses to be made available, or the result of an attempt made to
   obtain a general license or permission for the use of such
   proprietary rights by implementors or users of this specification can
   be obtained from the IETF Secretariat.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights which may cover technology that may be required to practice
   this standard. Please address the information to the IETF Executive
   Director.


Full Copyright Statement

   Copyright (C) The Internet Society (2003). 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 assignees.

   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



Lingle, et al.         Expires December 30, 2003              [Page 115]

Internet-Draft              SIP MIB Modules                    July 2003


   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Acknowledgment

   Funding for the RFC Editor function is currently provided by the
   Internet Society.











































Lingle, et al.         Expires December 30, 2003              [Page 116]


Html markup produced by rfcmarkup 1.109, available from https://tools.ietf.org/tools/rfcmarkup/