RFC 6768 - ATM-Based xDSL Bonded Interfaces MIB 日本語訳

原文URL : https://datatracker.ietf.org/doc/html/rfc6768
タイトル : RFC 6768 - ATMベースのxDSLボンディングインターフェイスMIB
翻訳編集 : 自動生成

[要約] この文書は、ATM（Asynchronous Transfer Mode）ベースのxDSLボンディングインターフェースを管理するためのMIBを定義しています。ATMセルレベルで複数のDSL回線を束ねる際の管理情報を標準化し、広帯域なDSLアクセスサービスの運用保守を支援します。

Internet Engineering Task Force (IETF)                          E. Beili
Request for Comments: 6768                              Actelis Networks
Category: Standards Track                                  February 2013
ISSN: 2070-1721

ATM-Based xDSL Bonded Interfaces MIB

ATMベースのxDSLボンディングインターフェイスMIB

Abstract

概要

This document defines a Management Information Base (MIB) module for use with network management protocols in TCP/IP-based internets. This document proposes an extension to the GBOND-MIB module with a set of objects for managing ATM-based multi-pair bonded xDSL interfaces, as defined in ITU-T Recommendation G.998.1.

このドキュメントでは、TCP / IPベースのインターネットのネットワーク管理プロトコルで使用する管理情報ベース（MIB）モジュールを定義します。このドキュメントは、ITU-T勧告G.998.1で定義されているように、ATMベースのマルチペアボンディングxDSLインターフェイスを管理するためのオブジェクトセットを備えたGBOND-MIBモジュールの拡張を提案します。

Status of This Memo

本文書の状態

This is an Internet Standards Track document.

これはInternet Standards Trackドキュメントです。

This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.

このドキュメントは、IETF（Internet Engineering Task Force）の製品です。これは、IETFコミュニティのコンセンサスを表しています。公開レビューを受け、インターネットエンジニアリングステアリンググループ（IESG）による公開が承認されました。インターネット標準の詳細については、RFC 5741のセクション2をご覧ください。

Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6768.

このドキュメントの現在のステータス、正誤表、およびフィードバックの提供方法に関する情報は、http://www.rfc-editor.org/info/rfc6768で入手できます。

著作権表示

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

この文書は、BCP 78およびこの文書の発行日に有効なIETF文書に関するIETFトラストの法的規定（http://trustee.ietf.org/license-info）の対象となります。これらのドキュメントは、このドキュメントに関するあなたの権利と制限を説明しているため、注意深く確認してください。このドキュメントから抽出されたコードコンポーネントには、Trust Legal Provisionsのセクション4.eに記載されているSimplified BSD Licenseのテキストが含まれている必要があり、Simplified BSD Licenseに記載されているように保証なしで提供されます。

Table of Contents

   1. Introduction ....................................................2
   2. The Internet-Standard Management Framework ......................3
   3. The Broadband Forum Management Framework for xDSL Bonding .......3
   4. Relationship to Other MIB Modules ...............................3
      4.1. Relationship to Interfaces Group MIB Module ................3
      4.2. Relationship to G.Bond MIB Module ..........................3
      4.3. Relationship to ATM MIB Module .............................4
   5. MIB Structure ...................................................4
      5.1. Overview ...................................................4
      5.2. Performance Monitoring .....................................4
      5.3. Mapping of Broadband Forum TR-159 Managed Objects ..........5
   6. G.Bond/ATM MIB Definitions ......................................7
   7. Security Considerations ........................................31
   8. IANA Considerations ............................................32
   9. Acknowledgments ................................................32
   10. References ....................................................32
      10.1. Normative References .....................................32
      10.2. Informative References ...................................33

1. Introduction

1. はじめに

ATM-Based Multi-Pair Bonding, a.k.a. G.Bond/ATM, is specified in ITU-T Recommendation G.998.1 [G.998.1], which defines a method for bonding (or aggregating) multiple xDSL lines (or individual bearer channels in multiple xDSL lines) into a single bidirectional logical link carrying an ATM stream.

ATMベースのマルチペアボンディング、別名G.Bond/ATMは、ITU-T勧告G.998.1 [G.998.1]で指定されており、複数のxDSL回線（または個々のベアラチャネルを複数のxDSL回線）をATMストリームを運ぶ単一の双方向論理リンクに接続します。

This specification can be viewed as an evolution of the legacy Inverse Multiplexing for ATM (IMA) technology [AF-PHY-0086], applied to xDSL with variable rates on each line/bearer channel. As with the other bonding schemes, ATM bonding also allows bonding of up to 32 individual sub-layers with variable rates, providing common functionality for the configuration, initialization, operation, and monitoring of the bonded link.

この仕様は、各ライン/ベアラチャネルで可変レートのxDSLに適用される、従来のATM用逆多重化（IMA）テクノロジー[AF-PHY-0086]の進化形と見なすことができます。他のボンディング方式と同様に、ATMボンディングでは、最大32の個別サブレイヤーを可変レートでボンディングできるため、ボンディングされたリンクの構成、初期化、操作、および監視に共通の機能を提供します。

The MIB module defined in this document defines a set of managed objects for the management of G.998.1 bonded interfaces, extending the common objects specified in the GBOND-MIB module [RFC6765].

このドキュメントで定義されているMIBモジュールは、GBOND-MIBモジュール[RFC6765]で指定されている共通オブジェクトを拡張して、G.998.1結合インターフェースを管理するための一連の管理対象オブジェクトを定義しています。

2. The Internet-Standard Management Framework

2. インターネット標準の管理フレームワーク

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 objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB 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）で定義されたメカニズムを使用して定義されます。このメモは、SMIv2に準拠するMIBモジュールを指定します。これは、STD 58、RFC 2578 [RFC2578]、STD 58、RFC 2579 [RFC2579]およびSTD 58、RFC 2580 [RFC2580]で説明されています。

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, RFC 2119 [RFC2119].

このドキュメントのキーワード "MUST"、"MUST NOT"、"REQUIRED"、"SHALL"、"SHALL NOT"、"SHOULD"、"SHOULD NOT"、"RECOMMENDED"、"NOT RECOMMENDED"、"MAY"、および "OPTIONAL" は、BCP 14 で説明されているように解釈されるものとします。

3. The Broadband Forum Management Framework for xDSL Bonding

3. xDSLボンディング用のブロードバンドフォーラム管理フレームワーク

This document makes use of the Broadband Forum technical report "Management Framework for xDSL Bonding" [TR-159], defining a management model and a hierarchy of management objects for the bonded xDSL interfaces.

このドキュメントでは、Broadband Forumテクニカルレポート「xDSLボンディングの管理フレームワーク」[TR-159]を使用して、ボンディングされたxDSLインターフェースの管理モデルと管理オブジェクトの階層を定義します。

4. Relationship to Other MIB Modules

4. 他のMIBモジュールとの関係

This section outlines the relationship of the MIB modules defined in this document with other MIB modules described in the relevant RFCs. Specifically, the following MIB modules are discussed: the Interfaces Group MIB (IF-MIB) and the G.Bond MIB (GBOND-MIB).

このセクションでは、このドキュメントで定義されているMIBモジュールと、関連するRFCで説明されている他のMIBモジュールとの関係について概説します。具体的には、次のMIBモジュールについて説明します：インターフェイスグループMIB（IF-MIB）およびG.Bond MIB（GBOND-MIB）。

4.1. Relationship to Interfaces Group MIB Module

4.1. インターフェイスグループMIBモジュールとの関係

A G.Bond/ATM port is a private case of a bonded multi-pair xDSL interface and as such is managed using generic interface management objects defined in the IF-MIB [RFC2863]. In particular, an interface index (ifIndex) is used to index instances of G.Bond/ATM ports, as well as xDSL lines/channels, in a managed system.

G.Bond/ATMポートは、ボンディングされたマルチペアxDSLインターフェイスのプライベートケースであり、IF-MIB [RFC2863]で定義されている一般的なインターフェイス管理オブジェクトを使用して管理されます。特に、インターフェイスインデックス（ifIndex）は、管理対象システム内のG.Bond/ATMポートのインスタンスだけでなく、xDSL回線/チャネルのインデックスにも使用されます。

4.2. Relationship to G.Bond MIB Module

4.2. G.Bond MIBモジュールとの関係

The GBOND-MIB module [RFC6765] defines management objects common for all bonded multi-pair xDSL interfaces. In particular, it describes the bonding management, bonded port and channel configuration, initialization sequence, etc.

GBOND-MIBモジュール[RFC6765]は、すべてのボンディングされたマルチペアxDSLインターフェイスに共通の管理オブジェクトを定義します。特に、ボンディング管理、ボンディングされたポートとチャネルの構成、初期化シーケンスなどについて説明します。

Both the GBOND-MIB and G9981-MIB modules are REQUIRED to manage a G.Bond/ATM port.

G.Bond/ATMポートを管理するには、GBOND-MIBモジュールとG9981-MIBモジュールの両方が必要です。

4.3. Relationship to ATM MIB Module

4.3. ATM MIBモジュールとの関係

The ATM-MIB [RFC2515] module defines management objects for an ATM interface.

ATM-MIB [RFC2515]モジュールは、ATMインターフェイスの管理オブジェクトを定義します。

The ATM-MIB module can be used to manage the ATM aspects of a G.Bond/ ATM port.

ATM-MIBモジュールは、G.Bond / ATMポートのATMの側面を管理するために使用できます。

5. MIB Structure

5. MIBの構造

5.1. Overview

5.1. 概観

All management objects defined in the G9981-MIB module are contained in a single group g9981Port. This group is further split into 4 sub-groups, structured as recommended by RFC 4181 [RFC4181]:

G9981-MIBモジュールで定義されているすべての管理オブジェクトは、単一のグループg9981Portに含まれています。このグループはさらに4つのサブグループに分割され、RFC 4181 [RFC4181]で推奨されているように構造化されています。

o g9981PortNotifications - containing notifications (Up/Downstream Differential Delay Tolerance Exceeded).

o g9981PortNotifications-通知が含まれています（上流/下流の差分遅延許容値を超えています）。

o g9981PortConfTable - containing objects for configuration of a G.Bond/ATM port.

o g9981PortConfTable-G.Bond/ATMポートの構成用のオブジェクトを含みます。

o g9981PortStatusTable - containing objects providing overall status information of a G.Bond/ATM port, complementing the generic status information from the ifTable of the IF-MIB and the gBondFltStatus of the GBOND-MIB.

o g9981PortStatusTable-G-Bond / ATMポートの全体的なステータス情報を提供するオブジェクトを含み、IF-MIBのifTableとGBOND-MIBのgBondFltStatusからの一般的なステータス情報を補完します。

o g9981PM - containing objects providing historical Performance Monitoring (PM) information of a G.Bond/ATM port, complementing the PM information from the gBondPortPM of the GBOND-MIB.

o g9981PM-G.Bond/ATMポートの履歴Performance Monitoring（PM）情報を提供するオブジェクトを含み、GBOND-MIBのgBondPortPMからのPM情報を補完します。

Note that the rest of the objects for the Generic Bonding Sub-layer (GBS) port configuration, capabilities, status, notifications, and Performance Monitoring are located in the GBOND-MIB module.

Generic Bonding Sub-layer（GBS）ポート構成、機能、ステータス、通知、およびパフォーマンスモニタリングの残りのオブジェクトは、GBOND-MIBモジュールにあります。

5.2. Performance Monitoring

5.2. パフォーマンス監視

The OPTIONAL Performance Monitoring counters, thresholds, and history buckets (interval-counters) are implemented using the textual conventions defined in the HC-PerfHist-TC-MIB [RFC3705]. The HC-PerfHist-TC-MIB defines 64-bit versions of the textual conventions found in the PerfHist-TC-MIB [RFC3593].

オプションの (OPTIONAL)パフォーマンスモニタリングカウンター、しきい値、および履歴バケット（間隔カウンター）は、HC-PerfHist-TC-MIB [RFC3705]で定義されているテキストの規則を使用して実装されます。 HC-PerfHist-TC-MIBは、PerfHist-TC-MIB [RFC3593]にあるテキスト表記の64ビットバージョンを定義します。

The agent SHOULD align the beginning of each interval to a fifteen-minute boundary of a wall clock. Likewise, the beginning of each one-day interval SHOULD be aligned with the start of a day.

エージェントは、各間隔の始まりを壁時計の15分の境界に合わせるべきです（SHOULD）。同様に、各1日の間隔の開始は、1日の開始に合わせるべきです (SHOULD)。

Counters are not reset when a GBS is re-initialized, but rather only when the agent is reset or re-initialized.

GBSが再初期化されたときにカウンターがリセットされるのではなく、エージェントがリセットまたは再初期化されたときにのみカウンターがリセットされます。

Note that the accumulation of certain performance events for a monitored entity is inhibited (counting stops) during periods of service unavailability on that entity. The DESCRIPTION clause of Performance Monitoring counters in this MIB module specifies which of the counters are inhibited during periods of service unavailability.

監視対象エンティティの特定のパフォーマンスイベントの蓄積は、そのエンティティでサービスを利用できない期間中は禁止（カウント停止）されることに注意してください。このMIBモジュールのパフォーマンスモニタリングカウンタのDESCRIPTION句は、サービスが利用できない期間にどのカウンタを禁止するかを指定します。

5.3. Mapping of Broadband Forum TR-159 Managed Objects

5.3. ブロードバンドフォーラムTR-159管理対象オブジェクトのマッピング

This section contains the mapping between relevant managed objects (attributes) defined in [TR-159] and the managed objects defined in this document.

このセクションには、[TR-159]で定義されている関連する管理対象オブジェクト（属性）と、このドキュメントで定義されている管理対象オブジェクトの間のマッピングが含まれています。

   +-----------------------------+-------------------------------------+
   | TR-159 Managed Object       | Corresponding SNMP Object           |
   +-----------------------------+-------------------------------------+
   | oBondATM - Basic Package    |                                     |
   | (Mandatory)                 |                                     |
   +-----------------------------+-------------------------------------+
   | aIMARxLostCells             | g9981PortStatRxLostCells            |
   +-----------------------------+-------------------------------------+
   | aIMAPeerRxLostCells         | g9981PortStatTxLostCells            |
   +-----------------------------+-------------------------------------+
   | aIMAMaxUpDiffDelay          | g9981PortStatMaxUpDiffDelay         |
   +-----------------------------+-------------------------------------+
   | aIMAMaxDownDiffDelay        | g9981PortStatMaxDnDiffDelay         |
   +-----------------------------+-------------------------------------+
   | aIMAUpDiffDelayTolerance    | g9981PortConfUpDiffDelayTolerance   |
   +-----------------------------+-------------------------------------+
   | aIMADownDiffDelayTolerance  | g9981PortConfDnDiffDelayTolerance   |
   +-----------------------------+-------------------------------------+
   | aIMADiffDelayToleranceExcee | g9981PortConfDiffDelayToleranceExce |
   | dedEnable                   | ededEnable                          |
   +-----------------------------+-------------------------------------+
   | nIMAUpDiffDelayToleranceExc | g9981UpDiffDelayToleranceExceeded   |
   | eeded                       |                                     |
   +-----------------------------+-------------------------------------+
   | nIMADownDiffDelayToleranceE | g9981DnDiffDelayToleranceExceeded   |
   | xceeded                     |                                     |
   +-----------------------------+-------------------------------------+

Table 1: Mapping of TR-159 Managed Objects

表1：TR-159管理対象オブジェクトのマッピング

Note that some of the mapping between the objects defined in TR-159 and the ones defined in this MIB module is not one-to-one; for example, while TR-159 PM attributes aGroupPerf* map to the corresponding gBondPortPm* objects of the GBOND-MIB module, there are no dedicated PM attributes for the g9981PortPm* objects introduced in this MIB module. However, since their definition is identical to the definition of gBondPortPm* objects of the GBOND-MIB module, we can map g9981PortPm* to the relevant aGroupPerf* attributes of TR-159 and use the term 'partial mapping' to denote the fact that this mapping is not one-to-one.

TR-159で定義されたオブジェクトとこのMIBモジュールで定義されたオブジェクトの間のマッピングの一部は1対1ではないことに注意してください。たとえば、TR-159 PM属性aGroupPerf *は、GBOND-MIBモジュールの対応するgBondPortPm *オブジェクトにマッピングされますが、このMIBモジュールでは、g9981PortPm *オブジェクトに専用のPM属性が導入されていません。ただし、それらの定義はGBOND-MIBモジュールのgBondPortPm *オブジェクトの定義と同じであるため、g9981PortPm *をTR-159の関連するaGroupPerf *属性にマップし、「部分的なマッピング」という用語を使用して、このことを示すことができます。マッピングは1対1ではありません。

6. G.Bond/ATM MIB Definitions

6. G.Bond/ATM MIB定義

The G9981-MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863], and HC-PerfHist-TC-MIB [RFC3705]. The module has been structured as recommended by [RFC4181].

G9981-MIBモジュールは、SNMPv2-SMI [RFC2578]、SNMPv2-TC [RFC2579]、SNMPv2-CONF [RFC2580]、IF-MIB [RFC2863]、およびHC-PerfHist-TC-MIB [RFC3705]からオブジェクトをインポートします。モジュールは、[RFC4181]によって推奨されるように構成されています。

G9981-MIB DEFINITIONS ::= BEGIN

  IMPORTS
    MODULE-IDENTITY,
    OBJECT-TYPE,
    NOTIFICATION-TYPE,
    mib-2,
    Unsigned32,
    Counter32
      FROM SNMPv2-SMI           -- RFC 2578
    TEXTUAL-CONVENTION,
    TruthValue
      FROM SNMPv2-TC            -- RFC 2579
    MODULE-COMPLIANCE,
    OBJECT-GROUP,
    NOTIFICATION-GROUP
      FROM SNMPv2-CONF          -- RFC 2580
    ifIndex
      FROM IF-MIB               -- RFC 2863
    HCPerfCurrentCount,
    HCPerfIntervalCount,
    HCPerfValidIntervals,
    HCPerfInvalidIntervals,
    HCPerfTimeElapsed
      FROM  HC-PerfHist-TC-MIB  -- RFC 3705
    ;
------------------------------------------------------------------------
  g9981MIB MODULE-IDENTITY
    LAST-UPDATED "201302200000Z"  -- 20 February 2013
    ORGANIZATION "IETF ADSL MIB Working Group"
    CONTACT-INFO
      "WG charter:
        http://datatracker.ietf.org/wg/adslmib/charter/

      Mailing Lists:
        General Discussion: adslmib@ietf.org
        To Subscribe: adslmib-request@ietf.org
        In Body: subscribe your_email_address

Chair: Menachem Dodge Postal: ECI Telecom, Ltd. 30 Hasivim St., Petach-Tikva 4951169 Israel Phone: +972-3-926-8421 EMail: menachemdodge1@gmail.com

議長：Menachem Dodge郵便番号：ECI Telecom、Ltd.30 Hasivim St.、Petach-Tikva 4951169 Israel電話：+ 972-3-926-8421メール：menachemdodge1@gmail.com

Editor: Edward Beili Postal: Actelis Networks, Inc. 25 Bazel St., P.O.B. 10173 Petach-Tikva 49103 Israel Phone: +972-3-924-3491 EMail: edward.beili@actelis.com"

編集者：Edward Beili郵便番号：Actelis Networks、Inc.25 Bazel St.、P.O.B. 10173 Petach-Tikva 49103 Israel電話：+ 972-3-924-3491メール：edward.beili@actelis.com "

DESCRIPTION "The objects in this MIB module are used to manage the multi-pair bonded xDSL interfaces using ATM inverse multiplexing, as defined in ITU-T Recommendation G.998.1 (G.Bond/ATM).

説明「このMIBモジュールのオブジェクトは、ITU-T勧告G.998.1（G.Bond/ATM）で定義されているように、ATM逆多重化を使用してマルチペアボンディングxDSLインターフェイスを管理するために使用されます。

This MIB module MUST be used in conjunction with the GBOND-MIB module, common to all G.Bond technologies.

このMIBモジュールは、すべてのG.Bondテクノロジーに共通のGBOND-MIBモジュールと組み合わせて使用しなければなりません (MUST)。

The following references are used throughout this MIB module:

このMIBモジュール全体で次の参照が使用されています。

[G.998.1] refers to: ITU-T Recommendation G.998.1: 'ATM-based multi-pair bonding', January 2005.

[G.998.1]は次を参照します：ITU-T勧告G.998.1：「ATMベースのマルチペアボンディング」、2005年1月。

[TR-159] refers to: Broadband Forum Technical Report: 'Management Framework for xDSL Bonding', December 2008.

[TR-159]は、ブロードバンドフォーラムテクニカルレポート：「xDSLボンディングの管理フレームワーク」、2008年12月を指します。

      Naming Conventions:
        ATM   - Asynchronous Transfer Mode
        BCE   - Bonding Channel Entity
        BTU   - Bonding Terminating Unit
        CO    - Central Office
        CPE   - Customer Premises Equipment
        GBS   - Generic Bonding Sub-layer
        GBS-C - Generic Bonding Sub-layer, CO side
        GBS-R - Generic Bonding Sub-layer, RT (or CPE) side
        PM    - Performance Monitoring
        RT    - Remote Terminal
        SNR   - Signal to Noise Ratio
        SES   - Severely Errored Seconds
        UAS   - Unavailable Seconds

Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info)."

ソースおよびバイナリ形式での再配布および使用は、変更の有無にかかわらず、IETFドキュメントに関連するIETFトラストの法的規定のセクション4.cに記載されているSimplified BSD Licenseに準拠し、それに含まれるライセンス条項に従って許可されます（ http://trustee.ietf.org/license-info）」

REVISION "201302200000Z" -- 20 February 2013 DESCRIPTION "Initial version, published as RFC 6768."

改訂 "201302200000Z"-2013年2月20日説明 "初期バージョン、RFC 6768として公開されました。"

    ::= { mib-2 208 }

   -- Sections of the module
   -- Structured as recommended by RFC 4181, Appendix D

   g9981Objects     OBJECT IDENTIFIER ::= { g9981MIB 1 }

   g9981Conformance OBJECT IDENTIFIER ::= { g9981MIB 2 }

-- Groups in the module

-モジュール内のグループ

   g9981Port        OBJECT IDENTIFIER ::= { g9981Objects 1 }

-- Textual Conventions

-テキスト表記

   MilliSeconds ::= TEXTUAL-CONVENTION
     DISPLAY-HINT "d"
     STATUS      current
     DESCRIPTION
       "Represents time unit value in milliseconds."
     SYNTAX      Unsigned32

-- Port Notifications group

-ポート通知グループ

   g9981PortNotifications OBJECT IDENTIFIER
     ::= { g9981Port 0 }

   g9981UpDiffDelayToleranceExceeded NOTIFICATION-TYPE
     OBJECTS {
       -- ifIndex is not needed here, since we are under specific GBS
       g9981PortConfUpDiffDelayTolerance,
       g9981PortStatMaxUpDiffDelay
     }
     STATUS      current
     DESCRIPTION
       "This notification indicates that the maximum upstream
       differential delay has exceeded the max upstream differential
       delay threshold, specified by
       g9981PortConfUpDiffDelayTolerance.

This notification MAY be sent for the GBS-C ports while the port is 'up', on the crossing event in both directions: from normal (diff. delay is above the threshold) to low (diff. delay equals the threshold or is below it) and from low to normal. This notification is not applicable to the GBS-R ports.

この通知は、ポートが「アップ」の間に、両方向の交差イベントで、GBS-Cポートに対して送信される場合があります (MAY)：通常（差分遅延がしきい値を超える）から低（差分遅延がしきい値に等しいか、しきい値未満）それから）そして低から通常に。この通知は、GBS-Rポートには適用されません。

Generation of this notification is controlled by the g9981PortConfDiffDelayToleranceExceededEnable attribute.

この通知の生成は、g9981PortConfDiffDelayToleranceExceededEnable属性によって制御されます。

       This object maps to the TR-159 notification
       nIMAUpDiffDelayToleranceExceeded."
     REFERENCE
       "[TR-159], Section 5.5.2.8"
     ::= { g9981PortNotifications 1 }

   g9981DnDiffDelayToleranceExceeded NOTIFICATION-TYPE
     OBJECTS {
       -- ifIndex is not needed here, since we are under specific GBS
       g9981PortConfDnDiffDelayTolerance,
       g9981PortStatMaxDnDiffDelay
     }
     STATUS      current
     DESCRIPTION
       "This notification indicates that the maximum downstream
       differential delay has exceeded the max downstream
       differential delay threshold, specified by
       g9981PortConfDnDiffDelayTolerance.

Generation of this notification is controlled by the g9981PortConfDiffDelayToleranceExceededEnable attribute.

この通知の生成は、g9981PortConfDiffDelayToleranceExceededEnable属性によって制御されます。

       This object maps to the TR-159 notification
       nIMADownDiffDelayToleranceExceeded."
     REFERENCE
       "[TR-159], Section 5.5.2.9"
     ::= { g9981PortNotifications 2 }

-- G.Bond/ATM Port group

-G.Bond/ATMポートグループ

   g9981PortConfTable OBJECT-TYPE
     SYNTAX      SEQUENCE OF G9981PortConfEntry
     MAX-ACCESS  not-accessible
     STATUS      current
     DESCRIPTION
       "Table for configuration of G.Bond/ATM ports.  Entries in
       this table MUST be maintained in a persistent manner."
     ::= { g9981Port 1 }

   g9981PortConfEntry OBJECT-TYPE
     SYNTAX      G9981PortConfEntry
     MAX-ACCESS  not-accessible
     STATUS      current
     DESCRIPTION
       "An entry in the G.Bond/ATM Port Configuration table.
       Each entry represents a G.Bond/ATM port indexed by the
       ifIndex.  Additional configuration parameters are available
       via the gBondPortConfEntry of the GBOND-MIB.
       Note that a G.Bond/ATM port runs on top of a single or
       multiple BCE port(s), which are also indexed by the ifIndex."
     INDEX  { ifIndex }
     ::= { g9981PortConfTable 1 }

   G9981PortConfEntry ::=
     SEQUENCE {
       g9981PortConfUpDiffDelayTolerance             MilliSeconds,
       g9981PortConfDnDiffDelayTolerance             MilliSeconds,
       g9981PortConfDiffDelayToleranceExceededEnable TruthValue
     }

   g9981PortConfUpDiffDelayTolerance  OBJECT-TYPE
     SYNTAX      MilliSeconds (0..2047)
     UNITS       "milliseconds"
     MAX-ACCESS  read-write
     STATUS      current
     DESCRIPTION
       "A maximum tolerated upstream differential delay (among
       the member BCEs) of a G.Bond/ATM port, expressed in ms.

This object is read-write for the GBS-C ports. It is irrelevant for the GBS-R ports -- an attempt to read or change this object MUST be rejected (in the case of SNMP, with the error inconsistentValue).

このオブジェクトは、GBS-Cポートでは読み書き可能です。これは、GBS-Rポートには関係ありません。このオブジェクトの読み取りまたは変更の試みは拒否しなければなりません (MUST)（SNMPの場合、エラーinconsistentValue）。

       This object maps to the TR-159 attribute
       aIMAUpDiffDelayTolerance."
     REFERENCE
       "[TR-159], Section 5.5.2.5; [G.998.1], Section 11.4.1 (6)"
     ::= { g9981PortConfEntry 1 }

   g9981PortConfDnDiffDelayTolerance  OBJECT-TYPE
     SYNTAX      MilliSeconds (0..2047)
     UNITS       "milliseconds"
     MAX-ACCESS  read-write
     STATUS      current
     DESCRIPTION
       "A maximum tolerated downstream differential delay (among
       the member BCEs) of a G.Bond/ATM port, expressed in ms.

       This object maps to the TR-159 attribute
       aIMADownDiffDelayTolerance."
     REFERENCE
       "[TR-159], Section 5.5.2.6; [G.998.1], Section 11.4.1 (6)"
     ::= { g9981PortConfEntry 2 }

   g9981PortConfDiffDelayToleranceExceededEnable  OBJECT-TYPE
     SYNTAX      TruthValue
     MAX-ACCESS  read-write
     STATUS      current
     DESCRIPTION
       "Indicates whether g9981UpDiffDelayToleranceExceeded and
       g9981DnDiffDelayToleranceExceeded notifications should
       be generated for G.Bond/ATM port.

A value of true(1) indicates that the notifications are enabled. A value of false(2) indicates that the notifications are disabled.

true（1）の値は、通知が有効であることを示します。 false（2）の値は、通知が無効であることを示します。

This object is read-write for the GBS-C. It is irrelevant for the GBS-R ports -- an attempt to read or change this object MUST be rejected (in the case of SNMP, with the error inconsistentValue).

このオブジェクトは、GBS-Cの読み取り/書き込みです。これは、GBS-Rポートには関係ありません。このオブジェクトの読み取りまたは変更の試みは拒否しなければなりません (MUST)（SNMPの場合、エラーinconsistentValue）。

       This object maps to the TR-159 attribute
       aIMADiffDelayToleranceExceededEnable."
     REFERENCE
       "[TR-159], Section 5.5.5.7"
     ::= { g9981PortConfEntry 3 }

   g9981PortStatTable OBJECT-TYPE
     SYNTAX      SEQUENCE OF G9981PortStatEntry
     MAX-ACCESS  not-accessible
     STATUS      current
     DESCRIPTION
       "This table provides overall status information of G.Bond/ATM
       ports, complementing the generic status information from the
       ifTable of the IF-MIB and the gBondFltStatus of the GBOND-MIB.
       Additional status information about connected BCEs is available
       from the relevant line MIBs.

       This table contains live data from the equipment.  As such, it
       is NOT persistent."
     ::= { g9981Port 2 }

   g9981PortStatEntry OBJECT-TYPE
     SYNTAX      G9981PortStatEntry
     MAX-ACCESS  not-accessible
     STATUS      current
     DESCRIPTION
       "An entry in the G.Bond/ATM Port Status table.
       Each entry represents a G.Bond/ATM port indexed by the
       ifIndex.
       Note that a GBS port runs on top of a single or multiple BCE
       port(s), which are also indexed by the ifIndex."
     INDEX  { ifIndex }
     ::= { g9981PortStatTable 1 }

   G9981PortStatEntry ::=
     SEQUENCE {
       g9981PortStatRxLostCells      Counter32,
       g9981PortStatTxLostCells      Counter32,
       g9981PortStatMaxUpDiffDelay   Unsigned32,
       g9981PortStatMaxDnDiffDelay   Unsigned32
     }

   g9981PortStatRxLostCells  OBJECT-TYPE
     SYNTAX      Counter32
     UNITS       "cells"
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "The number of lost ATM cells detected by the G.Bond/ATM port
       in the receive direction (e.g., upstream direction for
       a GBS-C port).

Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime as defined in the IF-MIB.

このカウンターの値の不連続は、管理システムの再初期化時に発生する可能性があります。また、IF-MIBで定義されているifCounterDiscontinuityTimeの値によって示される他の場合にも発生する可能性があります。

       This object maps to the TR-159 attribute aIMARxLostCells."
     REFERENCE
       "[TR-159], Section 5.5.2.1; [G.998.1], Section 11.4.2 (4)"
     ::= { g9981PortStatEntry 1 }

   g9981PortStatTxLostCells  OBJECT-TYPE
     SYNTAX      Counter32
     UNITS       "cells"
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "The number of lost ATM cells detected by the peer G.Bond/ATM
       port in the receive direction, i.e., downstream direction for a
       GBS-C port.

This object is irrelevant for the GBS-R ports -- an attempt to read it MUST be rejected (in the case of SNMP, with the error inconsistentValue).

このオブジェクトはGBS-Rポートには関係ありません-それを読む試みは拒否されなければなりません (MUST)（SNMPの場合、エラーinconsistentValueで）。

       This object maps to the TR-159 attribute aIMAPeerRxLostCells."
     REFERENCE
       "[TR-159], Section 5.5.2.2; [G.998.1], Section 11.4.2 (4)"
     ::= { g9981PortStatEntry 2 }

   g9981PortStatMaxUpDiffDelay  OBJECT-TYPE
     SYNTAX      Unsigned32
     UNITS       "0.1 ms"
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "Current maximum upstream differential delay between all
       operational BCEs in the G.Bond/ATM bonding group, measured in
       units of 0.1 ms.

This object is read-only for the GBS-C ports. It is irrelevant for the GBS-R ports -- an attempt to read this object MUST be rejected (in the case of SNMP, with the error inconsistentValue).

このオブジェクトは、GBS-Cポートでは読み取り専用です。これはGBS-Rポートには関係ありません-このオブジェクトを読み取る試みは拒否されなければなりません (MUST)（SNMPの場合、エラーinconsistentValueで）。

       This object maps to the TR-159 attribute aIMAMaxUpDiffDelay."
     REFERENCE
       "[TR-159], Section 5.5.2.3"
     ::= { g9981PortStatEntry 3 }

   g9981PortStatMaxDnDiffDelay  OBJECT-TYPE
     SYNTAX      Unsigned32
     UNITS       "0.1 ms"
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "Current maximum downstream differential delay between all
       operational BCEs in the G.Bond/ATM bonding group, measured in
       units of 0.1 ms.

This object is read-only for the GBS-C ports. It is irrelevant for the GBS-R ports -- an attempt to read this object MUST be rejected (in the case of SNMP, with the error inconsistentValue).

       This object maps to the TR-159 attribute aIMAMaxDownDiffDelay."
     REFERENCE
       "[TR-159], Section 5.5.2.4"
     ::= { g9981PortStatEntry 4 }

   -------------------------------
   -- Performance Monitoring group
   -------------------------------

   g9981PM   OBJECT IDENTIFIER ::= { g9981Port 3 }

   g9981PortPmCurTable OBJECT-TYPE
     SYNTAX      SEQUENCE OF G9981PortPmCurEntry
     MAX-ACCESS  not-accessible
     STATUS      current
     DESCRIPTION
       "This table contains current Performance Monitoring information
       for a G.Bond/ATM port.  This table contains live data from the
       equipment and as such is NOT persistent."
     ::= { g9981PM 1 }

   g9981PortPmCurEntry OBJECT-TYPE
     SYNTAX      G9981PortPmCurEntry
     MAX-ACCESS  not-accessible
     STATUS      current
     DESCRIPTION
       "An entry in the G.Bond/ATM Port PM table.
       Each entry represents a G.Bond/ATM port indexed by the
       ifIndex."
     INDEX  { ifIndex }
     ::= { g9981PortPmCurTable 1 }

   G9981PortPmCurEntry ::=
     SEQUENCE {
       g9981PortPmCur15MinValidIntervals   HCPerfValidIntervals,
       g9981PortPmCur15MinInvalidIntervals HCPerfInvalidIntervals,
       g9981PortPmCur15MinTimeElapsed      HCPerfTimeElapsed,
       g9981PortPmCur15MinRxLostCells      HCPerfCurrentCount,
       g9981PortPmCur15MinTxLostCells      HCPerfCurrentCount,
       g9981PortPmCur15MinUpDiffDelay      HCPerfCurrentCount,
       g9981PortPmCur15MinDnDiffDelay      HCPerfCurrentCount,
       g9981PortPmCur1DayValidIntervals    Unsigned32,
       g9981PortPmCur1DayInvalidIntervals  Unsigned32,
       g9981PortPmCur1DayTimeElapsed       HCPerfTimeElapsed,
       g9981PortPmCur1DayRxLostCells       HCPerfCurrentCount,
       g9981PortPmCur1DayTxLostCells       HCPerfCurrentCount,
       g9981PortPmCur1DayUpDiffDelay       HCPerfCurrentCount,
       g9981PortPmCur1DayDnDiffDelay       HCPerfCurrentCount
     }

   g9981PortPmCur15MinValidIntervals  OBJECT-TYPE
     SYNTAX      HCPerfValidIntervals
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "A read-only number of 15-minute intervals for which the
       performance data was collected.  The value of this object will
       be 96 or the maximum number of 15-minute history intervals
       collected by the implementation, unless the measurement was
       (re)started recently, in which case the value will be the
       number of complete 15-minute intervals for which there are at
       least some data.

In certain cases, it is possible that some intervals are unavailable. In this case, this object reports the maximum interval number for which data is available.

場合によっては、一部の間隔が使用できない可能性があります。この場合、このオブジェクトは、データが利用可能な最大間隔数を報告します。

       This object partially maps to the TR-159 attribute
       aGroupPerf15MinValidIntervals."
     REFERENCE
       "[TR-159], Section 5.5.1.32"
     ::= { g9981PortPmCurEntry 1 }

   g9981PortPmCur15MinInvalidIntervals  OBJECT-TYPE
     SYNTAX      HCPerfInvalidIntervals
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "A read-only number of 15-minute intervals for which the
       performance data was not always available.  The value will
       typically be zero, except in cases where the data for some
       intervals are not available.

       This object partially maps to the TR-159 attribute
       aGroupPerf15MinInvalidIntervals."
     REFERENCE
       "[TR-159], Section 5.5.1.33"
     ::= { g9981PortPmCurEntry 2 }

   g9981PortPmCur15MinTimeElapsed  OBJECT-TYPE
     SYNTAX      HCPerfTimeElapsed
     UNITS       "seconds"
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "A read-only count of seconds that have elapsed since the
       beginning of the current 15-minute performance interval.

       This object partially maps to the TR-159 attribute
       aGroupPerfCurr15MinTimeElapsed."
     REFERENCE
       "[TR-159], Section 5.5.1.34"
     ::= { g9981PortPmCurEntry 3 }

   g9981PortPmCur15MinRxLostCells  OBJECT-TYPE
     SYNTAX      HCPerfCurrentCount
     UNITS       "cells"
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "A read-only count of lost ATM cells detected by a G.Bond/ATM
       port (e.g., the GBS-C) in the receive direction, during the
       current 15-minute performance history interval.

Note that the total number of lost ATM cells is indicated by the g9981PortStatRxLostCells object.

失われたATMセルの総数は、g9981PortStatRxLostCellsオブジェクトによって示されることに注意してください。

       This object is inhibited during Severely Errored Seconds (SES)
       or Unavailable Seconds (UAS)."
     REFERENCE
       "[TR-159], Section 5.5.2.1"
     ::= { g9981PortPmCurEntry 4}

   g9981PortPmCur15MinTxLostCells  OBJECT-TYPE
     SYNTAX      HCPerfCurrentCount
     UNITS       "cells"
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "A read-only count of lost ATM cells detected by the peer
       G.Bond/ATM port (e.g., by the GBS-R for the GBS-C) during the
       current 15-minute performance history interval.

Note that the total number of lost ATM cells is indicated by the g9981PortStatTxLostCells object.

失われたATMセルの総数は、g9981PortStatTxLostCellsオブジェクトによって示されることに注意してください。

       This object is inhibited during Unavailable Seconds (UAS)."
     REFERENCE
       "[TR-159], Section 5.5.2.2"
     ::= { g9981PortPmCurEntry 5}

   g9981PortPmCur15MinUpDiffDelay  OBJECT-TYPE
     SYNTAX      HCPerfCurrentCount
     UNITS       "0.1 ms"
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "A read-only value specifying the maximum upstream differential
       delay between all operational BCEs in the GBS-C, measured in
       units of 0.1 ms, during the current 15-minute performance
       interval.

Note that the current max upstream differential delay is indicated by the g9981PortStatMaxUpDiffDelay object.

現在の最大アップストリーム差分遅延は、g9981PortStatMaxUpDiffDelayオブジェクトによって示されることに注意してください。

This object is inhibited during Unavailable Seconds (UAS)."

このオブジェクトは、使用不可秒数（UAS）の間は禁止されています。」

     REFERENCE
       "[TR-159], Section 5.5.2.3"
     ::= { g9981PortPmCurEntry 6}

   g9981PortPmCur15MinDnDiffDelay  OBJECT-TYPE
     SYNTAX      HCPerfCurrentCount
     UNITS       "0.1 ms"
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "A read-only value specifying the maximum downstream
       differential delay between all operational BCEs in the GBS-C
       (as perceived by the GBS-R), measured in units of 0.1 ms,
       during the current 15-minute performance history interval.

Note that the current max downstream differential delay is indicated by the g9981PortStatMaxDnDiffDelay object.

現在の最大ダウンストリーム差分遅延は、g9981PortStatMaxDnDiffDelayオブジェクトによって示されることに注意してください。

       This object is inhibited during Unavailable Seconds (UAS)."
     REFERENCE
       "[TR-159], Section 5.5.2.4"
     ::= { g9981PortPmCurEntry 7}

   g9981PortPmCur1DayValidIntervals  OBJECT-TYPE
     SYNTAX      Unsigned32 (0..7)
     UNITS       "days"
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "A read-only number of 1-day intervals for which data was
       collected.  The value of this object will be 7 or the maximum
       number of 1-day history intervals collected by the
       implementation, unless the measurement was (re)started recently,
       in which case the value will be the number of complete 1-day
       intervals for which there are at least some data.
       In certain cases, it is possible that some intervals are
       unavailable.  In this case, this object reports the maximum
       interval number for which data is available."
     REFERENCE
       "[TR-159], Section 5.5.1.45"
     ::= { g9981PortPmCurEntry 8 }

   g9981PortPmCur1DayInvalidIntervals  OBJECT-TYPE
     SYNTAX      Unsigned32 (0..7)
     UNITS       "days"
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "A read-only number of 1-day intervals for which data was
       not always available.  The value will typically be zero, except
       in cases where the data for some intervals are not available."
     REFERENCE
       "[TR-159], Section 5.5.1.46"
     ::= { g9981PortPmCurEntry 9 }

   g9981PortPmCur1DayTimeElapsed  OBJECT-TYPE
     SYNTAX      HCPerfTimeElapsed
     UNITS       "seconds"
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "A read-only count of seconds that have elapsed since the
       beginning of the current 1-day performance interval."
     REFERENCE
       "[TR-159], Section 5.5.1.47"
     ::= { g9981PortPmCurEntry 10 }

   g9981PortPmCur1DayRxLostCells  OBJECT-TYPE
     SYNTAX      HCPerfCurrentCount
     UNITS       "cells"
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "A read-only count of lost ATM cells detected by the G.Bond/ATM
       port (e.g., the GBS-C) during the current 1-day performance
       interval.

       This object is inhibited during Severely Errored Seconds (SES)
       and Unavailable Seconds (UAS)."
     ::= { g9981PortPmCurEntry 11 }

   g9981PortPmCur1DayTxLostCells OBJECT-TYPE
     SYNTAX      HCPerfCurrentCount
     UNITS       "cells"
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "A read-only count of lost ATM cells detected by the peer
       G.Bond/ATM port (e.g., by the GBS-R for the GBS-C) during the
       current 1-day performance history interval.

       This object is inhibited during Unavailable Seconds (UAS)."
     ::= { g9981PortPmCurEntry 12 }

   g9981PortPmCur1DayUpDiffDelay  OBJECT-TYPE
     SYNTAX      HCPerfCurrentCount
     UNITS       "0.1 ms"
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "A read-only value specifying the maximum upstream differential
       delay between all operational BCEs in the GBS-C, measured in
       units of 0.1 ms, during the current 1-day performance
       interval.

       This object is inhibited during Unavailable Seconds (UAS)."
     ::= { g9981PortPmCurEntry 13 }

   g9981PortPmCur1DayDnDiffDelay  OBJECT-TYPE
     SYNTAX      HCPerfCurrentCount
     UNITS       "0.1 ms"
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "A read-only value specifying the maximum downstream
       differential delay between all operational BCEs in the GBS-C,
       measured in units of 0.1 ms, during the current 1-day
       performance interval.

       This object is inhibited during Unavailable Seconds (UAS)."
     ::= { g9981PortPmCurEntry 14 }

-- Port PM history: 15-min buckets

-ポートPM履歴：15分のバケット

   g9981PortPm15MinTable OBJECT-TYPE
     SYNTAX      SEQUENCE OF G9981PortPm15MinEntry
     MAX-ACCESS  not-accessible
     STATUS      current
     DESCRIPTION
       "This table contains historical 15-minute buckets of Performance
       Monitoring information for a G.Bond/ATM port (a row for each
       15-minute interval, up to 96 intervals).
       Entries in this table MUST be maintained in a persistent manner."
     ::= { g9981PM 2 }

   g9981PortPm15MinEntry OBJECT-TYPE
     SYNTAX      G9981PortPm15MinEntry
     MAX-ACCESS  not-accessible
     STATUS      current
     DESCRIPTION
       "An entry in the G.Bond/ATM Port historical 15-minute PM table.
       Each entry represents Performance Monitoring data for a
       G.Bond/ATM port, indexed by the ifIndex, collected during a
       particular 15-minute interval, indexed by the
       g9981PortPm15MinIntervalIndex."
     INDEX  { ifIndex, g9981PortPm15MinIntervalIndex }
     ::= { g9981PortPm15MinTable 1 }

   G9981PortPm15MinEntry ::=
     SEQUENCE {
       g9981PortPm15MinIntervalIndex       Unsigned32,
       g9981PortPm15MinIntervalMoniTime    HCPerfTimeElapsed,
       g9981PortPm15MinIntervalRxLostCells HCPerfIntervalCount,
       g9981PortPm15MinIntervalTxLostCells HCPerfIntervalCount,
       g9981PortPm15MinIntervalUpDiffDelay HCPerfIntervalCount,
       g9981PortPm15MinIntervalDnDiffDelay HCPerfIntervalCount,
       g9981PortPm15MinIntervalValid       TruthValue
     }

   g9981PortPm15MinIntervalIndex  OBJECT-TYPE
     SYNTAX      Unsigned32 (1..96)
     MAX-ACCESS  not-accessible
     STATUS      current
     DESCRIPTION
       "Performance data interval number.  1 is the most recent previous
       interval; interval 96 is 24 hours ago.
       Intervals 2..96 are OPTIONAL.

       This object partially maps to the TR-159 attribute
       aGroupPerf15MinIntervalNumber."
     REFERENCE
       "[TR-159], Section 5.5.1.57"
     ::= { g9981PortPm15MinEntry 1 }

   g9981PortPm15MinIntervalMoniTime  OBJECT-TYPE
     SYNTAX      HCPerfTimeElapsed
     UNITS       "seconds"
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "A read-only count of seconds over which the performance data
       was actually monitored.  This value will be the same as the
       interval duration (900 seconds), except in a situation where
       performance data could not be collected for any reason."
     ::= { g9981PortPm15MinEntry 2 }

   g9981PortPm15MinIntervalRxLostCells  OBJECT-TYPE
     SYNTAX      HCPerfIntervalCount
     UNITS       "cells"
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "A read-only count of lost ATM cells detected by a G.Bond/ATM
       port (e.g., the GBS-C) in the receive direction, during the
       15-minute performance history interval.

Note that the total number of lost ATM cells is indicated by the g9981PortStatRxLostCells object.

失われたATMセルの総数は、g9981PortStatRxLostCellsオブジェクトによって示されることに注意してください。

       This object is inhibited during Severely Errored Seconds (SES)
       or Unavailable Seconds (UAS)."
     REFERENCE
       "[TR-159], Section 5.5.2.1"
     ::= { g9981PortPm15MinEntry 3 }

   g9981PortPm15MinIntervalTxLostCells  OBJECT-TYPE
     SYNTAX      HCPerfIntervalCount
     UNITS       "cells"
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "A read-only count of lost ATM cells detected by the peer
       G.Bond/ATM port (e.g., by the GBS-R for the GBS-C) during the
       15-minute performance history interval.

Note that the total number of lost ATM cells is indicated by the g9981PortStatTxLostCells object.

失われたATMセルの総数は、g9981PortStatTxLostCellsオブジェクトによって示されることに注意してください。

       This object is inhibited during Unavailable Seconds (UAS)."
     REFERENCE
       "[TR-159], Section 5.5.2.2"
     ::= { g9981PortPm15MinEntry 4 }

   g9981PortPm15MinIntervalUpDiffDelay  OBJECT-TYPE
     SYNTAX      HCPerfIntervalCount
     UNITS       "0.1 ms"
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "A read-only value specifying the maximum upstream differential
       delay between all operational BCEs in the GBS, measured in
       units of 0.1 ms, during the 15-minute performance history
       interval.

Note that the current max upstream differential delay is indicated by the g9981PortStatMaxUpDiffDelay object.

現在の最大アップストリーム差分遅延は、g9981PortStatMaxUpDiffDelayオブジェクトによって示されることに注意してください。

This object is inhibited during Unavailable Seconds (UAS)."

このオブジェクトは、使用不可秒数（UAS）の間は禁止されています。」

     REFERENCE
       "[TR-159], Section 5.5.2.3"
     ::= { g9981PortPm15MinEntry 5 }

   g9981PortPm15MinIntervalDnDiffDelay  OBJECT-TYPE
     SYNTAX      HCPerfIntervalCount
     UNITS       "0.1 ms"
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "A read-only value specifying the maximum downstream
       differential delay between all operational BCEs in the GBS,
       as perceived by its peer port, measured in units of 0.1 ms,
       during the 15-minute performance history interval.

Note that the current max downstream differential delay is indicated by the g9981PortStatMaxDnDiffDelay object.

現在の最大ダウンストリーム差分遅延は、g9981PortStatMaxDnDiffDelayオブジェクトによって示されることに注意してください。

       This object is inhibited during Unavailable Seconds (UAS)."
     REFERENCE
       "[TR-159], Section 5.5.2.4"
     ::= { g9981PortPm15MinEntry 6 }

   g9981PortPm15MinIntervalValid  OBJECT-TYPE
     SYNTAX      TruthValue
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "A read-only object indicating whether or not this history
       bucket contains valid data.  A valid bucket is reported as
       true(1) and an invalid bucket as false(2).
       If this history bucket is invalid, the BTU MUST NOT produce
       notifications based upon the value of the counters in this
       bucket.
       Note that an implementation may decide not to store invalid
       history buckets in its database.  In such a case, this object
       is not required, as only valid history buckets are available
       while invalid history buckets are simply not in the database.

       This object partially maps to the TR-159 attribute
       aGroupPerf15MinIntervalValid."
     REFERENCE
       "[TR-159], Section 5.5.1.58"
     ::= { g9981PortPm15MinEntry 7 }

-- Port PM history: 1-day buckets

-ポートPM履歴：1日バケット

   g9981PortPm1DayTable OBJECT-TYPE
     SYNTAX      SEQUENCE OF G9981PortPm1DayEntry
     MAX-ACCESS  not-accessible
     STATUS      current
     DESCRIPTION
       "This table contains historical 1-day buckets of Performance
       Monitoring information for a G.Bond/ATM port (a row for each
       1-day interval, up to 7 intervals).
       Entries in this table MUST be maintained in a persistent manner."
     ::= { g9981PM 3 }

   g9981PortPm1DayEntry OBJECT-TYPE
     SYNTAX      G9981PortPm1DayEntry
     MAX-ACCESS  not-accessible
     STATUS      current
     DESCRIPTION
       "An entry in the G.Bond/ATM Port historical 1-day PM table.
       Each entry represents Performance Monitoring data for such a
       port, indexed by the ifIndex, collected during a particular
       1-day interval, indexed by the g9981PortPm1DayIntervalIndex."
     INDEX  { ifIndex, g9981PortPm1DayIntervalIndex }
     ::= { g9981PortPm1DayTable 1 }

   G9981PortPm1DayEntry ::=
     SEQUENCE {
       g9981PortPm1DayIntervalIndex        Unsigned32,
       g9981PortPm1DayIntervalMoniTime     HCPerfTimeElapsed,
       g9981PortPm1DayIntervalRxLostCells  HCPerfIntervalCount,
       g9981PortPm1DayIntervalTxLostCells  HCPerfIntervalCount,
       g9981PortPm1DayIntervalUpDiffDelay  HCPerfIntervalCount,
       g9981PortPm1DayIntervalDnDiffDelay  HCPerfIntervalCount,
       g9981PortPm1DayIntervalValid        TruthValue
     }

   g9981PortPm1DayIntervalIndex  OBJECT-TYPE
     SYNTAX      Unsigned32 (1..7)
     MAX-ACCESS  not-accessible
     STATUS      current
     DESCRIPTION
       "Performance data interval number.  1 is the most recent previous
       interval; interval 7 is 24 hours ago.
       Intervals 2..7 are OPTIONAL.

This object partially maps to the TR-159 attribute aGroupPerf1DayIntervalNumber."

このオブジェクトは、TR-159属性aGroupPerf1DayIntervalNumberに部分的にマッピングされます。

     REFERENCE
       "[TR-159], Section 5.5.1.62"
     ::= { g9981PortPm1DayEntry 1 }

   g9981PortPm1DayIntervalMoniTime  OBJECT-TYPE
     SYNTAX      HCPerfTimeElapsed
     UNITS       "seconds"
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "A count of seconds over which the performance data was actually
       monitored.  This value will be the same as the interval duration
       (86400 seconds), except in a situation where performance data
       could not be collected for any reason.

       This object partially maps to the TR-159 attribute
       aGroupPerf1DayIntervalMoniSecs."
     REFERENCE
       "[TR-159], Section 5.5.1.64"
     ::= { g9981PortPm1DayEntry 2 }

   g9981PortPm1DayIntervalRxLostCells  OBJECT-TYPE
     SYNTAX      HCPerfIntervalCount
     UNITS       "cells"
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "A count of lost ATM cells detected by the G.Bond/ATM port
       (e.g., the GBS-C) during the 1-day performance history interval.

       This object is inhibited during Severely Errored Seconds (SES)
       and Unavailable Seconds (UAS)."
     ::= { g9981PortPm1DayEntry 3 }

   g9981PortPm1DayIntervalTxLostCells  OBJECT-TYPE
     SYNTAX      HCPerfIntervalCount
     UNITS       "cells"
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "A count of lost ATM cells detected by the peer G.Bond/ATM port
       (e.g., by the GBS-R for the GBS-C) during the 1-day performance
       history interval.

       This object is inhibited during Unavailable Seconds (UAS)."
     ::= { g9981PortPm1DayEntry 4 }

   g9981PortPm1DayIntervalUpDiffDelay  OBJECT-TYPE
     SYNTAX      HCPerfIntervalCount
     UNITS       "0.1 ms"
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "A read-only value specifying the maximum upstream differential
       delay between all operational BCEs in the GBS-C, measured in
       units of 0.1 ms, during the 1-day performance history interval.

       This object is inhibited during Unavailable Seconds (UAS)."
     ::= { g9981PortPm1DayEntry 5 }

   g9981PortPm1DayIntervalDnDiffDelay  OBJECT-TYPE
     SYNTAX      HCPerfIntervalCount
     UNITS       "0.1 ms"
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "A read-only value specifying the maximum downstream
       differential delay between all operational BCEs in the GBS-C,
       measured in units of 0.1 ms, during the 1-day performance
       history interval.

       This object is inhibited during Unavailable Seconds (UAS)."
     ::= { g9981PortPm1DayEntry 6 }

   g9981PortPm1DayIntervalValid  OBJECT-TYPE
     SYNTAX      TruthValue
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
       "A read-only object indicating whether or not this history
       bucket contains valid data.  A valid bucket is reported as
       true(1) and an invalid bucket as false(2).
       If this history bucket is invalid, the BTU MUST NOT produce
       notifications based upon the value of the counters in this
       bucket.
       Note that an implementation may decide not to store invalid
       history buckets in its database.  In such a case, this object
       is not required, as only valid history buckets are available
       while invalid history buckets are simply not in the database.

       This object partially maps to the TR-159 attribute
       aGroupPerf1DayIntervalValid."
     REFERENCE
       "[TR-159], Section 5.5.1.63"
     ::= { g9981PortPm1DayEntry 7 }

-- -- Conformance Statements --

--適合宣言-

   g9981Groups      OBJECT IDENTIFIER
     ::= { g9981Conformance 1 }

   g9981Compliances OBJECT IDENTIFIER
     ::= { g9981Conformance 2 }

-- Object Groups

-オブジェクトグループ

   g9981BasicGroup OBJECT-GROUP
     OBJECTS {
       g9981PortStatRxLostCells,
       g9981PortStatTxLostCells,
       g9981PortStatMaxUpDiffDelay,
       g9981PortStatMaxDnDiffDelay
     }
     STATUS      current
     DESCRIPTION
       "A collection of objects representing management information
       for a G.Bond/ATM port."
     ::= { g9981Groups 1 }

   g9981AlarmConfGroup OBJECT-GROUP
     OBJECTS {
       g9981PortConfUpDiffDelayTolerance,
       g9981PortConfDnDiffDelayTolerance,
       g9981PortConfDiffDelayToleranceExceededEnable
     }
     STATUS      current
     DESCRIPTION
       "A collection of objects required for configuration of alarm
       thresholds and notifications in G.Bond/ATM ports."
     ::= { g9981Groups 2 }

   g9981NotificationGroup NOTIFICATION-GROUP
     NOTIFICATIONS {
       g9981UpDiffDelayToleranceExceeded,
       g9981DnDiffDelayToleranceExceeded
     }
     STATUS      current
     DESCRIPTION
       "This group supports notifications of significant conditions
       associated with G.Bond/ATM ports."
     ::= { g9981Groups 3 }

   g9981PerfCurrGroup OBJECT-GROUP
     OBJECTS {
       g9981PortPmCur15MinValidIntervals,
       g9981PortPmCur15MinInvalidIntervals,
       g9981PortPmCur15MinTimeElapsed,
       g9981PortPmCur15MinRxLostCells,
       g9981PortPmCur15MinTxLostCells,
       g9981PortPmCur15MinUpDiffDelay,
       g9981PortPmCur15MinDnDiffDelay,
       g9981PortPmCur1DayValidIntervals,
       g9981PortPmCur1DayInvalidIntervals,
       g9981PortPmCur1DayTimeElapsed,
       g9981PortPmCur1DayRxLostCells,
       g9981PortPmCur1DayTxLostCells,
       g9981PortPmCur1DayUpDiffDelay,
       g9981PortPmCur1DayDnDiffDelay
     }
     STATUS      current
     DESCRIPTION
       "A collection of objects supporting OPTIONAL current Performance
       Monitoring information for G.Bond/ATM ports."
     ::= { g9981Groups 4 }

   g9981Perf15MinGroup OBJECT-GROUP
     OBJECTS {
       g9981PortPm15MinIntervalMoniTime,
       g9981PortPm15MinIntervalRxLostCells,
       g9981PortPm15MinIntervalTxLostCells,
       g9981PortPm15MinIntervalUpDiffDelay,
       g9981PortPm15MinIntervalDnDiffDelay,
       g9981PortPm15MinIntervalValid
     }
     STATUS      current
     DESCRIPTION
       "A collection of objects supporting OPTIONAL historical
       Performance Monitoring information for G.Bond/ATM ports, during
       previous 15-minute intervals."
     ::= { g9981Groups 5 }

   g9981Perf1DayGroup OBJECT-GROUP
     OBJECTS {
       g9981PortPm1DayIntervalMoniTime,
       g9981PortPm1DayIntervalRxLostCells,
       g9981PortPm1DayIntervalTxLostCells,
       g9981PortPm1DayIntervalUpDiffDelay,
       g9981PortPm1DayIntervalDnDiffDelay,
       g9981PortPm1DayIntervalValid
     }
     STATUS      current
     DESCRIPTION
       "A collection of objects supporting OPTIONAL historical
       Performance Monitoring information for G.Bond/ATM ports, during
       previous 1-day intervals."
     ::= { g9981Groups 6 }

-- Compliance Statements

-コンプライアンスステートメント

g9981Compliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for G.Bond/ATM interfaces. Compliance with the following external compliance statements is REQUIRED:

g9981Compliance MODULE-COMPLIANCE STATUS current DESCRIPTION "G.Bond/ATMインターフェースのコンプライアンスステートメント。次の外部コンプライアンスステートメントへの準拠が必要です。

       MIB Module             Compliance Statement
       ----------             --------------------
       IF-MIB                 ifCompliance3
       GBOND-MIB              gBondCompliance"

     MODULE  -- this module
       MANDATORY-GROUPS {
         g9981BasicGroup,
         g9981AlarmConfGroup,
         g9981NotificationGroup
       }

GROUP g9981PerfCurrGroup DESCRIPTION "Support for this group is only required for implementations supporting Performance Monitoring."

グループg9981PerfCurrGroup説明「このグループのサポートは、パフォーマンスモニタリングをサポートする実装にのみ必要です。」

GROUP g9981Perf15MinGroup DESCRIPTION "Support for this group is only required for implementations supporting historical Performance Monitoring."

グループg9981Perf15MinGroup説明「このグループのサポートは、履歴パフォーマンスモニタリングをサポートする実装にのみ必要です。」

GROUP g9981Perf1DayGroup DESCRIPTION "Support for this group is only required for implementations supporting 1-day historical Performance Monitoring."

グループg9981Perf1DayGroup説明「このグループのサポートは、1日の履歴パフォーマンスモニタリングをサポートする実装にのみ必要です。」

     ::= { g9981Compliances 1 }
END

7. Security Considerations

7. セキュリティに関する考慮事項

There are a number of managed objects defined in this MIB module with a MAX-ACCESS clause of read-write. 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 are the tables and objects and their sensitivity/vulnerability:

このMIBモジュールには、読み取り/書き込みのMAX-ACCESS句を使用して定義された管理対象オブジェクトがいくつかあります。このようなオブジェクトは、一部のネットワーク環境では機密または脆弱であると見なされる場合があります。適切に保護されていない非セキュア環境でのSET操作のサポートは、ネットワーク操作に悪影響を及ぼす可能性があります。これらは、テーブルとオブジェクト、およびそれらの機密性/脆弱性です。

o Changing of g9981PortConfTable configuration parameters MAY lead to a potential Service Level Agreement (SLA) breach, for example, if a traffic delay is increased as a result of the higher delay tolerance (increased g9981PortConfUpDiffDelayTolerance and/or g9981PortConfDnDiffDelayTolerance), or the differential delay tolerance notifications are disabled by manipulating the g9981PortConfDiffDelayToleranceExceededEnable parameter.

o g9981PortConfTable構成パラメーターを変更すると、たとえば、遅延許容度が高くなった結果（g9981PortConfUpDiffDelayToleranceやg9981PortConfDnDiffDelayToleranceが増加した結果）、または遅延差の許容差通知によってトラフィック遅延が増加した場合に、潜在的なサービスレベルアグリーメント（SLA）違反が発生する可能性があります (MAY)。 g9981PortConfDiffDelayToleranceExceededEnableパラメータを操作して無効にします。

Some of the readable objects in this MIB module (i.e., objects with a MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments since, collectively, they provide information about the performance of network interfaces and can reveal some aspects of their configuration.

このMIBモジュール内の一部の読み取り可能なオブジェクト（つまり、アクセス不可以外のMAX-ACCESSを持つオブジェクト）は、ネットワークインターフェイスのパフォーマンスに関する情報を提供し、明らかにできるため、一部のネットワーク環境では機密または脆弱であると見なされる場合がありますそれらの構成のいくつかの側面。

It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP.

したがって、これらのオブジェクトへのGETおよび/またはNOTIFYアクセスを制御し、SNMP経由でネットワーク経由で送信するときにこれらのオブジェクトの値を暗号化することも重要です。

SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPsec), 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.

SNMPv3より前のSNMPバージョンには、十分なセキュリティが含まれていませんでした。ネットワーク自体が（たとえばIPsecを使用して）安全であっても、安全なネットワーク上の誰がこのMIBモジュール内のオブジェクトにアクセスしてGET/SET（読み取り/変更/作成/削除）できるかは制御できません。

Implementations SHOULD provide the security features described by the SNMPv3 framework (see [RFC3410]), and implementations claiming compliance to the SNMPv3 standard MUST include full support for authentication and privacy via the User-based Security Model (USM) [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations MAY also provide support for the Transport Security Model (TSM) [RFC5591] in combination with a secure transport such as SSH [RFC5592] or TLS/DTLS [RFC6353].

実装は、SNMPv3 framework（[RFC3410]参照）で説明されるセキュリティ機能を提供すべきです (SHOULD)。SNMPv3標準への準拠を主張する実装は、AES cipher algorithm [RFC3826]を用いたUser-based Security Model (USM) [RFC3414]による認証およびプライバシーを完全にサポートしなければなりません (MUST)。実装は、SSH [RFC5592]またはTLS/DTLS [RFC6353]などの安全なトランスポートと組み合わせてTransport Security Model (TSM) [RFC5591]もサポートしてもよい (MAY)。

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（変更/ create / delete）それら。

8. IANA Considerations

8. IANAに関する考慮事項

IANA has assigned 208 as the object identifier for g9981MIB MODULE-IDENTITY in the MIB-2 transmission sub-tree <http://www.iana.org/>.

IANAは、MIB-2送信サブツリー<http://www.iana.org/>のg9981MIB MODULE-IDENTITYのオブジェクト識別子として208を割り当てています。

9. Acknowledgments

9. 謝辞

This document was produced by the [ADSLMIB] working group.

このドキュメントは、[ADSLMIB]ワーキンググループによって作成されました。

Special thanks to Dan Romascanu for his meticulous review of this text.

このテキストの綿密なレビューを行ったDan Romascanuに特に感謝します。

10. References

10. 参考文献

10.1. Normative References

10.1. 引用文献

[G.998.1] ITU-T, "ATM-based multi-pair bonding", ITU-T Recommendation G.998.1, January 2005, <http://www.itu.int/rec/T-REC-G.998.1/en>.

[G.998.1] ITU-T、「ATMベースのマルチペアボンディング」、ITU-T勧告G.998.1、2005年1月、<http://www.itu.int/rec/T-REC-G.998.1/en>。

[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月。

[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.

[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Structure of Management Information Version 2（SMIv2）"、STD 58、RFC 2578、April 1999。

[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.

[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Textual Conventions for SMIv2"、STD 58、RFC 2579、April 1999。

[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.

[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder、「SMIv2の適合宣言」、STD 58、RFC 2580、1999年4月。

[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000.

[RFC2863] McCloghrie, K. and F. Kastenholz、「The Interfaces Group MIB」、RFC 2863、2000年6月。

[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", STD 62, RFC 3414, December 2002.

[RFC3414] Blumenthal, U. and B. Wijnen、「Simple Network Management Protocol（SNMPv3）バージョン3のユーザーベースのセキュリティモデル（USM）」、STD 62、RFC 3414、2002年12月。

[RFC3705] Ray, B. and R. Abbi, "High Capacity Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals", RFC 3705, February 2004.

[RFC3705] Ray, B. and R. Abbi、「15分の間隔に基づくパフォーマンス履歴を使用したMIBモジュールの大容量テキスト表記」、RFC 3705、2004年2月。

[RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security Model", RFC 3826, June 2004.

[RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie、「SNMP User-based Security ModelのAdvanced Encryption Standard（AES）暗号アルゴリズム」、RFC 3826、2004年6月。

[RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model for the Simple Network Management Protocol (SNMP)", RFC 5591, June 2009.

[RFC5591] Harrington, D. and W. Hardaker、「簡易ネットワーク管理プロトコル（SNMP）のトランスポートセキュリティモデル」、RFC 5591、2009年6月。

[RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure Shell Transport Model for the Simple Network Management Protocol (SNMP)", RFC 5592, June 2009.

[RFC5592] Harrington, D., Salowey, J., and W. Hardaker、「Secure Network Transport Model for the Simple Network Management Protocol（SNMP）」、RFC 5592、2009年6月。

[RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)", RFC 6353, July 2011.

[RFC6353] Hardaker, W.、「簡易ネットワーク管理プロトコル（SNMP）のトランスポート層セキュリティ（TLS）トランスポートモデル」、RFC 6353、2011年7月。

[RFC6765] Beili, E. and M. Morgenstern, "xDSL Multi-Pair Bonding (G.Bond) MIB", RFC 6765, February 2013.

[RFC6765] Beili, E. and M. Morgenstern、「xDSL Multi-Pair Bonding（G.Bond）MIB」、RFC 6765、2013年2月。

[TR-159] Beili, E. and M. Morgenstern, "Management Framework for xDSL Bonding", Broadband Forum Technical Report TR-159, December 2008, <http://www.broadband-forum.org/technical/ download/TR-159.pdf>.

[TR-159] Beili, E. and M. Morgenstern、「xDSLボンディングの管理フレームワーク」、ブロードバンドフォーラムテクニカルレポートTR-159、2008年12月、<http://www.broadband-forum.org/technical/download/TR-159.pdf>。

10.2. Informative References

10.2. 参考引用

[ADSLMIB] IETF, "ADSL MIB (adslmib) Charter", <http://datatracker.ietf.org/wg/adslmib/charter/>.

[ADSLMIB] IETF、「ADSL MIB（adslmib）Charter」、<http://datatracker.ietf.org/wg/adslmib/charter/>。

[AF-PHY-0086] ATM Forum, "Inverse Multiplexing for ATM (IMA) Specification Version 1.1", ATM Forum specification af-phy-0086.001, March 1999, <http://www.broadband-forum.org/ ftp/pub/approved-specs/af-phy-0086.001.pdf>.

[AF-PHY-0086] ATM Forum、「ATM（IMA）仕様の逆多重化バージョン1.1」、ATMフォーラム仕様af-phy-0086.001、1999年3月、<http://www.broadband-forum.org/ftp/pub/approved-specs/af-phy-0086.001.pdf>。

[RFC2515] Tesink, K., "Definitions of Managed Objects for ATM Management", RFC 2515, February 1999.

[RFC2515] Tesink, K.、「Definions of Managed Objects for ATM Management」、RFC 2515、1999年2月。

[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., and B. Stewart、「Introduction and Applicability Statements for Internet-Standard Management Framework」、RFC 3410、2002年12月。

[RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals", RFC 3593, September 2003.

[RFC3593] Tesink, K.、「15分の間隔に基づくパフォーマンス履歴を使用するMIBモジュールのテキスト表記法」、RFC 3593、2003年9月。

[RFC4181] Heard, C., "Guidelines for Authors and Reviewers of MIB Documents", BCP 111, RFC 4181, September 2005.

[RFC4181] Heard, C.、「MIBドキュメントの作成者およびレビュー担当者向けガイドライン」、BCP 111、RFC 4181、2005年9月。

Author's Address

著者のアドレス

Edward Beili Actelis Networks 25 Bazel St. Petach-Tikva 49103 Israel

Edward Beili Actelis Networks 25 Bazel St. Petach-Tikva 49103イスラエル

   Phone: +972-3-924-3491
   EMail: edward.beili@actelis.com