Network Working Group M. Mealling
Request for Comments: 3001 Network Solutions, Inc.
Category: Informational November 2000
Network Working Group M. Mealling
Request for Comments: 3001 Network Solutions, Inc.
Category: Informational November 2000
A URN Namespace of Object Identifiers
对象标识符的URN命名空间
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) The Internet Society (2000). All Rights Reserved.
版权所有（C）互联网协会（2000年）。版权所有。
Abstract
摘要
This document describes a Uniform Resource Names (URN) namespace that contains Object Identifiers (OIDs).
本文档描述了包含对象标识符（OID）的统一资源名称（URN）命名空间。
An Object Identifier is a series of digits delimited in some way. The rules roughly state that once an entity is assigned an Object Identifier (OID) it has sole discretion to further subdelegate off of that OID. Some examples of OIDs include:
对象标识符是以某种方式分隔的一系列数字。这些规则大致规定，一旦实体被分配了一个对象标识符（OID），它就有权自行决定是否从该OID进一步进行子委托。OID的一些示例包括：
o 1.3.6.1 - the Internet OID
o 1.3.6.1.4.1 - IANA-assigned company OIDs, used for private MIBs
and such things
o 1.3.6.1.2.1.27 - The Applications MIB
o 0.9.2342.19200300.100.4 - Object ID's used in the directory pilot
project to identify X.500 Object Classes. Mostly defined in RFC-
1274.
o 1.3.6.1 - the Internet OID
o 1.3.6.1.4.1 - IANA-assigned company OIDs, used for private MIBs
and such things
o 1.3.6.1.2.1.27 - The Applications MIB
o 0.9.2342.19200300.100.4 - Object ID's used in the directory pilot
project to identify X.500 Object Classes. Mostly defined in RFC-
1274.
This document specifies the "oid" URN namespace [1]. This namespace is for encoding an Object Identifier as specified in ASN.1 [2] as a URI.
本文档指定了“oid”URN命名空间[1]。此命名空间用于将ASN.1[2]中指定的对象标识符编码为URI。
The namespace specification is for a formal namespace.
名称空间规范用于正式名称空间。
Namespace ID:
命名空间ID:
"oid" requested.
请求“oid”。
Registration Information:
注册资料：
Registration Version Number: 1 Registration Date: 2000-04-30
注册版本号：1注册日期：2000-04-30
Declared registrant of the namespace:
已声明命名空间的注册人：
I need help here. I'm not comfortable being the 'registrant'. So who do I actually put here?
我需要帮助。作为“注册人”我不舒服。那么我到底把谁放在这里呢？
The ISO/IEC Joint Technical Committee 1 - SubCommittee 6 The actual real authority is the ASN.1 specification itself but at present SC6 is the committee that has the authority to interpret what that means.
ISO/IEC联合技术委员会1-小组委员会6实际的权威是ASN.1规范本身，但目前SC6是有权解释其含义的委员会。
Declaration of structure:
结构声明：
The NSS portion of the identifier follows the string encoding rules found in RFC 1778 Section 2.15 [3] which specifies a series of digits separated by a period with the most significant digit being at the left and the least significant being at the right.
标识符的NSS部分遵循RFC 1778第2.15[3]节中的字符串编码规则，该规则规定了一系列由一个句点分隔的数字，其中最高有效位在左侧，最低有效位在右侧。
No changes are anticipated since Object Identifiers are fairly simple and have been standardized with no changes for many years.
由于对象标识符相当简单，并且多年来一直在标准化，没有任何更改，因此预计不会发生任何更改。
Relevant ancillary documentation:
相关辅助文件：
Relevant documentation can be found in X.660/Amd 2 | ISO/IEC 9834-1/Amd 2 [2].
相关文件见X.660/Amd 2 | ISO/IEC 9834-1/Amd 2[2]。
Identifier uniqueness considerations:
标识符唯一性注意事项：
The rules for assignment of OIDs requires that each OID be unique to the OID space and that it cannot be reassigned or reused. By reference this URN namespace inherents those rules.
OID分配规则要求每个OID对于OID空间是唯一的，并且不能重新分配或重用。通过引用，此URN命名空间继承了这些规则。
Identifier persistence considerations:
标识符持久性注意事项：
The rules concerning the use of OIDs requires that they not be reused once assigned. By reference this URN namespace inherents those rules.
关于OID使用的规则要求，一旦分配OID，就不能重复使用OID。通过引用，此URN命名空间继承了这些规则。
Process of identifier assignment:
标识符分配过程：
Once an OID is assigned to some entity, that entity can then create and assign new OIDs below that particular OID. There are multiple entities that assign new OIDs to the general public. The top three levels are pre-assigned as follows:
将OID分配给某个实体后，该实体可以在该特定OID下创建并分配新的OID。有多个实体向公众分配新的OID。前三个级别预先分配如下：
0 - ITU-T assigned 1 - ISO assigned 2 - Joint ISO/ITU-T assignment
0-ITU-T分配1-ISO分配2-ISO/ITU-T联合分配
several assigned OIDs that are of importance to the Internet are:
对互联网非常重要的几个指定OID包括：
1.3.6.1 - the Internet OID 1.3.6.1.4.1 - IANA-assigned company OIDs, used for private MIBs and such things
1.3.6.1 -互联网OID 1.3.6.1.4.1-IANA分配的公司OID，用于私有MIB等
Process of identifier resolution:
标识符解析过程：
At this time no resolution mechanism is defined.
目前尚未定义任何解析机制。
Rules for Lexical Equivalence:
词汇对等规则：
OIDs are composed of multiple occurrences of digits and the "." character. Lexical equivalence is achieved by exact string match.
OID由多次出现的数字和“.”字符组成。词汇对等是通过精确的字符串匹配来实现的。
Conformance with URN Syntax:
符合URN语法：
There are no additional characters reserved.
没有保留其他字符。
Validation mechanism:
验证机制：
None.
没有一个
Scope:
范围：
Global
全球的
The following examples are taken from the example OIDs from the Introduction:
以下示例摘自引言中的示例OID：
urn:oid:1.3.6.1
urn:oid:1.3.6.1.4.1
urn:oid:1.3.6.1.2.1.27
URN:OID:0.9.2342.19200300.100.4
urn:oid:1.3.6.1
urn:oid:1.3.6.1.4.1
urn:oid:1.3.6.1.2.1.27
URN:OID:0.9.2342.19200300.100.4
None not already inherent to using unverifiable OIDs
使用无法验证的OID时还没有固有的特性
The author would like to thank Harald Alvestrand for the use of his OID database as a source for examples and references.
作者要感谢Harald Alvestrand使用他的OID数据库作为示例和参考资料的来源。
References
工具书类
[1] Moats, R., "URN Syntax", RFC 2141, May 1997.
[1] 护城河，R.，“瓮语法”，RFC 21411997年5月。
[2] CCITT, "Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN.1)", CCITT Recommendation X.209, January 1988.
[2] CCITT，“抽象语法符号1（ASN.1）基本编码规则规范”，CCITT建议X.209，1988年1月。
[3] Howes, T., Kille, S., Yeong, W. and C. Robbins, "The String Representation of Standard Attribute Syntaxes", RFC 1778, March 1995.
[3] Howes，T.，Kille，S.，Yeong，W.和C.Robbins，“标准属性语法的字符串表示”，RFC 17781995年3月。
Author's Address
作者地址
Michael Mealling Network Solutions, Inc. 505 Huntmar Park Drive Herndon, VA 22070 US
迈克尔·米林网络解决方案公司，美国弗吉尼亚州亨特马公园大道505号，邮编：22070
Phone: +1 770 935 5492
EMail: michaelm@netsol.com
URI: http://www.netsol.com
Phone: +1 770 935 5492
EMail: michaelm@netsol.com
URI: http://www.netsol.com
Full Copyright Statement
完整版权声明
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编辑功能的资金目前由互联网协会提供。