idnits 2.17.1 draft-campbell-oauth-urn-sub-ns-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 29, 2011) is 4652 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 B. Campbell, Ed. 3 Internet-Draft Ping Identity Corp. 4 Intended status: Informational H. Tschofenig 5 Expires: January 30, 2012 Nokia Siemens Networks 6 July 29, 2011 8 An IETF URN Sub-Namespace for OAuth 9 draft-campbell-oauth-urn-sub-ns-00 11 Abstract 13 This document creates and registers an IETF URN Sub-namespace for use 14 with OAuth related specifications. 16 Status of this Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at http://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on January 30, 2012. 33 Copyright Notice 35 Copyright (c) 2011 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 51 2. Notational Conventions . . . . . . . . . . . . . . . . . . . . 3 52 3. Registration Template for Sub-Namspace Registration of 53 urn:ietf:params:oauth . . . . . . . . . . . . . . . . . . . . . 3 54 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 55 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 56 5.1. IETF URN Sub-namespace Registration 57 urn:ietf:params:oauth . . . . . . . . . . . . . . . . . . . 4 58 Appendix A. Document History . . . . . . . . . . . . . . . . . . . 4 59 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 60 6.1. Normative References . . . . . . . . . . . . . . . . . . . 4 61 6.2. Informative References . . . . . . . . . . . . . . . . . . 5 62 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 64 1. Introduction 66 Various extensions and companion specifications to The OAuth 2.0 67 Authorization Protocol [I-D.ietf.oauth-v2] utilize URIs to identify 68 the extension in use or other relevant context. This document 69 creates and registers an IETF URN Sub-namespace, as documented in RFC 70 3553 [RFC3553], for use with such specifications. The new 'oauth' 71 sub-namespace look like urn:ietf:params:oauth and OAuth relevant 72 parameters will be established underneath it. 74 2. Notational Conventions 76 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 77 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 78 document are to be interpreted as described in RFC 2119 [RFC2119]. 80 3. Registration Template for Sub-Namspace Registration of 81 urn:ietf:params:oauth 83 If the registrant wishes to have a URI assigned, then a URN of the 84 form urn:ietf:params:oauth:: will be assigned where 85 is the category of the parameters being registered and 86 is a unique id generated by the IANA based on any means the IANA 87 deems necessary to maintain uniqueness and persistence. NOTE: in 88 order for a URN of this type to be assigned, the item being 89 registered MUST be documented in a RFC. The RFC 3553 [RFC3553] URN 90 registration template is found in the IANA consideration section of 91 this document. 93 The registration procedure for new entries to the requires a request 94 in the form of the following template: 96 URN: 97 The token URI that identifies the registered component. If the 98 registrant is requesting that the IANA assign a URI then this 99 field should be specified as "please assign". 101 Common Name: 102 The name by which the functionality being registered is generally 103 referred. 105 Registrant Contact: 106 The individual/organization that is the registration contact for 107 the component being registered. Ideally, this will be the name 108 and pertinent physical and network contact information. In the 109 case of IETF developed standards, the Registrant will be the IESG. 111 Description: 112 Information about the registered functionality. 114 4. Security Considerations 116 None not already inherent to using URNs as discussed in RFC 3553 117 [RFC3553]. 119 5. IANA Considerations 121 5.1. IETF URN Sub-namespace Registration urn:ietf:params:oauth 123 Per RFC 3553 [RFC3553], IANA is requested to establish the following 124 registry. New entries to the registry are Specification Required. 126 o Registry name: urn:ietf:params:oauth 128 o Specification: Section 3 of this document contains the registry 129 specification. 131 o Repository: To be assigned according to the guidelines found 132 above. 134 o Index value: The class name 136 Appendix A. Document History 138 [[ to be removed by RFC editor before publication as an RFC ]] 140 draft-campbell-oauth-urn-sub-ns-00 142 o initial draft based on 143 http://www.ietf.org/mail-archive/web/oauth/current/msg06949.html 145 6. References 147 6.1. Normative References 149 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 150 Requirement Levels", BCP 14, RFC 2119, March 1997. 152 [RFC3553] Mealling, M., Masinter, L., Hardie, T., and G. Klyne, "An 153 IETF URN Sub-namespace for Registered Protocol 154 Parameters", BCP 73, RFC 3553, June 2003. 156 6.2. Informative References 158 [I-D.ietf.oauth-v2] 159 Hammer-Lahav, E., Ed., Recordon, D., and D. Hardt, "The 160 OAuth 2.0 Authorization Protocol", 161 ID draft-ietf-oauth-v2-20 (work in progress), July 2011. 163 Authors' Addresses 165 Brian Campbell (editor) 166 Ping Identity Corp. 168 Email: brian.d.campbell@gmail.com 170 Hannes Tschofenig 171 Nokia Siemens Networks 173 Email: hannes.tschofenig@gmx.net