< draft-ietf-oauth-urn-sub-ns-01.txt   draft-ietf-oauth-urn-sub-ns-02.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: June 3, 2012 Nokia Siemens Networks Expires: July 4, 2012 Nokia Siemens Networks
Dec 2011 Jan 2012
An IETF URN Sub-Namespace for OAuth An IETF URN Sub-Namespace for OAuth
draft-ietf-oauth-urn-sub-ns-01 draft-ietf-oauth-urn-sub-ns-02
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 June 3, 2012. This Internet-Draft will expire on July 4, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 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
skipping to change at page 3, line 33 skipping to change at page 3, line 33
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.
The registration procedure for new entries to the requires a request The registration procedure for new entries requires a request in the
in the form of the following template: form of the following template:
URN: URN:
The token URI that identifies the registered component. If the The token URI that identifies the registered component. If the
registrant is requesting that the IANA assign a URI then this registrant is requesting that the IANA assign a URI then this
field should be specified as "please assign". field should be specified as "please assign".
Common Name: Common Name:
The name by which the functionality being registered is generally The name by which the functionality being registered is generally
referred. referred.
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-ietf-oauth-urn-sub-ns-02
o fix typo: "The registration procedure for new entries to the
requires a request ..." --> "The registration procedure for new
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 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
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
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
 End of changes. 7 change blocks. 
7 lines changed or deleted 16 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/