SEA Area Report. Reston, VA, USA, 26 October 2005. SEA Includes: System Architecture, Information Architecture & Security Working Groups SANA BoF (seeking WG status now) SGIA BoF (initial meeting) XML Standards and Guidelines SIG (initial meeting) Responsibilities
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Reston, VA, USA, 26 October 2005
System Architecture, Information Architecture & Security Working Groups
SANA BoF (seeking WG status now)
SGIA BoF (initial meeting)
XML Standards and Guidelines SIG (initial meeting)
Overall architecture for space mission communications, operations, and cross-support
Coordinate and collaborate with the other areas about architectural choices and options
Support the CESG in evaluating consistency of all area programs of work with the defined architecture
Create such working groups and BoFs as are required to progress the work of CCSDSSystem Engineering AreaOverview
System Architecture WG - Met in Atlanta
Develop a high level system architecture reference model and formal methodology and tools.
Finalize Reference Architecture for Space Data Systems (RASDS) V1 Magenta Book
Discuss how to progress future work on architectural formalisms
Information Architecture WG - Met in Atlanta
Develop a high level Information Architecture reference model and definitions of active and passive information objects
Finalize Reference Architecture for Space Information Management (RASIM) V1 Green Book
Discuss how / where to begin work to define component interfaces and standards
Security WG - Met in Atlanta
Develop security overview & threat assessment, and security architecture, framework and related standards
Progress Security Architecture and other specific security elements (Key management, Crypto and Authentication Standards)
Discussions with other WGs as neededSystem Engineering Area Summary:Current WGs and BOFs
SANA BoF - Met in Atlanta
Develop detailed requirements for the Space Assigned Numbers Authority (SANA), an implementation approach and a plan for a rapid prototype to demonstrate functionality
Finalize SANA charter, submitted to CESG for approval
Demo SANA prototype
New BoF & SIGs
Space Ground Interoperability Architecture (SGIA) BoF - Met in Atlanta
Develop an end to end space / ground cross support architecture and services catalog in response to IOAG request
Initiate SGIA charter discussions, create shared vision for task
XML Standards & Guidelines (XSG) SIG - Met in Atlanta
Develop guidelines and standard approaches for XML schema and namespaces, short fuse due to immediate WG needs
Created agreed task concept, identified chair and members, initiated discussions, first telecon heldSystem Engineering Area Summary:Current WGs and BOFs
Delta-DOR End to End Processing - Discussed w/ CESG in Atlanta
Develop an end to end approach to Delta-DOR processing, including RF signals, data reception, raw data capture & transmission, data processing, delivery of products and ancillary information such as quasar catalogs
Initiate discussions, create shared vision for task and where / how the work should be carried out, co-location problems, first telecon held
Data Management / Data Accountability - brief discussion in Atlanta
Develop an end to end data management and data accountability approach
Initiate discussions, create shared vision for task and where / how the work should be carried outSystem Engineering Area Summary:Current WGs and BOFs
Goal: Develop a reference architecture and a formal representation method
Working Group Status: Active ___ Idle ___ Work is suspended _X_
Working Group Summary Situation:
Working Group Summary progress:
Updated the RASDS document (nearly final RP)
Started to develop a formal model (before WB)
Problems and Issues:
Requested by CMC to cease work on formal models
Development of formal model is deemed essential by SAWGSAWG Summary Technical Status
Working Group is advancing and producing good products.
Docs OK. New work OK.
Goal: Develop a Reference Architecture for Space Information Management as extension to RASDS Information Viewpoint
Working Group Status: Active _X_ Idle ___
Working Group Summary Situation:
Working Group Summary progress:
Updated the RASIM document (nearly complete GB),
Discussed how to transition to development of components & interfaces
Problems and Issues:
Agreement on transition is still unclear
Availability of agency participants with right skill set is uncertainIAWG Summary Technical Status
8 representatives included NASA (JPL, GSFC, MSFC), ESA
Establish plan, processes and recommended practices for CCSDS Space Assigned Numbers Authority (SANA)
Define content, overall approach, and means for updating included information
Define how the SANA would work with different CCSDS WGs, registries, and with agency specific elements
Establish practice for future maintenance and sustaining of the SANA
Primarily provide access to CCSDS global information
Manage central info centrally as authoritative source
Support local management of distributed agency & mission info, provide central pointers to their authoritative sources
Existing SANA is largely conceptual, as defined in CCSDS A02.1-Y-2.Restructured Organization and Processes for the Consultative Committee for Space Data Systems. Yellow Book. Issue 2. April 2004:
“SANA” materials are in some existing repositories and also are buried within a number of different CCSDS documents
Users have a very difficult time locating these within the CCSDS web site and understanding how they relate one to the otherSANA BOF Executive Summary
Update the SANA charter to reflect agreements from meeting and submit to the CESG for approval
Ensure that the SANA can deal with the complexity of future spaceflight programs, projects and the technologies involved
Help reduce stove piping
Setup a mechanism to access and apply specific information technologies through registry processes and artifacts (CCSDS common S/W)
Introduce information management commonality across operational domains Enable interoperability & reuse (data dictionaries & glossary, schemas, assigned numbers, common name registry)
Provide commonality at the technical & operational level among disparate projects and development organizations
Single point of (common) access for management, technologists, developers and operators to technically relevant CCSDS related information (SANA=web link management)SANA BOF Recommendations
11 representatives included NASA (JPL, MSFC), ESA, CSA, and JAXA participation
Attendees: Shames, Okino, Crichton, Weiss, Yamada, Kearney, Peccia, Gannet, Hughes, Reich, Hartmann
JPL and MSFC are actively supporting effort
ESA has indicated that they will provide some level of support (telecon, email coordination level) – support from existing SAWG members
CNES & JAXA are seeking support
General agreement on: Charter of SGIA
Some CHANGE in terms of generalization as to the service provider/user model, specifically do not constrain to SLE
General agreement on: 5 step process
Some CHANGE in terms of language to capture iteration and stakeholder feedback towards
the cross support service catalog
cross support service architecture
Some CHANGE in terms of refinement of the content, including process as well as the level of detail of the cross support service catalog was identified.SGIA BoF Executive Summary
A specific suggestion was that it may be sufficient to provide gateway interfaces
Possible options are to present interoperability at the gateway level or end-to-end service along with identified confederated nodes and profiles.
Desire to ensure that existing organizational boundaries and implementation approaches are accommodated
Leverage IOAG DRAFT catalog and architecture
Schedule - general belief we could get an initial WB by June 06 meeting
There was some concern about the scope and meaning of “profiles”.SGIA BoF Discussion
XSG SIG on 14 September 2005 in Atlanta, GA would entail:
23 representatives included NASA (JPL, GSFC, MSFC), ESA, CNES, OMG SDTF, and other participation
Establish guidelines and recommended practices for CCSDS XML schema, naming, and usage before this first set of schema, from several different working groups, become finalized and externally visible
Define common rules, naming and style guides, define URL hierarchy and namespace architecture, define versioning and use schema location as a resolvable URL
Get CCSDS namespace and rules sorted out before current standards are finalized
Four separate XML schemas are in development, there is no consistency of naming, usage, namespace, etc across them
Enable interoperable implementations of SW and systems
Create collaborative solutions and an authoritative source for CCSDS and agency useXSG SIG Executive Summary
Create a small working group of current XML schema authors and experts to develop short term approach
XML Stds & Guidelines SIG
Erik Barkley (CSS, NASA / JPL)
David Berry (MOIMS, NASA / JPL)
Lou Reich (chair, MOIMS, NASA / GSFC)
Gerry Simon (OMG Space DTF)
Arnaud Lucas(CSS, CNES)
Martin Soto (ESA)
Define a URL hierarchy and namespace architecture
Create a naming and style guide, including guidelines for development of schema and namespace
Define versioning approach
Create a resolvable URL for schemaLocation, ( create a CCSDS server for these, future)
Define levels of XML schema reusable components (potentially based on the UBL model)
Define approach for consistent use of qualified and unqualified types, elements and attributes
Get a CCSDS NID by submitting an RFC to IETF, establish base for URN, list of 23 exist now (RFC 3406, May 2005), see also IANA registry of URI (RFC 3986)XSG SIG Recommendations
SysML Partners have developed a system engineering modeling language based upon UML 2.0. A liaison has been agreed to, which opens up a communication channel between the SEA and SysML groups. The intent is to provide the SysML solution to CCSDS for their validation for application to Space Systems.
SysML agreed to form a liaison w/ CCSDS. SEA, on behalf of CCSDS, has agreed to that liaison and several joint meetings have been held.
The SysML spec is currently at version 0.9. Four UML tool vendors have demonstrated SysML 0.9 compliant versions of their tools. A summary presentation is available from the SysML web site.
An informal liaison has been developed with ISO/IEC JTC 1 / SC7 which is developing an UML for RM-ODP approach. This opens up a useful communication channel between the two groups. The intent is to validate the RASDS to the RM-ODP and to provide feedback to the SC7 WG it its applicability to Space Systems.
The JTC 1 / SC 7 chair has agreed to establish an informal liaison w/ CCSDS. SEA, on behalf of CCSDS, has agreed to that liaison and a joint meeting and telecons have been held.SEA Liaisons
Information Architecture (IA) elements becoming more important to other groups
SLE (data dictionaries, XML schemas, …)
CSS (SMWG) and MOIMS (NavWG & IPR WG) use of XML schemas
XML Standards and Guidelines SIG
SANA, various new and future registries
IAWG needs on-going coordination with MOIMS Information Packaging and Registries (IPR).
Much more partnering is occurring with a focus on how to define an information infrastructure (interfaces, specifications, architecture, components and best practices)
Recommend that BoF be created for cross-cutting information infrastructure specification (registries, repositories) that gets participation from agency specialists as well as stakeholdersCross Area WG / BOF Issues
Security is a cross-cutting discipline that needs to be included in many other Areas and WGs.
CESG is alerted that other Areas and WG should request support from the Security WG (in addition to the SecWG being proactive).
We believe that the mandatory security section in documents will force the other Areas and WGs to seek out help.
Recommend that existing security section be strengthened, waivers are too lenient
Propose a SecWG overview briefing at the Spring ‘06 meeting opening plenary to cover everyone at one time
Security 101 and SecWG initiatives within CCSDSCross Area WG / BOF Issues
SGIA participation from WGs & IOAG agencies included in many other Areas and WGs.
Major issue if IOAG operational organizations do not provide technical point of contact (TPOC)
Delta-DOR end to end process and flow
Study has been initiated, NASA/JPL & ESA participation
CESG Agreement on definition of “Recommended Practice”
A “Litmus Test” has been created by CESG
XML Standards & Guidelines SIG resources
Support from other WGs for short term appears adequate
SANA coordination with other WGs & agencies
Need to get the charter released and approved
Data Management / Data Accountability BoF and where to do the workSEA Other Issues & Concerns
Review of the RASDS document was done by the SAWG members and an expert on RM-ODP. Some issues were found but the WG agreed to necessary updates to the document.
It was agreed to send the updated RASDS document, based on the discussion at this meeting, to CESG and CMC for approval as a Recommended Practice document.
It was also agreed that the work on development of a RASDS formal model should be continued in some form (preferably by a CCSDS BoF/WG) leveraging the liaison relationship established with the ISO/IEC group developing “UML for ODP.”SAWG Executive Summary
Attendees from CNES, BNSC (telecon), NASA/GSFC, NASA/ Langley (telecon), ESA/ESOC (a first!), DLR, NASA/JPL & NASA/GRC (brief)
Discussed and revised the SecWG Security Architecture documents
Discussed and accepted proposals for CCSDS standards for:
Encryption (AES w/ min 128-bit key, additional algorithms allowed)
Authentication/integrity (Digital Signature Standard for public key-based authentication, HMAC-SHA1 for MAC-based authentication)
Discussed CNES approach to developing security requirements and their use of the EBIOS tool
Discussed the development of:
Security Policy Framework
Information Security Planning Guide
Potential usage of Common Criteria to develop mission Protection Profiles
Discussed issues from NASA DSWG – identity management, SCID “exposure” on SANA (aggregates of public data may be a security risk).SecWG Executive Summary
The draft Reference Architecture for Space Information Management Green Book was discussed
Included the updates from the NASA TIM that occurred in August.
Established much improved convergence between GSFC and JPL with respect to the relationship between IA and OAIS.
Chapter 2, the information model, requires more substantial updates than Chapter 3, the functional information management components.
The afternoon IAWG session was canceled in lieu of the meeting on XML best practices (XSG SIG)IAWG Executive Summary
CSS: and CSA.
SGIA role TBD
Use of SecWG authentication & access control
Coordination between Information Packaging and Registries & Information Architecture, discussions on-going
SGIA role TBD
Discussions of development of DM / DA BoF effort needed
Use of RASDS in SM&C doc
Use of SecWG authentication and security framework
Relationships among AMS, MTS, and MOIMS S/C Mon & Con protocol (SM&C)
SGIA role TBD
Uplink & downlink network layer security
SGIA role TBD
Uplink & downlink link & physical layer security
SGIA role TBD
Uplink, downlink & on-board securitySEA Cross Area Coordination
RESOLUTION 1 and CSA. : SEA-SecWG-R-0509-001
The SecWG sent a resolution up requesting that every CCSDS document contain a standard security section. The return flow indicated this was passed.
More than a year later we learn that the language was changed (only blue books, resource problems allow provide a waiver, etc).
And recognizing that:
CCSDS must ensure that security is adequately addressed in our standards,
The current wording in the CMC resolution is too weak,
The AREA resolves that:
The Standard security section should require that include ALL CCSDS documents, not just Blue Books, include the mandatory security section, and …
The security section be mandatory and not waived based on resources.
ACTION ITEM 1: SEA-SecWG-A-0509-001
Request that the CMC update policy on security section to make it mandatory on all CCSDS documents and to remove simple “resources waiver”. At minimum this should apply to Blue, Orange, and Magenta Books.SEA Resolutions to be Sent to CESG and Then to CMC
ACTION ITEM 1: SEA-SecWG-A-0504-001 and CSA.
Request that the CMC review SecWG scope and requirements for cross support and interoperability with agency security policy experts.
ACTION ITEM 1: SEA-SecWG-A-0504-002
Request that the CMC provide adequate resources to the SEA / SecWG to accomplish development of encryption and authentication/integrity standards which are fully adapted to the space community and have been profiled, implemented, and tested before becoming CCSDS recommended standards no later than the end of April 2005.
ACTION ITEM 3: SEA-A-0504-001
Request that the CESG develop a clear and unambiguous process for submitting and resolving RIDs no later than the end of May 2005.
ACTION ITEM 1: SEA-A-0504-002
Request that the areas that have developed or are developing reference architectures or service interfaces to provide them to the SAWG and work with the SAWG to ensure that they and their cross area interactions are correctly understood and properly documented.Outcomes of Earlier SEA Resolutions Sent to CESG
But no simpler.
Internet Robustness Principle -
Be liberal in what you accept, and
conservative in what you send.
Jon Postel, RFC 793 & 1122
Though ambition in itself is a vice,
Yet it is often a source of virtue.
Old Chinese proverb
(from Hsu’s Fortune Cookie)
Suggested for consideration by all ADs and WG chairsPoints to Ponder