idnits 2.17.1 draft-blanchet-ccsds-urn-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 15, 2015) is 3114 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Looks like a reference, but probably isn't: '1' on line 318 -- Looks like a reference, but probably isn't: '2' on line 320 -- Looks like a reference, but probably isn't: '3' on line 322 -- Looks like a reference, but probably isn't: '4' on line 324 ** Obsolete normative reference: RFC 2141 (Obsoleted by RFC 8141) ** Obsolete normative reference: RFC 3406 (Obsoleted by RFC 8141) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Blanchet 3 Internet-Draft A. Schiltknecht 4 Intended status: Informational Viagenie/SANA 5 Expires: April 17, 2016 P. Shames 6 Jet Propulsion Laboratory, NASA 7 October 15, 2015 9 A Uniform Resource Name (URN) Namespace for the Consultative Committee 10 for Space Data Systems (CCSDS) 11 draft-blanchet-ccsds-urn-01.txt 13 Abstract 15 This document describes a Uniform Resource Name (URN) namespace 16 intended for persistently and uniquely naming resources published by 17 the Consultative Committee for Space Data Systems (CCSDS). 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on April 17, 2016. 36 Copyright Notice 38 Copyright (c) 2015 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 2. Requirements Language Section . . . . . . . . . . . . . . . . 3 55 3. URN Specification for ccsds Namespace ID . . . . . . . . . . 3 56 3.1. Namespace ID . . . . . . . . . . . . . . . . . . . . . . 3 57 3.2. Registration Information . . . . . . . . . . . . . . . . 3 58 3.3. Declared registrant of the namespace . . . . . . . . . . 3 59 3.4. Declaration of Syntactic Structure . . . . . . . . . . . 4 60 3.5. Relevant Ancillary Documentation . . . . . . . . . . . . 4 61 3.6. Identifier Uniqueness Considerations . . . . . . . . . . 4 62 3.7. Identifier persistence considerations . . . . . . . . . . 4 63 3.8. Process of Identifier Assignment . . . . . . . . . . . . 5 64 3.9. Process for Identifier Resolution . . . . . . . . . . . . 5 65 3.10. Rules for Lexical Equivalence . . . . . . . . . . . . . . 5 66 3.11. Conformance with URN Syntax . . . . . . . . . . . . . . . 5 67 3.12. Validation mechanism . . . . . . . . . . . . . . . . . . 5 68 3.13. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 5 69 4. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 6 70 5. Namespace Considerations . . . . . . . . . . . . . . . . . . 6 71 6. Community Considerations . . . . . . . . . . . . . . . . . . 6 72 7. Security Considerations . . . . . . . . . . . . . . . . . . . 6 73 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 74 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 75 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 76 10.1. Normative References . . . . . . . . . . . . . . . . . . 7 77 10.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 7 78 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 80 1. Introduction 82 The Consultative Committee for Space Data Systems (CCSDS) [1] was 83 formed in 1982 by the major space agencies of the world to provide a 84 forum for discussion of common problems in the development and 85 operation of space data systems. At the time of publication of this 86 document, it is composed of eleven member agencies, twenty-eight 87 observer agencies, and over 100 industrial associates. Since its 88 establishment, CCSDS has been actively developing Recommendations for 89 data- and information-systems standards, intended to promote 90 interoperability and cross support among cooperating space agencies. 92 CCSDS has a permanent secretariat reporting to the CCSDS Engineering 93 Steering Group, which maintains documents for the CCSDS protocols. 94 CCSDS also has its Naming Authority under the Space Assigned Number 95 Authority (SANA) [2] that manages its registries and namespaces. 97 CCSDS produces protocol standards documents requiring a permanent and 98 unique namespace. CCSDS also uses Extensible Markup Language (XML) 99 schemas to define XML messaging in its various protocols 100 recommendations. These schemas require a persistent, unique and 101 location-independent namespace for identification purposes. 103 This namespace specification is for a formal namespace identifier 104 (NID), as per [RFC3406]. 106 2. Requirements Language Section 108 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 109 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 110 document are to be interpreted as described in [RFC2119]. 112 3. URN Specification for ccsds Namespace ID 114 3.1. Namespace ID 116 "ccsds" 118 3.2. Registration Information 120 Registration version number: 1 122 Registration date: YYYY-MM-DD [RFCeditor: substitute to document 123 date] 125 3.3. Declared registrant of the namespace 127 Registering organization: 129 Consultative Committee for Space Data Systems (CCSDS) Secretariat 131 Office of Space Communication (Code M-3) 133 National Aeronautics and Space Administration 135 Washington, DC 20546, USA 137 E-Mail: secretariat@mailman.ccsds.org 139 Designated Contact: 141 Space Assigned Numbers Authority (SANA) 143 mailto:info@sanaregistry.org 144 http://sanaregistry.org 146 3.4. Declaration of Syntactic Structure 148 The formal syntax definitions below are given in ABNF [RFC5234]. 150 The namespace-specific string (NSS) in the urn:ccsds names hierarchy 151 begins with a subnamespace identifier (SNID), followed by a delimiter 152 and a subnamespace-dependent string 154 CCCSDS-URN = "urn:ccsds:" SNID ":" SUBNAMESPACE-SPECIFIC-STRING 156 where is a unique subnamespace identifier for the 157 specification, and is a unique 158 identifier within the subnamespace identifier scope. 160 has the same syntax as a as defined in [RFC2141]. 162 The Space Assigned Numbers Authority (SANA) assigns SNIDs. 164 The syntax of is dependent on the 165 and MUST be defined by a CCSDS Document. This document does 166 not pose any additional restrictions to the other than what is defined in the NSS syntax as defined by 168 [RFC2141]: 170 SUBNAMESPACE-SPECIFIC-STRING = 1* 172 is defined in Section 2.2 of [RFC2141]. 174 3.5. Relevant Ancillary Documentation 176 SANA keeps the "urn:ccsds" namespace as a registry [3]. Procedures 177 to register a subnamespace identifier are described in the header of 178 the registry. 180 3.6. Identifier Uniqueness Considerations 182 SANA is the authority responsible for uniqueness of identifiers by 183 the recommendations of CCSDS. SANA will assign unique identifiers 184 and keep a public registry [4]. 186 3.7. Identifier persistence considerations 188 CCSDS is committed to guarantee the accessibility and persistence of 189 all the resources that are assigned URNs. 191 3.8. Process of Identifier Assignment 193 Assignment of identifiers is limited to CCSDS and those authorities 194 explicitly designated by CCSDS. CCSDS is committed to assign URN 195 identifiers only in accord to the rules specified in this document or 196 in future updates to this document, either published as IETF RFC 197 documents or as CCSDS recommendations. 199 3.9. Process for Identifier Resolution 201 The CCSDS namespace is not currently listed with a Resolution 202 Discovery System (RDS), but nothing about the namespace prohibits the 203 future definition of appropriate resolution methods or listing with 204 an RDS. 206 3.10. Rules for Lexical Equivalence 208 The part of URNs in the CCSDS hierarchy is case insensitive. 209 Thus, the MUST be case normalized before comparison. 211 3.11. Conformance with URN Syntax 213 The intention of this document is to only restrict the syntax of the 214 . The syntax of the follows the 215 general syntax of a URN: 217 SUBNAMESPACE-SPECIFIC-STRING = 1* 219 Documents defining a subnamespace identifier SHOULD specify further 220 syntactic restrictions in . It is 221 RECOMMENDED that these documents forbid the assignment of URNs 222 containing characters in the set ("%", "/", "?", and "#") 223 as defined in [RFC2141]. This is in accordance with Section 2.2 of 224 [RFC3986]. 226 3.12. Validation mechanism 228 The validation mechanism of URNs in the hierarchy is specific for 229 each SNID and SHOULD be defined when an SNID is assigned. 231 URNs in the hierarchy without an assigned SNID are considered to be 232 invalid. 234 3.13. Scope 236 Global URNs are relevant for the space agencies networks both in 237 space and on Earth. 239 4. Examples 241 URNs in this section are not guaranteed to be real, and are listed 242 here only for illustration purposes. The following are examples of 243 valid URNs for the "document" and "schema" categories: 245 urn:ccsds:document:313x0y1 247 urn:ccsds:schema:ndm:aem 249 5. Namespace Considerations 251 CCSDS is an international standards development organization in the 252 field of space and Earth communications. The use of this URN 253 hierarchy is expected to be broad, including but not limited to usage 254 for: 256 CCSDS documents 258 XML Schemas 260 CCSDS registries 262 The CCSDS documents and registries are available openly. 264 6. Community Considerations 266 Usage of the URN namespace has been requested within the CCSDS 267 community for various projects. 269 The CCCSDS Management Council approved this document in its DATE 270 meeting. 272 7. Security Considerations 274 No additional security considerations are relevant, other than those 275 normally related with the general use and resolution of URNs. 277 8. IANA Considerations 279 IANA is requested to register the "ccsds" NID within the IANA 280 registry of URN NIDs in the "Formal URN Namespaces" sub-registry. 282 9. Acknowledgements 284 This document is based on previous versions authored by Martin A. 285 Soto and Louis Reich. This document was reviewed by the XML Steering 286 Group(XSG) of the Systems Engineering and Architecture Area(SEA) in 287 CCSDS. 289 10. References 291 10.1. Normative References 293 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 294 Requirement Levels", BCP 14, RFC 2119, 295 DOI 10.17487/RFC2119, March 1997, 296 . 298 [RFC2141] Moats, R., "URN Syntax", RFC 2141, DOI 10.17487/RFC2141, 299 May 1997, . 301 [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, 302 "Uniform Resource Names (URN) Namespace Definition 303 Mechanisms", BCP 66, RFC 3406, DOI 10.17487/RFC3406, 304 October 2002, . 306 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 307 Resource Identifier (URI): Generic Syntax", STD 66, 308 RFC 3986, DOI 10.17487/RFC3986, January 2005, 309 . 311 [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax 312 Specifications: ABNF", STD 68, RFC 5234, 313 DOI 10.17487/RFC5234, January 2008, 314 . 316 10.2. URIs 318 [1] http://www.ccsds.org 320 [2] http://sanaregistry.org 322 [3] http://sanaregistry.org/r/urn 324 [4] http://sanaregistry.org/r/urn 326 Authors' Addresses 327 Marc Blanchet 328 Viagenie/SANA 329 246 Aberdeen 330 Quebec, QC G1R 2E1 331 Canada 333 Email: Marc.Blanchet@viagenie.ca 334 URI: http://viagenie.ca 336 Audric Schiltknecht 337 Viagenie/SANA 338 246 Aberdeen 339 Quebec, QC G1R 2E1 340 Canada 342 Email: audric.schiltknecht@viagenie.ca 343 URI: http://viagenie.ca 345 Peter Shames 346 Jet Propulsion Laboratory, NASA 348 Email: peter.m.shames@jpl.nasa.gov 349 URI: http://cwe.ccsds.org/sea/default.aspx