<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ligatures:standardcontextual;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Hi Peter,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I did do a review of as much more of the book as I could manage in the limited time I have available for such reviews. The latest version from me, with mark-ups throughout, is attached.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I totally support Tom’s comments, for a couple of reasons, primary being adherence to the CCSDS Publication guidelines, including using terse style, and the size of section 3. I would admit, for myself, that complying with terse style
can be a personal challenge, but it really is essential in the heart of Blue Books. That said, I have absolutely no issue with including UML/SysML diagrams where they bring clarity, in part because they can be examples of their own form of terse and accurate
style. I find them to be of considerable value.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">You may want to think about taking those many pages of descriptive materials and moving them into their own “best practices” Magenta Book. I do realize that this represents work, but it would also have the useful effect of rendering the
required BB contents of the document in a more useful and accessible way. Right now it is a bit of a “door stop”, thick and heavy. We can discuss how best to do this if you are interested.<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"><b><span lang="EN-GB" style="font-size:12.0pt;color:black">From:
</span></b><span lang="EN-GB" style="font-size:12.0pt;color:black">Peter Van Der Plas <Peter.van.der.Plas@esa.int><br>
<b>Date: </b>Wednesday, January 10, 2024 at 9:19 AM<br>
<b>To: </b>Tom Gannett <thomas.gannett@tgannett.net>, Peter Shames <peter.m.shames@jpl.nasa.gov><br>
<b>Cc: </b>"moims-mp@mailman.ccsds.org" <moims-mp@mailman.ccsds.org><br>
<b>Subject: </b>[EXTERNAL] RE: CESG-P-2023-10-008 Approval to release CCSDS 529.1-R-1, Mission Operations—Mission Planning and Scheduling Services (Red Book, Issue 1) for CCSDS Agency review<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
</div>
<p class="MsoPlainText"><span lang="EN-GB">Dear Tom and Peter,<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">Please find here a first response to your comments on the Mission Planning and Scheduling Services Red Book as per below email.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">Regarding Tom's note on the content of section 3: The WG agrees to remove any descriptive text and UML diagrams from section 3. However, the tables in section 3 contain the specification of all data types as used in
the Mission Planning Services (section 4) and File Formats (section 7). As such, this is information passed "over the wire" (or in XML files) and is testable (we will cover this with test cases in our Yellow Book). As such, we believe this information qualifies
as Blue Book material. Note that this approach is similar as compared to other MO Services books. With the information in section 3 now becoming less descriptive, we may move the updated section 3 further down in the document, in favour of the Services and
File Formats specifications. In addition, the WG considers making the information in the current section 3 available in a new Magenta book on the "MP&S Information Model".<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">Please let us know if our suggested way forward is acceptable for you. We can then proceed updating the current Red Book accordingly, and to possibly initiate a new Magenta Book project.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">Regarding the table formatting problem as observed by Peter: This problem was introduced during the processing of our White Book and mainly affects the table borders and header colours. Below I have included an example
of the original layout of the tables in our White Book:<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB" style="mso-ligatures:none"><img width="629" height="122" style="width:6.552in;height:1.2708in" id="Picture_x0020_1" src="cid:image001.png@01DA43AB.5FBC5E60"></span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">We believe that we can correct the table borders and headers relatively easily (hopefully in an automated way using Word macros). As such, we will take the action to update the tables in the current Red Book as provided
by Tom on 2023-11-29.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">Regarding the other comments from Peter: we will soon provide a full response to all comments. Peter: You have indicated below that “I do commit to reading the rest of it and providing feedback”. Would you have an
idea when you will be able to provide your feedback on the remaining part of the book?<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">Best regards,<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">Peter<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="ES">ESA - European Space Agency<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="ES"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="ES">Peter van der Plas<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">EGSE and Ground Systems section (TEC-SWG)<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">Directorate of Technology, Engineering and Quality<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="NL">ESTEC<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="NL">Keplerlaan 1, PO Box 299, NL-2200 AG Noordwijk, The Netherlands<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><a href="mailto:Peter.van.der.Plas@esa.int"><span lang="NL">Peter.van.der.Plas@esa.int</span></a></span><span lang="NL"> | </span><span lang="EN-GB"><a href="https://urldefense.us/v3/__http:/www.esa.int__;!!PvBDto6Hs4WbVuu7!KHBO7a7nNHZrEQv9tgIxb-EJkK9BhMLF1EkLhsAwAHc-NV2k8Yo0PXVGEf3Ck3d7JSskYuuUYywXRiSlLWuP1PppSTJC8pVM9QUv$"><span lang="NL">www.esa.int</span></a></span><span lang="NL"><o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="FR">Phone +31 71 565 5848 | Fax +31 71 565 5420 | Mobile +31 6 81 75 01 50<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="FR"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="FR">-----Original Message-----<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">From: Thomas Gannett <<a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a>>
<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">Sent: Friday, December 1, 2023 4:29 PM<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">To: Peter Van Der Plas <<a href="mailto:Peter.van.der.Plas@esa.int">Peter.van.der.Plas@esa.int</a>><o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">Subject: FW: CESG-P-2023-10-008 Approval to release CCSDS 529.1-R-1, Mission Operations—Mission Planning and Scheduling Services (Red Book, Issue 1) for CCSDS Agency review<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="ES">Logothete, L.L.C.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><a href="mailto:thomas.gannett@tgannett.net"><span lang="ES">thomas.gannett@tgannett.net</span></a></span><span lang="ES"><o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">+1 443 472 0805<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">-----Original Message-----<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">From: CCSDS Secretariat [<a href="mailto:thomas.gannett@tgannett.net">mailto:thomas.gannett@tgannett.net</a>]<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">Sent: Friday, December 01, 2023 10:24 AM<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">To: <a href="mailto:tyamada@pub.isas.ac.jp">
tyamada@pub.isas.ac.jp</a>; <a href="mailto:roger.rocketbrain@btinternet.com">roger.rocketbrain@btinternet.com</a><o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">Cc: <a href="mailto:Peter.M.Shames@jpl.nasa.gov">
Peter.M.Shames@jpl.nasa.gov</a>; <a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a><o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">Subject: Re: CESG-P-2023-10-008 Approval to release CCSDS 529.1-R-1, Mission Operations—Mission Planning and Scheduling Services (Red Book, Issue 1) for CCSDS Agency review<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">Dear Document Rapporteur,<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">The CESG poll to approve release of CCSDS 529.1-R-1, Mission Operations—Mission Planning and Scheduling Services (Red Book, Issue 1) for CCSDS Agency review concluded with conditions. Please negotiate disposition of
the conditions directly with the AD(s) who voted to approve with conditions and CC the Secretariat on all related correspondence.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">CESG E-Poll Identifier: CESG-P-2023-10-008 Approval to release CCSDS 529.1-R-1, Mission Operations—Mission Planning and Scheduling Services (Red Book, Issue 1) for CCSDS Agency review<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">Results of CESG poll beginning 31 October 2023 and ending 30 November 2023:<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"> Abstain: 0 (0%)<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">Approve Unconditionally: 3 (60%) (Fischer, Aguilar Sanchez, Wilmot) Approve with Conditions: 2 (40%) (Shames, Cola) Disapprove with Comment: 0 (0%)
<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">CONDITIONS/COMMENTS:<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"> Peter Shames (Approve with Conditions): This is a new document, and I have given it a close read. There are a significant number of confusing definitions and terms, issues with presentation and formating, and
other issues with the document. I have not yet read it in its entirety, but there are already enough issues noted to request that the document be reviewed and "scrubbed". I do commit to reading the rest of it and providing feedback.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"> Tomaso de Cola (Approve with Conditions): Maybe it's more relavant for the update of other MAL existing book:<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">In the security annex it is claimed that the channel security is matter of the transport layer. From the existing MAL association blue books (i.e. MAL over TCP/HTTP/SPP/ZMTP) I cannot find however very specific details
on this. There are certainly mention about IPsec, TLS, SSL, HTTPS, but not such to provide means to implement a secure association.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"> Jonathan Wilmot (Approve Unconditionally): Comments to consider as part of agency review.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">1) In section 1.4 “security considerations are assumed to be handled at the MO framework layer or below” You might consider signed messages and/or file as being above the MO framework especially if the plans are to
be used on deployed space systems or critical operations. The term “body signature” seems misleading. Isn’t it just the body/contents of the structure?<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">2) Overall concern that with the MAL book is being substantially updated, some of the concepts referenced in the MAL framework may no longer be valid. Would this book have to change if the MAL has changes?<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">3) There is overall value in an exchangeable format for operations plan, but it should be understood that an organization’s mission operations facility already has systems in place that have been developed and certified
for the mission class at great cost. It would be useful for those mission operations facilities to have a standard format to exchange plans such that the plans could be integrated into their existing systems. This format could be used without having to replace
the existing framework and tools.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">4) In Figure 3-24: Position Data Type, there are several parameters listed as strings, is there a standard dictionary of terms that would be used? Something like Earth, Moon, Mars, as position references? I assume
alititude is above the PositionReference. This comment is general and not specific to the figure. All plans should be based on an standard DoT.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">Total Respondents: 5<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">No response was received from the following Area(s):<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"> CSS<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">SECRETARIAT INTERPRETATION OF RESULTS: Approved with Conditions<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">PROPOSED SECRETARIAT ACTION: Generate CMC poll after conditions have been addressed<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">* * * * * * * * * * * * * * * * * * * * * * * * Editor’s note:<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">Section 3 of this document, which is 129 pages in length and thus constitutes nearly half the document, is essentially a tutorial with a handful for requirements sprinkled in. It is as such in direct violation of the
both the letter and spirit of the Publications Manual:<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">“terse style: Style of specification in which normal text is limited to concise statements of requirements. Discussions concerning rationale, background, and other ancillary topics are constrained to be brief and
are set off from normal text, usually in a note, or sometimes in a subsection that is clearly labeled as being non-normative.” (1.6.1 TERMS)<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">“3.4.3.3 For normative-track documents,<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">a) specifications shall begin in section 3 and continue through as many subsequent sections as needed;<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">b) each specification shall be explicitly identified by a unique subsection or paragraph number;<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">c) text shall be written in terse style [emphasis added]; . . .”<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB">Since there is no provision in CCSDS procedures for granting dispensations for Publications Manual requirements, section 3 needs to be either removed from the document in its entirety, perhaps to be reworked as a Magenta
Book, or reduced to the handful of requirements it contains, possibly with the informative material replicated in a Green Book.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have
received this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).
<o:p></o:p></span></p>
</div>
</body>
</html>