idnits 2.17.1 draft-ietf-oauth-urn-sub-ns-02.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 (Jan 2012) is 4484 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 2141 (Obsoleted by RFC 8141) Summary: 1 error (**), 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: July 4, 2012 Nokia Siemens Networks 6 Jan 2012 8 An IETF URN Sub-Namespace for OAuth 9 draft-ietf-oauth-urn-sub-ns-02 11 Abstract 13 This document establishes an IETF URN Sub-namespace for use with 14 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 July 4, 2012. 33 Copyright Notice 35 Copyright (c) 2012 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 . . . . . . . . . . . . . . . . . . . . . 3 53 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 54 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 55 5.1. IETF URN Sub-namespace Registration 56 urn:ietf:params:oauth . . . . . . . . . . . . . . . . . . . 4 57 Appendix A. Document History . . . . . . . . . . . . . . . . . . . 4 58 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 59 6.1. Normative References . . . . . . . . . . . . . . . . . . . 5 60 6.2. Informative References . . . . . . . . . . . . . . . . . . 5 61 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 63 1. Introduction 65 Various extensions and companion specifications to The OAuth 2.0 66 Authorization Protocol [I-D.ietf.oauth-v2] utilize URIs to identify 67 the extension in use or other relevant context. This document 68 creates and registers an IETF URN Sub-namespace, as documented in RFC 69 3553 [RFC3553], for use with such specifications. The new 'oauth' 70 sub-namespace look like urn:ietf:params:oauth and OAuth relevant 71 parameters will be established underneath it. 73 2. Notational Conventions 75 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 76 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 77 document are to be interpreted as described in RFC 2119 [RFC2119]. 79 3. Registration Template 81 If the registrant wishes to have a URI assigned, then a URN of the 82 form urn:ietf:params:oauth:: will be assigned where 83 is the category of the parameters being registered and 84 is a unique id generated by the IANA based on any means the IANA 85 deems necessary to maintain uniqueness and persistence. NOTE: in 86 order for a URN of this type to be assigned, the item being 87 registered MUST be documented in a RFC. The RFC 3553 [RFC3553] URN 88 registration template is found in the IANA consideration section of 89 this document. 91 The registration procedure for new entries requires a request in the 92 form of the following template: 94 URN: 95 The token URI that identifies the registered component. If the 96 registrant is requesting that the IANA assign a URI then this 97 field should be specified as "please assign". 99 Common Name: 100 The name by which the functionality being registered is generally 101 referred. 103 Registrant Contact: 104 The individual/organization that is the registration contact for 105 the component being registered. Ideally, this will be the name 106 and pertinent physical and network contact information. In the 107 case of IETF developed standards, the Registrant will be the IESG. 109 Description: 110 Information about the registered functionality. 112 4. Security Considerations 114 None not already inherent to using URNs. Security considerations for 115 URNs in general can be found in RFC 2141 [RFC2141]. 117 5. IANA Considerations 119 5.1. IETF URN Sub-namespace Registration urn:ietf:params:oauth 121 Per RFC 3553 [RFC3553], IANA is requested to establish the following 122 registry. New entries to the registry are Specification Required. 124 o Registry name: urn:ietf:params:oauth 126 o Specification: Section 3 of this document contains the registry 127 specification. 129 o Repository: To be assigned according to the guidelines found 130 above. 132 o Index value: The class name 134 Appendix A. Document History 136 [[ to be removed by RFC editor before publication as an RFC ]] 138 draft-ietf-oauth-urn-sub-ns-02 140 o fix typo: "The registration procedure for new entries to the 141 requires a request ..." --> "The registration procedure for new 142 entries requires a request ..." 144 draft-ietf-oauth-urn-sub-ns-01 146 o security considerations now points to RFC 2141 rather than RFC 147 3553 per 148 http://www.ietf.org/mail-archive/web/oauth/current/msg07880.html 150 draft-ietf-oauth-urn-sub-ns-00 152 o change doc name from draft-campbell-oauth-urn-sub-ns to 153 draft-ietf-oauth-urn-sub-ns per 154 http://www.ietf.org/mail-archive/web/oauth/current/msg07384.html 156 draft-campbell-oauth-urn-sub-ns-01 158 o minor editorial changes 160 draft-campbell-oauth-urn-sub-ns-00 162 o initial draft based on 163 http://www.ietf.org/mail-archive/web/oauth/current/msg06949.html 165 6. References 167 6.1. Normative References 169 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 170 Requirement Levels", BCP 14, RFC 2119, March 1997. 172 [RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997. 174 [RFC3553] Mealling, M., Masinter, L., Hardie, T., and G. Klyne, "An 175 IETF URN Sub-namespace for Registered Protocol 176 Parameters", BCP 73, RFC 3553, June 2003. 178 6.2. Informative References 180 [I-D.ietf.oauth-v2] 181 Hammer-Lahav, E., Ed., Recordon, D., and D. Hardt, "The 182 OAuth 2.0 Authorization Protocol", 183 ID draft-ietf-oauth-v2-20 (work in progress), July 2011. 185 Authors' Addresses 187 Brian Campbell (editor) 188 Ping Identity Corp. 190 Email: brian.d.campbell@gmail.com 192 Hannes Tschofenig 193 Nokia Siemens Networks 195 Email: hannes.tschofenig@gmx.net