rfc7467v5.txt		rfc7467.txt
	Internet Engineering Task Force (IETF) A. Murdock		Internet Engineering Task Force (IETF) A. Murdock
	Request for Comments: 7467 NATO C&I Agency		Request for Comments: 7467 NATO C&I Agency
	Category: Informational March 2015		Category: Informational April 2015
	ISSN: 2070-1721		ISSN: 2070-1721
	URN Namespace for the North Atlantic Treaty Organization (NATO)		URN Namespace for the North Atlantic Treaty Organization (NATO)
	Abstract		Abstract
	This document allocates a formal Uniform Resource Name (URN)		This document allocates a formal Uniform Resource Name (URN)
	namespace for assignment by the North Atlantic Treaty Organization		namespace for assignment by the North Atlantic Treaty Organization
	(NATO), as specified in RFC 3406. At this time, the URN will be used		(NATO), as specified in RFC 3406. At this time, the URN will be used
	primarily to uniquely identify Extensible Markup Language (XML)		primarily to uniquely identify Extensible Markup Language (XML)
	skipping to change at page 2, line 47		skipping to change at page 2, line 47
	both among its commands and with national entities, commercial		both among its commands and with national entities, commercial
	partners, and Non-Governmental Organizations (NGOs). These MTFs are		partners, and Non-Governmental Organizations (NGOs). These MTFs are
	generated using the NATO Message Text Formatting System (FORMETS) in		generated using the NATO Message Text Formatting System (FORMETS) in
	accordance with the rules, constructions, and vocabulary specified		accordance with the rules, constructions, and vocabulary specified
	within the Allied Data Publication Number 3 (ADatP-3). Almost 400		within the Allied Data Publication Number 3 (ADatP-3). Almost 400
	NATO-defined messages that conform to ADatP-3 are contained in the		NATO-defined messages that conform to ADatP-3 are contained in the
	Allied Procedural Publication Number 11 (APP-11) NATO Message		Allied Procedural Publication Number 11 (APP-11) NATO Message
	Catalogue [7].		Catalogue [7].
	Prior to 2008, these messages were only available as slash-delimited		Prior to 2008, these messages were only available as slash-delimited
	textual messages. Since 2008, the APP-11 message catalogue also		textual messages. Since 2008, the APP-11 message catalogue also
	includes XML-MTF definitions for these messages, giving rise to a		includes XML-MTF definitions for these messages, giving rise to a
	need to define and manage a URN namespace to name the XML namespaces.		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		To address this need, this document requests that a formal URN space
	type be assigned as described in Section 4.3 of RFC 3406.		type be assigned as described in Section 4.3 of RFC 3406.
	2. Specification Template		2. Specification Template
	2.1. Namespace ID		2.1. Namespace ID
	The Namespace ID (NID) "nato" has been assigned by IANA.		The Namespace ID (NID) "nato" has been assigned by IANA.
	skipping to change at page 3, line 22		skipping to change at page 3, line 22
	Version 1		Version 1
	Date: 2014-09-11		Date: 2014-09-11
	2.3. Declared Registrant of the Namespace		2.3. Declared Registrant of the Namespace
	Registering Organization:		Registering Organization:
	Name: North Atlantic Treaty Organization (NATO)		Name: North Atlantic Treaty Organization (NATO)
	Communications & Information Agency (NCIA)		Communications & Information Agency (NCIA)
	Address: SHAPE, 7010, Belgium		Address: SHAPE, 7010, Belgium
	Declared Contact: NATO Naming and Addressing Registration Authority (NRA)		Declared Contact: NATO Naming and Addressing Registration
			Authority (NRA)
	Email: nra@ncia.nato.int		Email: nra@ncia.nato.int
	2.4. Declaration of Syntactic Structure		2.4. Declaration of Syntactic Structure
	The Namespace Specific String (NSS) of all URNs that use the "nato"		The Namespace Specific String (NSS) of all URNs that use the "nato"
	NID shall have the following structure:		NID shall have the following structure:
	<URN> ::= "urn:" "nato" ":" <NSS>		<URN> ::= "urn:" "nato" ":" <NSS>
	<NSS> ::= <Type> | <Type> ":" <Source> | <Type> ":" <Source> 1*( ":"		<NSS> ::= <Type> | <Type> ":" <Source> |
	<segment> )		<Type> ":" <Source> 1*( ":" <segment> )
	<Type> ::= 1*<non-colon chars>		<Type> ::= 1*<non-colon chars>
	<Source> ::= 1*<non-colon chars>		<Source> ::= 1*<non-colon chars>
	<segment> ::= 1*<non-colon chars>		<segment> ::= 1*<non-colon chars>
	<non-colon chars> ::= <non-colon trans> | "%" <hex> <hex>		<non-colon chars> ::= <non-colon trans> | "%" <hex> <hex>
	<non-colon trans> ::= <upper> | <lower> | <number> | <non-colon		<non-colon trans> ::= <upper> | <lower> | <number> |
	other>		<non-colon other>
	<hex> ::= <number> | "A" | "B" | "C" | "D" | "E" | "F" |		<hex> ::= <number> | "A" | "B" | "C" | "D" | "E" | "F" |
	"a" | "b" | "c" | "d" | "e" | "f"		"a" | "b" | "c" | "d" | "e" | "f"
	<non-colon other> ::= "(" | ")" | "+" | "," | "-" | "." |		<non-colon other> ::= "(" | ")" | "+" | "," | "-" | "." |
	"=" | "@" | ";" | "$" |"_" | "!" | "*" | "'"		"=" | "@" | ";" | "$" |"_" | "!" | "*" | "'"
	The "Type" is the top-level segment of the NSS. It is a required		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		US-ASCII string, subject to the above syntax, that conforms to the
	URN syntax requirements (see RFC 2141 [1]). It identifies a		URN syntax requirements (see RFC 2141 [1]). It identifies a
	skipping to change at page 7, line 10		skipping to change at page 7, line 10
	'Partners around the Globe' summarizes all partners that are listed		'Partners around the Globe' summarizes all partners that are listed
	on the NATO webpage: Euro-Atlantic Partnership Council (EAPC), NATO's		on the NATO webpage: Euro-Atlantic Partnership Council (EAPC), NATO's
	Mediterranean Dialogue (MD), Istanbul Cooperation Initiative (ICI)		Mediterranean Dialogue (MD), Istanbul Cooperation Initiative (ICI)
	and Partners across the globe" [8].		and Partners across the globe" [8].
	5. Security Considerations		5. Security Considerations
	Since the URNs in this namespace are opaque, there are no additional		Since the URNs in this namespace are opaque, there are no additional
	security considerations other than those normally associated with the		security considerations other than those normally associated with the
	use and resolution of URIs and URNs in general (see the Security		use and resolution of URIs and URNs in general (see the Security
	Considerations in Internet STD 66 [RFC3986], RFC 2141 [RFC2141], and		Considerations in Internet STD 66 [4], RFC 2141 [1], and BCP 66 [2]).
	BCP 66 [RFC3406]).
	It is noted, however, that resolution algorithms and rules for		It is noted, however, that resolution algorithms and rules for
	handling invalid URNs are opaque. Therefore, attempting to resolve a		handling invalid URNs are opaque. Therefore, attempting to resolve a
	NATO URN through a resolver other than one operated or delegated by		NATO URN through a resolver other than one operated or delegated by
	NATO may return outdated, incorrect, or confusing results.		NATO may return outdated, incorrect, or confusing results.
	Distribution of NATO information in any form is subject to its		Distribution of NATO information in any form is subject to its
	security policies. Nonetheless, this specification is for public use		security policies. Nonetheless, this specification is for public use
	and not subject to any NATO security policies.		and not subject to any NATO security policies.
End of changes. 6 change blocks.
	9 lines changed or deleted		9 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/