draft-ietf-oauth-urn-sub-ns-00.txt   draft-ietf-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: February 2, 2012 Nokia Siemens Networks Expires: June 3, 2012 Nokia Siemens Networks
Aug 2011 Dec 2011
An IETF URN Sub-Namespace for OAuth An IETF URN Sub-Namespace for OAuth
draft-ietf-oauth-urn-sub-ns-00 draft-ietf-oauth-urn-sub-ns-01
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 February 2, 2012. This Internet-Draft will expire on June 3, 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
skipping to change at page 4, line 10 skipping to change at page 4, line 10
The individual/organization that is the registration contact for The individual/organization that is the registration contact for
the component being registered. Ideally, this will be the name the component being registered. Ideally, this will be the name
and pertinent physical and network contact information. In the and pertinent physical and network contact information. In the
case of IETF developed standards, the Registrant will be the IESG. case of IETF developed standards, the Registrant will be the IESG.
Description: Description:
Information about the registered functionality. Information about the registered functionality.
4. Security Considerations 4. Security Considerations
None not already inherent to using URNs as discussed in RFC 3553 None not already inherent to using URNs. Security considerations for
[RFC3553]. URNs in general can be found in RFC 2141 [RFC2141].
5. IANA Considerations 5. IANA Considerations
5.1. IETF URN Sub-namespace Registration urn:ietf:params:oauth 5.1. IETF URN Sub-namespace Registration urn:ietf:params:oauth
Per RFC 3553 [RFC3553], IANA is requested to establish the following Per RFC 3553 [RFC3553], IANA is requested to establish the following
registry. New entries to the registry are Specification Required. registry. New entries to the registry are Specification Required.
o Registry name: urn:ietf:params:oauth o Registry name: urn:ietf:params:oauth
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-01
o security considerations now points to RFC 2141 rather than RFC
3553 per
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.
[RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997.
[RFC3553] Mealling, M., Masinter, L., Hardie, T., and G. Klyne, "An [RFC3553] Mealling, M., Masinter, L., Hardie, T., and G. Klyne, "An
IETF URN Sub-namespace for Registered Protocol IETF URN Sub-namespace for Registered Protocol
Parameters", BCP 73, RFC 3553, June 2003. Parameters", BCP 73, RFC 3553, June 2003.
6.2. Informative References 6.2. Informative References
[I-D.ietf.oauth-v2] [I-D.ietf.oauth-v2]
Hammer-Lahav, E., Ed., Recordon, D., and D. Hardt, "The Hammer-Lahav, E., Ed., Recordon, D., and D. Hardt, "The
OAuth 2.0 Authorization Protocol", OAuth 2.0 Authorization Protocol",
ID draft-ietf-oauth-v2-20 (work in progress), July 2011. ID draft-ietf-oauth-v2-20 (work in progress), July 2011.
 End of changes. 7 change blocks. 
9 lines changed or deleted 14 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/