draft-ietf-oauth-urn-sub-ns-04.txt   draft-ietf-oauth-urn-sub-ns-05.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 24, 2012 Nokia Siemens Networks Expires: December 28, 2012 Nokia Siemens Networks
June 22, 2012 June 26, 2012
An IETF URN Sub-Namespace for OAuth An IETF URN Sub-Namespace for OAuth
draft-ietf-oauth-urn-sub-ns-04 draft-ietf-oauth-urn-sub-ns-05
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 24, 2012. This Internet-Draft will expire on December 28, 2012.
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
skipping to change at page 2, line 19 skipping to change at page 2, line 19
3. Registration Template . . . . . . . . . . . . . . . . . . . . . 3 3. Registration Template . . . . . . . . . . . . . . . . . . . . . 3
3.1. Example Registration Request . . . . . . . . . . . . . . . 4 3.1. Example Registration Request . . . . . . . . . . . . . . . 4
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
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Normative References . . . . . . . . . . . . . . . . . . . 5 6.1. Normative References . . . . . . . . . . . . . . . . . . . 5
6.2. Informative References . . . . . . . . . . . . . . . . . . 5 6.2. Informative References . . . . . . . . . . . . . . . . . . 5
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . . 5 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . . 5
Appendix B. Document History . . . . . . . . . . . . . . . . . . . 5 Appendix B. Document History . . . . . . . . . . . . . . . . . . . 6
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
skipping to change at page 3, line 29 skipping to change at page 3, line 29
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 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 subject to Expert Review per form of the following template and is Specification Required per RFC
RFC 5226 [RFC5226]. 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
skipping to change at page 5, line 45 skipping to change at page 5, line 45
6.2. Informative References 6.2. Informative References
[I-D.ietf-oauth-v2] [I-D.ietf-oauth-v2]
Hammer-Lahav, E., Recordon, D., and D. Hardt, "The OAuth Hammer-Lahav, E., Recordon, D., and D. Hardt, "The OAuth
2.0 Authorization Framework", draft-ietf-oauth-v2-27 (work 2.0 Authorization Framework", draft-ietf-oauth-v2-27 (work
in progress), June 2012. in progress), June 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 and Michael B. Jones. Stephen Farrell, Barry Leiba, Peter Saint-Andre, Eran Hammer, John
Bradley 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
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) 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
so as to be less restrictive so as to be less restrictive
draft-ietf-oauth-urn-sub-ns-03 draft-ietf-oauth-urn-sub-ns-03
o Changes to address comments in the message "AD review of o Changes to address comments in the message "AD review of
draft-ietf-oauth-urn-sub-ns-02" at draft-ietf-oauth-urn-sub-ns-02" at
skipping to change at page 7, line 5 skipping to change at page 7, line 14
o fix typo: "The registration procedure for new entries to the o fix typo: "The registration procedure for new entries to the
requires a request ..." --> "The registration procedure for new requires a request ..." --> "The registration procedure for new
entries requires a request ..." entries requires a request ..."
draft-ietf-oauth-urn-sub-ns-01 draft-ietf-oauth-urn-sub-ns-01
o security considerations now points to RFC 2141 rather than RFC o security considerations now points to RFC 2141 rather than RFC
3553 per 3553 per
http://www.ietf.org/mail-archive/web/oauth/current/msg07880.html 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 o change doc name from draft-campbell-oauth-urn-sub-ns to
draft-ietf-oauth-urn-sub-ns per draft-ietf-oauth-urn-sub-ns per
http://www.ietf.org/mail-archive/web/oauth/current/msg07384.html http://www.ietf.org/mail-archive/web/oauth/current/msg07384.html
draft-campbell-oauth-urn-sub-ns-01 draft-campbell-oauth-urn-sub-ns-01
o minor editorial changes o minor editorial changes
draft-campbell-oauth-urn-sub-ns-00 draft-campbell-oauth-urn-sub-ns-00
 End of changes. 8 change blocks. 
8 lines changed or deleted 20 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/