Management Information Base for Telephony Routing over IP (TRIP)
RFC 3872
Network Working Group D. Zinman
Request for Comments: 3872 D. Walker
Category: Standards Track J. Jiang
September 2004
Management Information Base
for Telephony Routing over IP (TRIP)
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 (2004).
Abstract
This memo defines a portion of the Management Information Base (MIB)
module for use with network management protocols in the Internet
community. In particular, it describes a set of managed objects that
are used to manage Telephony Routing over IP (TRIP) devices.
Table of Contents
1. The Internet-Standard Management Framework . . . . . . . . . . 2
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Conventions used in this document. . . . . . . . . . . . . . . 2
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
5. Structure of TRIP MIB. . . . . . . . . . . . . . . . . . . . . 2
5.1. Textual Conventions. . . . . . . . . . . . . . . . . . . 3
6. Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . 4
6.1. TRIP Textual Conventions . . . . . . . . . . . . . . . . 4
6.2. TRIP MIB . . . . . . . . . . . . . . . . . . . . . . . . 7
7. Security Considerations. . . . . . . . . . . . . . . . . . . . 48
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 50
8.1. Normative References . . . . . . . . . . . . . . . . . . 50
8.2. Informative References . . . . . . . . . . . . . . . . . 51
9. Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . 51
10. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 52
11. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 53
Zinman, et al. Standards Track [Page 1]
RFC 3872 MIB for TRIP September 2004
1. 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 [RFC3410].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB module objects are
generally accessed through the Simple Network Management Protocol
(SNMP). Objects in this MIB module 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 [RFC2578], STD 58, RFC 2579 [RFC2579],
and STD 58, RFC 2580 [RFC2580].
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 schedule management operations periodically or at specified dates
and times. Since TRIP [RFC3219] is modeled after the Border Gateway
Protocol (BGP-4) [RFC1771], the managed objects for TRIP are also
modeled after RFC1657 - Definitions of Managed Objects for the
Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2
[RFC1657].
3. Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this document are to be interpreted as described in BCP 14, RFC 2119
[RFC2119].
4. Overview
This MIB module provides managed objects for TRIP devices defined in
Telephony Routing over IP [RFC3219]. TRIP is an inter-domain
application-layer control protocol that exchanges information
between TRIP location servers (LS) to provide efficient IP telephony
routing.
5. Structure of TRIP MIB
This MIB module utilizes the framework described in RFC 2788
[RFC2788] for management of multiple instances of TRIP from a single
entity. The Network Services Monitoring MIB module applTable will
be populated with entries corresponding to each TRIP Location Server
Zinman, et al. Standards Track [Page 2]
RFC 3872 MIB for TRIP September 2004
in the system. Each TRIP Location Server will then have an
applIndex associated with it. The value assigned to applIndex will
represent the distinct instance of TRIP.
Show full document text