Debian Codegraph @

rfc6453.html

raw
1 <pre>Internet Engineering Task Force (IETF) F. Dijkstra
2 Request for Comments: 6453 SARA
3 Category: Informational R. Hughes-Jones
4 ISSN: 2070-1721 DANTE
5 December 2011
6
7
8 <span class="h1">A URN Namespace for the Open Grid Forum (OGF)</span>
9
10 Abstract
11
12 This document describes a URN (Uniform Resource Name) namespace that
13 is engineered by the Open Grid Forum (OGF) for naming persistent
14 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&nbsp;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/rfc6453">http://www.rfc-editor.org/info/rfc6453</a>.
31
32 Copyright Notice
33
34 Copyright (c) 2011 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">Dijkstra &amp; Hughes-Jones Informational [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc6453">RFC 6453</a> URN Namespace for the OGF December 2011</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-1.1">1.1</a>. Requirements Language ......................................<a href="#page-2">2</a>
61 <a href="#section-2">2</a>. URN Specification for "ogf" Namespace ID (NID) ..................<a href="#page-3">3</a>
62 <a href="#section-2.1">2.1</a>. Namespace ID ...............................................<a href="#page-3">3</a>
63 <a href="#section-2.2">2.2</a>. Registration Information ...................................<a href="#page-3">3</a>
64 <a href="#section-2.3">2.3</a>. Declared Registrant of the Namespace .......................<a href="#page-3">3</a>
65 <a href="#section-2.4">2.4</a>. Declaration of Syntactic Structure .........................<a href="#page-3">3</a>
66 <a href="#section-2.5">2.5</a>. Relevant Ancillary Documentation ...........................<a href="#page-4">4</a>
67 <a href="#section-2.6">2.6</a>. Identifier Uniqueness Considerations .......................<a href="#page-4">4</a>
68 <a href="#section-2.7">2.7</a>. Identifier Persistence Considerations ......................<a href="#page-4">4</a>
69 <a href="#section-2.8">2.8</a>. Process of Identifier Assignment ...........................<a href="#page-5">5</a>
70 <a href="#section-2.9">2.9</a>. Process of Identifier Resolution ...........................<a href="#page-5">5</a>
71 <a href="#section-2.10">2.10</a>. Rules for Lexical Equivalence .............................<a href="#page-5">5</a>
72 <a href="#section-2.11">2.11</a>. Conformance with URN Syntax ...............................<a href="#page-5">5</a>
73 <a href="#section-2.12">2.12</a>. Validation Mechanism ......................................<a href="#page-6">6</a>
74 <a href="#section-2.13">2.13</a>. Scope .....................................................<a href="#page-6">6</a>
75 <a href="#section-3">3</a>. Examples (Informative) ..........................................<a href="#page-6">6</a>
76 <a href="#section-4">4</a>. Namespace Considerations ........................................<a href="#page-6">6</a>
77 <a href="#section-5">5</a>. Community Considerations ........................................<a href="#page-7">7</a>
78 <a href="#section-6">6</a>. Security Considerations .........................................<a href="#page-7">7</a>
79 <a href="#section-7">7</a>. IANA Considerations .............................................<a href="#page-7">7</a>
80 <a href="#section-8">8</a>. Acknowledgements ................................................<a href="#page-7">7</a>
81 <a href="#section-9">9</a>. References ......................................................<a href="#page-8">8</a>
82 <a href="#section-9.1">9.1</a>. Normative References .......................................<a href="#page-8">8</a>
83 <a href="#section-9.2">9.2</a>. Informative References .....................................<a href="#page-8">8</a>
84
85 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
86
87 The Open Grid Forum (OGF) is a standardisation development
88 organisation in the field of distributed computing. The OGF produces
89 documents such as working drafts, specifications, and schemata. For
90 more information, see &lt;<a href="http://www.ogf.org/">http://www.ogf.org/</a>&gt;.
91
92 Working groups in the OGF community have expressed the need for
93 global, distributed, persistent identifiers in working drafts and
94 standards. Motivated by this need, the OGF would like to assign URNs
95 to some resources in order to retain unique, permanent, location-
96 independent names for them.
97
98 This namespace specification is for a formal namespace.
99
100 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Requirements Language</span>
101
102 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
103 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
104 document are to be interpreted as described in [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
105
106
107
108 <span class="grey">Dijkstra &amp; Hughes-Jones Informational [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc6453">RFC 6453</a> URN Namespace for the OGF December 2011</span>
111
112
113 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. URN Specification for "ogf" Namespace ID (NID)</span>
114
115 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Namespace ID</span>
116
117 "ogf" (where "ogf" is an acronym for "Open Grid Forum").
118
119 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Registration Information</span>
120
121 Registration Version Number: 1
122 Registration Date: December 2011
123
124 <span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Declared Registrant of the Namespace</span>
125
126 Technical Director
127 Open Grid Forum
128 P.O. Box 1738
129 Muncie, Indiana 47308
130 USA
131 <a href="http://www.ogf.org/">http://www.ogf.org/</a>
132 EMail: [email protected]
133
134 The position of Technical Director is currently fulfilled by Joel
135 Replogle.
136
137 <span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. Declaration of Syntactic Structure</span>
138
139 The formal syntax definitions below are given in ABNF [<a href="./rfc5234" title="&quot;Augmented BNF for Syntax Specifications: ABNF&quot;">RFC5234</a>].
140
141 The namespace-specific string (NSS) in the urn:ogf names hierarchy
142 begins with a subnamespace identifier (SNID), followed by a delimiter
143 and a subnamespace-dependent string
144
145 OGF-URN = "urn:ogf:" SNID ":" SUBNAMESPACE-SPECIFIC-STRING
146
147 where &lt;SNID&gt; is a unique subnamespace identifier for the
148 specification, and &lt;SUBNAMESPACE-SPECIFIC-STRING&gt; is a unique
149 identifier within the subnamespace identifier scope.
150
151 &lt;SNID&gt; has the same syntax as a &lt;NID&gt; as defined in [<a href="./rfc2141" title="&quot;URN Syntax&quot;">RFC2141</a>]:
152
153 SNID = ( ALPHA / DIGIT ) *31( ALPHA / DIGIT / "-" )
154
155 ALPHA and DIGIT are defined in <a href="./rfc5234#appendix-B">Appendix&nbsp;B of [RFC5234]</a>.
156
157 The Technical Director at OGF (or their successors) assigns SNIDs.
158
159
160
161
162
163
164 <span class="grey">Dijkstra &amp; Hughes-Jones Informational [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc6453">RFC 6453</a> URN Namespace for the OGF December 2011</span>
167
168
169 The syntax of &lt;SUBNAMESPACE-SPECIFIC-STRING&gt; is dependent on the
170 &lt;SNID&gt; and MUST be defined by a Grid Forum Document [<a href="#ref-GFD.1" title="&quot;GGF Document Series&quot;">GFD.1</a>]. This
171 document does not pose any additional restrictions to the
172 &lt;SUBNAMESPACE-SPECIFIC-STRING&gt; other than what is defined in the NSS
173 syntax as defined by [<a href="./rfc2141" title="&quot;URN Syntax&quot;">RFC2141</a>] or its successor:
174
175 SUBNAMESPACE-SPECIFIC-STRING = 1*&lt;URN chars&gt;
176
177 &lt;URN chars&gt; is defined in <a href="./rfc2141#section-2.2">Section&nbsp;2.2 of [RFC2141]</a>.
178
179 <span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>. Relevant Ancillary Documentation</span>
180
181 The Technical Director at OGF (or their successors) will keep a list
182 of assigned subnamespace identifiers and associated documentation at
183 &lt;<a href="http://www.ogf.org/urn/">http://www.ogf.org/urn/</a>&gt; [<a href="#ref-URN-OGF" title="&quot;URN:OGF Hierarchy Registry and Documentation&quot;">URN-OGF</a>].
184
185 The procedures regarding how to register a subnamespace identifier
186 are described in [<a href="#ref-GFD.191" title="&quot;Procedure for Registration of Subnamespace Identifiers in the URN:OGF Hierarchy&quot;">GFD.191</a>] and can also be found at the above
187 Website.
188
189 <span class="h3"><a class="selflink" id="section-2.6" href="#section-2.6">2.6</a>. Identifier Uniqueness Considerations</span>
190
191 Identifier uniqueness will be enforced by the Technical Director of
192 the Open Grid Forum.
193
194 The OGF Technical Director may sub-delegate part of the namespace to
195 third parties. It will not be permissible, neither by the OGF nor
196 any third party, to re-assign previously assigned URNs. A practical
197 consequence is that a previously assigned subnamespace cannot be
198 re-assigned, unless additional arrangements are made to prevent
199 identifier re-assignments.
200
201 <span class="h3"><a class="selflink" id="section-2.7" href="#section-2.7">2.7</a>. Identifier Persistence Considerations</span>
202
203 The Technical Director will only assign subnamespace identifiers for
204 persistent resources.
205
206 In order to enforce identifier persistence for individual resources,
207 each document defining subnamespace identifiers MUST contain a
208 section on the type of resource that is specified (e.g., whether a
209 URN in the subnamespace identifies a specific version of a resource,
210 the latest version of a resource, a specific manifestation, or a more
211 general concept).
212
213 The namespace identifier "ogf" MUST NOT change, even if the Open Grid
214 Forum changes its name or is disbanded.
215
216
217
218
219
220 <span class="grey">Dijkstra &amp; Hughes-Jones Informational [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc6453">RFC 6453</a> URN Namespace for the OGF December 2011</span>
223
224
225 <span class="h3"><a class="selflink" id="section-2.8" href="#section-2.8">2.8</a>. Process of Identifier Assignment</span>
226
227 Assignment of subnamespace identifiers is limited to the OGF and
228 those authorities that are specifically designated by the OGF
229 Technical Director of the OGF. The OGF may assign portions of its
230 namespace (specifically, those under designated subnamespace
231 identifiers) for assignment by third parties.
232
233 The details of this process are specified in [<a href="#ref-GFD.191" title="&quot;Procedure for Registration of Subnamespace Identifiers in the URN:OGF Hierarchy&quot;">GFD.191</a>].
234
235 The syntax and semantics of each subnamespace MUST be defined by a
236 Grid Forum Document [<a href="#ref-GFD.1" title="&quot;GGF Document Series&quot;">GFD.1</a>] before the corresponding SNID is
237 assigned.
238
239 <span class="h3"><a class="selflink" id="section-2.9" href="#section-2.9">2.9</a>. Process of Identifier Resolution</span>
240
241 The OGF namespace is not currently listed with a Resolution Discovery
242 System (RDS), but nothing about the namespace prohibits the future
243 definition of appropriate resolution methods or listing with an RDS.
244
245 The OGF will maintain an index of all subnamespace identifiers on its
246 Website &lt;<a href="http://www.ogf.org/urn/">http://www.ogf.org/urn/</a>&gt;. This list may refer to known
247 Resolution Discovery Systems.
248
249 <span class="h3"><a class="selflink" id="section-2.10" href="#section-2.10">2.10</a>. Rules for Lexical Equivalence</span>
250
251 The &lt;SNID&gt; part of URNs in the OGF hierarchy is case insensitive.
252 Thus, the &lt;SNID&gt; MUST be case normalised before comparison.
253
254 The rules for lexical equivalence of the
255 &lt;SUBNAMESPACE-SPECIFIC-STRING&gt; part of URNs in the OGF hierarchy is
256 specific for each SNID and MUST be defined when a SNID is assigned by
257 the OGF Technical Director. These definitions MUST include
258 information about case sensitivity, and in the case of %-escaped
259 octets, MUST define the exact normalisation to be used (e.g.,
260 interpret as octet, interpret as UTF-8, specify type of Unicode
261 normalisation factor, etc.).
262
263 <span class="h3"><a class="selflink" id="section-2.11" href="#section-2.11">2.11</a>. Conformance with URN Syntax</span>
264
265 The intention of this document is to only restrict the syntax of the
266 &lt;SNID&gt;. The syntax of the &lt;SUBNAMESPACE-SPECIFIC-STRING&gt; follows the
267 general syntax of a URN:
268
269 SUBNAMESPACE-SPECIFIC-STRING = 1*&lt;URN chars&gt;
270
271
272
273
274
275
276 <span class="grey">Dijkstra &amp; Hughes-Jones Informational [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc6453">RFC 6453</a> URN Namespace for the OGF December 2011</span>
279
280
281 Documents defining a subnamespace identifier SHOULD specify further
282 syntactic restrictions in &lt;SUBNAMESPACE-SPECIFIC-STRING&gt;. It is
283 RECOMMENDED that these documents forbid the assignment of URNs
284 containing characters in the &lt;reserved&gt; set ("%", "/", "?", and "#")
285 as defined in [<a href="./rfc2141" title="&quot;URN Syntax&quot;">RFC2141</a>]. This is in accordance with <a href="./rfc3986#section-2.2">Section&nbsp;2.2 of
286 [RFC3986]</a>.
287
288 For forward compatibility, it is RECOMMENDED that software
289 implementations that don't validate subnamespace-specific strings
290 validate the syntax according to the generic rules for validating
291 URIs, as defined in [<a href="./rfc3986" title="&quot;Uniform Resource Identifier (URI): Generic Syntax&quot;">RFC3986</a>]. URIs may contain all characters
292 defined in &lt;URN chars&gt;, including the characters in &lt;reserved&gt;
293 (albeit they have a special meaning), as well as the characters "&amp;"
294 and "~".
295
296 <span class="h3"><a class="selflink" id="section-2.12" href="#section-2.12">2.12</a>. Validation Mechanism</span>
297
298 The validation mechanism of URNs in the OGF hierarchy is specific for
299 each SNID and SHOULD be defined when a SNID is assigned by the OGF
300 Technical Director.
301
302 URNs in the OGF hierarchy without an assigned SNID are considered to
303 be invalid.
304
305 <span class="h3"><a class="selflink" id="section-2.13" href="#section-2.13">2.13</a>. Scope</span>
306
307 Global URNs are relevant for the distributed computing community in
308 general, and the Open Grid Forum in particular.
309
310 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Examples (Informative)</span>
311
312 Since no subnamespace identifiers have been defined yet, no actual
313 examples can be given. Therefore, the following examples are not
314 guaranteed to be real or even syntactically correct.
315
316 Grid Forum Documents defining the "gfd" and "network" subnamespace
317 identifiers may give the following examples.
318
319 o urn:ogf:gfd:136
320
321 o urn:ogf:network:canarie.ca:kisti-uninett-glif-001
322
323 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Namespace Considerations</span>
324
325 The Open Grid Forum (OGF) is a standardisation development
326 organisation in the field of distributed computing.
327
328
329
330
331
332 <span class="grey">Dijkstra &amp; Hughes-Jones Informational [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc6453">RFC 6453</a> URN Namespace for the OGF December 2011</span>
335
336
337 The use of the OGF hierarchy is expected to be broad, including but
338 not limited to usage for:
339
340 o Grid Forum Documents
341
342 o XML (Extensible Markup Language) Schemata
343
344 o RDF (Resource Description Framework) Schemata
345
346 The Open Grid Forum is dedicated to openly publishing all technical
347 documentation related to URNs in the OGF hierarchy and allowing
348 unlimited distribution of these documents.
349
350 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Community Considerations</span>
351
352 Members of the distributed computing community will benefit from
353 persistent and globally unique identifiers for use in protocols
354 developed by the Open Grid Forum.
355
356 Practical use of the urn:ogf namespace has been detected, and a
357 formal registration will allow the Open Grid Forum to document this
358 usage and enforce technical review of current practices.
359
360 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
361
362 There are no additional security considerations other than those
363 normally associated with the use and resolution of URNs in general,
364 which are described in [<a href="./rfc1737" title="&quot;Functional Requirements for Uniform Resource Names&quot;">RFC1737</a>], [<a href="./rfc2141" title="&quot;URN Syntax&quot;">RFC2141</a>], and [<a href="./rfc3406" title="&quot;Uniform Resource Names (URN) Namespace Definition Mechanisms&quot;">RFC3406</a>].
365
366 It is recommended that implementers check the OGF registry and
367 documentation [<a href="#ref-URN-OGF" title="&quot;URN:OGF Hierarchy Registry and Documentation&quot;">URN-OGF</a>] before assuming that a given identifier is
368 valid or has a certain meaning.
369
370 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. IANA Considerations</span>
371
372 IANA has registered the "ogf" namespace identifier (NID) with a
373 reference to this document in the "Formal URN Namespaces"
374 sub-registry [<a href="./rfc3406" title="&quot;Uniform Resource Names (URN) Namespace Definition Mechanisms&quot;">RFC3406</a>] of the "Uniform Resource Names (URN)
375 Namespaces" registry [<a href="#ref-URN-NAMESPACES">URN-NAMESPACES</a>].
376
377 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Acknowledgements</span>
378
379 The template and useful examples from [<a href="./rfc3406" title="&quot;Uniform Resource Names (URN) Namespace Definition Mechanisms&quot;">RFC3406</a>] formed the basis for
380 this document. The authors would like to thank Joel Replogle and
381 Andre Mersky for setting up the urn:ogf subnamespace registry.
382 Jeroen van der Ham, Peter Saint-Andre, and Mykyta Yevstifeyev
383 proofread this document and provided valuable feedback.
384
385
386
387
388 <span class="grey">Dijkstra &amp; Hughes-Jones Informational [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc6453">RFC 6453</a> URN Namespace for the OGF December 2011</span>
391
392
393 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. References</span>
394
395 <span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Normative References</span>
396
397 [<a id="ref-GFD.191">GFD.191</a>] Dijkstra, F., Hughes-Jones, R., Newby, G., and J.
398 Replogle, "Procedure for Registration of Subnamespace
399 Identifiers in the URN:OGF Hierarchy", GFD 191,
400 December 2011, &lt;<a href="http://www.ogf.org/documents/GFD.191.pdf">http://www.ogf.org/documents/GFD.191.pdf</a>&gt;.
401
402 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
403 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
404
405 [<a id="ref-RFC2141">RFC2141</a>] Moats, R., "URN Syntax", <a href="./rfc2141">RFC 2141</a>, May 1997.
406
407 [<a id="ref-RFC3986">RFC3986</a>] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
408 Resource Identifier (URI): Generic Syntax", STD 66,
409 <a href="./rfc3986">RFC 3986</a>, January 2005.
410
411 [<a id="ref-RFC5234">RFC5234</a>] Crocker, D., Ed., and P. Overell, "Augmented BNF for
412 Syntax Specifications: ABNF", STD 68, <a href="./rfc5234">RFC 5234</a>,
413 January 2008.
414
415 <span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Informative References</span>
416
417 [<a id="ref-GFD.1">GFD.1</a>] Catlett, C., "GGF Document Series", GFD 1, April 2002,
418 &lt;<a href="http://www.ogf.org/documents/GFD.1.pdf">http://www.ogf.org/documents/GFD.1.pdf</a>&gt;.
419
420 [<a id="ref-RFC1737">RFC1737</a>] Sollins, K. and L. Masinter, "Functional Requirements for
421 Uniform Resource Names", <a href="./rfc1737">RFC 1737</a>, December 1994.
422
423 [<a id="ref-RFC3406">RFC3406</a>] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom,
424 "Uniform Resource Names (URN) Namespace Definition
425 Mechanisms", <a href="https://www.rfc-editor.org/bcp/bcp66">BCP 66</a>, <a href="./rfc3406">RFC 3406</a>, October 2002.
426
427 [<a id="ref-URN-NAMESPACES">URN-NAMESPACES</a>]
428 IANA, "Uniform Resource Names (URN) Namespaces",
429 &lt;<a href="http://www.iana.org/">http://www.iana.org/</a>&gt;.
430
431 [<a id="ref-URN-OGF">URN-OGF</a>] Open Grid Forum, "URN:OGF Hierarchy Registry and
432 Documentation", &lt;<a href="http://www.ogf.org/urn/">http://www.ogf.org/urn/</a>&gt;.
433
434
435
436
437
438
439
440
441
442
443
444 <span class="grey">Dijkstra &amp; Hughes-Jones Informational [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc6453">RFC 6453</a> URN Namespace for the OGF December 2011</span>
447
448
449 Authors' Addresses
450
451 Freek Dijkstra
452 SARA
453 Science Park 121
454 Amsterdam 1098 XG
455 NL
456
457 EMail: [email protected]
458
459
460 Richard Hughes-Jones
461 DANTE
462 City House
463 126-130 Hills Road
464 Cambridge CB2 1PQ
465 UK
466
467 EMail: [email protected]
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500 Dijkstra &amp; Hughes-Jones Informational [Page 9]
501 </pre>