[要約] RFC 2932はIPv4マルチキャストルーティングMIBに関する規格であり、マルチキャストルーティングの管理情報ベースを定義しています。このRFCの目的は、IPv4マルチキャストルーティングの監視と制御を容易にするための標準化を提供することです。
Network Working Group K. McCloghrie
Request for Comments: 2932 cisco Systems
Category: Standards Track D. Farinacci
Procket Networks
D. Thaler
Microsoft
October 2000
IPv4 Multicast Routing MIB
IPv4マルチキャストルーティングMIB
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 (2000). All Rights Reserved.
Copyright（c）The Internet Society（2000）。無断転載を禁じます。
Abstract
概要
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 managed objects used for managing IP Multicast Routing for IPv4, independent of the specific multicast routing protocol in use.
このメモは、インターネットコミュニティのネットワーク管理プロトコルで使用するための管理情報ベース（MIB）の一部を定義します。特に、使用中の特定のマルチキャストルーティングプロトコルとは無関係に、IPv4のIPマルチキャストルーティングの管理に使用される管理オブジェクトについて説明します。
Table of Contents
目次
1 Introduction ................................................. 2
2 The SNMP Management Framework ................................ 2
3 Overview ..................................................... 3
4 Definitions .................................................. 4
5 IANA Considerations .......................................... 22
6 Security Considerations ...................................... 22
7 Intellectual Property Notice ................................. 23
8 Acknowledgements ............................................. 23
9 Authors' Addresses ........................................... 24
10 References ................................................... 25
11 Full Copyright Statement ..................................... 27
This MIB describes objects used for managing IP Multicast Routing [16], independent of the specific multicast routing protocol [17-21] in use. Managed objects specific to particular multicast routing protocols are specified elsewhere. Similarly, this MIB does not support management of multicast routing for other address families, including IPv6. Such management may be supported by other MIBs.
このMIBは、使用中の特定のマルチキャストルーティングプロトコル[17-21]とは無関係に、IPマルチキャストルーティング[16]の管理に使用されるオブジェクトについて説明しています。特定のマルチキャストルーティングプロトコルに固有の管理オブジェクトは、他の場所で指定されています。同様に、このMIBは、IPv6を含む他のアドレスファミリのマルチキャストルーティングの管理をサポートしていません。このような管理は、他のMIBによってサポートされる場合があります。
The SNMP Management Framework presently consists of five major components:
SNMP管理フレームワークは現在、5つの主要なコンポーネントで構成されています。
o An overall architecture, described in RFC 2571 [1].
o RFC 2571 [1]に記載されている全体的なアーキテクチャ。
o Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and described in STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The second version, called SMIv2, is described in STD 58, RFC 2578 [5], STD 58, RFC 2579 [6] and STD 58, RFC 2580 [7].
o 管理を目的としたオブジェクトとイベントを説明および名前を付けるためのメカニズム。この管理情報構造（SMI）の最初のバージョンはSMIV1と呼ばれ、STD 16、RFC 1155 [2]、STD 16、RFC 1212 [3]およびRFC 1215 [4]で説明されています。SMIV2と呼ばれる2番目のバージョンは、STD 58、RFC 2578 [5]、STD 58、RFC 2579 [6]およびSTD 58、RFC 2580 [7]に記載されています。
o Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in STD 15, RFC 1157 [8]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12].
o 管理情報を転送するためのメッセージプロトコル。SNMPメッセージプロトコルの最初のバージョンはSNMPV1と呼ばれ、STD 15、RFC 1157 [8]で説明されています。インターネット標準トラックプロトコルではないSNMPメッセージプロトコルの2番目のバージョンは、SNMPV2Cと呼ばれ、RFC 1901 [9]およびRFC 1906 [10]で説明されています。メッセージプロトコルの3番目のバージョンはSNMPV3と呼ばれ、RFC 1906 [10]、RFC 2572 [11]、およびRFC 2574 [12]で説明されています。
o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in STD 15, RFC 1157 [8]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [13].
o 管理情報にアクセスするためのプロトコル操作。プロトコル操作の最初のセットと関連するPDU形式は、STD 15、RFC 1157 [8]で説明されています。プロトコル操作の2番目のセットと関連するPDU形式は、RFC 1905 [13]で説明されています。
o A set of fundamental applications described in RFC 2573 [14] and the view-based access control mechanism described in RFC 2575 [15].
o RFC 2573 [14]に記載されている一連の基本的なアプリケーションと、RFC 2575 [15]で説明されているビューベースのアクセス制御メカニズム。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the mechanisms defined in the SMI.
管理されたオブジェクトは、管理情報ベースまたはMIBと呼ばれる仮想情報ストアからアクセスされます。MIBのオブジェクトは、SMIで定義されたメカニズムを使用して定義されます。
This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no translation is possible (use of Counter64). Some machine readable information in SMIv2 will be converted into textual descriptions in SMIv1 during the translation process. However, this loss of machine readable information is not considered to change the semantics of the MIB.
このメモは、SMIV2に準拠したMIBモジュールを指定します。SMIV1に準拠するMIBは、適切な翻訳を通じて生成できます。結果の翻訳されたMIBは、翻訳が不可能であるためオブジェクトまたはイベントが省略されている場合を除き、意味的に同等でなければなりません（Counter64の使用）。SMIV2の一部の機械読み取り可能な情報は、翻訳プロセス中にSMIV1のテキスト説明に変換されます。ただし、この機械の読み取り可能な情報の損失は、MIBのセマンティクスを変更するとは見なされません。
This MIB module contains one scalar and five tables. The tables are:
このMIBモジュールには、1つのスカラーと5つのテーブルが含まれています。テーブルは次のとおりです。
(1) the IP Multicast Route Table containing multicast routing information for IP datagrams sent by particular sources to the IP multicast groups known to a router.
(1) 特定のソースから送信されたIPデータグラムのマルチキャストルーティング情報を含むIPマルチキャストルートテーブルは、ルーターに知られているIPマルチキャストグループに送信されました。
(2) the IP Multicast Routing Next Hop Table containing information on the next-hops for the routing IP multicast datagrams. Each entry is one of a list of next-hops on outgoing interfaces for particular sources sending to a particular multicast group address.
(2) ルーティングIPマルチキャストデータグラムの次のホップに関する情報を含むIPマルチキャストルーティング次のホップテーブル。各エントリは、特定のマルチキャストグループアドレスに送信する特定のソースの発信インターフェイスに関する次のホップのリストの1つです。
(3) the IP Multicast Routing Interface Table containing multicast routing information specific to interfaces.
(3) インターフェイスに固有のマルチキャストルーティング情報を含むIPマルチキャストルーティングインターフェイステーブル。
(4) the IP Multicast Scope Boundary Table containing the boundaries configured for multicast scopes [22].
(4) マルチキャストスコープ用に構成された境界を含むIPマルチキャストスコープ境界テーブル[22]。
(5) the IP Multicast Scope Name Table containing human-readable names of multicast scope.
(5) マルチキャストスコープのヒューマン可読名を含むIPマルチキャストスコープ名テーブル。
IPMROUTE-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, mib-2,
Integer32, Counter32, Counter64, Gauge32,
IpAddress, TimeTicks FROM SNMPv2-SMI
RowStatus, TEXTUAL-CONVENTION,
TruthValue FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
SnmpAdminString FROM SNMP-FRAMEWORK-MIB
InterfaceIndexOrZero,
InterfaceIndex FROM IF-MIB
IANAipRouteProtocol,
IANAipMRouteProtocol FROM IANA-RTPROTO-MIB;
ipMRouteStdMIB MODULE-IDENTITY LAST-UPDATED "200009220000Z" -- September 22, 2000 ORGANIZATION "IETF IDMR Working Group" CONTACT-INFO " Dave Thaler Microsoft Corporation One Microsoft Way Redmond, WA 98052-6399 US
IPMROUTESTDMIBモジュールIDULE INDITITY LATS-UPDATED "200009220000Z" - 2000年9月22日「IETF IDMRワーキンググループ "連絡先INFO" Dave Thaler Microsoft Corporation One Microsoft Way Redmond、WA 98052-6399 US US US
Phone: +1 425 703 8835
EMail: dthaler@microsoft.com"
DESCRIPTION
"The MIB module for management of IP Multicast routing, but
independent of the specific multicast routing protocol in
use."
REVISION "200009220000Z" -- September 22, 2000
DESCRIPTION
"Initial version, published as RFC 2932."
::= { mib-2 83 }
-- Textual Conventions
- テキストの慣習
LanguageTag ::= TEXTUAL-CONVENTION
DISPLAY-HINT "100a" STATUS current DESCRIPTION "An RFC 1766-style language tag, with all alphabetic characters converted to lowercase. This restriction is intended to make the lexical ordering imposed by SNMP useful when applied to language tags. Note that it is theoretically possible for a valid language tag to exceed the allowed length of this syntax, and thus be impossible to represent with this syntax. Sampling of language tags in current use on the Internet suggests that this limit does not pose a serious problem in practice." SYNTAX OCTET STRING (SIZE (1..100))
ディスプレイヒント「100A」ステータス現在の説明 "RFC 1766スタイルの言語タグ、すべてのアルファベット文字が小文字に変換されます。この制限は、SNMPによって課される語彙順序を言語タグに適用すると有用にすることを目的としています。有効な言語タグがこの構文の許可された長さを超えているため、この構文を表すことは不可能です。インターネット上での現在の使用における言語タグのサンプリングは、この制限が実際に深刻な問題をもたらさないことを示唆しています。」構文オクテット文字列（サイズ（1..100））
-- Top-level structure of the MIB
- MIBのトップレベル構造
ipMRouteMIBObjects OBJECT IDENTIFIER ::= { ipMRouteStdMIB 1 }
ipMRoute OBJECT IDENTIFIER ::= { ipMRouteMIBObjects 1 }
-- the IP Multicast Routing MIB-Group
--
-- a collection of objects providing information about
-- IP Multicast Groups
ipMRouteEnable OBJECT-TYPE
SYNTAX INTEGER { enabled(1), disabled(2) }
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The enabled status of IP Multicast routing on this router."
::= { ipMRoute 1 }
ipMRouteEntryCount OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of rows in the ipMRouteTable. This can be used
to monitor the multicast routing table size."
::= { ipMRoute 7 }
ipMRouteTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpMRouteEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The (conceptual) table containing multicast routing
information for IP datagrams sent by particular sources to
the IP multicast groups known to this router."
::= { ipMRoute 2 }
ipMRouteEntry OBJECT-TYPE
SYNTAX IpMRouteEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (conceptual row) containing the multicast routing
information for IP datagrams from a particular source and
addressed to a particular IP multicast group address.
Discontinuities in counters in this entry can be detected by
observing the value of ipMRouteUpTime."
INDEX { ipMRouteGroup,
ipMRouteSource,
ipMRouteSourceMask }
::= { ipMRouteTable 1 }
IpMRouteEntry ::= SEQUENCE {
ipMRouteGroup IpAddress,
ipMRouteSource IpAddress,
ipMRouteSourceMask IpAddress,
ipMRouteUpstreamNeighbor IpAddress,
ipMRouteInIfIndex InterfaceIndexOrZero,
ipMRouteUpTime TimeTicks,
ipMRouteExpiryTime TimeTicks,
ipMRoutePkts Counter32,
ipMRouteDifferentInIfPackets Counter32,
ipMRouteOctets Counter32,
ipMRouteProtocol IANAipMRouteProtocol,
ipMRouteRtProto IANAipRouteProtocol,
ipMRouteRtAddress IpAddress,
ipMRouteRtMask IpAddress,
ipMRouteRtType INTEGER,
ipMRouteHCOctets Counter64
}
ipMRouteGroup OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The IP multicast group address for which this entry
contains multicast routing information."
::= { ipMRouteEntry 1 }
ipMRouteSource OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION
ipmroutesource object-type構文ipaddress max-accessアクセス不可能なステータス現在の説明
"The network address which when combined with the
corresponding value of ipMRouteSourceMask identifies the
sources for which this entry contains multicast routing
information."
::= { ipMRouteEntry 2 }
ipMRouteSourceMask OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The network mask which when combined with the corresponding
value of ipMRouteSource identifies the sources for which
this entry contains multicast routing information."
::= { ipMRouteEntry 3 }
ipMRouteUpstreamNeighbor OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The address of the upstream neighbor (e.g., RPF neighbor)
from which IP datagrams from these sources to this multicast
address are received, or 0.0.0.0 if the upstream neighbor is
unknown (e.g., in CBT)."
::= { ipMRouteEntry 4 }
ipMRouteInIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of ifIndex for the interface on which IP
datagrams sent by these sources to this multicast address
are received. A value of 0 indicates that datagrams are not
subject to an incoming interface check, but may be accepted
on multiple interfaces (e.g., in CBT)."
::= { ipMRouteEntry 5 }
ipMRouteUpTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time since the multicast routing information
represented by this entry was learned by the router."
::= { ipMRouteEntry 6 }
ipMRouteExpiryTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The minimum amount of time remaining before this entry will
be aged out. The value 0 indicates that the entry is not
subject to aging."
::= { ipMRouteEntry 7 }
ipMRoutePkts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets which this router has received from
these sources and addressed to this multicast group
address."
::= { ipMRouteEntry 8 }
ipMRouteDifferentInIfPackets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets which this router has received from
these sources and addressed to this multicast group address,
which were dropped because they were not received on the
interface indicated by ipMRouteInIfIndex. Packets which are
not subject to an incoming interface check (e.g., using CBT)
are not counted."
::= { ipMRouteEntry 9 }
ipMRouteOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets contained in IP datagrams which were
received from these sources and addressed to this multicast
group address, and which were forwarded by this router."
::= { ipMRouteEntry 10 }
ipMRouteProtocol OBJECT-TYPE SYNTAX IANAipMRouteProtocol MAX-ACCESS read-only STATUS current DESCRIPTION
IPMROUTEPROTOCOLオブジェクトタイプの構文IANAIPMROUTEPROTOCOL MAX-ACCESS READ-ONLYステータス現在の説明
"The multicast routing protocol via which this multicast
forwarding entry was learned."
::= { ipMRouteEntry 11 }
ipMRouteRtProto OBJECT-TYPE
SYNTAX IANAipRouteProtocol
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The routing mechanism via which the route used to find the
upstream or parent interface for this multicast forwarding
entry was learned. Inclusion of values for routing
protocols is not intended to imply that those protocols need
be supported."
::= { ipMRouteEntry 12 }
ipMRouteRtAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The address portion of the route used to find the upstream
or parent interface for this multicast forwarding entry."
::= { ipMRouteEntry 13 }
ipMRouteRtMask OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The mask associated with the route used to find the upstream
or parent interface for this multicast forwarding entry."
::= { ipMRouteEntry 14 }
ipMRouteRtType OBJECT-TYPE
SYNTAX INTEGER {
unicast (1), -- Unicast route used in multicast RIB
multicast (2) -- Multicast route
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The reason the given route was placed in the (logical)
multicast Routing Information Base (RIB). A value of
unicast means that the route would normally be placed only
in the unicast RIB, but was placed in the multicast RIB
(instead or in addition) due to local configuration, such as
when running PIM over RIP. A value of multicast means that
the route was explicitly added to the multicast RIB by the
routing protocol, such as DVMRP or Multiprotocol BGP."
::= { ipMRouteEntry 15 }
ipMRouteHCOctets OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets contained in IP datagrams which were
received from these sources and addressed to this multicast
group address, and which were forwarded by this router.
This object is a 64-bit version of ipMRouteOctets."
::= { ipMRouteEntry 16 }
-- -- The IP Multicast Routing Next Hop Table --
--- IPマルチキャストルーティング次のホップテーブル -
ipMRouteNextHopTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpMRouteNextHopEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The (conceptual) table containing information on the next-
hops on outgoing interfaces for routing IP multicast
datagrams. Each entry is one of a list of next-hops on
outgoing interfaces for particular sources sending to a
particular multicast group address."
::= { ipMRoute 3 }
ipMRouteNextHopEntry OBJECT-TYPE
SYNTAX IpMRouteNextHopEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (conceptual row) in the list of next-hops on
outgoing interfaces to which IP multicast datagrams from
particular sources to a IP multicast group address are
routed. Discontinuities in counters in this entry can be
detected by observing the value of ipMRouteUpTime."
INDEX { ipMRouteNextHopGroup, ipMRouteNextHopSource,
ipMRouteNextHopSourceMask, ipMRouteNextHopIfIndex,
ipMRouteNextHopAddress }
::= { ipMRouteNextHopTable 1 }
IpMRouteNextHopEntry ::= SEQUENCE {
ipMRouteNextHopGroup IpAddress,
ipMRouteNextHopSource IpAddress,
ipMRouteNextHopSourceMask IpAddress,
ipMRouteNextHopIfIndex InterfaceIndex,
ipMRouteNextHopAddress IpAddress,
ipMRouteNextHopState INTEGER,
ipMRouteNextHopUpTime TimeTicks,
ipMRouteNextHopExpiryTime TimeTicks,
ipMRouteNextHopClosestMemberHops Integer32,
ipMRouteNextHopProtocol IANAipMRouteProtocol,
ipMRouteNextHopPkts Counter32
}
ipMRouteNextHopGroup OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The IP multicast group for which this entry specifies a
next-hop on an outgoing interface."
::= { ipMRouteNextHopEntry 1 }
ipMRouteNextHopSource OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The network address which when combined with the
corresponding value of ipMRouteNextHopSourceMask identifies
the sources for which this entry specifies a next-hop on an
outgoing interface."
::= { ipMRouteNextHopEntry 2 }
ipMRouteNextHopSourceMask OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The network mask which when combined with the corresponding
value of ipMRouteNextHopSource identifies the sources for
which this entry specifies a next-hop on an outgoing
interface."
::= { ipMRouteNextHopEntry 3 }
ipMRouteNextHopIfIndex OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION
ipmroutenexthopifindex object-type interfaceindex max-accessアクセス不可能なステータス現在の説明
"The ifIndex value of the interface for the outgoing
interface for this next-hop."
::= { ipMRouteNextHopEntry 4 }
ipMRouteNextHopAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The address of the next-hop specific to this entry. For
most interfaces, this is identical to ipMRouteNextHopGroup.
NBMA interfaces, however, may have multiple next-hop
addresses out a single outgoing interface."
::= { ipMRouteNextHopEntry 5 }
ipMRouteNextHopState OBJECT-TYPE
SYNTAX INTEGER { pruned(1), forwarding(2) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An indication of whether the outgoing interface and next-
hop represented by this entry is currently being used to
forward IP datagrams. The value 'forwarding' indicates it
is currently being used; the value 'pruned' indicates it is
not."
::= { ipMRouteNextHopEntry 6 }
ipMRouteNextHopUpTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time since the multicast routing information
represented by this entry was learned by the router."
::= { ipMRouteNextHopEntry 7 }
ipMRouteNextHopExpiryTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The minimum amount of time remaining before this entry will
be aged out. If ipMRouteNextHopState is pruned(1), the
remaining time until the prune expires and the state reverts
to forwarding(2). Otherwise, the remaining time until this
entry is removed from the table. The time remaining may be
copied from ipMRouteExpiryTime if the protocol in use for
this entry does not specify next-hop timers. The value 0
indicates that the entry is not subject to aging."
::= { ipMRouteNextHopEntry 8 }
ipMRouteNextHopClosestMemberHops OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The minimum number of hops between this router and any
member of this IP multicast group reached via this next-hop
on this outgoing interface. Any IP multicast datagrams for
the group which have a TTL less than this number of hops
will not be forwarded to this next-hop."
::= { ipMRouteNextHopEntry 9 }
ipMRouteNextHopProtocol OBJECT-TYPE
SYNTAX IANAipMRouteProtocol
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The routing mechanism via which this next-hop was learned."
::= { ipMRouteNextHopEntry 10 }
ipMRouteNextHopPkts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets which have been forwarded using this
route."
::= { ipMRouteNextHopEntry 11 }
-- -- The Multicast Routing Interface Table --
---マルチキャストルーティングインターフェイステーブル -
ipMRouteInterfaceTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpMRouteInterfaceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The (conceptual) table containing multicast routing
information specific to interfaces."
::= { ipMRoute 4 }
ipMRouteInterfaceEntry OBJECT-TYPE
SYNTAX IpMRouteInterfaceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (conceptual row) containing the multicast routing
information for a particular interface."
INDEX { ipMRouteInterfaceIfIndex }
::= { ipMRouteInterfaceTable 1 }
IpMRouteInterfaceEntry ::= SEQUENCE {
ipMRouteInterfaceIfIndex InterfaceIndex,
ipMRouteInterfaceTtl Integer32,
ipMRouteInterfaceProtocol IANAipMRouteProtocol,
ipMRouteInterfaceRateLimit Integer32,
ipMRouteInterfaceInMcastOctets Counter32,
ipMRouteInterfaceOutMcastOctets Counter32,
ipMRouteInterfaceHCInMcastOctets Counter64,
ipMRouteInterfaceHCOutMcastOctets Counter64
}
ipMRouteInterfaceIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The ifIndex value of the interface for which this entry
contains information."
::= { ipMRouteInterfaceEntry 1 }
ipMRouteInterfaceTtl OBJECT-TYPE
SYNTAX Integer32 (0..255)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The datagram TTL threshold for the interface. Any IP
multicast datagrams with a TTL less than this threshold will
not be forwarded out the interface. The default value of 0
means all multicast packets are forwarded out the
interface."
::= { ipMRouteInterfaceEntry 2 }
ipMRouteInterfaceProtocol OBJECT-TYPE
SYNTAX IANAipMRouteProtocol
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The routing protocol running on this interface."
::= { ipMRouteInterfaceEntry 3 }
ipMRouteInterfaceRateLimit OBJECT-TYPE
ipmrouteinterfaceratelimitオブジェクトタイプ
SYNTAX Integer32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The rate-limit, in kilobits per second, of forwarded
multicast traffic on the interface. A rate-limit of 0
indicates that no rate limiting is done."
DEFVAL { 0 }
::= { ipMRouteInterfaceEntry 4 }
ipMRouteInterfaceInMcastOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets of multicast packets that have arrived
on the interface, including framing characters. This object
is similar to ifInOctets in the Interfaces MIB, except that
only multicast packets are counted."
::= { ipMRouteInterfaceEntry 5 }
ipMRouteInterfaceOutMcastOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets of multicast packets that have been
sent on the interface."
::= { ipMRouteInterfaceEntry 6 }
ipMRouteInterfaceHCInMcastOctets OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets of multicast packets that have arrived
on the interface, including framing characters. This object
is a 64-bit version of ipMRouteInterfaceInMcastOctets. It
is similar to ifHCInOctets in the Interfaces MIB, except
that only multicast packets are counted."
::= { ipMRouteInterfaceEntry 7 }
ipMRouteInterfaceHCOutMcastOctets OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets of multicast packets that have been
sent on the interface. This object is a 64-bit version of
ipMRouteInterfaceOutMcastOctets."
::= { ipMRouteInterfaceEntry 8 }
-- -- The IP Multicast Scope Boundary Table --
---IPマルチキャストスコープ境界テーブル -
ipMRouteBoundaryTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpMRouteBoundaryEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The (conceptual) table listing the router's scoped
multicast address boundaries."
::= { ipMRoute 5 }
ipMRouteBoundaryEntry OBJECT-TYPE
SYNTAX IpMRouteBoundaryEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (conceptual row) in the ipMRouteBoundaryTable
representing a scoped boundary."
INDEX { ipMRouteBoundaryIfIndex, ipMRouteBoundaryAddress,
ipMRouteBoundaryAddressMask }
::= { ipMRouteBoundaryTable 1 }
IpMRouteBoundaryEntry ::= SEQUENCE {
ipMRouteBoundaryIfIndex InterfaceIndex,
ipMRouteBoundaryAddress IpAddress,
ipMRouteBoundaryAddressMask IpAddress,
ipMRouteBoundaryStatus RowStatus
}
ipMRouteBoundaryIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The IfIndex value for the interface to which this boundary
applies. Packets with a destination address in the
associated address/mask range will not be forwarded out this
interface."
::= { ipMRouteBoundaryEntry 1 }
ipMRouteBoundaryAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The group address which when combined with the
corresponding value of ipMRouteBoundaryAddressMask
identifies the group range for which the scoped boundary
exists. Scoped addresses must come from the range 239.x.x.x
as specified in RFC 2365."
::= { ipMRouteBoundaryEntry 2 }
ipMRouteBoundaryAddressMask OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The group address mask which when combined with the
corresponding value of ipMRouteBoundaryAddress identifies
the group range for which the scoped boundary exists."
::= { ipMRouteBoundaryEntry 3 }
ipMRouteBoundaryStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this row, by which new entries may be
created, or old entries deleted from this table."
::= { ipMRouteBoundaryEntry 4 }
-- -- The IP Multicast Scope Name Table --
---IPマルチキャストスコープ名テーブル -
ipMRouteScopeNameTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpMRouteScopeNameEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The (conceptual) table listing the multicast scope names."
::= { ipMRoute 6 }
ipMRouteScopeNameEntry OBJECT-TYPE SYNTAX IpMRouteScopeNameEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) in the ipMRouteScopeNameTable representing a multicast scope name."
IPMROUTESCOPENAMEENTRYオブジェクトタイプの構文IPMROUTESCOPENAMEENTRY MAX-ACCESS NOT-ACCESSABLEステータス現在の説明 "マルチキャストスコープ名を表すIPMRoutESCopenAmaTableのエントリ（概念的行）。
INDEX { ipMRouteScopeNameAddress,
ipMRouteScopeNameAddressMask,
IMPLIED ipMRouteScopeNameLanguage }
::= { ipMRouteScopeNameTable 1 }
IpMRouteScopeNameEntry ::= SEQUENCE {
ipMRouteScopeNameAddress IpAddress,
ipMRouteScopeNameAddressMask IpAddress,
ipMRouteScopeNameLanguage LanguageTag,
ipMRouteScopeNameString SnmpAdminString,
ipMRouteScopeNameDefault TruthValue,
ipMRouteScopeNameStatus RowStatus
}
ipMRouteScopeNameAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The group address which when combined with the
corresponding value of ipMRouteScopeNameAddressMask
identifies the group range associated with the multicast
scope. Scoped addresses must come from the range
239.x.x.x."
::= { ipMRouteScopeNameEntry 1 }
ipMRouteScopeNameAddressMask OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The group address mask which when combined with the
corresponding value of ipMRouteScopeNameAddress identifies
the group range associated with the multicast scope."
::= { ipMRouteScopeNameEntry 2 }
ipMRouteScopeNameLanguage OBJECT-TYPE
SYNTAX LanguageTag
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The RFC 1766-style language tag associated with the scope
name."
::= { ipMRouteScopeNameEntry 3 }
ipMRouteScopeNameString OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The textual name associated with the multicast scope. The
value of this object should be suitable for displaying to
end-users, such as when allocating a multicast address in
this scope. When no name is specified, the default value of
this object should be the string 239.x.x.x/y with x and y
replaced appropriately to describe the address and mask
length associated with the scope."
::= { ipMRouteScopeNameEntry 4 }
ipMRouteScopeNameDefault OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"If true, indicates a preference that the name in the
following language should be used by applications if no name
is available in a desired language."
DEFVAL { false }
::= { ipMRouteScopeNameEntry 5 }
ipMRouteScopeNameStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this row, by which new entries may be
created, or old entries deleted from this table."
::= { ipMRouteScopeNameEntry 6 }
-- conformance information
- 適合情報
ipMRouteMIBConformance
OBJECT IDENTIFIER ::= { ipMRouteStdMIB 2 }
ipMRouteMIBCompliances
OBJECT IDENTIFIER ::= { ipMRouteMIBConformance 1 }
ipMRouteMIBGroups OBJECT IDENTIFIER ::= { ipMRouteMIBConformance 2 }
-- compliance statements
- コンプライアンスステートメント
ipMRouteMIBCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for the IP Multicast MIB." MODULE -- this module MANDATORY-GROUPS { ipMRouteMIBBasicGroup,
IPMRouteMibComplianceモジュールコンプライアンスステータス現在の説明「IPマルチキャストMIBのコンプライアンスステートメント」モジュール - このモジュールの必須グループ{ipmroutemibbasicgroup、
ipMRouteMIBRouteGroup}
ipmroutemibroutegroup}
GROUP ipMRouteMIBBoundaryGroup DESCRIPTION "This group is mandatory if the router supports administratively-scoped multicast address boundaries."
グループIPMRouteMiboundaryGroupの説明「ルーターが管理上スコープされたマルチキャストアドレスの境界をサポートする場合、このグループは必須です。」
OBJECT ipMRouteBoundaryStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required."
オブジェクトIPMRouteBoundaryStatus Min-Access Readのみの説明「書き込みアクセスは不要です。」
OBJECT ipMRouteScopeNameStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required."
オブジェクトIPMROUTESCOPENAMESTATUS MIN-ACCESS読み取り専用説明「書き込みアクセスは不要です。」
GROUP ipMRouteMIBHCInterfaceGroup DESCRIPTION "This group is mandatory only for those network interfaces for which the value of the corresponding instance of ifSpeed is greater than 20,000,000 bits/second."
グループIPMRoutemibhcinterfaceGroup説明「このグループは、IFSPEEDの対応するインスタンスの値が20,000,000ビット/秒を超えるネットワークインターフェイスにのみ必須です。」
::= { ipMRouteMIBCompliances 1 }
-- units of conformance
- 適合ユニット
ipMRouteMIBBasicGroup OBJECT-GROUP
OBJECTS { ipMRouteEnable, ipMRouteEntryCount,
ipMRouteUpstreamNeighbor, ipMRouteInIfIndex,
ipMRouteUpTime, ipMRouteExpiryTime,
ipMRouteNextHopState,
ipMRouteNextHopUpTime,
ipMRouteNextHopExpiryTime,
ipMRouteNextHopProtocol,
ipMRouteNextHopPkts,
ipMRouteInterfaceTtl,
ipMRouteInterfaceProtocol, ipMRouteInterfaceRateLimit,
ipMRouteInterfaceInMcastOctets,
ipMRouteInterfaceOutMcastOctets,
ipMRouteProtocol
}
STATUS current
DESCRIPTION
"A collection of objects to support basic management of IP
Multicast routing."
::= { ipMRouteMIBGroups 1 }
ipMRouteMIBHopCountGroup OBJECT-GROUP
OBJECTS { ipMRouteNextHopClosestMemberHops }
STATUS current
DESCRIPTION
"A collection of objects to support management of the use of
hop counts in IP Multicast routing."
::= { ipMRouteMIBGroups 2 }
ipMRouteMIBBoundaryGroup OBJECT-GROUP
OBJECTS { ipMRouteBoundaryStatus, ipMRouteScopeNameString,
ipMRouteScopeNameDefault, ipMRouteScopeNameStatus }
STATUS current
DESCRIPTION
"A collection of objects to support management of scoped
multicast address boundaries."
::= { ipMRouteMIBGroups 3 }
ipMRouteMIBPktsOutGroup OBJECT-GROUP
OBJECTS { ipMRouteNextHopPkts }
STATUS current
DESCRIPTION
"A collection of objects to support management of packet
counters for each outgoing interface entry of a route."
::= { ipMRouteMIBGroups 4 }
ipMRouteMIBHCInterfaceGroup OBJECT-GROUP
OBJECTS { ipMRouteInterfaceHCInMcastOctets,
ipMRouteInterfaceHCOutMcastOctets,
ipMRouteHCOctets }
STATUS current
DESCRIPTION
"A collection of objects providing information specific to
high speed (greater than 20,000,000 bits/second) network
interfaces."
::= { ipMRouteMIBGroups 5 }
ipMRouteMIBRouteGroup OBJECT-GROUP
OBJECTS { ipMRouteRtProto, ipMRouteRtAddress,
ipMRouteRtMask, ipMRouteRtType }
STATUS current
DESCRIPTION
"A collection of objects providing information on the
relationship between multicast routing information, and the
IP Forwarding Table."
::= { ipMRouteMIBGroups 6 }
ipMRouteMIBPktsGroup OBJECT-GROUP OBJECTS { ipMRoutePkts, ipMRouteDifferentInIfPackets,
ipmroutemibpktsgroupオブジェクトグループオブジェクト{ipmroutepkts、ipmroutedifferentinifpackets、
ipMRouteOctets }
STATUS current
DESCRIPTION
"A collection of objects to support management of packet
counters for each forwarding entry."
::= { ipMRouteMIBGroups 7 }
END
終わり
The ipMRouteRtProto, ipMRouteNextHopProtocol, ipMRouteInterfaceProtocol, and ipMRouteProtocol use textual conventions imported from the IANA-RTPROTO-MIB. The purpose of defining these textual conventions in a separate MIB module is to allow additional values to be defined without having to issue a new version of this document. The Internet Assigned Numbers Authority (IANA) is responsible for the assignment of all Internet numbers, including various SNMP-related numbers; it will administer the values associated with these textual conventions.
IPMRouterTProto、IPMRoutEnexThopProtocol、IPMRouteInterfaceProtocol、およびIPMRouteProtocolは、IANA-RTProto-Mibからインポートされたテキストの規則を使用します。これらのテキスト規則を別のMIBモジュールで定義する目的は、このドキュメントの新しいバージョンを発行することなく、追加の値を定義できるようにすることです。インターネットが割り当てられた番号当局（IANA）は、さまざまなSNMP関連の番号を含むすべてのインターネット番号の割り当てを担当しています。これらのテキストの規則に関連する値を管理します。
The rules for additions or changes to the IANA-RTPROTO-MIB are outlined in the DESCRIPTION clause associated with its MODULE-IDENTITY statement.
IANA-RTProto-MIBの追加または変更に関するルールは、そのモジュールIDENTITYステートメントに関連付けられた説明条項で概説されています。
The current versions of the IANA-RTPROTO-MIB can be accessed from the IANA home page at: "http://www.iana.org/".
IANA-RTProto-Mibの現在のバージョンには、IANAホームページ「http://www.iana.org/」からアクセスできます。
This MIB contains readable objects whose values provide information related to multicast routing, including information on what machines are sending to which groups. There are also a number of objects that have a MAX-ACCESS clause of read-write and/or read-create, such as those which allow an administrator to configure multicast boundaries.
このMIBには、マルチキャストルーティングに関連する情報を提供する値を提供する読みやすいオブジェクトが含まれています。また、管理者がマルチキャストの境界を構成できるように、読み取りワイトおよび/または読み取りクリートの最大アクセス句を持つオブジェクトも多数あります。
While unauthorized access to the readable objects is relatively innocuous, unauthorized access to the write-able objects could cause a denial of service, or could cause wider distribution of packets intended only for local distribution. Hence, the support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations.
読みやすいオブジェクトへの不正アクセスは比較的無害ですが、書き込み可能なオブジェクトへの不正アクセスは、サービスの拒否を引き起こす可能性があります。したがって、適切な保護のない非セクチャ環境でのセット操作のサポートは、ネットワーク操作に悪影響を与える可能性があります。
SNMPv1 by itself is such an insecure 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 SET (change/create/delete) the objects in this MIB.
SNMPV1自体は、このような不安定な環境です。ネットワーク自体が（たとえばIPSECを使用して）安全である場合でも、それでも、セキュアネットワーク上の誰がこのMIBのオブジェクトにアクセスして設定（変更/作成/削除）を許可するかについての制御はありません。
It is recommended that the implementers consider the security features as provided by the SNMPv3 framework. Specifically, the use of the User-based Security Model RFC 2574 [12] and the View-based Access Control Model RFC 2575 [15] is recommended.
実装者は、SNMPV3フレームワークで提供されるセキュリティ機能を考慮することをお勧めします。具体的には、ユーザーベースのセキュリティモデルRFC 2574 [12]およびビューベースのアクセス制御モデルRFC 2575 [15]の使用が推奨されます。
It is then a customer/user responsibility to ensure that the SNMP entity giving access to this MIB, is properly configured to give access to those objects only to those principals (users) that have legitimate rights to access them.
その場合、このMIBへのアクセスを提供するSNMPエンティティが、それらにアクセスする正当な権利を持つプリンシパル（ユーザー）にのみこれらのオブジェクトにアクセスできるように適切に構成されていることを保証することは、顧客/ユーザーの責任です。
The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF Secretariat.
IETFは、知的財産またはその他の権利の有効性または範囲に関して、この文書に記載されているテクノロジーの実装または使用に関連すると主張される可能性のある他の権利、またはそのような権利に基づくライセンスがどの程度であるかについての程度に関連する可能性があるという立場はありません。利用可能;また、そのような権利を特定するために努力したことも表明していません。標準トラックおよび標準関連のドキュメントの権利に関するIETFの手順に関する情報は、BCP-11に記載されています。出版のために利用可能にされた権利の請求のコピーと、利用可能になるライセンスの保証、またはこの仕様の実装者またはユーザーによるそのような独自の権利の使用のための一般的なライセンスまたは許可を取得するための試みの結果を取得できますIETF事務局から。
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director.
IETFは、関心のある当事者に、著作権、特許、または特許出願、またはこの基準を実践するために必要な技術をカバーする可能性のあるその他の独自の権利を注意深く招待します。情報をIETFエグゼクティブディレクターに宛ててください。
This MIB module was updated based on feedback from the IETF's Inter-Domain Multicast Routing (IDMR) Working Group.
このMIBモジュールは、IETFのドメイン間マルチキャストルーティング（IDMR）ワーキンググループからのフィードバックに基づいて更新されました。
Keith McCloghrie cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706
Keith McCloghrie Cisco Systems、Inc。170 West Tasman Drive San Jose、CA 95134-1706
Phone: +1 408 526 5260
EMail: kzm@cisco.com
Dino Farinacci Procket Networks 3850 North First Street San Jose, CA 95134
Dino Farinacci Procket Networks 3850 North First Street San Jose、CA 95134
Phone: +1 408-954-7909
Email: dino@procket.com
Dave Thaler Microsoft Corporation One Microsoft Way Redmond, WA 98052-6399
Dave Thaler Microsoft Corporation One Microsoft Way Redmond、WA 98052-6399
Phone: +1 425 703 8835
EMail: dthaler@microsoft.com
[1] Wijnen, B., Harrington, D. and R. Presuhn, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999.
[1] Wijnen、B.、Harrington、D。、およびR. Presuhn、「SNMP管理フレームワークを説明するためのアーキテクチャ」、RFC 2571、1999年4月。
[2] Rose, M. and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990.
[2] Rose、M。and K. McCloghrie、「TCP/IPベースのインターネットの管理情報の構造と識別」、STD 16、RFC 1155、1990年5月。
[3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1212, March 1991.
[3] Rose、M。and K. McCloghrie、「Scise MIB Definitions」、STD 16、RFC 1212、1991年3月。
[4] Rose, M., "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991.
[4] Rose、M。、「SNMPで使用するトラップを定義するための慣習」、RFC 1215、1991年3月。
[5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, STD 58, April 1999.
[5] McCloghrie、K.、Perkins、D.、Schoenwaelder、J.、Case、J.、Rose、M。and S. Waldbusser、「管理情報の構造バージョン2（SMIV2）」、STD 58、RFC 2578、STD 58、1999年4月。
[6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[6] McCloghrie、K.、Perkins、D.、Schoenwaelder、J.、Case、J.、Rose、M。and S. Waldbusser、「Smiv2のテキストコンベンション」、STD 58、RFC 2579、1999年4月。
[7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[7] McCloghrie、K.、Perkins、D.、Schoenwaelder、J.、Case、J.、Rose、M。、およびS. Waldbusser、「Smiv2の適合ステートメント」、Std 58、RFC 2580、1999年4月。
[8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, May 1990.
[8] Case、J.、Fedor、M.、Schoffstall、M。and J. Davin、「Simple Network Management Protocol」、STD 15、RFC 1157、1990年5月。
[9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January 1996.
[9] Case、J.、McCloghrie、K.、Rose、M。、およびS. Waldbusser、「コミュニティベースのSNMPV2の紹介」、RFC 1901、1996年1月。
[10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1906, January 1996.
[10] Case、J.、McCloghrie、K.、Rose、M。、およびS. Waldbusser、「単純なネットワーク管理プロトコル（SNMPV2）のバージョン2の輸送マッピング」、RFC 1906、1996年1月。
[11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2572, April 1999.
[11] Case、J.、Harrington D.、Presuhn R.およびB. Wijnen、「Simple Network Management Protocol（SNMP）のメッセージ処理とディスパッチ」、RFC 2572、1999年4月。
[12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, April 1999.
[12] Blumenthal、U.およびB. Wijnen、「シンプルネットワーク管理プロトコル（SNMPV3）のバージョン3のユーザーベースのセキュリティモデル（USM）」、RFC 2574、1999年4月。
[13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996.
[13] Case、J.、McCloghrie、K.、Rose、M。、およびS. Waldbusser、「単純なネットワーク管理プロトコル（SNMPV2）のバージョン2のプロトコル操作」、RFC 1905、1996年1月。
[14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC 2573, April 1999.
[14] Levi、D.、Meyer、P。and B. Stewart、「SNMPV3 Applications」、RFC 2573、1999年4月。
[15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2575, April 1999.
[15] Wijnen、B.、Presuhn、R。、およびK. McCloghrie、「シンプルネットワーク管理プロトコル（SNMP）のビューベースのアクセス制御モデル（VACM）」、RFC 2575、1999年4月。
[16] Deering, S., "Multicast Routing in a Datagram Internetwork", PhD thesis, Electrical Engineering Dept., Stanford University, December 1991.
[16] Deering、S。、「データグラムインターネットワークでのマルチキャストルーティング」、PhD論文、Stanford University、1991年12月。
[17] Waitzman, D., Partridge, C. and S. Deering, "Distance Vector Multicast Routing Protocol", RFC 1075, November 1988.
[17] Waitzman、D.、Partridge、C。and S. Deering、「距離ベクトルマルチキャストルーティングプロトコル」、RFC 1075、1988年11月。
[18] Estrin, D., Farinacci, D., Helmy, A., Thaler, D., Deering, S., Handley, M., Jacobson, V., Liu, C., Sharma, P. and L. Wei, "Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol Specification", RFC 2362, June 1998.
[18] Estrin、D.、Farinacci、D.、Helmy、A.、Thaler、D.、Deering、S.、Handley、M.、Jacobson、V.、Liu、C.、Sharma、P。and L. wei、 "Protocol Independent Multicast-Sparseモード（PIM-SM）：プロトコル仕様」、RFC 2362、1998年6月。
[19] Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Helmy, A. and L. Wei, "Protocol Independent Multicast Version 2, Dense Mode Specification", Work in Progress.
[19] Deering、S.、Estrin、D.、Farinacci、D.、Jacobson、V.、Helmy、A。and L. Wei、「プロトコル独立マルチキャストバージョン2、密度モード仕様」、作業進行中。
[20] Moy, J., "Multicast Extensions to OSPF", RFC 1584, March 1994.
[20] Moy、J。、「OSPFへのマルチキャスト拡張」、RFC 1584、1994年3月。
[21] Ballardie, A., "Core Based Trees (CBT version 2) Multicast Routing", RFC 2189, September 1997.
[21] Ballardie、A。、「コアベースのツリー（CBTバージョン2）マルチキャストルーティング」、RFC 2189、1997年9月。
[22] Meyer, D., "Administratively Scoped IP Multicast", BCP 23, RFC 2365, July 1998.
[22] Meyer、D。、「管理上スコープIPマルチキャスト」、BCP 23、RFC 2365、1998年7月。
Copyright (C) The Internet Society (2000). All Rights Reserved.
Copyright（c）The Internet Society（2000）。無断転載を禁じます。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
このドキュメントと翻訳は他の人にコピーされて提供される場合があります。また、それについてコメントまたは説明する派生作品、またはその実装を支援することは、いかなる種類の制限なしに、準備、コピー、公開、および部分的に配布される場合があります。、上記の著作権通知とこの段落がそのようなすべてのコピーとデリバティブ作品に含まれている場合。ただし、このドキュメント自体は、インターネット協会や他のインターネット組織への著作権通知や参照を削除するなど、いかなる方法でも変更できない場合があります。インターネット標準プロセスに従うか、英語以外の言語に翻訳するために必要な場合に従う必要があります。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上記の限られた許可は永続的であり、インターネット社会またはその後継者または譲受人によって取り消されることはありません。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
この文書と本書に含まれる情報は、「現状」に基づいて提供されており、インターネット社会とインターネットエンジニアリングタスクフォースは、ここにある情報の使用が行われないという保証を含むがこれらに限定されないすべての保証を否認します。特定の目的に対する商品性または適合性の権利または黙示的な保証を侵害します。
Acknowledgement
謝辞
Funding for the RFC Editor function is currently provided by the Internet Society.
RFCエディター機能の資金は現在、インターネット協会によって提供されています。