Skip Ribbon Commands
Skip to main content
SharePoint

Charters : 1.04 Space Assigned Numbers Authority Working Group

Manage PermissionsManage Permissions
|
Version HistoryVersion History

Name of Group

Short Name

Area

Chairperson

Chairperson E-Mail Address

Chairperson Agency

Deputy Chairperson

Deputy Chairperson E-Mail Address

Deputy Chairperson Agency

Mailing List

Scope of Activity

Rationale for Activity

Goals

Survey of Similar Standards Efforts Undertaken in Other Bodies and elsewhere in CCSDS

Patent Licensing Applicability for Future Standards

Technical Risk Mitigation Strategy

Management Risk Mitigation Strategy

Description of Change

Disable Alert

Area Director E-Mail Address

Deputy Area Director E-Mail Address

Create Poll

CC Yourself

Completed/Closed

Approval Status

Attachments

Version:
Created at by
Last modified at by

Manage PermissionsManage Permissions
|
Version HistoryVersion History

Name of Group

1.04 Space Assigned Numbers Authority Working Group

Area

Systems Engineering Area (SEA)

Chairperson

Marc Blanchet

Chairperson E-Mail Address

marc.blanchet@viagenie.ca

Chairperson Agency

CSA

Deputy Chairperson

Deputy Chairperson E-Mail Address

Deputy Chairperson Agency

Mailing List

sea-sana@mailman.ccsds.org

Scope of Activity

The purpose of the Space Assigned Numbers Authority (SANA) Working Group is to focus on generating the technical analysis and requirements for SANA.
 
A SANA registry will register information about protocols and standards, as they relate to spaceflight, that need updating or extension more frequently than is practical in a CCSDS standard or report. 

Rationale for Activity

CCSDS A02.1-Y-2.  Restructured Organization and Processes for the Consultative Committee for Space Data Systems. Yellow Book.  Issue 2. April 2004:

1.4.6 Space Assigned Numbers Authority (SANA) The core registrar for the CMC’s activities is the SANA. Many space mission protocols require that someone 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 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 provided by the Secretariat.

There are four prioritized categories of work which need to be either investigated for registry requirements or assessed for possible adjustment. These categories start with the officially sanctioned CCSDS processes/technologies and extend to those process/technologies that are not covered.  Category four will be addressed only as it relates to specific spaceflight related requirements either identified in categories one through three or required by new or impending technologies (generally identified but not assessed in any detail).

Category one (1) is current CCSDS registries, namely SCIDs and SFDU CA.  

Category two (2) is the set of protocol identifiers, assigned numbers, port numbers and reserved APIDs that are currently documented within CCSDS approved documents and SCPS protocol numbers including other current deployments like SLE service providers.  This would include existing elements e.g. glossary, ground data systems and acronym lists. 

Category three (3) is the list of current CCSDS working groups e.g. SM&C, XML schema and namespaces, and birds of a feather that may require registries and also includes current CCSDS developments.

Category four (4) is the catch all for all other activities which may possess a registries requirement, e.g. information models, reference software, but currently do not fall under CCSDS and/or do not currently operate under a registry.

Goals

Provide the mechanisms, processes and documentation required for a CCSDS registry capability.

– Objective 1: Provide detailed requirements for a CCSDS registry.

– Objective 2: Coordinate and integrate current CCSDS registry processes and other operational information into a unified standardized framework.

– Objective 3: Propose a SANA advisory group and develop rules and processes to operate and support the SANA and identify the resources needed for the continuing operation, deployment, outreach, and evolution.

Survey of Similar Standards Efforts Undertaken in
Other Bodies and elsewhere in CCSDS

Patent Licensing Applicability for Future Standards

NA 

Technical Risk Mitigation Strategy

Risks: No significant technical risk is involved.  Technical risks are low since this is essentially process based. 
Mitigation:  None required

Management Risk Mitigation Strategy

Risks:  Some management risk is involved including the usual politics and consensus building necessary for success.

– Issues of privacy, ownership
– Issues of security and access to aggregated information
– International resources for the WG and operations team

Mitigation: Work as required
Version:
Created at by
Last modified at by

Note - To view "Draft" projects, which are not yet approved Click Here.

 Approved Projects

|Export to Spreadsheet|
Currently 2 Projects     
Document Type
Project Status
Project Phase
Modified By
XML Namespace Policy (Yellow Book)YellowAll Tasks CompletedProject CompletedCCSDS Framework 
Space Assigned Numbers Authority (SANA)-Role, Responsibilities, Policies and Procedures (Yellow Book, Issue 2)YellowAll Tasks CompletedProject CompletedCCSDS Tech Support