<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
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:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
mso-fareast-language:EN-GB;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:889925641;
mso-list-template-ids:-67334778;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level2 lfo3
{mso-level-start-at:2;}
@list l0:level2 lfo4
{mso-level-start-at:3;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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-GB link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>Just in case you did not receive this<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>..David<o:p></o:p></span></p><p class=MsoNormal><a name="_MailEndCompose"><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'><o:p> </o:p></span></a></p><span style='mso-bookmark:_MailEndCompose'></span><p class=MsoNormal><b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif'> MOIMS [mailto:moims-bounces@mailman.ccsds.org] <b>On Behalf Of </b>Nestor.Peccia@esa.int<br><b>Sent:</b> 20 September 2016 09:29<br><b>To:</b> Mario.Merri@esa.int<br><b>Cc:</b> moims@mailman.ccsds.org; cesg@mailman.ccsds.org<br><b>Subject:</b> Re: [MOIMS] MOIMS Comments to IOAG/MOSSG Report<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>Mario</span> <br><br><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>As CESG Chair I have the following comments to the MOIMS response to MOSSG documents</span> <o:p></o:p></p><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>The MOSSG report is generally very supportive of the MOIMS work, although concerns are raised on their slow adoption. Once the report is approved by the IOAG, it assumed that it should be promoted by the IOAG, thus speeding up adoption by missions. How can the IOAG and CCSDS team up to best achieve this?</span> <o:p></o:p></li></ul><ul type=disc><ol start=1 type=1><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo2'><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:blue'>Missions usually adopt published standards. Its slow motion is justified by the lack of a minimum suite of SM&C standards that guarantees interoperability</span> <o:p></o:p></li></ol></ul><ul type=disc><ol start=2 type=1><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo3'><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:blue'>IOAG has not given any priority to the Catalogue 3. MOSSG did it (but it is the opinion of the SG members and not the result of an IOAG Agency wide poll). CCSDS' comment will be to take them out in order to follow the same process and format of SC #1 and 2. IOAG has its internal procedure to do it.</span> <o:p></o:p></li></ol></ul><ul type=disc><ol start=3 type=1><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo4'><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:blue'>CCSDS shall issue a common and global comment for all 3 IOAG SCs (1, 2 and 3) wrt slow adoption by missions due to long elapsed time for production of standards (associated with the lack of resources)</span> <o:p></o:p></li><ul type=square><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level3 lfo4'><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:blue'>Just to give an example: When comparing our current Projects wrt SC#1 and taking out the already published standards (6), we have</span><span style='font-size:10.0pt;font-family:"Arial",sans-serif'> <b><span style='color:red'>3 Approved , 6 Drafts and 6 not yet existing Projects. This means 36 resouces from all Agencies</span></b></span> <o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level3 lfo4'><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:blue'>SC#2 status is worse</span><o:p></o:p></li></ul></ol></ul><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt'><b><u><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:blue'>CESG Chair Suggestion: </span></u></b><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:blue'>Issue global comment for all IOAG SCs on slow adoption by mission and lack of CCSDS resources to implement them</span> <o:p></o:p></p><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo4'><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>Considering the bullet above and the many comments/clarifications raised on the draft Catalog#3, it is suggested that a small joint team, MOSSG-MOIMS, initiate a technical discussion to refine Catalog#3.</span> <br><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:blue'>I disagree. CCSDS needs to produce recommendations and leave away this notion to continuously create new joint teams. </span><br><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:blue'>The idea was that the MOSSG completes its task after approval of the catalogue. </span><br><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:blue'>As both MOSSG Chairs are members of the SM&C WG (one of them being the Chair), the technical discussion is guaranteed within the CCSDS MOIMS SM&C WG. The Rome meeting is the ideal venue to discuss it from the technical point of view. Telecons and San Antonio meeting will also address this point.</span> <br><b><u><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:blue'>CESG Chair suggestion</span></u></b><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:blue'>: Enforce technical discussion of SC# 3 in the next 2 Technical meeting (Rome and San Antonio) and the usual monthly telecons.</span> <o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo4'><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>R1.1: The recommendation is generally well received that we should focus on a limited number of functional areas, however several comments have been raised on the scope of the high priority functional areas (see Calatog#3). In any case, even if minor misalignment in scope exists, we would like to give priority to the books that are close to publication.</span> <br><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:blue'>No comments shall be raised on priorities, because they are a consensus of the SG members and not the result of an agreed IOAG Agencies poll.</span> <br><b><u><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:blue'>CESG Chair Suggestion:</span></u></b><b><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:blue'> </span></b><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:blue'>Raise a global comment on SC#3: Take priorities out</span> <o:p></o:p></li></ul><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>I plan to circulate the 1st draft of the CCSDS Presentation to IOAG by todqay cob</span> <br><br><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>ciao</span> <br><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>nestor </span><o:p></o:p></p><pre>This message and any attachments are intended for the use of the addressee or addressees only.<o:p></o:p></pre><pre>The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<o:p></o:p></pre><pre>content is not permitted.<o:p></o:p></pre><pre>If you received this message in error, please notify the sender and delete it from your system.<o:p></o:p></pre><pre>Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Please consider the environment before printing this email.<o:p></o:p></pre></div></body></html>