< draft-campbell-oauth-urn-sub-ns-00.txt   draft-campbell-oauth-urn-sub-ns-01.txt >
B. Campbell, Ed. B. Campbell, Ed.
Internet-Draft Ping Identity Corp. Internet-Draft Ping Identity Corp.
Intended status: Informational H. Tschofenig Intended status: Informational H. Tschofenig
Expires: January 30, 2012 Nokia Siemens Networks Expires: February 2, 2012 Nokia Siemens Networks
July 29, 2011 Aug 2011
An IETF URN Sub-Namespace for OAuth An IETF URN Sub-Namespace for OAuth
draft-campbell-oauth-urn-sub-ns-00 draft-campbell-oauth-urn-sub-ns-01
Abstract Abstract
This document creates and registers an IETF URN Sub-namespace for use This document establishes an IETF URN Sub-namespace for use with
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.
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 January 30, 2012. This Internet-Draft will expire on February 2, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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. Notational Conventions . . . . . . . . . . . . . . . . . . . . 3
3. Registration Template for Sub-Namspace Registration of 3. Registration Template . . . . . . . . . . . . . . . . . . . . . 3
urn:ietf:params:oauth . . . . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
5.1. IETF URN Sub-namespace Registration 5.1. IETF URN Sub-namespace Registration
urn:ietf:params:oauth . . . . . . . . . . . . . . . . . . . 4 urn:ietf:params:oauth . . . . . . . . . . . . . . . . . . . 4
Appendix A. Document History . . . . . . . . . . . . . . . . . . . 4 Appendix A. Document History . . . . . . . . . . . . . . . . . . . 4
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4
6.1. Normative References . . . . . . . . . . . . . . . . . . . 4 6.1. Normative References . . . . . . . . . . . . . . . . . . . 4
6.2. Informative References . . . . . . . . . . . . . . . . . . 5 6.2. Informative References . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5
skipping to change at page 3, line 21 skipping to change at page 3, line 21
3553 [RFC3553], for use with such specifications. The new 'oauth' 3553 [RFC3553], for use with such specifications. The new 'oauth'
sub-namespace look like urn:ietf:params:oauth and OAuth relevant sub-namespace look like urn:ietf:params:oauth and OAuth relevant
parameters will be established underneath it. parameters will be established underneath it.
2. Notational Conventions 2. Notational Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
3. Registration Template for Sub-Namspace Registration of 3. Registration Template
urn:ietf:params:oauth
If the registrant wishes to have a URI assigned, then a URN of the 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 form urn:ietf:params:oauth:<class>:<id> will be assigned where
<class> is the category of the parameters being registered and <id> <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 is a unique id generated by the IANA based on any means the IANA
deems necessary to maintain uniqueness and persistence. NOTE: in deems necessary to maintain uniqueness and persistence. NOTE: in
order for a URN of this type to be assigned, the item being 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 registered MUST be documented in a RFC. The RFC 3553 [RFC3553] URN
registration template is found in the IANA consideration section of registration template is found in the IANA consideration section of
this document. this document.
skipping to change at page 4, line 34 skipping to change at page 4, line 34
o Repository: To be assigned according to the guidelines found o Repository: To be assigned according to the guidelines found
above. above.
o Index value: The class name o Index value: The class name
Appendix A. Document History Appendix A. 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-campbell-oauth-urn-sub-ns-01
o minor editorial changes
draft-campbell-oauth-urn-sub-ns-00 draft-campbell-oauth-urn-sub-ns-00
o initial draft based on o initial draft based on
http://www.ietf.org/mail-archive/web/oauth/current/msg06949.html http://www.ietf.org/mail-archive/web/oauth/current/msg06949.html
6. References 6. References
6.1. Normative References 6.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
 End of changes. 7 change blocks. 
10 lines changed or deleted 12 lines changed or added

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