Internet Engineering Task Force (IETF) S. Martin
Request for Comments: 7853 S. Tuecke
Category: Informational B. McCollam
ISSN: 2070-1721 M. Lidman
University of Chicago
May 2016
Internet Engineering Task Force (IETF) S. Martin
Request for Comments: 7853 S. Tuecke
Category: Informational B. McCollam
ISSN: 2070-1721 M. Lidman
University of Chicago
May 2016
A URN Namespace for Globus
Globus的URN名称空间
Abstract
摘要
This document describes a URN (Uniform Resource Name) namespace to be used by Globus for naming persistent resources.
本文档描述了Globus用于命名持久资源的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/rfc7853.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7853.
Copyright Notice
版权公告
Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2016 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
2. Specification Template ........................................ 3
3. Examples (Informative) ........................................ 5
4. Namespace Considerations ...................................... 5
5. Community Considerations ...................................... 6
6. Security Considerations ....................................... 6
7. IANA Considerations ........................................... 6
8. Normative References .......................................... 6
Acknowledgments .................................................. 7
Authors' Addresses ............................................... 7
1. Introduction .................................................. 2
2. Specification Template ........................................ 3
3. Examples (Informative) ........................................ 5
4. Namespace Considerations ...................................... 5
5. Community Considerations ...................................... 6
6. Security Considerations ....................................... 6
7. IANA Considerations ........................................... 6
8. Normative References .......................................... 6
Acknowledgments .................................................. 7
Authors' Addresses ............................................... 7
Globus (https://www.globus.org) is a software-as-a-service provider that develops and operates services and tools for the global research and education community.
球状体(https://www.globus.org)是一家软件即服务提供商，为全球研究和教育界开发和运营服务和工具。
Globus provides multiple services for users across many institutions, primarily for research driven by high-performance computing. Globus creates unique identifiers that will persist in external systems and must be identifiable as references to Globus entities.
Globus为许多机构的用户提供多种服务，主要用于由高性能计算驱动的研究。Globus创建唯一标识符，该标识符将在外部系统中持久存在，并且必须作为对Globus实体的引用进行标识。
To address this need, this document requests that a formal URN space type be assigned as described in Section 4.3 of [RFC3406].
为了满足这一需求，本文件要求按照[RFC3406]第4.3节中的描述分配正式的URN空间类型。
Namespace ID:
命名空间ID:
globus
球状体
Registration Information:
注册资料：
Version 1 Date: 2016-03-18
版本1日期：2016-03-18
Declared Registrant of the Namespace:
已声明命名空间的注册人：
Globus Project Lead 401 N Michigan Ave Suite 900 Chicago, Illinois 60611 USA
Globus项目负责人401 N密歇根大道900号套房伊利诺伊州芝加哥60611
Email: tuecke@globus.org
Email: tuecke@globus.org
The position of Globus Project Lead is currently filled by Steve Tuecke.
Globus项目负责人的职位目前由Steve Tuecke担任。
Declaration of Syntactic Structure:
句法结构声明：
The Namespace Specific String (NSS) of all URNs that use the "globus" NID shall have the following structure:
使用“globus”NID的所有URN的命名空间特定字符串（NSS）应具有以下结构：
<URN> ::= "urn:" "globus" ":" <NSS>
<URN> ::= "urn:" "globus" ":" <NSS>
<NSS> ::= <SNID> | <SNID> ":" <subnamespace-specific-string>
<NSS> ::= <SNID> | <SNID> ":" <subnamespace-specific-string>
<SNID> ::= 1*<non-colon-chars>
<SNID> ::= 1*<non-colon-chars>
<subnamespace-specific-string> ::= 1*<URN chars>
<subnamespace-specific-string> ::= 1*<URN chars>
<non-colon-chars> ::= <non-colon-trans> | "%" <hex> <hex>
<non-colon-chars> ::= <non-colon-trans> | "%" <hex> <hex>
<non-colon-trans> ::= <upper> | <lower> | <number> |
<non-colon-other>
<non-colon-trans> ::= <upper> | <lower> | <number> |
<non-colon-other>
<non-colon-other> ::= "(" | ")" | "+" | "," | "-" | "." | "=" |
"@" | ";" | "$" | "_" | "!" | "*" | "'"
<non-colon-other> ::= "(" | ")" | "+" | "," | "-" | "." | "=" |
"@" | ";" | "$" | "_" | "!" | "*" | "'"
The "SNID" is the top-level segment of the NSS. It is a required US-ASCII string, subject to the above syntax, that conforms to the URN syntax requirements (see [RFC2141]). It identifies a category
“SNID”是NSS的顶级部分。这是一个必需的US-ASCII字符串，符合上述语法，符合URN语法要求（请参见[RFC2141]）。它标识一个类别
of Globus entities, often associated with a particular Globus service. For example "auth" could be used as an SNID for identifiers generated by the Globus authentication and authorization service (Globus Auth).
指Globus实体，通常与特定Globus服务关联。例如，“auth”可以用作Globus身份验证和授权服务（Globus auth）生成的标识符的SNID。
The "subnamespace-specific-string" is an optional US-ASCII string and second-level segment of the NSS, belonging to the "SNID" context, subject to the above syntax and conformant to the URN syntax requirements (see [RFC2141]). "subnamespace-specific-string" identifies a category of thing within that Globus service, such as "scope:transfer.api.globus.org:all"
“子名称空间特定字符串”是可选的US-ASCII字符串和NSS的第二级段，属于“SNID”上下文，受上述语法约束，并符合URN语法要求（参见[RFC2141]）。“子名称空间特定字符串”标识Globus服务中的一个类别，例如“scope:transfer.api.Globus.org:all”
Relevant Ancillary Documentation:
相关辅助文件：
None.
没有一个
Identifier Uniqueness Considerations:
标识符唯一性注意事项：
Identifier uniqueness will be enforced by the Globus Project Lead. The Globus Project Lead may sub-delegate part of the namespace to third parties. It will not be permissible, neither by the Globus Project Lead nor any third party, to reassign previously assigned URNs. A practical consequence is that a previously assigned subnamespace cannot be reassigned, unless additional arrangements are made to prevent identifier reassignments.
Globus项目负责人将强制执行标识符唯一性。Globus项目负责人可以将命名空间的一部分再委托给第三方。Globus项目负责人或任何第三方都不允许重新分配以前分配的URN。一个实际的结果是，以前分配的子名称空间无法重新分配，除非作出额外安排以防止重新分配标识符。
Identifier Persistence Considerations:
标识符持久性注意事项：
Identifiers will never be reassigned, but in some circumstances they may be invalidated by the Globus Project Lead or by a third party.
标识符永远不会重新分配，但在某些情况下，它们可能会被Globus项目负责人或第三方作废。
Process of Identifier Assignment:
标识符分配过程：
Assignment of subnamespace identifiers is limited to the Globus Project Lead and those authorities that are specifically designated by the Globus Project Lead. The Globus Project Lead may assign portions of the globus namespace (specifically, those under designated subnamespace identifiers) for assignment by third parties.
子名称空间标识符的分配仅限于Globus项目负责人和Globus项目负责人特别指定的机构。Globus项目负责人可以分配Globus命名空间的部分（特别是指定子命名空间标识符下的部分），以供第三方分配。
Process of Identifier Resolution:
标识符解析过程：
None currently.
目前没有。
Future versions of this document may define resources that can be used to resolve Globus identifiers.
本文档的未来版本可能会定义可用于解析Globus标识符的资源。
Rules for Lexical Equivalence:
词汇对等规则：
No additional rules beyond those specified in RFC 2141.
除RFC 2141中规定的规则外，没有其他规则。
Conformance with URN Syntax:
符合URN语法：
No special considerations.
没有特别考虑。
Validation Mechanism:
验证机制：
None currently.
目前没有。
Future versions of this document may define resources that can be used to validate Globus identifiers.
本文档的未来版本可能会定义可用于验证Globus标识符的资源。
Scope:
范围：
Global.
全球的
The following examples are based on plans for the Globus URN. They are therefore not guaranteed to be valid.
以下示例基于Globus URN的计划。因此，它们不能保证有效。
The Globus Auth service defines the "auth" SNID and contains the following URNs:
Globus Auth服务定义“Auth”SNID，并包含以下URN：
o urn:globus:auth:scope:transfer.api.globus.org:all
o urn:globus:auth:scope:transfer.api.globus.org:all
o urn:globus:auth:grants:dependent_token
o urn:globus:auth:grants:dependent_令牌
A hypothetical service, the Globus Groups service, would have a distinct SNID. If that SNID were "groups", it might have URNs such as the following:
一个假设的服务，Globus Group服务，将有一个独特的SNID。如果该SNID是“组”，它可能有如下骨灰盒：
o urn:globus:groups:group:669b572e-9de4-11e5-966e-3c970e0c9cc4
o urn:globus:组：组：669b572e-9de4-11e5-966e-3c970e0c9cc4
o urn:globus:groups:memberships:72e1c6c6-9de4-11e5-966e-3c970e0c9cc4
o urn:globus:groups:memberships:72e1c6c6-9de4-11e5-966e-3c970e0c9cc4
The current set of existing IANA namespaces are insufficient because Globus will be creating unique identifiers that will persist in the external system; these identifiers must be identifiable as references to Globus entities.
现有的一组IANA名称空间不足，因为Globus将创建唯一标识符，该标识符将在外部系统中持久存在；这些标识符必须可识别为对Globus实体的引用。
The use of the Globus namespace is expected to be broad, including but not limited to usage for:
Globus命名空间的使用范围预计会很广，包括但不限于以下用途：
o OAuth2 scopes (see [RFC6749])
o OAuth2作用域（请参见[RFC6749]）
o OAuth2 custom extension grants
o OAuth2自定义扩展授权
o Entity identification for Globus Services
o Globus服务的实体标识
Members of the Globus community will benefit from persistent and globally unique identifiers for use in software and in conformance with protocols developed and used by Globus and third-party collaborators.
Globus社区的成员将受益于在软件中使用的持久且全球唯一的标识符，并符合Globus和第三方合作者开发和使用的协议。
There are no special meanings for characters in the NSS. Thus, 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] and [RFC2141].
NSS中的字符没有特殊含义。因此，除了[RFC1737]和[RFC2141]中描述的通常与URN的使用和解析相关的安全注意事项外，没有其他安全注意事项。
IANA has registered the "globus" namespace identifier (NID) in the "Formal URN Namespaces" registry located at <http://www.iana.org/assignments/urn-namespaces>.
IANA已在位于的“正式URN命名空间”注册表中注册了“globus”命名空间标识符（NID）<http://www.iana.org/assignments/urn-namespaces>.
[RFC1737] Sollins, K. and L. Masinter, "Functional Requirements for Uniform Resource Names", RFC 1737, DOI 10.17487/RFC1737, December 1994, <http://www.rfc-editor.org/info/rfc1737>.
[RFC1737]Sollins，K.和L.Masinter，“统一资源名称的功能要求”，RFC 1737，DOI 10.17487/RFC1737，1994年12月<http://www.rfc-editor.org/info/rfc1737>.
[RFC2141] Moats, R., "URN Syntax", RFC 2141, DOI 10.17487/RFC2141, May 1997, <http://www.rfc-editor.org/info/rfc2141>.
[RFC2141]护城河，R.，“瓮语法”，RFC 2141，DOI 10.17487/RFC2141，1997年5月<http://www.rfc-editor.org/info/rfc2141>.
[RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, "Uniform Resource Names (URN) Namespace Definition Mechanisms", BCP 66, RFC 3406, DOI 10.17487/RFC3406, October 2002, <http://www.rfc-editor.org/info/rfc3406>.
[RFC3406]Daigle，L.，van Gulik，D.，Iannella，R.，和P.Faltstrom，“统一资源名称（URN）命名空间定义机制”，BCP 66，RFC 3406，DOI 10.17487/RFC3406，2002年10月<http://www.rfc-editor.org/info/rfc3406>.
[RFC6749] Hardt, D., Ed., "The OAuth 2.0 Authorization Framework", RFC 6749, DOI 10.17487/RFC6749, October 2012, <http://www.rfc-editor.org/info/rfc6749>.
[RFC6749]Hardt，D.，Ed.“OAuth 2.0授权框架”，RFC 6749，DOI 10.17487/RFC6749，2012年10月<http://www.rfc-editor.org/info/rfc6749>.
Acknowledgments
致谢
The authors would like to thank Stephen Rosen and Vas Vasiliadis for proofreading this document and providing valuable feedback.
作者感谢Stephen Rosen和Vas Vasiliadis校对本文件并提供宝贵反馈。
Authors' Addresses
作者地址
Stuart Martin University of Chicago 401 N Michigan Ave Suite 900 Chicago, Illinois 60611 United States
斯图亚特马丁芝加哥大学401 N密歇根大道套房900伊利诺斯芝加哥60611美国
Email: sjmartin@uchicago.edu
Email: sjmartin@uchicago.edu
Steve Tuecke University of Chicago 401 N Michigan Ave Suite 900 Chicago, Illinois 60611 United States
史提夫Tuekk芝加哥大学401 N密歇根大道套房900伊利诺斯芝加哥60611美国
Email: tuecke@globus.org
Email: tuecke@globus.org
Brendan McCollam University of Chicago 401 N Michigan Ave Suite 900 Chicago, Illinois 60611 United States
布伦丹麦考勒姆芝加哥大学401 N密歇根大道套房900伊利诺斯芝加哥60611美国
Email: bmccollam@uchicago.edu
Email: bmccollam@uchicago.edu
Mattias Lidman University of Chicago 401 N Michigan Ave Suite 900 Chicago, Illinois 60611 United States
马蒂亚斯利德曼芝加哥大学401 N密歇根大道套房900伊利诺斯芝加哥60611美国
Email: mattias@uchicago.edu
Email: mattias@uchicago.edu