B. Campbell, Ed.
Internet-Draft Ping Identity Corp.
Intended status: Informational H. Tschofenig
Expires: February 2, 2012 Nokia Siemens Networks
Aug 2011
An IETF URN Sub-Namespace for OAuth
draft-ietf-oauth-urn-sub-ns-00
Abstract
This document establishes an IETF URN Sub-namespace for use with
OAuth related specifications.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
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
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 2, 2012.
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
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.
Campbell & Tschofenig Expires February 2, 2012 [Page 1]
Internet-Draft An IETF URN Sub-Namespace for OAuth Aug 2011
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Notational Conventions . . . . . . . . . . . . . . . . . . . . 3
3. Registration Template . . . . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
5.1. IETF URN Sub-namespace Registration
urn:ietf:params:oauth . . . . . . . . . . . . . . . . . . . 4
Appendix A. Document History . . . . . . . . . . . . . . . . . . . 4
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Normative References . . . . . . . . . . . . . . . . . . . 5
6.2. Informative References . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5
Campbell & Tschofenig Expires February 2, 2012 [Page 2]
Internet-Draft An IETF URN Sub-Namespace for OAuth Aug 2011
1. Introduction
Various extensions and companion specifications to The OAuth 2.0
Authorization Protocol [I-D.ietf.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 look like urn:ietf:params:oauth and OAuth relevant
parameters will be established underneath it.
2. Notational Conventions
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 the registrant wishes to have a URI assigned, then a URN of the
form urn:ietf:params:oauth:<class>:<id> will be assigned where
<class> is the category of the parameters being registered and <id>
is a unique id generated by the IANA based on any means the IANA
deems necessary to maintain uniqueness and persistence. NOTE: in
order for a URN of this type to be assigned, the item being
registered MUST be documented in a RFC. The RFC 3553 [RFC3553] URN
registration template is found in the IANA consideration section of
this document.
The registration procedure for new entries to the requires a request
in the form of the following template:
URN:
The token URI that identifies the registered component. If the
registrant is requesting that the IANA assign a URI then this
field should be specified as "please assign".
Common Name:
The name by which the functionality being registered is generally
referred.
Registrant Contact:
The individual/organization that is the registration contact for
the component being registered. Ideally, this will be the name
and pertinent physical and network contact information. In the
case of IETF developed standards, the Registrant will be the IESG.
Campbell & Tschofenig Expires February 2, 2012 [Page 3]
Internet-Draft An IETF URN Sub-Namespace for OAuth Aug 2011
Description:
Information about the registered functionality.
4. Security Considerations
None not already inherent to using URNs as discussed in RFC 3553
[RFC3553].
5. IANA Considerations
5.1. IETF URN Sub-namespace Registration urn:ietf:params:oauth
Per RFC 3553 [RFC3553], IANA is requested to establish the following
registry. New entries to the registry are Specification Required.
o Registry name: urn:ietf:params:oauth
o Specification: Section 3 of this document contains the registry
specification.
o Repository: To be assigned according to the guidelines found
above.
o Index value: The class name
Appendix A. Document History
[[ to be removed by RFC editor before publication as an RFC ]]
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
Campbell & Tschofenig Expires February 2, 2012 [Page 4]
Internet-Draft An IETF URN Sub-Namespace for OAuth Aug 2011
6. References
6.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[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.
6.2. Informative References
[I-D.ietf.oauth-v2]
Hammer-Lahav, E., Ed., Recordon, D., and D. Hardt, "The
OAuth 2.0 Authorization Protocol",
ID draft-ietf-oauth-v2-20 (work in progress), July 2011.
Authors' Addresses
Brian Campbell (editor)
Ping Identity Corp.
Email: brian.d.campbell@gmail.com
Hannes Tschofenig
Nokia Siemens Networks
Email: hannes.tschofenig@gmx.net
Campbell & Tschofenig Expires February 2, 2012 [Page 5]
