Internet Engineering Task Force (IETF) F. Dijkstra
Request for Comments: 6453 SARA
Category: Informational R. Hughes-Jones
ISSN: 2070-1721 DANTE
December 2011
Internet Engineering Task Force (IETF) F. Dijkstra
Request for Comments: 6453 SARA
Category: Informational R. Hughes-Jones
ISSN: 2070-1721 DANTE
December 2011
A URN Namespace for the Open Grid Forum (OGF)
开放网格论坛（OGF）的URN命名空间
Abstract
摘要
This document describes a URN (Uniform Resource Name) namespace that is engineered by the Open Grid Forum (OGF) for naming persistent resources.
本文档描述了开放网格论坛（OGF）为命名持久资源而设计的URN（统一资源名称）命名空间。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非IESG批准的所有文件都适用于任何级别的互联网标准；见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6453.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6453.
Copyright Notice
版权公告
Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2011 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction ....................................................2
1.1. Requirements Language ......................................2
2. URN Specification for "ogf" Namespace ID (NID) ..................3
2.1. Namespace ID ...............................................3
2.2. Registration Information ...................................3
2.3. Declared Registrant of the Namespace .......................3
2.4. Declaration of Syntactic Structure .........................3
2.5. Relevant Ancillary Documentation ...........................4
2.6. Identifier Uniqueness Considerations .......................4
2.7. Identifier Persistence Considerations ......................4
2.8. Process of Identifier Assignment ...........................5
2.9. Process of Identifier Resolution ...........................5
2.10. Rules for Lexical Equivalence .............................5
2.11. Conformance with URN Syntax ...............................5
2.12. Validation Mechanism ......................................6
2.13. Scope .....................................................6
3. Examples (Informative) ..........................................6
4. Namespace Considerations ........................................6
5. Community Considerations ........................................7
6. Security Considerations .........................................7
7. IANA Considerations .............................................7
8. Acknowledgements ................................................7
9. References ......................................................8
9.1. Normative References .......................................8
9.2. Informative References .....................................8
1. Introduction ....................................................2
1.1. Requirements Language ......................................2
2. URN Specification for "ogf" Namespace ID (NID) ..................3
2.1. Namespace ID ...............................................3
2.2. Registration Information ...................................3
2.3. Declared Registrant of the Namespace .......................3
2.4. Declaration of Syntactic Structure .........................3
2.5. Relevant Ancillary Documentation ...........................4
2.6. Identifier Uniqueness Considerations .......................4
2.7. Identifier Persistence Considerations ......................4
2.8. Process of Identifier Assignment ...........................5
2.9. Process of Identifier Resolution ...........................5
2.10. Rules for Lexical Equivalence .............................5
2.11. Conformance with URN Syntax ...............................5
2.12. Validation Mechanism ......................................6
2.13. Scope .....................................................6
3. Examples (Informative) ..........................................6
4. Namespace Considerations ........................................6
5. Community Considerations ........................................7
6. Security Considerations .........................................7
7. IANA Considerations .............................................7
8. Acknowledgements ................................................7
9. References ......................................................8
9.1. Normative References .......................................8
9.2. Informative References .....................................8
The Open Grid Forum (OGF) is a standardisation development organisation in the field of distributed computing. The OGF produces documents such as working drafts, specifications, and schemata. For more information, see <http://www.ogf.org/>.
开放网格论坛（OGF）是分布式计算领域的标准化开发组织。OGF生成工作草案、规范和模式等文档。有关详细信息，请参阅<http://www.ogf.org/>.
Working groups in the OGF community have expressed the need for global, distributed, persistent identifiers in working drafts and standards. Motivated by this need, the OGF would like to assign URNs to some resources in order to retain unique, permanent, location-independent names for them.
OGF社区的工作组已经表示需要在工作草案和标准中使用全局、分布式、持久的标识符。出于这种需要，OGF希望将URN分配给某些资源，以便为它们保留唯一、永久、位置独立的名称。
This namespace specification is for a formal namespace.
此名称空间规范适用于正式名称空间。
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 [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
"ogf" (where "ogf" is an acronym for "Open Grid Forum").
“ogf”（其中“ogf”是“开放网格论坛”的首字母缩写）。
Registration Version Number: 1 Registration Date: December 2011
注册版本号：1注册日期：2011年12月
Technical Director Open Grid Forum P.O. Box 1738 Muncie, Indiana 47308 USA http://www.ogf.org/ EMail: urn@ogf.org
美国印第安纳州芒西市1738号邮箱开放电网论坛技术总监47308http://www.ogf.org/ 电邮：urn@ogf.org
The position of Technical Director is currently fulfilled by Joel Replogle.
技术总监的职位目前由Joel Replogle担任。
The formal syntax definitions below are given in ABNF [RFC5234].
ABNF[RFC5234]中给出了以下正式语法定义。
The namespace-specific string (NSS) in the urn:ogf names hierarchy begins with a subnamespace identifier (SNID), followed by a delimiter and a subnamespace-dependent string
urn:ogf names层次结构中的特定于名称空间的字符串（NSS）以子名称空间标识符（SNID）开头，后跟分隔符和子名称空间相关字符串
OGF-URN = "urn:ogf:" SNID ":" SUBNAMESPACE-SPECIFIC-STRING
OGF-URN = "urn:ogf:" SNID ":" SUBNAMESPACE-SPECIFIC-STRING
where <SNID> is a unique subnamespace identifier for the specification, and <SUBNAMESPACE-SPECIFIC-STRING> is a unique identifier within the subnamespace identifier scope.
其中，<SNID>是规范的唯一子名称空间标识符，<subnamespace-SPECIFIC-STRING>是子名称空间标识符范围内的唯一标识符。
<SNID> has the same syntax as a <NID> as defined in [RFC2141]:
<SNID>与[RFC2141]中定义的<NID>具有相同的语法：
SNID = ( ALPHA / DIGIT ) *31( ALPHA / DIGIT / "-" )
SNID = ( ALPHA / DIGIT ) *31( ALPHA / DIGIT / "-" )
ALPHA and DIGIT are defined in Appendix B of [RFC5234].
[RFC5234]附录B中定义了字母和数字。
The Technical Director at OGF (or their successors) assigns SNIDs.
OGF的技术总监（或其继任者）指派SNID。
The syntax of <SUBNAMESPACE-SPECIFIC-STRING> is dependent on the <SNID> and MUST be defined by a Grid Forum Document [GFD.1]. This document does not pose any additional restrictions to the <SUBNAMESPACE-SPECIFIC-STRING> other than what is defined in the NSS syntax as defined by [RFC2141] or its successor:
<SUBNAMESPACE-SPECIFIC-STRING>的语法取决于<SNID>，必须由网格论坛文档[GFD.1]定义。除[RFC2141]或其后续版本在NSS语法中定义的内容外，本文档对<SUBNAMESPACE-SPECIFIC-STRING>没有任何其他限制：
SUBNAMESPACE-SPECIFIC-STRING = 1*<URN chars>
SUBNAMESPACE-SPECIFIC-STRING = 1*<URN chars>
<URN chars> is defined in Section 2.2 of [RFC2141].
[RFC2141]第2.2节定义了<URN chars>。
The Technical Director at OGF (or their successors) will keep a list of assigned subnamespace identifiers and associated documentation at <http://www.ogf.org/urn/> [URN-OGF].
OGF的技术总监（或其继任者）将在<http://www.ogf.org/urn/>[URN-OGF]。
The procedures regarding how to register a subnamespace identifier are described in [GFD.191] and can also be found at the above Website.
[GFD.191]中描述了有关如何注册子名称空间标识符的程序，也可以在上述网站上找到。
Identifier uniqueness will be enforced by the Technical Director of the Open Grid Forum.
标识符唯一性将由开放网格论坛的技术总监执行。
The OGF Technical Director may sub-delegate part of the namespace to third parties. It will not be permissible, neither by the OGF nor any third party, to re-assign previously assigned URNs. A practical consequence is that a previously assigned subnamespace cannot be re-assigned, unless additional arrangements are made to prevent identifier re-assignments.
OGF技术总监可以将命名空间的一部分再委托给第三方。OGF或任何第三方都不允许重新分配以前分配的URN。一个实际的结果是，以前分配的子名称空间不能重新分配，除非作出额外安排以防止重新分配标识符。
The Technical Director will only assign subnamespace identifiers for persistent resources.
技术主管将仅为持久性资源分配子名称空间标识符。
In order to enforce identifier persistence for individual resources, each document defining subnamespace identifiers MUST contain a section on the type of resource that is specified (e.g., whether a URN in the subnamespace identifies a specific version of a resource, the latest version of a resource, a specific manifestation, or a more general concept).
为了强制各个资源的标识符持久性，定义子名称空间标识符的每个文档都必须包含指定资源类型的部分（例如，子名称空间中的URN是否标识资源的特定版本、资源的最新版本、特定表现形式或更一般的概念）。
The namespace identifier "ogf" MUST NOT change, even if the Open Grid Forum changes its name or is disbanded.
名称空间标识符“ogf”不得更改，即使开放网格论坛更改其名称或解散。
Assignment of subnamespace identifiers is limited to the OGF and those authorities that are specifically designated by the OGF Technical Director of the OGF. The OGF may assign portions of its namespace (specifically, those under designated subnamespace identifiers) for assignment by third parties.
子名称空间标识符的分配仅限于OGF和OGF技术总监特别指定的机构。OGF可以为第三方分配其命名空间的部分（特别是指定子命名空间标识符下的部分）。
The details of this process are specified in [GFD.191].
[GFD.191]中规定了该过程的详细信息。
The syntax and semantics of each subnamespace MUST be defined by a Grid Forum Document [GFD.1] before the corresponding SNID is assigned.
在分配相应的SNID之前，每个子名称空间的语法和语义必须由网格论坛文档[GFD.1]定义。
The OGF namespace is not currently listed with a Resolution Discovery System (RDS), but nothing about the namespace prohibits the future definition of appropriate resolution methods or listing with an RDS.
OGF名称空间当前未与解析发现系统（RDS）一起列出，但名称空间的任何内容都不禁止将来定义适当的解析方法或与RDS一起列出。
The OGF will maintain an index of all subnamespace identifiers on its Website <http://www.ogf.org/urn/>. This list may refer to known Resolution Discovery Systems.
OGF将在其网站上维护所有子命名空间标识符的索引<http://www.ogf.org/urn/>. 此列表可能涉及已知的分辨率发现系统。
The <SNID> part of URNs in the OGF hierarchy is case insensitive. Thus, the <SNID> MUST be case normalised before comparison.
OGF层次结构中URN的<SNID>部分不区分大小写。因此，<SNID>必须在比较之前进行案例标准化。
The rules for lexical equivalence of the <SUBNAMESPACE-SPECIFIC-STRING> part of URNs in the OGF hierarchy is specific for each SNID and MUST be defined when a SNID is assigned by the OGF Technical Director. These definitions MUST include information about case sensitivity, and in the case of %-escaped octets, MUST define the exact normalisation to be used (e.g., interpret as octet, interpret as UTF-8, specify type of Unicode normalisation factor, etc.).
OGF层次结构中URN的<SUBNAMESPACE-SPECIFIC-STRING>部分的词汇等效规则对于每个SNID都是特定的，必须在OGF技术总监分配SNID时定义。这些定义必须包括有关大小写敏感度的信息，对于转义的八位字节，必须定义要使用的精确归一化（例如，解释为八位字节、解释为UTF-8、指定Unicode归一化因子的类型等）。
The intention of this document is to only restrict the syntax of the <SNID>. The syntax of the <SUBNAMESPACE-SPECIFIC-STRING> follows the general syntax of a URN:
本文档的目的只是限制<SNID>的语法。<SUBNAMESPACE-SPECIFIC-STRING>的语法遵循URN的一般语法：
SUBNAMESPACE-SPECIFIC-STRING = 1*<URN chars>
SUBNAMESPACE-SPECIFIC-STRING = 1*<URN chars>
Documents defining a subnamespace identifier SHOULD specify further syntactic restrictions in <SUBNAMESPACE-SPECIFIC-STRING>. It is RECOMMENDED that these documents forbid the assignment of URNs containing characters in the <reserved> set ("%", "/", "?", and "#") as defined in [RFC2141]. This is in accordance with Section 2.2 of [RFC3986].
定义子名称空间标识符的文档应在<subnamespace-SPECIFIC-STRING>中指定进一步的语法限制。建议这些文件禁止分配包含[RFC2141]中定义的<reserved>集合（“%”、“/”、“？”和“#”）中字符的URN。这符合[RFC3986]第2.2节的规定。
For forward compatibility, it is RECOMMENDED that software implementations that don't validate subnamespace-specific strings validate the syntax according to the generic rules for validating URIs, as defined in [RFC3986]. URIs may contain all characters defined in <URN chars>, including the characters in <reserved> (albeit they have a special meaning), as well as the characters "&" and "~".
为了向前兼容，建议不验证子名称空间特定字符串的软件实现根据[RFC3986]中定义的验证URI的通用规则验证语法。URI可能包含<URN chars>中定义的所有字符，包括<reserved>中的字符（尽管它们具有特殊含义），以及字符“&”和“~”。
The validation mechanism of URNs in the OGF hierarchy is specific for each SNID and SHOULD be defined when a SNID is assigned by the OGF Technical Director.
OGF层次结构中URN的验证机制对于每个SNID都是特定的，应该在OGF技术总监分配SNID时定义。
URNs in the OGF hierarchy without an assigned SNID are considered to be invalid.
OGF层次结构中没有指定SNID的URN被视为无效。
Global URNs are relevant for the distributed computing community in general, and the Open Grid Forum in particular.
全局URN通常与分布式计算社区相关，尤其是开放网格论坛。
Since no subnamespace identifiers have been defined yet, no actual examples can be given. Therefore, the following examples are not guaranteed to be real or even syntactically correct.
由于尚未定义子名称空间标识符，因此无法给出实际示例。因此，以下示例不能保证是真实的，甚至不能保证语法正确。
Grid Forum Documents defining the "gfd" and "network" subnamespace identifiers may give the following examples.
定义“gfd”和“网络”子名称空间标识符的网格论坛文件可能给出以下示例。
o urn:ogf:gfd:136
o urn:ogf:gfd:136
o urn:ogf:network:canarie.ca:kisti-uninett-glif-001
o urn:ogf:network:canarie.ca:kisti-uninett-glif-001
The Open Grid Forum (OGF) is a standardisation development organisation in the field of distributed computing.
开放网格论坛（OGF）是分布式计算领域的标准化开发组织。
The use of the OGF hierarchy is expected to be broad, including but not limited to usage for:
OGF层次结构的使用预计将是广泛的，包括但不限于以下用途：
o Grid Forum Documents
o 网格论坛文件
o XML (Extensible Markup Language) Schemata
o XML（可扩展标记语言）模式
o RDF (Resource Description Framework) Schemata
o RDF（资源描述框架）模式
The Open Grid Forum is dedicated to openly publishing all technical documentation related to URNs in the OGF hierarchy and allowing unlimited distribution of these documents.
开放网格论坛致力于公开发布OGF层次结构中与URN相关的所有技术文档，并允许不受限制地分发这些文档。
Members of the distributed computing community will benefit from persistent and globally unique identifiers for use in protocols developed by the Open Grid Forum.
分布式计算社区的成员将受益于开放网格论坛开发的协议中使用的持久和全球唯一标识符。
Practical use of the urn:ogf namespace has been detected, and a formal registration will allow the Open Grid Forum to document this usage and enforce technical review of current practices.
已经检测到urn:ogf名称空间的实际使用，正式注册将允许开放网格论坛记录这种使用，并强制对当前实践进行技术审查。
There are no additional security considerations other than those normally associated with the use and resolution of URNs in general, which are described in [RFC1737], [RFC2141], and [RFC3406].
除了[RFC1737]、[RFC2141]和[RFC3406]中描述的通常与URN的使用和解析相关的安全注意事项外，没有其他安全注意事项。
It is recommended that implementers check the OGF registry and documentation [URN-OGF] before assuming that a given identifier is valid or has a certain meaning.
建议实施者在假设给定标识符有效或具有特定含义之前，检查OGF注册表和文档[URN-OGF]。
IANA has registered the "ogf" namespace identifier (NID) with a reference to this document in the "Formal URN Namespaces" sub-registry [RFC3406] of the "Uniform Resource Names (URN) Namespaces" registry [URN-NAMESPACES].
IANA已在“统一资源名称（URN）名称空间”注册表[URN-Namespaces]的“正式URN名称空间”子注册表[RFC3406]中注册了“ogf”名称空间标识符（NID），并引用了本文档。
The template and useful examples from [RFC3406] formed the basis for this document. The authors would like to thank Joel Replogle and Andre Mersky for setting up the urn:ogf subnamespace registry. Jeroen van der Ham, Peter Saint-Andre, and Mykyta Yevstifeyev proofread this document and provided valuable feedback.
[RFC3406]中的模板和有用示例构成了本文件的基础。作者要感谢Joel Replogle和Andre Mersky建立urn:ogf subnamespace注册表。Jeroen van der Ham、Peter Saint Andre和Mykyta Yevstifeyev校对了该文件并提供了宝贵的反馈。
[GFD.191] Dijkstra, F., Hughes-Jones, R., Newby, G., and J. Replogle, "Procedure for Registration of Subnamespace Identifiers in the URN:OGF Hierarchy", GFD 191, December 2011, <http://www.ogf.org/documents/GFD.191.pdf>.
[GFD.191]Dijkstra，F.，Hughes Jones，R.，Newby，G.，和J.Replogle，“在URN:OGF层次结构中注册子名称空间标识符的程序”，GFD 191，2011年12月<http://www.ogf.org/documents/GFD.191.pdf>.
[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月。
[RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997.
[RFC2141]Moats，R.，“瓮语法”，RFC 21411997年5月。
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005.
[RFC3986]Berners Lee，T.，Fielding，R.，和L.Masinter，“统一资源标识符（URI）：通用语法”，STD 66，RFC 3986，2005年1月。
[RFC5234] Crocker, D., Ed., and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, January 2008.
[RFC5234]Crocker，D.，Ed.，和P.Overell，“语法规范的扩充BNF:ABNF”，STD 68，RFC 5234，2008年1月。
[GFD.1] Catlett, C., "GGF Document Series", GFD 1, April 2002, <http://www.ogf.org/documents/GFD.1.pdf>.
[GFD.1]Catlett，C.，“GGF文件系列”，GFD 11902年4月<http://www.ogf.org/documents/GFD.1.pdf>.
[RFC1737] Sollins, K. and L. Masinter, "Functional Requirements for Uniform Resource Names", RFC 1737, December 1994.
[RFC1737]Sollins，K.和L.Masinter，“统一资源名称的功能要求”，RFC 1737，1994年12月。
[RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, "Uniform Resource Names (URN) Namespace Definition Mechanisms", BCP 66, RFC 3406, October 2002.
[RFC3406]Daigle，L.，van Gulik，D.，Iannella，R.，和P.Faltstrom，“统一资源名称（URN）命名空间定义机制”，BCP 66，RFC 3406，2002年10月。
[URN-NAMESPACES] IANA, "Uniform Resource Names (URN) Namespaces", <http://www.iana.org/>.
[URN-NAMESPACES]IANA，“统一资源名称（URN）命名空间”<http://www.iana.org/>.
[URN-OGF] Open Grid Forum, "URN:OGF Hierarchy Registry and Documentation", <http://www.ogf.org/urn/>.
[URN-OGF]开放网格论坛，“URN:OGF层次结构注册表和文档”<http://www.ogf.org/urn/>.
Authors' Addresses
作者地址
Freek Dijkstra SARA Science Park 121 Amsterdam 1098 XG NL
Freek Dijkstra SARA科技园121阿姆斯特丹1098 XG NL
EMail: Freek.Dijkstra@sara.nl
EMail: Freek.Dijkstra@sara.nl
Richard Hughes-Jones DANTE City House 126-130 Hills Road Cambridge CB2 1PQ UK
Richard Hughes Jones DANTE City House 126-130 Hills Road Cambridge CB2 1PQ UK
EMail: Richard.Hughes-Jones@dante.net
EMail: Richard.Hughes-Jones@dante.net