<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=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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Webdings;
panose-1:5 3 1 2 1 5 9 6 7 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
span.moz-txt-tag
{mso-style-name:moz-txt-tag;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;}
span.EmailStyle25
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.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 bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>Dear CESG Members,<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Conditions for approval of CESG-P-2017-06-003 Approval to release CCSDS 522.2-R-1, Mission Operations—Mission Data Product Distribution Services (Red Book, Issue 1) for CCSDS Agency review have been disposed to the satisfaction of the AD(s) who voted to approve with conditions. The Secretariat will now proceed with CMC polling to authorize release for CCSDS Agency review.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>On 18/10/2018 15:32, Barkley, Erik J (3970) wrote:<o:p></o:p></p><p class=MsoNormal><span style='font-family:"Georgia",serif;color:#1F497D'>Sam,</span><o:p></o:p></p><p class=MsoNormal><span style='font-family:"Georgia",serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-family:"Georgia",serif;color:#1F497D'>Thanks for taking the time to chat during the Berlin meetings. I now consider my conditions to be retired.</span><o:p></o:p></p><p class=MsoNormal><span style='font-family:"Georgia",serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-family:"Georgia",serif;color:#1F497D'>Best regards,</span><o:p></o:p></p><p class=MsoNormal><span style='font-family:"Georgia",serif;color:#1F497D'>-Erik </span><o:p></o:p></p><p class=MsoNormal><span style='font-family:"Georgia",serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext'> Sam Cooper <a href="mailto:sam@brightascension.com"><sam@brightascension.com></a> <br><b>Sent:</b> Thursday, October 11, 2018 00:38<br><b>To:</b> Barkley, Erik J (3970) <a href="mailto:Erik.J.Barkley@jpl.nasa.gov"><Erik.J.Barkley@jpl.nasa.gov></a>; Thomas Gannett <a href="mailto:thomas.gannett@tgannett.net"><thomas.gannett@tgannett.net></a>; Burleigh, Scott C (312B) <a href="mailto:Scott.C.Burleigh@jpl.nasa.gov"><Scott.C.Burleigh@jpl.nasa.gov></a><br><b>Cc:</b> <a href="mailto:Mario.Merri@esa.int">Mario.Merri@esa.int</a>; 'Smith, Danford S. (GSFC-5800)' <a href="mailto:danford.s.smith@nasa.gov"><danford.s.smith@nasa.gov></a>; Shames, Peter M (312B) <a href="mailto:Peter.M.Shames@jpl.nasa.gov"><Peter.M.Shames@jpl.nasa.gov></a><br><b>Subject:</b> Re: CCSDS MO MDPD Service specification</span><o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>Hi Erik,<br><br>We now have a fuller example given in section 2.3.1. For the COM archive usage, these relationships are detailed in section 3 (specifically 3.2.(4, 5, 6) and 3.3.(4, 5, 6)).<br><br>Best regards,<br>Sam.<o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext'> Burleigh, Scott C (312B) [mailto:Scott.C.Burleigh@jpl.nasa.gov] <br><b>Sent:</b> Wednesday, October 10, 2018 1:33 PM<br><b>To:</b> Sam Cooper <sam@brightascension.com>; Thomas Gannett <thomas.gannett@tgannett.net>; Barkley, Erik J (3970) <Erik.J.Barkley@jpl.nasa.gov><br><b>Cc:</b> Mario.Merri@esa.int; 'Smith, Danford S. (GSFC-5800)' <danford.s.smith@nasa.gov>; Shames, Peter M (312B) <Peter.M.Shames@jpl.nasa.gov><br><b>Subject:</b> RE: FW: CCSDS MO MDPD Service specification<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Sorry, guys, I didn’t realize that a response to my stated condition on this book had been sent; I must have misfiled it. Assuming that the response was the same explanation that was given for 522x0, I agree that my condition is resolved in exactly the same way that my condition on the earlier document was resolved. My reservations are undiminished.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Scott<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Sam Cooper <<a href="mailto:sam@brightascension.com">sam@brightascension.com</a>> <br><b>Sent:</b> Wednesday, October 10, 2018 9:00 AM<br><b>To:</b> Thomas Gannett <<a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a>>; Barkley, Erik J (3970) <<a href="mailto:Erik.J.Barkley@jpl.nasa.gov">Erik.J.Barkley@jpl.nasa.gov</a>>; Burleigh, Scott C (312B) <<a href="mailto:Scott.C.Burleigh@jpl.nasa.gov">Scott.C.Burleigh@jpl.nasa.gov</a>><br><b>Cc:</b> <a href="mailto:Mario.Merri@esa.int">Mario.Merri@esa.int</a>; 'Smith, Danford S. (GSFC-5800)' <<a href="mailto:danford.s.smith@nasa.gov">danford.s.smith@nasa.gov</a>>; Shames, Peter M (312B) <<a href="mailto:Peter.M.Shames@jpl.nasa.gov">Peter.M.Shames@jpl.nasa.gov</a>><br><b>Subject:</b> Re: FW: CCSDS MO MDPD Service specification<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>Sure, no problem, just trying to keep things moving.<br><br><span style='font-size:11.0pt'><o:p></o:p></span></p><div><p class=MsoNormal>On 10/10/2018 16:56, Thomas Gannett wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Thanks, Sam.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>I am hoping to get an explicit OK from Scott for notification to the CESG; failing to receive that I will use what you just sent.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Tom</span><o:p></o:p></p><div><div style='border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in'><p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></p></div><p class=MsoNormal><span style='color:#1F497D'>Logothete, L.L.C.</span><o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'><a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a></span><o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'>+1 443 472 0805</span><o:p></o:p></p></div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma",sans-serif'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma",sans-serif'> Sam Cooper [<a href="mailto:sam@brightascension.com">mailto:sam@brightascension.com</a>] <br><b>Sent:</b> Wednesday, October 10, 2018 11:49 AM<br><b>To:</b> Thomas Gannett; <a href="mailto:Erik.J.Barkley@jpl.nasa.gov">Erik.J.Barkley@jpl.nasa.gov</a>; Scott C Burleigh<br><b>Cc:</b> <a href="mailto:Mario.Merri@esa.int">Mario.Merri@esa.int</a>; 'Smith, Danford S. (GSFC-5800)'; 'Shames, Peter M (312B)'<br><b>Subject:</b> Re: FW: CCSDS MO MDPD Service specification</span><o:p></o:p></p></div></div><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>Hi Tom,<br><br>Scott raised an identical comment on our specification for Common services (522x0):<br><br><br><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>Scott Burleigh (Approve with Conditions)</b>: This seems to be excellent work, but I don't see how it can be released as a draft Recommended Standard. According to section 6261 of the A02.1-Y-4 Procedures book, a document can be released as a Recommended Standard only after "two independent and interoperable prototypes or implementations ... have been developed and demonstrated in an operationally relevant environment". Because this specification relies wholly on the definitions of MAL and COM, which are abstract and therefore cannot be implemented, I don't see how two interoperable prototypes of this specification can ever be independently developed and demonstrated. I think this book is probably an excellent statement of <span class=moz-txt-tag><b>*</b></span><b>requirements<span class=moz-txt-tag>*</span></b> for a new Recommended Standard, hence an excellent Green Book. But I don't know how it can be released as a Red Book. My approval is conditional upon an explanation.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:red'>Response:</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:red'>Our services are defined in an abstract notation that becomes concrete when one of our technology mappings is used. Currently we have one published (524.1-B-1) and three in the CCSDS pipeline. So, to test these service specifications you just need to select a mapping and test using that. It is what we have done for the services defined in the COM specification.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:red'>The reality is that all these parts form aspects of the concrete protocol, you need to select a book from each aspect to be able to implement it all. So you need the MAL and COM, and you need a service specification, and you need a technology mapping. You probably also might as well choose one of our APIs (Magenta books) but that is not needed for interoperability. None of these are Green Book material (informational) they are all specification. We separate them into separate books as they are not specific to any one combination, i.e. you can use out SPP mapping for any service, in the same way you can use this service specification over any technology mapping.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:red'>The issue is that currently CCSDS book colouring does not really cover this approach if taken literally, I suspect Blue Book were originally intended for something very fixed and very focussed such as time format encodings. Now that we, and other working groups, are looking to create suites of standards that can be combined and recombined in different ways (but are still formal specification in their own right but only part of the whole) the current book colourings get a bit confusing.</span><o:p></o:p></p><p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:red'>So, TL;DR, these are formal specifications and therefore should be Blue. Yes, you must combine these with other existing SM&C Blue books to be implementable/testable, but that approach has already been agreed as long as we clearly identify this “stack” in the yellow book produced during testing.</span> <br><br>Scott's response to this was (email dated 14/09/2017):<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Sam, I recognize that your response to the condition I stated reflects what has become the reality of CCSDS specification approval thinking, and on that basis I guess I have to say that you have met my condition.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>This is by no means to say that I find this current reality satisfactory. If the Blue Book definitions and procedures in the Yellow Book cannot accommodate the work that is being done for SM&C, then either the Yellow Book must be updated to reflect reality or else the SM&C books cannot be Blue. If we are doing otherwise then we are kidding ourselves, and in the long run that compromise will damage CCSDS.<br><br></span>So whilst I cannot comment on higher regards of Yellow book procedures, I would say that we have met Scott's identical condition on this.<br><br><br>For Erik's comments, if these are not addressed directly then I would suggest we move these to Agency review RIDs to keep the moment up on this specification.<br><br><br>Best regards,<br>Sam.<o:p></o:p></p><div><p class=MsoNormal>On 10/10/2018 16:21, Thomas Gannett wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Erik, Scott:</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>I have received indication that Peter has signed off on resolution of his poll conditions for the poll below, but I have so far failed to find responses from you two. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Can you either forward correspondence related to resolution of your conditions or signify by return email your acquiescence?</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>The current version is attached.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>* * * * * * * * * * * * * * * * * * * * * * * *</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>CESG E-Poll Identifier: CESG-P-2017-06-003 Approval to release CCSDS 522.2-R-1, Mission Operations—Mission Data Product Distribution Services (Red Book, Issue 1) for CCSDS Agency review</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Results of CESG poll beginning 30 June 2017 and ending 14 July 2017:</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> Abstain: 1 (16.67%) (Calzolari)</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Approve Unconditionally: 2 (33.33%) (Merri, Behal)</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Approve with Conditions: 3 (50%) (Barkley, Shames, Burleigh)</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Disapprove with Comment: 0 (0%)</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>CONDITIONS/COMMENTS:</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Erik Barkley (Approve with Conditions): Two conditions, and a general observation, question.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>1) Pg 2-2 , at the top, RE: "...The product type represents a category of mission data to which the product belongs</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>(e.g., parameter value evolution in a given time period, actions history)..."</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>How is a "parameter value evolution in a given time period.." a product type? I suspect the type, as in classification, that is being attempted here is engineering telemetry. If I think of controlling, via product type, I doubt I'd be selecting access control just for evething that is on a time-series basis -- rather I think it would be types of telemetry/particular instrument readings, etc. They all have a time-series nature, but that is not the fundamental type. Can a better example be provided?</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>2) Pg 2-7 states that the catalog entry is created and stored in the "COM Archive". Please include a mapping that ensures the "the product type, the product source", and the "product format" conform with COM Archive service needs (its not clear how this maps, to, for example, "area service", "object instance identifier", etc)</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>General observation/question (not a condition): in reviewing this, I could not but help to think about the fact that some CCSDS member space agencies already have various data distribution capabilities in place. For example, ESA has the Planetary Science Archive (PSA) and NASA has the Planetary Data System (PDS). To the best of my knowledge these organizations have already cooperated in developing standards related to distribution of various mission science products, particularly, through the IPDA (for example see <a href="https://planetarydata.org/standards/IPDA_PDAP_v1.0.pdf">https://planetarydata.org/standards/IPDA_PDAP_v1.0.pdf</a>) I can't help but wonder with regard to this recommendation if in fact CCSDS is not overlapping with standards that have already been established. Perhaps there is a need for a liaison to be established? At the least, it seems that perhaps there could be supporting standards to this recommendation and therefore an overall stronger body of work.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Peter Shames (Approve with Conditions): This document is too immature to be esnt out for agency review.See attached PID form and document with mark-ups for details.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Scott Burleigh (Approve with Conditions): This seems to be excellent work, as best I can tell, but I don't see how I can in good conscience approve its release as a draft Recommended Standard. According to section 6261 of the A02.1-Y-4 Procedures book, a document can be released as a Recommended Standard only after "two independent and interoperable prototypes or implementations ... have been developed and demonstrated in an operationally relevant environment". Because this specification is entirely abstract, I don't see how two interoperable prototypes of the specification can ever be independently developed and demonstrated. I think this book is probably an excellent statement of *requirements* for a new Recommended Standard, hence an excellent Green Book. But I don't know how it can be released as a Red Book. My approval is conditional upon an explanation.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Total Respondents: 6</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>No response was received from the following Area(s):</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>SOIS</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>SECRETARIAT INTERPRETATION OF RESULTS: Approved with Conditions</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>PROPOSED SECRETARIAT ACTION: Generate CMC poll after conditions have been addressed</span><o:p></o:p></p><div style='border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in'><p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></p></div><p class=MsoNormal><span style='color:#1F497D'>Logothete, L.L.C.</span><o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'><a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a></span><o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'>+1 443 472 0805</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma",sans-serif'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma",sans-serif'> <a href="mailto:Mario.Merri@esa.int">Mario.Merri@esa.int</a> [<a href="mailto:Mario.Merri@esa.int">mailto:Mario.Merri@esa.int</a>] <br><b>Sent:</b> Friday, October 05, 2018 8:59 AM<br><b>To:</b> <a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a><br><b>Cc:</b> Sam Cooper; Dan Smith<br><b>Subject:</b> Re: CCSDS MO MDPD Service specification</span><o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Arial",sans-serif'>Dear Tom,</span> <br><br><span style='font-size:11.0pt;font-family:"Arial",sans-serif'>I think that now the document can be put finally under Agency Review. Sam will provide you with the agreed version of the document.</span> <br><br><span style='font-size:11.0pt;font-family:"Arial",sans-serif'>Thanks,</span> <br><br><span style='font-size:11.0pt;font-family:"Arial",sans-serif'>__Mario</span> <br><span style='font-size:9.0pt;font-family:"Arial",sans-serif;color:purple'>----- Forwarded by Mario Merri/esoc/ESA on 05/10/2018 14:56 -----</span> <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 (312B)" <a href="mailto:Peter.M.Shames@jpl.nasa.gov"><Peter.M.Shames@jpl.nasa.gov></a></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'>Sam Cooper <a href="mailto:sam@brightascension.com"><sam@brightascension.com></a></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'>Maciej Józef Prokopczyk <a href="mailto:mprokopczyk@gmv.com"><mprokopczyk@gmv.com></a>, "Mario Merri" <a href="mailto:Mario.Merri@esa.int"><Mario.Merri@esa.int></a>, Mehran Sarkarati <a href="mailto:Mehran.Sarkarati@esa.int"><Mehran.Sarkarati@esa.int></a>, "Dan Smith" <a href="mailto:danford.s.smith@nasa.gov"><danford.s.smith@nasa.gov></a></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'>05/10/2018 01:03</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: CCSDS MO MDPD Service specification</span> <o:p></o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="100%" noshade style='color:#A0A0A0' align=center></div><p class=MsoNormal style='margin-bottom:12.0pt'> <o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Ok. I (obviously) just do not have the spare cycles at this point to deal with this. Agency review will have to suffice.</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> </span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Cheers, Peter</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> </span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> </span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> </span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><b><span style='font-family:"Calibri",sans-serif'>From: </span></b><span style='font-family:"Calibri",sans-serif'>Sam Cooper <a href="mailto:sam@brightascension.com"><sam@brightascension.com></a><b><br>Date: </b>Thursday, October 4, 2018 at 1:10 AM<b><br>To: </b>Peter Shames <a href="mailto:Peter.M.Shames@jpl.nasa.gov"><Peter.M.Shames@jpl.nasa.gov></a><b><br>Cc: </b>Maciej Józef Prokopczyk <a href="mailto:mprokopczyk@gmv.com"><mprokopczyk@gmv.com></a>, Mario Merri <a href="mailto:Mario.Merri@esa.int"><Mario.Merri@esa.int></a>, Mehran Sarkarati <a href="mailto:Mehran.Sarkarati@esa.int"><Mehran.Sarkarati@esa.int></a>, Dan Smith <a href="mailto:danford.s.smith@nasa.gov"><danford.s.smith@nasa.gov></a><b><br>Subject: </b>Re: CCSDS MO MDPD Service specification</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> </span><o:p></o:p></p><p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:0in'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>HI Peter,<br><br>Just to let you know I'm assuming Maciej's update is satisfactory for you. I'm going to apply a bit of polish to it and pass it to Tom for further processing. <br><br>My opinion is that anything left outstanding should be delegated to the Agency review at this point.<br><br>Best regards,<br>Sam.</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>On 20/09/2018 08:40, Sam Cooper wrote:</span><o:p></o:p></p><p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:2.5in;margin-left:0in'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Hi Peter,<br><br>Just a gentle reminder to cast your eyes over Maciej's updated document. Just to keep things moving, if I've not heard anything by the end of September I'll assume nothing major is wrong and update it and pass it to Tom.<br><br>Cheers,<br>Sam.</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>On 14/08/2018 09:24, Sam Cooper wrote:</span><o:p></o:p></p><p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:2.5in;margin-left:0in'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Peter, could you check you are happy with the updates as made?<br><br>Once that's done I'll do a pass over it to check it before we pass it back to Tom for putting out for Agency review.<br><br>Sam.</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>On 13/08/2018 16:33, Maciej Józef Prokopczyk wrote:</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#004080'>Dear All,</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#004080'> </span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#004080'>Here is a document with (I hope) all updates requested in the Excel file (attached) and also updates Sam asked for (examples of type, source, format).</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#004080'> </span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#004080'>Please let me know if it is OK and how should we proceed.</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#004080'> </span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#004080'>Best regards,</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#004080'>Maciej</span><o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="100%" noshade style='color:#A0A0A0' align=center></div><table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 width="100%" style='width:100.0%;border-collapse:collapse'><tr style='height:6.0pt'><td width="100%" style='width:100.0%;padding:0in 0in 0in 0in;height:6.0pt'><table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 width="100%" style='width:100.0%;border-collapse:collapse'><tr style='height:6.0pt'><td width="28%" valign=top style='width:28.0%;padding:0in 0in 0in 0in;height:6.0pt'></td><td width="40%" valign=top style='width:40.0%;padding:0in 0in 0in 0in;height:6.0pt'><p class=MsoNormal style='mso-line-height-alt:6.0pt'><b><span style='font-size:10.0pt;font-family:"Verdana",sans-serif'>Maciej Prokopczyk</span></b><span style='font-size:8.0pt;font-family:"Verdana",sans-serif'><br>Kierownik projektów, Inżynier oprogramowania/<br>Project manager, Software engineer</span> <o:p></o:p></p></td><td width="31%" valign=top style='width:31.0%;padding:0in 0in 0in 0in;height:6.0pt'><p class=MsoNormal style='line-height:105%'><span style='font-size:8.0pt;line-height:105%;font-family:"Verdana",sans-serif'>GMV <br>Ul. Hrubieszowska 2<br>01-209 Warszawa<br>Tel. +48 22 395 51 65<br>Fax +48 22 395 51 67 </span><u><span style='font-family:"Calibri",sans-serif;color:#0082BF'><br></span></u><a href="http://www.gmv.com/"><span style='font-size:8.0pt;line-height:105%;font-family:"Verdana",sans-serif;color:#A2A2A2'>www.gmv.com </span></a><o:p></o:p></p><table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 width=0 style='width:165.0pt;border-collapse:collapse'><tr style='height:6.0pt'><td width=24 style='width:.25in;padding:0in 0in 0in 0in;height:6.0pt'></td><td width=39 style='width:29.25pt;padding:0in 0in 0in 0in;height:6.0pt'></td><td width=39 style='width:29.25pt;padding:0in 0in 0in 0in;height:6.0pt'></td><td width=39 style='width:29.25pt;padding:0in 0in 0in 0in;height:6.0pt'></td><td width=39 style='width:29.25pt;padding:0in 0in 0in 0in;height:6.0pt'></td><td width=39 style='width:29.25pt;padding:0in 0in 0in 0in;height:6.0pt'></td></tr></table><p style='margin:0in;margin-bottom:.0001pt;line-height:105%'><span style='font-family:"Calibri",sans-serif'> </span><o:p></o:p></p><p class=MsoNormal style='line-height:105%'> <o:p></o:p></p><table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 width=0 style='width:1.0in;border-collapse:collapse'><tr style='height:6.0pt'><td width=96 style='width:1.0in;padding:0in 0in 0in 0in;height:6.0pt'></td></tr></table></td></tr></table></td></tr></table><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#004080'> </span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Sam Cooper [</span><a href="mailto:sam@brightascension.com"><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF'>mailto:sam@brightascension.com</span></a><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>] <b><br>Sent:</b> Thursday, August 2, 2018 12:26 PM<b><br>To:</b> Maciej Józef Prokopczyk </span><a href="mailto:mprokopczyk@gmv.com"><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF'><mprokopczyk@gmv.com></span></a><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><br>Cc:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Mario Merri </span><a href="mailto:Mario.Merri@esa.int"><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF'><Mario.Merri@esa.int></span></a><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>; Mehran Sarkarati </span><a href="mailto:Mehran.Sarkarati@esa.int"><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF'><Mehran.Sarkarati@esa.int></span></a><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>; Dan Smith </span><a href="mailto:danford.s.smith@nasa.gov"><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF'><danford.s.smith@nasa.gov></span></a><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><br>Subject:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Re: CCSDS MO MDPD Service specification</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> </span><o:p></o:p></p><p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:0in'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Attached.<br><br>I was wondering if we could add the following modifications to the specification to help users understand what kind of data this service can be used for. At the moment it is not obvious that it can be used for data other than existing MO services (which is not the case as I understand it).<br><br>So in section 1.6 (Definitions) expand "Product Type" to something like:<br>product type: A distinct category of mission data, e.g., CCSDS space packet, navigation orbit files, image files, parameter time series, action history.<br><br>Then add to section 2 of the specification an expansion of those examples to really explain the concept that it can hold anything but also to give real examples of the product type, source, format. I think it would be good to add a section 2.2.1 that expands the following examples:<br> CCSDS Space packet<br> Navigation orbit files<br> Mission specific images files (for example JPEGs)<br> Parameter time series<br> Action history<br><br>If you could add in a first revision of these examples I'm happy to help you polish the text in that section.<br><br>Cheers,<br>Sam.<br><br><br><br></span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>On 02/08/2018 10:31, Maciej Józef Prokopczyk wrote:</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#004080'>Hello Sam,</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#004080'> </span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#004080'>I will try to do it at the end of the next week. Could you provide me the last version of the specification in the Word format?</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#004080'> </span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#004080'>Best regards,</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#004080'>Maciej</span><o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="100%" noshade style='color:#A0A0A0' align=center></div><table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 width="100%" style='width:100.0%;border-collapse:collapse'><tr style='height:6.0pt'><td width="100%" style='width:100.0%;padding:0in 0in 0in 0in;height:6.0pt'><table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 width="100%" style='width:100.0%;border-collapse:collapse'><tr style='height:6.0pt'><td width="28%" valign=top style='width:28.0%;padding:0in 0in 0in 0in;height:6.0pt'></td><td width="40%" valign=top style='width:40.0%;padding:0in 0in 0in 0in;height:6.0pt'><p class=MsoNormal style='mso-line-height-alt:6.0pt'><b><span style='font-size:10.0pt;font-family:"Verdana",sans-serif'>Maciej Prokopczyk</span></b><span style='font-size:8.0pt;font-family:"Verdana",sans-serif'><br>Kierownik projektów, Inżynier oprogramowania/<br>Project manager, Software engineer</span> <o:p></o:p></p></td><td width="31%" valign=top style='width:31.0%;padding:0in 0in 0in 0in;height:6.0pt'><p class=MsoNormal style='line-height:105%'><span style='font-size:8.0pt;line-height:105%;font-family:"Verdana",sans-serif'>GMV <br>Ul. Hrubieszowska 2<br>01-209 Warszawa<br>Tel. +48 22 395 51 65<br>Fax +48 22 395 51 67 </span><u><span style='font-family:"Calibri",sans-serif;color:#0082BF'><br></span></u><a href="http://www.gmv.com/"><span style='font-size:8.0pt;line-height:105%;font-family:"Verdana",sans-serif;color:#A2A2A2'>www.gmv.com </span></a><o:p></o:p></p><table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 width=0 style='width:165.0pt;border-collapse:collapse'><tr style='height:6.0pt'><td width=24 style='width:.25in;padding:0in 0in 0in 0in;height:6.0pt'></td><td width=39 style='width:29.25pt;padding:0in 0in 0in 0in;height:6.0pt'></td><td width=39 style='width:29.25pt;padding:0in 0in 0in 0in;height:6.0pt'></td><td width=39 style='width:29.25pt;padding:0in 0in 0in 0in;height:6.0pt'></td><td width=39 style='width:29.25pt;padding:0in 0in 0in 0in;height:6.0pt'></td><td width=39 style='width:29.25pt;padding:0in 0in 0in 0in;height:6.0pt'></td></tr></table><p style='margin:0in;margin-bottom:.0001pt;line-height:105%'><span style='font-family:"Calibri",sans-serif'> </span><o:p></o:p></p><p class=MsoNormal style='line-height:105%'> <o:p></o:p></p><table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 width=0 style='width:1.0in;border-collapse:collapse'><tr style='height:6.0pt'><td width=96 style='width:1.0in;padding:0in 0in 0in 0in;height:6.0pt'></td></tr></table></td></tr></table></td></tr></table><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#004080'> </span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Sam Cooper [</span><a href="mailto:sam@brightascension.com"><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF'>mailto:sam@brightascension.com</span></a><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>] <b><br>Sent:</b> Thursday, August 2, 2018 11:14 AM<b><br>To:</b> Maciej Józef Prokopczyk </span><a href="mailto:mprokopczyk@gmv.com"><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF'><mprokopczyk@gmv.com></span></a><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><br>Cc:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Mario Merri </span><a href="mailto:Mario.Merri@esa.int"><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF'><Mario.Merri@esa.int></span></a><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>; Mehran Sarkarati </span><a href="mailto:Mehran.Sarkarati@esa.int"><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF'><Mehran.Sarkarati@esa.int></span></a><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>; Dan Smith </span><a href="mailto:danford.s.smith@nasa.gov"><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF'><danford.s.smith@nasa.gov></span></a><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><br>Subject:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Re: CCSDS MO MDPD Service specification</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> </span><o:p></o:p></p><p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:0in'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Hi Maciej,<br><br>Ok so the next step is to update the document taking into account the changes listed in that Excel sheet, don't forget to include the changes requested by Peter in the last set of discussions as the sheet still has those marked down as Reject.<br><br>When do you think you will be able to do this update by?<br><br>Sam.<br><br><br><br><br></span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>On 01/08/2018 16:18, Shames, Peter M (312B) wrote:</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Hi Sam,</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> </span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Ok. I can accept those changes.</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> </span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Thanks, Peter</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> </span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> </span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><b><span style='font-family:"Calibri",sans-serif'>From: </span></b><span style='font-family:"Calibri",sans-serif'>Sam Cooper </span><a href="mailto:sam@brightascension.com"><span style='font-family:"Calibri",sans-serif;color:#0082BF'><sam@brightascension.com></span></a><b><span style='font-family:"Calibri",sans-serif'><br>Date: </span></b><span style='font-family:"Calibri",sans-serif'>Wednesday, August 1, 2018 at 8:07 AM<b><br>To: </b>Peter Shames </span><a href="mailto:peter.m.shames@jpl.nasa.gov"><span style='font-family:"Calibri",sans-serif;color:#0082BF'><peter.m.shames@jpl.nasa.gov></span></a><b><span style='font-family:"Calibri",sans-serif'><br>Cc: </span></b><span style='font-family:"Calibri",sans-serif'>Mario Merri </span><a href="mailto:Mario.Merri@esa.int"><span style='font-family:"Calibri",sans-serif;color:#0082BF'><Mario.Merri@esa.int></span></a><span style='font-family:"Calibri",sans-serif'>, Mehran Sarkarati </span><a href="mailto:Mehran.Sarkarati@esa.int"><span style='font-family:"Calibri",sans-serif;color:#0082BF'><Mehran.Sarkarati@esa.int></span></a><span style='font-family:"Calibri",sans-serif'>, Dan Smith </span><a href="mailto:danford.s.smith@nasa.gov"><span style='font-family:"Calibri",sans-serif;color:#0082BF'><danford.s.smith@nasa.gov></span></a><span style='font-family:"Calibri",sans-serif'>, Maciej Józef Prokopczyk </span><a href="mailto:mprokopczyk@gmv.com"><span style='font-family:"Calibri",sans-serif;color:#0082BF'><mprokopczyk@gmv.com></span></a><b><span style='font-family:"Calibri",sans-serif'><br>Subject: </span></b><span style='font-family:"Calibri",sans-serif'>Re: CCSDS MO MDPD Service specification</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> </span><o:p></o:p></p><p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:0in'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Hi Peter,<br><br>Sorry if you got caught up in internal discussions, not my intension!<br><br>I think we've finally hammered out the last few updates in the excel sheet for you to review, we've only looked at your yellow commented lines and have proposed next to it a change or clarification (ignore the other columns where we say REJECTED etc, we just haven't updated those yet).<br><br>Could you check that you are happy with these proposed changes please and then we can move this forward.<br><br>Best regards,<br>Sam.<br><br><br><br></span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>On 09/07/2018 16:27, Shames, Peter M (312B) wrote:</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Ah, and now the attachment …</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> </span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>-p</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> </span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> </span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><b><span style='font-family:"Calibri",sans-serif'>From: </span></b><span style='font-family:"Calibri",sans-serif'>Sam Cooper </span><a href="mailto:sam@brightascension.com"><span style='font-family:"Calibri",sans-serif;color:#0082BF'><sam@brightascension.com></span></a><b><span style='font-family:"Calibri",sans-serif'><br>Date: </span></b><span style='font-family:"Calibri",sans-serif'>Thursday, June 14, 2018 at 7:32 AM<b><br>To: </b>Peter Shames </span><a href="mailto:peter.m.shames@jpl.nasa.gov"><span style='font-family:"Calibri",sans-serif;color:#0082BF'><peter.m.shames@jpl.nasa.gov></span></a><b><span style='font-family:"Calibri",sans-serif'><br>Cc: </span></b><span style='font-family:"Calibri",sans-serif'>Mario Merri </span><a href="mailto:Mario.Merri@esa.int"><span style='font-family:"Calibri",sans-serif;color:#0082BF'><Mario.Merri@esa.int></span></a><span style='font-family:"Calibri",sans-serif'>, Mehran Sarkarati </span><a href="mailto:Mehran.Sarkarati@esa.int"><span style='font-family:"Calibri",sans-serif;color:#0082BF'><Mehran.Sarkarati@esa.int></span></a><span style='font-family:"Calibri",sans-serif'>, Dan Smith </span><a href="mailto:danford.s.smith@nasa.gov"><span style='font-family:"Calibri",sans-serif;color:#0082BF'><danford.s.smith@nasa.gov></span></a><span style='font-family:"Calibri",sans-serif'>, Maciej Józef Prokopczyk </span><a href="mailto:mprokopczyk@gmv.com"><span style='font-family:"Calibri",sans-serif;color:#0082BF'><mprokopczyk@gmv.com></span></a><b><span style='font-family:"Calibri",sans-serif'><br>Subject: </span></b><span style='font-family:"Calibri",sans-serif'>CCSDS MO MDPD Service specification</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> </span><o:p></o:p></p><p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:0in'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Hi Peter,<br><br>Apologies in advance here, this may take some recollection on your part but hopefully you'll be able to work it out!<br><br>You provided some comments on one of our draft specification as part of CESG review before Agency review almost exactly one year ago. After a lot of going round the houses we have finally managed to collection a set of responses to your comments. <br><br>I have attached them in a spreadsheet and also include your original PDF review document with your comments in for your reference. Please could you cast your eye over the responses and let me know what you think.<br><br>Again, sorry for the long delay, hopefully you can get to grips with it again and we can get this specification moving!<br><br>Best regards,<br>Sam.<br><br><br><br><br><br></span><o:p></o:p></p><p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:0in'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><br><br><br><br></span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'> <o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:18.0pt;font-family:Webdings;color:green'><br>P </span><span style='font-size:7.0pt;font-family:"Arial",sans-serif;color:green'>Please consider the environment before printing this e-mail.</span> <o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'> <o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:18.0pt;font-family:Webdings;color:green'><br>P </span><span style='font-size:7.0pt;font-family:"Arial",sans-serif;color:green'>Please consider the environment before printing this e-mail.</span><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> </span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> </span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> </span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'> <o:p></o:p></p><pre>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre><pre>protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre><pre>this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre><pre>personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (<a href="mailto:dpo@esa.int">dpo@esa.int</a>).<o:p></o:p></pre></blockquote><p class=MsoNormal> <o:p></o:p></p></blockquote><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p></div></body></html>