Network Working Group D. Zinman
Request for Comments: 3872 D. Walker
Category: Standards Track J. Jiang
September 2004
Management Information Base
for Telephony Routing over IP (TRIP)
Status of this Memo
このメモの位置付け
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
この文書は、インターネットコミュニティのためのインターネット標準トラックプロトコルを指定し、改善のための議論と提案を要求します。このプロトコルの標準化状態と状態への「インターネット公式プロトコル標準」（STD 1）の最新版を参照してください。このメモの配布は無制限です。
Copyright Notice
著作権表示
Copyright (C) The Internet Society (2004).
著作権（C）インターネット協会（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.
このメモは、インターネットコミュニティでのネットワーク管理プロトコルで使用するための管理情報ベース（MIB）モジュールの一部を定義します。特に、それは、IP（TRIP）デバイス上のテレフォニールーティングを管理するために使用されている管理対象オブジェクトの集合を記述する。
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
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410].
現在のインターネット標準の管理フレームワークを記述したドキュメントの詳細な概要については、RFC 3410 [RFC3410]のセクション7を参照してください。
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].
管理対象オブジェクトが仮想情報店を介してアクセスされ、管理情報ベースまたはMIBと呼ばれます。 MIBモジュールオブジェクトは、一般的に簡易ネットワーク管理プロトコル（SNMP）を介してアクセスされます。このMIBモジュール内のオブジェクトは、管理情報（SMI）の構造で定義されたメカニズムを使用して定義されています。このメモは、STD 58、RFC 2578 [RFC2578]、STD 58、RFC 2579 [RFC2579]に記載されているのSMIv2、およびSTD 58、RFC 2580 [RFC2580]に準拠しているMIBモジュールを指定します。
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].
このメモは、インターネットコミュニティでのネットワーク管理プロトコルで使用するための管理情報ベース（MIB）の一部を定義します。特に、それは定期的に、または指定した日時に管理操作をスケジュールするために使用されている管理対象オブジェクトの集合を記述する。 TRIP [RFC3219]はボーダーゲートウェイプロトコル（BGP-4）[RFC1771]の後にモデル化されているので、TRIPの管理対象オブジェクトは、RFC1657の後にモデル化されている - ボーダーゲートウェイプロトコル（BGP-4）第4バージョンのための管理オブジェクトの定義をSMIv2の[RFC1657]を使用して。
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].
この文書のキーワード "MUST"、 "MUST NOT"、 "REQUIRED"、、、、 "べきではない" "べきである" "ないもの" "ものとし"、 "推奨"、 "MAY"、および "OPTIONAL" はありますBCP 14、RFC 2119 [RFC2119]に記載されているように解釈されます。
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.
このMIBモジュールは、IP [RFC3219]の上に電話ルーティングで定義されたTRIPデバイスのための管理オブジェクトを提供します。 TRIPは、効率的なIPテレフォニールーティングを提供するために、TRIP位置サーバ（LS）との間で情報を交換ドメイン間のアプリケーション層制御プロトコルです。
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.
このMIBモジュールは、単一のエンティティからTRIPの複数のインスタンスを管理するためにRFC 2788 [RFC2788]に記載のフレームワークを利用します。 MIBモジュールapplTableの監視ネットワークサービスは、システム内の各TRIPのロケーションサーバに対応するエントリが取り込まれます。各TRIPロケーションサーバは、それに関連付けられているapplIndexのを持っています。 applIndexのに割り当てられた値は、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:
TRIP MIBモジュールは、特異TRIPエンティティの管理の一環として、各グループオブジェクトの次のグループを含んでいます。各グループは、TRIPの機能の一部を説明します。
o The tripConfigGroup contains the common configuration objects applicable to all TRIP applications referenced by the applIndex.
oをtripConfigGroupはapplIndexのが参照するすべてのTRIPアプリケーションに適用可能な一般的な構成オブジェクトが含まれています。
o The tripPeerTableConfigGroup contains the configuration objects applicable to all TRIP peers of the Location Server referenced by the applIndex.
oをtripPeerTableConfigGroupはapplIndexのが参照するロケーションサーバのすべてTRIPピアに適用可能な構成オブジェクトが含まれています。
o The tripRouteGroup contains the configuration objects related to the routes of all TRIBs of this Location Server.
O tripRouteGroupは、このロケーションサーバのすべてTRIBsのルートに関連する構成オブジェクトが含まれています。
o The tripItadTopologyGroup contains information about the topology of the TRIP ITADs concerning this Location Server.
O tripItadTopologyGroupは、このロケーションサーバに関するTRIPのITADsのトポロジーに関する情報が含まれています。
o The tripPeerTableStatsGroup contains the statistical objects applicable to all TRIP peers of the Location Server referenced by the applIndex.
O tripPeerTableStatsGroupはapplIndexのが参照するロケーションサーバのすべてTRIPピアに適用される統計的なオブジェクトが含まれています。
o The tripNotificationGroup contains notifications that the TRIP application can generate.
O tripNotificationGroupはTRIPアプリケーションが生成することができます通知が含まれています。
o The tripNotifObjectGroup contains the objects needed by one or more of the notifications.
O tripNotifObjectGroupは、通知の一つ以上が必要とするオブジェクトが含まれています。
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.
データ型TripItadとTripIdは、この文書のテキストの表記法として使用されています。 TRIPのITAD（IPテレフォニー管理ドメイン）は、[RFC3219]に記載されています。 TRIP IDは、TRIPロケーション・サーバのための別個の識別子として使用されます。 TripAppProtocolは、アプリケーションプロトコルを識別するために使用されます。 TripAddressFamilyは、アドレスファミリを定義するために使用されます。 TripCommunityIdはTRIPコミュニティのための明確な識別子として使用されます。 TripProtocolVersionは、TRIPプロトコルのバージョン番号を示します。 TripSendReceiveModeはTRIPアプリケーションの動作モードについて説明します。
TRIP-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, Unsigned32, Integer32, mib-2 FROM SNMPv2-SMI -- [RFC2578]
輸入MODULE-IDENTITY、Unsigned32の、Integer32の、MIB-2のSNMPv2-SMI FROM - [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
tripTC MODULE-IDENTITY LAST-UPDATED "200409020000Z" - 2004年9月2日ORGANIZATION "IETF IPTelワーキンググループメーリングリスト：。iptel@lists.bell-labs.com" CONTACT-INFO「共同編集者デイヴィッド・ジンマンは、郵便：265リドリー・ブルバード。トロントON、M5M 4N8カナダEメール：dzinman@rogers.com電話：+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
共同編集者Jianping江Syndesis限定郵便：30フルトン・ウェイリッチモンドヒル、L4B 1J5カナダON
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
電子メール：jjiang@syndesis.com電話：+1 905 886から7818 x2515「DESCRIPTION」TRIP（テレフォニールーティングオーバーIP）MIBテキストの表記法モジュールの初期バージョンで使用される他
TRIP-related MIB Modules.
TRIP関連のMIBモジュール。
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) }
SYNTAX INTEGER {小数（1）、十五進法（2）、E164（3）、その他（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) }
SYNTAX INTEGER {SIP（1）、Q931（2）、RAS（3）、annexG（4）、その他（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
終わり
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]
SNMPv2-CONFからオブジェクト・グループ、MODULE-COMPLIANCE、NOTIFICATION-GROUP - [RFC2580]
InetAddressType, InetAddress, InetPortNumber FROM INET-ADDRESS-MIB -- [RFC3291]
INET-ADDRESS-MIBからのInetAddressType、InetAddressの、InetPortNumber - [RFC3291]
applIndex, applRFC2788Group FROM NETWORK-SERVICES-MIB -- [RFC2788]
applIndexの、NETWORK-SERVICES-MIBからapplRFC2788Group - [RFC2788]
TripItad, TripId, TripAppProtocol, TripAddressFamily, TripCommunityId, TripProtocolVersion, TripSendReceiveMode FROM TRIP-TC-MIB; -- [RFC3872]
TripItad、TripId、TripAppProtocol、TripAddressFamily、TripCommunityId、TripProtocolVersion、TRIP-TC-MIBからTripSendReceiveMode。 - [RFC3872]
tripMIB MODULE-IDENTITY LAST-UPDATED "200409020000Z" -- Sep 02, 2004 ORGANIZATION "IETF IPTel Working Group.
tripMIBのMODULE-IDENTITY LAST-UPDATED "200409020000Z" - 2004年9月2日ORGANIZATION「IETF IPTelワーキンググループ。
Mailing list: iptel@lists.bell-labs.com"
メーリングリスト：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
CONTACT-INFO「共同編集者デイヴィッド・ジンマン郵便：265リドリー・ブルバードトロントON、M5M 4N8カナダEメール：dzinman@rogers.com電話：+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
共同編集者：デビッド・ウォーカーセドナワイヤレス株式会社郵便：495月の道、スイート500オタワ、K2K 3G1カナダの電子メールON：david.walker@sedna-wireless.com電話：+1 613 878 8142
Co-editor Jianping Jiang Syndesis Limited postal: 30 Fulton Way Richmond Hill, ON L4B 1J5 Canada
共同編集者Jianping江Syndesis限定郵便：30フルトン・ウェイリッチモンドヒル、L4B 1J5カナダON
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.
メール：jjiang@syndesis.com電話：+1 905 886から7818 x2515 "DESCRIPTION" IP（TRIP）上テレフォニールーティングを記述するMIBモジュール。 TRIPは、ロケーションサーバ（LS）との間に、電話の目的地の到達可能性を広告するための、およびそれらの目的地へのルートの広告属性の間の管理ドメインプロトコル駆動方針です。
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.
tripCfgAdminStatusのOBJECT-TYPE SYNTAX INTEGER {アップ（1）、ダウン（2）} MAX-ACCESS読み取りと書き込みステータス現在の説明「所望のTRIP状態。
up(1) : Set the application to normal operation.
アップ（1）：通常動作にアプリケーションを設定します。
down(2): Set the application to a state where it will not process TRIP messages.
ダウン（2）：それはTRIPメッセージを処理しません状態にアプリケーションを設定します。
Setting this object should be reflected in tripCfgOperStatus. If an unknown error occurs tripCfgOperStatus will return unknown(0)."
このオブジェクトを設定することはtripCfgOperStatusに反映されるべきです。不明なエラーが発生した場合tripCfgOperStatusは（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.
tripCfgOperStatusのOBJECT-TYPE SYNTAX INTEGER {不明（0）、最大（1）、ダウン（2）、不良（3）} MAX-ACCESS read-only説明「TRIPプロトコルの現在の動作状態。
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.
アップ（1）：アプリケーションが正常に動作し、かつ処理する準備ができている（受信および問題）TRIPの要求と応答。
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).
ダウン（2）：アプリケーションは、現在、TRIPメッセージを処理していません。これは、TRIPアプリケーションは初期化状態にある場合に発生またはtripCfgAdminStatusがダウンに設定されている場合（2）。
faulty(3): The application is not operating normally due to a fault in the system.
故障（3）：アプリケーションは、システムの故障に正常に動作していません。
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
"RFC 3291, section 3."
::= { tripCfgEntry 6 }
tripCfgAddr OBJECT-TYPE SYNTAX InetAddress
tripCfgAddrのOBJECT-TYPE構文InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The network address of the local LS that the peer
connects to. The type of address depends on the object
tripCfgAddrIAddrType. The type of this address is
determined by the value of the
tripCfgAddrIAddrType object."
REFERENCE
"RFC 3291, section 3."
::= { tripCfgEntry 7 }
tripCfgPort OBJECT-TYPE
SYNTAX InetPortNumber
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The local tcp/udp port on the local LS that the peer
connects to."
::= { tripCfgEntry 8 }
tripCfgMinItadOriginationInterval OBJECT-TYPE
SYNTAX Unsigned32 (1..2147483647)
UNITS "Seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The minimum amount of time that MUST elapse between
advertisement of the update message that reports changes
within the LS's own ITAD."
DEFVAL { 30 }
::= { tripCfgEntry 9 }
tripCfgMinRouteAdvertisementInterval OBJECT-TYPE
SYNTAX Unsigned32 (1..2147483647)
UNITS "Seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Specifies minimal interval between successive
advertisements to a particular destination from an LS."
DEFVAL { 30 }
::= { tripCfgEntry 10 }
tripCfgMaxPurgeTime OBJECT-TYPE SYNTAX Unsigned32 (1..2147483647) UNITS "Seconds" MAX-ACCESS read-write
tripCfgMaxPurgeTime OBJECT-TYPEの構文Unsigned32（1 2147483647）UNITS "秒" MAX-ACCESSの読み取りと書き込み
STATUS current
DESCRIPTION
"Indicates the interval that the LS MUST maintain routes
marked as withdrawn in its database."
DEFVAL { 10 }
::= { tripCfgEntry 11 }
tripCfgDisableTime OBJECT-TYPE
SYNTAX Unsigned32 (1..2147483647)
UNITS "Seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates the interval that the TRIP module of the
LS MUST be disabled while routes originated by this
LS with high sequence numbers can be removed."
DEFVAL { 180 }
::= { tripCfgEntry 12 }
tripCfgSendReceiveMode OBJECT-TYPE
SYNTAX TripSendReceiveMode
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The operational mode of the TRIP entity running on this
system."
::= { tripCfgEntry 13 }
tripCfgStorage OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The storage type for this conceptual row. Conceptual rows
having the value 'permanent' need not allow write-access
to any columnar objects in the row."
DEFVAL { nonVolatile }
::= { tripCfgEntry 14 }
-- -- TripRouteTypeTable --
- - TripRouteTypeTable -
tripRouteTypeTable OBJECT-TYPE SYNTAX SEQUENCE OF TripRouteTypeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION
TripRouteTypeEntry MAX-ACCESSステータス現在の説明のtripRouteTypeTable OBJECT-TYPE構文配列
"The TRIP peer Route Type table contains one entry per
supported protocol - address family pair. The objects in
this table are volatile and are refreshed after a reboot."
::= { tripMIBObjects 2 }
tripRouteTypeEntry OBJECT-TYPE SYNTAX TripRouteTypeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry containing information about the route type that a particular TRIP entity supports. Each entry represents information about either the local or a remote LS peer. The object tripRouteTypePeer is used to distinguish this. In the case of a local LS, the address/port information will reflect the values configured in tripCfgTable. In the case of a remote peer, the address/port information will reflect the values of an entry in the tripPeerTable.
tripRouteTypeEntry OBJECT-TYPE構文TripRouteTypeEntry MAX-ACCESSステータス現在の説明「特定のTRIPエンティティがサポートするルートタイプに関する情報が含まれているエントリは、各エントリは、ローカルまたはリモートLSピアのいずれかに関する情報を表す。オブジェクトtripRouteTypePeerが使用されていますこれを区別する。ローカルLSの場合には、アドレス/ポート情報がtripCfgTableに設定された値を反映します。リモートピアの場合には、アドレス/ポート情報がtripPeerTableのエントリの値を反映します。
Implementation need to be aware that if the size of
tripRouteTypeAddr exceeds 111 sub-IDs, then OIDs of column
instances in this table will have more than 128 sub-IDs
and cannot be accessed using SNMPv1, SNMPv2c, or snmpv3."
INDEX { applIndex,
tripRouteTypeAddrInetType,
tripRouteTypeAddr,
tripRouteTypePort,
tripRouteTypeProtocolId,
tripRouteTypeAddrFamilyId }
::= { tripRouteTypeTable 1 }
TripRouteTypeEntry ::= SEQUENCE {
tripRouteTypeAddrInetType InetAddressType,
tripRouteTypeAddr InetAddress,
tripRouteTypePort InetPortNumber,
tripRouteTypeProtocolId TripAppProtocol,
tripRouteTypeAddrFamilyId TripAddressFamily,
tripRouteTypePeer INTEGER
}
tripRouteTypeAddrInetType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS not-accessible STATUS current DESCRIPTION "The type of Inet Address of the tripRouteTypeAddr." REFERENCE
tripRouteTypeAddrInetType OBJECT-TYPE構文InetAddressType MAX-ACCESSステータス現在の説明 "tripRouteTypeAddrのInetのアドレスのタイプ。"参照
"RFC 3291, section 3."
::= { tripRouteTypeEntry 1 }
tripRouteTypeAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The network address of this entry's TRIP peer LS. The
type of this address is determined by the value of the
tripRouteTypeAddrInetType object."
REFERENCE
"RFC 3291, section 3."
::= { tripRouteTypeEntry 2 }
tripRouteTypePort OBJECT-TYPE
SYNTAX InetPortNumber
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The port for the TCP connection between this and
an associated TRIP peer."
::= { tripRouteTypeEntry 3 }
tripRouteTypeProtocolId OBJECT-TYPE
SYNTAX TripAppProtocol
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The object identifier of a protocol that the associated
peer is using."
::= { tripRouteTypeEntry 4 }
tripRouteTypeAddrFamilyId OBJECT-TYPE
SYNTAX TripAddressFamily
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The object identifier of an address family that the
associated peer belongs to."
::= { tripRouteTypeEntry 5 }
tripRouteTypePeer OBJECT-TYPE
SYNTAX INTEGER { local(1), remote(2) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object identifies whether this entry is associated with a 'local' or 'remote' LS peer."
::= { tripRouteTypeEntry 6 }
-- -- tripSupportedCommunityTable --
- - tripSupportedCommunityTable -
tripSupportedCommunityTable OBJECT-TYPE SYNTAX SEQUENCE OF TripSupportedCommunityEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The list of TRIP communities that this LS supports. A TRIP community is a group of destinations that share common properties.
TripSupportedCommunityEntry MAX-ACCESSステータス現在の説明は「これがサポートするLS TRIPコミュニティのリストOF tripSupportedCommunityTable OBJECT-TYPE構文配列。TRIPコミュニティは、共通の性質を共有する宛先のグループです。
The TRIP Supported Communities entry is used to group
destinations so that the routing decision can be based
on the identity of the group."
REFERENCE
"RFC 3219, section 5.9"
::= { tripMIBObjects 3 }
tripSupportedCommunityEntry OBJECT-TYPE
SYNTAX TripSupportedCommunityEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Entry containing information about a community. A TRIP
community is a group of destinations that share some
common property. This attribute is used so that routing
decisions can be based on the identity of the group."
INDEX { applIndex, tripSupportedCommunityId }
::= { tripSupportedCommunityTable 1 }
TripSupportedCommunityEntry ::= SEQUENCE {
tripSupportedCommunityId TripCommunityId,
tripSupportedCommunityItad TripItad,
tripSupportedCommunityStorage StorageType,
tripSupportedCommunityRowStatus RowStatus
}
tripSupportedCommunityId OBJECT-TYPE SYNTAX TripCommunityId MAX-ACCESS not-accessible STATUS current DESCRIPTION "The identifier of the supported Community."
tripSupportedCommunityIdのOBJECT-TYPE SYNTAX TripCommunityId MAX-ACCESSステータス現在の説明「サポートコミュニティの識別子。」
::= { tripSupportedCommunityEntry 1 }
tripSupportedCommunityItad OBJECT-TYPE
SYNTAX TripItad
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The ITAD of the community."
::= { tripSupportedCommunityEntry 2 }
tripSupportedCommunityStorage OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row. Conceptual
rows having the value 'permanent' need not allow write-
access to any columnar objects in the row. It is not a
requirement that this storage be non volatile."
DEFVAL { nonVolatile }
::= { tripSupportedCommunityEntry 3 }
tripSupportedCommunityRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The row status of the entry. This object is REQUIRED to create or delete rows by a manager. A value for tripSupportedCommunityItad MUST be set for row creation to be successful. If the instance already exists for a particular applIndex, the row create operation will fail.
tripSupportedCommunityRowStatusのOBJECT-TYPE構文RowStatus MAX-ACCESSはリード作成ステータス現在の説明「エントリの行ステータスをこのオブジェクトは、管理者によって行を作成または削除する必要がある。tripSupportedCommunityItadの値は、成功するために行作成のために設定しなければなりません。インスタンスが既に特定のapplIndexのために存在している場合、行は、操作が失敗する作ります。
The value of this object has no effect on whether
other objects in this conceptual row can be modified."
::= { tripSupportedCommunityEntry 4 }
--
-- TripPeerTable
--
tripPeerTable OBJECT-TYPE
SYNTAX SEQUENCE OF TripPeerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The TRIP peer table. This table contains one entry per
TRIP peer, and information about the connection with the peer."
::= { tripMIBObjects 4 }
tripPeerEntry OBJECT-TYPE SYNTAX TripPeerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Entry containing information about the connection with a TRIP peer.
TRIPピアとの接続に関する情報を含むtripPeerEntry OBJECT-TYPE構文TripPeerEntry MAX-ACCESSステータス現在の説明「エントリ。
Implementation need to be aware that if the size of
tripPeerRemoteAddr exceeds 113 sub-IDs, then OIDs of
column instances in this table will have more than 128
sub-IDs and cannot be accessed using SNMPv1, SNMPv2c, or
snmpv3."
INDEX { applIndex,
tripPeerRemoteAddrInetType,
tripPeerRemoteAddr,
tripPeerRemotePort }
::= {tripPeerTable 1}
TripPeerEntry ::= SEQUENCE {
tripPeerRemoteAddrInetType InetAddressType,
tripPeerRemoteAddr InetAddress,
tripPeerRemotePort InetPortNumber,
tripPeerIdentifier TripId,
tripPeerState INTEGER,
tripPeerAdminStatus INTEGER,
tripPeerNegotiatedVersion TripProtocolVersion,
tripPeerSendReceiveMode TripSendReceiveMode,
tripPeerRemoteItad TripItad,
tripPeerConnectRetryInterval Unsigned32,
tripPeerMaxRetryInterval Unsigned32,
tripPeerHoldTime Unsigned32,
tripPeerKeepAlive Unsigned32,
tripPeerHoldTimeConfigured Unsigned32,
tripPeerKeepAliveConfigured Unsigned32,
tripPeerMaxPurgeTime Unsigned32,
tripPeerDisableTime Unsigned32,
tripPeerLearned TruthValue,
tripPeerStorage StorageType,
tripPeerRowStatus RowStatus
}
tripPeerRemoteAddrInetType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS not-accessible
tripPeerRemoteAddrInetTypeのOBJECT-TYPE構文InetAddressType MAX-ACCESSアクセス不可能
STATUS current
DESCRIPTION
"The type of Inet Address of the tripPeerRemoteAddr."
REFERENCE
"RFC 3291, section 3."
::= { tripPeerEntry 1 }
tripPeerRemoteAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The IP address of this entry's TRIP peer LS. The type of
this address is determined by the value of the
tripPeerRemoteAddrInetType object."
REFERENCE
"RFC 3291, section 3."
::= { tripPeerEntry 2 }
tripPeerRemotePort OBJECT-TYPE
SYNTAX InetPortNumber
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The remote port for the TCP connection between the
TRIP peers."
::= { tripPeerEntry 3 }
tripPeerIdentifier OBJECT-TYPE
SYNTAX TripId
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"TRIP identifier of the peer."
::= { tripPeerEntry 4 }
tripPeerState OBJECT-TYPE SYNTAX INTEGER { idle(1), connect(2), active(3), openSent(4), openConfirm(5), established(6) } MAX-ACCESS read-only STATUS current DESCRIPTION
tripPeerStateのOBJECT-TYPE SYNTAX INTEGER {アイドル（1）、確立され、（2）、アクティブ（3）、openSent（4）、openConfirm（5）接続（6）} MAX-ACCESS read-only説明
"TRIP Peer Finite State Machine state.
「TRIPピア有限状態機械の状態。
idle(1) : The initial state. Local LS refuses all incoming connections. No application resources are allocated to processing information about the remote peer.
アイドル（1）：初期状態。ローカルLSは、すべての着信接続を拒否します。いいえアプリケーション・リソースがリモートピアに関する情報の処理に割り当てられていません。
connect(2) : Local LS waiting for a transport protocol connection to be completed to the peer, and is listening for inbound transport connections from the peer.
（2）接続：ローカルLSは、トランスポートプロトコル接続がピアに完了するのを待って、ピアからの着信転送接続を待機しています。
active(3) : Local LS is listening for an inbound connection from the peer, but is not in the process of initiating a connection to the remote peer.
アクティブ（3）：ローカルLSは、ピアからの着信接続をリッスンするが、リモートピアへの接続を開始する処理ではありません。
openSent(4) : Local LS has sent an OPEN message to its peer and is waiting for an OPEN message from the remote peer.
openSent（4）：ローカルLSは、そのピアにOPENメッセージを送信し、リモートピアからOPENメッセージを待っています。
openConfirm(5): Local LS has sent an OPEN message to the remote peer, received an OPEN message from the remote peer, and sent a KEEPALIVE message in response to the OPEN. The local LS is now waiting for a KEEPALIVE message or a NOTIFICATION message in response to its OPEN message.
openConfirm（5）：ローカルLSは、リモートピアにOPENメッセージを送信したリモートピアからOPENメッセージを受信し、そしてOPENに応答して、KEEPALIVEメッセージを送信しました。ローカルLSは現在、OPENメッセージに応答してKEEPALIVEメッセージかNOTIFICATIONメッセージを待っています。
established(6): LS can exchange UPDATE, NOTIFICATION, and
KEEPALIVE messages with its peer."
::= { tripPeerEntry 5 }
tripPeerAdminStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "This object is used to affect the TRIP connection state.
tripPeerAdminStatusのOBJECT-TYPE SYNTAX INTEGER {アップ（1）、ダウン（2）} MAX-ACCESSはリード作成ステータス現在の説明は「このオブジェクトは、TRIP接続状態に影響を与えるために使用されます。
up(1) : Allow a connection with the peer LS.
アップ（1）：ピアLSとの接続を許可します。
down(2) : disconnect the connection from the peer LS and do not allow any further connections to this peer.
ダウン（2）：ピアLSからの接続を切断し、このピアへのさらなる接続を許可しません。
If this value is set to down(2) then tripPeerState will
have the value of idle(1)."
DEFVAL { up }
::= { tripPeerEntry 6 }
tripPeerNegotiatedVersion OBJECT-TYPE
SYNTAX TripProtocolVersion
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The negotiated version of TRIP running between this
local entity and this peer."
::= { tripPeerEntry 7 }
tripPeerSendReceiveMode OBJECT-TYPE
SYNTAX TripSendReceiveMode
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The operational mode of this peer."
::= { tripPeerEntry 8 }
tripPeerRemoteItad OBJECT-TYPE
SYNTAX TripItad
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Internet Telephony Administrative domain of
this peer."
::= { tripPeerEntry 9 }
tripPeerConnectRetryInterval OBJECT-TYPE
SYNTAX Unsigned32 (0..2147483647)
UNITS "Seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the initial amount of time that will elapse
between connection retry. This value SHOULD double
after each attempt up to the value of
tripPeerMaxRetryInterval. This value MUST always be less
than or equal to the value of tripPeerMaxRetryInterval.
Attempts to set this value higher than the max retry
will not be allowed."
DEFVAL { 120 }
::= { tripPeerEntry 10 }
tripPeerMaxRetryInterval OBJECT-TYPE
SYNTAX Unsigned32 (0..2147483647)
UNITS "Seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the maximum amount of time that will elapse
between connection retries. Once the value of
tripPeerConnectRetryInterval has reached this value, no
more retries will be attempted. Attempts to set this
value lower than the retry interval SHOULD not be
allowed."
DEFVAL { 360 }
::= { tripPeerEntry 11 }
tripPeerHoldTime OBJECT-TYPE
SYNTAX Unsigned32 (1..2147483647)
UNITS "Seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time interval in seconds for the hold timer that
is established with the peer. The value of this object
is the smaller of the values in
tripPeerHoldTimeConfigured and the hold time received
in the open message."
::= { tripPeerEntry 12 }
tripPeerKeepAlive OBJECT-TYPE
SYNTAX Unsigned32 (1..2147483647)
UNITS "Seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies the amount of time that MUST elapse between
keep alive messages. This value is negotiated with the
remote when a connection is established."
::= { tripPeerEntry 13 }
tripPeerHoldTimeConfigured OBJECT-TYPE
SYNTAX Unsigned32 (0 | 3..65535)
UNITS "Seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the maximum time that MAY elapse between the
receipt of successive keepalive or update message. A value
of 0 means that keepalive or update messages will not be sent."
DEFVAL { 240 }
::= { tripPeerEntry 14 }
tripPeerKeepAliveConfigured OBJECT-TYPE
SYNTAX Unsigned32 (1..2147483647)
UNITS "Seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the amount of time that MUST elapse between
keep alive messages."
DEFVAL { 30 }
::= { tripPeerEntry 15 }
tripPeerMaxPurgeTime OBJECT-TYPE
SYNTAX Unsigned32 (1..65535)
UNITS "Seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates the interval that the LS MUST maintain routes
marked as withdrawn in its database."
DEFVAL { 10 }
::= { tripPeerEntry 16 }
tripPeerDisableTime OBJECT-TYPE
SYNTAX Unsigned32 (1..65535)
UNITS "Seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicate the interval that the TRIP module of the remote
peer LS MUST be disabled while routes originated by the
local LS with high sequence numbers can be removed."
DEFVAL { 180 }
::= { tripPeerEntry 17 }
tripPeerLearned OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates whether this entry was learned or
configured."
DEFVAL { false }
::= { tripPeerEntry 18 }
tripPeerStorage OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row. Conceptual
rows having the value 'permanent' need not allow write-
access to any columnar objects in the row. It is not a
requirement that this storage be non volatile."
DEFVAL { nonVolatile }
::= { tripPeerEntry 19 }
tripPeerRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The row status of the entry. This object is REQUIRED to create or delete rows remotely by a manager. If the instance already exists for a particular applIndex, the row create operation will fail.
tripPeerRowStatus OBJECT-TYPE構文RowStatus MAX-ACCESSはリード作成ステータス現在の説明「エントリの行ステータスをこのオブジェクトは、管理者がリモートで行を作成または削除するために必要とされる。インスタンスが既に特定のapplIndexのために存在している場合、行が作成操作は失敗します。
The value of this object has no effect on whether
other objects in this conceptual row can be modified.
Entries in this table can be learned by the TRIP
application, or provisioned through this table."
::= { tripPeerEntry 20 }
-- -- TripPeerStatisticsTable --
- - ピア統計表について -
tripPeerStatisticsTable OBJECT-TYPE
SYNTAX SEQUENCE OF TripPeerStatisticsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The TRIP peer stats table. This table contains one
entry per remote TRIP peer, and statistics related to the
connection with the remote peer. The objects in this
table are volatile."
::= { tripMIBObjects 5 }
tripPeerStatisticsEntry OBJECT-TYPE SYNTAX TripPeerStatisticsEntry MAX-ACCESS not-accessible STATUS current
tripPeerStatisticsEntryのOBJECT-TYPE SYNTAX TripPeerStatisticsEntry MAX-ACCESSステータス現在の
DESCRIPTION
"Entry containing information about the connection with
a TRIP peer."
AUGMENTS { tripPeerEntry }
::= { tripPeerStatisticsTable 1 }
TripPeerStatisticsEntry ::= SEQUENCE {
tripPeerInUpdates Counter32,
tripPeerOutUpdates Counter32,
tripPeerInTotalMessages Counter32,
tripPeerOutTotalMessages Counter32,
tripPeerFsmEstablishedTransitions Counter32,
tripPeerFsmEstablishedTime DateAndTime,
tripPeerInUpdateElapsedTime TimeInterval,
tripPeerStateChangeTime TimeStamp
}
tripPeerInUpdates OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of TRIP update messages received from this
remote peer since the last restart of this location
server."
::= { tripPeerStatisticsEntry 1 }
tripPeerOutUpdates OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of TRIP update messages sent to this remote
peer since the last restart of this LS."
::= { tripPeerStatisticsEntry 2 }
tripPeerInTotalMessages OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of TRIP messages received from the
remote peer on this connection since the last restart
of this LS."
::= { tripPeerStatisticsEntry 3 }
tripPeerOutTotalMessages OBJECT-TYPE SYNTAX Counter32
tripPeerOutTotalMessagesのOBJECT-TYPE SYNTAXカウンタ
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of outgoing TRIP messages sent to the
remote peer since the last restart of this LS."
::= { tripPeerStatisticsEntry 4 }
tripPeerFsmEstablishedTransitions OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the remote peer has transitioned
into the established state since the last restart of this
LS."
::= { tripPeerStatisticsEntry 5 }
tripPeerFsmEstablishedTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the time and date that this remote peer entered
the 'established' state."
::= { tripPeerStatisticsEntry 6 }
tripPeerInUpdateElapsedTime OBJECT-TYPE
SYNTAX TimeInterval
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Elapsed time in hundredths of seconds since the last
TRIP update message was received from this remote peer."
::= { tripPeerStatisticsEntry 7 }
tripPeerStateChangeTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime when the last state change of
tripPeerState took place."
::= { tripPeerStatisticsEntry 8 }
-- TRIP Received Route Table. This table contains -- all routes from all sources. Each entry consists -- of a route and its associated path attributes.
- TRIPは、ルートテーブルを受信しました。このテーブルには含まれています - すべてのソースからのすべてのルートを。ルートおよびその関連するパス属性 - 各エントリには構成されています。
tripRouteTable OBJECT-TYPE
SYNTAX SEQUENCE OF TripRouteEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The TRIP route table containing information about
reachable routes that are to be added to service by the
receiving LS. The objects in this table are volatile
and are refreshed when this LS rediscovers its route
table."
::= { tripMIBObjects 6 }
tripRouteEntry OBJECT-TYPE
SYNTAX TripRouteEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a route to a called destination."
INDEX { applIndex,
tripRouteAppProtocol,
tripRouteAddressFamily,
tripRouteAddress,
tripRoutePeer
}
::= { tripRouteTable 1 }
TripRouteEntry ::= SEQUENCE {
tripRouteAppProtocol TripAppProtocol,
tripRouteAddressFamily TripAddressFamily,
tripRouteAddress OCTET STRING,
tripRoutePeer TripId,
tripRouteTRIBMask BITS,
tripRouteAddressSequenceNumber Unsigned32,
tripRouteAddressOriginatorId TripId,
tripRouteNextHopServerIAddrType InetAddressType,
tripRouteNextHopServer InetAddress,
tripRouteNextHopServerPort InetPortNumber,
tripRouteNextHopServerItad TripItad,
tripRouteMultiExitDisc Unsigned32,
tripRouteLocalPref Unsigned32,
tripRouteAdvertisementPath OCTET STRING,
tripRouteRoutedPath OCTET STRING,
tripRouteAtomicAggregate TruthValue,
tripRouteUnknown OCTET STRING,
tripRouteWithdrawn TruthValue,
tripRouteConverted TruthValue,
tripRouteReceivedTime TimeStamp
}
tripRouteAppProtocol OBJECT-TYPE
SYNTAX TripAppProtocol
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The protocol for which this entry of the routing table
is maintained."
::= { tripRouteEntry 1 }
tripRouteAddressFamily OBJECT-TYPE
SYNTAX TripAddressFamily
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Specifies the type of address for the destination
route."
::= { tripRouteEntry 2 }
tripRouteAddress OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(1..105))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This is the address (prefix) of the family type given
by Address Family of the destination. It is the prefix
of addresses reachable from this gateway via the next
hop server. The SIZE value of 105 has been assigned due
to the sub identifier of object types length limitation
as defined in SMIv2."
REFERENCE
"RFC 3219, section 5.1.1.1."
::= { tripRouteEntry 3 }
tripRoutePeer OBJECT-TYPE
SYNTAX TripId
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The identifier of the peer where the route information
was learned."
::= { tripRouteEntry 4 }
tripRouteTRIBMask OBJECT-TYPE SYNTAX BITS { adjTribIns(0), extTrib(1), locTrib(2), adjTribOut(3)
tripRouteTRIBMask OBJECT-TYPE構文BITS {adjTribIns（0）、extTrib（1）、locTrib（2）、adjTribOut（3）
} MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates which Telephony Routing Information Base (TRIB) this entry belongs to. This is a bit-map of possible types. If the bit has a value of 1, then the entry is a member of the corresponding TRIB type. If the bit has a value of 0 then the entry is not a member of the TRIP type. The various bit positions are:
} MAX-ACCESS read-only説明は「電話ルーティング情報ベース（TRIB）このエントリが属するが、これは可能なタイプのビットマップであることを示し、ビットの値が1の場合、エントリがメンバーであります。。、対応するサブ・タイプのビットは0の値を有する場合、エントリはTRIP型のメンバーではない、様々なビット位置は次のとおりです。
0 adjTribIns The entry is of type adj-TRIBs-ins,
stores routing information that has
been learned from inbound UPDATE
messages.
1 extTrib The entry is of type ext-TRIB, the
best route for a given destination.
2 locTrib The entry is of type loc-TRIB contains
the local TRIP routing information
that the LS has selected.
3 adjTribOut The entry is of type adj-TRIBs-out,
stores the information that the local
LS has selected for advertisement to
its external peers."
REFERENCE
"RFC 3291, section 3.5."
::= { tripRouteEntry 5 }
tripRouteAddressSequenceNumber OBJECT-TYPE
SYNTAX Unsigned32 (1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the version of the destination route
originated by the LS identified by
tripRouteAddressOriginatorId intra-domain attribute."
::= { tripRouteEntry 6 }
tripRouteAddressOriginatorId OBJECT-TYPE
SYNTAX TripId
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This is an intra-domain attribute indicating the
internal LS that originated the route into the ITAD."
::= { tripRouteEntry 7 }
tripRouteNextHopServerIAddrType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of Inet Address of the tripRouteNextHopServer."
REFERENCE
"RFC 3291, section 3."
::= { tripRouteEntry 8 }
tripRouteNextHopServer OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the next hop that messages of a given protocol
destined for tripRouteAddress SHOULD be sent to. The type
of this address is determined by the value of the
tripRouteNextHopServerIAddrType object."
::= { tripRouteEntry 9 }
tripRouteNextHopServerPort OBJECT-TYPE
SYNTAX InetPortNumber
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The port of the next hop server that this route
will use."
::= { tripRouteEntry 10 }
tripRouteNextHopServerItad OBJECT-TYPE
SYNTAX TripItad
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the domain of the next hop."
::= { tripRouteEntry 11 }
tripRouteMultiExitDisc OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) MAX-ACCESS read-only STATUS current DESCRIPTION "The Multiple Exit Discriminator allows an LS to discriminate between, and indicate preference for, otherwise similar routes to a neighbouring domain. A higher value represents a more preferred routing object."
tripRouteMultiExitDiscのOBJECT-TYPE構文Unsigned32（0 4294967295）MAX-ACCESS read-only説明「複数の出口弁別器は区別するLSを可能とするための好みを示し、隣接するドメインと他の同様の経路。より高い値が表しますより好ましいルーティングオブジェクト。」
REFERENCE
"RFC 3219, section 5.8"
::= { tripRouteEntry 12 }
tripRouteLocalPref OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicated the local LS's degree of preference for an
advertised route destination."
REFERENCE
"RFC 3219, section 4.3.4.7"
::= { tripRouteEntry 13 }
tripRouteAdvertisementPath OBJECT-TYPE SYNTAX OCTET STRING (SIZE(4..252)) MAX-ACCESS read-only STATUS current DESCRIPTION "Identifies the sequence of domains through which this advertisement has passed.
tripRouteAdvertisementPath OBJECT-TYPE構文オクテットSTRING（SIZE（4..252））MAX-ACCESS read-only説明は「この広告が通過した領域のシーケンスを識別する。
This object is probably best represented as sequence of
TripItads. For SMI compatibility, though, it is
represented as an OCTET STRING. This object is a sequence
of ITADs where each set of 4 octets corresponds to a TRIP
ITAD in network byte order."
REFERENCE
"RFC 3219, section 4.3.4.4"
::= { tripRouteEntry 14 }
tripRouteRoutedPath OBJECT-TYPE SYNTAX OCTET STRING (SIZE(4..252)) MAX-ACCESS read-only STATUS current DESCRIPTION "Identifies the ITADs through which messages sent using this route would pass. These are a subset of tripRouteAdvertisementPath.
tripRouteRoutedPathのOBJECT-TYPE構文オクテットSTRING（SIZE（4..252））MAX-ACCESS read-onlyステータス現在の説明は「これらはtripRouteAdvertisementPathのサブセットである。この経路を使用して送信されたメッセージを渡す、それを通してITADsを識別する。
This object is probably best represented as sequence of
TripItads. For SMI compatibility, though, it is
represented as OCTET STRING. This object is a sequence
of ITADs where each set of 4 octets corresponds to a TRIP
ITAD in network byte order."
REFERENCE
"RFC 3219, section 4.3.4.5"
::= { tripRouteEntry 15 }
tripRouteAtomicAggregate OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates that a route MAY traverse domains not listed
in tripRouteRoutedPath. If an LS selects the less
specific route from a set of overlapping routes, then
this value returns TRUE."
REFERENCE
"RFC 3219, section 4.3.4.6"
::= { tripRouteEntry 16 }
tripRouteUnknown OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..255))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains one or more attributes that were not
understood, and because they were transitive, were dropped
during aggregation. They take the format of a triple
<attribute type, attribute length, attribute value>, of
variable length. If no attributes were dropped, this
returns an OCTET STRING of size 0."
REFERENCE
"RFC 3219, sections 4.3.1, 4.3.2.3"
::= { tripRouteEntry 17 }
tripRouteWithdrawn OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates if this route is to be removed from service
by the receiving LS."
::= { tripRouteEntry 18 }
tripRouteConverted OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates if this route has been converted to a
different application protocol than it had originally."
::= { tripRouteEntry 19 }
tripRouteReceivedTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime when this route was received."
::= { tripRouteEntry 20 }
-- -- TRIP Received Route Community Table. --
- - ルートコミュニティ表受信TRIP。 -
tripRouteCommunityTable OBJECT-TYPE
SYNTAX SEQUENCE OF TripRouteCommunityEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing a list of TRIP communities associated
with a route. Each instance of tripRouteTypeEntry that has
the tripRouteTypePeer object set to remote(2) has an
instance in the tripRouteTable as a parent. The objects
in this table are volatile and are refreshed after a
reboot."
REFERENCE
"RFC 3219, section 5.9."
::= { tripMIBObjects 7 }
tripRouteCommunityEntry OBJECT-TYPE
SYNTAX TripRouteCommunityEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about communities associated with a route.
An entry with a tripRouteAddress of 00 and a
tripRoutePeer of 0 refers to the local LS."
INDEX { applIndex,
tripRouteAppProtocol,
tripRouteAddressFamily,
tripRouteAddress,
tripRoutePeer,
tripRouteCommunityId
}
::= { tripRouteCommunityTable 1 }
TripRouteCommunityEntry ::= SEQUENCE {
tripRouteCommunityId TripCommunityId,
tripRouteCommunityItad TripItad
}
tripRouteCommunityId OBJECT-TYPE
SYNTAX TripCommunityId
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The community identifier."
::= { tripRouteCommunityEntry 1 }
tripRouteCommunityItad OBJECT-TYPE
SYNTAX TripItad
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The ITAD associated with this community."
::= { tripRouteCommunityEntry 2 }
-- -- tripItadTopologyTable --
- - tripItadTopologyTable -
tripItadTopologyTable OBJECT-TYPE
SYNTAX SEQUENCE OF TripItadTopologyEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The sequence of link connections between peers within an
ITAD. The objects in this table are volatile and are
refreshed after a reboot."
::= { tripMIBObjects 8 }
tripItadTopologyEntry OBJECT-TYPE
SYNTAX TripItadTopologyEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a peer of the LS identified by
tripItadTopologyOrigId."
INDEX { applIndex, tripItadTopologyOrigId }
::= { tripItadTopologyTable 1 }
TripItadTopologyEntry ::= SEQUENCE {
tripItadTopologyOrigId TripId,
tripItadTopologySeqNum Unsigned32
}
tripItadTopologyOrigId OBJECT-TYPE SYNTAX TripId MAX-ACCESS not-accessible
tripItadTopologyOrigId OBJECT-TYPE SYNTAX TripIdアクセス不可能なMAX-ACCESS
STATUS current
DESCRIPTION
"Indicates the internal LS that originated the ITAD
topology information into the ITAD."
::= { tripItadTopologyEntry 1 }
tripItadTopologySeqNum OBJECT-TYPE
SYNTAX Unsigned32 (1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the version of the ITAD topology originated
by the LS identified by tripItadTopologyOrigId."
::= { tripItadTopologyEntry 2 }
-- -- tripItadTopologyIdTable --
- - tripItadTopologyIdTable -
tripItadTopologyIdTable OBJECT-TYPE
SYNTAX SEQUENCE OF TripItadTopologyIdEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The list of other LS's within the ITAD domain that the
LS identified by tripItadTopologyOrigId is currently
peering. Each instance of tripItadTopologyIdEntry has an
instance in the tripItadTopologyTable as a parent. The
objects in this table are volatile and are refreshed
after a reboot."
::= { tripMIBObjects 9 }
tripItadTopologyIdEntry OBJECT-TYPE
SYNTAX TripItadTopologyIdEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a peer to the LS identified by
tripItadTopologyOrigId."
INDEX { applIndex,
tripItadTopologyOrigId,
tripItadTopologyId }
::= { tripItadTopologyIdTable 1 }
TripItadTopologyIdEntry ::= SEQUENCE {
tripItadTopologyId TripId
}
tripItadTopologyId OBJECT-TYPE
SYNTAX TripId
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The index into this entry. Indicates the other location
servers within the ITAD domain that this LS identified
by tripItadTopologyOrigId is currently peering."
::= { tripItadTopologyIdEntry 1 }
-- -- Notification objects --
- - 通知オブジェクト -
tripNotifApplIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"This object contains the application Index. It is used
to bind this notification with a specific instance of
TRIP entity."
REFERENCE
"RFC 2788, section 3."
::= { tripMIBNotifObjects 1 }
tripNotifPeerAddrInetType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The type of Inet Address of the tripNotifPeerAddr."
REFERENCE
"RFC 3291, section 3."
::= { tripMIBNotifObjects 2 }
tripNotifPeerAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The IP address of this entry's TRIP peer LS. This object
contains the value of tripPeerRemoteAddr. The type of this
address is determined by the value of the
tripNotifPeerAddrInetType object."
REFERENCE
"RFC 3291, section 3."
::= { tripMIBNotifObjects 3 }
tripNotifPeerErrCode OBJECT-TYPE SYNTAX INTEGER { messageHeader(1), openMessage(2), updateMessage(3), holdTimerExpired(4), finiteStateMachine(5), cease(6), tripNotification(7) } MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION "Notification message of TRIP error. The meaning of this value is applicable to the following functions:
tripNotifPeerErrCodeのOBJECT-TYPE SYNTAX INTEGER {messageHeader（1）、openMessage（2）、updateMessage（3）、holdTimerExpired（4）、finiteStateMachine（5）、中止（6）、tripNotification（7）} MAX-ACCESSがアクセス-FOR-通知。ステータス現在の説明は「TRIPエラーの通知メッセージは、この値の意味は以下の機能に適用されます。
messageHeader(1)
- All errors detected while processing the TRIP message
header.
openMessage(2) - All errors detected while processing the OPEN message.
openMessage（2） - OPENメッセージを処理している間に検出されたすべてのエラー。
updateMessage(3) - All errors detected while processing the UPDATE message.
updateMessage（3） - UPDATEメッセージを処理している間に検出されたすべてのエラー。
holdTimerExpired(4) - A notification generated when the hold timer expires.
holdTimerExpired（4） - ホールドタイマが満了したときに生成される通知。
finiteStateMachine(5) - All errors detected by the TRIP Finite State Machine.
finiteStateMachine（5） - TRIP有限状態マシンによって検出されたすべてのエラー。
cease(6) - Any fatal error condition that the rest of the values do not cover.
（6）中止 - 値の残りの部分はカバーしていないという致命的なエラー状態を。
tripNotification(7)
- Any error encountered while sending a notification
message."
::= { tripMIBNotifObjects 4 }
tripNotifPeerErrSubcode OBJECT-TYPE SYNTAX Unsigned32 (1..2147483647) MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION "The sub error code associated with error code. The meaning of this value is dependent on the value of tripNotifPeerErrCode.
tripNotifPeerErrSubcodeのOBJECT-TYPE構文Unsigned32（1 2147483647）MAX-ACCESSアクセス可能のため、通知ステータス現在の説明「エラーコードに関連付けられたサブエラーコード。この値の意味はtripNotifPeerErrCodeの値に依存しています。
Message Header (1) Error Subcodes:
1 - Bad Message Length.
2 - Bad Message Type.
OPEN Message (2) Error Subcodes: 1 - Unsupported Version Number. 2 - Bad Peer ITAD. 3 - Bad TRIP Identifier. 4 - Unsupported Optional Parameter. 5 - Unacceptable Hold Time. 6 - Unsupported Capability. 7 - Capability Mismatch.
OPENメッセージ（2）エラーサブコード：1 - サポートされていないバージョン番号。 2 - バートピアITAD。 3 - バートTRIP識別子。 4 - サポートされていない任意パラメータ。 5 - 許容できないホールド時間。 6 - サポートされていない機能。 7 - 能力の不一致。
UPDATE Message (3) Error Subcodes:
1 - Malformed Attribute List.
2 - Unrecognized Well-known Attribute.
3 - Missing Well-known Mandatory Attribute.
4 - Attribute Flags Error.
5 - Attribute Length Error.
6 - Invalid Attribute."
::= { tripMIBNotifObjects 5 }
--
-- Notifications
--
tripConnectionEstablished NOTIFICATION-TYPE
OBJECTS { tripNotifApplIndex,
tripNotifPeerAddrInetType,
tripNotifPeerAddr
}
STATUS current
DESCRIPTION
"The TRIP Connection Established event is generated when
the TRIP finite state machine enters the ESTABLISHED
state."
::= { tripMIBNotifications 1 }
tripConnectionDropped NOTIFICATION-TYPE OBJECTS { tripNotifApplIndex, tripNotifPeerAddrInetType, tripNotifPeerAddr } STATUS current DESCRIPTION "The TRIP Connection Dropped event is generated when the
tripConnectionDropped NOTIFICATION-TYPEオブジェクト{tripNotifApplIndex、tripNotifPeerAddrInetType、tripNotifPeerAddr}ステータス現在の説明は「TRIP接続ドロップイベントが発生した場合
TRIP finite state machine leaves the ESTABLISHED state."
::= { tripMIBNotifications 2 }
tripFSM NOTIFICATION-TYPE
OBJECTS { tripNotifApplIndex,
tripNotifPeerAddrInetType,
tripNotifPeerAddr,
tripNotifPeerErrCode,
tripNotifPeerErrSubcode,
tripPeerState
}
STATUS current
DESCRIPTION
"The trip FSM Event is generated when any error is
detected by the TRIP Finite State Machine."
::= { tripMIBNotifications 3 }
tripOpenMessageError NOTIFICATION-TYPE
OBJECTS { tripNotifApplIndex,
tripNotifPeerAddrInetType,
tripNotifPeerAddr,
tripNotifPeerErrCode,
tripNotifPeerErrSubcode,
tripPeerState
}
STATUS current
DESCRIPTION
"Errors detected while processing the OPEN message."
::= { tripMIBNotifications 4 }
tripUpdateMessageError NOTIFICATION-TYPE
OBJECTS { tripNotifApplIndex,
tripNotifPeerAddrInetType,
tripNotifPeerAddr,
tripNotifPeerErrCode,
tripNotifPeerErrSubcode,
tripPeerState
}
STATUS current
DESCRIPTION
"Errors detected while processing the UPDATE message."
::= { tripMIBNotifications 5 }
tripHoldTimerExpired NOTIFICATION-TYPE
OBJECTS { tripNotifApplIndex,
tripNotifPeerAddrInetType,
tripNotifPeerAddr,
tripNotifPeerErrCode, tripNotifPeerErrSubcode,
tripPeerState
}
STATUS current
DESCRIPTION
"The system does not receive successive messages within
the period specified by the negotiated Hold Time."
::= { tripMIBNotifications 6 }
tripConnectionCollision NOTIFICATION-TYPE
OBJECTS { tripNotifApplIndex }
STATUS current
DESCRIPTION
"A pair of LSs tried to simultaneously to establish a
transport connection to each other."
::= { tripMIBNotifications 7 }
tripCease NOTIFICATION-TYPE OBJECTS { tripNotifApplIndex, tripNotifPeerAddrInetType, tripNotifPeerAddr, tripNotifPeerErrCode, tripNotifPeerErrSubcode, tripPeerState } STATUS current DESCRIPTION "A TRIP peer MAY choose at any given time to close its TRIP connection by sending this notification message. However, the Cease notification message MUST NOT be used when a fatal error occurs."
tripCease NOTIFICATION-TYPEオブジェクト{tripNotifApplIndex、tripNotifPeerAddrInetType、tripNotifPeerAddr、tripNotifPeerErrCode、tripNotifPeerErrSubcode、tripPeerState}ステータス現在の説明「TRIPピアがこの通知メッセージを送信することによって、そのTRIP接続を閉じるために、任意の時点で選択してもよいが、シーズ通知メッセージではないMUST致命的なエラーが発生したときに使用します。」
::= { tripMIBNotifications 8 }
tripNotificationErr NOTIFICATION-TYPE
OBJECTS { tripNotifApplIndex }
STATUS current
DESCRIPTION
"Generated if there is an error detected in a TRIP
notification message sent with another cause. Note that
the TRIP notification referred to in this object is not
an SNMP notification, it is a specific message described
in the TRIP specification."
REFERENCE
"RFC 3219, section 6.4."
::= { tripMIBNotifications 9 }
--
--
-- Compliance Statements --
- コンプライアンスステートメント -
tripMIBFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for TRIP entities that implement this MIB module in read-write mode, such that it can be used for both monitoring and configuring the TRIP entity.
tripMIBFullCompliance MODULE-COMPLIANCEステータス現在の説明「それは監視とTRIPエンティティの設定の両方に使用することができるように、読み書きモードでこのMIBモジュールを実装TRIPのエンティティのための準拠宣言。
There is one INDEX object that cannot be represented in
the form of OBJECT clauses in SMIv2, but for which there
is a compliance requirement, expressed in OBJECT clause
form in this description:
-- OBJECT tripRouteTypeAddrInetType -- SYNTAX InetAddressType (ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)) -- DESCRIPTION -- This MIB requires support for global and -- non-global ipv4 and ipv6 addresses. -- -- OBJECT tripRouteTypeAddr -- SYNTAX InetAddress (SIZE (4 | 8 | 16 | 20)) -- DESCRIPTION -- This MIB requires support for global and -- non-global IPv4 and IPv6 addresses. -- "
- オブジェクトtripRouteTypeAddrInetType - 構文InetAddressType（IPv4の（1）は、ipv6（2）、 - ipv4z（3）、ipv6z（4）） - 説明 - このMIBは、グローバルとのためのサポートが必要 - 非グローバルなIPv4およびIPv6アドレス。 - - OBJECT tripRouteTypeAddr - 構文InetAddress（SIZE（4 | 8 | 16 | 20）） - DESCRIPTION - 非グローバルIPv4アドレスとIPv6アドレス - このMIBは、グローバルとのサポートを必要とします。 - "
MODULE -- this module MANDATORY-GROUPS { tripConfigGroup, tripPeerTableConfigGroup, tripRouteGroup, tripItadTopologyGroup, tripPeerTableStatsGroup }
MODULE - このモジュールMANDATORY-GROUPS {tripConfigGroup、tripPeerTableConfigGroup、tripRouteGroup、tripItadTopologyGroup、tripPeerTableStatsGroup}
GROUP tripNotificationGroup DESCRIPTION "This group is OPTIONAL. A TRIP entity can choose not to send any notifications. If this group is implemented, the tripNotifObjectGroup MUST also be implemented."
GROUP tripNotificationGroup DESCRIPTION「このグループはオプションです。TRIPエンティティは任意の通知を送信しないように選択することができます。このグループが実装されている場合、tripNotifObjectGroupも実装しなければなりません。」
GROUP tripNotifObjectGroup DESCRIPTION "This group is OPTIONAL. A TRIP entity can choose not to send any notifications. If this group is implemented, the tripNotificationGroup MUST also be implemented."
GROUP tripNotifObjectGroup DESCRIPTION「このグループはオプションです。TRIPエンティティは任意の通知を送信しないように選択することができます。このグループが実装されている場合、tripNotificationGroupも実装しなければなりません。」
OBJECT tripSupportedCommunityRowStatus SYNTAX RowStatus { active(1) } WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } DESCRIPTION "Support for createAndWait and notInService is not required."
OBJECT tripSupportedCommunityRowStatus構文RowStatus {アクティブ（1）} WRITE-構文RowStatus {createAndGo（4）、（6）を破壊}説明は "createAndWaitにおよびnotInServiceのためのサポートが必要とされません。"
OBJECT tripPeerRowStatus SYNTAX RowStatus { active(1) } WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } DESCRIPTION "Support for createAndWait and notInService is not required."
OBJECT tripPeerRowStatus構文RowStatus {アクティブ（1）} WRITE-構文RowStatus {createAndGo（4）、（6）を破壊}説明は "createAndWaitにおよびnotInServiceのためのサポートが必要とされません。"
MODULE NETWORK-SERVICES-MIB MANDATORY-GROUPS { applRFC2788Group }
MODULEのNETWORK-SERVICES-MIB MANDATORY-GROUPS {applRFC2788Group}
::= { tripMIBCompliances 1 }
tripMIBReadOnlyCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for TRIP entities that
implement this MIB module in read only mode. Such TRIP
entities can then only be monitored, but not be
configured via this MIB module.
In read-only mode, the manager will not be able to add,
remove or modify rows to any table, however the TRIP
application may modify, remove or add rows to a table.
There is one INDEX object that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there is a compliance requirement, expressed in OBJECT clause form in this description:
SMIv2のOBJECT節の形で表すことができない1つのインデックスオブジェクトがあるが、そのため、コンプライアンス要件があり、この説明内のオブジェクト句形式で表現しました：
-- OBJECT tripRouteTypeAddrInetType -- SYNTAX InetAddressType (ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)) -- DESCRIPTION -- This MIB requires support for global and -- non-global ipv4 and ipv6 addresses. -- -- OBJECT tripRouteTypeAddr -- SYNTAX InetAddress (SIZE (4 | 8 | 16 | 20)) -- DESCRIPTION -- This MIB requires support for global and
- オブジェクトtripRouteTypeAddrInetType - 構文InetAddressType（IPv4の（1）は、ipv6（2）、 - ipv4z（3）、ipv6z（4）） - 説明 - このMIBは、グローバルとのためのサポートが必要 - 非グローバルなIPv4およびIPv6アドレス。 - - OBJECT tripRouteTypeAddr - 構文InetAddress（SIZE（4 | 8 | 16 | 20）） - 説明 - このMIBはグローバルのサポートを必要とし、
-- non-global IPv4 and IPv6 addresses. -- "
- 非グローバルIPv4アドレスとIPv6アドレス。 - "
MODULE -- this module MANDATORY-GROUPS { tripConfigGroup, tripPeerTableConfigGroup, tripRouteGroup, tripItadTopologyGroup, tripPeerTableStatsGroup }
MODULE - このモジュールMANDATORY-GROUPS {tripConfigGroup、tripPeerTableConfigGroup、tripRouteGroup、tripItadTopologyGroup、tripPeerTableStatsGroup}
GROUP tripNotificationGroup DESCRIPTION "This group is OPTIONAL. A TRIP entity can choose not to send any notifications. If this group is implemented, the tripNotifObjectGroup MUST also be implemented."
GROUP tripNotificationGroup DESCRIPTION「このグループはオプションです。TRIPエンティティは任意の通知を送信しないように選択することができます。このグループが実装されている場合、tripNotifObjectGroupも実装しなければなりません。」
GROUP tripNotifObjectGroup DESCRIPTION "This group is OPTIONAL. A TRIP entity can choose not to send any notifications. If this group is implemented, the tripNotificationGroup MUST also be implemented." OBJECT tripCfgItad MIN-ACCESS read-only DESCRIPTION "Write access is not required."
GROUP tripNotifObjectGroup DESCRIPTION「このグループはオプションです。TRIPエンティティは任意の通知を送信しないように選択することができます。このグループが実装されている場合、tripNotificationGroupも実装しなければなりません。」 OBJECT tripCfgItad MIN-ACCESS読み取り専用説明は "書く、アクセスは必要でありません。"
OBJECT tripCfgAdminStatus MIN-ACCESS not-accessible DESCRIPTION "Object is not needed when implemented in read-only mode."
OBJECT tripCfgAdminStatus MIN-ACCESSアクセス不可能説明「読み取り専用モードで実行する場合、オブジェクトは必要ありません。」
OBJECT tripCfgPort MIN-ACCESS read-only DESCRIPTION "Write access is not required."
OBJECT tripCfgPort MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"
OBJECT tripCfgMinItadOriginationInterval MIN-ACCESS read-only DESCRIPTION "Write access is not required."
OBJECT tripCfgMinItadOriginationInterval MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"
OBJECT tripCfgMinRouteAdvertisementInterval MIN-ACCESS read-only DESCRIPTION "Write access is not required."
OBJECT tripCfgMinRouteAdvertisementInterval MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"
OBJECT tripCfgMaxPurgeTime
OBJECTのtripCfgMaxPurgeTime
MIN-ACCESS read-only DESCRIPTION "Write access is not required."
MIN-ACCESS読み取り専用説明「書き込みアクセスが必要とされていません。」
OBJECT tripCfgDisableTime MIN-ACCESS read-only DESCRIPTION "Write access is not required."
OBJECT tripCfgDisableTime MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"
OBJECT tripCfgStorage MIN-ACCESS read-only DESCRIPTION "Write access is not required."
OBJECT tripCfgStorage MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"
OBJECT tripSupportedCommunityItad MIN-ACCESS read-only DESCRIPTION "Write access is not required."
OBJECT tripSupportedCommunityItad MIN-ACCESS読み取り専用説明は "書く、アクセスは必要でありません。"
OBJECT tripSupportedCommunityStorage MIN-ACCESS read-only DESCRIPTION "Write access is not required."
OBJECT tripSupportedCommunityStorage MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"
OBJECT tripSupportedCommunityRowStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required, and active is the only status that needs to be supported."
OBJECT tripSupportedCommunityRowStatus構文RowStatusがアクティブ{（1）} MIN-ACCESS読み取り専用説明「書き込みアクセス必要となりません、そして活性がサポートされる必要がある唯一の状態です。」
OBJECT tripPeerAdminStatus MIN-ACCESS not-accessible DESCRIPTION "Object is not needed when implemented in read-only mode."
OBJECT tripPeerAdminStatus MIN-ACCESSアクセス不可能説明「読み取り専用モードで実行する場合、オブジェクトは必要ありません。」
OBJECT tripPeerConnectRetryInterval MIN-ACCESS read-only DESCRIPTION "Write access is not required."
OBJECT tripPeerConnectRetryInterval MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"
OBJECT tripPeerMaxRetryInterval MIN-ACCESS read-only DESCRIPTION "Write access is not required."
OBJECT tripPeerMaxRetryInterval MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"
OBJECT tripPeerHoldTimeConfigured MIN-ACCESS read-only
OBJECTは、MIN-ACCESS読み取り専用tripPeerHoldTimeConfigured
DESCRIPTION "Write access is not required."
DESCRIPTION「書き込みアクセスが必要とされていません。」
OBJECT tripPeerKeepAliveConfigured MIN-ACCESS read-only DESCRIPTION "Write access is not required."
OBJECTは、MIN-ACCESS読み取り専用説明は "書く、アクセスは必要でない。" tripPeerKeepAliveConfigured
OBJECT tripPeerMaxPurgeTime MIN-ACCESS read-only DESCRIPTION "Write access is not required."
OBJECT tripPeerMaxPurgeTime MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"
OBJECT tripPeerDisableTime MIN-ACCESS read-only DESCRIPTION "Write access is not required."
OBJECT tripPeerDisableTime MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"
OBJECT tripPeerStorage MIN-ACCESS read-only DESCRIPTION "Write access is not required."
OBJECT tripPeerStorage MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"
OBJECT tripPeerRowStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required, and active is the only status that needs to be supported." MODULE NETWORK-SERVICES-MIB MANDATORY-GROUPS { applRFC2788Group }
OBJECT tripPeerRowStatus構文RowStatusがアクティブ{（1）} MIN-ACCESS読み取り専用説明「書き込みアクセス必要となりません、そして活性がサポートされる必要がある唯一の状態です。」 MODULEのNETWORK-SERVICES-MIB MANDATORY-GROUPS {applRFC2788Group}
::= { tripMIBCompliances 2 }
-- -- Object and event conformance groups --
- - オブジェクトおよびイベント順応グループ -
tripConfigGroup OBJECT-GROUP
OBJECTS {
tripCfgProtocolVersion,
tripCfgItad,
tripCfgIdentifier,
tripCfgOperStatus,
tripCfgAdminStatus,
tripCfgAddrIAddrType,
tripCfgAddr,
tripCfgPort, tripCfgMinItadOriginationInterval,
tripCfgMinRouteAdvertisementInterval,
tripCfgMaxPurgeTime,
tripCfgDisableTime,
tripCfgSendReceiveMode,
tripCfgStorage,
tripSupportedCommunityItad,
tripSupportedCommunityStorage,
tripRouteTypePeer,
tripSupportedCommunityRowStatus
}
STATUS current
DESCRIPTION
"The global objects for configuring trip."
::= { tripMIBGroups 1 }
tripPeerTableConfigGroup OBJECT-GROUP OBJECTS { tripPeerIdentifier, tripPeerState, tripPeerAdminStatus, tripPeerNegotiatedVersion, tripPeerSendReceiveMode, tripPeerRemoteItad, tripPeerConnectRetryInterval, tripPeerMaxRetryInterval, tripPeerHoldTime, tripPeerKeepAlive, tripPeerHoldTimeConfigured, tripPeerKeepAliveConfigured, tripPeerMaxPurgeTime, tripPeerDisableTime, tripPeerLearned, tripPeerStorage, tripPeerRowStatus }
tripPeerTableConfigGroupオブジェクト・グループオブジェクト{tripPeerIdentifier、tripPeerState、tripPeerAdminStatus、tripPeerNegotiatedVersion、tripPeerSendReceiveMode、tripPeerRemoteItad、tripPeerConnectRetryInterval、tripPeerMaxRetryInterval、tripPeerHoldTime、tripPeerKeepAlive、tripPeerHoldTimeConfigured、tripPeerKeepAliveConfigured、tripPeerMaxPurgeTime、tripPeerDisableTime、tripPeerLearned、tripPeerStorage、tripPeerRowStatus}
STATUS current
DESCRIPTION
"The global objects for configuring the TRIP peer
table."
::= { tripMIBGroups 2 }
tripPeerTableStatsGroup OBJECT-GROUP
OBJECTS {
tripPeerInUpdates,
tripPeerOutUpdates,
tripPeerInTotalMessages, tripPeerOutTotalMessages,
tripPeerFsmEstablishedTransitions,
tripPeerFsmEstablishedTime,
tripPeerInUpdateElapsedTime,
tripPeerStateChangeTime
}
STATUS current
DESCRIPTION
"The global statistics the TRIP peer table."
::= { tripMIBGroups 3 }
tripRouteGroup OBJECT-GROUP OBJECTS { tripRouteTRIBMask, tripRouteAddressSequenceNumber, tripRouteAddressOriginatorId, tripRouteNextHopServerIAddrType, tripRouteNextHopServer, tripRouteNextHopServerPort, tripRouteNextHopServerItad, tripRouteMultiExitDisc, tripRouteLocalPref, tripRouteAdvertisementPath, tripRouteRoutedPath, tripRouteAtomicAggregate, tripRouteUnknown, tripRouteWithdrawn, tripRouteConverted, tripRouteReceivedTime, tripRouteCommunityItad }
tripRouteGroupオブジェクト・グループオブジェクト{tripRouteTRIBMask、tripRouteAddressSequenceNumber、tripRouteAddressOriginatorId、tripRouteNextHopServerIAddrType、tripRouteNextHopServer、tripRouteNextHopServerPort、tripRouteNextHopServerItad、tripRouteMultiExitDisc、tripRouteLocalPref、tripRouteAdvertisementPath、tripRouteRoutedPath、tripRouteAtomicAggregate、tripRouteUnknown、tripRouteWithdrawn、tripRouteConverted、tripRouteReceivedTime、tripRouteCommunityItad}
STATUS current
DESCRIPTION
"The global objects for configuring route attribute."
::= { tripMIBGroups 4 }
tripItadTopologyGroup OBJECT-GROUP
OBJECTS {
tripItadTopologySeqNum,
tripItadTopologyId
}
STATUS current
DESCRIPTION
"The objects that define the TRIP ITAD topology."
::= { tripMIBGroups 5 }
tripNotificationGroup NOTIFICATION-GROUP NOTIFICATIONS {
tripNotificationGroup NOTIFICATION-GROUP通知{
tripConnectionEstablished,
tripConnectionDropped,
tripFSM,
tripOpenMessageError,
tripUpdateMessageError,
tripHoldTimerExpired,
tripConnectionCollision,
tripCease,
tripNotificationErr
}
STATUS current
DESCRIPTION
"A collection of notifications defined for TRIP."
::= { tripMIBGroups 6 }
tripNotifObjectGroup OBJECT-GROUP
OBJECTS {
tripNotifApplIndex,
tripNotifPeerAddrInetType,
tripNotifPeerAddr,
tripNotifPeerErrCode,
tripNotifPeerErrSubcode
}
STATUS current
DESCRIPTION
"The collection of objects that specify information for
TRIP notifications."
::= { tripMIBGroups 7 }
END
終わり
The managed objects in this MIB module contain sensitive information since, collectively, they allow tracing and influencing of connections in TRIP devices and provide information of their connection characteristics. As such, improper manipulation of the objects represented by this MIB module MAY result in denial of service to a large number of available routes.
このMIBモジュール内の管理対象オブジェクトをまとめ、彼らはトレースとTRIPデバイス内の接続の影響を与えるとそれらの接続特性の情報を提供して許可するため、機密情報が含まれています。このように、このMIBモジュールによって表されるオブジェクトの不適切な操作は、利用可能なルートの多数のサービスの拒否をもたらすことができます。
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. Such objects MAY be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. These objects include:
読み書きおよび/またはリード作成のMAX-ACCESS節を持っているこのMIBモジュールで定義された管理オブジェクトの数があります。このようなオブジェクトは、いくつかのネットワーク環境で敏感であるか、または脆弱とみなすことができます。適切な保護のない非安全な環境におけるSET操作のサポートはネットワーク操作のときにマイナスの影響を与える可能性があります。これらのオブジェクトは、次のとおりです。
tripCfgItad: Improper setting of tripCfgItad value can make all peer connections drop and not be re-established.
tripCfgItad：tripCfgItad値の不適切な設定が再確立され、すべてのピア接続のドロップを作成し、することはできません。
tripCfgAdminStatus: Improper setting of tripCfgAdminStatus from up to down will cause the TRIP Location Server stop processing TRIP messages.
tripCfgAdminStatus：アップからダウンにtripCfgAdminStatusの不適切な設定がTRIPロケーションサーバの停止処理TRIPメッセージが発生します。
tripCfgPort: Improper setting of tripCfgPort can cause the failure of a peer establishing a connection.
tripCfgPort：tripCfgPortの不適切な設定は、接続を確立するピアの障害を引き起こす可能性があります。
tripCfgMinItadOriginationInterval, tripCfgMinRouteAdvertisementInterval: Improper configuration of these values MAY adversely affect local and global convergence of the routes advertised by this TRIP Location Server.
tripCfgMinItadOriginationInterval、tripCfgMinRouteAdvertisementInterval：これらの値の設定が不適切に悪影響このTRIPロケーションサーバによってアドバタイズされたルートのローカルおよびグローバルな収束に影響を与える可能性があります。
tripPeerAdminStatus: Improper setting of tripPeerAdminStatus from up to down can cause significant disruption of the connectivity to the destination via the applicable remote TRIP Location Server peer.
tripPeerAdminStatus：アップからダウンにtripPeerAdminStatusの不適切な設定が適用されるリモートTRIPロケーションサーバのピアを経由して目的地への接続の大きな混乱を引き起こす可能性があります。
tripPeerConnectRetryInterval,tripPeerMaxRetryInterval: Improper configuration of these values can cause connections to be disrupted for extremely long time periods when otherwise they would be restored in a relatively short period of time.
tripPeerConnectRetryInterval、tripPeerMaxRetryInterval：これらの値の設定が不適切では接続がそうでない場合は、比較的短時間で復元されるだろう、非常に長い期間のために破壊されることがあります。
tripPeerHoldTimeConfigured, tripPeerKeepAliveConfigured: Improper configuration of these value can make TRIP peer sessions more fragile and less resilient to denial of service attacks.
tripPeerHoldTimeConfigured、tripPeerKeepAliveConfigured：これらの値の不適切な構成は、サービス拒否攻撃にTRIPピアセッションは壊れやすいと少ない弾力性にすることができます。
There are a number of managed objects in this MIB module that contain sensitive information regarding the operation of a network. For example, a TRIP Location Server peer's local and remote addresses might be sensitive for ISPs who want to keep interface addresses on TRIP Location Server confidential so as to prevent TRIP Location Server addresses used for a denial of service attack or address spoofing.
ネットワークの運用に関する機密情報を含むこのMIBモジュール内の管理対象オブジェクトの数があります。例えば、TRIPのロケーションサーバのピアのローカルとリモートのアドレスは、サービスの攻撃やアドレススプーフィングの拒否に使用TRIPロケーションサーバのアドレスを防ぐために機密TRIPロケーションサーバ上のインターフェイスアドレスを維持したいのISPに対して敏感であるかもしれません。
Therefore, it is thus important to control even GET access to these objects and possibly to even encrypt the values of these object when sending them over the network via SNMP. Not all versions of SNMP provide features for such a secure environment.
したがって、これらのオブジェクトへのアクセスを取得しても制御し、おそらくSNMPを通してネットワークの上にそれらを送信するときにも、これらのオブジェクトの値を暗号化することが重要です。 SNMPのすべてのバージョンは、このような安全な環境のための機能を提供していません。
SNMPv1 by itself is not a secure environment. Even if the network itself is secure (for example by using IPSec), even then, there is no 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.
それ自体でSNMPv1が安全な環境ではありません。ネットワーク自体が（IPSecを使用することにより、例えば）安全であっても、その後も、安全なネットワーク上で/ SETにアクセスし、GETだれに許容されているかのように何の制御（読み取り/変更/作成/削除）この内のオブジェクトが存在しませんMIBモジュール。
It is RECOMMENDED that the implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy).
実装がSNMPv3フレームワークで提供するようにセキュリティ機能を考えることが推奨される（認証とプライバシーのために）SNMPv3の暗号化メカニズムの完全なサポートを含む、（[RFC3410]セクション8を参照）。
Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them.
さらに、SNMPv3の前のSNMPバージョンの展開はお勧めしません。代わりに、SNMPv3を展開すると、暗号化セキュリティを有効にすることをお勧めします。このMIBモジュールのインスタンスへのアクセスを与えるSNMP実体が適切にのみプリンシパル（ユーザ）にオブジェクトへのアクセスを提供するように設定されていることを確認するために、顧客/オペレータ責任実際にGETまたはSET（変化への正当な権利を有することです/）/削除、それらを作成します。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]ブラドナーの、S.、 "要件レベルを示すためにRFCsにおける使用のためのキーワード"、BCP 14、RFC 2119、1997年3月。
[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579] McCloghrie、K.、パーキンス、D.、およびJ. Schoenwaelder、 "SMIv2のためのテキストの表記法"、STD 58、RFC 2579、1999年4月。
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2580] McCloghrie、K.、パーキンス、D.、およびJ. Schoenwaelder、 "SMIv2のための適合性宣言"、STD 58、RFC 2580、1999年4月。
[RFC2788] Freed, N. and S. Kille, "Network Services Monitoring MIB", RFC 2788, March 2000.
[RFC2788]フリード、N.およびS. Kille、 "ネットワークサービスの監視MIB"、RFC 2788、2000年3月。
[RFC3219] Rosenberg, J., Salama, H., and M. Squire, "Telephony Routing over IP (TRIP)", RFC 3219, January 2002.
"オーバーIPテレフォニールーティング（TRIP）" [RFC3219]ローゼンバーグ、J.、サラマ、H.、およびM.スクワイア、RFC 3219、2002年1月。
[RFC3291] Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder, "Textual Conventions for Internet Network Addresses", RFC 3291, May 2002.
[RFC3291]ダニエル、M.、ハーバーマン、B.、Routhier、S.、およびJ. Schoenwaelder、 "インターネットネットワークアドレスのためのテキストの表記法"、RFC 3291、2002年5月。
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2578] McCloghrie、K.、パーキンス、D.、およびJ. Schoenwaelder、STD 58、RFC 2578、1999年4月 "管理情報バージョン2（SMIv2）の構造"。
[RFC1657] Willis, S., Burruss, J., and J. Chu, Ed., "Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2", RFC 1657, July 1994.
[RFC1657]ウィリス、S.、Burruss、J.、およびJ.チュー、編、RFC 1657、1994年7月 "SMIv2のを使用してボーダーゲートウェイプロトコル（BGP-4）第4版のための管理オブジェクトの定義"。
[RFC1771] Rekhter, Y. and T. Li, "Border Gateway Protocol 4 (BGP-4)", RFC 1771, March 1995.
[RFC1771] Rekhter、Y.とT.李、 "ボーダーゲートウェイプロトコル4（BGP-4）"、RFC 1771、1995年3月。
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002.
[RFC3410]ケース、J.、マンディ、R.、パーテイン、D.、およびB.スチュワート、 "インターネット標準の管理フレームワークのための序論と適用性声明"、RFC 3410、2002年12月。
The authors wish to thank Bert Wijnen, Dan Romascanu, and Jonathan Rosenberg for their insightful comments and suggestions.
作者は彼らの洞察に満ちたコメントと提案のためにバートWijnen、ダンRomascanu、およびジョナサンローゼンバーグに感謝したいです。
Thanks to Kevin Lingle for his invaluable comments, help with MIB things and great ideas.
彼の貴重なコメントのケビンLingleのおかげで、MIBのものと素晴らしいアイデアを助けます。
David Zinman Editor 265 Ridley Blvd Toronto ON M5M 4N8 Canada
デイヴィッド・ジンマンエディタ265リドリー・ブルバードトロントON M5M 4N8カナダ
Phone: +1 416 433 4298 EMail: dzinman@rogers.com
電話：+1 416 433 4298 Eメール：dzinman@rogers.com
David Walker Sedna Wireless Inc. 495 March Road, Suite 500 Ottawa, ON K2K 3G1 Canada
デビッド・ウォーカーセドナワイヤレス株式会社K2K 3G1カナダON 495マーチ道路、スイート500オタワ、
Phone: +1 613 878 8142 EMail: david.walker@sedna-wireless.com
電話：+1 613 878 8142 Eメール：david.walker@sedna-wireless.com
Jianping Jiang Syndesis Limited 30 Fulton Way Richmond Hill, ON L4B 1J5 Canada
L4B 1J5カナダON Jianping江Syndesis限定30フルトン・ウェイリッチモンドヒル、
Phone: +1 905 886-7818 x2515 EMail: jjiang@syndesis.com
電話：+1 905 886-7818 x2515メール：jjiang@syndesis.com
Copyright (C) The Internet Society (2004).
著作権（C）インターネット協会（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.
この文書では、BCP 78に含まれる権利と許可と制限の適用を受けており、その中の記載を除いて、作者は彼らのすべての権利を保有します。
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.
この文書とここに含まれている情報は、基礎とHEが表すCONTRIBUTOR、ORGANIZATION HE / S OR（もしあれば）後援されており、インターネットソサエティおよびインターネット・エンジニアリング・タスク・フォース放棄すべての保証、明示、「そのまま」で提供されていますOR情報の利用は、特定の目的に対する権利または商品性または適合性の黙示の保証を侵害しない任意の保証を含むがこれらに限定されないで、黙示。
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.
IETFは、本書またはそのような権限下で、ライセンスがたりないかもしれない程度に記載された技術の実装や使用に関係すると主張される可能性があります任意の知的財産権やその他の権利の有効性または範囲に関していかなる位置を取りません利用可能です。またそれは、それがどのような権利を確認する独自の取り組みを行ったことを示すものでもありません。 IETF文書の権利に関するIETFの手続きの情報は、BCP 78および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.
IPRの開示のコピーが利用できるようにIETF事務局とライセンスの保証に行われた、または本仕様の実装者または利用者がそのような所有権の使用のための一般的なライセンスまたは許可を取得するために作られた試みの結果を得ることができますhttp://www.ietf.org/iprのIETFのオンライン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.
IETFは、その注意にこの標準を実装するために必要とされる技術をカバーすることができる任意の著作権、特許または特許出願、またはその他の所有権を持ってすべての利害関係者を招待します。 ietf-ipr@ietf.orgのIETFに情報を記述してください。
Acknowledgement
謝辞
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC Editor機能のための基金は現在、インターネット協会によって提供されます。