Joint CMC-CESG Meeting Aerocampus Aquitaine, Bordeaux, France Hosted by CNES 22 April 2013

1. CCSDS Engineering Steering Group (CESG): report to the CCSDS Management Council (CMC) concerning the Spring 2013 Technical Plenary Joint CMC-CESG Meeting Aerocampus Aquitaine, Bordeaux, France Hosted by CNES 22 April 2013

2. CESG Spring 2013: CCSDS Overview

3. Current CCSDS Working Groups, BOFs and SIGs Systems Engineering • Security • Space Assigned Numbers Auth. • Delta-DOR • Time Correlation & Synchronization MISSION CONTROL CENTER End Users Applications/Archives UPDATE MISSION CONTROL CENTER End Users Spacecraft Onboard Interface Services Space Link Services Cross Support Services Space Internetworking Services Mission Ops & Info Mgt Services • RF & Modulation • Space Link Coding & Sync. • Multi/Hyper Data Compress. • Space Link Protocols • Next Generation Uplink • Space Data Link Security • PlanetaryCommunications • Optical Coding and Mod • Onboard Wireless WG • Application Supt Services (incl. Plug-n-Play) • CS Service Management • CS Transfer Services • Cross Supt Service Arch. • Asynchronous Messaging • IP-over-CCSDS Links • Motion Imagery & Apps • Delay Tolerant Networking • Voice • CFDP over Encapsulation • Data Archive Ingestion • Navigation • Spacecraft Monitor & Control • Digital Repository Audit/Certification • Telerobotics Middleware • Planning and Scheduling • Active Working Group (producing standards) • Working Group(in process of closing • Birds-Of-a-Feather (pre-WG approval) • Special Interest Group (pre-BOF integration forum) Six Technical Areas; Twenty six active topics

4. Members of the CESG Systems Engineering CESG Chairs • Security • Space Assigned Numbers Auth. • Delta-DOR • Time Correlation & Synchronization MISSION CONTROL CENTER End Users Applications/Archives Chair Adrian Hooke Deputy Nestor Peccia SE Area Peter Shames Deputy Takahiro Yamada MOIMS Nestor Peccia Deputy Roger Thompson CSS Area Erik Barkley Deputy Margheritadi Giulio SLS Area G-P Calzolari Deputy Gilles Moury SIS Area Keith Scott Deputy Dai Stanton SOIS Area Chris Taylor Deputy Stuart Fowell UPDATE MISSION CONTROL CENTER End Users Spacecraft Onboard Interface Services Space Link Services Cross Support Services Space Internetworking Services Mission Ops & Info Mgt Services • RF & Modulation • Coding & Sync. • Multi/Hyper Data Comp. • Space Link Protocols • Next Generation Uplink • Space Data Link Security • PlanetaryComm • Optical Coding and Mod • Onboard Wireless WG • Application Supt Services (incl. Plug-n-Play) • CS Service Management • CS Transfer Services • Cross Supt Service Arch. • Asynchronous Messaging • IP-over-CCSDS Links • Motion Imagery & Apps • Delay Tolerant Networking • Voice • CFDP over Encapsulation • Data Archive Ingestion • Navigation • Spacecraft Monitor & Control • Digital Repository Audit/Certification • Telerobotics

5. CCSDS Adoption by Missions CCSDS has published 73 Currently Active Standards and Practices UPDATE 596space missions have adopted and used various CCSDS standards

6. Standards Production in CY12 UPDATE

7. CESG FALL 2012: items brought to attention of the CMC

8. Ethical Breach • A serious breach of professional ethics was uncovered in a CCSDS working group • A member of this group attended one meeting and did not contribute anything • This individual then used his private CWE access to write a journal paper that: • Appears to have plagiarized work • Misrepresented the work of other WG members in potentially damaging ways and exposed WG-internal debates that were not meant to be made public and which took place at a meeting that the member in question did not attend • We intercepted this paper only because one of the other WG members happened to be on the pre-publication technical review board of the journal. The plagiarism issue is being handled by the journal. However, because of the professional confidentiality issues involved, no action can be taken on the misrepresentation of CCSDS work. • Instead, the CESG recommends that the CMC should adopt a slightly-modified version of the ISO code of ethics, which would then be impressed on every member of a CCSDS working group. UPDATE

9. The CESG recommends the following as the CCSDS Code of Conduct Considering the role of CCSDS as ISO Technical Committee 20 Subcommittee 13, CCSDS fully adopts the ISO Code of Conduct. This Code of Conduct (Code) is to facilitate ISO's work which is carried out in an international, multi-stakeholder, multi-sector environment. It applies to people who choose to participate in an ISO committee, working group or other consensus group. The Code is an obligation for participation in the above groups that work in the framework of the ISO/IEC Directives. As participants in ISO work, we acknowledge the responsibility and value of participating in developing International Standards. We therefore adhere to this Code in accordance with the terms below. UPDATE Further, CCSDS also adopts the following augmentation to the ISO Code of Conduct.

10. Periodic Review and Deprecation • The following documents are up for periodic review • CCSDS 620.0-B-2: Standard Formatted Data Units¬ Structure and Construction Rules • CCSDS 622.0-B-1: Standard Formatted Data Units¬ Referencing Environment • CCSDS 630.0-B-1: Standard Formatted Data Units ¬ Control Authority Procedures • CCSDS 632.0-B-1: Standard Formatted Data Units ¬ Control Authority Data Structures • CCSDS 641.0-B-2: Parameter Value Language Specification (CCSD0006 and CCSD0008) • CCSDS 643.0-B-1: ASCII Encoded English (CCSD0002) • CCSDS 647.1-B-1: Data Entity Dictionary Specification Language (DEDSL)-Abstract Syntax (CCSD0011) • CCSDS 647.2-B-1: Data Entity Dictionary Specification Language (DEDSL)¬PVL Syntax (CCSD0012) • CCSDS 647.3-B-1: Data Entity Dictionary Specification Language (DEDSL)¬ XML/DTD Syntax (CCSD0013 ) • This was to be their last planned re-affirmation. However, there are no resources available to perform the reviews • The CESG’s first thought was simply to re-affirm the whole suite without review and to add a disclaimer that they will be deprecated to Historical (Silver Book) status in five years. • However, Silver Book status puts them on the Non-Normative track. But we have data stored in SFDU format with the intention of it being stored for the long-term, possibly 50 + years. An argument has been made that the SFDU family should not be deprecated to Silver any more than the Fortran or the even older COBOL language standards are disposed of • The standards for the computer languages remain standards, even when other computer languages are adopted for wide-spread use. • A number of the members of the suite (such as DEDSL and EAST) are actively being used and there is no proposed replacement for them at this point. Certainly these should remain Blue Books until there is a defined replacement. • Other standards (such as SFDU and XFDU) are more problematic, since they aren't totally replacements for one another. The WG would generally recommend XFDU for totally new systems although SFDU could also still make sense for NEW projects, especially if the data were binary formatted rather than character oriented. This is sort of like determining what computer language you use to program in. We can use either one of them to write almost any system, but your particular project needs (and the choices within your programming environment) determine which tool you will use. • The general feeling of the CESG seems to be to just go ahead and reaffirm the suite without review. Does the CMC have any comment? UPDATE

11. Removing Overlaps • CCSDS areas and working group products continue to have disconnects: • We still do not have a common architecture nor a common information model (RA SIG was cancelled) • Multiple XML schema using different formats, namespaces, and vocabularies (old XSG SIG problem that was never completed) • We may be able to help guide recurring XML issues by (finally) publishing the RFC & XML Guidelines from the XSG SIG • An Information Model is a candidate for inclusion in the proposed Timeline Standard BOF: need to confirm along with resources • We simply don’t have adequate resources to get these overlaps properly resolved UPDATE

12. Future Messaging Standards (Again) • As noted at the Spring 2012 meeting, there are two potentially-competing standards, at a key cross support interface, that are proceeding independently • ESA’s Packet Utilization Standard (PUS), which is firmly rooted in the ECSS but which was not admitted into the CCSDS program of work. • NASA’s ex-Constellation Data Exchange Message (DEM), which has a lot of traction in NASA’s new Exploration systems (MPCV, SLS, etc.) • The PUS and the DEM are both “middleware” standards which define the semantics and syntax for passing control and state information to and from remote devices. Further complicating the situation is that CCSDS is embarking on Telerobotics middleware development, which also assumes that the physical transfer will occur using the CCSDS Asynchronous Messaging Service (AMS) protocol • Yet we have no forum or resources in CCSDS for discussing these issues • If this situation persists unchecked, the potential exists in the 2015 timeframe for serious interoperability issues if Europe and the US try to integrate international exploration missions with different ways of passing data between systems • This problem may not be limited to human exploration missions. Some international exploration scenarios involve a blend of robotic and human systems • This is another instance where lack of resources now may lead to serious future repercussions. Does the CMC want to attempt a “fix”, for instance by making another overture to the International Space Exploration Coordination Group (ISECG)? Rumor has it that the ISECG is now starting to take communications architectures more seriously. UPDATE

13. Meeting Hosting and Support • The CESG received generally favorable reviews of the Cleveland location, hotel and meeting support • However, a major issue – and this was a big one – was the absence of a break area and refreshments where the working groups could mingle and network mid-morning and mid-afternoon • This isn’t a luxury: the ability to cross-pollinate and network with peers in other working groups is a key facet of face-face Plenary meetings • As a minimum, a lounge-style room should be provided where people can bring back their own coffee/snacks and socialize with others during the breaks UPDATE

14. CESG FALL 2012: Area Reports

15. SPACECRAFT ONBOARD INTERFACES SERVICES (SOIS) AREA Chris Taylor (AD) Stuart Fowell (DAD)

16. SOIS Area Report - Current Working Groups • Application Support Services WG • Wireless WG • Subnetwork Services WG (Inactive) The SOIS area covers onboard communication services with the intention of standardising H/W and S/W interfaces between avionics elements & devices. Wireless activities cover intra-spacecraft communication, AIV and RFID A considerable part of our work is outside of the CCSDS where we perform a harmonising role for avionics related development

17. SOIS Area Report B. Meeting Demographics UPDATE

18. SOIS Area Report • Application Support Services Working Group • Goal: Develop SOIS Application Support layer services and if appropriate protocols • Working Group Status • Device Data Pooling, Device Access and Message Transfer Magenta Books published Nov 2012 – Mar 2013 • RIDs raised from CESG from poll to publish GreenBookIssue 2 • Device Enumeration and Device Virtualisation Red Books completing updates following RIDs raised from CESG for poll for 1st Agency Review • Progressing Electronic Data Sheets Red Book & associated XML Schema • Progressing Common Dictionary of Terms Red Book & associated ontology • Some attendance via WebEx – problems with microphones in meeting room so not great solution

19. SOIS Area Report • Application Support Services WG (cont.) • Progress • All 1st set of SOIS APP service specifications are either published, or with Secretariat for publishing or for Agency review process • Exploratory prototyping of XML schemas for device EDS by ESA proceeding, two alternatives produced • ESA and NASA planning to experiment with using both XML schemas for defining example device data sheets (SpaceWire camera, star tracker, gyro, GPS receiver, SDR) • Relationship with Common Dictionary of Terms defined • Process for development of device data sheets defined • Explored a couple of issues of how to use SOIS architecture (remote interface units, polled data acquisitions on 1553, use of result metadata in indication service primitives) • Explored how SUMO, NASA-JSC and NASA-GRC can contribute to this process, e.g. US industry outreach, example real-world ICD transformations to EDS • Planning • Publish remaining Green and Magenta Books • Continue fortnightly telecons • Produce experimental device EDS for Fall 2013 meeting, using Common DoT terms, to complete exploratory prototyping of XML schema • Extend Common DoT taxonomy with common terms for examined ICDs for Fall 2013 meeting

20. SOIS Area Report Application Support Services WG Near Term Planning

21. Wireless WG SOIS Area Report • Goal: Develop wireless recommendations for onboard space applications • Working Group Status: • Did not meet due to NASA travel issues • Progress • Planning • LDR MB RID responses to originators to be composed and completed by November 2nd. • LDR MB RID closure-related updates to be completed by November 30th. • Green book updates covering high rate use cases and technology evaluation to be completed by April 8th, 2013. • Continue monthly telecons

22. SOIS Area Report Wireless WG (continued) Near Term Planning

23. SOIS WGs Telecon Usage

24. APP WG Remaining Magenta books (almost) under publication or ready for Agency review Electronic data sheet activities on schedule Possibly the biggest issue is the success of Electronic data sheets – every one wants to use them but in their own way! By Fall 2013 we should have completed exploratory prototyping Wireless WG Did not meet SOIS Area Report: Summary

25. SYSTEMS ENGINEERING (SE) AREA Peter Shames (AD) Takahiro Yamada (DAD)

26. System Engineering Area (SEA) • Objective • Guide overall CCSDS architecture for space mission communications, operations, and cross-support • Support the CESG in evaluating consistency of all area programs of work with the defined architecture • Create cross-cutting working groups and BOFs as required to progress the work of CCSDS • Focus • Define reference architectures for describing space mission communications, operations, and cross-support standardization • Coordinate and collaborate with other areas about architectural choices and options • Define standards for cross cutting topics such as security and discrete architecture frameworks, and for those that cross cut multiple layers of protocols • Support other working groups and BoFs that are addressing cross cutting issues • SEA Working Groups • Security Working Group • Delta-DOR Working Group • Space Assigned Numbers Authority (SANA) Steering Group (operational) UPDATE

27. SE Area ReportB. Meeting Demographics UPDATE

28. Systems Engineering Area Report • Security WG Goals: • Develop security overview & threat assessment, and security architecture, framework and related standards • Current focus (security architecture, glossary, algorithms, key management) • Working Group Status: • Progress • Algorithms BB, Security Architecture MB, and Information Security Glossary GB have passed final CESG poll ready for publication. • Update the Algorithm Yellow Book to include the hash function to be used for digital signature testing. DLR will document the testing they have already accomplished. • Reviewed draft of Algorithm Green Book. • Discussed Threat Green Book revision and agreed on updated outline. • Agreed to go forward with the writing of an adaptation profile of IPSec for CCSDS. • Security Glossary complete, to review against CCSDS Glossary, update, remove any issues, and publish. • WG agreed to request new work programs: update of Threat GB, adaptation profile of IPSec, create Algorithms GB. • Good joint progress on Space Data Link Layer Security WG, produced by SecWG members, reported in SLS UPDATE

29. Systems Engineering Area Report • Delta-DOR WG • Goals: • Develop delta differential one-way ranging (Delta-DOR) service • Coordinate work in other WGs (SLS/Ranging, CSS/CSTS, MOIMS/Nav, CSS/SM) • Develop integrated service, interoperability points, and standards • Working Group Status: • Delta-DOR Raw Data Exchange Format (RDEF) Blue Book draft (Red-2): all RIDs resolved, ready to be published as Blue Book • Interoperability validation 75% done (ESA, JAXA, NASA), YB test report to be complete, expect final 02/13. • DDOR Green Book updates final, publish by 11/12. • SANA Quasar Catalogue candidate created (Ka band, currently only S & X), discussed YB to define SANA registry and update policy. YB draft to be ready 06/13. • SMWG, expect D-DOR to be covered by next version of SM BB, no new issues, no discussion at this meeting. • Discussion with RF&M WG (mods to 2.5.6B, 25.5-27GHz), need note about power for DOR tones UPDATE

30. Systems Engineering Area Report • SANA Operations & SANA Steering Group (SSG) Goals: • Operate the Space Assigned Numbers Authority (SANA) • Support CCSDS WG use of the registry functions • Operations Status: • SANA operator in place, web site operational, thirty-two (32) approved registries, seven (7) candidate registries not yet approved, most waiting on final Blue Book publication • Met this week with SIS-DTN, SLS-SLP • SCID registry and SANA were out of sync, official registryhadmanyabnormalities and is hard to use. Suggest change of policy to leaveassignmentat official registry but use SANA as the actualregistry. Seehttp://sanaregistry.org/r/spacecraftid/spacecraftid.htmlvs http://standards.gsfc.nasa.gov/ccsds/ccsds_id.txt • SANA Steering Group met • CMC Chair, SEA AD, DLR reps only • SANA appears to be working well, several new registries in discussion • Agreed on approach for resolving SCID issue • Agreed to develop a prototype RESTful programmatic interface to SANA registries, SCID access is a driver • SANA Yellow Book procedure, CCSDS 313.0-Y-1, published, July 2011 UPDATE

31. Mission Planning SIG Participated in Mission Planning SIG, several presentations and excellent discussions Appears to be significant interest in continuing the MP discussions, leading to a BoF, and there was also expressed interest in the NASA Timeline Standard proposal Timelines are cross-cutting, potentially touching several working groups: MOIMS SM&C / MP, MOIMS Nav, CSS SM, SIS DTN Introduces need to arrive at a common CCSDS information model to permit data interoperable exchange and data comparisons SEA proposes to create a BoF to explore defining a compact, extensible, interoperable timeline data exchange standard, to be carefully coordinated with other WGs (see NASA Timeline Standard proposal for details) Sec WG - SDLS Meeting Joint meeting continues to be productive and work is largely on track Have identified no “show-stoppers” Details reported by SDLS WG chair in SLS report • Systems Engineering Area Report: Cross Area Meetings UPDATE

32. MISSION OPERATIONS AND INFORMATION MANAGEMENT SERVICES (MOIMS) AREA Nestor Peccia (AD) Roger Thompson (DAD)

33. MOIMS Area Report B. Meeting Demographics UPDATE

34. Navigation (NAV) Working Group • Conjunction Data Message (CDM) • Continued detailed planning for prototype testing by 5 organizations • Updated and more or less finalized the draft test plan • Discussed the schedules for testing and analysis of results • Discussed the document completion schedule • Conducted a detailed proofreading of the document • Navigation Green Book • Continued discussion of Green Book Version 4 volume 1 updates and supplements • Initiated identification of new content for the Version 4 volume 2 related to CDM and TDM • Pointing Requests Message (PRM) • Continued discussion of PRM • Discussed detail of the inertial pointing template and an example thereof • Previewed other planned templates UPDATE

35. Navigation (NAV) Working Group • Tracking Data Message (TDM) • Continued reconfirmation review with discussion of 2sets of proposed changes from 2 agencies • Initiated identification of requirements for new features, with some updates confirmed • Initiated identification of prototypers for new features • Navigation Hardware Message (NHM) • Completed discussion of NHM White Book 5 • Completed presentation of NHM concept to SM&C WG • Spacecraft Maneuver Message (SMM) • Initiated discussion of SMM Requirements • Events Message (EVM) • Completed discussion of the System Engineering Area involvement in the “event” construct and postponement of EVM • Spacecraft Perturbations Message (SPM) • We propose to delete the document from the Project Framework • We propose to retain the document in the WG Charter UPDATE

36. Navigation (NAV) Working Group • CROSS-AREA Meetings & Technical Issues • AGI/CSSI/Space Data Center liaison was in attendance Mon-Wed. Input was very helpful to Navigation WG goals. No current issues. • Met with Spacecraft Monitor & Control WG to discuss Flight Dynamics Service • Administration • Updated Charter: N/A... no changes necessary at this time • Initiated updates to project resources in the Framework • Insufficient time for review of Navigation Working Group 5 Year Plan UPDATE

37. Navigation (NAV) Working Group: Assessment • Met top priority goal for meetings (significant progress on CDM), made some progress on others (TDM Review, Green Book, PRM, NHM, SMM) • Excellent participation in this meeting…16 attendees most days • 4-Day Meeting: Navigation WG has occasionally concluded its work in 4 days, but this time again felt constrained (as at Darmstadt) due to the volume of work in progress UPDATE

38. Navigation (NAV) Working Group: Observations • Skype/GoogleVoice: GoogleVoice worked reasonably well on a limited scale (one person, one hour) at Darmstadt in Spring 2012. Attempted a Skype telecon (voice only) during the Cleveland meetings with less success. • Heavily prioritizing one document to the exclusion of others has both advantages and disadvantages. • Advantages: can “fast track” the standards development process • Disadvantages: can delay progress on projects with lower priority; can affect enthusiasm of members not directly involved in the “priority”document • The WG broke at 1730 most days (1745 on Wednesday)... the attempt to squeeze in more progress by routinely working until 1830, while it sounds desirable, can actually reduce productivity. UPDATE

39. Attendance More than 20 people on average from 10 different agencies/organisations Overall a very successful meeting SM&C WG thanks NASA for the excellent organization of the workshop. More coffee would have been appreciated! status: status: OK OK CAUTION CAUTION PROBLEM PROBLEM comment: comment: X X • MOIMS REPORT - SM&C WG Overall Status UPDATE

40. MOIMS Report - SM&C WG Books Status (1) • MO Reference Model (MB, ESA) • Published • MO Common Object Model (BB, ESA) • Completed Agency Review 3: 60 RIDs (12 ESA, 2 CNES, 46 NASA) received to be discussed this week • Major RIDs have been discussed and disposed. No showstopper • MO COM Testing (YB, ESA/CNES) • Work is on-going and waiting for the final version of the document to produce the final prototype • MO Message Abstraction Layer (BB, ESA) • Issue 1: published • Issue 2 (pink sheet to adapt to new COM and correct a few minor mistakes): completed Agency Review with 45 RIDs (19 ESA, 1 CNES, 25 NASA) received to be discussed this week • Major RIDs have been discussed and disposed. No showstopper • MO MAL Testing (YB, ESA/CNES) • Issue 1: published • Issue 2: needs updates following MAL issue 2, which are on-going • MO M&C Service (BB, ESA) • Submitted to Secretariat for Agency Review • Discussed operational issue on check service • Agreed on measures to make the MO Service standards more “user friendly” • MO M&C Service Testing (YB, ESA/DLR) • Needs to be produced UPDATE

41. MO Common Services (BB, ESA) Needs to be adapted to new MAL/COM. This will be the next document to be tackled after M&C MO Java Language API (MB, CNES) Completed Agency Review 1: responded internally to CESG clarifications. No showstopper. Proposed updates will be verified with the authors MO Space Packet Binding (BB, CNES) Resolution submitted by MOIMS AD requesting Agency Review MO C++ Language API (MB, NASA) Is on-going and the C++ API is being used in several projects. However, NASA/JSC cannot yet commit to the production of the document because of lack of resources XTCE 1.2 (BB pink sheet, NASA) Upgrade to be done by OMG first by Dec 2012. Review in parallel with OMG Changes are minor and should not require prototyping. XTCE Element Description (GB, NASA) Published in May 12 XTCE Conformance Profiles (OMG, NASA) Renamed on OMG request from Tailoring Guidelines. NASA has submitted their GovSat Conformance Profile to OMG which has published an RFC with due date 24Oct12 • MOIMS REPORT - SM&C WG Books Status (2) UPDATE

42. Presented MO Usage in Projects ESA METERON Implementation of the Action, Parameter and Activity services over Web Services. !Suite of MO Service Resources to aid potential users Organise existing material, create new material  Effort • MOIMS Report - SM&C WG General Points UPDATE

43. Joint Meeting with Telerobotic BOF MO Framework explicitly referred to into the BOF concept paper Joint SM&C-NAV Meeting Improved mutual awareness and understanding Identify potential use of MO Service s for Hardware Message. TN will be produced. • MOIMS REPORT - SM&C WG Joint Meetings UPDATE

44. Large attendance (about 26 persons at the meeting plus 8 via WebEx) General consensus on need for standardisation of Mission Planning Services Keep the level of standardisation simple, at least at the beginning Fast track (suboptimal solution) useful also to focus and consolidate the opinion of the planning experts Identified standardisation priorities Priority 1: Terminology + MP system context + data model Priority 2: Planning Request Management (and reporting) Priority 2: Plan/Timeline Management (and reporting), including the possible usage of JPL Timelines as exchange format To be done in cooperation with NAV: Flight Dynamics Event Management Rules & Constraints Management (and reporting): this was considered more difficult to agree upon Way forward After 2 sessions, the SM&C WG recommends that the MOIMS AD forms a new BOF to standardise Mission Planning Services based on the MO Service Framework with the priorities highlighted above JPL has agreed to evaluate the relevance of the “JPL Timeline” as exchange format for selected planning data based on the MO Service Framework. The results shall be reflected in a draft update of the Mission Planning concept paper • MOIMS REPORT - SM&C WG • Call for Interest in Standardization of Mission Planning Services UPDATE

45. MOIMS Area Report: SM&C WG • Schedule (updates in Red) UPDATE

46. MOIMS Area Report: SM&C WG • Contribution by Agencies (TBC in Red) UPDATE

47. MOIMS REPORT - DAI WG • Goal:Develop a CCSDS/ISO standard for a Submission Information Package (SIP) for transfer and validation of information submitted to an archive • Working Group Status: Active • Working Group Summary Situation: • WG met via webex. No physical meeting at Darmstadt UPDATE

48. PAIS Blue Book, Issue 2 WG is updating the BB WG is updating the prototypes and will complete testing report by March 2013 WG recommends to reaffirm the following documents (and asociated ISO docs) due to lack of resources CCSDS 620.0-B-2: Standard Formatted Data Units­ Structure and Construction Rules CCSDS 622.0-B-1: Standard Formatted Data Units­ Referencing Environment CCSDS 630.0-B-1: Standard Formatted Data Units ­ Control Authority Procedures CCSDS 632.0-B-1: Standard Formatted Data Units ­ Control Authority Data Structures CCSDS 641.0-B-2: Parameter Value Language Specification (CCSD0006 and CCSD0008) CCSDS 643.0-B-1: ASCII Encoded English (CCSD0002) CCSDS 647.1-B-1:  Data Entity Dictionary Specification Language (DEDSL)­Abstract Syntax (CCSD0011) CCSDS 647.2-B-1:  Data Entity Dictionary Specification Language (DEDSL)­PVL Syntax (CCSD0012) CCSDS 647.3-B-1:  Data Entity Dictionary Specification Language (DEDSL)­ XML/DTD Syntax (CCSD0013 ) • MOIMS REPORT - DAI WG UPDATE

49. MOIMS REPORT - RAC WG • Goal: Obtain ISO approval of a standard that establishes the criteria that a repository must meet to be designated an ISO Trusted Digital Repository • Working Group Status: Active __X_ Idle ____ • Working Group Summary Situation: • No physical meeting. Wiki based activity. UPDATE

50. MOIMS REPORT - Telerobotics BOF Status • Remote participation was enabled by Webex and Teleconference • 16 Local attendees • 3 Remote attendees • Meeting Length < 2hours • Meeting Results • Telerobotics Concept Paper is of sufficient quality and content • Draft Charter is of sufficient quality and content • Working Group will produce 1 Green Book and 1 Blue Book • Sufficient resources were committed by 4 agencies to enable the start of the Telerobotics Working Group • 37 MM of the required 48 MM were committed • CSA, DLR, ESA, NASA • NASA will act as Book Captain UPDATE