7738
INFORMATIONAL
A Uniform Resource Name (URN) Namespace for the Consultative Committee for Space Data Systems (CCSDS)
Authors: M. Blanchet, A. Schiltknecht, P. Shames
Date: January 2016
Working Group: NON WORKING GROUP
Stream: IETF
Abstract
This document describes a Uniform Resource Name (URN) namespace intended for persistently and uniquely naming resources published by the Consultative Committee for Space Data Systems (CCSDS).
RFC 7738
INFORMATIONAL
Internet Engineering Task Force (IETF) M. Blanchet
Request for Comments: 7738 A. Schiltknecht
Category: Informational Viagenie/SANA
ISSN: 2070-1721 P. Shames
Jet Propulsion Laboratory, NASA
January 2016
<span class="h1">A Uniform Resource Name (URN) Namespace for</span>
<span class="h1">the Consultative Committee for Space Data Systems (CCSDS)</span>
Abstract
This document describes a Uniform Resource Name (URN) namespace
intended for persistently and uniquely naming resources published by
the Consultative Committee for Space Data Systems (CCSDS).
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="https://www.rfc-editor.org/info/rfc7738">http://www.rfc-editor.org/info/rfc7738</a>.
Copyright Notice
Copyright (c) 2016 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">Blanchet, et al. Informational [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc7738">RFC 7738</a> URN Namespace for CCSDS January 2016</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2">2</a>. Requirements Language Section . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3">3</a>. URN Specification for "ccsds" Namespace ID . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3.1">3.1</a>. Namespace ID . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3.2">3.2</a>. Registration Information . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3.3">3.3</a>. Declared Registrant of the Namespace . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3.4">3.4</a>. Declaration of Syntactic Structure . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3.5">3.5</a>. Relevant Ancillary Documentation . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3.6">3.6</a>. Identifier Uniqueness Considerations . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3.7">3.7</a>. Identifier Persistence Considerations . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3.8">3.8</a>. Process of Identifier Assignment . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3.9">3.9</a>. Process for Identifier Resolution . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3.10">3.10</a>. Rules for Lexical Equivalence . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3.11">3.11</a>. Conformance with URN Syntax . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3.12">3.12</a>. Validation Mechanism . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3.13">3.13</a>. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-4">4</a>. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-5">5</a>. Namespace Considerations . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-6">6</a>. Community Considerations . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-7">7</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-8">8</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-9">9</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-9.1">9.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-9.2">9.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The Consultative Committee for Space Data Systems (CCSDS) [<a href="#ref-CCSDS" title=""The Consultative Committee for Space Data Systems"">CCSDS</a>] was
formed in 1982 by the major space agencies of the world to provide a
forum for discussion of common problems in the development and
operation of space data systems. At the time of publication of this
document, it is composed of eleven member agencies, twenty-eight
observer agencies, and over 100 industrial associates. Since its
establishment, CCSDS has been actively developing recommendations for
data- and information-systems standards, intended to promote
interoperability and cross support among cooperating space agencies.
CCSDS has a permanent secretariat reporting to the CCSDS Engineering
Steering Group, which maintains documents for the CCSDS protocols.
CCSDS also has its Naming Authority under the Space Assigned Number
Authority (SANA) [<a href="#ref-SANA" title=""Space Assigned Numbers Authority"">SANA</a>] that manages its registries and namespaces.
<span class="grey">Blanchet, et al. Informational [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc7738">RFC 7738</a> URN Namespace for CCSDS January 2016</span>
CCSDS produces protocol standards documents requiring a permanent and
unique namespace. CCSDS also uses Extensible Markup Language (XML)
schemas to define XML messaging in its various protocols
recommendations. These schemas require a persistent, unique, and
location-independent namespace for identification purposes.
This namespace specification is for a formal namespace identifier
(NID), as per [<a href="./rfc3406" title=""Uniform Resource Names (URN) Namespace Definition Mechanisms"">RFC3406</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Requirements Language Section</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. URN Specification for "ccsds" Namespace ID</span>
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Namespace ID</span>
"ccsds"
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Registration Information</span>
Registration version number: 1
Registration date: 2015-10-19
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Declared Registrant of the Namespace</span>
Registering organization:
Consultative Committee for Space Data Systems (CCSDS) Secretariat
Office of Space Communication (Code M-3)
National Aeronautics and Space Administration
Washington, DC 20546, USA
Email: [email protected]
Designated Contact:
Space Assigned Numbers Authority (SANA)
Email: [email protected]
<a href="http://sanaregistry.org">http://sanaregistry.org</a>
<span class="grey">Blanchet, et al. Informational [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc7738">RFC 7738</a> URN Namespace for CCSDS January 2016</span>
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Declaration of Syntactic Structure</span>
The formal syntax definitions below are given in ABNF [<a href="./rfc5234" title=""Augmented BNF for Syntax Specifications: ABNF"">RFC5234</a>].
The namespace-specific string (NSS) in the urn:ccsds names hierarchy
begins with a subnamespace identifier (SNID), followed by a delimiter
and a subnamespace-dependent string
CCCSDS-URN = "urn:ccsds:" SNID ":" SUBNAMESPACE-SPECIFIC-STRING
where <SNID> is a unique subnamespace identifier for the
specification, and <SUBNAMESPACE-SPECIFIC-STRING> is a unique
identifier within the subnamespace identifier scope.
<SNID> has the same syntax as an <NID> as defined in [<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>].
SANA assigns SNIDs.
The syntax of <SUBNAMESPACE-SPECIFIC-STRING> is dependent on the
<SNID> and MUST be defined by a CCSDS document. This document does
not pose any additional restrictions to the <SUBNAMESPACE-SPECIFIC-
STRING> other than what is defined in the NSS syntax as defined by
[<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>]:
SUBNAMESPACE-SPECIFIC-STRING = 1*<URN chars>
<URN chars> is defined in <a href="./rfc2141#section-2.2">Section 2.2 of [RFC2141]</a>.
<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. Relevant Ancillary Documentation</span>
SANA keeps the "urn:ccsds" namespace as a registry [<a href="#ref-SANA-Reg" title=""Space Assigned Number Authority (SANA) Registry"">SANA-Reg</a>].
Procedures to register a subnamespace identifier are described in the
header of the registry.
<span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a>. Identifier Uniqueness Considerations</span>
SANA is the authority responsible for uniqueness of identifiers by
the recommendations of CCSDS. SANA will assign unique identifiers
and keep a public registry [<a href="#ref-SANA-Reg" title=""Space Assigned Number Authority (SANA) Registry"">SANA-Reg</a>].
<span class="h3"><a class="selflink" id="section-3.7" href="#section-3.7">3.7</a>. Identifier Persistence Considerations</span>
CCSDS is committed to guaranteeing the accessibility and persistence
of all the resources that are assigned URNs.
<span class="grey">Blanchet, et al. Informational [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc7738">RFC 7738</a> URN Namespace for CCSDS January 2016</span>
<span class="h3"><a class="selflink" id="section-3.8" href="#section-3.8">3.8</a>. Process of Identifier Assignment</span>
Assignment of identifiers is limited to CCSDS and those authorities
explicitly designated by CCSDS. CCSDS is committed to assigning URN
identifiers only in accordance with the rules specified in this
document or in future updates to this document, either published as
IETF RFC documents or as CCSDS recommendations.
<span class="h3"><a class="selflink" id="section-3.9" href="#section-3.9">3.9</a>. Process for Identifier Resolution</span>
The CCSDS namespace is not currently listed with a Resolution
Discovery System (RDS), but nothing about the namespace prohibits the
future definition of appropriate resolution methods or listing with
an RDS.
<span class="h3"><a class="selflink" id="section-3.10" href="#section-3.10">3.10</a>. Rules for Lexical Equivalence</span>
The <SNID> part of URNs in the CCSDS hierarchy is case insensitive.
Thus, the <SNID> MUST be case normalized before comparison.
<span class="h3"><a class="selflink" id="section-3.11" href="#section-3.11">3.11</a>. Conformance with URN Syntax</span>
The intention of this document is to only restrict the syntax of the
<SNID>. The syntax of the <SUBNAMESPACE-SPECIFIC-STRING> follows the
general syntax of a URN:
SUBNAMESPACE-SPECIFIC-STRING = 1*<URN chars>
Documents defining a subnamespace identifier SHOULD specify further
syntactic restrictions in <SUBNAMESPACE-SPECIFIC-STRING>. It is
RECOMMENDED that these documents forbid the assignment of URNs
containing characters in the <reserved> set ("%", "/", "?", and "#")
as defined in [<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>]. This is in accordance with <a href="./rfc3986#section-2.2">Section 2.2 of
[RFC3986]</a>.
<span class="h3"><a class="selflink" id="section-3.12" href="#section-3.12">3.12</a>. Validation Mechanism</span>
The validation mechanism of URNs in the hierarchy is specific for
each SNID and SHOULD be defined when an SNID is assigned.
URNs in the hierarchy without an assigned SNID are considered to be
invalid.
<span class="h3"><a class="selflink" id="section-3.13" href="#section-3.13">3.13</a>. Scope</span>
Global URNs are relevant for the space agencies networks both in
space and on Earth.
<span class="grey">Blanchet, et al. Informational [Page 5]</span><span id="page-6" ></span>
<span class="grey"><a href="./rfc7738">RFC 7738</a> URN Namespace for CCSDS January 2016</span>
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Examples</span>
URNs in this section are not guaranteed to be real and are listed
here only for illustration purposes. The following are examples of
valid URNs for the "document" and "schema" categories:
urn:ccsds:document:313x0y1
urn:ccsds:schema:ndm:aem
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Namespace Considerations</span>
CCSDS is an international standards development organization in the
field of space and Earth communications. The use of this URN
hierarchy is expected to be broad, including but not limited to usage
for:
CCSDS documents
XML Schemas
CCSDS registries
The CCSDS documents and registries are available openly.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Community Considerations</span>
Usage of the URN namespace has been requested within the CCSDS
community for various projects.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
No additional security considerations are relevant, other than those
normally related with the general use and resolution of URNs.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. IANA Considerations</span>
IANA has registered the "ccsds" NID within the IANA registry of URN
NIDs in the "Formal URN Namespaces" subregistry.
<span class="grey">Blanchet, et al. Informational [Page 6]</span><span id="page-7" ></span>
<span class="grey"><a href="./rfc7738">RFC 7738</a> URN Namespace for CCSDS January 2016</span>
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. References</span>
<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>,
DOI 10.17487/RFC2119, March 1997,
<<a href="https://www.rfc-editor.org/info/rfc2119">http://www.rfc-editor.org/info/rfc2119</a>>.
[<a id="ref-RFC2141">RFC2141</a>] Moats, R., "URN Syntax", <a href="./rfc2141">RFC 2141</a>, DOI 10.17487/RFC2141,
May 1997, <<a href="https://www.rfc-editor.org/info/rfc2141">http://www.rfc-editor.org/info/rfc2141</a>>.
[<a id="ref-RFC3406">RFC3406</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>, DOI 10.17487/RFC3406,
October 2002, <<a href="https://www.rfc-editor.org/info/rfc3406">http://www.rfc-editor.org/info/rfc3406</a>>.
[<a id="ref-RFC3986">RFC3986</a>] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66,
<a href="./rfc3986">RFC 3986</a>, DOI 10.17487/RFC3986, January 2005,
<<a href="https://www.rfc-editor.org/info/rfc3986">http://www.rfc-editor.org/info/rfc3986</a>>.
[<a id="ref-RFC5234">RFC5234</a>] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, <a href="./rfc5234">RFC 5234</a>,
DOI 10.17487/RFC5234, January 2008,
<<a href="https://www.rfc-editor.org/info/rfc5234">http://www.rfc-editor.org/info/rfc5234</a>>.
<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Informative References</span>
[<a id="ref-CCSDS">CCSDS</a>] CCSDS, "The Consultative Committee for Space Data
Systems", <<a href="http://www.ccsds.org/">http://www.ccsds.org/</a>>.
[<a id="ref-SANA">SANA</a>] SANA, "Space Assigned Numbers Authority",
<<a href="http://sanaregistry.org/">http://sanaregistry.org/</a>>.
[<a id="ref-SANA-Reg">SANA-Reg</a>] SANA, "Space Assigned Number Authority (SANA) Registry",
<<a href="http://sanaregistry.org/r/urn">http://sanaregistry.org/r/urn</a>>.
<span class="grey">Blanchet, et al. Informational [Page 7]</span><span id="page-8" ></span>
<span class="grey"><a href="./rfc7738">RFC 7738</a> URN Namespace for CCSDS January 2016</span>
Acknowledgements
This document is based on previous draft versions authored by Martin
A. Soto and Louis Reich. This document was reviewed by the XML
Steering Group (XSG) of the Systems Engineering and Architecture Area
(SEA) in CCSDS.
Authors' Addresses
Marc Blanchet
Viagenie/SANA
246 Aberdeen
Quebec, QC G1R 2E1
Canada
Email: [email protected]
URI: <a href="http://viagenie.ca">http://viagenie.ca</a>
Audric Schiltknecht
Viagenie/SANA
246 Aberdeen
Quebec, QC G1R 2E1
Canada
Email: [email protected]
URI: <a href="http://viagenie.ca">http://viagenie.ca</a>
Peter Shames
Jet Propulsion Laboratory, NASA
Email: [email protected]
URI: <a href="http://cwe.ccsds.org/sea/default.aspx">http://cwe.ccsds.org/sea/default.aspx</a>
Blanchet, et al. Informational [Page 8]
Annotations
Select text to annotate