<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ligatures:standardcontextual;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-ligatures:standardcontextual;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">CSS Cloud BOF Colleagues,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The CESG/CMC discussed the cloud BOF and resulting recommendation for working group formation this past Tuesday at the Tokyo meetings. The conclusion from that meeting is to add a lower priority consideration with regard to inclusion of
command data delivery via cloud computing. In this case, of course, it would be the mission GDS delivering command data to the agency ground station. I don't think this changes very much of the concept paper as command data delivery would essentially be another
form of streaming data, leveraging the CLTU PDU for format definition. (It begs the question of delivery for files of command data, but frankly, I think the management of such a filetype is best left to the mission ops center with the understanding that the
MOC can initiate streaming from any such files under their control.) <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I know we have not discussed this use case in depth in the BOF but my sense is that this can be addressed in the working group, and that we risk more harm than benefit in delaying the creation of the working group. The concept paper with
some very minor updates can be found in the CWE via <a href="https://cwe.ccsds.org/css/docs/CSS-CLOUD/CWE%20Private/Concept%20Paper/Drafts/230601-ConceptPaper%26Report.pdf">
https://cwe.ccsds.org/css/docs/CSS-CLOUD/CWE%20Private/Concept%20Paper/Drafts/230601-ConceptPaper%26Report.pdf</a>. Please look for the yellow highlighting in sections 5 and 7.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In the interest of time, I plan to send the concept paper to the CMC Chair to get the wheels turning re creation of the WG. Nonetheless if you have any comments please feel free to send those comments along.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal">-Erik<o:p></o:p></p>
</div>
</body>
</html>