rfc3055.txt

<VC++网络游戏建摸与实现>源代码

Network Working Group                                    M. Krishnaswamy
Request for Comments: 3055                                Photuris, Inc.
Category: Standards Track                                   D. Romascanu
                                                     Avaya Communication
                                                           February 2001


     Management Information Base for the PINT Services Architecture

Status of this Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

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

Abstract

   This memo describes a proposed Management Information Base (MIB) for
   the PSTN/Internet Interworking (PINT) Services Architecture.

Table of Contents

   1.  Introduction ................................................   2
   2.  The SNMP Management Framework ...............................   2
   3.  The need for PINT Services monitoring MIB ...................   3
   4.  PINT MIB Overview ...........................................   4
   5.  Definitions .................................................   5
   6.  Acknowledgements ............................................  17
   7.  Security Considerations .....................................  17
   8.  IANA Considerations .........................................  18
   9.  Intellectual Property .......................................  18
   10. References ..................................................  18
   11. Authors' Addresses ..........................................  20
   12. Full Copyright Statement ....................................  21











Krishnaswamy & Romascanu    Standards Track                     [Page 1]

RFC 3055                        PINT MIB                   February 2001


1. Introduction

   PINT services are an emerging set of new Internet based applications
   where voice (and fax) requests to the PSTN (Public Switched Telephone
   Network) are carried over the Internet.  RFC 2458 [1] gives a good
   introduction to the (pre-standard) PINT architecture and services.
   It also has examples of some of the early implementations of pre-
   PINT.

   This document defines a MIB which contains the elements for
   monitoring the performance of a PINT based service.  The MIB consists
   of details of the four basic PINT services and their performance
   statistics measured under various criteria.

   It is not the purpose of this MIB to enable management of the PINT
   networking elements.  We are concerned only with the PINT specific
   performance parameters.  While it is understood that PINT service
   performance is closely related to host and network performance, they
   are not addressed here.

2. The SNMP Management Framework

   The SNMP Management Framework presently consists of five major
   components:

    o   An overall architecture, described in RFC 2571 [2].

    o   Mechanisms for describing and naming objects and events for the
        purpose of management.  The first version of this Structure of
        Management Information (SMI) is called SMIv1 and described in
        STD 16, RFC 1155 [3], STD 16, RFC 1212 [4] and RFC 1215 [5].
        The second version, called SMIv2, is described in STD 58,
        RFC 2578 [6], RFC 2579 [7] and RFC 2580 [8].

    o   Message protocols for transferring management information.  The
        first version of the SNMP message protocol is called SNMPv1 and
        described in STD 15, RFC 1157 [9].  A second version of the SNMP
        message protocol, which is not an Internet standards track
        protocol, is called SNMPv2c and described in RFC 1901 [10] and
        RFC 1906 [11].  The third version of the message protocol is
        called SNMPv3 and described in RFC 1906 [11], RFC 2572 [12] and
        RFC 2574 [13].

    o   Protocol operations for accessing management information.  The
        first set of protocol operations and associated PDU formats is
        described in STD 15, RFC 1157 [9].  A second set of protocol
        operations and associated PDU formats is described in RFC 1905
        [14].



Krishnaswamy & Romascanu    Standards Track                     [Page 2]

RFC 3055                        PINT MIB                   February 2001


    o   A set of fundamental applications described in RFC 2573 [15] and
        the view-based access control mechanism described in RFC 2575
        [16].

   A more detailed introduction to the current SNMP Management Framework
   can be found in RFC 2570 [17].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  Objects in the MIB are
   defined using the mechanisms defined in the SMI.

   This memo specifies a MIB module that is compliant to the SMIv2.  A
   MIB conforming to the SMIv1 can be produced through the appropriate
   translations.  The resulting translated MIB must be semantically
   equivalent, except where objects or events are omitted because no
   translation is possible (use of Counter64).  Some machine-readable
   information in SMIv2 will be converted into textual descriptions in
   SMIv1 during the translation process.  However, this loss of machine
   readable information is not considered to change the semantics of the
   MIB.

3. The need for PINT services monitoring MIB

   Traditionally voice (and fax) requests originate and terminate inside
   a PSTN network.  This network is well known for robust handling of
   the requests, in terms of availability and security.  However when
   the requests originate from the Internet there is a concern both on
   the part of the user as well as the provider about issues like
   reliable forwarding of the call requests to the PINT gateway under
   various network conditions, user/host authentication, secure handling
   of the user information etc.  Performance and security management
   becomes all the more important where PINT services cross multiple
   administrative domains (or providers).

   This MIB is an attempt to list the parameters that need to be
   monitored on an user, PINT client, PINT server and PINT gateway
   basis.

   (PINT services, their invocation methods/protocols and security
   issues associated with the PINT architecture are discussed in detail
   in [18]).










Krishnaswamy & Romascanu    Standards Track                     [Page 3]

RFC 3055                        PINT MIB                   February 2001


4. PINT MIB - Overview

   Following is a list of some explanations on the MIB definitions that
   we have chosen to construct.

    o   The basic purpose of this MIB is to monitor the access to PINT
        services both from the performance and security point of view.
        Information may pertain to a certain user or his/her system
        (PINT client) or the system providing the PINT services (PINT
        server) or the PINT gateway that forwards the call to the PSTN
        network.

    o   We chose to build the configuration table as an extension of the
        Application MIB - RFC 2287 [19] using the augments construct.
        Server location and contact might be retrieved from the standard
        MIB-II sysLocation and sysContact objects.  There is no need to
        replicate this information in the PINT MIB.  However, the PINT
        administrator may be a different person than the sysadmin with
        global responsibilities, thus a pintSysContact object is
        defined.

    o   We chose to monitor the gateway connections from the PINT
        server.  While the agent runs in the PINT servers, the
        connections to the gateways might need to be monitored in order
        to understand what goes on.  We placed them in a separate MIB
        group, and by using MODULE-COMPLIANCE clauses, agents that
        cannot implement this stuff will not be mandated to do it.

    o   There is no traps definition in this MIB module.  Note that
        thresholding on counters is always possible by using a standard
        mechanism defined by the Remote Monitoring MIB, that can be
        referenced here.  Some events that may be defined by using this
        mechanisms:

            *  continuous login/authentication failure or refusal from a
               particular client or user

            *  nuisance call - repeated calls (within a specified
               period) to a number originating from the same user

    o   The client performance and user performance tables may be rather
        resource demanding for an agent implementation.  In some MIBs,
        like the Remote Monitoring (RMON) MIBs, control mechanisms were
        built in order to activate those statistics on demand.  If
        needed, a sorting ('topN') mechanism can be designed, so that a
        sorted view of clients or users is presented for the high level
        debugging.




Krishnaswamy & Romascanu    Standards Track                     [Page 4]

RFC 3055                        PINT MIB                   February 2001


    o   We built a time-distribution trying to cover both short-lived,
        as well as longer sessions (1-10 secs, 10 secs - 1 min., 1-15
        min., 15 mins-24 hours, longer).

    o   PintServerClientAddress is defined as a SnmpAdminString.  It may
        include an IpAddress and/or name, but we preferred to minimize
        the number of indices at this stage, and keep a human-readable
        format at the same time.

    o   We define pintServerUserIdName as the UserId.  This UserId needs
        to be unique across multiple PINT servers and gateways
        (depending on the architecture) and is mapped to the SessionId.
        One way to achieve this uniqueness is by appending clientId to
        the UserId string before sending to the PINT server.  The
        SessionId could then be a combination of this new UserId and a
        timestamp.

5. Definitions

PINT-MIB DEFINITIONS ::= BEGIN

         IMPORTS
          OBJECT-TYPE, Counter32, MODULE-IDENTITY, mib-2
         FROM   SNMPv2-SMI
         TEXTUAL-CONVENTION
         FROM SNMPv2-TC
         MODULE-COMPLIANCE, OBJECT-GROUP
         FROM SNMPv2-CONF
         sysApplInstallPkgEntry
         FROM SYSAPPL-MIB
         SnmpAdminString
         FROM SNMP-FRAMEWORK-MIB;  -- RFC 2571 [2]

         pintMib MODULE-IDENTITY
         LAST-UPDATED "200102010000Z" -- 1 Feb 2001

ORGANIZATION "IETF PINT Working Group"
CONTACT-INFO "
        Chairs:  Steve Bellovin
                    E-mail: [e-mail]

                    Igor Faynberg
                    E-mail: [e-mail]

        Authors: Murali Krishnaswamy
                     Postal: 20 Corporate Place South
                                Piscataway, NJ 08854
                                Tel:    [phone]



Krishnaswamy & Romascanu    Standards Track                     [Page 5]

RFC 3055                        PINT MIB                   February 2001


                                E-mail: [e-mail]

                                Dan Romascanu
                                Postal: Atidim Technology Park, Bldg 3
                                Tel Aviv, Israel
                                Tel:    [phone]
                                E-mail: [e-mail]

        General Discussion:[e-mail]
        To Subscribe: [e-mail]
        In Body: subscribe your-email-addres
        Archive: http://www.bell-labs.com/mailing-lists/pint/
        "

DESCRIPTION
    "This MIB defines the objects necessary to monitor
     PINT Services"

-- Revision history

REVISION "200102010000Z" -- 1 Feb 2001
DESCRIPTION
    "Initial version, published as RFC 3055."
::= { mib-2 93 }

PintServiceType ::= TEXTUAL-CONVENTION
        STATUS      current
        DESCRIPTION
            "This TC describes the type of a PINT service."
        SYNTAX  INTEGER {
                r2C(1),     -- Request-to-Talk
                r2F(2),     -- Request-to-Fax
                r2FB(3),    -- Request-to-Fax-Back
                r2HC(4)     -- Request-to-Hear-Content
        }

PintPerfStatPeriod ::= TEXTUAL-CONVENTION
STATUS      current
DESCRIPTION
    "This TC describes the statistics period of time.

    Note that the values of the counters indexed with a value
    SinceReboot(4) can be potentially affected by a counter rollover.
    It is the responsibility of the application using this object to
    take into account that the counter has been zeroed each time it
    reached a value of (2**32-1)."
SYNTAX  INTEGER {
last30sec(1),   -- Performance Statics for the last 30 sec



Krishnaswamy & Romascanu    Standards Track                     [Page 6]

RFC 3055                        PINT MIB                   February 2001


last15min(2),   --    15 min
last24Hr(3),    --    24 Hour
sinceReboot(4)  --    Since the time the pint server was
--      last rebooted
}

pintServerConfig        OBJECT IDENTIFIER ::= { pintMib 1 }
pintServerMonitor       OBJECT IDENTIFIER ::= { pintMib 2 }
pintMibConformance      OBJECT IDENTIFIER ::= { pintMib 3 }

-- pintServerConfig - PINT configuration MIB variables

pintReleaseNumber OBJECT-TYPE
    SYNTAX      SnmpAdminString
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
     "An indication of version of the PINT protocol supported
     by this agent."
    ::= { pintServerConfig 1 }

pintSysContact           OBJECT-TYPE
    SYNTAX        SnmpAdminString
    MAX-ACCESS read-write
    STATUS current
    DESCRIPTION
     "Contact information related to the administration of the PINT
     services."
    ::= { pintServerConfig 2 }

pintApplInstallPkgTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF PintApplInstallPkgEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
     "Table describing the PINT applications that are installed."
    ::= { pintServerConfig 3 }

pintApplInstallPkgEntry OBJECT-TYPE
    SYNTAX      PintApplInstallPkgEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
     "Entries per PINT Application."
    AUGMENTS { sysApplInstallPkgEntry }
    ::= { pintApplInstallPkgTable 1 }

PintApplInstallPkgEntry ::= SEQUENCE {



Krishnaswamy & Romascanu    Standards Track                     [Page 7]