<html 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=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Courier New";
panose-1:2 7 3 9 2 2 5 2 4 4;}
@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;}
@font-face
{font-family:sans-serif;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Courier;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Ciao Nestor,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">I read over the presentation you have prepared and have a few comments, take them for what they are worth.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Overall it seems like it covers the CCSDS territory and does a quite good job of getting across the story of the future challenges for space exploration and of the advantages of interoperable
and cross supportable standards. The intent, as I understand it, is to point out that CCSDS does look toward the future and that we have a suite of standards, in place and being developed, that address many of the communications challenges.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">The one chart that I found most difficult to understand was pg 5. I just do not understand the graphics nor what they are trying to say. I do get the points about:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:11.0pt;font-family:Calibri">Select optimal frequency bands to grant high degree of interoperability</span></b><b><span style="font-size:11.0pt;font-family:"MS Mincho"">
</span></b><span style="font-size:11.0pt;font-family:Calibri">•
<b>Moon / Earth, Mars / Earth, Lunar / Mars Proximity forward / return links </b>
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:11.0pt;font-family:Calibri">Select optimal coding / modulation schemes
</span></b><span style="font-size:11.0pt;font-family:Calibri"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">And also<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:11.0pt;font-family:Calibri">DTN</span></b><b><span style="font-size:11.0pt;font-family:"MS Mincho"">
<o:p></o:p></span></b></p>
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:11.0pt;font-family:Calibri">Service Management
<o:p></o:p></span></b></p>
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:11.0pt;font-family:Calibri">Optical communication
</span></b><span style="font-size:11.0pt;font-family:Calibri"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">I'm guessing that this chart is animated and that is a part of delivering the message. I am wondering why the emphasis on "<b>optimal frequency bands"
</b>and<b> " optimal coding / modulation" </b>to grant a high degree of interoperability. Surely selection of a suitable link layer that would run over all those links and support high optical comm data rates would also be a part of optimal interoperability.
I'd specifically add in USLP since it does meet those criteria. I also note that you have DTN and SM in the list, but not CSS. These standards may be a bit more obscure, but they are a cornerstone in CCSDS and the IOAG for supporting interoperable use of
what will continue to be, I am sure, scarce and expensive space comm assets.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Pg 7, is a great motivator for the future and also emphasizes interoperability and cross support. I also see drivers for networking, sensor webs, mobile comm, and it has a couple of lines
about multi-agency mission ops and human or robotic exploration. But after all of this emphasis on interoperability, communications, and networking what rather surprised me was seeing MOIMS listed as number 2 in the CCSDS Strategic Plan (pg 8) and that
pgs 9 & 10 also are about MOIMS. Based on everything else in these materials I would have expected more emphasis on communications, optical comm, DTN, and cross support (SM & CSTS), not on MOIMS and what is happening in Europe. I think we all know that is
your background and apparent interest, but it does not come across as a well balanced set of materials aligned with the focus (CCSDS in the future) nor with the story told in the first 7 pages.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Similarly, SOIS, pg 12, seems out of place ahead of SLS and SIS. I can see not much in the way of motivation for this in any of the preceding materials, but do acknowledge that it is an
area of work in CCSDS and that it may yet produce interoperable standards. And speaking of SLS, I would expect to see USLP figure prominently for the future, but it's not shown at all. Pg 11 should probably be entitled SM & CSTS and some emphasis placed
on the CSTS services which also appear on this diagram. The whole new set of RD-CSTS, MD-CSTS, SC-CSTS, and FF-CSTS are really important for future interoperability and I think they should be emphasized or at least mentioned.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">My own biases are well known, and while I do see System Engineering on pg 8 there is no chart for System Engineering. Given the SEA role in Security (space asset protection must be an
important topic for everyone), in D-DOR (essential for precision entry, descent, and landing for human and robotic missions), and also the architecture work, RASDS, leadership in SCCS-ADD and in the current Applications and Support Layer architecture (which
is where slide 9 came from) it does seem like a slight to leave SEA out entirely. I've attached a set of diagrams taken from the SCCS-ARD that use RASDS to address end-to-end deployments of a large part of the CCSDS suite of interoperable standards. In addition
to the static and multi-path "stack" diagram on the SLS page (pg 13) these show actual future end-to-end deployments (the "plumbing" that will make pg 5 real), and also will allow you to say something about the SEA architecture work.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">I would ask you to do the suggested re-ordering and other adjustments, drop slide 10, and insert some sort of SEA representation.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Thanks, Peter<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"></span><span style="font-size:11.0pt;font-family:Calibri"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-family:Calibri;color:black">From:
</span></b><span style="font-family:Calibri;color:black">CESG <cesg-bounces@mailman.ccsds.org> on behalf of Nestor Peccia <Nestor.Peccia@esa.int><br>
<b>Date: </b>Tuesday, March 7, 2017 at 11:49 PM<br>
<b>To: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><br>
<b>Subject: </b>[CESG] CCSDS presentation at GSAW<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;font-family:"sans-serif","serif"">Dear all,</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">Please find attached a CCSDS presentation to be given at the next GSAW</span>
<br>
<br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">Comments welcome (and if you have better pictures it would be great)</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">ciao</span> <br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">nestor</span> <o:p>
</o:p></p>
<pre style="margin-left:.5in">This message and any attachments are intended for the use of the addressee or addressees only.<o:p></o:p></pre>
<pre style="margin-left:.5in">The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<o:p></o:p></pre>
<pre style="margin-left:.5in">content is not permitted.<o:p></o:p></pre>
<pre style="margin-left:.5in">If you received this message in error, please notify the sender and delete it from your system.<o:p></o:p></pre>
<pre style="margin-left:.5in">Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></pre>
<pre style="margin-left:.5in"><o:p> </o:p></pre>
<pre style="margin-left:.5in">Please consider the environment before printing this email.<o:p></o:p></pre>
<pre style="margin-left:.5in"><o:p> </o:p></pre>
</div>
</body>
</html>