[CMC] Draft CCSDS communique to the IOAG

[Jean-Francois.Kaufeler at esa.int]

Adrian, this is OK with me. Best regards, JFK




"Adrian J. Hooke" <adrian.j.hooke at jpl.nasa.gov> 
Sent by: cmc-bounces at mailman.ccsds.org
19.06.2008 09:29

To
"CCSDS Management Council" <cmc at mailman.ccsds.org>
cc

Subject
[CMC] Draft CCSDS communique to the IOAG






Here is the raw text of the three proposed resolutions to the IOAG that 
were drafted this afternoon in Tsukuba. These will be put up for CMC 
ratification via a poll.

+++++++++++++++++++++++++++++++++++++++++++++++++
[Resolution on future IOP-2 policy making]

CONSIDERING THAT:

1. A major chartered role of the CCSDS is to develop - through consensus - 
appropriate international standards that will guide the development of 
agency infrastructure to maximize interoperability and reduce cost;

2.  A major chartered role of the IOAG is to provide a forum for 
identifying common needs across multiple agencies and for coordinating 
space communications policy, high level procedures, technical interfaces 
and other matters related to interoperability and space communications; 
and that a specific IOAG goal is the achievement of full interoperability 
among member space agencies;

3.  The CCSDS looks to the IOAG to help promote the adoption by member 
agencies of the standards that we develop cooperatively;

AND RECOGNIZING THAT:

1. Achieving such full interoperability requires a close cooperation and 
partnership between agencies; mission planners, designers and operators; 
mission support infrastructure providers; and international standards 
developers;

2. International policy is an important mechanism for coordinating and 
guiding national and agency activities in collaborative missions;

3. Adoption and propagation of standards and associated technology and, 
therefore, accruing their benefits are greatly accelerated by incremental 
deployment of assets, continuous operations and the accumulation of 
heritage and experience;

THE MANAGEMENT COUNCIL OF CCSDS RESOLVES:

To request the IOAG to recommend to the IOP-2 participants the development 
of the following policies: 
International Interoperability Framework

International policy on the need to adopt an integrated approach to 
interoperability, identifying the major anticipated points of cross agency 
support across the total scope of operations. This would unite the major 
mission domains including Earth observation, Lunar exploration, Mars 
exploration, science and deep space and accommodating new initiatives such 
as the Global Exploration Strategy 

Re-usable in-space infrastructure development

International policy for multi-agency deployment of Earth, moon and Mars 
orbital data relays and surface communications assets that can be "left 
behind" and used as part of extended and future missions

Confederated ground infrastructure development 
International policy for continued multi-agency deployment of ground Cross 
Support Transfer Services and Cross Support Service Management. 
+++++++++++++++++++++++++++++++++++++++++++++++++
[Resolution on a Mission Interoperability Working Group]

CONSIDERING THAT:
1. A major chartered role of the CCSDS is to develop - through consensus - 
appropriate international standards that will guide the development of 
agency infrastructure so that interoperability is maximized;

2. A major chartered role of the IOAG is to provide a forum for 
identifying common needs across multiple agencies and for coordinating 
space communications policy, high level procedures, technical interfaces 
and other matters related to interoperability and space communications; 
and that a specific IOAG goal is the achievement of full interoperability 
among member space agencies.

3. The CCSDS looks to the IOAG to be a major customer in terms of needs 
for new standards.

AND RECOGNIZING THAT:

1. Achieving such full interoperability requires a close cooperation and 
partnership between future space mission planners, designers and 
operators; mission support infrastructure providers; and international 
standards developers that addresses broader topics than have been 
historically discussed in the IOAG.

2. Groups such as the ?Global Exploration Strategy Framework for 
Coordination? (GES) and the ?International Lunar Network? (ILN) have begun 
to form independently and outside of the IOAG?s sphere of interest, and 
that these groups have each articulated objectives that include the  need 
to to promote international interoperability.

3. CCSDS would prefer to work within the coordinating framework of the 
IOAG when approaching such groups to gather future requirements, instead 
of developing its own independent contacts.

THE MANAGEMENT COUNCIL OF THE CCSDS RESOLVES:

1. To request that the IOAG should advocate the establishment of a working 
forum (a ?Mission Interoperability Working Group??) whereby space mission 
designers and operators, mission support infrastructure providers and 
international standards developers can meet periodically to identify 
future requirements for interoperability and standardization of mission 
operations infrastructure.

2. That the IOAG should ask the IOP to ensure that such a group will 
contain representation from credible future partner agencies, who are not 
necessarily all members of the IOAG and/or the CCSDS.

3. That the IOAG should forward this suggestion to the IOP for action, 
with a view towards convening such a group early in 2009.

+++++++++++++++++++++++++++++++++++++++++++++++++
[Resolution on an International Space Network]

CONSIDERING THAT:

1. A major outcome of the Inter-Operability Plenary (IOP-1) in June 1999 
was a high level recommendation to begin the deployment of standardized 
interfaces by which ground infrastructure services of cooperating space 
agencies can be offered across international boundaries, using the 
emerging CCSDS ?SLE? series of standards.

2. This recommendation has resulted in a highly satisfactory initial 
deployment of the beginnings of a standardized international space 
communications service infrastructure.

3. There appears to be a need to re-affirm the commitments made at IOP-1 
and to continue with the build-out of these initial ?SLE? services to 
embrace their generalization into new CCSDS ?Cross Support Transfer 
Services? and ?Cross Support Service Management?, deployed in accordance 
with a service catalog that is agreed by participating agencies.

AND RECOGNIZING THAT:

1. Such a continued build-out would represent the beginnings of the 
establishment of a formal international cross support service 
infrastructure within the ground segment.

2. CCSDS standards allow these services to extend into the space segment 
so that agencies with in-space assets (e.g., data relays around the Moon 
and Mars) could prospectively offer flexible space communications and 
navigation services to each other?s remote spacecraft and that it is now 
feasible to migrate these basic space communications and navigation 
services from supporting low-level data exchange to embrace higher level 
space mission operations functions.

THE MANAGEMENT COUNCIL OF THE CCSDS RESOLVES:

1. To suggest that the IOAG should formulate an international 
interoperability architecture which will provide the guidance for 
participating space agencies and commercial operators to each contribute 
elements towards a  future confederated International Space Network. Such 
a network should be ?virtual? (in that it would have no central ownership 
or administration) but it would be united through the independent 
provision of standardized, interoperable services.

2. That the vision for evolving towards a scalable International Space 
Network should become one of the primary recommendations that is codified 
and ratified at the second Inter-Operability Plenary meeting in December 
2008. 

+++++++++++++++++++++++++++++++++++++++++++++++++
_______________________________________________
CMC mailing list
CMC at mailman.ccsds.org
http://mailman.ccsds.org/mailman/listinfo/cmc

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/cmc/attachments/20080630/8cdf8a98/attachment.htm