1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
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
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
|
<pre>Internet Engineering Task Force (IETF) A. Murdock
Request for Comments: 7467 NATO C&I Agency
Category: Informational April 2015
ISSN: 2070-1721
<span class="h1">URN Namespace for the North Atlantic Treaty Organization (NATO)</span>
Abstract
This document allocates a formal Uniform Resource Name (URN)
namespace for assignment by the North Atlantic Treaty Organization
(NATO), as specified in <a href="./rfc3406">RFC 3406</a>. At this time, the URN will be used
primarily to uniquely identify Extensible Markup Language (XML)
artefacts that provide information about NATO message text formats
and service specifications as described in various NATO standards,
instructions, and publications.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc7467">http://www.rfc-editor.org/info/rfc7467</a>.
Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
<span class="grey">Murdock Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc7467">RFC 7467</a> URN Namespace for NATO April 2015</span>
Table of Contents
<a href="#section-1">1</a>. Introduction ................................................ <a href="#page-2">2</a>
<a href="#section-2">2</a>. Specification Template ...................................... <a href="#page-3">3</a>
<a href="#section-2.1">2.1</a>. Namespace ID ........................................... <a href="#page-3">3</a>
<a href="#section-2.2">2.2</a>. Registration Information ............................... <a href="#page-3">3</a>
<a href="#section-2.3">2.3</a>. Declared Registrant of the Namespace ................... <a href="#page-3">3</a>
<a href="#section-2.4">2.4</a>. Declaration of Syntactic Structure ..................... <a href="#page-3">3</a>
<a href="#section-2.5">2.5</a>. Relevant Ancillary Documentation ....................... <a href="#page-4">4</a>
<a href="#section-2.6">2.6</a>. Identifier Uniqueness Considerations ................... <a href="#page-4">4</a>
<a href="#section-2.7">2.7</a>. Identifier Persistence Considerations .................. <a href="#page-4">4</a>
<a href="#section-2.8">2.8</a>. Process of Identifier Assignment ....................... <a href="#page-5">5</a>
<a href="#section-2.9">2.9</a>. Process for Identifier Resolution ...................... <a href="#page-5">5</a>
<a href="#section-2.10">2.10</a>. Rules for Lexical Equivalence ......................... <a href="#page-5">5</a>
<a href="#section-2.11">2.11</a>. Conformance with URN Syntax ........................... <a href="#page-5">5</a>
<a href="#section-2.12">2.12</a>. Validation Mechanism .................................. <a href="#page-5">5</a>
<a href="#section-2.13">2.13</a>. Scope ................................................. <a href="#page-5">5</a>
<a href="#section-3">3</a>. Namespace Considerations .................................... <a href="#page-6">6</a>
<a href="#section-4">4</a>. Community Considerations .................................... <a href="#page-6">6</a>
<a href="#section-5">5</a>. Security Considerations ..................................... <a href="#page-7">7</a>
<a href="#section-6">6</a>. IANA Considerations ......................................... <a href="#page-7">7</a>
<a href="#section-7">7</a>. Conclusions ................................................. <a href="#page-7">7</a>
<a href="#section-8">8</a>. References .................................................. <a href="#page-7">7</a>
<a href="#section-8.1">8.1</a>. Normative References ................................... <a href="#page-7">7</a>
<a href="#section-8.2">8.2</a>. Informative References ................................. <a href="#page-8">8</a>
Acknowledgments ................................................ <a href="#page-8">8</a>
Author's Address ............................................... <a href="#page-8">8</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
Historically, NATO has used standardized character-oriented message
text formats (MTF) to interoperate, report, and exchange information
both among its commands and with national entities, commercial
partners, and Non-Governmental Organizations (NGOs). These MTFs are
generated using the NATO Message Text Formatting System (FORMETS) in
accordance with the rules, constructions, and vocabulary specified
within the Allied Data Publication Number 3 (ADatP-3). Almost 400
NATO-defined messages that conform to ADatP-3 are contained in the
Allied Procedural Publication Number 11 (APP-11) NATO Message
Catalogue [<a href="#ref-7" title=""NATO Message Catalogue - APP-11(C) Change 1"">7</a>].
Prior to 2008, these messages were only available as slash-delimited
textual messages. Since 2008, the APP-11 message catalogue also
includes XML-MTF definitions for these messages, giving rise to a
need to define and manage a URN namespace to name the XML namespaces.
To address this need, this document requests that a formal URN space
type be assigned as described in <a href="./rfc3406#section-4.3">Section 4.3 of RFC 3406</a>.
<span class="grey">Murdock Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc7467">RFC 7467</a> URN Namespace for NATO April 2015</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Specification Template</span>
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Namespace ID</span>
The Namespace ID (NID) "nato" has been assigned by IANA.
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Registration Information</span>
Version 1
Date: 2014-09-11
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Declared Registrant of the Namespace</span>
Registering Organization:
Name: North Atlantic Treaty Organization (NATO)
Communications & Information Agency (NCIA)
Address: SHAPE, 7010, Belgium
Declared Contact: NATO Naming and Addressing Registration
Authority (NRA)
Email: nra@ncia.nato.int
<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. Declaration of Syntactic Structure</span>
The Namespace Specific String (NSS) of all URNs that use the "nato"
NID shall have the following structure:
<URN> ::= "urn:" "nato" ":" <NSS>
<NSS> ::= <Type> | <Type> ":" <Source> |
<Type> ":" <Source> 1*( ":" <segment> )
<Type> ::= 1*<non-colon chars>
<Source> ::= 1*<non-colon chars>
<segment> ::= 1*<non-colon chars>
<non-colon chars> ::= <non-colon trans> | "%" <hex> <hex>
<non-colon trans> ::= <upper> | <lower> | <number> |
<non-colon other>
<hex> ::= <number> | "A" | "B" | "C" | "D" | "E" | "F" |
"a" | "b" | "c" | "d" | "e" | "f"
<non-colon other> ::= "(" | ")" | "+" | "," | "-" | "." |
"=" | "@" | ";" | "$" |"_" | "!" | "*" | "'"
<span class="grey">Murdock Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc7467">RFC 7467</a> URN Namespace for NATO April 2015</span>
The "Type" is the top-level segment of the NSS. It is a required
US-ASCII string, subject to the above syntax, that conforms to the
URN syntax requirements (see <a href="./rfc2141">RFC 2141</a> [<a href="#ref-1" title=""URN Syntax"">1</a>]). It identifies a
particular category or type of named resources, such as "mtf".
The "Source" is the second-level segment of the NSS, belonging to the
"Type" context. At this time, not all "Type" segments have "Source"
children, making "Source" an optional US-ASCII string, subject to the
above syntax and conformant to the URN syntax requirements (see <a href="./rfc2141">RFC</a>
<a href="./rfc2141">2141</a> [<a href="#ref-1" title=""URN Syntax"">1</a>]). "Source" identifies a particular standard, catalogue, or
other relevant specifications.
The NATO Naming and Registration Authority (NRA) functions as a Local
Internet Registry under RIPE NCC and will also serve as the
responsible registrar for assigning the first two levels of segments
within the NSS ("Type" and "Source"). The NRA may directly assign
segments below these levels of the namespace hierarchy, or delegate
assignment responsibilities for segments below the second level
(i.e., below "Source") at its discretion. In either case, the NRA
will ensure that a registry of the resulting namespace is maintained.
<span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>. Relevant Ancillary Documentation</span>
ADatP-3 - NATO, "Concept of NATO Message Text Formatting System
(Conformets) - ADatP-3 (A)", STANAG 5500 - Edition 7, November 2010.
<span class="h3"><a class="selflink" id="section-2.6" href="#section-2.6">2.6</a>. Identifier Uniqueness Considerations</span>
The NRA, as registrar, shall directly ensure the global uniqueness of
the assigned strings. Though responsibility for administration of
sub-trees may be delegated, these shall not be published to the
registry or be requested to be resolved by any URN resolver until the
uniqueness of the resulting urn:nato URN has been validated against
the existing contents of the registry. URN identifiers shall be
assigned to one resource at most and not reassigned.
<span class="h3"><a class="selflink" id="section-2.7" href="#section-2.7">2.7</a>. Identifier Persistence Considerations</span>
The Registrar may assign URNs in sub-trees below the level of Type or
Standard; however, once registered, URNs shall not be reassigned.
Within the registry, their status as "active" or "archive" shall be
recorded.
<span class="grey">Murdock Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc7467">RFC 7467</a> URN Namespace for NATO April 2015</span>
<span class="h3"><a class="selflink" id="section-2.8" href="#section-2.8">2.8</a>. Process of Identifier Assignment</span>
A namespace-specific string within the NATO namespace will only be
assigned upon advancement of a relevant specification. The Registrar
will check all requested identifiers against the existing
registrations within urn:nato to ensure uniqueness and encourage
relevance.
The assignment may include delegated registration activities for the
sub-tree if underpinned by supporting agreements. Otherwise, such
responsibilities remain with the NRA as the overarching Registrar.
In any case, the URN must be registered with appropriate metadata
before an authorized request for URN resolution can be initiated (if
necessary).
<span class="h3"><a class="selflink" id="section-2.9" href="#section-2.9">2.9</a>. Process for Identifier Resolution</span>
The namespace is not currently listed with a Resolution Discovery
System (RDS) [<a href="#ref-3" title=""Architectural Principles of Uniform Resource Name Resolution"">3</a>]. In the future, URNs from this namespace may be
resolved using a NATO listing in an RDS, using a third-party-listed
resolver, an unlisted private resolver, or some combination of these.
The resolution method for each segment will be registered with the
NRA Registrar.
<span class="h3"><a class="selflink" id="section-2.10" href="#section-2.10">2.10</a>. Rules for Lexical Equivalence</span>
No special considerations. The rules for lexical equivalence
specified in <a href="./rfc2141">RFC 2141</a> apply.
<span class="h3"><a class="selflink" id="section-2.11" href="#section-2.11">2.11</a>. Conformance with URN Syntax</span>
No special considerations.
<span class="h3"><a class="selflink" id="section-2.12" href="#section-2.12">2.12</a>. Validation Mechanism</span>
None specified. It will be conducted as part of the application for
identifier registration as indicated in preceding paragraphs.
<span class="h3"><a class="selflink" id="section-2.13" href="#section-2.13">2.13</a>. Scope</span>
Global.
<span class="grey">Murdock Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc7467">RFC 7467</a> URN Namespace for NATO April 2015</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Namespace Considerations</span>
In addition to the large number of XML message specifications that
now exist in APP-11, there are other existing and emerging NATO
standard messages expressed as XML, as well as ongoing Web service
specification development. With no single NID registered to NATO,
some of these specifications may be established within locally
relevant, self-generated URN namespaces. Not only does this inhibit
the portability and adoption intended by standards development [<a href="#ref-5" title=""List of Current NATO Standards"">5</a>],
it risks name collisions when exposed to the global context of the
federation of partners for which these messages are destined.
The use of Uniform Resource Names with an appropriate Namespace ID
will enable the various NATO standards committees and working groups
[<a href="#ref-6" title=""NATO HQ C3 Staff Main Page"">6</a>] to use unique, relevant, reliable, permanent, managed, and
accessible namespace names for their XML products.
A dedicated namespace also provides NATO the opportunity to leverage
the use of URNs for persistent naming of non-XML resources.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Community Considerations</span>
The NATO standards development community, and those implementing such
standards, will benefit from publication of this namespace by having
more permanent and reliable names for the XML namespaces defined
within STANAGs, the MTF catalogue (APP-11), and other published
standards [<a href="#ref-5" title=""List of Current NATO Standards"">5</a>].
Though these are NATO-published standards [<a href="#ref-5" title=""List of Current NATO Standards"">5</a>], they represent the
consensus of multi-national working groups, are implemented in
commercial products, and are used by partners within the
international community.
In the case of MTF standards [<a href="#ref-7" title=""NATO Message Catalogue - APP-11(C) Change 1"">7</a>], the responsibility for its
development and maintenance belongs to the NATO C3 Board's Message
Text Formats (MFT) Capability Team [<a href="#ref-6" title=""NATO HQ C3 Staff Main Page"">6</a>]. This team is "open to all
recognized NATO Partners around the Globe in principle. The term
'Partners around the Globe' summarizes all partners that are listed
on the NATO webpage: Euro-Atlantic Partnership Council (EAPC), NATO's
Mediterranean Dialogue (MD), Istanbul Cooperation Initiative (ICI)
and Partners across the globe" [<a href="#ref-8" title=""Request to open MTF CaT to all NATO Partners"">8</a>].
<span class="grey">Murdock Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc7467">RFC 7467</a> URN Namespace for NATO April 2015</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
Since the URNs in this namespace are opaque, there are no additional
security considerations other than those normally associated with the
use and resolution of URIs and URNs in general (see the Security
Considerations in Internet STD 66 [<a href="#ref-4" title=""Uniform Resource Identifier (URI): Generic Syntax"">4</a>], <a href="./rfc2141">RFC 2141</a> [<a href="#ref-1" title=""URN Syntax"">1</a>], and <a href="https://www.rfc-editor.org/bcp/bcp66">BCP 66</a> [<a href="#ref-2" title=""Uniform Resource Names (URN) Namespace Definition Mechanisms"">2</a>]).
It is noted, however, that resolution algorithms and rules for
handling invalid URNs are opaque. Therefore, attempting to resolve a
NATO URN through a resolver other than one operated or delegated by
NATO may return outdated, incorrect, or confusing results.
Distribution of NATO information in any form is subject to its
security policies. Nonetheless, this specification is for public use
and not subject to any NATO security policies.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span>
This document registers the formal URN NID "nato", which has been
entered into the "Formal URN Namespaces" IANA registry [<a href="#ref-9" title=""Uniform Resource Names (URN) Namespaces"">9</a>]. Per
<a href="./rfc3406#section-4.3">Section 4.3 of RFC 3406</a> [<a href="#ref-2" title=""Uniform Resource Names (URN) Namespace Definition Mechanisms"">2</a>], formal NIDs are assigned via IETF
Consensus and are subject to IESG review and acceptance. The
registration template is given in <a href="#section-2">Section 2</a>.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Conclusions</span>
It is necessary that NATO ensures its messages, service
specifications, and other XML artefacts are based in namespaces that
can be described using unique, persistent, and managed URNs.
Considering its role as an information broker between many disparate
communities, this document registers a formal namespace identifier
(NID) "nato" for Uniform Resource Names (URN) associated with NATO
information products and vocabularies: urn:nato.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span>
[<a id="ref-1">1</a>] Moats, R., "URN Syntax", <a href="./rfc2141">RFC 2141</a>, May 1997,
<<a href="http://www.rfc-editor.org/info/rfc2141">http://www.rfc-editor.org/info/rfc2141</a>>.
[<a id="ref-2">2</a>] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom,
"Uniform Resource Names (URN) Namespace Definition Mechanisms",
<a href="https://www.rfc-editor.org/bcp/bcp66">BCP 66</a>, <a href="./rfc3406">RFC 3406</a>, October 2002,
<<a href="http://www.rfc-editor.org/info/rfc3406">http://www.rfc-editor.org/info/rfc3406</a>>.
<span class="grey">Murdock Informational [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc7467">RFC 7467</a> URN Namespace for NATO April 2015</span>
[<a id="ref-3">3</a>] Sollins, K., "Architectural Principles of Uniform Resource Name
Resolution", <a href="./rfc2276">RFC 2276</a>, January 1998,
<<a href="http://www.rfc-editor.org/info/rfc2276">http://www.rfc-editor.org/info/rfc2276</a>>.
[<a id="ref-4">4</a>] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, <a href="./rfc3986">RFC 3986</a>,
January 2005, <<a href="http://www.rfc-editor.org/info/rfc3986">http://www.rfc-editor.org/info/rfc3986</a>>.
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span>
[<a id="ref-5">5</a>] NATO, "List of Current NATO Standards",
<<a href="http://nso.nato.int/nso/nsdd/listpromulg.html">http://nso.nato.int/nso/nsdd/listpromulg.html</a>>.
[<a id="ref-6">6</a>] NATO, "NATO HQ C3 Staff Main Page",
<<a href="https://nhqc3s.hq.nato.int/Default.aspx">https://nhqc3s.hq.nato.int/Default.aspx</a>>.
[<a id="ref-7">7</a>] NATO, "NATO Message Catalogue - APP-11(C) Change 1" STANAG 7149,
Edition 5, September 2010.
[<a id="ref-8">8</a>] NATO, "Request to open MTF CaT to all NATO Partners", document
AC/322-N(2014)0091-AS1, 2014. Available from the NATO Public
Diplomacy Division.
[<a id="ref-9">9</a>] IANA, "Uniform Resource Names (URN) Namespaces",
<<a href="http://www.iana.org/assignments/urn-namespaces">http://www.iana.org/assignments/urn-namespaces</a>>.
Acknowledgments
The author acknowledges and appreciates the support and expertise
provided by Nanda Kol, Ulrich Ritgen, and the urn-nid review team.
Authors' Address
Aidan Murdock
NATO C&I Agency
Core Enterprise Services
Naming and Registration Authority
SHAPE, Belgium
7010
EMail: Aidan.murdock@ncia.nato.int
Murdock Informational [Page 8]
</pre>
|
