16 June 2006 PS 1

SEA CESG SUMMARYSEA CESG SUMMARY

Rome, Italy, 16 June 2006

16 June 2006 PS 2

SEA: Meeting Scheduleand Locations

Working Group/BOF Day/Time Location

SEA Kick-off Plenary Monday0930-1200

tbd

System Architecture WG Wednesday0900-1700

tbd

Information Architecture WG Wednesday0900-1700

tbd

Security WG Mon 1400-1700 Tues 0900-1700

tbdtbd

SANA BoF Thurs 0900-1700 tbd

XML Stds & Guideline SIG Mon 1400-1700Thurs 0900-1700Fri 0900-1200

tbdtbdtbd

System Engineering Area Plenary Friday1300-1600

tbd

16 June 2006 PS 3

System Engineering Area

Overview

• SEA Includes:• System Architecture, Information Architecture & Security

Working Groups• SANA WG (starting to meet as WG now)• XML Standards and Guidelines SIG (cross WG effort)• Delta-DOR SIG (cross WG effort)• SGIA BoF (no IOAG / agency support)

• Responsibilities• 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 CCSDS

16 June 2006 PS 4

System Engineering Area: Current WGs and BOFs

• System Architecture WG - meeting this week• Develop a high level system architecture reference model (and formal

methodology and tools - deferred as work item)• Finalize Reference Architecture for Space Data Systems (RASDS) V1

Magenta Book, resolved handling of RIDs• Discuss future BoF to work on object attributes & templates

• Information Architecture WG - meeting this week• 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 process of work to define component interfaces and

standards w/ MOIMS IPR, focus on only schema registries concern• Security WG - meeting this week

• 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 were useful, but conflicting needs / requirements identified

16 June 2006 PS 5

System Engineering Area: Current WGs and BOFs

• SANA WG - meeting this week• Develop detailed requirements for the Space Assigned

Numbers Authority (SANA) • Review proposed approach & requirements• Only NASA support, task will proceed as support activity to

CCSDS and Secretariat- Other agencies are welcome to review and / or participate

New BoFs

• Space Ground Interoperability Architecture BoF - meeting this week• Develop an end to end space / ground cross support

architecture and services catalog in response to IOAG request• Work may be de-scoped to only services catalog• No IOAG / agency support, draft resolution for IOAG response• Still not clear that this is going to go ahead as CCSDS effort,

cannot without resources• Relationship to proposed object / template BoF unclear

16 June 2006 PS 6

System Engineering Area: Current Special Interest Groups (SIGs)

• Delta-DOR SIG - meeting this week, no feedback• Develop detailed requirements for delta differential one-way

ranging (Delta-DOR) service • Coordinate work in other WGs (SIS/Ranging, CSS/CSTS,

MOIMS/Nav)• Develop integrated vision of service and interoperability

points• Develop any over-arching documents, as needed

• XML Standards and Guidelines SIG - meeting this week• Develop a set of common standards and guidelines for XML

use across CCSDS• Coordinate work in other WGs (MOIMS/Nav, MOIMS/SM&C,

CSS/SMWG, SEA/IAWG)• Product will be a set of guidelines for all CCSDS WG that use

XML to follow• Namespace RFC in development, soon to go out

16 June 2006 PS 7

SAWG Executive Summary

1. A CESG poll for “Approval of RASDS for Agency Red-1 review” was posted in March 2006, and comments were received from the CESG Chairman and the SIS Area Director. Another comment was received from an industrial partner. The WG reviewed these comments.

2. The WG agreed to the disposition on the received comments and the final document will be developed shortly.

3. A proposal was made to create a BoF to develop the charter of a WG to develop templates of service catalogues.

16 June 2006 PS 8

IAWG Executive Summary

• The draft Information Architecture Green Book RASIM was discussed. Input was received from both NASA and CNES from the March version. A May version was distributed which included several updates. Minor updates need to be made as a result of this meeting. A new version will be distributed for final comments by the beginning of July.

• The meeting also discussed the importance of developing some best practice case examples using RASIM modeling and functional components.

• A discussion occurred about the use of RASIM to support SANA

• A joint meeting occurred with IPR related to registries (albeit narrowly focused on schema registries)

16 June 2006 PS 9

SecWG Executive Summary

• Attendees from CNES, BNSC, ESA/ESOC, ESA/ESTEC, ESA/ESRIN, DLR, NASA/MSFC, ASI, CSA (Viagenie) and NASA/JPL.

• Major participation by ESA! Majority of attendees from multiple establishments.• Discussed and revised the SecWG Security Architecture documents and decided

that it should not be Blue but rather (probably) Magenta. Fold key management into architecture document. • Discussions regarding whether this architecture should be informational or

proscriptive• Final thoughts that it should be informational

• Discussed the encryption and authentication draft documents.• Some controversy on this – ESA did not see the need for standardizing on

algorithms- They didn’t need it for interoperability - They want more than just algorithms

• Agreement to add more “meat” to the drafts to further explain the need and desirability to have such recommendations.

• Revised the charter and workplan. Working group to think more about the workplan and provide comments to finalize the revision.

• Discussed the draft of the secure interconnection guide. Major concern was that it was too generic whereas the original NIST 800-47 was too US Govt centric. Agreed to make the document more space-centric.

• Discussed and agreed to a resolution of the public exposure of SCIDs.• Held a successful joint meeting with SM&C, Navigation, AMS, and SANA

• Agreed to develop a strawman security architecture/design in response to SM&C requirements.

16 June 2006 PS 10

SANA Executive Summary

• Executive Summary• Reviewed ops concepts SCID, Heat Sensor and VoIP• Changed to SCID, XML Schema and Heat Sensor• Took action to create a White Paper on SCID future expansion to accommodate

more spacecraft• Reviewed the SANA Action Plan and assigned actions (no major comments)

- Cat 1 SCIDs and CA: MSFC- Cat 2 Current CCSDS Standards and Processes: JPL- Cat 3 Current WGs/SIGs/BoFs: Secretariat- Cat 4 All others: TBD

• Resource: No international participation, proceeding to define service• Schedule requires changing with the creation of a white paper• Even though a review of the charter was scheduled it was not required due to the

limited participation (everyone was familiar with it)• Progress Achieved

• Clarified SANA scope addressing SCIDs and eventually unique numbering on a larger scale (phased)

- SANA addresses numbers and names and addresses- Added a Glossary- Place emphasis on CCSDS related registry requirements first

• SANA proposed implementation of a Registry of Registries was discussed• Discussion of Green/Magenta book was discussed deciding on a Green Book • Detailed discussion on ops concepts and suggestion to establish thread from

the RoR to a detailed xml schema• Schedule

16 June 2006 PS 11

XSG SIG Current Status

• XSG is currently drafting an XML schema Naming and Design Guidelines(NDG) document. • Requires CESG consensus and approval• Needs RFC formatting for submission

• Schedule is to submit a final draft of namespace and versioning sections of NDG to CESG by 09/30/2006

• An annotated outline of full document will be supplied by 09/30/2006 with recommendations for priorities based on CCSDS WG requirements

• The XSG SIG will deliver further NDR draft sections by 01/2007 based on CESG input on priorities

16 June 2006 PS 12

XSG SIG Issues

• Significant resource will be needed both to complete the XML Schema NDR and to supply the domain knowledge to enable the development of reusable and Interoperable XML Schemas

• The XSG recommends the XML SIG be dissolved and a BOF be created so appropriate levels of resource can be assigned to this effort. The XSG SIG will lead this BOF and supply a draft charter as input to the BOF if requested by the CESG.

16 June 2006 PS 13

Other Issues & Concerns

• Highly distributed or once a year meetings• Will make SEA tasks nearly impossible / highly costly• Particular effect on Security WG and also cross area SIGs

• CCSDS Architectural Principles, as called for in A02.1-Y-2 & A00.0-Y-9

• XML Standards & Guidelines development process

• SANA direction & support from other agencies • SGIA futures

• Lack of participation from IOAG, other agencies / WGs• Relationship to other space data system efforts

• Global Earth Obs Sys of Sys (GEOSS), Geneva- WMO, all space agencies w/ Earth Obs- Coord obs & sci, 10 yr plan

• NASA / Constellation & SCAWG activities- Interoperability and cross support- Manned & robotic exploration at the Moon and Mars

16 June 2006 PS 14

SEA Cross Area Coordination

• CSS:• D-DOR SIG • XSG SIG• Transport security• Use of SecWG authentication & access control

• MOIMS:• Coordination between Information Packaging and Registries & Information

Architecture, discussions proceeding, joint meetings planned this week• D-DOR SIG • XSG SIG • Use of RASDS in SM&C doc• Use of SecWG authentication and security framework

• SIS:• End to end architecture for IP over CCSDS, CSS?• Uplink & downlink network layer security

• SLS:• D-DOR SIG • Uplink & downlink link & physical layer security

• SOIS:• Relationships among AMS, MTS, and MOIMS S/C Mon & Con protocol (SM&C)• Uplink, downlink & on-board security