draft-ietf-oauth-urn-sub-ns-06.txt   rfc6755.txt 
OAuth Working Group B. Campbell Internet Engineering Task Force (IETF) B. Campbell
Internet-Draft Ping Identity Corp. Request for Comments: 6755 Ping Identity Corp.
Intended status: Standards Track H. Tschofenig Category: Informational H. Tschofenig
Expires: January 17, 2013 Nokia Siemens Networks ISSN: 2070-1721 Nokia Siemens Networks
July 16, 2012 October 2012
An IETF URN Sub-Namespace for OAuth An IETF URN Sub-Namespace for OAuth
draft-ietf-oauth-urn-sub-ns-06
Abstract Abstract
This document establishes an IETF URN Sub-namespace for use with This document establishes an IETF URN Sub-namespace for use with
OAuth related specifications. OAuth-related specifications.
Status of this Memo
This Internet-Draft is submitted in full conformance with the Status of This Memo
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This document is not an Internet Standards Track specification; it is
Task Force (IETF). Note that other groups may also distribute published for informational purposes.
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." 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.
This Internet-Draft will expire on January 17, 2013. 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.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction ....................................................2
2. Registration Template . . . . . . . . . . . . . . . . . . . . . 3 2. Registration Template ...........................................2
2.1. Example Registration Request . . . . . . . . . . . . . . . 3 2.1. Example Registration Request ...............................3
3. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 3. Security Considerations .........................................3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 4. IANA Considerations .............................................3
4.1. IETF URN Sub-namespace Registration 4.1. IETF URN Sub-Namespace Registration urn:ietf:params:oauth ..4
urn:ietf:params:oauth . . . . . . . . . . . . . . . . . . . 4 5. References ......................................................4
5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 5.1. Normative References .......................................4
5.1. Normative References . . . . . . . . . . . . . . . . . . . 5 5.2. Informative Reference ......................................4
5.2. Informative References . . . . . . . . . . . . . . . . . . 5 Appendix A. Acknowledgements ......................................5
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . . 5
Appendix B. Document History . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction 1. Introduction
Various extensions and companion specifications to The OAuth 2.0 Various extensions and companion specifications to the OAuth 2.0
Authorization Framework [I-D.ietf-oauth-v2] utilize URIs to identify Authorization Framework [OAUTH-V2] utilize URIs to identify the
the extension in use or other relevant context. This document extension in use or other relevant context. This document creates
creates and registers an IETF URN Sub-namespace, as documented in RFC and registers an IETF URN Sub-namespace, as documented in RFC 3553
3553 [RFC3553], for use with such specifications. The new 'oauth' [RFC3553], for use with such specifications. The new 'oauth' Sub-
sub-namespace is urn:ietf:params:oauth and OAuth relevant parameters namespace is urn:ietf:params:oauth, and OAuth relevant parameters
will be established underneath it. will be established underneath it.
2. Registration Template 2. Registration Template
If a registrant wishes to have a OAuth URI registered, then a URN of 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 the form urn:ietf:params:oauth:<value> will be requested where
<value> is a suitable representation of the functionality or concept <value> is a suitable representation of the functionality or concept
being registered. being registered.
The registration procedure for new entries requires a request in the The registration procedure for new entries requires a request in the
form of the following template and is Specification Required per RFC form of the following template and is "Specification Required" per
5226 [RFC5226]. RFC 5226 [RFC5226].
URN: URN:
The URI that identifies the registered functionality. The URI that identifies the registered functionality.
Common Name: Common Name:
The name by which the functionality being registered is generally The name by which the functionality being registered is generally
known. known.
Change Controller: For standards-track RFCs, state "IETF". For Change Controller: For Standards Track RFCs, state "IETF". For
others, give the name of the responsible party. Other details others, give the name of the responsible party. Other details
(e.g., postal address, e-mail address, home page URI) may also be (e.g., postal address, email address, and home page URI) may also
included. be included.
Specification Document(s): Reference to the document that specifies Specification Document(s): Reference to the document that specifies
the URI, preferably including a URI that can be used to retrieve a the URI, preferably including a URI that can be used to retrieve a
copy of the document. An indication of the relevant sections may copy of the document. An indication of the relevant sections may
also be included, but is not required. also be included but is not required.
The registration request for the urn:ietf:params:oauth URN Sub- The registration request for the urn:ietf:params:oauth URN Sub-
namespace is found in the IANA Considerations (Section 4) section of namespace is found in the IANA Considerations section of this
this document. document (Section 4).
2.1. Example Registration Request 2.1. Example Registration Request
The following is an example registration request for a URI underneath The following is an example registration request for a URI underneath
the urn:ietf:params:oauth sub-namespece. The requested URI the urn:ietf:params:oauth Sub-namespace. The requested URI
represents a new OAuth 2.0 grant type. represents a new OAuth 2.0 grant type.
This is a request to IANA to please register the value This is a request to IANA to please register the value
"grant-type:example" in the registry urn:ietf:params:oauth "grant-type:example" in the registry urn:ietf:params:oauth
established in An IETF URN Sub-Namespace for OAuth. established in an IETF URN Sub-namespace for OAuth.
o URN: urn:ietf:params:oauth:grant-type:example o URN: urn:ietf:params:oauth:grant-type:example
o Common Name: An Example Grant Type for OAuth 2.0 o Common Name: An Example Grant Type for OAuth 2.0
o Change controller: IETF o Change controller: IETF
o Specification Document: [[the document URI]] o Specification Document: [the document URI]
3. Security Considerations 3. Security Considerations
There are no additional security considerations beyond those already There are no additional security considerations beyond those already
inherent to using URNs. Security considerations for URNs in general inherent to using URNs. Security considerations for URNs in general
can be found in RFC 2141 [RFC2141]. can be found in RFC 2141 [RFC2141].
Any work that is related to OAuth would benefit from familiarity with Any work that is related to OAuth would benefit from familiarity with
the security considerations of The OAuth 2.0 Authorization Framework the security considerations of the OAuth 2.0 Authorization Framework
[I-D.ietf-oauth-v2]. [OAUTH-V2].
4. IANA Considerations 4. IANA Considerations
This document makes two requests of IANA: IANA has created the following:
o Registration of a new IANA URN sub-namespace, o The registration of a new IANA URN Sub-namespace,
urn:ietf:params:oauth:, per RFC 3553 [RFC3553]. The registration urn:ietf:params:oauth:, per RFC 3553 [RFC3553]. The registration
request can be found in Section 4.1 below. request can be found in Section 4.1 below.
o Establishment of a new registry for URNs subordinate to o A new registry called the "OAuth URI" registry for URNs
urn:ietf:params:oauth. Instructions for a registrant to request subordinate to urn:ietf:params:oauth. The registry "OAuth URI"
the registration of such a URN are in Section 2. has been added to a new top-level registry called "OAuth
Parameters" as defined by [OAUTH-V2]. Instructions for a
registrant to request the registration of such a URN are in
Section 2.
4.1. IETF URN Sub-namespace Registration urn:ietf:params:oauth 4.1. IETF URN Sub-Namespace Registration urn:ietf:params:oauth
Per RFC 3553 [RFC3553], IANA is requested to please register a new Per RFC 3553 [RFC3553], IANA has registered a new URN Sub-namespace,
URN sub-namespace, urn:ietf:params:oauth. urn:ietf:params:oauth.
o Registry name: oauth o Registry name: oauth
o Specification: [[this document]] o Specification: [this document]
o Repository: [The registry created in Section 2.]
o Repository: [[The registry created in Section 3.]]
o Index value: values subordinate to urn:ietf:params:oauth are of o Index value: values subordinate to urn:ietf:params:oauth are of
the form urn:ietf:params:oauth:<value> with <value> as the index the form urn:ietf:params:oauth:<value> with <value> as the index
value. It is suggested that <value> include both a "class" and an value. It is suggested that <value> include both a "class" and an
"identifier-within-class" component, with the two components being "identifier-within-class" component, with the two components being
separated by a colon (":"); other compositions of the <value> may separated by a colon (":"); other compositions of the <value> may
also be used. also be used.
5. References 5. References
5.1. Normative References 5.1. Normative References
[RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997. [RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997.
[RFC3553] Mealling, M., Masinter, L., Hardie, T., and G. Klyne, "An [RFC3553] Mealling, M., Masinter, L., Hardie, T., and G. Klyne, "An
IETF URN Sub-namespace for Registered Protocol IETF URN Sub-namespace for Registered Protocol
Parameters", BCP 73, RFC 3553, June 2003. Parameters", BCP 73, RFC 3553, June 2003.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
5.2. Informative References 5.2. Informative Reference
[I-D.ietf-oauth-v2] [OAUTH-V2] Hardt, D., "The OAuth 2.0 Authorization Framework", Work
Hardt, D. and D. Recordon, "The OAuth 2.0 Authorization in Progress, July 2012.
Framework", draft-ietf-oauth-v2-30 (work in progress),
July 2012.
Appendix A. Acknowledgements Appendix A. Acknowledgements
The authors thank the following for their helpful contributions: The authors thank the following for their helpful contributions:
Stephen Farrell, Barry Leiba, Peter Saint-Andre, Eran Hammer, John Stephen Farrell, Barry Leiba, Peter Saint-Andre, Eran Hammer, John
Bradley, Ben Campbell and Michael B. Jones. Bradley, Ben Campbell, and Michael B. Jones.
Appendix B. Document History
[[ to be removed by RFC editor before publication as an RFC ]]
draft-ietf-oauth-urn-sub-ns-06
o Address editorial comments from Gen-ART LC Review:
http://www.ietf.org/mail-archive/web/gen-art/current/msg07576.html
draft-ietf-oauth-urn-sub-ns-05
o Change the registration procedure from Expert Review to
Specification Required per WG discussion
http://www.ietf.org/mail-archive/web/oauth/current/msg09445.html
draft-ietf-oauth-urn-sub-ns-04
o Changed the Index value (and Registration Template into paragraph)
from <class><id> to just <value> with a suggestion that it have
both a "class" and an "identifier-within-class" parts per
http://www.ietf.org/mail-archive/web/oauth/current/msg09381.html
so as to be less restrictive
draft-ietf-oauth-urn-sub-ns-03
o Changes to address comments in the message "AD review of
draft-ietf-oauth-urn-sub-ns-02" at
http://www.ietf.org/mail-archive/web/oauth/current/msg09350.html
and subsequent messages in that thread
o Update area and workgroup (now Security and OAuth was Internet and
nothing)
o Change from informational to standards-track
o Requesting new URNs now more lightweight by changing from 'RFC
Required' to 'Expert Review' (RFC5226)
o Rework much of the document to be more clear about it registering
the urn:ietf:params:oauth URN sub-namespace and separately how
other documents are to request URNs under that sub-namespace.
o Removed everything about asking the IANA to generate any part of
the URN.
o Added an Example Registration Request
o Added reference to OAuth security considerations in security
considerations.
o Added Acknowledgements
draft-ietf-oauth-urn-sub-ns-02
o fix typo: "The registration procedure for new entries to the
requires a request ..." --> "The registration procedure for new
entries requires a request ..."
draft-ietf-oauth-urn-sub-ns-01
o security considerations now points to RFC 2141 rather than RFC
3553 per
http://www.ietf.org/mail-archive/web/oauth/current/msg07880.html
draft-ietf-oauth-urn-sub-ns-00
o change doc name from draft-campbell-oauth-urn-sub-ns to
draft-ietf-oauth-urn-sub-ns per
http://www.ietf.org/mail-archive/web/oauth/current/msg07384.html
draft-campbell-oauth-urn-sub-ns-01
o minor editorial changes
draft-campbell-oauth-urn-sub-ns-00
o initial draft based on
http://www.ietf.org/mail-archive/web/oauth/current/msg06949.html
Authors' Addresses Authors' Addresses
Brian Campbell Brian Campbell
Ping Identity Corp. Ping Identity Corp.
Email: brian.d.campbell@gmail.com EMail: brian.d.campbell@gmail.com
Hannes Tschofenig Hannes Tschofenig
Nokia Siemens Networks Nokia Siemens Networks
Email: hannes.tschofenig@gmx.net EMail: hannes.tschofenig@gmx.net
 End of changes. 34 change blocks. 
154 lines changed or deleted 74 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/