draft-ietf-iptel-trip-mib-10.txt   rfc3872.txt 
Internet Draft D. Zinman Network Working Group D. Zinman
Document: draft-ietf-iptel-trip-mib-10.txt D. Walker Request for Comments: 3872 D. Walker
Expires: August 2004 J. Jiang Category: Standards Track J. Jiang
September 2004
Management Information Base Management Information Base
for Telephony Routing over IP (TRIP) for Telephony Routing over IP (TRIP)
<draft-ietf-iptel-trip-mib-10.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document specifies an Internet standards track protocol for the
all provisions of Section 10 of RFC 2026 [RFC2026]. Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Internet-Drafts are working documents of the Internet Engineering Official Protocol Standards" (STD 1) for the standardization state
Task Force (IETF), its areas, and its working groups. Note that and status of this protocol. Distribution of this memo is unlimited.
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.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004).
Abstract Abstract
This memo defines a portion of the MIB (Management Information Base) This memo defines a portion of the Management Information Base (MIB)
module for use with network management protocols in the Internet module for use with network management protocols in the Internet
community. In particular, it describes a set of managed objects that community. In particular, it describes a set of managed objects that
are used to manage TRIP (Telephony Routing over IP) devices. are used to manage Telephony Routing over IP (TRIP) devices.
Zinman/Walker/Jiang 1
Table of Contents Table of Contents
Status of this Memo................................................1 1. The Internet-Standard Management Framework . . . . . . . . . . 2
Copyright Notice...................................................1 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
Abstract...........................................................1 3. Conventions used in this document. . . . . . . . . . . . . . . 2
1. The Internet-Standard Management Framework....................3 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Introduction..................................................3 5. Structure of TRIP MIB. . . . . . . . . . . . . . . . . . . . . 2
3. Conventions used in this document.............................3 5.1. Textual Conventions. . . . . . . . . . . . . . . . . . . 3
4. Overview......................................................3 6. Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. Structure of TRIP MIB.........................................3 6.1. TRIP Textual Conventions . . . . . . . . . . . . . . . . 4
5.1 Textual Conventions.........................................4 6.2. TRIP MIB . . . . . . . . . . . . . . . . . . . . . . . . 7
6. Definitions...................................................4 7. Security Considerations. . . . . . . . . . . . . . . . . . . . 48
6.1 TRIP Textual Conventions....................................4 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 50
6.2 TRIP MIB ...................................................7 8.1. Normative References . . . . . . . . . . . . . . . . . . 50
7. Security Considerations......................................45 8.2. Informative References . . . . . . . . . . . . . . . . . 51
8. Full Copyright Statement.....................................47 9. Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . 51
9. Normative References.........................................48 10. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 52
10. Informative References.......................................48 11. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 53
11. Intellectual Property Notice.................................48
12. Acknowledgments..............................................49
13. Author's Addresses...........................................49
Zinman/Walker/Jiang 2
1. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB module objects are the Management Information Base or MIB. MIB module objects are
generally accessed through the Simple Network Management Protocol generally accessed through the Simple Network Management Protocol
(SNMP). Objects in this MIB module are defined using the mechanisms (SNMP). Objects in this MIB module are defined using the mechanisms
defined in the Structure of Management Information (SMI). This memo defined in the Structure of Management Information (SMI). This memo
specifies a MIB module that is compliant to the SMIv2, which is specifies a MIB module that is compliant to the SMIv2, which is
described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579],
and STD 58, RFC 2580 [RFC2580]. and STD 58, RFC 2580 [RFC2580].
2. Introduction 2. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes a set of managed objects that are used In particular, it describes a set of managed objects that are used
to schedule management operations periodically or at specified dates to schedule management operations periodically or at specified dates
and times. Since TRIP [RFC3219] is modeled after the Border Gateway and times. Since TRIP [RFC3219] is modeled after the Border Gateway
Protocol (BGP-4) [RFC1771], the managed objects for TRIP are also Protocol (BGP-4) [RFC1771], the managed objects for TRIP are also
modeled after RFC1657 - Definitions of Managed Objects for the modeled after RFC1657 - Definitions of Managed Objects for the
Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2 Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2
[RFC1657]. [RFC1657].
3. Conventions used in this document 3. Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this document are to be interpreted as described in BCP-0014 this document are to be interpreted as described in BCP 14, RFC 2119
[BCP0014]. [RFC2119].
4. Overview 4. Overview
This MIB module provides managed objects for TRIP devices defined in This MIB module provides managed objects for TRIP devices defined in
Telephony Routing over IP [RFC3219]. TRIP is an inter-domain Telephony Routing over IP [RFC3219]. TRIP is an inter-domain
application-layer control protocol that exchanges information application-layer control protocol that exchanges information
between TRIP location servers (LS) to provide efficient IP telephony between TRIP location servers (LS) to provide efficient IP telephony
routing. routing.
5. Structure of TRIP MIB 5. Structure of TRIP MIB
This MIB module utilizes the framework described in RFC 2788 This MIB module utilizes the framework described in RFC 2788
[RFC2788] for management of multiple instances of TRIP from a single [RFC2788] for management of multiple instances of TRIP from a single
entity. The Network Services Monitoring MIB module applTable will entity. The Network Services Monitoring MIB module applTable will
be populated with entries corresponding to each TRIP Location Server be populated with entries corresponding to each TRIP Location Server
in the system. Each TRIP Location Server will then have an in the system. Each TRIP Location Server will then have an
applIndex associated with it. The value assigned to applIndex will applIndex associated with it. The value assigned to applIndex will
represent the distinct instance of TRIP. represent the distinct instance of TRIP.
Zinman/Walker/Jiang 3
The TRIP MIB module contains the following groups of objects with The TRIP MIB module contains the following groups of objects with
each group as part of the management of a singular TRIP entity. Each each group as part of the management of a singular TRIP entity. Each
group covers a section of functionality of TRIP: group covers a section of functionality of TRIP:
o The tripConfigGroup contains the common configuration objects o The tripConfigGroup contains the common configuration objects
applicable to all TRIP applications referenced by the applIndex. applicable to all TRIP applications referenced by the applIndex.
o The tripPeerTableConfigGroup contains the configuration objects o The tripPeerTableConfigGroup contains the configuration objects
applicable to all TRIP peers of the Location Server referenced by applicable to all TRIP peers of the Location Server referenced by
the applIndex. the applIndex.
o The tripRouteGroup contains the configuration objects related to o The tripRouteGroup contains the configuration objects related to
the routes of all TRIBs of this Location Server. the routes of all TRIBs of this Location Server.
o The tripItadTopologyGroup contains information about the topology o The tripItadTopologyGroup contains information about the topology
of the TRIP ITADs concerning this Location Server. of the TRIP ITADs concerning this Location Server.
o The tripPeerTableStatsGroup contains the statistical objects o The tripPeerTableStatsGroup contains the statistical objects
applicable to all TRIP peers of the Location Server referenced by applicable to all TRIP peers of the Location Server referenced by
the applIndex. the applIndex.
o The tripNotificationGroup contains notifications that the TRIP o The tripNotificationGroup contains notifications that the TRIP
application can generate. application can generate.
o The tripNotifObjectGroup contains the objects needed by one or o The tripNotifObjectGroup contains the objects needed by one or
more of the notifications. more of the notifications.
5.1 Textual Conventions 5.1. Textual Conventions
The data types TripItad and TripId are used as textual conventions The data types TripItad and TripId are used as textual conventions
in this document. A TRIP ITAD (IP Telephony Administrative Domain) in this document. A TRIP ITAD (IP Telephony Administrative Domain)
is described in [RFC3219]. A TRIP ID is used as a distinct is described in [RFC3219]. A TRIP ID is used as a distinct
identifier for a TRIP Location Server. A TripAppProtocol is used to identifier for a TRIP Location Server. A TripAppProtocol is used to
identify an application protocol. A TripAddressFamily is used to identify an application protocol. A TripAddressFamily is used to
define an address family. TripCommunityId is used as a distinct define an address family. TripCommunityId is used as a distinct
identifier for a TRIP community. TripProtocolVersion depicts the identifier for a TRIP community. TripProtocolVersion depicts the
version number of the TRIP protocol. TripSendReceiveMode describes version number of the TRIP protocol. TripSendReceiveMode describes
the operational mode of the TRIP application. the operational mode of the TRIP application.
6. Definitions 6. Definitions
6.1 TRIP Textual Conventions 6.1. TRIP Textual Conventions
TRIP-TC DEFINITIONS ::= BEGIN TRIP-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
Unsigned32, Unsigned32,
Integer32, Integer32,
mib-2 mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC; FROM SNMPv2-TC; -- [RFC2579]
tripTC MODULE-IDENTITY tripTC MODULE-IDENTITY
LAST-UPDATED "200402050000Z" -- Feb 05, 2004 LAST-UPDATED "200409020000Z" -- Sep 02, 2004
Zinman/Walker/Jiang 4
ORGANIZATION "IETF IPTel Working Group. ORGANIZATION "IETF IPTel Working Group.
Mailing list: iptel@lists.bell-labs.com" Mailing list: iptel@lists.bell-labs.com"
CONTACT-INFO CONTACT-INFO
"Co-editor David Zinman "Co-editor David Zinman
postal: 265 Ridley Blvd. postal: 265 Ridley Blvd.
Toronto ON, M5M 4N8 Toronto ON, M5M 4N8
Canada Canada
email: dzinman@rogers.com email: dzinman@rogers.com
phone: +1 416 433 4298 phone: +1 416 433 4298
Co-editor Dave Walker Co-editor: David Walker
SS8 Networks, Inc. Sedna Wireless Inc.
postal: 495 March Road, Suite #500 postal: 495 March Road, Suite 500
Ottawa, ON, K2K 3G1 Ottawa, ON K2K 3G1
Canada Canada
email: drwalker@ss8.com email: david.walker@sedna-wireless.com
phone: +1 613 592 2100 phone: +1 613 878 8142
Co-editor Jianping Jiang Co-editor Jianping Jiang
SGNT Technologies, Inc. Syndesis Limited
postal: 5850 Keaton Crescent postal: 30 Fulton Way
Mississauga, ON L5R 3K2 Richmond Hill, ON L4B 1J5
Canada Canada
email: jjiang@sgntt.com
phone: +1 905 290 1384 email: jjiang@syndesis.com
phone: +1 905 886-7818 x2515
" "
DESCRIPTION DESCRIPTION
"Initial version of TRIP (Telephony Routing Over IP) "Initial version of TRIP (Telephony Routing Over IP)
MIB Textual Conventions module used by other MIB Textual Conventions module used by other
TRIP-related MIB Modules. TRIP-related MIB Modules.
Copyright (C) The Internet Society (2004). This version of Copyright (C) The Internet Society (2004). This version of
this MIB module is part of RFC xxxx, see the RFC itself this MIB module is part of RFC 3872, see the RFC itself
for full legal notices." for full legal notices."
REVISION "200402050000Z" -- Feb 05, 2004 REVISION "200409020000Z" -- Sep 02, 2004
DESCRIPTION DESCRIPTION
"The initial version, Published as RFC xxxx." "The initial version, Published as RFC 3872."
::= { mib-2 xxxx } -- to be assigned by IANA ::= { mib-2 115 }
-- --
-- Textual Conventions -- Textual Conventions
-- --
TripItad ::= TEXTUAL-CONVENTION TripItad ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The values for identifying the IP Telephony "The values for identifying the IP Telephony
Administrative Domain (ITAD)." Administrative Domain (ITAD)."
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
TripId ::= TEXTUAL-CONVENTION TripId ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at line 225 skipping to change at page 5, line 28
TripItad ::= TEXTUAL-CONVENTION TripItad ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The values for identifying the IP Telephony "The values for identifying the IP Telephony
Administrative Domain (ITAD)." Administrative Domain (ITAD)."
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
TripId ::= TEXTUAL-CONVENTION TripId ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
Zinman/Walker/Jiang 5
"The TRIP Identifier uniquely identifies a LS within its "The TRIP Identifier uniquely identifies a LS within its
ITAD. It is a 4 octet unsigned integer that may, but not ITAD. It is a 4 octet unsigned integer that may, but not
necessarily, represent the IPv4 address of a Location necessarily, represent the IPv4 address of a Location
Server. Where bytes 1-4 of the Unsigned32 represent Server. Where bytes 1-4 of the Unsigned32 represent
1-4 bytes of the IPv4 address in network-byte order. For 1-4 bytes of the IPv4 address in network-byte order. For
an IPv6 network, TripId will not represent the IPv6 an IPv6 network, TripId will not represent the IPv6
address." address."
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
TripAddressFamily ::= TEXTUAL-CONVENTION TripAddressFamily ::= TEXTUAL-CONVENTION
skipping to change at line 279 skipping to change at page 6, line 33
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The range of legal values for a TRIP Community "The range of legal values for a TRIP Community
Identifier." Identifier."
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
TripProtocolVersion ::= TEXTUAL-CONVENTION TripProtocolVersion ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The version number of the TRIP protocol." "The version number of the TRIP protocol."
Zinman/Walker/Jiang 6
SYNTAX Integer32 (1..255) SYNTAX Integer32 (1..255)
TripSendReceiveMode ::= TEXTUAL-CONVENTION TripSendReceiveMode ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The operational mode of the TRIP application. Possible "The operational mode of the TRIP application. Possible
values are: values are:
1 - Send Receive mode 1 - Send Receive mode
2 - Send only mode 2 - Send only mode
3 - Receive Only mode" 3 - Receive Only mode"
SYNTAX INTEGER { sendReceive(1), sendOnly(2), receiveOnly(3) } SYNTAX INTEGER { sendReceive(1), sendOnly(2), receiveOnly(3) }
END END
6.2 TRIP MIB 6.2. TRIP MIB
TRIP-MIB DEFINITIONS ::= BEGIN TRIP-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
NOTIFICATION-TYPE, NOTIFICATION-TYPE,
Unsigned32, Unsigned32,
Integer32, Integer32,
Counter32, Counter32,
mib-2 mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI -- [RFC2578]
DateAndTime, DateAndTime,
TimeInterval, TimeInterval,
TruthValue, TruthValue,
TimeStamp, TimeStamp,
StorageType, StorageType,
RowStatus RowStatus
FROM SNMPv2-TC FROM SNMPv2-TC -- [RFC2579]
OBJECT-GROUP, OBJECT-GROUP,
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
NOTIFICATION-GROUP NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF -- [RFC2580]
InetAddressType, InetAddressType,
InetAddress, InetAddress,
InetPortNumber InetPortNumber
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB -- [RFC3291]
applIndex, applIndex,
applRFC2788Group applRFC2788Group
FROM NETWORK-SERVICES-MIB FROM NETWORK-SERVICES-MIB -- [RFC2788]
TripItad, TripItad,
TripId, TripId,
Zinman/Walker/Jiang 7
TripAppProtocol, TripAppProtocol,
TripAddressFamily, TripAddressFamily,
TripCommunityId, TripCommunityId,
TripProtocolVersion, TripProtocolVersion,
TripSendReceiveMode TripSendReceiveMode
FROM TRIP-TC; FROM TRIP-TC-MIB; -- [RFC3872]
tripMIB MODULE-IDENTITY tripMIB MODULE-IDENTITY
LAST-UPDATED "200402050000Z" -- Feb 05, 2004 LAST-UPDATED "200409020000Z" -- Sep 02, 2004
ORGANIZATION "IETF IPTel Working Group. ORGANIZATION "IETF IPTel Working Group.
Mailing list: iptel@lists.bell-labs.com" Mailing list: iptel@lists.bell-labs.com"
CONTACT-INFO CONTACT-INFO
"Co-editor David Zinman "Co-editor David Zinman
postal: 265 Ridley Blvd. postal: 265 Ridley Blvd.
Toronto ON, M5M 4N8 Toronto ON, M5M 4N8
Canada Canada
email: dzinman@rogers.com email: dzinman@rogers.com
phone: +1 416 433 4298 phone: +1 416 433 4298
skipping to change at line 355 skipping to change at page 8, line 15
Mailing list: iptel@lists.bell-labs.com" Mailing list: iptel@lists.bell-labs.com"
CONTACT-INFO CONTACT-INFO
"Co-editor David Zinman "Co-editor David Zinman
postal: 265 Ridley Blvd. postal: 265 Ridley Blvd.
Toronto ON, M5M 4N8 Toronto ON, M5M 4N8
Canada Canada
email: dzinman@rogers.com email: dzinman@rogers.com
phone: +1 416 433 4298 phone: +1 416 433 4298
Co-editor Dave Walker Co-editor: David Walker
SS8 Networks, Inc. Sedna Wireless Inc.
postal: 495 March Road, Suite #500 postal: 495 March Road, Suite 500
Ottawa, ON, K2K 3G1 Ottawa, ON K2K 3G1
Canada Canada
email: drwalker@ss8.com email: david.walker@sedna-wireless.com
phone: +1 613 592 2100 phone: +1 613 878 8142
Co-editor Jianping Jiang Co-editor Jianping Jiang
SGNT Technologies, Inc. Syndesis Limited
postal: 5850 Keaton Crescent postal: 30 Fulton Way
Mississauga, ON L5R 3K2 Richmond Hill, ON L4B 1J5
Canada Canada
email: jjiang@sgntt.com
phone: +1 905 290 1384 email: jjiang@syndesis.com
phone: +1 905 886-7818 x2515
" "
DESCRIPTION DESCRIPTION
"The MIB module describing Telephony Routing over IP "The MIB module describing Telephony Routing over IP
(TRIP). TRIP is a policy driven inter-administrative (TRIP). TRIP is a policy driven inter-administrative
domain protocol for advertising the reachability of domain protocol for advertising the reachability of
telephony destinations between location servers (LS), and telephony destinations between location servers (LS), and
for advertising attributes of the routes to those for advertising attributes of the routes to those
destinations. destinations.
Copyright (C) The Internet Society (2004). This version of Copyright (C) The Internet Society (2004). This version of
this MIB module is part of RFC xxxx, see the RFC itself this MIB module is part of RFC 3872, see the RFC itself
for full legal notices." for full legal notices."
REVISION "200402050000Z" -- Feb 05, 2004 REVISION "200409020000Z" -- Sep 02, 2004
DESCRIPTION DESCRIPTION
"The initial version, Published as RFC xxxx." "The initial version, Published as RFC 3872."
::= { mib-2 xxxx } -- to be assigned by IANA ::= { mib-2 116 }
Zinman/Walker/Jiang 8
tripMIBNotifications OBJECT IDENTIFIER ::= { tripMIB 0 } tripMIBNotifications OBJECT IDENTIFIER ::= { tripMIB 0 }
tripMIBObjects OBJECT IDENTIFIER ::= { tripMIB 1 } tripMIBObjects OBJECT IDENTIFIER ::= { tripMIB 1 }
tripMIBConformance OBJECT IDENTIFIER ::= { tripMIB 2 } tripMIBConformance OBJECT IDENTIFIER ::= { tripMIB 2 }
tripMIBNotifObjects OBJECT IDENTIFIER ::= { tripMIB 3 } tripMIBNotifObjects OBJECT IDENTIFIER ::= { tripMIB 3 }
tripMIBCompliances OBJECT IDENTIFIER ::= tripMIBCompliances OBJECT IDENTIFIER ::=
{ tripMIBConformance 1 } { tripMIBConformance 1 }
tripMIBGroups OBJECT IDENTIFIER ::= tripMIBGroups OBJECT IDENTIFIER ::=
{ tripMIBConformance 2 } { tripMIBConformance 2 }
-- --
-- tripCfgTable -- tripCfgTable
-- --
tripCfgTable OBJECT-TYPE tripCfgTable OBJECT-TYPE
SYNTAX SEQUENCE OF TripCfgEntry SYNTAX SEQUENCE OF TripCfgEntry
skipping to change at line 440 skipping to change at page 9, line 51
tripCfgOperStatus INTEGER, tripCfgOperStatus INTEGER,
tripCfgAddrIAddrType InetAddressType, tripCfgAddrIAddrType InetAddressType,
tripCfgAddr InetAddress, tripCfgAddr InetAddress,
tripCfgPort InetPortNumber, tripCfgPort InetPortNumber,
tripCfgMinItadOriginationInterval Unsigned32, tripCfgMinItadOriginationInterval Unsigned32,
tripCfgMinRouteAdvertisementInterval Unsigned32, tripCfgMinRouteAdvertisementInterval Unsigned32,
tripCfgMaxPurgeTime Unsigned32, tripCfgMaxPurgeTime Unsigned32,
tripCfgDisableTime Unsigned32, tripCfgDisableTime Unsigned32,
tripCfgSendReceiveMode TripSendReceiveMode, tripCfgSendReceiveMode TripSendReceiveMode,
tripCfgStorage StorageType tripCfgStorage StorageType
Zinman/Walker/Jiang 9
} }
tripCfgProtocolVersion OBJECT-TYPE tripCfgProtocolVersion OBJECT-TYPE
SYNTAX TripProtocolVersion SYNTAX TripProtocolVersion
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object will reflect the version of TRIP "This object will reflect the version of TRIP
supported by this system. It follows the same supported by this system. It follows the same
format as TRIP version information contained format as TRIP version information contained
in the TRIP messages generated by this TRIP entity." in the TRIP messages generated by this TRIP entity."
REFERENCE REFERENCE
skipping to change at line 490 skipping to change at page 10, line 50
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The desired TRIP state. "The desired TRIP state.
up(1) : Set the application to normal operation. up(1) : Set the application to normal operation.
down(2): Set the application to a state where it will down(2): Set the application to a state where it will
not process TRIP messages. not process TRIP messages.
Setting this object should be reflected in Setting this object should be reflected in
tripCfgOperStatus. If an unkown error occurs tripCfgOperStatus. If an unknown error occurs
tripCfgOperStatus will return unknown(0)." tripCfgOperStatus will return unknown(0)."
::= { tripCfgEntry 4 } ::= { tripCfgEntry 4 }
Zinman/Walker/Jiang 10
tripCfgOperStatus OBJECT-TYPE tripCfgOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(0), unknown(0),
up(1), up(1),
down(2), down(2),
faulty(3) faulty(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at line 547 skipping to change at page 12, line 10
::= { tripCfgEntry 6 } ::= { tripCfgEntry 6 }
tripCfgAddr OBJECT-TYPE tripCfgAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The network address of the local LS that the peer "The network address of the local LS that the peer
connects to. The type of address depends on the object connects to. The type of address depends on the object
tripCfgAddrIAddrType. The type of this address is tripCfgAddrIAddrType. The type of this address is
Zinman/Walker/Jiang 11
determined by the value of the determined by the value of the
tripCfgAddrIAddrType object." tripCfgAddrIAddrType object."
REFERENCE REFERENCE
"RFC 3291, section 3." "RFC 3291, section 3."
::= { tripCfgEntry 7 } ::= { tripCfgEntry 7 }
tripCfgPort OBJECT-TYPE tripCfgPort OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
skipping to change at line 601 skipping to change at page 13, line 14
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the interval that the LS MUST maintain routes "Indicates the interval that the LS MUST maintain routes
marked as withdrawn in its database." marked as withdrawn in its database."
DEFVAL { 10 } DEFVAL { 10 }
::= { tripCfgEntry 11 } ::= { tripCfgEntry 11 }
tripCfgDisableTime OBJECT-TYPE tripCfgDisableTime OBJECT-TYPE
SYNTAX Unsigned32 (1..2147483647) SYNTAX Unsigned32 (1..2147483647)
UNITS "Seconds" UNITS "Seconds"
Zinman/Walker/Jiang 12
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the interval that the TRIP module of the "Indicates the interval that the TRIP module of the
LS MUST be disabled while routes originated by this LS MUST be disabled while routes originated by this
LS with high sequence numbers can be removed." LS with high sequence numbers can be removed."
DEFVAL { 180 } DEFVAL { 180 }
::= { tripCfgEntry 12 } ::= { tripCfgEntry 12 }
tripCfgSendReceiveMode OBJECT-TYPE tripCfgSendReceiveMode OBJECT-TYPE
skipping to change at line 655 skipping to change at page 14, line 18
tripRouteTypeEntry OBJECT-TYPE tripRouteTypeEntry OBJECT-TYPE
SYNTAX TripRouteTypeEntry SYNTAX TripRouteTypeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry containing information about the route type "An entry containing information about the route type
that a particular TRIP entity supports. Each entry that a particular TRIP entity supports. Each entry
represents information about either the local or a remote represents information about either the local or a remote
LS peer. The object tripRouteTypePeer is used to LS peer. The object tripRouteTypePeer is used to
Zinman/Walker/Jiang 13
distinguish this. In the case of a local LS, the distinguish this. In the case of a local LS, the
address/port information will reflect the values address/port information will reflect the values
configured in tripCfgTable. In the case of a remote configured in tripCfgTable. In the case of a remote
peer, the address/port information will reflect the peer, the address/port information will reflect the
values of an entry in the tripPeerTable. values of an entry in the tripPeerTable.
Implementation need to be aware that if the size of Implementation need to be aware that if the size of
tripRouteTypeAddr exceeds 111 sub-IDs, then OIDs of column tripRouteTypeAddr exceeds 111 sub-IDs, then OIDs of column
instances in this table will have more than 128 sub-IDs instances in this table will have more than 128 sub-IDs
and cannot be accessed using SNMPv1, SNMPv2c, or snmpv3." and cannot be accessed using SNMPv1, SNMPv2c, or snmpv3."
skipping to change at line 709 skipping to change at page 15, line 22
"The network address of this entry's TRIP peer LS. The "The network address of this entry's TRIP peer LS. The
type of this address is determined by the value of the type of this address is determined by the value of the
tripRouteTypeAddrInetType object." tripRouteTypeAddrInetType object."
REFERENCE REFERENCE
"RFC 3291, section 3." "RFC 3291, section 3."
::= { tripRouteTypeEntry 2 } ::= { tripRouteTypeEntry 2 }
tripRouteTypePort OBJECT-TYPE tripRouteTypePort OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
Zinman/Walker/Jiang 14
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The port for the TCP connection between this and "The port for the TCP connection between this and
an associated TRIP peer." an associated TRIP peer."
::= { tripRouteTypeEntry 3 } ::= { tripRouteTypeEntry 3 }
tripRouteTypeProtocolId OBJECT-TYPE tripRouteTypeProtocolId OBJECT-TYPE
SYNTAX TripAppProtocol SYNTAX TripAppProtocol
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at line 764 skipping to change at page 16, line 27
TRIP community is a group of destinations that share TRIP community is a group of destinations that share
common properties. common properties.
The TRIP Supported Communities entry is used to group The TRIP Supported Communities entry is used to group
destinations so that the routing decision can be based destinations so that the routing decision can be based
on the identity of the group." on the identity of the group."
REFERENCE REFERENCE
"RFC 3219, section 5.9" "RFC 3219, section 5.9"
::= { tripMIBObjects 3 } ::= { tripMIBObjects 3 }
Zinman/Walker/Jiang 15
tripSupportedCommunityEntry OBJECT-TYPE tripSupportedCommunityEntry OBJECT-TYPE
SYNTAX TripSupportedCommunityEntry SYNTAX TripSupportedCommunityEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Entry containing information about a community. A TRIP "Entry containing information about a community. A TRIP
community is a group of destinations that share some community is a group of destinations that share some
common property. This attribute is used so that routing common property. This attribute is used so that routing
decisions can be based on the identity of the group." decisions can be based on the identity of the group."
INDEX { applIndex, tripSupportedCommunityId } INDEX { applIndex, tripSupportedCommunityId }
skipping to change at line 816 skipping to change at page 17, line 30
rows having the value 'permanent' need not allow write- rows having the value 'permanent' need not allow write-
access to any columnar objects in the row. It is not a access to any columnar objects in the row. It is not a
requirement that this storage be non volatile." requirement that this storage be non volatile."
DEFVAL { nonVolatile } DEFVAL { nonVolatile }
::= { tripSupportedCommunityEntry 3 } ::= { tripSupportedCommunityEntry 3 }
tripSupportedCommunityRowStatus OBJECT-TYPE tripSupportedCommunityRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
Zinman/Walker/Jiang 16
DESCRIPTION DESCRIPTION
"The row status of the entry. This object is REQUIRED "The row status of the entry. This object is REQUIRED
to create or delete rows by a manager. A value for to create or delete rows by a manager. A value for
tripSupportedCommunityItad MUST be set for row creation tripSupportedCommunityItad MUST be set for row creation
to be successful. If the instance already exists for a to be successful. If the instance already exists for a
particular applIndex, the row create operation will particular applIndex, the row create operation will
fail. fail.
The value of this object has no effect on whether The value of this object has no effect on whether
other objects in this conceptual row can be modified." other objects in this conceptual row can be modified."
skipping to change at line 870 skipping to change at page 18, line 34
::= {tripPeerTable 1} ::= {tripPeerTable 1}
TripPeerEntry ::= SEQUENCE { TripPeerEntry ::= SEQUENCE {
tripPeerRemoteAddrInetType InetAddressType, tripPeerRemoteAddrInetType InetAddressType,
tripPeerRemoteAddr InetAddress, tripPeerRemoteAddr InetAddress,
tripPeerRemotePort InetPortNumber, tripPeerRemotePort InetPortNumber,
tripPeerIdentifier TripId, tripPeerIdentifier TripId,
tripPeerState INTEGER, tripPeerState INTEGER,
tripPeerAdminStatus INTEGER, tripPeerAdminStatus INTEGER,
tripPeerNegotiatedVersion TripProtocolVersion, tripPeerNegotiatedVersion TripProtocolVersion,
Zinman/Walker/Jiang 17
tripPeerSendReceiveMode TripSendReceiveMode, tripPeerSendReceiveMode TripSendReceiveMode,
tripPeerRemoteItad TripItad, tripPeerRemoteItad TripItad,
tripPeerConnectRetryInterval Unsigned32, tripPeerConnectRetryInterval Unsigned32,
tripPeerMaxRetryInterval Unsigned32, tripPeerMaxRetryInterval Unsigned32,
tripPeerHoldTime Unsigned32, tripPeerHoldTime Unsigned32,
tripPeerKeepAlive Unsigned32, tripPeerKeepAlive Unsigned32,
tripPeerHoldTimeConfigured Unsigned32, tripPeerHoldTimeConfigured Unsigned32,
tripPeerKeepAliveConfigured Unsigned32, tripPeerKeepAliveConfigured Unsigned32,
tripPeerMaxPurgeTime Unsigned32, tripPeerMaxPurgeTime Unsigned32,
tripPeerDisableTime Unsigned32, tripPeerDisableTime Unsigned32,
skipping to change at line 924 skipping to change at page 19, line 38
"The remote port for the TCP connection between the "The remote port for the TCP connection between the
TRIP peers." TRIP peers."
::= { tripPeerEntry 3 } ::= { tripPeerEntry 3 }
tripPeerIdentifier OBJECT-TYPE tripPeerIdentifier OBJECT-TYPE
SYNTAX TripId SYNTAX TripId
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"TRIP identifier of the peer." "TRIP identifier of the peer."
Zinman/Walker/Jiang 18
::= { tripPeerEntry 4 } ::= { tripPeerEntry 4 }
tripPeerState OBJECT-TYPE tripPeerState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
idle(1), idle(1),
connect(2), connect(2),
active(3), active(3),
openSent(4), openSent(4),
openConfirm(5), openConfirm(5),
established(6) established(6)
skipping to change at line 978 skipping to change at page 20, line 42
established(6): LS can exchange UPDATE, NOTIFICATION, and established(6): LS can exchange UPDATE, NOTIFICATION, and
KEEPALIVE messages with its peer." KEEPALIVE messages with its peer."
::= { tripPeerEntry 5 } ::= { tripPeerEntry 5 }
tripPeerAdminStatus OBJECT-TYPE tripPeerAdminStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
up(1), up(1),
down(2) down(2)
} }
Zinman/Walker/Jiang 19
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to affect the TRIP connection "This object is used to affect the TRIP connection
state. state.
up(1) : Allow a connection with the peer LS. up(1) : Allow a connection with the peer LS.
down(2) : disconnect the connection from the peer LS and down(2) : disconnect the connection from the peer LS and
do not allow any further connections to this do not allow any further connections to this
skipping to change at line 1032 skipping to change at page 21, line 46
tripPeerConnectRetryInterval OBJECT-TYPE tripPeerConnectRetryInterval OBJECT-TYPE
SYNTAX Unsigned32 (0..2147483647) SYNTAX Unsigned32 (0..2147483647)
UNITS "Seconds" UNITS "Seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the initial amount of time that will elapse "Specifies the initial amount of time that will elapse
between connection retry. This value SHOULD double between connection retry. This value SHOULD double
after each attempt up to the value of after each attempt up to the value of
Zinman/Walker/Jiang 20
tripPeerMaxRetryInterval. This value MUST always be less tripPeerMaxRetryInterval. This value MUST always be less
than or equal to the value of tripPeerMaxRetryInterval. than or equal to the value of tripPeerMaxRetryInterval.
Attempts to set this value higher than the max retry Attempts to set this value higher than the max retry
will not be allowed." will not be allowed."
DEFVAL { 120 } DEFVAL { 120 }
::= { tripPeerEntry 10 } ::= { tripPeerEntry 10 }
tripPeerMaxRetryInterval OBJECT-TYPE tripPeerMaxRetryInterval OBJECT-TYPE
SYNTAX Unsigned32 (0..2147483647) SYNTAX Unsigned32 (0..2147483647)
UNITS "Seconds" UNITS "Seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the maximum amount of time that will elapse "Specifies the maximum amount of time that will elapse
between connection retries. Once the value of between connection retries. Once the value of
tripPeerConnectRetryInterval has reached this value, no tripPeerConnectRetryInterval has reached this value, no
more retries will be attempted. Attempts to set this more retries will be attempted. Attempts to set this
skipping to change at line 1086 skipping to change at page 22, line 49
keep alive messages. This value is negotiated with the keep alive messages. This value is negotiated with the
remote when a connection is established." remote when a connection is established."
::= { tripPeerEntry 13 } ::= { tripPeerEntry 13 }
tripPeerHoldTimeConfigured OBJECT-TYPE tripPeerHoldTimeConfigured OBJECT-TYPE
SYNTAX Unsigned32 (0 | 3..65535) SYNTAX Unsigned32 (0 | 3..65535)
UNITS "Seconds" UNITS "Seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
Zinman/Walker/Jiang 21
"Specifies the maximum time that MAY elapse between the "Specifies the maximum time that MAY elapse between the
receipt of successive keepalive or update message. A value receipt of successive keepalive or update message. A value
of 0 means that keepalive or update messages will not be of 0 means that keepalive or update messages will not be
sent." sent."
DEFVAL { 240 } DEFVAL { 240 }
::= { tripPeerEntry 14 } ::= { tripPeerEntry 14 }
tripPeerKeepAliveConfigured OBJECT-TYPE tripPeerKeepAliveConfigured OBJECT-TYPE
SYNTAX Unsigned32 (1..2147483647) SYNTAX Unsigned32 (1..2147483647)
UNITS "Seconds" UNITS "Seconds"
skipping to change at line 1138 skipping to change at page 24, line 4
tripPeerLearned OBJECT-TYPE tripPeerLearned OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether this entry was learned or "Indicates whether this entry was learned or
configured." configured."
DEFVAL { false } DEFVAL { false }
::= { tripPeerEntry 18 } ::= { tripPeerEntry 18 }
tripPeerStorage OBJECT-TYPE tripPeerStorage OBJECT-TYPE
Zinman/Walker/Jiang 22
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row. Conceptual "The storage type for this conceptual row. Conceptual
rows having the value 'permanent' need not allow write- rows having the value 'permanent' need not allow write-
access to any columnar objects in the row. It is not a access to any columnar objects in the row. It is not a
requirement that this storage be non volatile." requirement that this storage be non volatile."
DEFVAL { nonVolatile } DEFVAL { nonVolatile }
::= { tripPeerEntry 19 } ::= { tripPeerEntry 19 }
skipping to change at line 1194 skipping to change at page 25, line 10
tripPeerStatisticsEntry OBJECT-TYPE tripPeerStatisticsEntry OBJECT-TYPE
SYNTAX TripPeerStatisticsEntry SYNTAX TripPeerStatisticsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Entry containing information about the connection with "Entry containing information about the connection with
a TRIP peer." a TRIP peer."
AUGMENTS { tripPeerEntry } AUGMENTS { tripPeerEntry }
::= { tripPeerStatisticsTable 1 } ::= { tripPeerStatisticsTable 1 }
Zinman/Walker/Jiang 23
TripPeerStatisticsEntry ::= SEQUENCE { TripPeerStatisticsEntry ::= SEQUENCE {
tripPeerInUpdates Counter32, tripPeerInUpdates Counter32,
tripPeerOutUpdates Counter32, tripPeerOutUpdates Counter32,
tripPeerInTotalMessages Counter32, tripPeerInTotalMessages Counter32,
tripPeerOutTotalMessages Counter32, tripPeerOutTotalMessages Counter32,
tripPeerFsmEstablishedTransitions Counter32, tripPeerFsmEstablishedTransitions Counter32,
tripPeerFsmEstablishedTime DateAndTime, tripPeerFsmEstablishedTime DateAndTime,
tripPeerInUpdateElapsedTime TimeInterval, tripPeerInUpdateElapsedTime TimeInterval,
tripPeerStateChangeTime TimeStamp tripPeerStateChangeTime TimeStamp
} }
skipping to change at line 1247 skipping to change at page 26, line 14
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of outgoing TRIP messages sent to the "The total number of outgoing TRIP messages sent to the
remote peer since the last restart of this LS." remote peer since the last restart of this LS."
::= { tripPeerStatisticsEntry 4 } ::= { tripPeerStatisticsEntry 4 }
tripPeerFsmEstablishedTransitions OBJECT-TYPE tripPeerFsmEstablishedTransitions OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
Zinman/Walker/Jiang 24
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of times the remote peer has transitioned "The number of times the remote peer has transitioned
into the established state since the last restart of this into the established state since the last restart of this
LS." LS."
::= { tripPeerStatisticsEntry 5 } ::= { tripPeerStatisticsEntry 5 }
tripPeerFsmEstablishedTime OBJECT-TYPE tripPeerFsmEstablishedTime OBJECT-TYPE
SYNTAX DateAndTime SYNTAX DateAndTime
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at line 1301 skipping to change at page 27, line 19
DESCRIPTION DESCRIPTION
"The TRIP route table containing information about "The TRIP route table containing information about
reachable routes that are to be added to service by the reachable routes that are to be added to service by the
receiving LS. The objects in this table are volatile receiving LS. The objects in this table are volatile
and are refreshed when this LS rediscovers its route and are refreshed when this LS rediscovers its route
table." table."
::= { tripMIBObjects 6 } ::= { tripMIBObjects 6 }
tripRouteEntry OBJECT-TYPE tripRouteEntry OBJECT-TYPE
SYNTAX TripRouteEntry SYNTAX TripRouteEntry
Zinman/Walker/Jiang 25
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about a route to a called destination." "Information about a route to a called destination."
INDEX { applIndex, INDEX { applIndex,
tripRouteAppProtocol, tripRouteAppProtocol,
tripRouteAddressFamily, tripRouteAddressFamily,
tripRouteAddress, tripRouteAddress,
tripRoutePeer tripRoutePeer
} }
skipping to change at line 1356 skipping to change at page 28, line 22
tripRouteAddressFamily OBJECT-TYPE tripRouteAddressFamily OBJECT-TYPE
SYNTAX TripAddressFamily SYNTAX TripAddressFamily
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the type of address for the destination "Specifies the type of address for the destination
route." route."
::= { tripRouteEntry 2 } ::= { tripRouteEntry 2 }
Zinman/Walker/Jiang 26
tripRouteAddress OBJECT-TYPE tripRouteAddress OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(1..105)) SYNTAX OCTET STRING (SIZE(1..105))
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the address (prefix) of the family type given "This is the address (prefix) of the family type given
by Address Family of the destination. It is the prefix by Address Family of the destination. It is the prefix
of addresses reachable from this gateway via the next of addresses reachable from this gateway via the next
hop server. The SIZE value of 105 has been assigned due hop server. The SIZE value of 105 has been assigned due
to the sub identifier of object types length limitation to the sub identifier of object types length limitation
skipping to change at line 1408 skipping to change at page 29, line 25
0 adjTribIns The entry is of type adj-TRIBs-ins, 0 adjTribIns The entry is of type adj-TRIBs-ins,
stores routing information that has stores routing information that has
been learned from inbound UPDATE been learned from inbound UPDATE
messages. messages.
1 extTrib The entry is of type ext-TRIB, the 1 extTrib The entry is of type ext-TRIB, the
best route for a given destination. best route for a given destination.
2 locTrib The entry is of type loc-TRIB contains 2 locTrib The entry is of type loc-TRIB contains
the local TRIP routing information the local TRIP routing information
that the LS has selected. that the LS has selected.
Zinman/Walker/Jiang 27
3 adjTribOut The entry is of type adj-TRIBs-out, 3 adjTribOut The entry is of type adj-TRIBs-out,
stores the information that the local stores the information that the local
LS has selected for advertisement to LS has selected for advertisement to
its external peers." its external peers."
REFERENCE REFERENCE
"RFC 3291, section 3.5." "RFC 3291, section 3.5."
::= { tripRouteEntry 5 } ::= { tripRouteEntry 5 }
tripRouteAddressSequenceNumber OBJECT-TYPE tripRouteAddressSequenceNumber OBJECT-TYPE
SYNTAX Unsigned32 (1..2147483647) SYNTAX Unsigned32 (1..2147483647)
skipping to change at line 1462 skipping to change at page 30, line 29
"Indicates the next hop that messages of a given protocol "Indicates the next hop that messages of a given protocol
destined for tripRouteAddress SHOULD be sent to. The type destined for tripRouteAddress SHOULD be sent to. The type
of this address is determined by the value of the of this address is determined by the value of the
tripRouteNextHopServerIAddrType object." tripRouteNextHopServerIAddrType object."
::= { tripRouteEntry 9 } ::= { tripRouteEntry 9 }
tripRouteNextHopServerPort OBJECT-TYPE tripRouteNextHopServerPort OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
Zinman/Walker/Jiang 28
DESCRIPTION DESCRIPTION
"The port of the next hop server that this route "The port of the next hop server that this route
will use." will use."
::= { tripRouteEntry 10 } ::= { tripRouteEntry 10 }
tripRouteNextHopServerItad OBJECT-TYPE tripRouteNextHopServerItad OBJECT-TYPE
SYNTAX TripItad SYNTAX TripItad
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at line 1516 skipping to change at page 31, line 33
DESCRIPTION DESCRIPTION
"Identifies the sequence of domains through which this "Identifies the sequence of domains through which this
advertisement has passed. advertisement has passed.
This object is probably best represented as sequence of This object is probably best represented as sequence of
TripItads. For SMI compatibility, though, it is TripItads. For SMI compatibility, though, it is
represented as an OCTET STRING. This object is a sequence represented as an OCTET STRING. This object is a sequence
of ITADs where each set of 4 octets corresponds to a TRIP of ITADs where each set of 4 octets corresponds to a TRIP
ITAD in network byte order." ITAD in network byte order."
REFERENCE REFERENCE
Zinman/Walker/Jiang 29
"RFC 3219, section 4.3.4.4" "RFC 3219, section 4.3.4.4"
::= { tripRouteEntry 14 } ::= { tripRouteEntry 14 }
tripRouteRoutedPath OBJECT-TYPE tripRouteRoutedPath OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(4..252)) SYNTAX OCTET STRING (SIZE(4..252))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Identifies the ITADs through which messages sent using "Identifies the ITADs through which messages sent using
this route would pass. These are a subset of this route would pass. These are a subset of
skipping to change at line 1570 skipping to change at page 32, line 37
<attribute type, attribute length, attribute value>, of <attribute type, attribute length, attribute value>, of
variable length. If no attributes were dropped, this variable length. If no attributes were dropped, this
returns an OCTET STRING of size 0." returns an OCTET STRING of size 0."
REFERENCE REFERENCE
"RFC 3219, sections 4.3.1, 4.3.2.3" "RFC 3219, sections 4.3.1, 4.3.2.3"
::= { tripRouteEntry 17 } ::= { tripRouteEntry 17 }
tripRouteWithdrawn OBJECT-TYPE tripRouteWithdrawn OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
Zinman/Walker/Jiang 30
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates if this route is to be removed from service "Indicates if this route is to be removed from service
by the receiving LS." by the receiving LS."
::= { tripRouteEntry 18 } ::= { tripRouteEntry 18 }
tripRouteConverted OBJECT-TYPE tripRouteConverted OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at line 1624 skipping to change at page 33, line 41
tripRouteCommunityEntry OBJECT-TYPE tripRouteCommunityEntry OBJECT-TYPE
SYNTAX TripRouteCommunityEntry SYNTAX TripRouteCommunityEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about communities associated with a route. "Information about communities associated with a route.
An entry with a tripRouteAddress of 00 and a An entry with a tripRouteAddress of 00 and a
tripRoutePeer of 0 refers to the local LS." tripRoutePeer of 0 refers to the local LS."
INDEX { applIndex, INDEX { applIndex,
tripRouteAppProtocol, tripRouteAppProtocol,
Zinman/Walker/Jiang 31
tripRouteAddressFamily, tripRouteAddressFamily,
tripRouteAddress, tripRouteAddress,
tripRoutePeer, tripRoutePeer,
tripRouteCommunityId tripRouteCommunityId
} }
::= { tripRouteCommunityTable 1 } ::= { tripRouteCommunityTable 1 }
TripRouteCommunityEntry ::= SEQUENCE { TripRouteCommunityEntry ::= SEQUENCE {
tripRouteCommunityId TripCommunityId, tripRouteCommunityId TripCommunityId,
tripRouteCommunityItad TripItad tripRouteCommunityItad TripItad
skipping to change at line 1678 skipping to change at page 34, line 44
tripItadTopologyEntry OBJECT-TYPE tripItadTopologyEntry OBJECT-TYPE
SYNTAX TripItadTopologyEntry SYNTAX TripItadTopologyEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about a peer of the LS identified by "Information about a peer of the LS identified by
tripItadTopologyOrigId." tripItadTopologyOrigId."
INDEX { applIndex, tripItadTopologyOrigId } INDEX { applIndex, tripItadTopologyOrigId }
::= { tripItadTopologyTable 1 } ::= { tripItadTopologyTable 1 }
Zinman/Walker/Jiang 32
TripItadTopologyEntry ::= SEQUENCE { TripItadTopologyEntry ::= SEQUENCE {
tripItadTopologyOrigId TripId, tripItadTopologyOrigId TripId,
tripItadTopologySeqNum Unsigned32 tripItadTopologySeqNum Unsigned32
} }
tripItadTopologyOrigId OBJECT-TYPE tripItadTopologyOrigId OBJECT-TYPE
SYNTAX TripId SYNTAX TripId
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at line 1731 skipping to change at page 35, line 48
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about a peer to the LS identified by "Information about a peer to the LS identified by
tripItadTopologyOrigId." tripItadTopologyOrigId."
INDEX { applIndex, INDEX { applIndex,
tripItadTopologyOrigId, tripItadTopologyOrigId,
tripItadTopologyId } tripItadTopologyId }
::= { tripItadTopologyIdTable 1 } ::= { tripItadTopologyIdTable 1 }
Zinman/Walker/Jiang 33
TripItadTopologyIdEntry ::= SEQUENCE { TripItadTopologyIdEntry ::= SEQUENCE {
tripItadTopologyId TripId tripItadTopologyId TripId
} }
tripItadTopologyId OBJECT-TYPE tripItadTopologyId OBJECT-TYPE
SYNTAX TripId SYNTAX TripId
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The index into this entry. Indicates the other location "The index into this entry. Indicates the other location
servers within the ITAD domain that this LS identified servers within the ITAD domain that this LS identified
by tripItadTopologyOrigId is currently peering." by tripItadTopologyOrigId is currently peering."
::= { tripItadTopologyIdEntry 1 } ::= { tripItadTopologyIdEntry 1 }
skipping to change at line 1784 skipping to change at page 37, line 4
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of this entry's TRIP peer LS. This object "The IP address of this entry's TRIP peer LS. This object
contains the value of tripPeerRemoteAddr. The type of this contains the value of tripPeerRemoteAddr. The type of this
address is determined by the value of the address is determined by the value of the
tripNotifPeerAddrInetType object." tripNotifPeerAddrInetType object."
REFERENCE REFERENCE
"RFC 3291, section 3." "RFC 3291, section 3."
::= { tripMIBNotifObjects 3 } ::= { tripMIBNotifObjects 3 }
Zinman/Walker/Jiang 34
tripNotifPeerErrCode OBJECT-TYPE tripNotifPeerErrCode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
messageHeader(1), messageHeader(1),
openMessage(2), openMessage(2),
updateMessage(3), updateMessage(3),
holdTimerExpired(4), holdTimerExpired(4),
finiteStateMachine(5), finiteStateMachine(5),
cease(6), cease(6),
tripNotification(7) tripNotification(7)
} }
skipping to change at line 1837 skipping to change at page 38, line 7
tripNotifPeerErrSubcode OBJECT-TYPE tripNotifPeerErrSubcode OBJECT-TYPE
SYNTAX Unsigned32 (1..2147483647) SYNTAX Unsigned32 (1..2147483647)
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The sub error code associated with error code. The "The sub error code associated with error code. The
meaning of this value is dependent on the value of meaning of this value is dependent on the value of
tripNotifPeerErrCode. tripNotifPeerErrCode.
Zinman/Walker/Jiang 35
Message Header (1) Error Subcodes: Message Header (1) Error Subcodes:
1 - Bad Message Length. 1 - Bad Message Length.
2 - Bad Message Type. 2 - Bad Message Type.
OPEN Message (2) Error Subcodes: OPEN Message (2) Error Subcodes:
1 - Unsupported Version Number. 1 - Unsupported Version Number.
2 - Bad Peer ITAD. 2 - Bad Peer ITAD.
3 - Bad TRIP Identifier. 3 - Bad TRIP Identifier.
4 - Unsupported Optional Parameter. 4 - Unsupported Optional Parameter.
5 - Unacceptable Hold Time. 5 - Unacceptable Hold Time.
skipping to change at line 1890 skipping to change at page 39, line 11
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The TRIP Connection Dropped event is generated when the "The TRIP Connection Dropped event is generated when the
TRIP finite state machine leaves the ESTABLISHED state." TRIP finite state machine leaves the ESTABLISHED state."
::= { tripMIBNotifications 2 } ::= { tripMIBNotifications 2 }
tripFSM NOTIFICATION-TYPE tripFSM NOTIFICATION-TYPE
OBJECTS { tripNotifApplIndex, OBJECTS { tripNotifApplIndex,
tripNotifPeerAddrInetType, tripNotifPeerAddrInetType,
tripNotifPeerAddr, tripNotifPeerAddr,
Zinman/Walker/Jiang 36
tripNotifPeerErrCode, tripNotifPeerErrCode,
tripNotifPeerErrSubcode, tripNotifPeerErrSubcode,
tripPeerState tripPeerState
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The trip FSM Event is generated when any error is "The trip FSM Event is generated when any error is
detected by the TRIP Finite State Machine." detected by the TRIP Finite State Machine."
::= { tripMIBNotifications 3 } ::= { tripMIBNotifications 3 }
skipping to change at line 1944 skipping to change at page 40, line 15
tripPeerState tripPeerState
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The system does not receive successive messages within "The system does not receive successive messages within
the period specified by the negotiated Hold Time." the period specified by the negotiated Hold Time."
::= { tripMIBNotifications 6 } ::= { tripMIBNotifications 6 }
tripConnectionCollision NOTIFICATION-TYPE tripConnectionCollision NOTIFICATION-TYPE
OBJECTS { tripNotifApplIndex } OBJECTS { tripNotifApplIndex }
Zinman/Walker/Jiang 37
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A pair of LSs tried to simultaneously to establish a "A pair of LSs tried to simultaneously to establish a
transport connection to each other." transport connection to each other."
::= { tripMIBNotifications 7 } ::= { tripMIBNotifications 7 }
tripCease NOTIFICATION-TYPE tripCease NOTIFICATION-TYPE
OBJECTS { tripNotifApplIndex, OBJECTS { tripNotifApplIndex,
tripNotifPeerAddrInetType, tripNotifPeerAddrInetType,
tripNotifPeerAddr, tripNotifPeerAddr,
skipping to change at line 1975 skipping to change at page 40, line 44
fatal error occurs." fatal error occurs."
::= { tripMIBNotifications 8 } ::= { tripMIBNotifications 8 }
tripNotificationErr NOTIFICATION-TYPE tripNotificationErr NOTIFICATION-TYPE
OBJECTS { tripNotifApplIndex } OBJECTS { tripNotifApplIndex }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Generated if there is an error detected in a TRIP "Generated if there is an error detected in a TRIP
notification message sent with another cause. Note that notification message sent with another cause. Note that
the TRIP notification refered to in this object is not the TRIP notification referred to in this object is not
an SNMP notification, it is a specific message described an SNMP notification, it is a specific message described
in the TRIP specification." in the TRIP specification."
REFERENCE REFERENCE
"RFC 3219, section 6.4." "RFC 3219, section 6.4."
::= { tripMIBNotifications 9 } ::= { tripMIBNotifications 9 }
-- --
-- Compliance Statements -- Compliance Statements
-- --
tripMIBFullCompliance MODULE-COMPLIANCE tripMIBFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for TRIP entities that "The compliance statement for TRIP entities that
implement this MIB module in read-write mode, such implement this MIB module in read-write mode, such
that it can be used for both monitoring and configuring that it can be used for both monitoring and configuring
the TRIP entity. the TRIP entity.
There is one INDEX object that cannot be represented in There is one INDEX object that cannot be represented in
the form of OBJECT clauses in SMIv2, but for which there the form of OBJECT clauses in SMIv2, but for which there
skipping to change at line 1998 skipping to change at page 41, line 20
"The compliance statement for TRIP entities that "The compliance statement for TRIP entities that
implement this MIB module in read-write mode, such implement this MIB module in read-write mode, such
that it can be used for both monitoring and configuring that it can be used for both monitoring and configuring
the TRIP entity. the TRIP entity.
There is one INDEX object that cannot be represented in There is one INDEX object that cannot be represented in
the form of OBJECT clauses in SMIv2, but for which there the form of OBJECT clauses in SMIv2, but for which there
is a compliance requirement, expressed in OBJECT clause is a compliance requirement, expressed in OBJECT clause
form in this description: form in this description:
Zinman/Walker/Jiang 38
-- OBJECT tripRouteTypeAddrInetType -- OBJECT tripRouteTypeAddrInetType
-- SYNTAX InetAddressType (ipv4(1), ipv6(2), -- SYNTAX InetAddressType (ipv4(1), ipv6(2),
-- ipv4z(3), ipv6z(4)) -- ipv4z(3), ipv6z(4))
-- DESCRIPTION -- DESCRIPTION
-- This MIB requires support for global and -- This MIB requires support for global and
-- non-global ipv4 and ipv6 addresses. -- non-global ipv4 and ipv6 addresses.
-- --
-- OBJECT tripRouteTypeAddr -- OBJECT tripRouteTypeAddr
-- SYNTAX InetAddress (SIZE (4 | 8 | 16 | 20)) -- SYNTAX InetAddress (SIZE (4 | 8 | 16 | 20))
-- DESCRIPTION -- DESCRIPTION
skipping to change at line 2051 skipping to change at page 42, line 24
SYNTAX RowStatus { active(1) } SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION DESCRIPTION
"Support for createAndWait and notInService is not "Support for createAndWait and notInService is not
required." required."
MODULE NETWORK-SERVICES-MIB MODULE NETWORK-SERVICES-MIB
MANDATORY-GROUPS { applRFC2788Group } MANDATORY-GROUPS { applRFC2788Group }
::= { tripMIBCompliances 1 } ::= { tripMIBCompliances 1 }
Zinman/Walker/Jiang 39
tripMIBReadOnlyCompliance MODULE-COMPLIANCE tripMIBReadOnlyCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for TRIP entities that "The compliance statement for TRIP entities that
implement this MIB module in read only mode. Such TRIP implement this MIB module in read only mode. Such TRIP
entities can then only be monitored, but not be entities can then only be monitored, but not be
configured via this MIB module. configured via this MIB module.
In read-only mode, the manager will not be able to add, In read-only mode, the manager will not be able to add,
remove or modify rows to any table, however the TRIP remove or modify rows to any table, however the TRIP
skipping to change at line 2103 skipping to change at page 43, line 26
DESCRIPTION DESCRIPTION
"This group is OPTIONAL. A TRIP entity can choose not to "This group is OPTIONAL. A TRIP entity can choose not to
send any notifications. If this group is implemented, send any notifications. If this group is implemented,
the tripNotifObjectGroup MUST also be implemented." the tripNotifObjectGroup MUST also be implemented."
GROUP tripNotifObjectGroup GROUP tripNotifObjectGroup
DESCRIPTION DESCRIPTION
"This group is OPTIONAL. A TRIP entity can choose not to "This group is OPTIONAL. A TRIP entity can choose not to
send any notifications. If this group is implemented, send any notifications. If this group is implemented,
the tripNotificationGroup MUST also be implemented." the tripNotificationGroup MUST also be implemented."
Zinman/Walker/Jiang 40
OBJECT tripCfgItad OBJECT tripCfgItad
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT tripCfgAdminStatus OBJECT tripCfgAdminStatus
MIN-ACCESS not-accessible MIN-ACCESS not-accessible
DESCRIPTION DESCRIPTION
"Object is not needed when implemented in read-only mode." "Object is not needed when implemented in read-only mode."
skipping to change at line 2156 skipping to change at page 44, line 29
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT tripSupportedCommunityStorage OBJECT tripSupportedCommunityStorage
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT tripSupportedCommunityRowStatus OBJECT tripSupportedCommunityRowStatus
Zinman/Walker/Jiang 41
SYNTAX RowStatus { active(1) } SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required, and active is the only "Write access is not required, and active is the only
status that needs to be supported." status that needs to be supported."
OBJECT tripPeerAdminStatus OBJECT tripPeerAdminStatus
MIN-ACCESS not-accessible MIN-ACCESS not-accessible
DESCRIPTION DESCRIPTION
"Object is not needed when implemented in read-only mode." "Object is not needed when implemented in read-only mode."
skipping to change at line 2210 skipping to change at page 45, line 33
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT tripPeerRowStatus OBJECT tripPeerRowStatus
SYNTAX RowStatus { active(1) } SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required, and active is the only "Write access is not required, and active is the only
status that needs to be supported." status that needs to be supported."
Zinman/Walker/Jiang 42
MODULE NETWORK-SERVICES-MIB MODULE NETWORK-SERVICES-MIB
MANDATORY-GROUPS { applRFC2788Group } MANDATORY-GROUPS { applRFC2788Group }
::= { tripMIBCompliances 2 } ::= { tripMIBCompliances 2 }
-- --
-- Object and event conformance groups -- Object and event conformance groups
-- --
tripConfigGroup OBJECT-GROUP tripConfigGroup OBJECT-GROUP
skipping to change at line 2263 skipping to change at page 46, line 36
tripPeerSendReceiveMode, tripPeerSendReceiveMode,
tripPeerRemoteItad, tripPeerRemoteItad,
tripPeerConnectRetryInterval, tripPeerConnectRetryInterval,
tripPeerMaxRetryInterval, tripPeerMaxRetryInterval,
tripPeerHoldTime, tripPeerHoldTime,
tripPeerKeepAlive, tripPeerKeepAlive,
tripPeerHoldTimeConfigured, tripPeerHoldTimeConfigured,
tripPeerKeepAliveConfigured, tripPeerKeepAliveConfigured,
tripPeerMaxPurgeTime, tripPeerMaxPurgeTime,
tripPeerDisableTime, tripPeerDisableTime,
Zinman/Walker/Jiang 43
tripPeerLearned, tripPeerLearned,
tripPeerStorage, tripPeerStorage,
tripPeerRowStatus tripPeerRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The global objects for configuring the TRIP peer "The global objects for configuring the TRIP peer
table." table."
::= { tripMIBGroups 2 } ::= { tripMIBGroups 2 }
skipping to change at line 2317 skipping to change at page 47, line 40
tripRouteWithdrawn, tripRouteWithdrawn,
tripRouteConverted, tripRouteConverted,
tripRouteReceivedTime, tripRouteReceivedTime,
tripRouteCommunityItad tripRouteCommunityItad
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The global objects for configuring route attribute." "The global objects for configuring route attribute."
::= { tripMIBGroups 4 } ::= { tripMIBGroups 4 }
Zinman/Walker/Jiang 44
tripItadTopologyGroup OBJECT-GROUP tripItadTopologyGroup OBJECT-GROUP
OBJECTS { OBJECTS {
tripItadTopologySeqNum, tripItadTopologySeqNum,
tripItadTopologyId tripItadTopologyId
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The objects that define the TRIP ITAD topology." "The objects that define the TRIP ITAD topology."
::= { tripMIBGroups 5 } ::= { tripMIBGroups 5 }
skipping to change at line 2368 skipping to change at page 48, line 41
::= { tripMIBGroups 7 } ::= { tripMIBGroups 7 }
END END
7. Security Considerations 7. Security Considerations
The managed objects in this MIB module contain sensitive information The managed objects in this MIB module contain sensitive information
since, collectively, they allow tracing and influencing of since, collectively, they allow tracing and influencing of
connections in TRIP devices and provide information of their connections in TRIP devices and provide information of their
connection characteristics. As such, improper manipulation of the connection characteristics. As such, improper manipulation of the
Zinman/Walker/Jiang 45
objects represented by this MIB module MAY result in denial of objects represented by this MIB module MAY result in denial of
service to a large number of availiable routes. service to a large number of available routes.
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
that have a MAX-ACCESS clause of read-write and/or read-create. that have a MAX-ACCESS clause of read-write and/or read-create. Such
Such objects MAY be considered sensitive or vulnerable in some objects MAY be considered sensitive or vulnerable in some network
network environments. The support for SET operations in a non- environments. The support for SET operations in a non-secure
secure environment without proper protection can have a negative environment without proper protection can have a negative effect on
effect on network operations. These objects include: network operations. These objects include:
tripCfgItad: tripCfgItad:
Improper setting of tripCfgItad value can make all peer Improper setting of tripCfgItad value can make all peer
connections drop and not be re-established. connections drop and not be re-established.
tripCfgAdminStatus: tripCfgAdminStatus:
Improper setting of tripCfgAdminStatus from up to down will Improper setting of tripCfgAdminStatus from up to down will cause
cause the TRIP Location Server stop processing TRIP messages. the TRIP Location Server stop processing TRIP messages.
tripCfgPort: tripCfgPort:
Improper setting of tripCfgPort can cause the failure of a peer Improper setting of tripCfgPort can cause the failure of a peer
establishing a connection. establishing a connection.
tripCfgMinItadOriginationInterval, tripCfgMinItadOriginationInterval,
tripCfgMinRouteAdvertisementInterval: tripCfgMinRouteAdvertisementInterval:
Improper configuration of these values MAY adversely affect Improper configuration of these values MAY adversely affect local
local and global convergence of the routes advertised by this and global convergence of the routes advertised by this TRIP
TRIP Location Server. Location Server.
tripPeerAdminStatus: tripPeerAdminStatus:
Improper setting of tripPeerAdminStatus from up to down can Improper setting of tripPeerAdminStatus from up to down can cause
cause significant disruption of the connectivity to the significant disruption of the connectivity to the destination via
destination via the applicable remote TRIP Location Server the applicable remote TRIP Location Server peer.
peer.
tripPeerConnectRetryInterval,tripPeerMaxRetryInterval: tripPeerConnectRetryInterval,tripPeerMaxRetryInterval:
Improper configuration of these values can cause connections to Improper configuration of these values can cause connections to be
be disrupted for extremely long time periods when otherwise disrupted for extremely long time periods when otherwise they
they would be restored in a relatively short period of time. would be restored in a relatively short period of time.
tripPeerHoldTimeConfigured, tripPeerKeepAliveConfigured: tripPeerHoldTimeConfigured, tripPeerKeepAliveConfigured:
Improper configuration of these value can make TRIP peer Improper configuration of these value can make TRIP peer sessions
sessions more fragile and less resilient to denial of service more fragile and less resilient to denial of service attacks.
attacks.
There are a number of managed objects in this MIB module that There are a number of managed objects in this MIB module that contain
contain sensitive information regarding the operation of a network. sensitive information regarding the operation of a network. For
For example, a TRIP Location Server peer's local and remote example, a TRIP Location Server peer's local and remote addresses
addresses might be sensitive for ISPs who want to keep interface might be sensitive for ISPs who want to keep interface addresses on
addresses on TRIP Location Server confidential so as to prevent TRIP TRIP Location Server confidential so as to prevent TRIP Location
Location Server addresses used for a denial of service attack or Server addresses used for a denial of service attack or address
address spoofing. spoofing.
Zinman/Walker/Jiang 46
Therefore, it is thus important to control even GET access to these Therefore, it is thus important to control even GET access to these
objects and possibly to even encrypt the values of these object when objects and possibly to even encrypt the values of these object when
sending them over the network via SNMP. Not all versions of SNMP sending them over the network via SNMP. Not all versions of SNMP
provide features for such a secure environment. provide features for such a secure environment.
SNMPv1 by itself is not a secure environment. Even if the network SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSec), even then, there is itself is secure (for example by using IPSec), even then, there is no
no control as to who on the secure network is allowed to access and 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. GET/SET (read/change/create/delete) the objects in this MIB module.
It is RECOMMENDED that the implementers consider the security It is RECOMMENDED that the implementers consider the security
features as provided by the SNMPv3 framework (see [RFC3410], section features as provided by the SNMPv3 framework (see [RFC3410], section
8), including full support for the SNMPv3 cryptographic mechanisms 8), including full support for the SNMPv3 cryptographic mechanisms
(for authentication and privacy). (for authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
8. Full Copyright Statement 8. References
Copyright (C) The Internet Society (2004). 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 assigns.
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
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Zinman/Walker/Jiang 47
9. Normative References 8.1. Normative References
[RFC3219] Rosenberg, J., Salama, H. and Squire, M., "Telephony [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Routing over IP (TRIP)", RFC 3219 January 2002. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3291] Daniele, M., Haberman, B., Routhier, S., Schoenwaelder, [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual
J., "Textual Conventions for Internet Network Conventions for SMIv2", STD 58, RFC 2579, April 1999.
Addresses", RFC 3291, May 2002.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
Rose, M. and S. Waldbusser, "Structure of Management "Conformance Statements for SMIv2", STD 58, RFC 2580, April
Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999. 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2788] Freed, N. and S. Kille, "Network Services Monitoring MIB",
Rose, M. and S. Waldbusser, "Textual Conventions for RFC 2788, March 2000.
SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999.
[RFC2026] Bradner, S., "The Internet Standards Process _ Revision [RFC3219] Rosenberg, J., Salama, H., and M. Squire, "Telephony
3", BCP 9, RFC 2026, October 1996. Routing over IP (TRIP)", RFC 3219, January 2002.
[RFC2788] Freed, N., Kiley, S., "Network Services Monitoring MIB", [RFC3291] Daniele, M., Haberman, B., Routhier, S., and J.
RFC 2788, March 2000. Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 3291, May 2002.
10. Informative References [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Structure of Management Information Version 2 (SMIv2)",
STD 58, RFC 2578, April 1999.
[RFC1771] Rekhter, Y. and Li, T., "Border Gateway Protocol 4 8.2. Informative References
(BGP-4)", RFC 1771, March 1995.
[RFC1657] Willis, S., Burruss, J., and Chu, J., "Definitions of [RFC1657] Willis, S., Burruss, J., and J. Chu, Ed., "Definitions of
Managed Objects for the Fourth Version of the Border Managed Objects for the Fourth Version of the Border
Gateway Protocol (BGP-4) using SMIv2", RFC 1657, July Gateway Protocol (BGP-4) using SMIv2", RFC 1657, July 1994.
1994.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC1771] Rekhter, Y. and T. Li, "Border Gateway Protocol 4 (BGP-4)",
RFC 1771, March 1995.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 9. Acknowledgments
Requirement Levels", BCP 14, RFC 2119, March 1997.
11. Intellectual Property Notice
Zinman/Walker/Jiang 48
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 implementers 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.
The IETF has been notified of intellectual property rights claimed
in regard to some or all of the specification contained in this
document. For more information consult the online list of claimed
rights.
12. Acknowledgments
The authors wish to thank Bert Wijnen, Dan Romascanu, and Jonathan The authors wish to thank Bert Wijnen, Dan Romascanu, and Jonathan
Rosenberg for their insightful comments and suggestions. Rosenberg for their insightful comments and suggestions.
Thanks to Kevin Lingle for his invaluable comments, help with MIB Thanks to Kevin Lingle for his invaluable comments, help with MIB
things and great ideas. things and great ideas.
13. Author's Addresses 10. Authors' Addresses
David Zinman David Zinman
Editor Editor
265 Ridley Blvd 265 Ridley Blvd
Toronto ON M5M 4N8 Toronto ON M5M 4N8
Canada Canada
phone: +1 416 433 4298
email: dzinman@rogers.com
Dave Walker Phone: +1 416 433 4298
SS8 Networks, Inc. EMail: dzinman@rogers.com
495 March Road, Suite #500
David Walker
Sedna Wireless Inc.
495 March Road, Suite 500
Ottawa, ON K2K 3G1 Ottawa, ON K2K 3G1
Canada Canada
Phone: +1 613 592 2100
Email: drwalker@ss8.com
Zinman/Walker/Jiang 49 Phone: +1 613 878 8142
EMail: david.walker@sedna-wireless.com
Jianping Jiang Jianping Jiang
SGNT Technologies, Inc. Syndesis Limited
5850 Keaton Crescent 30 Fulton Way
Mississauga, ON L5R 3K2 Richmond Hill, ON L4B 1J5
Canada Canada
Phone: +1 905 290 1384
Email: jjiang@sgntt.com
Zinman/Walker/Jiang 50 Phone: +1 905 886-7818 x2515
EMail: jjiang@syndesis.com
11. Full Copyright Statement
Copyright (C) The Internet Society (2004).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/S HE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE
INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights 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; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the IETF's procedures with respect to rights in IETF Documents can
be found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat 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 implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 

This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/