| 1 |
<pre>Internet Engineering Task Force (IETF) S. Martin |
| 2 |
Request for Comments: 7853 S. Tuecke |
| 3 |
Category: Informational B. McCollam |
| 4 |
ISSN: 2070-1721 M. Lidman |
| 5 |
University of Chicago |
| 6 |
May 2016 |
| 7 |
|
| 8 |
|
| 9 |
<span class="h1">A URN Namespace for Globus</span> |
| 10 |
|
| 11 |
Abstract |
| 12 |
|
| 13 |
This document describes a URN (Uniform Resource Name) namespace to be |
| 14 |
used by Globus for naming persistent resources. |
| 15 |
|
| 16 |
Status of This Memo |
| 17 |
|
| 18 |
This document is not an Internet Standards Track specification; it is |
| 19 |
published for informational purposes. |
| 20 |
|
| 21 |
This document is a product of the Internet Engineering Task Force |
| 22 |
(IETF). It represents the consensus of the IETF community. It has |
| 23 |
received public review and has been approved for publication by the |
| 24 |
Internet Engineering Steering Group (IESG). Not all documents |
| 25 |
approved by the IESG are a candidate for any level of Internet |
| 26 |
Standard; see <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>. |
| 27 |
|
| 28 |
Information about the current status of this document, any errata, |
| 29 |
and how to provide feedback on it may be obtained at |
| 30 |
<a href="http://www.rfc-editor.org/info/rfc7853">http://www.rfc-editor.org/info/rfc7853</a>. |
| 31 |
|
| 32 |
Copyright Notice |
| 33 |
|
| 34 |
Copyright (c) 2016 IETF Trust and the persons identified as the |
| 35 |
document authors. All rights reserved. |
| 36 |
|
| 37 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 38 |
Provisions Relating to IETF Documents |
| 39 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 40 |
publication of this document. Please review these documents |
| 41 |
carefully, as they describe your rights and restrictions with respect |
| 42 |
to this document. Code Components extracted from this document must |
| 43 |
include Simplified BSD License text as described in Section 4.e of |
| 44 |
the Trust Legal Provisions and are provided without warranty as |
| 45 |
described in the Simplified BSD License. |
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Martin, et al. Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc7853">RFC 7853</a> A URN Namespace for Globus May 2016</span> |
| 55 |
|
| 56 |
|
| 57 |
Table of Contents |
| 58 |
|
| 59 |
<a href="#section-1">1</a>. Introduction .................................................. <a href="#page-2">2</a> |
| 60 |
<a href="#section-2">2</a>. Specification Template ........................................ <a href="#page-3">3</a> |
| 61 |
<a href="#section-3">3</a>. Examples (Informative) ........................................ <a href="#page-5">5</a> |
| 62 |
<a href="#section-4">4</a>. Namespace Considerations ...................................... <a href="#page-5">5</a> |
| 63 |
<a href="#section-5">5</a>. Community Considerations ...................................... <a href="#page-6">6</a> |
| 64 |
<a href="#section-6">6</a>. Security Considerations ....................................... <a href="#page-6">6</a> |
| 65 |
<a href="#section-7">7</a>. IANA Considerations ........................................... <a href="#page-6">6</a> |
| 66 |
<a href="#section-8">8</a>. Normative References .......................................... <a href="#page-6">6</a> |
| 67 |
Acknowledgments .................................................. <a href="#page-7">7</a> |
| 68 |
Authors' Addresses ............................................... <a href="#page-7">7</a> |
| 69 |
|
| 70 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 71 |
|
| 72 |
Globus (<a href="https://www.globus.org">https://www.globus.org</a>) is a software-as-a-service provider |
| 73 |
that develops and operates services and tools for the global research |
| 74 |
and education community. |
| 75 |
|
| 76 |
Globus provides multiple services for users across many institutions, |
| 77 |
primarily for research driven by high-performance computing. Globus |
| 78 |
creates unique identifiers that will persist in external systems and |
| 79 |
must be identifiable as references to Globus entities. |
| 80 |
|
| 81 |
To address this need, this document requests that a formal URN space |
| 82 |
type be assigned as described in <a href="./rfc3406#section-4.3">Section 4.3 of [RFC3406]</a>. |
| 83 |
|
| 84 |
|
| 85 |
|
| 86 |
|
| 87 |
|
| 88 |
|
| 89 |
|
| 90 |
|
| 91 |
|
| 92 |
|
| 93 |
|
| 94 |
|
| 95 |
|
| 96 |
|
| 97 |
|
| 98 |
|
| 99 |
|
| 100 |
|
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Martin, et al. Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc7853">RFC 7853</a> A URN Namespace for Globus May 2016</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Specification Template</span> |
| 114 |
|
| 115 |
Namespace ID: |
| 116 |
|
| 117 |
globus |
| 118 |
|
| 119 |
Registration Information: |
| 120 |
|
| 121 |
Version 1 |
| 122 |
Date: 2016-03-18 |
| 123 |
|
| 124 |
Declared Registrant of the Namespace: |
| 125 |
|
| 126 |
Globus Project Lead |
| 127 |
401 N Michigan Ave |
| 128 |
Suite 900 |
| 129 |
Chicago, Illinois 60611 |
| 130 |
USA |
| 131 |
|
| 132 |
Email: [email protected] |
| 133 |
|
| 134 |
The position of Globus Project Lead is currently filled by Steve |
| 135 |
Tuecke. |
| 136 |
|
| 137 |
Declaration of Syntactic Structure: |
| 138 |
|
| 139 |
The Namespace Specific String (NSS) of all URNs that use the |
| 140 |
"globus" NID shall have the following structure: |
| 141 |
|
| 142 |
<URN> ::= "urn:" "globus" ":" <NSS> |
| 143 |
|
| 144 |
<NSS> ::= <SNID> | <SNID> ":" <subnamespace-specific-string> |
| 145 |
|
| 146 |
<SNID> ::= 1*<non-colon-chars> |
| 147 |
|
| 148 |
<subnamespace-specific-string> ::= 1*<URN chars> |
| 149 |
|
| 150 |
<non-colon-chars> ::= <non-colon-trans> | "%" <hex> <hex> |
| 151 |
|
| 152 |
<non-colon-trans> ::= <upper> | <lower> | <number> | |
| 153 |
<non-colon-other> |
| 154 |
|
| 155 |
<non-colon-other> ::= "(" | ")" | "+" | "," | "-" | "." | "=" | |
| 156 |
"@" | ";" | "$" | "_" | "!" | "*" | "'" |
| 157 |
|
| 158 |
The "SNID" is the top-level segment of the NSS. It is a required |
| 159 |
US-ASCII string, subject to the above syntax, that conforms to the |
| 160 |
URN syntax requirements (see [<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>]). It identifies a category |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Martin, et al. Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc7853">RFC 7853</a> A URN Namespace for Globus May 2016</span> |
| 167 |
|
| 168 |
|
| 169 |
of Globus entities, often associated with a particular Globus |
| 170 |
service. For example "auth" could be used as an SNID for |
| 171 |
identifiers generated by the Globus authentication and |
| 172 |
authorization service (Globus Auth). |
| 173 |
|
| 174 |
The "subnamespace-specific-string" is an optional US-ASCII string |
| 175 |
and second-level segment of the NSS, belonging to the "SNID" |
| 176 |
context, subject to the above syntax and conformant to the URN |
| 177 |
syntax requirements (see [<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>]). "subnamespace-specific- |
| 178 |
string" identifies a category of thing within that Globus service, |
| 179 |
such as "scope:transfer.api.globus.org:all" |
| 180 |
|
| 181 |
Relevant Ancillary Documentation: |
| 182 |
|
| 183 |
None. |
| 184 |
|
| 185 |
Identifier Uniqueness Considerations: |
| 186 |
|
| 187 |
Identifier uniqueness will be enforced by the Globus Project Lead. |
| 188 |
The Globus Project Lead may sub-delegate part of the namespace to |
| 189 |
third parties. It will not be permissible, neither by the Globus |
| 190 |
Project Lead nor any third party, to reassign previously assigned |
| 191 |
URNs. A practical consequence is that a previously assigned |
| 192 |
subnamespace cannot be reassigned, unless additional arrangements |
| 193 |
are made to prevent identifier reassignments. |
| 194 |
|
| 195 |
Identifier Persistence Considerations: |
| 196 |
|
| 197 |
Identifiers will never be reassigned, but in some circumstances |
| 198 |
they may be invalidated by the Globus Project Lead or by a third |
| 199 |
party. |
| 200 |
|
| 201 |
Process of Identifier Assignment: |
| 202 |
|
| 203 |
Assignment of subnamespace identifiers is limited to the Globus |
| 204 |
Project Lead and those authorities that are specifically |
| 205 |
designated by the Globus Project Lead. The Globus Project Lead |
| 206 |
may assign portions of the globus namespace (specifically, those |
| 207 |
under designated subnamespace identifiers) for assignment by third |
| 208 |
parties. |
| 209 |
|
| 210 |
Process of Identifier Resolution: |
| 211 |
|
| 212 |
None currently. |
| 213 |
|
| 214 |
Future versions of this document may define resources that can be |
| 215 |
used to resolve Globus identifiers. |
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Martin, et al. Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc7853">RFC 7853</a> A URN Namespace for Globus May 2016</span> |
| 223 |
|
| 224 |
|
| 225 |
Rules for Lexical Equivalence: |
| 226 |
|
| 227 |
No additional rules beyond those specified in <a href="./rfc2141">RFC 2141</a>. |
| 228 |
|
| 229 |
Conformance with URN Syntax: |
| 230 |
|
| 231 |
No special considerations. |
| 232 |
|
| 233 |
Validation Mechanism: |
| 234 |
|
| 235 |
None currently. |
| 236 |
|
| 237 |
Future versions of this document may define resources that can be |
| 238 |
used to validate Globus identifiers. |
| 239 |
|
| 240 |
Scope: |
| 241 |
|
| 242 |
Global. |
| 243 |
|
| 244 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Examples (Informative)</span> |
| 245 |
|
| 246 |
The following examples are based on plans for the Globus URN. They |
| 247 |
are therefore not guaranteed to be valid. |
| 248 |
|
| 249 |
The Globus Auth service defines the "auth" SNID and contains the |
| 250 |
following URNs: |
| 251 |
|
| 252 |
o urn:globus:auth:scope:transfer.api.globus.org:all |
| 253 |
|
| 254 |
o urn:globus:auth:grants:dependent_token |
| 255 |
|
| 256 |
A hypothetical service, the Globus Groups service, would have a |
| 257 |
distinct SNID. If that SNID were "groups", it might have URNs such |
| 258 |
as the following: |
| 259 |
|
| 260 |
o urn:globus:groups:group:669b572e-9de4-11e5-966e-3c970e0c9cc4 |
| 261 |
|
| 262 |
o urn:globus:groups:memberships:72e1c6c6-9de4-11e5-966e-3c970e0c9cc4 |
| 263 |
|
| 264 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Namespace Considerations</span> |
| 265 |
|
| 266 |
The current set of existing IANA namespaces are insufficient because |
| 267 |
Globus will be creating unique identifiers that will persist in the |
| 268 |
external system; these identifiers must be identifiable as references |
| 269 |
to Globus entities. |
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Martin, et al. Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc7853">RFC 7853</a> A URN Namespace for Globus May 2016</span> |
| 279 |
|
| 280 |
|
| 281 |
The use of the Globus namespace is expected to be broad, including |
| 282 |
but not limited to usage for: |
| 283 |
|
| 284 |
o OAuth2 scopes (see [<a href="./rfc6749" title=""The OAuth 2.0 Authorization Framework"">RFC6749</a>]) |
| 285 |
|
| 286 |
o OAuth2 custom extension grants |
| 287 |
|
| 288 |
o Entity identification for Globus Services |
| 289 |
|
| 290 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Community Considerations</span> |
| 291 |
|
| 292 |
Members of the Globus community will benefit from persistent and |
| 293 |
globally unique identifiers for use in software and in conformance |
| 294 |
with protocols developed and used by Globus and third-party |
| 295 |
collaborators. |
| 296 |
|
| 297 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span> |
| 298 |
|
| 299 |
There are no special meanings for characters in the NSS. Thus, there |
| 300 |
are no additional security considerations other than those normally |
| 301 |
associated with the use and resolution of URNs in general, which are |
| 302 |
described in [<a href="./rfc1737" title=""Functional Requirements for Uniform Resource Names"">RFC1737</a>] and [<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>]. |
| 303 |
|
| 304 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. IANA Considerations</span> |
| 305 |
|
| 306 |
IANA has registered the "globus" namespace identifier (NID) in the |
| 307 |
"Formal URN Namespaces" registry located at |
| 308 |
<<a href="http://www.iana.org/assignments/urn-namespaces">http://www.iana.org/assignments/urn-namespaces</a>>. |
| 309 |
|
| 310 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Normative References</span> |
| 311 |
|
| 312 |
[<a id="ref-RFC1737">RFC1737</a>] Sollins, K. and L. Masinter, "Functional Requirements for |
| 313 |
Uniform Resource Names", <a href="./rfc1737">RFC 1737</a>, DOI 10.17487/RFC1737, |
| 314 |
December 1994, <<a href="http://www.rfc-editor.org/info/rfc1737">http://www.rfc-editor.org/info/rfc1737</a>>. |
| 315 |
|
| 316 |
[<a id="ref-RFC2141">RFC2141</a>] Moats, R., "URN Syntax", <a href="./rfc2141">RFC 2141</a>, DOI 10.17487/RFC2141, |
| 317 |
May 1997, <<a href="http://www.rfc-editor.org/info/rfc2141">http://www.rfc-editor.org/info/rfc2141</a>>. |
| 318 |
|
| 319 |
[<a id="ref-RFC3406">RFC3406</a>] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, |
| 320 |
"Uniform Resource Names (URN) Namespace Definition |
| 321 |
Mechanisms", <a href="https://www.rfc-editor.org/bcp/bcp66">BCP 66</a>, <a href="./rfc3406">RFC 3406</a>, DOI 10.17487/RFC3406, |
| 322 |
October 2002, <<a href="http://www.rfc-editor.org/info/rfc3406">http://www.rfc-editor.org/info/rfc3406</a>>. |
| 323 |
|
| 324 |
[<a id="ref-RFC6749">RFC6749</a>] Hardt, D., Ed., "The OAuth 2.0 Authorization Framework", |
| 325 |
<a href="./rfc6749">RFC 6749</a>, DOI 10.17487/RFC6749, October 2012, |
| 326 |
<<a href="http://www.rfc-editor.org/info/rfc6749">http://www.rfc-editor.org/info/rfc6749</a>>. |
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Martin, et al. Informational [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc7853">RFC 7853</a> A URN Namespace for Globus May 2016</span> |
| 335 |
|
| 336 |
|
| 337 |
Acknowledgments |
| 338 |
|
| 339 |
The authors would like to thank Stephen Rosen and Vas Vasiliadis for |
| 340 |
proofreading this document and providing valuable feedback. |
| 341 |
|
| 342 |
Authors' Addresses |
| 343 |
|
| 344 |
Stuart Martin |
| 345 |
University of Chicago |
| 346 |
401 N Michigan Ave |
| 347 |
Suite 900 |
| 348 |
Chicago, Illinois 60611 |
| 349 |
United States |
| 350 |
|
| 351 |
Email: [email protected] |
| 352 |
|
| 353 |
|
| 354 |
Steve Tuecke |
| 355 |
University of Chicago |
| 356 |
401 N Michigan Ave |
| 357 |
Suite 900 |
| 358 |
Chicago, Illinois 60611 |
| 359 |
United States |
| 360 |
|
| 361 |
Email: [email protected] |
| 362 |
|
| 363 |
|
| 364 |
Brendan McCollam |
| 365 |
University of Chicago |
| 366 |
401 N Michigan Ave |
| 367 |
Suite 900 |
| 368 |
Chicago, Illinois 60611 |
| 369 |
United States |
| 370 |
|
| 371 |
Email: [email protected] |
| 372 |
|
| 373 |
|
| 374 |
Mattias Lidman |
| 375 |
University of Chicago |
| 376 |
401 N Michigan Ave |
| 377 |
Suite 900 |
| 378 |
Chicago, Illinois 60611 |
| 379 |
United States |
| 380 |
|
| 381 |
Email: [email protected] |
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
Martin, et al. Informational [Page 7] |
| 389 |
</pre> |