Management Information Base for the PINT Services Architecture
RFC 3055

Document Type RFC - Proposed Standard (February 2001; No errata)
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 3055 (Proposed Standard)
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
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
Show full document text