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
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
A Uniform Resource Name (URN) Namespace for the Consultative Committee for Space Data Systems (CCSDS)
空间数据系统协商委员会（CCSDS）的统一资源名称（URN）命名空间
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).
本文件描述了空间数据系统协商委员会（CCSDS）发布的一个统一资源名称（URN）命名空间，旨在对资源进行持久和唯一的命名。
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.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非IESG批准的所有文件都适用于任何级别的互联网标准；见RFC 5741第2节。
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/rfc7738.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7738.
Copyright Notice
版权公告
Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2016 IETF信托基金和确定为文件作者的人员。版权所有。
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.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Language Section . . . . . . . . . . . . . . . . 3
3. URN Specification for "ccsds" Namespace ID . . . . . . . . . 3
3.1. Namespace ID . . . . . . . . . . . . . . . . . . . . . . 3
3.2. Registration Information . . . . . . . . . . . . . . . . 3
3.3. Declared Registrant of the Namespace . . . . . . . . . . 3
3.4. Declaration of Syntactic Structure . . . . . . . . . . . 4
3.5. Relevant Ancillary Documentation . . . . . . . . . . . . 4
3.6. Identifier Uniqueness Considerations . . . . . . . . . . 4
3.7. Identifier Persistence Considerations . . . . . . . . . . 4
3.8. Process of Identifier Assignment . . . . . . . . . . . . 5
3.9. Process for Identifier Resolution . . . . . . . . . . . . 5
3.10. Rules for Lexical Equivalence . . . . . . . . . . . . . . 5
3.11. Conformance with URN Syntax . . . . . . . . . . . . . . . 5
3.12. Validation Mechanism . . . . . . . . . . . . . . . . . . 5
3.13. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 6
5. Namespace Considerations . . . . . . . . . . . . . . . . . . 6
6. Community Considerations . . . . . . . . . . . . . . . . . . 6
7. Security Considerations . . . . . . . . . . . . . . . . . . . 6
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
9.1. Normative References . . . . . . . . . . . . . . . . . . 7
9.2. Informative References . . . . . . . . . . . . . . . . . 7
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Language Section . . . . . . . . . . . . . . . . 3
3. URN Specification for "ccsds" Namespace ID . . . . . . . . . 3
3.1. Namespace ID . . . . . . . . . . . . . . . . . . . . . . 3
3.2. Registration Information . . . . . . . . . . . . . . . . 3
3.3. Declared Registrant of the Namespace . . . . . . . . . . 3
3.4. Declaration of Syntactic Structure . . . . . . . . . . . 4
3.5. Relevant Ancillary Documentation . . . . . . . . . . . . 4
3.6. Identifier Uniqueness Considerations . . . . . . . . . . 4
3.7. Identifier Persistence Considerations . . . . . . . . . . 4
3.8. Process of Identifier Assignment . . . . . . . . . . . . 5
3.9. Process for Identifier Resolution . . . . . . . . . . . . 5
3.10. Rules for Lexical Equivalence . . . . . . . . . . . . . . 5
3.11. Conformance with URN Syntax . . . . . . . . . . . . . . . 5
3.12. Validation Mechanism . . . . . . . . . . . . . . . . . . 5
3.13. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 6
5. Namespace Considerations . . . . . . . . . . . . . . . . . . 6
6. Community Considerations . . . . . . . . . . . . . . . . . . 6
7. Security Considerations . . . . . . . . . . . . . . . . . . . 6
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
9.1. Normative References . . . . . . . . . . . . . . . . . . 7
9.2. Informative References . . . . . . . . . . . . . . . . . 7
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
The Consultative Committee for Space Data Systems (CCSDS) [CCSDS] 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）[CCSDS]由世界主要空间机构于1982年成立，为讨论空间数据系统开发和运行中的常见问题提供了一个论坛。在本文件出版时，它由11个成员机构、28个观察员机构和100多个行业协会组成。自成立以来，CCSDS一直在积极制定关于数据和信息系统标准的建议，旨在促进合作空间机构之间的互操作性和交叉支持。
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) [SANA] that manages its registries and namespaces.
CCSDS设有一个向CCSDS工程指导小组报告的常设秘书处，该小组负责保存CCSDS协议的文件。CCSDS还拥有空间分配号码管理局（SANA）[SANA]下的命名权限，该管理局负责管理其注册表和名称空间。
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.
CCSDS生成协议标准文档，需要一个永久且唯一的名称空间。CCSDS还使用可扩展标记语言（XML）模式在其各种协议建议中定义XML消息传递。为了便于识别，这些模式需要一个持久的、唯一的和位置无关的命名空间。
This namespace specification is for a formal namespace identifier (NID), as per [RFC3406].
根据[RFC3406]，此名称空间规范适用于正式名称空间标识符（NID）。
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 [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
"ccsds"
“ccsds”
Registration version number: 1
注册版本号：1
Registration date: 2015-10-19
注册日期：2015-10-19
Registering organization:
注册机构：
Consultative Committee for Space Data Systems (CCSDS) Secretariat
空间数据系统协商委员会（CCSDS）秘书处
Office of Space Communication (Code M-3)
空间通信办公室（代码M-3）
National Aeronautics and Space Administration
美国国家航空航天局
Washington, DC 20546, USA
美国华盛顿特区20546
Email: secretariat@mailman.ccsds.org
Email: secretariat@mailman.ccsds.org
Designated Contact:
指定联系人：
Space Assigned Numbers Authority (SANA)
空间分配号码管理局（SANA）
Email: info@sanaregistry.org
Email: info@sanaregistry.org
http://sanaregistry.org
http://sanaregistry.org
The formal syntax definitions below are given in ABNF [RFC5234].
ABNF[RFC5234]中给出了以下正式语法定义。
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
urn:ccsds names层次结构中的命名空间特定字符串（NSS）以子名称空间标识符（SNID）开头，后跟分隔符和子名称空间相关字符串
CCCSDS-URN = "urn:ccsds:" SNID ":" SUBNAMESPACE-SPECIFIC-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>是规范的唯一子名称空间标识符，<subnamespace-SPECIFIC-STRING>是子名称空间标识符范围内的唯一标识符。
<SNID> has the same syntax as an <NID> as defined in [RFC2141].
<SNID>与[RFC2141]中定义的<NID>具有相同的语法。
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 [RFC2141]:
<SUBNAMESPACE-SPECIFIC-STRING>的语法取决于<SNID>，必须由CCSDS文档定义。除[RFC2141]在NSS语法中定义的内容外，本文档对<SUBNAMESPACE-SPECIFIC-STRING>没有任何其他限制：
SUBNAMESPACE-SPECIFIC-STRING = 1*<URN chars>
SUBNAMESPACE-SPECIFIC-STRING = 1*<URN chars>
<URN chars> is defined in Section 2.2 of [RFC2141].
[RFC2141]第2.2节定义了<URN chars>。
SANA keeps the "urn:ccsds" namespace as a registry [SANA-Reg]. Procedures to register a subnamespace identifier are described in the header of the registry.
SANA将“urn:ccsds”命名空间保留为注册表[SANA Reg]。注册表头中描述了注册子名称空间标识符的过程。
SANA is the authority responsible for uniqueness of identifiers by the recommendations of CCSDS. SANA will assign unique identifiers and keep a public registry [SANA-Reg].
SANA是根据CCSDS的建议负责标识符唯一性的机构。SANA将分配唯一标识符并保留公共注册表[SANA Reg]。
CCSDS is committed to guaranteeing the accessibility and persistence of all the resources that are assigned URNs.
CCSDS致力于保证分配给URN的所有资源的可访问性和持久性。
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.
标识符的分配仅限于CCSDS和CCSDS明确指定的机构。CCSDS承诺仅根据本文件规定的规则或本文件的未来更新（作为IETF RFC文件或CCSDS建议发布）分配URN标识符。
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.
CCSDS名称空间当前未与解决方案发现系统（RDS）一起列出，但名称空间的任何内容都不禁止将来定义适当的解决方案方法或与RDS一起列出。
The <SNID> part of URNs in the CCSDS hierarchy is case insensitive. Thus, the <SNID> MUST be case normalized before comparison.
CCSDS层次结构中URN的<SNID>部分不区分大小写。因此，<SNID>必须在比较之前进行大小写规范化。
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:
本文档的目的只是限制<SNID>的语法。<SUBNAMESPACE-SPECIFIC-STRING>的语法遵循URN的一般语法：
SUBNAMESPACE-SPECIFIC-STRING = 1*<URN chars>
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 [RFC2141]. This is in accordance with Section 2.2 of [RFC3986].
定义子名称空间标识符的文档应在<subnamespace-SPECIFIC-STRING>中指定进一步的语法限制。建议这些文件禁止分配包含[RFC2141]中定义的<reserved>集合（“%”、“/”、“？”和“#”）中字符的URN。这符合[RFC3986]第2.2节的规定。
The validation mechanism of URNs in the hierarchy is specific for each SNID and SHOULD be defined when an SNID is assigned.
层次结构中URN的验证机制对于每个SNID都是特定的，应该在分配SNID时定义。
URNs in the hierarchy without an assigned SNID are considered to be invalid.
层次结构中没有指定SNID的URN被视为无效。
Global URNs are relevant for the space agencies networks both in space and on Earth.
全球URN与空间和地球上的空间机构网络相关。
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示例：
urn:ccsds:document:313x0y1
urn:ccsds:document:313x0y1
urn:ccsds:schema:ndm:aem
urn:ccsds:schema:ndm:aem
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是空间和地球通信领域的一个国际标准制定组织。预计此URN层次结构的使用范围将非常广泛，包括但不限于以下用途：
CCSDS documents
CCSDS文件
XML Schemas
XML纲要
CCSDS registries
CCSDS登记处
The CCSDS documents and registries are available openly.
CCSDS文件和登记册可公开获取。
Usage of the URN namespace has been requested within the CCSDS community for various projects.
在CCSDS社区中，各种项目都要求使用URN命名空间。
No additional security considerations are relevant, other than those normally related with the general use and resolution of URNs.
除了通常与骨灰盒的一般用途和分辨率相关的安全考虑之外，没有其他相关的安全考虑。
IANA has registered the "ccsds" NID within the IANA registry of URN NIDs in the "Formal URN Namespaces" subregistry.
IANA已在“正式URN名称空间”分区的URN NID IANA注册中心注册了“ccsds”NID。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <http://www.rfc-editor.org/info/rfc2119>.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，DOI 10.17487/RFC2119，1997年3月<http://www.rfc-editor.org/info/rfc2119>.
[RFC2141] Moats, R., "URN Syntax", RFC 2141, DOI 10.17487/RFC2141, May 1997, <http://www.rfc-editor.org/info/rfc2141>.
[RFC2141]护城河，R.，“瓮语法”，RFC 2141，DOI 10.17487/RFC2141，1997年5月<http://www.rfc-editor.org/info/rfc2141>.
[RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, "Uniform Resource Names (URN) Namespace Definition Mechanisms", BCP 66, RFC 3406, DOI 10.17487/RFC3406, October 2002, <http://www.rfc-editor.org/info/rfc3406>.
[RFC3406]Daigle，L.，van Gulik，D.，Iannella，R.，和P.Faltstrom，“统一资源名称（URN）命名空间定义机制”，BCP 66，RFC 3406，DOI 10.17487/RFC3406，2002年10月<http://www.rfc-editor.org/info/rfc3406>.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, DOI 10.17487/RFC3986, January 2005, <http://www.rfc-editor.org/info/rfc3986>.
[RFC3986]Berners Lee，T.，Fielding，R.，和L.Masinter，“统一资源标识符（URI）：通用语法”，STD 66，RFC 3986，DOI 10.17487/RFC3986，2005年1月<http://www.rfc-editor.org/info/rfc3986>.
[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, DOI 10.17487/RFC5234, January 2008, <http://www.rfc-editor.org/info/rfc5234>.
[RFC5234]Crocker，D.，Ed.和P.Overell，“语法规范的扩充BNF:ABNF”，STD 68，RFC 5234，DOI 10.17487/RFC5234，2008年1月<http://www.rfc-editor.org/info/rfc5234>.
[CCSDS] CCSDS, "The Consultative Committee for Space Data Systems", <http://www.ccsds.org/>.
[CCSDS]CCSDS，“空间数据系统协商委员会”<http://www.ccsds.org/>.
[SANA] SANA, "Space Assigned Numbers Authority", <http://sanaregistry.org/>.
[SANA]SANA，“空间分配号码管理局”<http://sanaregistry.org/>.
[SANA-Reg] SANA, "Space Assigned Number Authority (SANA) Registry", <http://sanaregistry.org/r/urn>.
[SANA Reg]SANA，“空间分配号码管理局（SANA）注册表”<http://sanaregistry.org/r/urn>.
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.
本文件基于Martin A.Soto和Louis Reich之前的草稿版本。本文档由CCSDS系统工程和体系结构领域（SEA）的XML指导小组（XSG）审查。
Authors' Addresses
作者地址
Marc Blanchet Viagenie/SANA 246 Aberdeen Quebec, QC G1R 2E1 Canada
Marc Blanchet Viagenie/SANA 246魁北克省阿伯丁市，QC G1R 2E1加拿大
Email: Marc.Blanchet@viagenie.ca
URI: http://viagenie.ca
Email: Marc.Blanchet@viagenie.ca
URI: http://viagenie.ca
Audric Schiltknecht Viagenie/SANA 246 Aberdeen Quebec, QC G1R 2E1 Canada
Audric Schiltknecht Viagenie/SANA 246魁北克省阿伯丁市，QC G1R 2E1加拿大
Email: audric.schiltknecht@viagenie.ca
URI: http://viagenie.ca
Email: audric.schiltknecht@viagenie.ca
URI: http://viagenie.ca
Peter Shames Jet Propulsion Laboratory, NASA
美国宇航局喷气推进实验室Peter Shames
Email: peter.m.shames@jpl.nasa.gov
URI: http://cwe.ccsds.org/sea/default.aspx
Email: peter.m.shames@jpl.nasa.gov
URI: http://cwe.ccsds.org/sea/default.aspx