[Secretariat] [CMC] CCSDS actions in response to IOAG resolution 12.9.1

[Kearney, Mike W. (MSFC-EO01)]

CMC colleagues: I discussed with Adrian the possible approaches for the next iteration of this dialogue with the IOAG.  We considered whether the CMC could take some action by poll first.  But after discussion, we concluded that the CMC really needed information from the CESG about whether the IOAG response could be factored into the current CCSDS working plan, either with or without new resources, or with or without impacting other ongoing work.  Without that assessment, the CMC would probably be unable to reach any conclusion about the best way forward.

So we concluded that it was best to "turn on" the CESG first, and then bring that assessment to the CMC for some decisional action.

If any CMC members have comments about this way forward, please let us know.

   -=- Mike

Mike Kearney
NASA MSFC EO-01
256-544-2029


From: secretariat-bounces at mailman.ccsds.org [mailto:secretariat-bounces at mailman.ccsds.org] On Behalf Of Hooke, Adrian J (9000)
Sent: Wednesday, August 26, 2009 10:28 AM
To: CESG
Cc: CCSDS Management Council
Subject: [Secretariat] [CMC] CCSDS actions in response to IOAG resolution 12.9.1
Importance: High

Area Directors:

1.    After the Spring 2009 meeting in Colorado Springs, the CMC sent the attached (04 May) "CCSDS response to IOAG Resolutions" letter to the IOAG.
2.    After an IOAG "mini-meeting" (13 May), the IOAG sent the attached (23 June) "IOAG-CMC Response 6-09" letter back to the CMC.

In particular, there is general IOAG agreement that - in the context of the redefined IOAG-R-12.9.1 - three documents need to be produced by CCSDS:

A.   a Recommended Practice that defines the profile of CCSDS standards required to operate CFDP over Space Packet over a single Proximity-1 link;
B.   a Recommended Practice that defines the profile of CCSDS standards required to operate CFDP over Space Packet over a single TM/TC/AOS link;
C.   a Recommended Standard for transferring files between ground communications complexes and ground users to support a variety of applications, including emergency commanding.

Items A and B would fall into the domain of SIS and it is my understanding that ESA has volunteered to lead the work.
ACTION R12.9.1-1: Bob Durst/Dai Stanton - identify which working group(s) would perform this work, modify/create draft charters accordingly, and prepare an overall proposal (including schedule and resources) for CMC approval.

Item C would fall into the domain of CSS and right now no-one has volunteered. The IOAG's language further states: "IOAG understanding of the proposed CCSDS standard on file transfers is that it shall cover all types of file transfers, i.e., for the single ground/space link and for the single space/space link.  It shall also cover the file transfers for the single space/space link for the purpose of Emergency Commanding and Essential Telemetry. This understanding is to be confirmed in the CCSDS resolution".
ACTION R12.9.1-2: Erik Barkley/Yves Doat - clarify the exact scope of the work, identify which working group would perform it, modify/create draft charters accordingly, and prepare an overall proposal (including schedule and resources) for CMC approval.

The IOAG-13 meeting is coming up next month (22-24 September) and I will need to present the status of this work. Please have responses to the two Actions prepared by 08 September.

Best regards
Adrian
Chairman, CESG
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/cmc/attachments/20090826/fb1e0403/attachment.html