<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:x="urn:schemas-microsoft-com:office:excel" 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="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
@font-face
        {font-family:Verdana;
        panose-1:2 11 6 4 3 5 4 4 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:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        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";}
p.msonormal0, li.msonormal0, div.msonormal0
        {mso-style-name:msonormal;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        font-family:Consolas;}
span.EmailStyle21
        {mso-style-type:personal-reply;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
.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><!--[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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span class="EmailStyle21">Dear Gippo,<o:p></o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle21"><o:p> </o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle21">The reason for including the CESG in this email discussion was not to "SPAM" them, that would waste their time.  Rather it was to make sure that they are a part of the discussion because they should be.  You must
 be aware that whatever fiddling you decide to do with the GFP at the SDLP to coding and synchronization interface also affects directly the CSS Area, for their SLE & CSTS service specs, Functional Resource (FR) model, Service Management, and architecture documents. 
 This is not just some SLS internal issue.  And, because these effects cross Area boundaries it is a concern for SEA as well.  It is in our charter to attend to such matters.  This is the same sort of consideration that has brought attention on some of the
 less than well thought out proposals from the Optical Com WG, like using Ethernet frames as space data link protocols.  I would expect you to welcome such support and not to castigate it.<o:p></o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle21"><o:p> </o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle21">Perhaps the issue with the wording of that sentence is just a matter of your use of English.  Perhaps what you meant to say was this:<o:p></o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle21"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Times New Roman",serif;color:blue">However,
</span><span style="font-size:14.0pt;font-family:"Times New Roman",serif;color:red">introducing
</span><span style="font-size:14.0pt;font-family:"Times New Roman",serif;color:blue">the Generic Framing Procedure entails matters affecting
</span><span style="font-size:14.0pt;font-family:"Times New Roman",serif;color:red">the communications
</span><span style="font-size:14.0pt;font-family:"Times New Roman",serif;color:blue">architecture stack,
</span><span style="font-size:14.0pt;font-family:"Times New Roman",serif;color:red">especially the
</span><span style="font-size:14.0pt;font-family:"Times New Roman",serif;color:blue">code & synch protocols
</span><span style="font-size:14.0pt;font-family:"Times New Roman",serif;color:red">and their interface to space data link protocols</span><span style="font-size:14.0pt;font-family:"Times New Roman",serif;color:blue">.
</span><br>
<br>
Lastly, I do want to remind you that even though this issue is technically within the SLS Area that it has ramifications well outside the area.  I think that you should expect continued interest and attention to this and to the Optical WG.  Unlike your continued
 attention to matters occurring <u>inside</u> the CFDP WG, this is actually within the scope of SEA and is a direct concern of CSS.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards, Peter<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></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-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Gian Paolo Calzolari <Gian.Paolo.Calzolari@esa.int><br>
<b>Date: </b>Thursday, November 14, 2019 at 3:11 AM<br>
<b>To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><br>
<b>Cc: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org>, Gilles Moury <Gilles.Moury@cnes.fr>, "Margherita.di.Giulio@esa.int" <Margherita.di.Giulio@esa.int><br>
<b>Subject: </b>Re: Your remark on SLS: [CESG] [EXTERNAL] CESG Meeting on 25 Oct . - Draft MoM<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:"Arial",sans-serif">Peter,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">        first of all I fail understanding how spamming the rest of CESG can help our discussion, but never mind.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Second, Margherita's sentence you comment does not state that SLP protocols need to be changed bur it rather puts accent on the impact on the "architecture stack".</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Nobody in SLS Area Plenary meeting as well as (two) CESG Meetings mentioned adding data types or anything else to Space Data Link Protocols.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Moreover, I do not "</span>invite the whole of SLS WG into this discussion<span style="font-size:10.0pt;font-family:"Arial",sans-serif">" and this is NOT what I "</span>wish to do<span style="font-size:10.0pt;font-family:"Arial",sans-serif">".</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Gilles and I simply reported the result of the discussion in the SLS Plenary.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Having said this, despite I think Margherita correctly captured the substance of the SLS reporting,  the only correction I think would be acceptable to that sentence is the following:</span>
<br>
<span style="font-size:14.0pt;font-family:"Times New Roman",serif;color:blue">However,
</span><span style="font-size:14.0pt;font-family:"Times New Roman",serif;color:red">introducing
</span><span style="font-size:14.0pt;font-family:"Times New Roman",serif;color:blue">the Generic Framing Procedure entails matters affecting architecture stack, code & synch, protocols.
</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">That's all on my side and will not comment further on this as the ball is now in the field of (some) SLS WGs for proper discussion.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Regards</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Gian Paolo</span> <br>
<br>
<br>
<br>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">From:        </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Shames, Peter M (US 312B)" <peter.m.shames@jpl.nasa.gov></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">To:        </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Gian.Paolo.Calzolari@esa.int" <Gian.Paolo.Calzolari@esa.int></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Cc:        </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Margherita.di.Giulio@esa.int" <Margherita.di.Giulio@esa.int>, "Gilles Moury" <Gilles.Moury@cnes.fr>, "CCSDS
 Engineering Steering Group - CESG Exec" <cesg@mailman.ccsds.org></span> <br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date:        </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">12-11-19 19:16</span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject:        </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Re: Your remark on SLS: [CESG] [EXTERNAL]  CESG Meeting on 25 Oct . - Draft MoM</span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="margin-left:.5in;text-align:center">
<hr size="0" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<o:p> </o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
Gippo,<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
 <o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
What is stated in inaccurate by any measure since GFP does not have anything to say about space data link protocols.  The only relationship that could possibly exist in the future would be to add another data type (or four) to the link layer protocols that
 GFP would formally recognize.  This requires no changes to those protocols, which is, in fact, a feature of GFP.<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
 <o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
I'm not suggesting that you should not invite the whole of SLS WG into this discussion is that is what you wish to do.  I am asking that we all not make statements that are confusing and inaccurate.  The whole purpose of sending out the MoM and asking for feedback
 is to avoid such issues.<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
 <o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
Regards, Peter<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
 <o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
 <o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<b><span style="font-size:12.0pt">From: </span></b><span style="font-size:12.0pt">Gian Paolo Calzolari <Gian.Paolo.Calzolari@esa.int><b><br>
Date: </b>Tuesday, November 12, 2019 at 2:50 AM<b><br>
To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><b><br>
Cc: </b>"Margherita.di.Giulio@esa.int" <Margherita.di.Giulio@esa.int>, Gilles Moury <Gilles.Moury@cnes.fr><b><br>
Subject: </b>Your remark on SLS: [CESG] [EXTERNAL] CESG Meeting on 25 Oct . - Draft MoM</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
 <o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Peter,</span> <span style="font-size:10.0pt;font-family:"Arial",sans-serif">
<br>
       with respect to your comment in the attached snapshot, I propose to do NO update to the MoMs also to avoid another useless saga on updates to updates to updates.</span>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
The natter will be properly discussed in SLS and this is the important message conveyed by the MoMs</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Regards</span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Gian Paolo</span> <br>
<br>
<br>
<img width="1418" height="294" style="width:14.7708in;height:3.0625in" id="_x0000_i1026" src="cid:image001.gif@01D59B9A.8F996000"><br>
<br>
<br>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
From:        </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Shames, Peter M\(US 312B\) via CESG" <cesg@mailman.ccsds.org></span>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
To:        </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Margherita.di.Giulio@esa.int" <Margherita.di.Giulio@esa.int>, "cesg@mailman.ccsds.org" <cesg@mailman.ccsds.org></span>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Date:        </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">11-11-19 20:09</span>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Subject:        </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Re: [CESG] [EXTERNAL]  CESG Meeting on 25 Oct . - Draft MoM</span>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Sent by:        </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"CESG" <cesg-bounces@mailman.ccsds.org></span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="margin-left:.5in;text-align:center">
<hr size="0" width="98%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
[attachment "d 0.1 CESG-Fall 19 Minutes of Meeting_ DRAFT-SEA.docx" deleted by Gian Paolo Calzolari/esoc/ESA]
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><br>
<span style="font-size:12.0pt">Hi Margherita,</span> <br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt">I had a few minutes free and have provided my feedback early, for a change.</span>
<br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt">Cheers, Peter</span> <br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt"> </span> <br>
<b><span style="font-size:12.0pt">From: </span></b><span style="font-size:12.0pt">CESG <cesg-bounces@mailman.ccsds.org> on behalf of "Margherita.di.Giulio@esa.int" <Margherita.di.Giulio@esa.int><b><br>
Date: </b>Monday, November 11, 2019 at 8:12 AM<b><br>
To: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><b><br>
Subject: </b>[EXTERNAL] [CESG] CESG Meeting on 25 Oct . - Draft MoM</span> <br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Dear All,</span><span style="font-size:12.0pt">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
please find attached the draft Minute of Meeting of CESG Meeting on 25th October at ESOC.</span><span style="font-size:12.0pt">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Let me have your comments by 20th November. <br>
If you edit the MoM, please use track changes.</span><span style="font-size:12.0pt">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
<br>
Kind regards<br>
Margherita </span><span style="font-size:12.0pt"><br>
<br>
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
<br>
--------------------------------------------------------------</span><b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#00A1E0"><br>
Margherita di Giulio</span></b><span style="font-size:12.0pt"> </span><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#5F5F5F"><br>
Ground Station Systems Division</span><span style="font-size:12.0pt"> </span><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#5F5F5F"><br>
Backend Software Section (OPS-GSB)</span><span style="font-size:12.0pt"> <br>
</span><b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#5F5F5F"><br>
<br>
European Space Agency ESA/ESOC</span></b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#5F5F5F"><br>
Robert-Bosch-Str. 5<br>
D-64293 Darmstadt - Germany<br>
Tel: +49-6151-902779<br>
e-mail: Margherita.di.Giulio@esa.int</span> <br>
<span style="font-size:10.0pt;font-family:"Courier New"">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New"">protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New"">this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New"">personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).</span>
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:2.5in;margin-left:.5in">
<span style="font-size:10.0pt;font-family:"Courier New""><br>
_______________________________________________<br>
CESG mailing list<br>
CESG@mailman.ccsds.org</span><u><span style="color:blue"><br>
</span></u><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg"><span style="font-size:10.0pt;font-family:"Courier New"">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg</span></a><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="font-size:10.0pt;font-family:"Courier New"">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="font-size:10.0pt;font-family:"Courier New"">protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="font-size:10.0pt;font-family:"Courier New"">this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="font-size:10.0pt;font-family:"Courier New"">personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).</span><o:p></o:p></p>
<pre style="margin-left:.5in">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre>
<pre style="margin-left:.5in">protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre>
<pre style="margin-left:.5in">this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre>
<pre style="margin-left:.5in">personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).<o:p></o:p></pre>
</div>
</body>
</html>