Network Working Group B. Wijnen
Request for Comments: 3737 Lucent Technologies
Category: Standards Track A. Bierman
Cisco Systems, Inc.
April 2004
Network Working Group B. Wijnen
Request for Comments: 3737 Lucent Technologies
Category: Standards Track A. Bierman
Cisco Systems, Inc.
April 2004
IANA Guidelines for the Registry of Remote Monitoring (RMON) MIB modules
IANA远程监控（RMON）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 (2004). All Rights Reserved.
版权所有（C）互联网协会（2004年）。版权所有。
Abstract
摘要
This document defines the procedures for IANA to administer and maintain the Object Identifier (OID) tree under the Remote Monitoring (rmon) root. This memo also documents the currently assigned values.
本文档定义了IANA在远程监控（rmon）根目录下管理和维护对象标识符（OID）树的过程。此备忘录还记录了当前分配的值。
The RMONMIB Working Group so far has maintained its own registry for OID assignments for new MIB modules under the root OID for rmon [RFC2819]. This has worked reasonably well, although errors had to be corrected at a late stage one or two times, and a few now defunct assignments have been made as well.
到目前为止，RMONMIB工作组在rmon的根OID[RFC2819]下为新MIB模块维护了自己的OID分配注册表。这项工作做得相当不错，尽管在后期必须纠正一两次错误，而且也有一些现已失效的任务已经完成。
It is also a somewhat non-standard way of doing things, because normally a new standards track MIB module will get a MIB root assigned at the time that the module is being published as part of an RFC.
这也是一种有点非标准的处理方式，因为通常情况下，新的标准跟踪MIB模块将在模块作为RFC的一部分发布时获得分配的MIB根。
This document lists the currently assigned rmon OIDs. It also describes the procedures and rules for new assignments and asks IANA to take over the responsibility for existing and future assignments.
本文档列出了当前分配的rmon OID。它还描述了新任务的程序和规则，并要求IANA接管现有和未来任务的责任。
The current assignments are not all too logical. Initially normal MIB OIDs were assigned under rmon, but at a later time the WG used the rmon root OID to create new MIB modules underneath it. Some
当前的分配不太符合逻辑。最初在rmon下分配正常的MIB OID，但后来工作组使用rmon根OID在其下创建新的MIB模块。一些
people will claim 'an OID is just an OID', and while this is true, it does not make things easier if the organisation of OIDs is not logical. However, we cannot change what has been assigned in the past. From now on, only MODULE-IDENTITY macro (MIB root) assignments will be made (by IANA) under the 'rmon' node. Within a MIB module, the working group authors/editors can then assign their own OIDs according to normal procedures.
人们会声称“一个OID就是一个OID”，虽然这是真的，但如果OID的组织不符合逻辑，这并不会让事情变得更容易。然而，我们不能改变过去分配的任务。从现在起，（IANA）将在“rmon”节点下仅分配模块标识宏（MIB根）。在MIB模块中，工作组作者/编辑可以根据正常程序分配自己的OID。
At the time of this writing, the following OIDs have been assigned and IANA has picked up this information in their public registry of assigned values. They are listed as part of the already existing smi-numbers registry at:
在撰写本文时，已分配了以下OID，IANA已在其分配值的公共注册表中获取该信息。它们列为现有smi编号注册表的一部分，位于：
http://www.iana.org/assignments/smi-numbers
http://www.iana.org/assignments/smi-numbers
...mib-2.rmon (1.3.6.1.2.1.16)
…mib-2.rmon（1.3.6.1.2.1.16）
The assignments under ...mib-2.rmon were maintained by the RMONMIB Working Group until publication of RFC 3737. Some (early) assignments may not look all too logical. That is true, but that is history and cannot be changed. From now on, only MODULE-IDENTITY macro (MIB root) assignments will be made (by IANA) under the 'rmon' node.
在RFC 3737发布之前，RMONMIB工作组保留了…mib-2.rmon下的任务。有些（早期）作业看起来可能不太合乎逻辑。这是事实，但这是历史，不能改变。从现在起，（IANA）将在“rmon”节点下仅分配模块标识宏（MIB根）。
Key: nnn == { rmon nnn }
Key: nnn == { rmon nnn }
nnn descriptor OID Type Document
nnn描述符OID类型文档
0 rmonEventsV2 Notifications root [RFC2819]
1 statistics OID [RFC2819]
2 history OID [RFC2819]
3 alarm OID [RFC2819]
4 hosts OID [RFC2819]
5 hostTopN OID [RFC2819]
6 matrix OID [RFC2819]
7 filter OID [RFC2819]
8 capture OID [RFC2819]
9 event OID [RFC2819]
10 tokenRing OID [RFC1513]
11 protocolDir OID [RFC2021]
12 protocolDist OID [RFC2021]
13 addressMap OID [RFC2021]
14 nlHost OID [RFC2021]
15 nlMatrix OID [RFC2021]
16 alHost OID [RFC2021]
17 alMatrix OID [RFC2021]
18 usrHistory OID [RFC2021]
19 probeConfig OID [RFC2021]
20 rmonConformance OID [RFC2021]
21 mediaIndependentStats OID [RFC3273]
22 switchRMON M-I [RFC2613]
23 apm M-I [RFC3729]
24 available
25 pmCapsMIB M-I (defunct)
26 dsmonMIB M-I [RFC3287]
27 interfaceTopNMIB M-I [RFC3144]
28 reserved for sspmMIB M-I [..rmonmib-sspm-mib-nn.txt]
29 hcAlarmMIB M-I [RFC3434]
30 reserved for tpmMIB M-I [..rmonmib-tpm-mib-nn.txt]
31 reserved for raqmon M-I [..rmonmib-raqmon-mib-nn.txt]
32 reserved for raqmonDs M-I [..rmonmib-raqmon-pdu-nn.txt]
0 rmonEventsV2 Notifications root [RFC2819]
1 statistics OID [RFC2819]
2 history OID [RFC2819]
3 alarm OID [RFC2819]
4 hosts OID [RFC2819]
5 hostTopN OID [RFC2819]
6 matrix OID [RFC2819]
7 filter OID [RFC2819]
8 capture OID [RFC2819]
9 event OID [RFC2819]
10 tokenRing OID [RFC1513]
11 protocolDir OID [RFC2021]
12 protocolDist OID [RFC2021]
13 addressMap OID [RFC2021]
14 nlHost OID [RFC2021]
15 nlMatrix OID [RFC2021]
16 alHost OID [RFC2021]
17 alMatrix OID [RFC2021]
18 usrHistory OID [RFC2021]
19 probeConfig OID [RFC2021]
20 rmonConformance OID [RFC2021]
21 mediaIndependentStats OID [RFC3273]
22 switchRMON M-I [RFC2613]
23 apm M-I [RFC3729]
24 available
25 pmCapsMIB M-I (defunct)
26 dsmonMIB M-I [RFC3287]
27 interfaceTopNMIB M-I [RFC3144]
28 reserved for sspmMIB M-I [..rmonmib-sspm-mib-nn.txt]
29 hcAlarmMIB M-I [RFC3434]
30 reserved for tpmMIB M-I [..rmonmib-tpm-mib-nn.txt]
31 reserved for raqmon M-I [..rmonmib-raqmon-mib-nn.txt]
32 reserved for raqmonDs M-I [..rmonmib-raqmon-pdu-nn.txt]
Key: xxx == { rmon.rmonConformance xxx }
Key: xxx == { rmon.rmonConformance xxx }
...mib-2.rmon.conformance (1.3.6.1.2.1.16.20)
…mib-2.rmon.一致性（1.3.6.1.2.1.16.20）
xxx descriptor OID Type Document
xxx描述符OID类型文档
1 rmon2MIBCompliances OID [RFC2021]
2 rmon2MIBGroups OID [RFC2021]
3 smonMIBCompliances OID [RFC2613]
4 smonMIBGroups OID [RFC2613]
5 hcRMON M-I [RFC3273]
6 hcRmonMIBCompliances OID [RFC3273]
7 hcRmonMIBGroups OID [RFC3273]
8 rmonMibModule M-I [RFC2819]
9 rmonCompliances OID [RFC2819]
10 rmonGroups OID [RFC2819]
1 rmon2MIBCompliances OID [RFC2021]
2 rmon2MIBGroups OID [RFC2021]
3 smonMIBCompliances OID [RFC2613]
4 smonMIBGroups OID [RFC2613]
5 hcRMON M-I [RFC3273]
6 hcRmonMIBCompliances OID [RFC3273]
7 hcRmonMIBGroups OID [RFC3273]
8 rmonMibModule M-I [RFC2819]
9 rmonCompliances OID [RFC2819]
10 rmonGroups OID [RFC2819]
When anyone is writing a internet-draft for which a new assignment is needed/wanted under the rmon OID, then the proper way to do so is as follows:
如果任何人正在撰写互联网草稿，并且需要/想要在rmon OID下完成新的任务，那么正确的方式如下：
EXAMPLE-MIB DEFINITIONS ::= BEGIN
EXAMPLE-MIB DEFINITIONS ::= BEGIN
IMPORTS rmon FROM RMON-MIB
从rmon-MIB导入rmon
.. other imports ..
.. 其他进口。。
exampleMIB MODULE-IDENTITY
示例MIB模块标识
... other normal MODULE-IDENTITY stuff ...
... 其他正常的模块身份信息。。。
::= { rmon nnn } -- IANA: please assign nnn
-- RFC-Editor: replace nnn with IANA-assigned
-- number and remove this note
::= { rmon nnn } -- IANA: please assign nnn
-- RFC-Editor: replace nnn with IANA-assigned
-- number and remove this note
IANA will assign the number as part of the RFC publication process.
IANA将在RFC发布过程中分配编号。
This memo describes procedures for IANA assignment of OBJECT IDENTIFIER values, and has no impact on the security of the Internet.
本备忘录描述了IANA分配对象标识符值的过程，对互联网安全没有影响。
IANA has picked up the initial set of assignments and integrated them into the existing registry for smi-numbers at:
IANA已获取初始分配集，并将其集成到smi编号的现有注册表中，地址为：
http://www.iana.org/assignments/smi-numbers
http://www.iana.org/assignments/smi-numbers
The list is presented in Section 2.
清单见第2节。
IANA is requested to maintain this registry for future assignments. New assignments can only be made via Standards Action as described in [RFC2434].
IANA被要求维护此注册表以备将来分配。新分配只能通过[RFC2434]中所述的标准行动进行。
IANA will assign the number as part of the RFC publication process.
IANA将在RFC发布过程中分配编号。
This document was produced as a result of discussion between the Operations and Management AD responsible for Network Management and the WG chair for the RMONMIB Working Group. Thanks to Andy Bierman for keeping and administering the registry up to this point in time.
本文件是负责网络管理的运营和管理AD与RMONMIB工作组工作组主席讨论的结果。感谢Andy Bierman及时保存和管理注册表。
The document has been reviewed by the RMONMIB Working Group.
该文件已由RMONMIB工作组审查。
[RFC1513] Waldbusser, S., "Token Ring Extensions to the Remote Network Monitoring MIB", RFC 1513, September 1993.
[RFC1513]Waldbusser，S.，“远程网络监控MIB的令牌环扩展”，RFC 1513，1993年9月。
[RFC2021] Waldbusser, S., "Remote Network Monitoring Management Information Base Version 2 using SMIv2", RFC 2021, January 1997.
[RFC2021]Waldbusser，S.，“使用SMIv2的远程网络监控管理信息库版本2”，RFC 20211997年1月。
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
[RFC2434]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 2434，1998年10月。
[RFC2613] Waterman, R., Lahaye, B., Romascanu, D. and S. Waldbusser, "Remote Network Monitoring MIB Extensions for Switched Networks Version 1.0", RFC 2613, June 1999.
[RFC2613]Waterman，R.，Lahaye，B.，Romascanu，D.和S.Waldbusser，“交换网络1.0版的远程网络监控MIB扩展”，RFC 2613，1999年6月。
[RFC2819] Waldbusser, S., "Remote Network Monitoring Management Information Base", STD 59, RFC 2819, May 2000.
[RFC2819]Waldbusser，S.，“远程网络监控管理信息库”，STD 59，RFC 2819，2000年5月。
[RFC3144] Romascanu, D., "Remote Monitoring MIB Extensions for Interface Parameters Monitoring", RFC 3144, August 2001.
[RFC3144]Romascanu，D.，“用于接口参数监控的远程监控MIB扩展”，RFC 31442001年8月。
[RFC3273] Waldbusser, S., "Remote Network Monitoring Management Information Base for High Capacity Networks", RFC 3273, July 2002.
[RFC3273]Waldbusser，S.，“大容量网络的远程网络监控管理信息库”，RFC3273，2002年7月。
[RFC3287] Bierman, A., "Remote Monitoring MIB Extensions for Differentiated Services", RFC 3287, July 2002.
[RFC3287]Bierman，A.，“区分服务的远程监控MIB扩展”，RFC3287，2002年7月。
[RFC3434] Bierman, A. and K. McCloghrie, "Remote Monitoring MIB Extensions for High Capacity Alarms", RFC 3434, December 2002.
[RFC3434]Bierman，A.和K.McCloghrie，“高容量警报的远程监控MIB扩展”，RFC 3434，2002年12月。
[RFC3729] Waldbusser, S., "Application Performance Measurement MIB", RFC 3729, March 2004.
[RFC3729]Waldbusser，S.，“应用程序性能度量MIB”，RFC 37292004年3月。
Bert Wijnen Lucent Technologies Schagen 33 3461 GL Linschoten Netherlands
Bert Wijnen-Lucent Technologies Schagen 33 3461德国劳埃德船级社荷兰
Phone: +31-348-407-775
EMail: bwijnen@lucent.com
Phone: +31-348-407-775
EMail: bwijnen@lucent.com
Andy Bierman Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA USA
安迪·比尔曼思科系统公司，美国加利福尼亚州圣何塞市西塔斯曼大道170号
Phone: +1-408-527-3711
EMail: abierman@cisco.com
Phone: +1-408-527-3711
EMail: abierman@cisco.com
Copyright (C) The Internet Society (2004). This document is subject to the rights, licenses and restrictions contained in BCP 78 and except as set forth therein, the authors retain all their rights.
版权所有（C）互联网协会（2004年）。本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。