1010ccsdssanayb.docx

1、1010ccsdssanaybSPACE Assigned Numbers AuThority (SANA) POLICIES and PROCEDURES DRAFT CCSDS RecordCCSDS 000.0-Y-0Draft Yellow BookOCTOBER 2008FOREWORDForeword text specific to this document goes here. The text below is boilerplate.Through the process of normal evolution, it is expected that expansion

2、, deletion, or modification of this document may occur. This document is therefore subject to CCSDS document management and change control procedures, which are defined in the Procedures Manual for the Consultative Committee for Space Data Systems. Current versions of CCSDS documents are maintained

3、at the CCSDS Web site:http:/www.ccsds.org/Questions relating to the contents or status of this document should be addressed to the CCSDS Secretariat at the address indicated on page i.At time of publication, the active Member and Observer Agencies of the CCSDS were:Member Agencies Agenzia Spaziale I

4、taliana (ASI)/Italy. British National Space Centre (BNSC)/United Kingdom. Canadian Space Agency (CSA)/Canada. Centre National dEtudes Spatiales (CNES)/France. Deutsches Zentrum fr Luft- und Raumfahrt e.V. (DLR)/Germany. European Space Agency (ESA)/Europe. Federal Space Agency (FSA)/Russian Federatio

5、n. Instituto Nacional de Pesquisas Espaciais (INPE)/Brazil. Japan Aerospace Exploration Agency (JAXA)/Japan. National Aeronautics and Space Administration (NASA)/USA.Observer Agencies Austrian Space Agency (ASA)/Austria. Belgian Federal Science Policy Office (BFSPO)/Belgium. Central Research Institu

6、te of Machine Building (TsNIIMash)/Russian Federation. Centro Tecnico Aeroespacial (CTA)/Brazil. Chinese Academy of Sciences (CAS)/China. Chinese Academy of Space Technology (CAST)/China. Commonwealth Scientific and Industrial Research Organization (CSIRO)/Australia. Danish National Space Center (DN

7、SC)/Denmark. European Organization for the Exploitation of Meteorological Satellites (EUMETSAT)/Europe. European Telecommunications Satellite Organization (EUTELSAT)/Europe. Hellenic National Space Committee (HNSC)/Greece. Indian Space Research Organization (ISRO)/India. Institute of Space Research

8、(IKI)/Russian Federation. KFKI Research Institute for Particle & Nuclear Physics (KFKI)/Hungary. Korea Aerospace Research Institute (KARI)/Korea. MIKOMTEK: CSIR (CSIR)/Republic of South Africa. Ministry of Communications (MOC)/Israel. National Institute of Information and Communications Technology (

9、NICT)/Japan. National Oceanic and Atmospheric Administration (NOAA)/USA. National Space Organization (NSPO)/Taiwan. Naval Center for Space Technology (NCST)/USA. Space and Upper Atmosphere Research Commission (SUPARCO)/Pakistan. Swedish Space Corporation (SSC)/Sweden. United States Geological Survey

10、 (USGS)/USA.DOCUMENT CONTROLDocumentTitle and IssueDateStatusCCSDS 000.0-Y-0Document Title, Draft CCSDS Record, Issue 0October 2008Current draftCONTENTSSection Page1Introduction1.1PurposeThe purpose of this document is to define the Space Assigned Numbers Authority(SANA), its role and responsibiliti

11、es within the CCSDS.1.2SCOPEThis document is limited to SANA realm of responsibilities. The assignment of the SANA operator and the liaison roles to other standard organizations or space-related organizations are the responsabilities of the CESG. 1.3APPLICABILITYThis document is applicable to the CC

12、SDS process of defining specifications of protocols. It defines an entity and a process that would constitute a registry of objects that will be used by protocol designers and implementers. However, this document and the SANA entity is of administrative nature and does not contain any protocol speci

13、fication.1.4RATIONALEAs many protocol engineering standard organisation such as the Internet Engineering Task Force (IETF), the Institute of Electrical and Electronics Engineers (IEEE) or the Third-Generation Project (3GPP), there is a need to separate constants and immuable objects from the protoco

14、l specification. These permanents objects are put into registries and managed by the operator of the registries on behalf of the engineering community. Separating the objects from the protocol specification enables the updating of the objects without modifying the protocol specification, which is mu

15、ch longer and tedious process than modifying the corresponding registry. It is important to note that SANA is running as a service to the engineering community. 1.5DOCUMENT STRUCTUREAfter providing an overview, the document describe the scope and the role of the to-be-created SANA. Then the requirem

16、ents for running SANA are listed. The registration rules are defined which governs how SANA will accomplish its duties. The document then describes the relationship between SANA and the other stakeholders within CCSDS, such as CESG, CMC and working groups. The work on registries is then described as

17、 well as the required SANA infrastructure to do its services.An appeal process is described in case of issues regarding the work of SANA. Finally, a process is described for the few pre-SANA registries that existed before the creation of SANA.1.6CONVENTIONS AND DEFINITIONS1.7REFERENCESThe following

18、documents contain provisions which, through reference in this text, constitute provisions of this Manual. At the time of publication, the editions indicated were valid. All documents are subject to revision, and users of this Manual are encouraged to investigate the possibility of applying the most

19、recent editions of the documents indicated below. The CCSDS Secretariat maintains a register of currently valid CCSDS Publications. 1 Restructured Organization and Processes for the Consultative Committee for Space Data Systems. CCSDS A02.1-Y-2. Yellow Book. Issue 2. April 2004 2OVERVIEWThe “Restruc

20、tured Organization and Processes for the Consultative Committee for Space Data Systems” Yellow Book published in April 2004 defines SANA as the following.Space Assigned Numbers Authority (SANA) The core registrar for the CMCs activities is the SANA. Many space mission protocols require that someone

21、keep track of key protocol numbering assignments that were added after the protocol came out. Typical examples of the kinds of registries needed are for Spacecraft IDs, protocol version numbers, reserved APIDs and SFDU Control Authorities. The SANA provides this key configuration management service

22、for CCSDS. The CCSDS Management Council (CMC) approves the organization that will act as the SANA. Its public interface is focused through web-based services or whatever manner required by CCSDS.3SANA PROCESS And role3.1SCOPESANA assigns and registers CCSDS protocol parameters and other CCSDS object

23、s as directed by the criteria and procedures specified in CCSDS documents. SANA only manages the protocol registries of the CCSDS who owns the corresponding protocol space. Whenever a protocol space is not owned by CCSDS but its registry is of use to the CCSDS community, SANA may reference to that e

24、xternal registry. For example, if CCSDS is using IP port numbers, SANA may reference the IANA port numbers registry within the SANA site, for the service to the CCSDS community. However, SANA will not make any assignments of that protocol space since it is not owned by CCSDS. Any liaison role to oth

25、er standard bodies is defined and managed by CMC.3.2ROLESANA is a service to the CCSDS engineering community. The engineering is done within CCSDS. SANA does not do engineering by itself. However, to best serve the community, SANA staff have to have some engineering background at the very minimum. F

26、rom time to time, the work and services that SANA provides will evolve as the engineering needs also change. 3.3CREATION and TermiNATIONSANA existence and role is defined in this document and approved by the CMC. SANA is created by and reports administratively to CMC and technically to CESG. CMC may

27、 terminate SANA at any time, but should determine in which way the registries remain after termination.3.4REQUIREMENTSSANA role and function must adhere to the following requirements: Accountability: requests are tracked and managed. Traceability: all requests and changes could be viewed or audited

28、by the community. Security: registries should be verifiable for their content in a secure manner based on best practices. Registry files will be copied and used by the CCSDS community, the space agencies and industry. Some registries might also be embedded into products. Therefore, a digital signatu

29、re is required to provide a way of verifying the consistency of the registry by the community at any time. The digital signature provides both the integrity validation and the source validation.3.5Registration RulesSANA is the first-level authority for CCSDS registries and core registrar. New regist

30、ries are managed by SANA. SANA is the registration clerk, since it does not define the registration rules. Instead, it applies the rules to the registries for the new registration requests or for the new registries. Registration rules for registries are defined in CCSDS protocol documents approved b

31、y the CESG. The following are the initial set of registration rules for assignments in a registry:a) requires a CCSDS approved documentb) requires an engineering review by a designated expert. The expert for that registry is assigned by the CESGc) requires no engineering review, but the request must

32、 come from the official representative of a space agency, member of the CCSDS. d) requires no review, assignments are done in a first come, first serve basisIn the CCSDS document that defines the creation of a registry, the registration rule for that registry must be defined either within the above set or another rule. This provides guidance to SANA on how to make assignments of new parameters for that reg