分享
 
 
 

RFC3001 - A URN Namespace of Object Identifiers

王朝other·作者佚名  2008-05-31
窄屏简体版  字體: |||超大  

Network Working Group M. Mealling

Request for Comments: 3001 Network Solutions, Inc.

Category: Informational November 2000

A URN Namespace of Object Identifiers

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.

Abstract

This document describes a Uniform Resource Names (URN) namespace that

contains Object Identifiers (OIDs).

1. IntrodUCtion

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:

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.

The namespace specification is for a formal namespace.

2. Specification Template

Namespace ID:

"oid" requested.

Registration Information:

Registration Version Number: 1

Registration Date: 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.

Declaration of structure:

The NSS portion of the identifier follows the string encoding

rules found in RFC1778 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.

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].

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.

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.

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:

0 - ITU-T assigned

1 - ISO assigned

2 - Joint ISO/ITU-T assignment

several assigned OIDs that are of importance to the Internet are:

1.3.6.1 - the Internet OID

1.3.6.1.4.1 - IANA-assigned company OIDs, used for private

MIBs and such things

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.

Conformance with URN Syntax:

There are no additional characters reserved.

Validation mechanism:

None.

Scope:

Global

3. Examples

The following examples are taken from the example OIDs from the

Introduction:

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

4. Security Considerations

None not already inherent to using unverifiable OIDs

5. Acknowledgements

The author would like to thank Harald Alvestrand for the use of his

OID database as a source for examples and references.

References

[1] Moats, R., "URN Syntax", RFC2141, May 1997.

[2] CCITT, "Specification of Basic Encoding Rules for Abstract

Syntax Notation One (ASN.1)", CCITT Recommendation X.209,

January 1988.

[3] Howes, T., Kille, S., Yeong, W. and C. Robbins, "The String

Representation of Standard Attribute Syntaxes", RFC1778, March

1995.

Author's Address

Michael Mealling

Network Solutions, Inc.

505 Huntmar Park Drive

Herndon, VA 22070

US

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.

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 RFCEditor function is currently provided by the

Internet Society.

 
 
 
免责声明:本文为网络用户发布,其观点仅代表作者个人观点,与本站无关,本站仅提供信息存储服务。文中陈述内容未经本站证实,其真实性、完整性、及时性本站不作任何保证或承诺,请读者仅作参考,并请自行核实相关内容。
2023年上半年GDP全球前十五强
 百态   2023-10-24
美众议院议长启动对拜登的弹劾调查
 百态   2023-09-13
上海、济南、武汉等多地出现不明坠落物
 探索   2023-09-06
印度或要将国名改为“巴拉特”
 百态   2023-09-06
男子为女友送行,买票不登机被捕
 百态   2023-08-20
手机地震预警功能怎么开?
 干货   2023-08-06
女子4年卖2套房花700多万做美容:不但没变美脸,面部还出现变形
 百态   2023-08-04
住户一楼被水淹 还冲来8头猪
 百态   2023-07-31
女子体内爬出大量瓜子状活虫
 百态   2023-07-25
地球连续35年收到神秘规律性信号,网友:不要回答!
 探索   2023-07-21
全球镓价格本周大涨27%
 探索   2023-07-09
钱都流向了那些不缺钱的人,苦都留给了能吃苦的人
 探索   2023-07-02
倩女手游刀客魅者强控制(强混乱强眩晕强睡眠)和对应控制抗性的关系
 百态   2020-08-20
美国5月9日最新疫情:美国确诊人数突破131万
 百态   2020-05-09
荷兰政府宣布将集体辞职
 干货   2020-04-30
倩女幽魂手游师徒任务情义春秋猜成语答案逍遥观:鹏程万里
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案神机营:射石饮羽
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案昆仑山:拔刀相助
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案天工阁:鬼斧神工
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案丝路古道:单枪匹马
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案镇郊荒野:与虎谋皮
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案镇郊荒野:李代桃僵
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案镇郊荒野:指鹿为马
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案金陵:小鸟依人
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案金陵:千金买邻
 干货   2019-11-12
 
推荐阅读
 
 
 
>>返回首頁<<
 
靜靜地坐在廢墟上,四周的荒凉一望無際,忽然覺得,淒涼也很美
© 2005- 王朝網路 版權所有