Network Working Group A. Bierman
Request for Comments: 2856 K. McCloghrie
Category: Standards Track Cisco Systems, Inc.
R. Presuhn
BMC Software, Inc.
June 2000
Network Working Group A. Bierman
Request for Comments: 2856 K. McCloghrie
Category: Standards Track Cisco Systems, Inc.
R. Presuhn
BMC Software, Inc.
June 2000
Textual Conventions for Additional High Capacity Data Types
其他高容量数据类型的文本约定
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年）。版权所有。
Abstract
摘要
This memo specifies new textual conventions for additional high capacity data types, intended for SNMP implementations which already support the Counter64 data type. The definitions contained in this document represent a short term solution which may be deprecated in the future.
此备忘录为其他高容量数据类型指定了新的文本约定，用于已支持Counter64数据类型的SNMP实现。本文档中包含的定义代表一种短期解决方案，将来可能会被弃用。
Table of Contents
目录
1 The SNMP Management Framework ................................. 2
2 Overview ...................................................... 3
2.1 Short Term and Long Term Objectives ......................... 3
2.2 Limitations of the Textual Convention Approach .............. 3
3 New Textual Conventions ....................................... 4
3.1 CounterBasedGauge64 ......................................... 4
3.2 ZeroBasedCounter64 .......................................... 4
4 Definitions ................................................... 4
5 Intellectual Property ......................................... 7
6 References .................................................... 7
7 Security Considerations ....................................... 9
8 Authors' Addresses ............................................ 9
9 Full Copyright Statement ...................................... 10
1 The SNMP Management Framework ................................. 2
2 Overview ...................................................... 3
2.1 Short Term and Long Term Objectives ......................... 3
2.2 Limitations of the Textual Convention Approach .............. 3
3 New Textual Conventions ....................................... 4
3.1 CounterBasedGauge64 ......................................... 4
3.2 ZeroBasedCounter64 .......................................... 4
4 Definitions ................................................... 4
5 Intellectual Property ......................................... 7
6 References .................................................... 7
7 Security Considerations ....................................... 9
8 Authors' Addresses ............................................ 9
9 Full Copyright Statement ...................................... 10
The SNMP Management Framework presently consists of five major components:
SNMP管理框架目前由五个主要组件组成：
o An overall architecture, described in RFC 2571 [RFC2571].
o RFC 2571[RFC2571]中描述的总体架构。
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 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 [RFC1215]. The second version, called SMIv2, is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
o 为管理目的描述和命名对象和事件的机制。这种管理信息结构（SMI）的第一个版本称为SMIv1，并在STD 16、RFC 1155[RFC1155]、STD 16、RFC 1212[RFC1212]和RFC 1215[RFC1215]中进行了描述。第二个版本称为SMIv2，在STD 58、RFC 2578[RFC2578]、STD 58、RFC 2579[RFC2579]和STD 58、RFC 2580[RFC2580]中进行了描述。
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 [RFC1157]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] and RFC 1906 [RFC1906]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574].
o 用于传输管理信息的消息协议。SNMP消息协议的第一个版本称为SNMPv1，在STD 15 RFC 1157[RFC1157]中进行了描述。SNMP消息协议的第二个版本不是Internet标准跟踪协议，称为SNMPv2c，在RFC 1901[RFC1901]和RFC 1906[RFC1906]中进行了描述。消息协议的第三个版本称为SNMPv3，在RFC 1906[RFC1906]、RFC 2572[RFC2572]和RFC 2574[RFC2574]中进行了描述。
o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in STD 15, RFC 1157 [RFC1157]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [RFC1905].
o 访问管理信息的协议操作。STD 15、RFC 1157[RFC1157]中描述了第一组协议操作和相关PDU格式。RFC 1905[RFC1905]中描述了第二组协议操作和相关PDU格式。
o A set of fundamental applications described in RFC 2573 [RFC2573] and the view-based access control mechanism described in RFC 2575 [RFC2575].
o RFC 2573[RFC2573]中描述的一组基本应用程序和RFC 2575[RFC2575]中描述的基于视图的访问控制机制。
A more detailed introduction to the current SNMP Management Framework can be found in RFC 2570 [RFC2570].
有关当前SNMP管理框架的更详细介绍，请参见RFC 2570[RFC2570]。
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. The textual conventions defined in this MIB module cannot be translated to SMIv1 since the Counter64 type does not exist in SMIv1.
此备忘录指定了符合SMIv2的MIB模块。无法将此MIB模块中定义的文本约定转换为SMIv1，因为SMIv1中不存在Counter64类型。
The Structure of Management Information [RFC2578] does not explicitly address the question of how to represent integer objects other than counters that would require up to 64 bits to provide the necessary range and precision. There are MIBs in progress targeted for the standards track, which need such data types. This memo specifies a short term solution, using textual conventions, to meet these needs.
管理信息的结构[RFC2578]没有明确解决如何表示整数对象的问题，而计数器需要多达64位才能提供必要的范围和精度。有一些针对标准跟踪的MIB正在进行中，它们需要这样的数据类型。本备忘录使用文本约定指定了一个短期解决方案，以满足这些需求。
There is an immediate need to provide a Gauge64 data type, similar in semantics to the Gauge32 data type, in order to support common data representations such as:
迫切需要提供一个与Gauge32数据类型语义相似的Gauge64数据类型，以支持常见的数据表示，例如：
- a snapshot of a Counter64 at a given moment, e.g., history ring buffer
- 计数器64在给定时刻的快照，例如历史环缓冲区
- the difference between two Counter64 values
- 两个计数器值之间的差
There is also an immediate need for a 64-bit zero-based counter type, similar in semantics to the ZeroBasedCounter32 TC defined in the RMON-2 MIB [RFC2021].
还迫切需要64位零基计数器类型，其语义类似于RMON-2 MIB[RFC2021]中定义的零基计数器32 TC。
Both of these textual conventions should use a base type of Gauge64 or Unsigned64, but such a base type is not available. Until such a base type is defined and deployed, these temporary textual conventions (which use a base type of Counter64) will be used in MIBs which require unsigned 64-bit data types.
这两种文本约定都应使用Gauge64或Unsigned64的基类型，但这种基类型不可用。在定义和部署这样的基类型之前，这些临时文本约定（使用Counter64基类型）将在需要无符号64位数据类型的MIB中使用。
In order to be backward compatible with existing implementations of Counter64, the ASN.1 encoding of unsigned 64-bit data types must be identical to the encoding of Counter64 objects, i.e., identified by the [APPLICATION 6] ASN.1 tag.
为了与Counter64的现有实现向后兼容，无符号64位数据类型的ASN.1编码必须与Counter64对象的编码相同，即由[APPLICATION 6]ASN.1标记标识。
Note that the textual conventions defined in this document represent a limited and short-term solution to the problem. These textual conventions may be deprecated as a long term solution is defined and deployed to replace them. A MIB object which uses either of these textual conventions may also eventually have to be deprecated.
请注意，本文档中定义的文本约定代表了问题的有限和短期解决方案。这些文本约定可能会被弃用，因为定义并部署了一个长期解决方案来替代它们。使用这些文本约定之一的MIB对象最终也可能会被弃用。
New unsigned data types with textual conventions based on the Counter64 tag, instead of a new (or other existing) ASN.1 tag have some limitations:
基于Counter64标记而不是新的（或其他现有的）ASN.1标记的文本约定的新的无符号数据类型有一些限制：
- The MAX-ACCESS of the TC must be read-only, because the MAX-ACCESS of the underlying Counter64 type is read-only.
- TC的MAX-ACCESS必须是只读的，因为基础Counter64类型的MAX-ACCESS是只读的。
- No sub-range can be specified on the TC-derived types, because sub-ranges are not allowed on Counter64 objects.
- 不能在TC派生类型上指定子范围，因为Counter64对象上不允许使用子范围。
- No DEFVAL clause can be specified for the TC-derived types, because DEFVALs are not allowed on Counter64 objects.
- 不能为TC派生类型指定DEFVAL子句，因为Counter64对象上不允许使用DEFVAL。
- The TC-derived types cannot be used in an INDEX clause, because there is no INDEX clause mapping defined for objects of type Counter64.
- TC派生类型不能在索引子句中使用，因为没有为Counter64类型的对象定义索引子句映射。
The following textual conventions are defined to support unsigned 64-bit data types.
定义以下文本约定以支持无符号64位数据类型。
This textual convention defines a 64-bit gauge, but defined with Counter64 syntax, since no Gauge64 or Unsigned64 base type is available in SMIv2.
此文本约定定义了64位量规，但使用Counter64语法定义，因为SMIv2中没有可用的量规64或无符号64基类型。
This TC is used for storing the difference between two Counter64 values, or simply storing a snapshot of a Counter64 value at a given moment in time.
此TC用于存储两个Counter64值之间的差异，或仅存储给定时刻Counter64值的快照。
This textual convention defines a 64-bit counter with an initial value of zero, instead of an arbitrary initial value.
此文本约定定义初始值为零的64位计数器，而不是任意初始值。
This TC is used for counter objects in tables which are instantiated by management application action.
此TC用于管理应用程序操作实例化的表中的计数器对象。
HCNUM-TC DEFINITIONS ::= BEGIN
HCNUM-TC DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, mib-2, Counter64 FROM SNMPv2-SMI TEXTUAL-CONVENTION FROM SNMPv2-TC;
从SNMPv2 TC导入SNMPv2 SMI文本约定中的模块标识、mib-2、计数器64；
hcnumTC MODULE-IDENTITY LAST-UPDATED "200006080000Z"
hcnumTC模块标识最后更新“20000608000Z”
ORGANIZATION "IETF OPS Area" CONTACT-INFO " E-mail: mibs@ops.ietf.org Subscribe: majordomo@psg.com with msg body: subscribe mibs
组织“IETF行动区”联系信息电子邮件：mibs@ops.ietf.org订阅：majordomo@psg.com使用消息体：订阅MIB
Andy Bierman Cisco Systems Inc. 170 West Tasman Drive San Jose, CA 95134 USA +1 408-527-3711 abierman@cisco.com
安迪·比尔曼思科系统公司，美国加利福尼亚州圣何塞西塔斯曼大道170号，邮编95134+1408-527-3711abierman@cisco.com
Keith McCloghrie Cisco Systems Inc. 170 West Tasman Drive San Jose, CA 95134 USA +1 408-526-5260 kzm@cisco.com
美国加利福尼亚州圣何塞西塔斯曼大道170号基思·麦克洛赫里思科系统公司，邮编95134+1408-526-5260kzm@cisco.com
Randy Presuhn
BMC Software, Inc.
Office 1-3141
2141 North First Street
San Jose, California 95131 USA
+1 408 546-1006
rpresuhn@bmc.com"
DESCRIPTION
"A MIB module containing textual conventions
for high capacity data types. This module
addresses an immediate need for data types not directly
supported in the SMIv2. This short-term solution
is meant to be deprecated as a long-term solution
is deployed."
REVISION "200006080000Z"
DESCRIPTION
"Initial Version of the High Capacity Numbers
MIB module, published as RFC 2856."
::= { mib-2 78 }
Randy Presuhn
BMC Software, Inc.
Office 1-3141
2141 North First Street
San Jose, California 95131 USA
+1 408 546-1006
rpresuhn@bmc.com"
DESCRIPTION
"A MIB module containing textual conventions
for high capacity data types. This module
addresses an immediate need for data types not directly
supported in the SMIv2. This short-term solution
is meant to be deprecated as a long-term solution
is deployed."
REVISION "200006080000Z"
DESCRIPTION
"Initial Version of the High Capacity Numbers
MIB module, published as RFC 2856."
::= { mib-2 78 }
CounterBasedGauge64 ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The CounterBasedGauge64 type represents a non-negative
integer, which may increase or decrease, but shall never
exceed a maximum value, nor fall below a minimum value. The
maximum value can not be greater than 2^64-1
(18446744073709551615 decimal), and the minimum value can
CounterBasedGauge64 ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The CounterBasedGauge64 type represents a non-negative
integer, which may increase or decrease, but shall never
exceed a maximum value, nor fall below a minimum value. The
maximum value can not be greater than 2^64-1
(18446744073709551615 decimal), and the minimum value can
not be smaller than 0. The value of a CounterBasedGauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the CounterBasedGauge64 also decreases (increases).
不能小于0。每当所建模的信息大于或等于其最大值时，CounterBasedGauge64的值具有其最大值；每当所建模的信息小于或等于其最小值时，CounterBasedGauge64的值具有其最小值。如果随后被建模的信息减小到最大（最小）值以下（增大到最大（最小）值以上），则CounterBasedGauge64也会减小（增大）。
Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects.
请注意，SMIv2中不严格支持此TC，因为与Counter64基类型关联的“始终递增”和“计数器换行”语义没有保留。完全依赖（Counter64）ASN.1标记来确定对象语义的管理应用程序可能会像对Counter64对象那样错误地对这种类型的对象进行操作。
This textual convention represents a limited and short-term solution, and may be deprecated as a long term solution is defined and deployed to replace it." SYNTAX Counter64
此文本约定表示有限的短期解决方案，可能会被弃用，因为定义并部署了长期解决方案来替代它。”语法计数器64
ZeroBasedCounter64 ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This TC describes an object which counts events with the
following semantics: objects of this type will be set to
zero(0) on creation and will thereafter count appropriate
events, wrapping back to zero(0) when the value 2^64 is
reached.
ZeroBasedCounter64 ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This TC describes an object which counts events with the
following semantics: objects of this type will be set to
zero(0) on creation and will thereafter count appropriate
events, wrapping back to zero(0) when the value 2^64 is
reached.
Provided that an application discovers the new object within the minimum time to wrap it can use the initial value as a delta since it last polled the table of which this object is part. It is important for a management station to be aware of this minimum time and the actual time between polls, and to discard data if the actual time is too long or there is no defined minimum time.
如果应用程序在包装的最短时间内发现新对象，则可以使用初始值作为增量，因为它上次轮询了该对象所属的表。对于管理站来说，了解此最短时间和轮询之间的实际时间非常重要，如果实际时间过长或没有定义最短时间，则丢弃数据。
Typically this TC is used in tables where the INDEX space is constantly changing and/or the TimeFilter mechanism is in use.
通常，此TC用于索引空间不断变化和/或使用时间过滤器机制的表中。
Note that this textual convention does not retain all the semantics of the Counter64 base type. Specifically, a Counter64 has an arbitrary initial value, but objects defined with this TC are required to start at the value
请注意，此文本约定并不保留Counter64基类型的所有语义。具体来说，计数器64具有任意初始值，但使用此TC定义的对象需要从该值开始
zero. This behavior is not likely to have any adverse effects on management applications which are expecting Counter64 semantics.
零这种行为不太可能对期望使用反语义的管理应用程序产生任何不利影响。
This textual convention represents a limited and short-term solution, and may be deprecated as a long term solution is defined and deployed to replace it." SYNTAX Counter64
此文本约定表示有限的短期解决方案，可能会被弃用，因为定义并部署了长期解决方案来替代它。”语法计数器64
END
终止
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执行董事。
[RFC1155] Rose, M. and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990.
[RFC1155]Rose，M.和K.McCloghrie，“基于TCP/IP的互联网管理信息的结构和识别”，STD 16，RFC 1155，1990年5月。
[RFC1157] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, May 1990.
[RFC1157]Case，J.，Fedor，M.，Schoffstall，M.和J.Davin，“简单网络管理协议”，STD 15，RFC 1157，1990年5月。
[RFC1212] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1212, March 1991.
[RFC1212]Rose，M.和K.McCloghrie，“简明MIB定义”，STD 16，RFC 1212，1991年3月。
[RFC1215] Rose, M., "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991.
[RFC1215]Rose，M.，“定义用于SNMP的陷阱的约定”，RFC1215，1991年3月。
[RFC1901] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January 1996.
[RFC1901]Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“基于社区的SNMPv2简介”，RFC 19011996年1月。
[RFC1905] 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.
[RFC1905]Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的协议操作”，RFC 1905，1996年1月。
[RFC1906] 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.
[RFC1906]Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的传输映射”，RFC 1906，1996年1月。
[RFC2021] Waldbusser, S., "Remote Network Monitoring MIB (RMON-2)", RFC 2021, January 1997.
[RFC2021]Waldbusser，S.，“远程网络监控MIB（RMON-2）”，RFC 20211997年1月。
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996.
[RFC2026]Bradner，S.，“互联网标准过程——第3版”，BCP 9，RFC 2026，1996年10月。
[RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction to Version 3 of the Internet-standard Network Management Framework", RFC 2570, April 1999.
[RFC2570]Case，J.，Mundy，R.，Partain，D.和B.Stewart，“互联网标准网络管理框架第3版简介”，RFC 25701999年4月。
[RFC2571] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999.
[RFC2571]Harrington，D.，Presohn，R.和B.Wijnen，“描述SNMP管理框架的体系结构”，RFC 2571，1999年4月。
[RFC2572] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2572, April 1999.
[RFC2572]Case，J.，Harrington D.，Presohn R.和B.Wijnen，“简单网络管理协议（SNMP）的消息处理和调度”，RFC 2572，1999年4月。
[RFC2573] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC 2573, April 1999.
[RFC2573]Levi，D.，Meyer，P.和B.Stewart，“SNMPv3应用”，RFC 2573，1999年4月。
[RFC2574] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, April 1999.
[RFC2574]Blumenthal，U.和B.Wijnen，“简单网络管理协议（SNMPv3）第3版基于用户的安全模型（USM）”，RFC 2574，1999年4月。
[RFC2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2575, April 1999.
[RFC2575]Wijnen，B.，Presohn，R.和K.McCloghrie，“用于简单网络管理协议（SNMP）的基于视图的访问控制模型（VACM）”，RFC 2575，1999年4月。
[RFC2578] 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.
[RFC2578]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2580]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
This module does not define any management objects. Instead, it defines a set of textual conventions which may be used by other MIB modules to define management objects.
此模块不定义任何管理对象。相反，它定义了一组文本约定，其他MIB模块可以使用这些文本约定来定义管理对象。
Meaningful security considerations can only be written in the modules that define management objects.
只有在定义管理对象的模块中才能编写有意义的安全注意事项。
Andy Bierman Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134 USA
安迪·比尔曼思科系统公司，美国加利福尼亚州圣何塞西塔斯曼大道170号，邮编95134
Phone: +1 408-527-3711
EMail: abierman@cisco.com
Phone: +1 408-527-3711
EMail: abierman@cisco.com
Keith McCloghrie Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134 USA
美国加利福尼亚州圣何塞西塔斯曼大道170号基思·麦克洛赫里思科系统公司，邮编95134
Phone: +1 408-526-5260
EMail: kzm@cisco.com
Phone: +1 408-526-5260
EMail: kzm@cisco.com
Randy Presuhn BMC Software, Inc. Office 1-3141 2141 North First Street San Jose, California 95131 USA
美国加利福尼亚州圣何塞北第一街2141号Randy Presohn BMC软件公司办公室1-3141 95131
Phone: +1 408 546-1006
EMail: rpresuhn@bmc.com
Phone: +1 408 546-1006
EMail: rpresuhn@bmc.com
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编辑功能的资金目前由互联网协会提供。