description	action	due date
J. Ellwood welcomed attendees (attachment 1) and apologised on behalf of IKI who could not attend.   The meeting was conducted according to the agenda provided in attachment 2.   The status of interoperability was reported by representatives from each agency (attachment 3). The following additional points were made:   NASA/JPL indicated a possible request for use of the ESA Perth 15m station in support of their SIRTF mission (Launch December 2001). NASA/JPL has been requested by ASI to specify in detail what DSN compatibility means. In this context JPL will also specify SLE service requirements. It was agreed that the SLE services Phase 1A/1B (CLTU, FSP, RAF, RCF and OCF) will be implemented for Integral, Muses-C, Rosetta and Mars Express. Prior to the start of Phase 1C, i.e. the addition of the SLE provider function in a ground station a validation exercise will be conducted. (Note Phases 1A, 1B and 1C, and their respective contents are primarily related to the ESA internal development plan) NASA has no plan for the implementation of the SLE OCF service.   NASA/JPL’s Network Information System (NIS) has two different systems: one for 34/70m and one for 26m stations. ISAS intends to initially implement SLE with a gateway, acting as a SLE server.   M. Warhaut and W. Martin gave a briefing of the Interoperability Plenary Meeting held at ESA-HQ (Paris) 21/22 June 1999 (attachment 4).   Actions   Actions were taken to define global and minimum SLE Management services.         A list of vocabulary/glossary for the level of cross support (prime, back-up, emergency etc.) will be compiled with a view to becoming an accepted set of terms/definitions. The vocabulary shall also include a definition of the term "service", since sometimes, one uses the term "service" to mean a "type of service", e.g. the telemetry vs. command service. At other times, it is meant to be an "instance of service". There are also times when the term "service" is uttered to differentiate one "mode of service" or "level of service" from another, i.e. on-line versus off-line, or prime vs. back-up, vs. emergency.   GSFC/NASA will report to WG-4 on the status of TCP/IP efforts at NASA for end-to-end mission communication.   An action is taken to report on the conclusion of frequency allocation discussions at the Space Frequency Coordination Group.	Global: B. Watson/ R. Miller Minimum: M. Warhaut   W. Martin                 W. Watson     W. Martin
Recommendations   A list of recommendations to be pursued at IACG, ITCOP and CCSDS level has been compiled and is delineated below.
IACG WG-4 has identified: RAF CLTU RCF FSP to be the most urgently required SLE Transfer Services for CCSDS compliant cross-support / interoperability. IACG WG-4 recommends that every effort is made to keep the current draft CCSDS Recommendations for these services stable and that they are advanced to the Blue Book state at highest priority.   IACG WG-4 foresees benefits in areas of both cost and interoperability if the SLE services interface utilises application programming interface (API) software and the development of each of the several APIs are undertaken by specific agencies whereafter they are exchanged among agencies. In the opinion of IACG WG-4 development of API in the manner outlined above, obviates the need for an SLE light specification freeing critical resources within CSDS panel 3 to focus on the development of other service specifications.   3. In the absence of an internationally agreed standard ESA and NASA/JPL have agreed on the use of Orbit Data File (ODF) and Spacecraft Planet Kernel (SPK) file format. The CCSDS shall establish pertinent recommendations for radiometric data exchange on the above basis. Priority shall be given to the SPK files, required to ensure proper antenna pointing required in the context of SLE.   Management Services: The IACG WG-4 will examine the current set of ad-hoc management services for CCSDS SLE Transfer Service, (Integral, Muses-C, Rosetta, Mars Express). WG-4 members will consult with their respective Space Science Organisations to identify future trends and needs for Transfer Service management. From these a set of high level management service requirements will be compared with the CCSDS service management specification for validation.   IACG WG-4 recommends the use of TCP/IP for inter-agency ground cross support. As such, IACG WG-4 recommends all new missions not to use data formats based on the 4800-bit NASCOM blocks. IACG WG-4 recommends as an interim solution all agencies to adopt the JPL-ESOC approach to credential verification using x.509 Simple Authentication Procedure as the means to interoperate across different security domains among agencies. In addition, a set of standard operational procedures, including rules and responsibility, for the administration of user names and passwords, should be defined.   IACG WG-4 foresees the benefits of using CCSDS File Delivery Protocol (CFDP) for future space missions starting 2003 and hence recommends CCSDS to expand the SLE service definition to accommodate the end-to-end delivery of telemetry and command data using file transfer protocols.   IACG WG-4 foresees the need for interagency coordination for better interoperability in the following areas: Definition of a standard Time Correlation Service Implementing Turbo Codes Definition of a standard Telemetry Directories Structure Having achieved convergence on the interoperability approach in the space science domain, the IACG WG-4 offers to present its concept to the CEOS, as proposed by the Interoperability Plenary.