Network Working Group P. Eronen
Request for Comments: 5612 Nokia
Category: Informational D. Harrington
Huawei Technologies (USA)
August 2009
Network Working Group P. Eronen
Request for Comments: 5612 Nokia
Category: Informational D. Harrington
Huawei Technologies (USA)
August 2009
Enterprise Number for Documentation Use
文件使用的企业编号
Abstract
摘要
This document describes an Enterprise Number (also known as SMI Network Management Private Enterprise Code) for use in documentation.
本文档描述了在文档中使用的企业编号（也称为SMI网络管理专用企业代码）。
Status of This Memo
关于下段备忘
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2009 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document.
本文件受BCP 78和IETF信托在本文件出版之日生效的与IETF文件有关的法律规定的约束(http://trustee.ietf.org/license-info). 请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。
RFC 1065 [RFC1065] (later superceded by [RFC1155] and [RFC2578]) created a subtree (arc) of object identifiers (OIDs) for identifying management objects that are defined unilaterally by a single party, such as an enterprise. The subtree for a particular enterprise consists of the prefix "1.3.6.1.4.1.", followed by the Enterprise Number assigned for that enterprise.
RFC 1065[RFC1065]（后来被[RFC1155]和[RFC2578]取代）创建了对象标识符（OID）的子树（arc），用于标识由单一方（如企业）单方面定义的管理对象。特定企业的子树由前缀“1.3.6.1.4.1.”组成，后跟为该企业分配的企业编号。
Enterprise Numbers are allocated by IANA, and are also known as "Private Enterprise Numbers", "Enterprise Codes", and "SMI (Structure of Management Information) Network Management Private Enterprise Codes". See the "Private Enterprise Number Application Form" [Application] for more information on how to request an Enterprise Number from IANA, and [Numbers] for the list of currently assigned numbers.
企业编号由IANA分配，也称为“私有企业编号”、“企业代码”和“SMI（管理信息结构）网络管理私有企业代码”。有关如何向IANA申请企业编号的更多信息，请参见“私人企业编号申请表”【申请】，以及当前分配编号列表的【编号】。
Enterprise Numbers have also been used for many other purposes than OIDs in various protocols; for example:
企业编号还被用于各种协议中OID以外的许多其他用途；例如：
o "STRUCTURED-DATA" identifiers in Syslog [RFC5424]
o "Vendor-Specific" RADIUS attributes [RFC2865]
o Mobile IPv4 vendor/organization-specific extensions [RFC3115]
o User-defined error information in RSVP [RFC5284]
o Vendor options in DHCPv4 [RFC3925]
o Enterprise-specific information elements in the IP Flow
Information Export (IPFIX) protocol [RFC5101]
o "STRUCTURED-DATA" identifiers in Syslog [RFC5424]
o "Vendor-Specific" RADIUS attributes [RFC2865]
o Mobile IPv4 vendor/organization-specific extensions [RFC3115]
o User-defined error information in RSVP [RFC5284]
o Vendor options in DHCPv4 [RFC3925]
o Enterprise-specific information elements in the IP Flow
Information Export (IPFIX) protocol [RFC5101]
Documents related to these protocols may include examples that contain Enterprise Numbers. To reduce the likelihood of conflict and confusion, this document specifies an Enterprise Number for use in examples in RFCs, books, documentation, and the like.
与这些协议相关的文档可能包括包含企业编号的示例。为了减少冲突和混淆的可能性，本文档指定了一个企业编号，用于RFC、书籍、文档等中的示例。
This Enterprise Number is not intended to be implemented. It is not expected that any implementation would send it, or that any implementation would treat it specially when receiving it.
本企业编号不打算实施。不希望任何实现发送它，也不希望任何实现在接收它时特别对待它。
The Enterprise Number 32473 has been allocated for use in examples in RFCs, books, documentation, and the like.
企业编号32473已分配用于rfc、书籍、文档等的示例中。
IANA has updated the registration for Enterprise Number 32473 to point to this RFC.
IANA已更新企业注册号32473，以指向此RFC。
Allocating an enterprise number for documentation use does not have any direct impact on security.
为文档使用分配企业编号不会对安全性产生任何直接影响。
The need for an Enterprise Number for documentation use was identified by Rainer Gerhards for the examples in [RFC5424]. The authors would also like to thank Michelle Cotton for her help, and Alfred Hoenes for his comments. This document borrows text from [RFC5398] and ideas from [RFC4735].
Rainer Gerhards在[RFC5424]中的示例中确定了文件使用的企业编号的需要。作者还要感谢米歇尔·科顿的帮助，以及阿尔弗雷德·霍恩斯的评论。本文件借用了[RFC5398]中的文本和[RFC4735]中的思想。
[Numbers] IANA, "Private Enterprise Numbers", <http://www.iana.org/assignments/enterprise-numbers>, 2009.
【编号】IANA，“私营企业编号”<http://www.iana.org/assignments/enterprise-numbers>, 2009.
[Application] IANA, "Protocol Registration Forms", http://www.iana.org/protocols/apply/.
[申请]IANA，“协议登记表”，http://www.iana.org/protocols/apply/.
[RFC1065] Rose, M. and K. McCloghrie, "Structure and identification of management information for TCP/IP-based internets", RFC 1065, August 1988.
[RFC1065]Rose，M.和K.McCloghrie，“基于TCP/IP的互联网管理信息的结构和识别”，RFC 1065，1988年8月。
[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月。
[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月。
[RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, "Remote Authentication Dial In User Service (RADIUS)", RFC 2865, June 2000.
[RFC2865]Rigney，C.，Willens，S.，Rubens，A.，和W.Simpson，“远程认证拨入用户服务（RADIUS）”，RFC 28652000年6月。
[RFC3115] Dommety, G. and K. Leung, "Mobile IP Vendor/ Organization-Specific Extensions", RFC 3115, April 2001.
[RFC3115]Dommety，G.和K.Leung，“移动IP供应商/组织特定扩展”，RFC 3115，2001年4月。
[RFC3925] Littlefield, J., "Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4)", RFC 3925, October 2004.
[RFC3925]Littlefield，J.，“供应商识别动态主机配置协议版本4（DHCPv4）的供应商选项”，RFC 39252004年10月。
[RFC4735] Taylor, T., "Example Media Types for Use in Documentation", RFC 4735, October 2006.
[RFC4735]Taylor，T.，“文档中使用的示例媒体类型”，RFC 47352006年10月。
[RFC5101] Claise, B., "Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information", RFC 5101, January 2008.
[RFC5101]Claise，B.，“用于交换IP流量信息的IP流量信息导出（IPFIX）协议规范”，RFC 5101，2008年1月。
[RFC5284] Swallow, G. and A. Farrel, "User-Defined Errors for RSVP", RFC 5284, August 2008.
[RFC5284]Swallow，G.和A.Farrel，“RSVP的用户定义错误”，RFC 5284，2008年8月。
[RFC5398] Huston, G., "Autonomous System (AS) Number Reservation for Documentation Use", RFC 5398, December 2008.
[RFC5398]Huston，G.，“文件使用的自主系统（AS）编号保留”，RFC 5398，2008年12月。
[RFC5424] Gerhards, R., "The Syslog Protocol", RFC 5424, March 2009.
[RFC5424]Gerhards，R.，“系统日志协议”，RFC 54242009年3月。
Authors' Addresses
作者地址
Pasi Eronen Nokia Research Center P.O. Box 407 FIN-00045 Nokia Group Finland
Pasi Eronen诺基亚研究中心邮政信箱407 FIN-00045诺基亚集团芬兰
EMail: pasi.eronen@nokia.com
EMail: pasi.eronen@nokia.com
David Harrington Huawei Technologies (USA) 1700 Alma Drive, Suite 100 Plano, TX 75075 USA
David Harrington华为技术（美国）美国德克萨斯州普莱诺市阿尔玛大道1700号100室75075
EMail: dharrington@huawei.com
EMail: dharrington@huawei.com