[Docs] [txt|pdf] [Tracker] [Email] [Nits]

Versions: 00 01 02 03 RFC 7467

INTERNET-DRAFT                                               A. Murdock
Intended status: Informational                          NATO C&I Agency
Expires: March 11, 2015                              September 11, 2014



                           URN Namespace for NATO
                       draft-murdock-nato-nid-00.txt


Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   This Internet-Draft will expire on March 18, 2015.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors. All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) 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.






Murdock                 Expires Feb. 21, 2015                  [Page 1]


Internet-Draft           URN Namespace for NATO             September 2014

Abstract

   This document describes a Uniform Resource Name (URN) namespace
   primarily for uniquely identifying Extensible Markup Language (XML)
   artifacts that provide information about NATO message text formats
   and service specifications as described in various NATO standards
   [4], instructions and publications.

Table of Contents


   1. Introduction...................................................2
   2. Specification Template.........................................3
      2.1. Namespace ID:.............................................3
      2.2. Registration Information:.................................3
      2.3. Declared Registrant of the Namespace:.....................3
      2.4. Declaration of Syntactic Structure:.......................3
      2.5. Relevant Ancillary Documentation:.........................4
      2.6. Identifier Uniqueness Considerations......................4
      2.7. Identifier Persistence Considerations:....................4
      2.8. Process of Identifier Assignment:.........................4
      2.9. Process for Identifier Resolution:........................5
      2.10. Rules for Lexical Equivalence:...........................5
      2.11. Conformance with URN Syntax:.............................5
      2.12. Validation Mechanism:....................................5
      2.13. Scope:...................................................5
   3. Namespace Considerations.......................................5
   4. Community Considerations.......................................6
   5. Security Considerations........................................6
   6. IANA Considerations............................................6
   7. Conclusions....................................................6
   8. References.....................................................7
      8.1. Normative References......................................7
      8.2. Informative References....................................7
   9. Acknowledgments................................................7

1. Introduction

   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 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 an Allied Procedural
   Publication Number 11 (APP-11) message catalogue.




Murdock                  Expires Mar 11, 2014                  [Page 2]


Internet-Draft           URN Namespace for NATO             September 2014


   Prior to 2008 these messages were only available as slash delimited
   textual messages. Since 2008, the APP-11 message catalogue (expresses
   message definitions) also includes XML-MTF definitions for these
   messages, giving rise to a need to define and manage a URN namespace
   rooted in the "nato" NID.

2. Specification Template

2.1. Namespace ID:

   The Namespace ID "nato" is requested.

2.2. Registration Information:

   Version 1

   Date: 2014-09-11

2.3. Declared Registrant of the Namespace:

   Registering Organization:

   North Atlantic Treaty Organization (NATO)

   Communications & Information Services Agency (NCIA)

   Address: SHAPE, 7010, Belgium

   Declared Contact:

   Role: NATO Naming and Addressing Authority (NRA)

   Email: nra@ncia.nato.int

2.4. Declaration of Syntactic Structure:

   The Namespace Specific String (NSS) of all URNs that use the "nato"
   NID shall have the following structure:

   urn:nato:<Type>:<Source>

   The "Type" is a required US-ASCII string that conforms to the URN
   syntax requirements (see RFC 2141 [1]) and defines a particular
   category or type of named resources, such as "mtf"





Murdock                  Expires Mar 11, 2014                  [Page 3]


Internet-Draft           URN Namespace for NATO             September 2014


   The "Source" is an optional US-ASCII string that conforms to the URN
   syntax requirements (see RFC 2141 [1]) and defines a particular
   standard, catalogue or other source of 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 managing the assignments of both "Type" and
   "Source" strings. The NRA may also assign URNs in sub-trees below the
   level of the Type or Source as needed. They will also ensure a
   registry of the resulting namespace is maintained.

2.5. Relevant Ancillary Documentation:

   APP-11 - the ADatP-3 message catalogue

   AdatP-3 - The message text format standard promulgated under STANAG
   5500 ed. 7

   The interim NATO Metadata Registry and Repository (NMRR) webpage can
   be found at https://nmrr.ncia.nato.int/home.htm

2.6. Identifier Uniqueness Considerations:

   The NRA, as registrar, shall directly assure 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 namespace has been validated
   against the existing contents of the registry. URN identifiers shall
   be assigned to at most one resource and not reassigned.

2.7. Identifier Persistence Considerations:

   The Registrar may assign URNs in sub-trees below the level of Type or
   Standard, but once registered, URNs shall not be re-assigned. Within
   the registry, their status as active or archive shall be recorded.

2.8. Process of Identifier Assignment:

   A namespace specific string within the NATO namespace will only be
   assigned upon advancement of a relevant specification. The Registrar
   checks all requested identifiers against the existing registrations
   within urn:nato to ensure uniqueness and encourage relevance. At this
   time, the possibility of delegating registration activities for the
   sub-tree is evaluated, subject to supporting agreements. Otherwise,
   such responsibilities remain with the NRA as overarching Registrar.
   The urn is then registered with appropriate metadata and an


Murdock                  Expires Mar 11, 2014                  [Page 4]


Internet-Draft           URN Namespace for NATO             September 2014


   authorized request for URN resolution can be initiated (if
   necessary).

2.9. Process for Identifier Resolution:

   The namespace is not currently listed with a Resolution Discovery
   System (RDS) [3]. In the future, URNs from this namespace may be                                                          rd        resolved using a NATO listing in an RDS, using a 3  party listed
   resolver, using an unlisted, private resolver, or some combination of
   these.  The resolution method for each sub-tree will be registered
   with the NRA Registrar.

2.10. Rules for Lexical Equivalence:

   No special considerations.  The rules for lexical equivalence
   specified in RFC 2141 apply.

2.11. Conformance with URN Syntax:

   No special considerations.

2.12. Validation Mechanism:

   None specified. It will be conducted as part of the application for
   identifier registration as indicated in preceding paragraphs.

2.13. Scope:

   Global.

3. Namespace Considerations

   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 [4],
   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
   [5] to use unique, relevant, reliable, permanent, managed and
   accessible namespace names for its XML products. It also provides



Murdock                  Expires Mar 11, 2014                  [Page 5]


Internet-Draft           URN Namespace for NATO             September 2014


   NATO the opportunity to leverage the use of URNs for persistent
   naming of non-XML resources.

4. Community Considerations

   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 [4].

   Though these are NATO-published standards [4], they represent the
   consensus of multi-national working groups, are implemented in
   commercial products and used by partners within the international
   community.

   In the case of MTF standards [5], the responsibility for its
   development and maintenance belongs to the NATO C3 Board's Message
   Text Formats (MFT) Capability Team [5].  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" [AC/322-N(2014)0091-AS1].



5. Security Considerations

   This document introduces no additional security considerations beyond
   those associated with the use and resolution of URNs in general.

   Distribution of NATO information in any form is subject to its
   security policies.

6. IANA Considerations

   This document defines a URN NID registration of "nato", which is
   requested to be entered into the IANA registry located at
   <http://www.iana.org/assignments/urn-namespaces>.

7. Conclusions

   It is necessary that a standards body, like NATO, ensures its
   messages, service specifications and other XML artifacts are based in
   namespaces that can be described using unique, persistent and managed
   URNs.  Considering its role as an information broker between many


Murdock                  Expires Mar 11, 2014                  [Page 6]


Internet-Draft           URN Namespace for NATO             September 2014


   disparate communities, this document recommends a formal namespace
   identifier (NID) urn:nato for Uniform Resource Names (URN) associated
   with NATO information products.

8. References

8.1. Normative References

   [1]   Moats, R., "URN Syntax", RFC 2141, May 1997.

   [2]   Daigle, L., van Gulik, D., Iannella, R. and P. Faltstrom,
         "Uniform Resource Name (URN) Namespace Definition Mechanisms",
         BCP 66, RFC 3406, October 2002.

   [3]   Sollins, K., "Architectural Principles of Uniform Resource Name
         Resolution", RFC 2276, January 1998.

8.2. Informative References

   [4]   List of Current NATO Standards (publicly available hosted by
         NATO Standardization Office):
         http://nso.nato.int/nso/nsdd/listpromulg.html

   [5]   The Message Text Format Capability Team website:
         https://nhqc3s.hq.nato.int/Default.aspx

   [AC/322-N(2014)0091-AS1] NATO notice which specifies that partners
             that have, or intend to introduce, systems interoperable
             with NATO MTFs may join the respective NATO working group,
             subject to the approval of the C3 Board.

9. Acknowledgments

   The author acknowledges and appreciates the support and expertise
   provided by Nanda Kol and Ulrich Ritgen.

   This document was prepared using 2-Word-v2.0.template.dot.










Murdock                  Expires Mar 11, 2014                  [Page 7]


Internet-Draft           URN Namespace for NATO             September 2014


Authors' Addresses

   Aidan Murdock
   NATO C&I Agency
   Core Enterprise Services
   Naming and Registration Authority
   SHAPE, Belgium
   7010

   Email: Aidan.murdock@ncia.nato.int







































Murdock                  Expires Mar 11, 2014                  [Page 8]


Html markup produced by rfcmarkup 1.129d, available from https://tools.ietf.org/tools/rfcmarkup/