Network Working Group K. McCloghrie
Request for Comments: 2864 Cisco Systems
Category: Standards Track G. Hanson
ADC Telecommunications
June 2000
Network Working Group K. McCloghrie
Request for Comments: 2864 Cisco Systems
Category: Standards Track G. Hanson
ADC Telecommunications
June 2000
The Inverted Stack Table Extension to the Interfaces Group MIB
接口组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.
版权所有（C）互联网协会（2000年）。版权所有。
Table of Contents
目录
1 Introduction .................................................. 1
2 The SNMP Network Management Framework ......................... 1
3 Interface Sub-Layers and the ifStackTable ..................... 3
4 Definitions ................................................... 4
5 Acknowledgements .............................................. 7
6 References .................................................... 7
7 Security Considerations ....................................... 8
8 Authors' Addresses ............................................ 9
9 Notice on Intellectual Property ............................... 10
10 Full Copyright Statement ..................................... 11
1 Introduction .................................................. 1
2 The SNMP Network Management Framework ......................... 1
3 Interface Sub-Layers and the ifStackTable ..................... 3
4 Definitions ................................................... 4
5 Acknowledgements .............................................. 7
6 References .................................................... 7
7 Security Considerations ....................................... 8
8 Authors' Addresses ............................................ 9
9 Notice on Intellectual Property ............................... 10
10 Full Copyright Statement ..................................... 11
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 which provide an inverted mapping of the interface stack table used for managing network interfaces.
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它描述了托管对象，这些对象提供了用于管理网络接口的接口堆栈表的反向映射。
The SNMP Management Framework presently consists of five major components:
SNMP管理框架目前由五个主要组件组成：
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, which consists of RFC 2578 [5], RFC 2579 [6] and RFC 2580 [7].
o 为管理目的描述和命名对象和事件的机制。这种管理信息结构（SMI）的第一个版本称为SMIv1，并在STD 16、RFC 1155[2]、STD 16、RFC 1212[3]和RFC 1215[4]中进行了描述。第二个版本称为SMIv2，在STD 58中有描述，其中包括RFC 2578[5]、RFC 2579[6]和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消息协议的第二个版本不是互联网标准跟踪协议，称为SNMPv2c，在RFC 1901[9]和RFC 1906[10]中进行了描述。消息协议的第三个版本称为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 访问管理信息的协议操作。STD 15、RFC 1157[8]中描述了第一组协议操作和相关PDU格式。RFC 1905[13]中描述了第二组协议操作和相关PDU格式。
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]中描述的基于视图的访问控制机制。
A more detailed introduction to the current SNMP Management Framework can be found in RFC 2570 [18].
有关当前SNMP管理框架的更详细介绍，请参见RFC 2570[18]。
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 (e.g., 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必须在语义上等效，除非由于无法翻译而省略了对象或事件（例如，使用计数器64）。在翻译过程中，SMIv2中的一些机器可读信息将转换为SMIv1中的文本描述。但是，这种机器可读信息的丢失不被认为会改变MIB的语义。
MIB-II [16] defines objects for managing network interfaces by providing a generic interface definition together with the ability to define media-specific extensions. The generic objects are known as the 'interfaces' group.
MIB-II[16]通过提供通用接口定义以及定义媒体特定扩展的能力，定义了用于管理网络接口的对象。通用对象称为“接口”组。
Experience in defining media-specific extensions showed the need to distinguish between the multiple sub-layers beneath the internetwork-layer. Consider, for example, an interface with PPP running over an HDLC link which uses a RS232-like connector. Each of these sub-layers has its own media-specific MIB module.
定义特定于媒体的扩展的经验表明，需要区分网络层下的多个子层。例如，考虑使用PPP在HDLC链路上运行的接口，该链路使用RS232型连接器。每个子层都有自己的媒体特定MIB模块。
The latest definition of the 'interfaces' group in the IF-MIB [17] satisfies this need by having each sub-layer be represented by its own conceptual row in the ifTable. It also defines an additional MIB table, the ifStackTable, to identify the "superior" and "subordinate" sub-layers through ifIndex "pointers" to the appropriate conceptual rows in the ifTable.
IF-MIB[17]中“接口”组的最新定义通过使每个子层在ifTable中由其自己的概念行表示来满足这一需求。它还定义了一个附加的MIB表ifStackTable，通过ifIndex指向ifTable中相应概念行的“指针”来标识“上级”和“下级”子层。
Each conceptual row in the ifStackTable represents a relationship between two interfaces, where this relationship is that the "higher-layer" interface runs "on top" of the "lower-layer" interface. For example, if a PPP module operated directly over a serial interface, the PPP module would be a "higher layer" to the serial interface, and the serial interface would be a "lower layer" to the PPP module. This concept of "higher-layer" and "lower-layer" is the same as embodied in the definitions of the ifTable's packet counters.
ifStackTable中的每个概念行表示两个接口之间的关系，其中该关系表示“较高层”接口在“较低层”接口的“顶部”运行。例如，如果PPP模块直接在串行接口上运行，则PPP模块将是串行接口的“高层”，而串行接口将是PPP模块的“下层”。“上层”和“下层”的概念与ifTable的数据包计数器定义中体现的概念相同。
The ifStackTable is INDEX-ed by the ifIndex values of the two interfaces involved in the relationship. By necessity, one of these ifIndex values must come first, and the IF-MIB chose to have the higher-layer interface first, and the lower-layer interface second. Due to this, it is straight-forward for a Network Management application to read a subset of the ifStackTable and thereby determine the interfaces which run underneath a particular interface. However, to determine which interfaces run on top of a particular interface, a Network Management application has no alternative but to read the whole table. This is very inefficient when querying a device which has many interfaces, and many conceptual rows in its ifStackTable.
ifStackTable由关系中涉及的两个接口的ifIndex值进行索引。根据需要，这些ifIndex值中的一个必须首先出现，并且IF-MIB选择首先使用高层接口，然后使用底层接口。因此，网络管理应用程序直接读取ifStackTable的子集，从而确定在特定接口下运行的接口。但是，要确定哪些接口运行在特定接口之上，网络管理应用程序除了读取整个表之外别无选择。当查询一个设备时，如果该设备有许多接口，并且其ifStackTable中有许多概念行，则效率非常低。
This MIB provides an inverted Interfaces Stack Table, the ifInvStackTable. While it contains no additional information beyond that already contained in the ifStackTable, the ifInvStackTable has the ifIndex values in its INDEX clause in the reverse order, i.e., the lower-layer interface first, and the higher-layer interface second. As a result, the ifInvStackTable is an inverted version of
此MIB提供一个反向接口堆栈表ifInvStackTable。虽然ifInvStackTable不包含ifStackTable中已包含的信息以外的其他信息，但ifInvStackTable在其INDEX子句中的ifIndex值顺序相反，即先是较低层接口，然后是较高层接口。因此，ifInvStackTable是的反转版本
the same information contained in the ifStackTable. Thus, the ifInvStackTable provides an efficient means for a Network Management application to read a subset of the ifStackTable and thereby determine which interfaces run on top of a particular interface.
ifStackTable中包含的信息相同。因此，ifInvStackTable为网络管理应用程序提供了读取ifStackTable子集的有效方法，从而确定哪些接口运行在特定接口之上。
IF-INVERTED-STACK-MIB DEFINITIONS ::= BEGIN
IF-INVERTED-STACK-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, mib-2 FROM SNMPv2-SMI RowStatus FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF ifStackGroup2, ifStackHigherLayer, ifStackLowerLayer FROM IF-MIB;
从SNMPv2导入模块标识、对象类型、mib-2，从SNMPv2导入SMI RowStatus，从SNMPv2导入TC模块符合性，从SNMPv2 CONF ifStackGroup2导入对象组，从IF-mib导入ifStackHigherLayer、ifStackLowerLayer；
ifInvertedStackMIB MODULE-IDENTITY LAST-UPDATED "200006140000Z" ORGANIZATION "IETF Interfaces MIB Working Group" CONTACT-INFO " Keith McCloghrie Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 US
ifInvertedStackMIB MODULE-IDENTITY最近更新的“200006140000Z”组织“IETF接口MIB工作组”联系方式“Keith McCloghrie Cisco Systems，Inc.美国加利福尼亚州圣何塞市西塔斯曼大道170号，邮编95134-1706
408-526-5260
kzm@cisco.com"
DESCRIPTION
"The MIB module which provides the Inverted Stack Table for
interface sub-layers."
REVISION "200006140000Z"
DESCRIPTION
"Initial revision, published as RFC 2864"
::= { mib-2 77 }
408-526-5260
kzm@cisco.com"
DESCRIPTION
"The MIB module which provides the Inverted Stack Table for
interface sub-layers."
REVISION "200006140000Z"
DESCRIPTION
"Initial revision, published as RFC 2864"
::= { mib-2 77 }
ifInvMIBObjects OBJECT IDENTIFIER ::= { ifInvertedStackMIB 1 }
ifInvMIBObjects OBJECT IDENTIFIER ::= { ifInvertedStackMIB 1 }
-- -- The Inverted Interface Stack Group --
----反向接口堆栈组--
ifInvStackTable OBJECT-TYPE SYNTAX SEQUENCE OF IfInvStackEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing information on the relationships between
ifInvStackTable对象类型IfInvStackEntry MAX-ACCESS的语法序列不可访问状态当前描述“包含以下项之间关系信息的表
the multiple sub-layers of network interfaces. In particular, it contains information on which sub-layers run 'underneath' which other sub-layers, where each sub-layer corresponds to a conceptual row in the ifTable. For example, when the sub-layer with ifIndex value x runs underneath the sub-layer with ifIndex value y, then this table contains:
网络接口的多个子层。特别是，它包含关于哪些子层“在”哪些其他子层下面运行的信息，其中每个子层对应于ifTable中的概念行。例如，当ifIndex值为x的子层在ifIndex值为y的子层下方运行时，此表包含：
ifInvStackStatus.x.y=active
ifInvStackStatus.x.y=激活
For each ifIndex value, z, which identifies an active interface, there are always at least two instantiated rows in this table associated with z. For one of these rows, z is the value of ifStackHigherLayer; for the other, z is the value of ifStackLowerLayer. (If z is not involved in multiplexing, then these are the only two rows associated with z.)
对于标识活动接口的每个ifIndex值z，此表中始终至少有两个实例化行与z关联。对于其中一行，z是ifStackHigherLayer的值；对于另一个，z是ifStackLowerLayer的值。（如果z不参与多路复用，则这是与z关联的仅有两行。）
For example, two rows exist even for an interface which has no others stacked on top or below it:
例如，即使对于顶部或下方没有其他堆叠的界面，也存在两行：
ifInvStackStatus.z.0=active ifInvStackStatus.0.z=active
ifInvStackStatus.z.0=活动ifInvStackStatus.0.z=活动
This table contains exactly the same number of rows as the
ifStackTable, but the rows appear in a different order."
REFERENCE
"ifStackTable of RFC 2863"
::= { ifInvMIBObjects 1 }
This table contains exactly the same number of rows as the
ifStackTable, but the rows appear in a different order."
REFERENCE
"ifStackTable of RFC 2863"
::= { ifInvMIBObjects 1 }
ifInvStackEntry OBJECT-TYPE
SYNTAX IfInvStackEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information on a particular relationship between two sub-
layers, specifying that one sub-layer runs underneath the
other sub-layer. Each sub-layer corresponds to a conceptual
row in the ifTable."
INDEX { ifStackLowerLayer, ifStackHigherLayer }
::= { ifInvStackTable 1 }
ifInvStackEntry OBJECT-TYPE
SYNTAX IfInvStackEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information on a particular relationship between two sub-
layers, specifying that one sub-layer runs underneath the
other sub-layer. Each sub-layer corresponds to a conceptual
row in the ifTable."
INDEX { ifStackLowerLayer, ifStackHigherLayer }
::= { ifInvStackTable 1 }
IfInvStackEntry ::=
SEQUENCE {
ifInvStackStatus RowStatus
}
IfInvStackEntry ::=
SEQUENCE {
ifInvStackStatus RowStatus
}
ifInvStackStatus OBJECT-TYPE
ifInvStackStatus对象类型
SYNTAX RowStatus MAX-ACCESS read-only STATUS current DESCRIPTION "The status of the relationship between two sub-layers.
语法RowStatus MAX-ACCESS只读状态current DESCRIPTION“两个子层之间关系的状态。
An instance of this object exists for each instance of the ifStackStatus object, and vice versa. For example, if the variable ifStackStatus.H.L exists, then the variable ifInvStackStatus.L.H must also exist, and vice versa. In addition, the two variables always have the same value.
ifStackStatus对象的每个实例都存在此对象的实例，反之亦然。例如，如果变量ifStackStatus.H.L存在，则变量ifInvStackStatus.L.H也必须存在，反之亦然。此外，这两个变量始终具有相同的值。
However, unlike ifStackStatus, the ifInvStackStatus object
is NOT write-able. A network management application wishing
to change a relationship between sub-layers H and L cannot
do so by modifying the value of ifInvStackStatus.L.H, but
must instead modify the value of ifStackStatus.H.L. After
the ifStackTable is modified, the change will be reflected
in this table."
::= { ifInvStackEntry 1 }
However, unlike ifStackStatus, the ifInvStackStatus object
is NOT write-able. A network management application wishing
to change a relationship between sub-layers H and L cannot
do so by modifying the value of ifInvStackStatus.L.H, but
must instead modify the value of ifStackStatus.H.L. After
the ifStackTable is modified, the change will be reflected
in this table."
::= { ifInvStackEntry 1 }
-- conformance information
--一致性信息
ifInvConformance OBJECT IDENTIFIER ::= { ifInvMIBObjects 2 }
ifInvConformance OBJECT IDENTIFIER ::= { ifInvMIBObjects 2 }
ifInvGroups OBJECT IDENTIFIER ::= { ifInvConformance 1 }
ifInvCompliances OBJECT IDENTIFIER ::= { ifInvConformance 2 }
ifInvGroups OBJECT IDENTIFIER ::= { ifInvConformance 1 }
ifInvCompliances OBJECT IDENTIFIER ::= { ifInvConformance 2 }
-- compliance statements
--合规声明
ifInvCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities which provide inverted information on the layering of network interfaces."
ifInvCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION“提供网络接口分层反向信息的SNMP实体的符合性声明。”
MODULE -- this module MANDATORY-GROUPS { ifInvStackGroup }
MODULE--此模块为强制组{ifInvStackGroup}
OBJECT ifInvStackStatus SYNTAX INTEGER { active(1) } DESCRIPTION "Support is only required for 'active'."
对象ifInvStackStatus语法整数{active（1）}说明“仅对'active'需要支持。”
MODULE IF-MIB MANDATORY-GROUPS { ifStackGroup2 }
模块IF-MIB强制组{ifStackGroup2}
::= { ifInvCompliances 1 }
::= { ifInvCompliances 1 }
-- units of conformance
--一致性单位
ifInvStackGroup OBJECT-GROUP
OBJECTS { ifInvStackStatus }
STATUS current
DESCRIPTION
"A collection of objects providing inverted information on
the layering of MIB-II interfaces."
::= { ifInvGroups 1 }
ifInvStackGroup OBJECT-GROUP
OBJECTS { ifInvStackStatus }
STATUS current
DESCRIPTION
"A collection of objects providing inverted information on
the layering of MIB-II interfaces."
::= { ifInvGroups 1 }
END
终止
This memo has been produced by the IETF's Interfaces MIB working-group.
本备忘录由IETF接口MIB工作组编制。
[1] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, January 1998.
[1] Harrington，D.，Presohn，R.和B.Wijnen，“描述SNMP管理框架的体系结构”，RFC 2571，1998年1月。
[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.和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.和K.McCloghrie，“简明MIB定义”，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的陷阱的约定”，RFC1215，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, April 1999.
[5] McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，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.，Schoenwaeld，J.，Case，J.，Rose，M.和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.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“SMIv2的一致性声明”，STD 58，RFC 25801999年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.和J.Davin，“简单网络管理协议”，STD 15，RFC 1157，1990年5月。
[9] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January 1996.
[9] SNMPv2工作组，Case，J.，McCloghrie，K.，Rose，M.，和S.Waldbusser，“基于社区的SNMPv2简介”，RFC 19011996年1月。
[10] SNMPv2 Working Group, 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] SNMPv2工作组，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, January 1998.
[11] Case，J.，Harrington D.，Presuhn R.和B.Wijnen，“简单网络管理协议（SNMP）的消息处理和调度”，RFC 2572，1998年1月。
[12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, January 1998.
[12] Blumenthal，U.和B.Wijnen，“简单网络管理协议（SNMPv3）第3版的基于用户的安全模型（USM）”，RFC 2574，1998年1月。
[13] SNMPv2 Working Group, 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] SNMPv2工作组，Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的协议操作”，RFC 1905，1996年1月。
[14] Levi, D., Meyer, P. and B. Stewart, "SNMP Applications", RFC 2573, January 1998.
[14] Levi，D.，Meyer，P.和B.Stewart，“SNMP应用”，RFC 2573，1998年1月。
[15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2575, January 1998.
[15] Wijnen，B.，Presuhn，R.和K.McCloghrie，“用于简单网络管理协议（SNMP）的基于视图的访问控制模型（VACM）”，RFC 2575，1998年1月。
[16] McCloghrie, K. and M. Rose, "Management Information Base for Network Management of TCP/IP-based internets - MIB-II", STD 17, RFC 1213, March 1991.
[16] McCloghrie，K.和M.Rose，“基于TCP/IP的互联网网络管理的管理信息库-MIB-II”，STD 17，RFC 1213，1991年3月。
[17] McCloghrie, K. and F. Kastenholz, "The Interface Group MIB", RFC 2863, June 2000.
[17] McCloghrie，K.和F.Kastenholz，“接口组MIB”，RFC 28632000年6月。
[18] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction to Version 3 of the Internet-standard Network Management Framework", RFC 2570, April 1999.
[18] Case，J.，Mundy，R.，Partain，D.和B.Stewart，“互联网标准网络管理框架第3版简介”，RFC 25701999年4月。
There are no management objects defined in this MIB that have a MAX-ACCESS clause of read-write and/or read-create. So, if this MIB is implemented correctly, then there is no risk that an intruder can alter or create any management objects of this MIB via direct SNMP SET operations.
此MIB中未定义具有读写和/或读创建MAX-ACCESS子句的管理对象。因此，如果此MIB正确实现，则入侵者不会通过直接的SNMP集操作更改或创建此MIB的任何管理对象。
SNMPv1 by itself is not a secure environment. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB.
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框架提供的安全特性。具体而言，建议使用基于用户的安全模型RFC2574[12]和基于视图的访问控制模型RFC2575[15]。
It is then a customer/user responsibility to ensure that the SNMP entity giving access to an instance of this MIB, 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.
然后，客户/用户有责任确保授予对此MIB实例访问权限的SNMP实体被正确配置为仅授予那些拥有确实获取或设置（更改/创建/删除）对象的合法权限的主体（用户）对对象的访问权限。
Keith McCloghrie Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706
Keith McCloghrie Cisco Systems，Inc.加利福尼亚州圣何塞西塔斯曼大道170号，邮编95134-1706
Phone: 408-526-5260 EMail: kzm@cisco.com
电话：408-526-5260电子邮件：kzm@cisco.com
Gary Hanson ADC Telecommunications 14375 NW Science Park Drive Portland, Oregon, 97229
加里·汉森，俄勒冈州波特兰市科学园大道西北14375号，邮编：97229
Phone: (800)733-5511 x6333 EMail: gary_hanson@adc.com
电话：（800）733-5511 x6333电子邮件：gary_hanson@adc.com
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 implementors 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执行董事。
Copyright (C) The Internet Society (2000). All Rights Reserved.
版权所有（C）互联网协会（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编辑功能的资金目前由互联网协会提供。