Network Working Group J. Schoenwaelder
Request for Comments: 4789 International University Bremen
Obsoletes: 1089 T. Jeffree
Updates: 3417 Consultant
Category: Standards Track November 2006
Network Working Group J. Schoenwaelder
Request for Comments: 4789 International University Bremen
Obsoletes: 1089 T. Jeffree
Updates: 3417 Consultant
Category: Standards Track November 2006
Simple Network Management Protocol (SNMP) over IEEE 802 Networks
IEEE 802网络上的简单网络管理协议（SNMP）
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 IETF Trust (2006).
版权所有（C）IETF信托基金（2006年）。
Abstract
摘要
This document specifies how Simple Network Management Protocol (SNMP) messages can be transmitted directly over IEEE 802 networks.
本文件规定了如何通过IEEE 802网络直接传输简单网络管理协议（SNMP）消息。
This document obsoletes RFC 1089.
本文件淘汰了RFC 1089。
Table of Contents
目录
1. Introduction ....................................................2
1.1. Key Words ..................................................2
2. Definitions .....................................................3
3. SNMP over IEEE 802 Networks .....................................4
3.1. Serialization ..............................................4
3.2. Well-known Values ..........................................4
3.3. IEEE 802.3 Frame Format ....................................5
4. Relationship to Other MIB Modules ...............................5
5. IANA Considerations .............................................6
6. Security Considerations .........................................6
7. Acknowledgments .................................................7
8. References ......................................................7
8.1. Normative References .......................................7
8.2. Informative References .....................................7
1. Introduction ....................................................2
1.1. Key Words ..................................................2
2. Definitions .....................................................3
3. SNMP over IEEE 802 Networks .....................................4
3.1. Serialization ..............................................4
3.2. Well-known Values ..........................................4
3.3. IEEE 802.3 Frame Format ....................................5
4. Relationship to Other MIB Modules ...............................5
5. IANA Considerations .............................................6
6. Security Considerations .........................................6
7. Acknowledgments .................................................7
8. References ......................................................7
8.1. Normative References .......................................7
8.2. Informative References .....................................7
This document specifies how Simple Network Management Protocol (SNMP) messages can be transmitted directly over IEEE 802 networks. For a detailed overview of the documents that describe the Internet-Standard management framework, please refer to section 7 of RFC 3410 [RFC3410]. This document supplements the standard SNMP transport mappings defined in RFC 3417 [RFC3417].
本文件规定了如何通过IEEE 802网络直接传输简单网络管理协议（SNMP）消息。有关描述互联网标准管理框架的文件的详细概述，请参阅RFC 3410[RFC3410]第7节。本文档补充了RFC 3417[RFC3417]中定义的标准SNMP传输映射。
This document obsoletes RFC 1089.
本文件淘汰了RFC 1089。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB对象通常通过简单网络管理协议（SNMP）进行访问。MIB中的对象是使用管理信息结构（SMI）中定义的机制定义的。本备忘录规定了符合SMIv2的MIB模块，如STD 58、RFC 2578[RFC2578]、STD 58、RFC 2579[RFC2579]和STD 58、RFC 2580[RFC2580]所述。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。
SNMP-IEEE802-TM-MIB DEFINITIONS ::= BEGIN
SNMP-IEEE802-TM-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-IDENTITY, snmpModules, snmpDomains FROM SNMPv2-SMI;
从SNMPv2 SMI导入模块标识、对象标识、snmpModules、snmpDomains；
snmpIeee802TmMib MODULE-IDENTITY LAST-UPDATED "200611210000Z" ORGANIZATION "IETF Operations and Management Area" CONTACT-INFO "Juergen Schoenwaelder (Editor) International University Bremen P.O. Box 750 561 28725 Bremen, Germany
SNMPIEEEE802TMIB模块标识最后更新的“20061121000Z”组织“IETF运营和管理区域”联系信息Juergen Schoenwaeld（编辑）国际大学不来梅邮政信箱750 561 28725德国不来梅
Phone: +49 421 200-3587
EMail: j.schoenwaelder@iu-bremen.de
Phone: +49 421 200-3587
EMail: j.schoenwaelder@iu-bremen.de
Send comments to <ietfmibs@ops.ietf.org>." DESCRIPTION "This MIB module defines the SNMP over IEEE 802 transport mapping.
将评论发送到<ietfmibs@ops.ietf.org>“说明”此MIB模块定义SNMP over IEEE 802传输映射。
Copyright (C) The IETF Trust (2006). This version
of this MIB module is part of RFC 4789; see the RFC
itself for full legal notices."
REVISION "200611210000Z"
DESCRIPTION
"The initial version, published as RFC 4789."
::= { snmpModules 21 }
Copyright (C) The IETF Trust (2006). This version
of this MIB module is part of RFC 4789; see the RFC
itself for full legal notices."
REVISION "200611210000Z"
DESCRIPTION
"The initial version, published as RFC 4789."
::= { snmpModules 21 }
snmpIeee802Domain OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The SNMP over IEEE 802 networks transport domain. The
corresponding transport address is of type MacAddress
as defined in the SNMPv2-TC module (RFC 2579)."
REFERENCE "RFC 2579"
::= { snmpDomains 6 }
END
snmpIeee802Domain OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The SNMP over IEEE 802 networks transport domain. The
corresponding transport address is of type MacAddress
as defined in the SNMPv2-TC module (RFC 2579)."
REFERENCE "RFC 2579"
::= { snmpDomains 6 }
END
This is an optional transport mapping. The need to carry SNMP directly over an 802 LAN transport in order to allow for the management of simple devices was identified in applications like the Two-Port Media Access Control (MAC) Relay, which is being developed in IEEE 802.1 as project P802.1aj [802.1aj].
这是一个可选的传输映射。在诸如双端口媒体访问控制（MAC）中继等应用中，发现需要通过802.LAN传输直接携带SNMP以允许管理简单设备，该中继在IEEE 802.1中作为项目P802.1aj[802.1aj]开发。
SNMP over IEEE 802 networks has some inherent restrictions. Using the SNMP over IEEE 802 transport mapping restricts messages to a single logical IEEE 802 LAN, bridged LAN or VLAN. Furthermore, only a single SNMP engine can be addressed on a given IEEE 802 network interface. In particular, command generators and notification receivers, as well as command responders and notification originators, must share a single transport endpoint.
IEEE 802网络上的SNMP有一些固有的限制。使用SNMP over IEEE 802传输映射将消息限制为单个逻辑IEEE 802 LAN、桥接LAN或VLAN。此外，在给定的IEEE 802网络接口上只能寻址单个SNMP引擎。特别是，命令生成器和通知接收方以及命令响应者和通知发起人必须共享一个传输端点。
SNMP messages are serialized, as described in Section 8 of RFC 3417 [RFC3417]. The resulting serialized message is shipped in the data portion of an IEEE LAN MAC frame.
SNMP消息被序列化，如RFC 3417[RFC3417]第8节所述。产生的序列化消息在IEEE LAN MAC帧的数据部分中发送。
Serialized SNMP messages are sent in IEEE 802.3 frames with an Ethernet type field of 33100 (hexadecimal 814C).
序列化的SNMP消息在IEEE 802.3帧中发送，以太网类型字段为33100（十六进制814C）。
When serialized SNMP messages are sent in IEEE 802.3 frames (and in other IEEE 802 MAC frame types that can natively represent Ethernet type values), an Ethernet type field value of 33100 (hexadecimal 814C) MUST be used as the link layer protocol identifier. In IEEE 802 LANs that use LLC as the means of link layer protocol identification, such as IEEE 802.11 Wireless LANs, the SNAP encapsulation method described in subclause 10.5 "Encapsulation of Ethernet frames over LLC" in [IEEE802] MUST be used.
当在IEEE 802.3帧（以及可以本机表示以太网类型值的其他IEEE 802 MAC帧类型）中发送序列化SNMP消息时，以太网类型字段值33100（十六进制814C）必须用作链路层协议标识符。在使用LLC作为链路层协议识别手段的IEEE 802 LAN中，如IEEE 802.11无线LAN，必须使用[IEEE802]中第10.5款“LLC上以太网帧的封装”中描述的快照封装方法。
When an SNMP entity uses this transport mapping, it MUST be capable of accepting SNMP messages up to and including 484 octets in size. It is RECOMMENDED that implementations be capable of accepting messages of up to 1472 octets in size. Implementation of larger values is encouraged whenever possible.
当SNMP实体使用此传输映射时，它必须能够接受大小不超过484个八位字节的SNMP消息。建议实现能够接受多达1472个八位字节大小的消息。尽可能鼓励实施更大的价值观。
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination |
+- -+
| Ethernet |
+- -+
| Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source |
+- -+
| Ethernet |
+- -+
| Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|1 0 0 0 0 0 0 1 0 1 0 0 1 1 0 0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SNMP |
+- -+
/ message ... /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination |
+- -+
| Ethernet |
+- -+
| Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source |
+- -+
| Ethernet |
+- -+
| Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|1 0 0 0 0 0 0 1 0 1 0 0 1 1 0 0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SNMP |
+- -+
/ message ... /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
(Each tic mark represents one bit.)
（每个tic标记代表一位。）
Several core SNMP MIB modules use TDomain/TAddress pairs to identify SNMP transport endpoints. The SNMP-TARGET-MIB [RFC3413] uses TDomain/TAddress pairs to identify targets that can be used as notification receivers. TDomain/TAddress pairs are used by the NOTIFICATION-LOG-MIB [RFC3014] to record the source from which a notification was received. The ENTITY-MIB [RFC4133] uses TDomain/ TAddress pairs to provide the transport endpoint of logical entities.
几个核心SNMP MIB模块使用TDomain/TAddress对来标识SNMP传输端点。SNMP-TARGET-MIB[RFC3413]使用TDomain/TADRESS对来识别可用作通知接收器的目标。NOTIFICATION-LOG-MIB[RFC3014]使用TDomain/TAddress对记录接收通知的来源。ENTITY-MIB[RFC4133]使用TDomain/TAddress对来提供逻辑实体的传输端点。
The MIB module contained in this document introduces the object identifier constant snmpIeee802Domain. This constant can be assigned to an object of type TDomain to identify an SNMP over IEEE 802 endpoint, in which case the corresponding TAddress will have a value that conforms to the MacAddress textual convention. By providing these definitions, it is possible to use the generic MIB modules to refer to SNMP over IEEE 802 endpoints.
本文档中包含的MIB模块引入了对象标识符常量snmpieee802域。可以将此常量分配给TDomain类型的对象，以标识IEEE 802端点上的SNMP，在这种情况下，相应的TadAddress将具有符合MacAddress文本约定的值。通过提供这些定义，可以使用通用MIB模块引用IEEE 802端点上的SNMP。
IANA made a MIB OID assignment under the snmpModules branch for the SNMP-IEEE802-TM-MIB module.
IANA在snmpModules分支下为SNMP-IEEE802-TM-MIB模块分配了MIB OID。
IANA assigned an OID value below snmpDomains for the transport domain. This first required the setup of a registry for OIDs under snmpDomains. At the point of this writing, the following assignments already exist:
IANA在传输域的snmpDomains下面分配了一个OID值。这首先需要为snmpDomains下的OID设置注册表。在撰写本文时，以下作业已经存在：
Prefix: iso.org.dod.internet.snmpv2.snmpDomains (1.3.6.1.6.1)
前缀：iso.org.dod.internet.snmpv2.snmpDomains（1.3.6.1.6.1）
Decimal Name Description References
------- ---- ----------- ----------
1 snmpUDPDomain SNMP over UDP [RFC3417]
2 snmpCLNSDomain SNMP over CLNS [RFC3417]
3 snmpCONSDomain SNMP over CONS [RFC3417]
4 snmpDDPDomain SNMP over DDP [RFC3417]
5 snmpIPXDomain SNMP over IPX [RFC3417]
Decimal Name Description References
------- ---- ----------- ----------
1 snmpUDPDomain SNMP over UDP [RFC3417]
2 snmpCLNSDomain SNMP over CLNS [RFC3417]
3 snmpCONSDomain SNMP over CONS [RFC3417]
4 snmpDDPDomain SNMP over DDP [RFC3417]
5 snmpIPXDomain SNMP over IPX [RFC3417]
The following assigment has been made:
已进行以下分配：
Decimal Name Description References
------- ---- ----------- ----------
6 snmpIeee802Domain SNMP over IEEE 802 RFC 4789
Decimal Name Description References
------- ---- ----------- ----------
6 snmpIeee802Domain SNMP over IEEE 802 RFC 4789
For new assignments, a specification is required as per [RFC2434].
对于新作业，需要按照[RFC2434]的要求提供规范。
This module does not define any management objects. Instead, it defines an OBJECT-IDENTIFIER which may be used by other MIB modules to identify an SNMP transport mapping. Meaningful security considerations can only be written in the MIB modules that define management objects. The MIB module in this document has therefore no impact on the security of the Internet.
此模块不定义任何管理对象。相反，它定义了一个对象标识符，其他MIB模块可以使用该标识符来标识SNMP传输映射。有意义的安全注意事项只能写入定义管理对象的MIB模块中。因此，本文档中的MIB模块对Internet的安全性没有影响。
SNMPv1 and SNMPv2c messages are not considered secure. It is recommended that the implementors consider the use of SNMPv3 messages and the security features as provided by the SNMPv3 framework. Specifically, the use of the User-based Security Model STD 62, RFC 3414 [RFC3414] and the View-based Access Control Model STD 62, RFC 3415 [RFC3415] is recommended.
SNMPv1和SNMPv2c消息被认为是不安全的。建议实施者考虑SNMPv3消息的使用和SNMPv3框架所提供的安全特性。具体而言，建议使用基于用户的安全模型STD 62、RFC 3414[RFC3414]和基于视图的访问控制模型STD 62、RFC 3415[RFC3415]。
It is then a customer/user responsibility to ensure that the SNMP entity giving access to a 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) them.
然后，客户/用户有责任确保对访问MIB的SNMP实体进行了正确配置，以便仅向那些拥有确实获取或设置（更改）对象的合法权限的主体（用户）授予对象访问权限。
The original SNMP over Ethernet definition was written by Marty Schoffstall, Chuck Davin, Mark Fedor, and Jeff Case, and published as RFC 1089 [RFC1089].
最初的SNMP over Ethernet定义由Marty Schoffstall、Chuck Davin、Mark Fedor和Jeff Case编写，并作为RFC 1089[RFC1089]发布。
Bert Wijnen and Dan Romascanu provided guidance on many aspects of this revised specification. David Harrington provided useful comments that improved the presentation.
Bert Wijnen和Dan Romascanu就本修订规范的许多方面提供了指导。David Harrington提供了有用的意见，改进了演示文稿。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2578]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2580]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[RFC3417] Presuhn, R., Ed., "Transport Mappings for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3417, December 2002.
[RFC3417]Presohn，R.，Ed.“简单网络管理协议（SNMP）的传输映射”，STD 62，RFC 34172002年12月。
[IEEE802] "IEEE Standard for Local Area Networks: Overview and Architecture", IEEE Std. 802-2001.
[IEEE802]“局域网IEEE标准：概述和体系结构”，IEEE标准802-2001。
[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月。
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002.
[RFC3410]Case，J.，Mundy，R.，Partain，D.，和B.Stewart，“互联网标准管理框架的介绍和适用性声明”，RFC 34102002年12月。
[RFC3413] Levi, D., Meyer, P., and B. Stewart, "Simple Network Management Protocol (SNMP) Applications", STD 62, RFC 3413, December 2002.
[RFC3413]Levi，D.，Meyer，P.，和B.Stewart，“简单网络管理协议（SNMP）应用”，STD 62，RFC 3413，2002年12月。
[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", STD 62, RFC 3414, December 2002.
[RFC3414]Blumenthal，U.和B.Wijnen，“简单网络管理协议（SNMPv3）版本3的基于用户的安全模型（USM）”，STD 62，RFC 3414，2002年12月。
[RFC3415] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3415, December 2002.
[RFC3415]Wijnen，B.，Presuhn，R.，和K.McCloghrie，“用于简单网络管理协议（SNMP）的基于视图的访问控制模型（VACM）”，STD 62，RFC 3415，2002年12月。
[RFC3014] Kavasseri, R., "Notification Log MIB", RFC 3014, November 2000.
[RFC3014]Kavasseri，R.，“通知日志MIB”，RFC30142000年11月。
[RFC4133] Bierman, A. and K. McCloghrie, "Entity MIB (Version 3)", RFC 4133, August 2005.
[RFC4133]Bierman，A.和K.McCloghrie，“实体MIB（版本3）”，RFC 41332005年8月。
[RFC1089] Schoffstall, M., Davin, C., Fedor, M., and J. Case, "SNMP over Ethernet", RFC 1089, February 1989.
[RFC1089]Schoffstall，M.，Davin，C.，Fedor，M.，和J.Case，“以太网上的SNMP”，RFC 1089，1989年2月。
[802.1aj] P802.1aj/D1.4 Draft Standard for Local and Metropolitan Area Networks - Virtual Bridged Local Area Networks - Amendment 08: Two-Port Media Access Control (MAC) Relay, IEEE 802.1 Working Group, June 2006, Work in Progress.
[802.1aj]P802.1aj/D1.4局域网和城域网标准草案-虚拟桥接局域网-修订件08：双端口媒体访问控制（MAC）中继，IEEE 802.1工作组，2006年6月，正在进行中。
Authors' Addresses
作者地址
Juergen Schoenwaelder International University Bremen Campus Ring 1 28725 Bremen Germany
德国不来梅Juergen Schoenwaeld国际大学不来梅校区环128725
Phone: +49 421 200-3587
EMail: j.schoenwaelder@iu-bremen.de
Phone: +49 421 200-3587
EMail: j.schoenwaelder@iu-bremen.de
Tony Jeffree Consultant 11a Poplar Grove Sale, Cheshire, M33 3AX United Kingdom
托尼·杰弗里顾问11a杨树林销售，柴郡，M33 3AX英国
Phone: +44-161-973-4278
EMail: tony@jeffree.co.uk
Phone: +44-161-973-4278
EMail: tony@jeffree.co.uk
Full Copyright Statement
完整版权声明
Copyright (C) The IETF Trust (2006).
版权所有（C）IETF信托基金（2006年）。
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.
本文件受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, THE IETF TRUST, 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.
本文件及其包含的信息以“原样”为基础提供，贡献者、他/她所代表或赞助的组织（如有）、互联网协会、IETF信托基金和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
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编辑功能的资金目前由互联网协会提供。