URN Namespace for the North Atlantic Treaty Organization (NATO)
RFC 7467
Document | Type |
RFC - Informational
(April 2015; No errata)
Was draft-murdock-nato-nid (individual in app area)
|
|
---|---|---|---|
Author | Aidan Murdock | ||
Last updated | 2015-10-14 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | Barry Leiba | ||
Shepherd write-up | Show (last changed 2014-11-19) | ||
IESG | IESG state | RFC 7467 (Informational) | |
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Barry Leiba | ||
Send notices to | (None) | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) A. Murdock Request for Comments: 7467 NATO C&I Agency Category: Informational April 2015 ISSN: 2070-1721 URN Namespace for the North Atlantic Treaty Organization (NATO) Abstract This document allocates a formal Uniform Resource Name (URN) namespace for assignment by the North Atlantic Treaty Organization (NATO), as specified in RFC 3406. 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 Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7467. Copyright Notice Copyright (c) 2015 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. 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. Murdock Informational [Page 1] RFC 7467 URN Namespace for NATO April 2015 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 ....................... 5 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 .................................... 6 4. Community Considerations .................................... 6 5. Security Considerations ..................................... 7 6. IANA Considerations ......................................... 7 7. Conclusions ................................................. 7 8. References .................................................. 7 8.1. Normative References ................................... 7 8.2. Informative References ................................. 8 Acknowledgments ................................................ 8 Author's Address ............................................... 8 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 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 [7]. 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.Show full document text