Internet Engineering Task Force (IETF) B. Campbell
Request for Comments: 6755 Ping Identity Corp.
Category: Informational H. Tschofenig
ISSN: 2070-1721 Nokia Siemens Networks
October 2012
Internet Engineering Task Force (IETF) B. Campbell
Request for Comments: 6755 Ping Identity Corp.
Category: Informational H. Tschofenig
ISSN: 2070-1721 Nokia Siemens Networks
October 2012
An IETF URN Sub-Namespace for OAuth
OAuth的IETF URN子命名空间
Abstract
摘要
This document establishes an IETF URN Sub-namespace for use with OAuth-related specifications.
本文档建立了一个IETF URN子命名空间，用于OAuth相关规范。
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/rfc6755.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6755.
Copyright Notice
版权公告
Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2012 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. Registration Template ...........................................2
2.1. Example Registration Request ...............................3
3. Security Considerations .........................................3
4. IANA Considerations .............................................3
4.1. IETF URN Sub-Namespace Registration urn:ietf:params:oauth ..4
5. References ......................................................4
5.1. Normative References .......................................4
5.2. Informative Reference ......................................4
Appendix A. Acknowledgements ......................................5
1. Introduction ....................................................2
2. Registration Template ...........................................2
2.1. Example Registration Request ...............................3
3. Security Considerations .........................................3
4. IANA Considerations .............................................3
4.1. IETF URN Sub-Namespace Registration urn:ietf:params:oauth ..4
5. References ......................................................4
5.1. Normative References .......................................4
5.2. Informative Reference ......................................4
Appendix A. Acknowledgements ......................................5
Various extensions and companion specifications to the OAuth 2.0 Authorization Framework [OAUTH-V2] utilize URIs to identify the extension in use or other relevant context. This document creates and registers an IETF URN Sub-namespace, as documented in RFC 3553 [RFC3553], for use with such specifications. The new 'oauth' Sub-namespace is urn:ietf:params:oauth, and OAuth relevant parameters will be established underneath it.
OAuth 2.0授权框架[OAuth-V2]的各种扩展和配套规范利用URI来标识正在使用的扩展或其他相关上下文。本文档创建并注册一个IETF URN子命名空间，如RFC 3553[RFC3553]中所述，用于此类规范。新的“oauth”子名称空间是urn:ietf:params:oauth，与oauth相关的参数将在它下面建立。
If a registrant wishes to have an OAuth URI registered, then a URN of the form urn:ietf:params:oauth:<value> will be requested where <value> is a suitable representation of the functionality or concept being registered.
如果注册人希望注册OAuth URI，则将请求形式为URN:ietf:params:OAuth:<value>的URN，其中<value>是所注册功能或概念的适当表示。
The registration procedure for new entries requires a request in the form of the following template and is "Specification Required" per RFC 5226 [RFC5226].
新条目的注册程序需要以下模板形式的请求，并且按照RFC 5226[RFC5226]的要求为“需要规范”。
URN: The URI that identifies the registered functionality.
URN：标识已注册功能的URI。
Common Name: The name by which the functionality being registered is generally known.
通用名称：注册功能时通常使用的名称。
Change Controller: For Standards Track RFCs, state "IETF". For others, give the name of the responsible party. Other details (e.g., postal address, email address, and home page URI) may also be included.
更改控制器：对于标准跟踪RFC，请注明“IETF”。对于其他人，请提供责任方的名称。还可以包括其他详细信息（例如，邮政地址、电子邮件地址和主页URI）。
Specification Document(s): Reference to the document that specifies the URI, preferably including a URI that can be used to retrieve a copy of the document. An indication of the relevant sections may also be included but is not required.
规范文档：对指定URI的文档的引用，最好包括可用于检索文档副本的URI。也可以包括相关章节的指示，但不需要。
The registration request for the urn:ietf:params:oauth URN Sub-namespace is found in the IANA Considerations section of this document (Section 4).
urn:ietf:params:oauth urn子命名空间的注册请求可在本文档的IANA注意事项部分（第4节）中找到。
The following is an example registration request for a URI underneath the urn:ietf:params:oauth Sub-namespace. The requested URI represents a new OAuth 2.0 grant type.
下面是urn:ietf:params:oauth子命名空间下URI的注册请求示例。请求的URI表示新的OAuth 2.0授权类型。
This is a request to IANA to please register the value "grant-type:example" in the registry urn:ietf:params:oauth established in an IETF URN Sub-namespace for OAuth.
这是对IANA的请求，请在为oauth建立的ietf urn子命名空间中的注册表urn:ietf:params:oauth中注册值“grant type:example”。
o URN: urn:ietf:params:oauth:grant-type:example
o URN:URN:ietf:params:oauth:grant类型：示例
o Common Name: An Example Grant Type for OAuth 2.0
o 公共名称：OAuth 2.0的一个示例授权类型
o Change controller: IETF
o 更改控制器：IETF
o Specification Document: [the document URI]
o 规范文档：[文档URI]
There are no additional security considerations beyond those already inherent to using URNs. Security considerations for URNs in general can be found in RFC 2141 [RFC2141].
除了使用URN固有的安全注意事项外，没有其他安全注意事项。一般而言，URN的安全注意事项可在RFC 2141[RFC2141]中找到。
Any work that is related to OAuth would benefit from familiarity with the security considerations of the OAuth 2.0 Authorization Framework [OAUTH-V2].
熟悉OAuth 2.0授权框架[OAuth-V2]的安全注意事项将有助于任何与OAuth相关的工作。
IANA has created the following:
IANA创建了以下内容：
o The registration of a new IANA URN Sub-namespace, urn:ietf:params:oauth:, per RFC 3553 [RFC3553]. The registration request can be found in Section 4.1 below.
o 根据RFC 3553[RFC3553]注册新的IANA URN子命名空间URN:ietf:params:oauth:。注册申请见下文第4.1节。
o A new registry called the "OAuth URI" registry for URNs subordinate to urn:ietf:params:oauth. The registry "OAuth URI" has been added to a new top-level registry called "OAuth
o 为从属于urn:ietf:params:OAuth的urn创建了一个名为“OAuth URI”的新注册表。注册表“OAuth URI”已添加到名为“OAuth”的新顶级注册表中
Parameters" as defined by [OAUTH-V2]. Instructions for a registrant to request the registration of such a URN are in Section 2.
[OAUTH-V2]定义的“参数”。注册人请求注册此类URN的说明见第2节。
Per RFC 3553 [RFC3553], IANA has registered a new URN Sub-namespace, urn:ietf:params:oauth.
根据RFC3553[RFC3553]，IANA注册了一个新的URN子命名空间URN:ietf:params:oauth。
o Registry name: oauth
o 注册名称：oauth
o Specification: [this document]
o 规格：[本文件]
o Repository: [The registry created in Section 2.]
o 存储库：[第2节中创建的注册表。]
o Index value: values subordinate to urn:ietf:params:oauth are of the form urn:ietf:params:oauth:<value> with <value> as the index value. It is suggested that <value> include both a "class" and an "identifier-within-class" component, with the two components being separated by a colon (":"); other compositions of the <value> may also be used.
o 索引值：从属于urn:ietf:params:oauth的值的形式为urn:ietf:params:oauth:<value>，索引值为<value>。建议<value>同时包含“类”和“类内标识符”组件，两个组件之间用冒号（“：”）分隔；也可使用<value>的其它组合物。
[RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997.
[RFC2141]Moats，R.，“瓮语法”，RFC 21411997年5月。
[RFC3553] Mealling, M., Masinter, L., Hardie, T., and G. Klyne, "An IETF URN Sub-namespace for Registered Protocol Parameters", BCP 73, RFC 3553, June 2003.
[RFC3553]Mealling，M.，Masinter，L.，Hardie，T.，和G.Klyne，“注册协议参数的IETF URN子命名空间”，BCP 73，RFC 3553，2003年6月。
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.
[RFC5226]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 5226，2008年5月。
[OAUTH-V2] Hardt, D., "The OAuth 2.0 Authorization Framework", Work in Progress, July 2012.
[OAUTH-V2]Hardt，D.，“OAUTH 2.0授权框架”，正在进行的工作，2012年7月。
The authors thank the following for their helpful contributions: Stephen Farrell, Barry Leiba, Peter Saint-Andre, Eran Hammer, John Bradley, Ben Campbell, and Michael B. Jones.
作者感谢以下人士的贡献：斯蒂芬·法雷尔、巴里·莱巴、彼得·圣安德烈、埃兰·哈默、约翰·布拉德利、本·坎贝尔和迈克尔·琼斯。
Authors' Addresses
作者地址
Brian Campbell Ping Identity Corp.
布莱恩·坎贝尔·平身份识别公司。
EMail: brian.d.campbell@gmail.com
EMail: brian.d.campbell@gmail.com
Hannes Tschofenig Nokia Siemens Networks
Hannes Tschofenig诺基亚西门子网络公司
EMail: hannes.tschofenig@gmx.net
EMail: hannes.tschofenig@gmx.net