draft-ietf-oauth-urn-sub-ns-05.txt   draft-ietf-oauth-urn-sub-ns-06.txt 
OAuth Working Group B. Campbell OAuth Working Group B. Campbell
Internet-Draft Ping Identity Corp. Internet-Draft Ping Identity Corp.
Intended status: Standards Track H. Tschofenig Intended status: Standards Track H. Tschofenig
Expires: December 28, 2012 Nokia Siemens Networks Expires: January 17, 2013 Nokia Siemens Networks
June 26, 2012 July 16, 2012
An IETF URN Sub-Namespace for OAuth An IETF URN Sub-Namespace for OAuth
draft-ietf-oauth-urn-sub-ns-05 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 Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 32 skipping to change at page 1, line 32
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 28, 2012. This Internet-Draft will expire on January 17, 2013.
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 . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Notational Conventions . . . . . . . . . . . . . . . . . . . . 3 2. Registration Template . . . . . . . . . . . . . . . . . . . . . 3
3. Registration Template . . . . . . . . . . . . . . . . . . . . . 3 2.1. Example Registration Request . . . . . . . . . . . . . . . 3
3.1. Example Registration Request . . . . . . . . . . . . . . . 4 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 4.1. IETF URN Sub-namespace Registration
5.1. IETF URN Sub-namespace Registration
urn:ietf:params:oauth . . . . . . . . . . . . . . . . . . . 4 urn:ietf:params:oauth . . . . . . . . . . . . . . . . . . . 4
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Normative References . . . . . . . . . . . . . . . . . . . 5 5.1. Normative References . . . . . . . . . . . . . . . . . . . 5
6.2. Informative References . . . . . . . . . . . . . . . . . . 5 5.2. Informative References . . . . . . . . . . . . . . . . . . 5
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . . 5 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . . 5
Appendix B. Document History . . . . . . . . . . . . . . . . . . . 6 Appendix B. Document History . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 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 [I-D.ietf-oauth-v2] utilize URIs to identify
the extension in use or other relevant context. This document the extension in use or other relevant context. This document
creates and registers an IETF URN Sub-namespace, as documented in RFC creates and registers an IETF URN Sub-namespace, as documented in RFC
3553 [RFC3553], for use with such specifications. The new 'oauth' 3553 [RFC3553], for use with such specifications. The new 'oauth'
sub-namespace is urn:ietf:params:oauth and OAuth relevant parameters sub-namespace is urn:ietf:params:oauth and OAuth relevant parameters
will be established underneath it. will be established underneath it.
2. Notational Conventions 2. Registration Template
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 RFC 2119 [RFC2119].
3. Registration Template
If a registrant wishes to have a OAuth URI registered, then a URN of If a registrant wishes to have a 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 RFC
5226 [RFC5226]. 5226 [RFC5226].
skipping to change at page 3, line 50 skipping to change at page 3, line 44
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, e-mail address, home page URI) may also be
included. 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 5) section of namespace is found in the IANA Considerations (Section 4) section of
this document. this document.
3.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-namespece. 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]]
4. Security Considerations 3. Security Considerations
None not already inherent to using URNs. Security considerations for There are no additional security considerations beyond those already
URNs in general can be found in RFC 2141 [RFC2141]. inherent to using URNs. Security considerations for URNs in general
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]. [I-D.ietf-oauth-v2].
5. IANA Considerations 4. IANA Considerations
This document makes two requests of IANA: This document makes two requests of IANA:
o Registration of a new IANA URN sub-namespace, o 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 5.1 below. request can be found in Section 4.1 below.
o Establishment of a new registry for URNs subordinate to o Establishment of a new registry for URNs subordinate to
urn:ietf:params:oauth. Instructions for a registrant to request urn:ietf:params:oauth. Instructions for a registrant to request
the registration of such a URN are in Section 3. the registration of such a URN are in Section 2.
5.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 is requested to please register a new
URN sub-namespace, urn:ietf:params:oauth. URN sub-namespace, 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 3.]] 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 from 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.
6. References 5. References
6.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 5.1. Normative References
Requirement Levels", BCP 14, RFC 2119, March 1997.
[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.
6.2. Informative References 5.2. Informative References
[I-D.ietf-oauth-v2] [I-D.ietf-oauth-v2]
Hammer-Lahav, E., Recordon, D., and D. Hardt, "The OAuth Hardt, D. and D. Recordon, "The OAuth 2.0 Authorization
2.0 Authorization Framework", draft-ietf-oauth-v2-27 (work Framework", draft-ietf-oauth-v2-30 (work in progress),
in progress), June 2012. 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 and Michael B. Jones. Bradley, Ben Campbell and Michael B. Jones.
Appendix B. Document History Appendix B. Document History
[[ to be removed by RFC editor before publication as an RFC ]] [[ to be removed by RFC editor before publication as an RFC ]]
draft-ietf-oauth-urn-sub-ns-05 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 o Change the registration procedure from Expert Review to
Specification Required per WG discussion Specification Required per WG discussion
http://www.ietf.org/mail-archive/web/oauth/current/msg09445.html http://www.ietf.org/mail-archive/web/oauth/current/msg09445.html
draft-ietf-oauth-urn-sub-ns-04 draft-ietf-oauth-urn-sub-ns-04
o Changed the Index value (and Registration Template into paragraph) o Changed the Index value (and Registration Template into paragraph)
from <class><id> to just <value> with a suggestion that it have from <class><id> to just <value> with a suggestion that it have
both a "class" and an "identifier-within-class" parts per both a "class" and an "identifier-within-class" parts per
http://www.ietf.org/mail-archive/web/oauth/current/msg09381.html http://www.ietf.org/mail-archive/web/oauth/current/msg09381.html
 End of changes. 24 change blocks. 
43 lines changed or deleted 37 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/