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
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
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.
The TRIP MIB module contains the following groups of objects with
each group as part of the management of a singular TRIP entity. Each
group covers a section of functionality of TRIP:
o The tripConfigGroup contains the common configuration objects
applicable to all TRIP applications referenced by the applIndex.
o The tripPeerTableConfigGroup contains the configuration objects
applicable to all TRIP peers of the Location Server referenced by
the applIndex.
o The tripRouteGroup contains the configuration objects related to
the routes of all TRIBs of this Location Server.
o The tripItadTopologyGroup contains information about the topology
of the TRIP ITADs concerning this Location Server.
o The tripPeerTableStatsGroup contains the statistical objects
applicable to all TRIP peers of the Location Server referenced by
the applIndex.
o The tripNotificationGroup contains notifications that the TRIP
application can generate.
o The tripNotifObjectGroup contains the objects needed by one or
more of the notifications.
5.1. Textual Conventions
The data types TripItad and TripId are used as textual conventions
in this document. A TRIP ITAD (IP Telephony Administrative Domain)
is described in [RFC3219]. A TRIP ID is used as a distinct
identifier for a TRIP Location Server. A TripAppProtocol is used to
identify an application protocol. A TripAddressFamily is used to
define an address family. TripCommunityId is used as a distinct
identifier for a TRIP community. TripProtocolVersion depicts the
version number of the TRIP protocol. TripSendReceiveMode describes
the operational mode of the TRIP application.
6. Definitions
6.1. TRIP Textual Conventions
TRIP-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
Unsigned32,
Integer32,
mib-2
FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION
FROM SNMPv2-TC; -- [RFC2579]
tripTC MODULE-IDENTITY
LAST-UPDATED "200409020000Z" -- Sep 02, 2004
ORGANIZATION "IETF IPTel Working Group.
Mailing list: iptel@lists.bell-labs.com"
CONTACT-INFO
"Co-editor David Zinman
postal: 265 Ridley Blvd.
Toronto ON, M5M 4N8
Canada
email: dzinman@rogers.com
phone: +1 416 433 4298
Co-editor: David Walker
Sedna Wireless Inc.
postal: 495 March Road, Suite 500
Ottawa, ON K2K 3G1
Canada
email: david.walker@sedna-wireless.com
phone: +1 613 878 8142
Co-editor Jianping Jiang
Syndesis Limited
postal: 30 Fulton Way
Richmond Hill, ON L4B 1J5
Canada
email: jjiang@syndesis.com
phone: +1 905 886-7818 x2515
"
DESCRIPTION
"Initial version of TRIP (Telephony Routing Over IP)
MIB Textual Conventions module used by other
TRIP-related MIB Modules.
Copyright (C) The Internet Society (2004). This version of
this MIB module is part of RFC 3872, see the RFC itself
for full legal notices."
REVISION "200409020000Z" -- Sep 02, 2004
DESCRIPTION
"The initial version, Published as RFC 3872."
::= { mib-2 115 }
--
-- Textual Conventions
--
TripItad ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The values for identifying the IP Telephony
Administrative Domain (ITAD)."
SYNTAX Unsigned32 (0..4294967295)
TripId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The TRIP Identifier uniquely identifies a LS within its
ITAD. It is a 4 octet unsigned integer that may, but not
necessarily, represent the IPv4 address of a Location
Server. Where bytes 1-4 of the Unsigned32 represent
1-4 bytes of the IPv4 address in network-byte order. For
an IPv6 network, TripId will not represent the IPv6
address."
SYNTAX Unsigned32 (0..4294967295)
TripAddressFamily ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A type of address for a TRIP route. Address families
defined within this MIB module are:
Code Address Family
1 Decimal Routing Numbers
2 PentaDecimal Routing Numbers
3 E.164 Numbers
255 An other type of address family"
SYNTAX INTEGER
{ decimal(1), pentadecimal(2), e164(3), other(255) }
TripAppProtocol ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The application protocol used for communication with TRIP
Location Servers. Protocols defined in this MIB Module
are:
Code Protocol
1 SIP
2 H.323-H.225.0-Q.931
3 H.323-H.225.0-RAS
4 H.323-H.225.0-Annex-G
255 An other type of application protocol"
SYNTAX INTEGER
{ sip(1), q931(2), ras(3), annexG(4), other(255) }
TripCommunityId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The range of legal values for a TRIP Community
Identifier."
SYNTAX Unsigned32 (0..4294967295)
TripProtocolVersion ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The version number of the TRIP protocol."
SYNTAX Integer32 (1..255)
TripSendReceiveMode ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The operational mode of the TRIP application. Possible
values are:
1 - Send Receive mode
2 - Send only mode
3 - Receive Only mode"
SYNTAX INTEGER { sendReceive(1), sendOnly(2), receiveOnly(3) }
END
6.2. TRIP MIB
TRIP-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
OBJECT-TYPE,
NOTIFICATION-TYPE,
Unsigned32,
Integer32,
Counter32,
mib-2
FROM SNMPv2-SMI -- [RFC2578]
DateAndTime,
TimeInterval,
TruthValue,
TimeStamp,
StorageType,
RowStatus
FROM SNMPv2-TC -- [RFC2579]
OBJECT-GROUP,
MODULE-COMPLIANCE,
NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580]
InetAddressType,
InetAddress,
InetPortNumber
FROM INET-ADDRESS-MIB -- [RFC3291]
applIndex,
applRFC2788Group
FROM NETWORK-SERVICES-MIB -- [RFC2788]
TripItad,
TripId,
TripAppProtocol,
TripAddressFamily,
TripCommunityId,
TripProtocolVersion,
TripSendReceiveMode
FROM TRIP-TC-MIB; -- [RFC3872]
tripMIB MODULE-IDENTITY
LAST-UPDATED "200409020000Z" -- Sep 02, 2004
ORGANIZATION "IETF IPTel Working Group.
Mailing list: iptel@lists.bell-labs.com"
CONTACT-INFO
"Co-editor David Zinman
postal: 265 Ridley Blvd.
Toronto ON, M5M 4N8
Canada
email: dzinman@rogers.com
phone: +1 416 433 4298
Co-editor: David Walker
Sedna Wireless Inc.
postal: 495 March Road, Suite 500
Ottawa, ON K2K 3G1
Canada
email: david.walker@sedna-wireless.com
phone: +1 613 878 8142
Co-editor Jianping Jiang
Syndesis Limited
postal: 30 Fulton Way
Richmond Hill, ON L4B 1J5
Canada
email: jjiang@syndesis.com
phone: +1 905 886-7818 x2515
"
DESCRIPTION
"The MIB module describing Telephony Routing over IP
(TRIP). TRIP is a policy driven inter-administrative
domain protocol for advertising the reachability of
telephony destinations between location servers (LS), and
for advertising attributes of the routes to those
destinations.
Copyright (C) The Internet Society (2004). This version of
this MIB module is part of RFC 3872, see the RFC itself
for full legal notices."
REVISION "200409020000Z" -- Sep 02, 2004
DESCRIPTION
"The initial version, Published as RFC 3872."
::= { mib-2 116 }
tripMIBNotifications OBJECT IDENTIFIER ::= { tripMIB 0 }
tripMIBObjects OBJECT IDENTIFIER ::= { tripMIB 1 }
tripMIBConformance OBJECT IDENTIFIER ::= { tripMIB 2 }
tripMIBNotifObjects OBJECT IDENTIFIER ::= { tripMIB 3 }
tripMIBCompliances OBJECT IDENTIFIER ::=
{ tripMIBConformance 1 }
tripMIBGroups OBJECT IDENTIFIER ::=
{ tripMIBConformance 2 }
--
-- tripCfgTable
--
tripCfgTable OBJECT-TYPE
SYNTAX SEQUENCE OF TripCfgEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains the common configuration objects
applicable to all TRIP applications referenced by the
applIndex. Each row represents those objects for a
particular TRIP LS present in this system. The
instances of TRIP LS’s are uniquely identified by the
applIndex. The objects in this table SHOULD be
nonVolatile and survive a reboot."
::= { tripMIBObjects 1 }
tripCfgEntry OBJECT-TYPE
SYNTAX TripCfgEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row of common configuration."
INDEX { applIndex }
::= { tripCfgTable 1 }
TripCfgEntry ::=
SEQUENCE {
tripCfgProtocolVersion TripProtocolVersion,
tripCfgItad TripItad,
tripCfgIdentifier TripId,
tripCfgAdminStatus INTEGER,
tripCfgOperStatus INTEGER,
tripCfgAddrIAddrType InetAddressType,
tripCfgAddr InetAddress,
tripCfgPort InetPortNumber,
tripCfgMinItadOriginationInterval Unsigned32,
tripCfgMinRouteAdvertisementInterval Unsigned32,
tripCfgMaxPurgeTime Unsigned32,
tripCfgDisableTime Unsigned32,
tripCfgSendReceiveMode TripSendReceiveMode,
tripCfgStorage StorageType
}
tripCfgProtocolVersion OBJECT-TYPE
SYNTAX TripProtocolVersion
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object will reflect the version of TRIP
supported by this system. It follows the same
format as TRIP version information contained
in the TRIP messages generated by this TRIP entity."
REFERENCE
"RFC 3219, section 4.2."
::= { tripCfgEntry 1 }
tripCfgItad OBJECT-TYPE
SYNTAX TripItad
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The Internet Telephony Administrative domain (ITAD)
of this LS."
::= { tripCfgEntry 2 }
tripCfgIdentifier OBJECT-TYPE
SYNTAX TripId
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The object that identifies this TRIP Client."
::= { tripCfgEntry 3 }
tripCfgAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
up(1),
down(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The desired TRIP state.
up(1) : Set the application to normal operation.
down(2): Set the application to a state where it will
not process TRIP messages.
Setting this object should be reflected in
tripCfgOperStatus. If an unknown error occurs
tripCfgOperStatus will return unknown(0)."
::= { tripCfgEntry 4 }
tripCfgOperStatus OBJECT-TYPE
SYNTAX INTEGER {
unknown(0),
up(1),
down(2),
faulty(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current operational state of the TRIP protocol.
unknown(0): The operating status of the application is
unknown.
up(1): The application is operating normally, and
is ready to process (receive and issue) TRIP
requests and responses.
down(2): The application is currently not processing
TRIP messages. This occurs if the TRIP
application is in an initialization state or
if tripCfgAdminStatus is set to down(2).
faulty(3): The application is not operating normally due
to a fault in the system.
If tripCfgAdminStatus is down(2) then tripOperStatus SHOULD
be down(2). If tripAdminStatus is changed to up(1) then
tripOperStatus SHOULD change to up(1) if there is no
fault that prevents the TRIP protocol from moving to the
up(1) state."
::= { tripCfgEntry 5 }
tripCfgAddrIAddrType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of Inet Address of the tripAddr."
REFERENCE