Network Working Group B. Campbell, Ed.
Internet-Draft Ping Identity Corp.
Intended status: Informational H. Tschofenig
Nokia Siemens Networks
Aug 2011

An IETF URN Sub-Namespace for OAuth


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

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."

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 ( 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.

Table of Contents

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:


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.

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.

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., 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:
Hannes Tschofenig Nokia Siemens Networks EMail: