[要約] RFC 3872は、Telephony Routing over IP（TRIP）のための管理情報ベース（MIB）に関する規格です。このRFCの目的は、TRIPプロトコルの実装と管理を支援するためのMIBオブジェクトを定義することです。
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)
IPを介したテレフォニールーティングの管理情報ベース（旅行）
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）The Internet Society（2004）。
Abstract
概要
This memo defines a portion of the Management Information Base (MIB) module for use with network management protocols in the Internet community. In particular, it describes a set of managed objects that are used to manage Telephony Routing over IP (TRIP) devices.
このメモは、インターネットコミュニティのネットワーク管理プロトコルで使用する管理情報ベース（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]、およびSTD 58、RFC 2580 [RFC2580]に記載されているSMIV2に準拠した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）の一部を定義します。特に、定期的にまたは指定された日時で管理操作をスケジュールするために使用される管理されたオブジェクトのセットについて説明します。トリップ[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].
「必須」、「そうしない」、「必須」、「必要」、「「しない」、「そうでない」、「そうではない」、「そうでない」、「推奨」、「5月」、および「オプション」は、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は、効率的なIPテレフォニールーティングを提供するために、トリップロケーションサーバー（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モジュールは、単一のエンティティからの旅行の複数のインスタンスの管理のために、RFC 2788 [RFC2788]で説明されているフレームワークを利用しています。MIBモジュールのAppltableを監視するネットワークサービスには、システム内の各Trip Location Serverに対応するエントリが入力されます。各Trip Location Serverには、Applindexが関連付けられます。Applindexに割り当てられた値は、旅行の明確なインスタンスを表します。
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モジュールには、特異なトリップエンティティの管理の一部として、各グループを持つオブジェクトの以下のグループが含まれています。各グループは、旅行の機能のセクションをカバーしています。
o The tripConfigGroup contains the common configuration objects applicable to all TRIP applications referenced by the applIndex.
o TRIPCONFIGGROUPには、ApplIndexが参照するすべてのトリップアプリケーションに適用される共通の構成オブジェクトが含まれています。
o The tripPeerTableConfigGroup contains the configuration objects applicable to all TRIP peers of the Location Server referenced by the applIndex.
o trippeertableconfiggroupには、Applindexが参照されているロケーションサーバーのすべてのトリップピアに適用される構成オブジェクトが含まれています。
o The tripRouteGroup contains the configuration objects related to the routes of all TRIBs of this Location Server.
o TripRoutegroupには、このロケーションサーバーのすべての部族のルートに関連する構成オブジェクトが含まれています。
o The tripItadTopologyGroup contains information about the topology of the TRIP ITADs concerning this Location Server.
o TripITADTOPOLOGYGROUPには、このロケーションサーバーに関するトリップITADSのトポロジに関する情報が含まれています。
o The tripPeerTableStatsGroup contains the statistical objects applicable to all TRIP peers of the Location Server referenced by the applIndex.
o Trippeertablestatsgroupには、Applindexが参照されているロケーションサーバーのすべてのトリップピアに適用される統計オブジェクトが含まれています。
o The tripNotificationGroup contains notifications that the TRIP application can generate.
o TripNotificationGroupには、旅行アプリケーションが生成できる通知が含まれています。
o The tripNotifObjectGroup contains the objects needed by one or more of the notifications.
o TripNotifObjectGroupには、1つ以上の通知が必要とするオブジェクトが含まれています。
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]に記載されています。旅行IDは、旅行ロケーションサーバーの明確な識別子として使用されます。TripAppprotocolは、アプリケーションプロトコルを識別するために使用されます。トリップドレスファミリーは、住所ファミリを定義するために使用されます。TripCommunityIDは、旅行コミュニティの明確な識別子として使用されます。Tripprotocolversionは、旅行プロトコルのバージョン番号を示しています。TRIPSENDRECEIVEMODEは、旅行アプリケーションの運用モードについて説明します。
TRIP-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, Unsigned32, Integer32, mib-2 FROM SNMPv2-SMI -- [RFC2578]
Intorts Module-Identity、unsigned32、Integer32、MIB-2からSNMPV2-SMI - [RFC2578]
TEXTUAL-CONVENTION FROM SNMPv2-TC; -- [RFC2579]
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モジュールのアイデンティティ最終処分「200409020000Z」 - 2004年9月2日組織 "IETF IPTELワーキンググループ。メーリングリスト。メーリングリスト：iptel@lists.bell-labs.com。トロントオン、M5M 4N8カナダメール：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
共同編集者：David Walker Sedna Wireless Inc. Postal：495 March Road、Suite 500 Ottawa、On K2K 3G1 Canada Email：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 Jiang Syndesis Limited Postal：30 Fulton Way Richmond Hill、L4B 1J5 Canada
email: jjiang@syndesis.com phone: +1 905 886-7818 x2515 " DESCRIPTION "Initial version of TRIP (Telephony Routing Over IP) MIB Textual Conventions module used by other TRIP-related MIB Modules.
電子メール：jjiang@syndesis.com電話：1 905 886-7818 x2515 "説明"他のトリップ関連MIBモジュールで使用されるTrip（IP上のテレフォニールーティング）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) }
TripAppProtocol ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The application protocol used for communication with TRIP
Location Servers. Protocols defined in this MIB Module
are:
Code Protocol
1 SIP
2 H.323-H.225.0-Q.931
3 H.323-H.225.0-RAS
4 H.323-H.225.0-Annex-G
255 An other type of application protocol"
SYNTAX INTEGER
{ sip(1), q931(2), ras(3), annexG(4), other(255) }
TripCommunityId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The range of legal values for a TRIP Community
Identifier."
SYNTAX Unsigned32 (0..4294967295)
TripProtocolVersion ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The version number of the TRIP protocol."
SYNTAX Integer32 (1..255)
TripSendReceiveMode ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The operational mode of the TRIP application. Possible
values are:
1 - Send Receive mode
2 - Send only mode
3 - Receive Only mode"
SYNTAX INTEGER { sendReceive(1), sendOnly(2), receiveOnly(3) }
END6.2. TRIP MIB
終了6.2。トリップミブ
TRIP-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Unsigned32, Integer32, Counter32, mib-2 FROM SNMPv2-SMI -- [RFC2578]
インポートモジュールアイデンティティ、オブジェクトタイプ、通知タイプ、unsigned32、integer32、counter32、mib-2 from snmpv2-smi- [rfc2578]
DateAndTime, TimeInterval, TruthValue, TimeStamp, StorageType, RowStatus FROM SNMPv2-TC -- [RFC2579]
dateandtime、timeinterval、truthvalue、timestamp、storageType、rowstatus from Snmpv2-tc- [RFC2579]
OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP FROM SNMPv2-CONF -- [RFC2580]
snmpv2-confからのオブジェクトグループ、モジュールコンプライアンス、通知グループ - [rfc2580]
InetAddressType, InetAddress, InetPortNumber FROM INET-ADDRESS-MIB -- [RFC3291]
inetAddressType、inetAddress、inetportnumber from inet-address-mib- [rfc3291]
applIndex, applRFC2788Group FROM NETWORK-SERVICES-MIB -- [RFC2788]
Applindex、Applrfc2788Group from Network-Services-Mib- [RFC2788]
TripItad, TripId, TripAppProtocol, TripAddressFamily, TripCommunityId, TripProtocolVersion, TripSendReceiveMode FROM TRIP-TC-MIB; -- [RFC3872]
Tripitad、Tripid、TripAppprotocol、Tripaddressfamily、TripCommunityId、Tripprotocolversion、TripsEndReceiveMode from TripTC-Mib; - [RFC3872]
tripMIB MODULE-IDENTITY LAST-UPDATED "200409020000Z" -- Sep 02, 2004 ORGANIZATION "IETF IPTel Working Group.
TRIPMIBモジュールのアイデンティティ最後のアップデート「200409020000Z」 - 2004年9月2日組織 "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 "共同編集者David Zinman Postal：265 Ridley Blvd. Toronto on、M5m 4n8カナダメール：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
共同編集者：David Walker Sedna Wireless Inc. Postal：495 March Road、Suite 500 Ottawa、On K2K 3G1 Canada Email：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 Jiang Syndesis Limited Postal：30 Fulton Way Richmond Hill、L4B 1J5 Canada
email: jjiang@syndesis.com phone: +1 905 886-7818 x2515 " DESCRIPTION "The MIB module describing Telephony Routing over IP (TRIP). TRIP is a policy driven inter-administrative domain protocol for advertising the reachability of telephony destinations between location servers (LS), and for advertising attributes of the routes to those destinations.
電子メール：jjiang@syndesis.com電話：1 905 886-7818 x2515 "説明" IP（TRIP）を介したテレフォニールーティングを説明するMIBモジュール。旅行は、ロケーションサーバー（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.
up(1) : Set the application to normal operation.
up（1）：アプリケーションを通常の操作に設定します。
down(2): Set the application to a state where it will not process TRIP messages.
ダウン（2）：トリップメッセージを処理しない状態にアプリケーションを設定します。
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.
unknown(0): The operating status of the application is unknown.
不明（0）：アプリケーションの動作ステータスは不明です。
up(1): The application is operating normally, and is ready to process (receive and issue) TRIP requests and responses.
UP（1）：アプリケーションは正常に動作しており、旅行のリクエストと回答を処理（受信および発行）する準備ができています。
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）：アプリケーションは現在、トリップメッセージを処理していません。これは、トリップアプリケーションが初期化状態にある場合、またはTRIPCFGADMINTATUSが下に設定されている場合に発生します（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
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
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 OBJECT-TYPE SYNTAX SEQUENCE OF TripRouteTypeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION
TriprouteTypeTableオブジェクトタイプの構文シーケンストリプルタータイプエントリーMax-Accessアクセス不可能なステータス現在の説明
"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オブジェクトタイプ構文TriprouteTypeEntry Max-Accessアクセス不可能なステータス現在これを区別するために。ローカル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オブジェクトタイプ構文inetAddressType max-accessアクセス不可能なステータス現在の説明参照
"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 --
--- TripSuptedCommunityTable-
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.
TripSuptuptedCommunityTableオブジェクトタイプの構文シーケンスTripSupportedCommunityEntry Max-Accessはアクセス不可能なステータス現在の説明 "このLSがサポートする旅行コミュニティのリスト。旅行コミュニティは、普通の特性を共有する目的地のグループです。
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."
TripSuptedCommunityID 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オブジェクトタイプの構文rowStatus max-access read-createステータス現在の説明 "エントリの行のステータス。このオブジェクトは、マネージャーによる行を作成または削除するために必要です。特定の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.
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
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
"TRIP Peer Finite State Machine state.
「ピア有限のステートマシン状態をトリップします。
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.
Connect（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.
Active（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はピアに開かれたメッセージを送信し、リモートピアからの開かれたメッセージを待っています。
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は、リモートピアにオープンメッセージを送信し、リモートピアから開いたメッセージを受け取り、オープンに応じてキープライブメッセージを送信しました。ローカルLSは、オープンメッセージに応じて、Keepaliveメッセージまたは通知メッセージを待っています。
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.
up(1) : Allow a connection with the peer LS.
UP（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 syntax rowstatus max-access read-createステータス現在操作は失敗します。
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-
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
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
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.
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オブジェクトタイプ構文ビット{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読み取り専用ステータス現在の説明 "このエントリが属するテレフォニールーティング情報ベース（trib）を示します。これは可能なタイプのビットマップです。ビットの値が1の場合、エントリはメンバーです。対応する部族の種類のうち。ビットの値が0の場合、エントリは旅行タイプのメンバーではありません。さまざまなビット位置は次のとおりです。
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-type syntax untigned32（0..4294967295）max-access read-only status current current current current discrentature "複数の出口識別子は、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.
TriprouteadeadvertisementPathオブジェクトタイプの構文octet String（size（4..252））max-access読み取り専用ステータス現在の説明 "この広告が通過したドメインのシーケンスを識別します。
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オブジェクトタイプの構文オクタックスストリング（サイズ（4..252））最大アクセス読み取り専用ステータス現在の説明 "このルートを使用して送信されたメッセージが通過するITADを識別します。
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"
このオブジェクトは、おそらくTripitadsのシーケンスとして最もよく表されます。ただし、SMIの互換性については、Octet Stringとして表されます。このオブジェクトは、4オクテットの各セットがネットワークバイトの順序でトリップITADに対応するITADのシーケンスです。 "参照" RFC 3219、セクション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. --
---旅行はルートコミュニティテーブルを受け取りました。 -
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
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:
messageHeader(1) - All errors detected while processing the TRIP message header.
MessageHeader（1） - トリップメッセージヘッダーの処理中にすべてのエラーが検出されました。
openMessage(2) - All errors detected while processing the OPEN message.
OpenMessage（2） - 開いたメッセージの処理中にすべてのエラーが検出されました。
updateMessage(3) - All errors detected while processing the UPDATE message.
UpdateMessage（3） - 更新メッセージの処理中にすべてのエラーが検出されました。
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） - トリップ有限状態マシンによって検出されたすべてのエラー。
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 syntax untigned32（1..2147483647）max-accessアクセス可能なステータス現在の説明 "エラーコードに関連付けられたサブエラーコード。この値の意味は、tripnotifpeerercodeの値に依存します。
Message Header (1) Error Subcodes: 1 - Bad Message Length. 2 - Bad Message Type.
メッセージヘッダー（1）エラーサブコード：1-悪いメッセージの長さ。2-悪いメッセージタイプ。
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.
メッセージ（2）エラーサブコード：1-サポートされていないバージョン番号。2-悪いピアitad。3-悪い旅行識別子。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
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 Objects {tripnotifapplindex、tripnotifpeeraddrinettype、tripnotifpeeraddr、tripnotifpeererrsubcode、tripnotifpeererrsubcode、trippeererstate}ステータス現在の説明 "Trip Peerは、Trip Connectionを閉じるために、Trip Connessification notificationメッセージを送信するために、このような通知を送信するために致命的なエラーが発生したときに使用します。」
::= { 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モジュールコンプライアンスステータス現在の説明 "このMIBモジュールを読み取りワイトモードで実装するトリップエンティティのコンプライアンスステートメント。これにより、トリップエンティティの監視と構成の両方に使用できます。
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のオブジェクト条項の形で表現できないインデックスオブジェクトは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
-- non-global IPv4 and IPv6 addresses.
--
"
MODULE -- this module MANDATORY-GROUPS { tripConfigGroup, tripPeerTableConfigGroup, tripRouteGroup, tripItadTopologyGroup, tripPeerTableStatsGroup }
モジュール - このモジュールの必須グループ{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."
グループTripNotificationGroupの説明「このグループはオプションです。トリップエンティティは通知を送信しないように選択できます。このグループが実装されている場合、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."
グループtripnotifobjectgroupの説明「このグループはオプションです。トリップエンティティは通知を送信しないことを選択できます。このグループが実装されている場合、TripNotificationGroupも実装する必要があります。」
OBJECT tripSupportedCommunityRowStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not
required."
OBJECT tripPeerRowStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not
required."
MODULE NETWORK-SERVICES-MIB MANDATORY-GROUPS { applRFC2788Group }
モジュールNetwork-Services-Mib Anctoration-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のオブジェクト条項の形で表現できないインデックスオブジェクトは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
-- non-global IPv4 and IPv6 addresses. -- "
- 非グロバルIPv4およびIPv6アドレス。 - 」
MODULE -- this module MANDATORY-GROUPS { tripConfigGroup, tripPeerTableConfigGroup, tripRouteGroup, tripItadTopologyGroup, tripPeerTableStatsGroup }
モジュール - このモジュールの必須グループ{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."
グループTripNotificationGroupの説明「このグループはオプションです。トリップエンティティは通知を送信しないように選択できます。このグループが実装されている場合、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."
グループtripnotifobjectgroupの説明「このグループはオプションです。トリップエンティティは通知を送信しないことを選択できます。このグループが実装されている場合、TripNotificationGroupも実装する必要があります。」オブジェクトTRIPCFGITAD MIN-ACCESS読み取り専用説明「書き込みアクセスは不要です。」
OBJECT tripCfgAdminStatus MIN-ACCESS not-accessible DESCRIPTION "Object is not needed when implemented in read-only mode."
オブジェクトTRIPCFGADMINSTATUS MIN-ACCESSアクセス不可能な説明「読み取り専用モードで実装されている場合、オブジェクトは必要ありません。」
OBJECT tripCfgPort MIN-ACCESS read-only DESCRIPTION "Write access is not required."
オブジェクトTRIPCFGPORT MIN-ACCESS読み取り専用説明「書き込みアクセスは不要です。」
OBJECT tripCfgMinItadOriginationInterval MIN-ACCESS read-only DESCRIPTION "Write access is not required."
オブジェクトTRIPCFGMINITADORIGINATIONINTERVAL MIN-ACCESS読み取り専用説明「書き込みアクセスは不要です。」
OBJECT tripCfgMinRouteAdvertisementInterval MIN-ACCESS read-only DESCRIPTION "Write access is not required."
オブジェクトtripcfgminrouteadedisementInterval min-access read-only説明「書き込みアクセスは不要です。」
OBJECT tripCfgMaxPurgeTime MIN-ACCESS read-only DESCRIPTION "Write access is not required."
オブジェクトTRIPCFGMAXPURGETIME MIN-ACCESS読み取り専用説明「書き込みアクセスは不要です。」
OBJECT tripCfgDisableTime MIN-ACCESS read-only DESCRIPTION "Write access is not required."
オブジェクトTRIPCFGDISABLETIME MIN-ACCESS読み取り専用説明「書き込みアクセスは不要です。」
OBJECT tripCfgStorage MIN-ACCESS read-only DESCRIPTION "Write access is not required."
オブジェクトTRIPCFGSTORAGE MIN-ACCESS読み取り専用説明「書き込みアクセスは不要です。」
OBJECT tripSupportedCommunityItad MIN-ACCESS read-only DESCRIPTION "Write access is not required."
Object TripsuptedCommunityItad Min-Access読み取り専用説明「書き込みアクセスは必要ありません」。
OBJECT tripSupportedCommunityStorage MIN-ACCESS read-only DESCRIPTION "Write access is not required."
Object TripsuptedCommunityStorage 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."
オブジェクトTripsuptedCommunityRowStatus Syntax RowStatus {Active（1）} Min-Access Read-Only説明「書き込みアクセスは不要であり、Activeはサポートする必要がある唯一のステータスです。」
OBJECT tripPeerAdminStatus MIN-ACCESS not-accessible DESCRIPTION "Object is not needed when implemented in read-only mode."
Object TrippeerAdmintatus 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 DESCRIPTION "Write access is not required."
Object TrippeerholdTimeConFigured Min-Access読み取り専用説明「書き込みアクセスは不要です。」
OBJECT tripPeerKeepAliveConfigured MIN-ACCESS read-only DESCRIPTION "Write access is not required."
Object TrippeerKeepaliveconfigured Min-Access読み取り専用説明「書き込みアクセスは不要です。」
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 }
::= { 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
}
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
}
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 Notifications {
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モジュールの管理されたオブジェクトには、総合的に、トリップデバイスの接続のトレースと影響を受け、接続特性の情報を提供するため、機密情報が含まれています。そのため、この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:
このMIBモジュールには、Read-Writeおよび/またはRead-Createの最大アクセス句がある管理オブジェクトが多数あります。このようなオブジェクトは、一部のネットワーク環境で敏感または脆弱と見なされる場合があります。適切な保護なしの非セキュア環境でのセット操作のサポートは、ネットワーク操作に悪影響を与える可能性があります。これらのオブジェクトには次のものが含まれます。
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.
tripcfgadmintatus：上から下までtripcfgadmintatusの不適切な設定は、トリップロケーションサーバーがトリップメッセージの処理を停止するのを引き起こします。
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.
tripcfgminitadoriginationterval、tripcfgminrouteadvertementementInterval：これらの値の不適切な構成は、この旅行ロケーションサーバーによって宣伝されているルートのローカルおよびグローバルな収束に悪影響を与える可能性があります。
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.
TrippeerAdmintatus：TrippeerAdmintatusの不適切な設定は、該当するリモートトリップロケーションサーバーピアを介して、宛先への接続性の大幅な破壊を引き起こす可能性があります。
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：これらの値の不適切な構成により、トリップピアセッションはサービス攻撃の拒否に対してより脆弱で回復力が低くなります。
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モジュールには、ネットワークの動作に関する機密情報を含む多くの管理されたオブジェクトがあります。たとえば、トリップロケーションサーバーのピアのローカルアドレスとリモートアドレスは、サービス攻撃の拒否またはアドレスのスプーフィングに使用されるトリップロケーションサーバーアドレスを防ぐために、トリップロケーションサーバーのインターフェイスアドレスを維持したい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を使用して）安全である場合でも、それでもセキュアネットワーク上の誰がアクセス/セット/セット（読み取り/変更/作成/削除/削除）を制御することはできません。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エンティティが、実際に取得または設定する正当な権利を持つプリンシパル（ユーザー）にのみオブジェクトにアクセスできるように適切に構成されていることを保証するのは、顧客/オペレーターの責任です（変更を変更します（変更）/作成/削除）それら。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119] Bradner、S。、「要件レベルを示すためにRFCで使用するためのキーワード」、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.、Perkins、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.、Perkins、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] Freed、N。およびS. Killee、「ネットワークサービス監視MIB」、RFC 2788、2000年3月。
[RFC3219] Rosenberg, J., Salama, H., and M. Squire, "Telephony Routing over IP (TRIP)", RFC 3219, January 2002.
[RFC3219] Rosenberg、J.、Salama、H。、およびM. Squire、「Thelephony Routing over IP（Trip）」、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] Daniele、M.、Haberman、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.、Perkins、D。、およびJ. Schoenwaelder、「管理情報の構造バージョン2（SMIV2）」、STD 58、RFC 2578、1999年4月。
[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] Willis、S.、Burruss、J。、およびJ. Chu、ed。、「SMIV2を使用したBorder Gateway Protocol（BGP-4）のマネージドオブジェクトの定義」、RFC 1657、1994年7月。
[RFC1771] Rekhter, Y. and T. Li, "Border Gateway Protocol 4 (BGP-4)", RFC 1771, March 1995.
[RFC1771] Rekhter、Y。およびT. Li、「Border Gateway Protocol 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] Case、J.、Mundy、R.、Partain、D。、およびB. Stewart、「インターネット標準管理フレームワークの紹介と適用声明」、RFC 3410、2002年12月。
The authors wish to thank Bert Wijnen, Dan Romascanu, and Jonathan Rosenberg for their insightful comments and suggestions.
著者は、洞察に満ちたコメントと提案について、Bert Wijnen、Dan Romascanu、Jonathan Rosenbergに感謝したいと考えています。
Thanks to Kevin Lingle for his invaluable comments, help with MIB things and great ideas.
Kevin Lingleが貴重なコメントをしてくれたことに感謝します。MIBのことと素晴らしいアイデアを手伝ってください。
David Zinman Editor 265 Ridley Blvd Toronto ON M5M 4N8 Canada
David Zinman Editor 265 Ridley Blvd Toronto on M5m 4N8カナダ
Phone: +1 416 433 4298
EMail: dzinman@rogers.com
David Walker Sedna Wireless Inc. 495 March Road, Suite 500 Ottawa, ON K2K 3G1 Canada
David Walker Sedna Wireless Inc. 495 March Road、Suite 500 Ottawa、K2K 3G1 Canada
Phone: +1 613 878 8142
EMail: david.walker@sedna-wireless.com
Jianping Jiang Syndesis Limited 30 Fulton Way Richmond Hill, ON L4B 1J5 Canada
Jianping Jiang Syndesis Limited 30 Fulton Way Richmond Hill、L4B 1J5 Canada
Phone: +1 905 886-7818 x2515
EMail: jjiang@syndesis.com
Copyright (C) The Internet Society (2004).
著作権（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.
この文書は、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.
このドキュメントとここに含まれる情報は、「現状のまま」と貢献者、彼が代表する組織（もしあれば）が後援する組織、インターネット社会、インターネットエンジニアリングタスクフォースがすべての保証を拒否し、表明または、ここでの情報の使用が、商品性または特定の目的に対する適合性の権利または黙示的な保証を侵害しないという保証を含むがこれらに限定されないことを含む。
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.
IETF事務局に行われたIPR開示のコピーと、利用可能にするライセンスの保証、またはこの仕様の実装者またはユーザーによるそのような独自の権利の使用のための一般的なライセンスまたは許可を取得しようとする試みの結果を取得できます。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エディター機能の資金は現在、インターネット協会によって提供されています。